202 | | 1) Definition of topic: [[BR]] |
203 | | |
204 | | a) Use for messages, not generalized data; assume relatively low rate. [[BR]] |
205 | | b) Use for OMF messages. [[BR]] |
206 | | c) Use for "event record messages", that can be logged. [[BR]] |
207 | | d) XMPP server, in public IP space. [[BR]] |
208 | | e) Entities connect, and are authenticated. [[BR]] |
209 | | f) An entity may start a pub/sub node. [[BR]] |
210 | | g) When an entity subscribes, a message is sent to publisher requesting authorization. [[BR]] |
211 | | h) Operations plan for XML Messaging Service. [[BR]] |
212 | | |
213 | | 2) Who: Rudra Dutta (NCSU); LEAD Anirban Mandal (RENCI); Christoph Dwertmann (NICTA); Ahmed El-Hassany (IU); Harry Mussman (GPO) [[BR]] |
| 202 | |
| 203 | 1) Goals [[BR]] |
| 204 | |
| 205 | For a detailed list, see the Spiral 4 SOW of the IMF project; these include: [[BR]] |
| 206 | |
| 207 | 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]] |
| 208 | |
| 209 | |
| 210 | 2) Tasks [[BR]] |
| 211 | |
| 212 | For a detailed list, see the Spiral 4 SOW of the IMF project; these include: [[BR]] |
| 213 | |
| 214 | Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC12. [[BR]] |
| 215 | |
| 216 | Support use in GENI by many tools, including GEMINI and GIMI I&M tools [[BR]] |
| 217 | |
| 218 | Define operations plan for XML Messaging Service. [[BR]] |
| 219 | |
| 220 | |
| 221 | 3) Team [[BR]] |
| 222 | |
| 223 | Rudra Dutta (NCSU) [[BR]] |
| 224 | LEAD Anirban Mandal (RENCI) [[BR]] |
| 225 | Christoph Dwertmann (NICTA) [[BR]] |
| 226 | Ahmed El-Hassany (IU) [[BR]] |
| 227 | Harry Mussman (GPO) [[BR]] |
| 228 | |