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]] |
| 203 | |
| 204 | 1) Goals [[BR]] |
| 205 | |
| 206 | In I&M, a Measurement Orchestration (MO) service needs to interact with the I&M services; one way to do so is to use the OMF interface, currently used (for example) by the OMF Experiment Controller to command an OMF Resource Controller (RC) that is installed next to an application. [[BR]] |
| 207 | |
| 208 | The OMF messages are carried between an EC and RC by an XML pub/sub messaging service, based on an XMPP server. [[BR]] |
| 209 | |
| 210 | For GENI, an XML Messaging service will be provided to carry these OMF messages, and thus enable orchestration. [[BR]] |
| 211 | |
| 212 | However, such a service may have other useful functions, such as transporting Event Records (ERs). [[BR]] |
| 213 | |
| 214 | To be generally useful, authentication and authorization functions must be provided. [[BR]] |
| 215 | |
| 216 | For a detailed list of all goals defined for the XML Messaging service, see the Spiral 4 SOW of the IMF project. [[BR]] |
| 217 | |
| 218 | |
| 219 | 2) Tasks [[BR]] |
| 220 | |
| 221 | Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC13. [[BR]] |
| 222 | |
| 223 | The XML Mesaaging service will be built by the IMF project. For a detailed task list, see the Spiral 4 SOW of the IMF project. [[BR]] |