Changes between Version 1 and Version 2 of InstMeasTopic_4.6MessagingService


Ignore:
Timestamp:
02/16/12 12:03:17 (8 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstMeasTopic_4.6MessagingService

    v1 v2  
    88[wiki:InstMeasTopic_4.6MessagingService  Work in Progress]  [[BR]]
    99
    10 1)  Definition of topic:  [[BR]]
    1110
    12 a)  Use for messages, not generalized data;  assume relatively low rate.  [[BR]]
     11== 1)  Goals ==
    1312
    14 b)  Use for OMF messages.  [[BR]]
     13 For a detailed list, see the Spiral 4 SOW of the IMF project;  these include:  [[BR]]
    1514
    16 c)  Use for "event record messages", that can be logged.  [[BR]]
     15 2.     (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.   [[BR]]
    1716
    18 d)  XMPP server, in public IP space.   Consider AMQP server?  Consider IF-MAP server? [[BR]]
     17 4.     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. [[BR]]
    1918
    20 e)  Entities connect, and are authenticated.  [[BR]]
     19 6.     (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.  [[BR]]
    2120
    22 f)  An entity may start a pub/sub node.  [[BR]]
     21 7.     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.  [[BR]]
    2322
    24 g)  When an entity subscribes, a message is sent to publisher requesting authorization.  [[BR]]
     23 9.     (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.  [[BR]]
     24
     25 10.    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).  [[BR]]
     26
     27 11.    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.  [[BR]]
     28
     29 12.    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.  [[BR]]
    2530
    2631
    2732
    28 2)  Who: Rudra Dutta (NCSU);  Anirban Mandal (RENCI);  LEAD Christoph Dwertmann (NICTA);  Ahmed El-Hassany (IU);  Prasad Calyam (OSC);  Deniz Gurken (UH) [[BR]]
     33==  2)  Tasks ==
     34
     35 For a detailed list, see the Spiral 4 SOW of the IMF project; these include:  [[BR]]
     36
     37 Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC12. [[BR]]
     38
     39 Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
     40
     41 Define operations plan for XML Messaging Service.  [[BR]]
     42
     43
     44== 3)  Team ==
     45 
     46 Rudra Dutta (NCSU) [[BR]]
     47 LEAD Anirban Mandal (RENCI) [[BR]]
     48 Christoph Dwertmann (NICTA) [[BR]]
     49 Ahmed El-Hassany (IU) [[BR]]
     50 Harry Mussman (GPO) [[BR]]
     51
     52
     53== 4)  Meetings ==
     54
     55 
     56 (organized calls or meetings before GEC13?)  [[BR]]
     57
     58 Review conclusions in pre-meeting at GEC13
     59
     60 Review with working team at GEC13
     61
     62
     63== 5)  Open Issues ==
     64
     65
     66== 6)  Definition of XML Messaging Service ==
     67
     68 a)  Use for messages, not generalized data;  assume relatively low rate.  [[BR]]
     69 b)  Use for OMF messages.  [[BR]]
     70 c)  Use for "event record messages", that can be logged.  [[BR]]
     71 d)  XMPP server, in public IP space.  [[BR]]
     72 e)  Entities connect, and are authenticated.  [[BR]]
     73 f)  An entity may start a pub/sub node.  [[BR]]
     74 g)  When an entity subscribes, a message is sent to publisher requesting authorization.  [[BR]]
     75