wiki:InstMeasTopic_4.6MessagingService

Version 3 (modified by hmussman@bbn.com, 8 years ago) (diff)

--

4.6) Messaging Service

XML Messaging Service

Work in Progress

1) Goals

For a detailed list, see the Spiral 4 SOW of the IMF project; these include:

  1. (a) Define, (b) prototype, demonstrate and operate a GENI Messaging service, that operates in public IP space, to provide XML message routing services utilizing an XMPP server, plus pub/sub services following XEP-0060; show how multiple servers could be federated.
  1. Include entity authentication for entities registered to your GENI Messaging service (XMPP server), using SASL and certificates; public key certificates for each entity can be stored locally, or retrieved from a registry. Generating certificates, or certifying, is not within the scope; the scope includes the capability to receive such certificates and store/retrieve in/from a registry.
  1. (a) Define, (b) prototype and demonstrate a GENI I&M Orchestration capability to manage I&M services/slivers all within one slice; use ORBIT Management Framework (OMF) software modules provided by NICTA, including the Experiment Controller (EC) and the Resource Controller (RC), that communicate using the GENI Messaging service. As proof of concept, develop OMF-style RC modules for one or more optical substrate devices.
  1. Define, prototype and demonstrate an authorization mechanism for your I&M Orchestration capability; consider the message signing being proposed by NICTA. This goal relates to the authority (end-to-end) of a given entity to perform a given actuation action. Scope includes ensuring that there is a provision for messages to be injected into the messaging system with accompanying signatures, and that messages with signatures are carried through the messaging service without damaging or altering the signature so they can be verified by and endpoint. Scope includes generating and verifying signatures.
  1. (a) Define, (b) prototype and demonstrate a GENI I&M Measurement Pub/Sub capability to transport event (or measurement) records; include software modules that collect the records, communicate using a pub/sub mechanism utilizing an XMPP server, archive the records in a repository, search the records, and display the records.
  1. Include an authorization mechanism for your Measurement Pub/Sub capability that is based on XEP-0060 Authorize Access Model. Scope includes authorization related issues related to the pub/sub records, and repositories (thus going beyond Goal 4, which this parallels).
  1. Demonstrate your Measurement Pub/Sub capability by transporting and distributing standardized GENI “resource event records”, as defined by the NetKarma project; these records could describe events such as assignments, faults or errors.
  1. Include a data repository associated with your Measurement Pub/Sub capability, that could subscribe to a node and archive all event messages. Scope includes internalizing into the GENI Messaging Service an instance of the type of repository of Goal 9.

2) Tasks

For a detailed list, see the Spiral 4 SOW of the IMF project; these include:

Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC12.

Support use in GENI by many tools, including GEMINI and GIMI I&M tools

Define operations plan for XML Messaging Service.

3) Team

Rudra Dutta (NCSU)
LEAD Anirban Mandal (RENCI)
Christoph Dwertmann (NICTA)
Ahmed El-Hassany (IU)
Harry Mussman (GPO)

4) Meetings

(organized calls or meetings before GEC13?)

Review conclusions in pre-meeting at GEC13

Review with working team at GEC13

5) Open Issues

6) Definition of XML Messaging Service

a) Use for messages, not generalized data; assume relatively low rate.
b) Use for OMF messages.
c) Use for "event record messages", that can be logged.
d) XMPP server, in public IP space.
e) Entities connect, and are authenticated.
f) An entity may start a pub/sub node.
g) When an entity subscribes, a message is sent to publisher requesting authorization.