Req AR – Architecture Requirements. These requirements raise the need of federation support from the CMFs and the support of typical abstractions used to accomplish the federation such as slices for accountability and clearinghouse for authentication. Therefore, several of these requirements are seen just as if the CMFs provide the mechanisms to do it, not the way the federation, messages and semantics, is going to be done. All the federation detailed discussion and specifications are going to be considered in WP4. Requirement XXXXXX FOAM OMF ProtoGENI I&M XXXXXX I&M OMF I&M ProtoGENI Req AR01 Req AR02 Req AR03 Req AR04 Req AR05 Req AR06 Req AR07 Req AR08 Req AR09 Req AR10 Req AR11 Req AR12 Req AR13 Req AR14 Req AR15 Req AR16 Req AR17 Req AR18 Req AR19 Req AR20 Req AR21 Req AR22 Req AR23 Req AR24 Req AR25 Req AR26 Req AR Req AR28 AR7, AR8, AR9 - Since the beginning, Expedient and GENI (and XXXXXX) we designed to support users from outside (the Internet) to participate in some experiment within the experimental infrastructure. Therefore, this makes possible also for one experiment participate, or be the input, for other experiment using a web interface (opt-in users). This is something planned to be tested in the XXXXXX, and later this functionality could be incorporated. AR11 - After discussion with the evaluators, we got a consensus that in AR11, XXXXXX has the mechanism support of SFA in the aggregate manager level, and SFA is an open interface. Therefore, it is fully supported. AR12 - It is related to measurements and addressed in Section 7.2 (FIBRE-BR Monitoring Integration Approach). AR14 - This requirement is about out-of-band network management, such that allocation of resources, routing and signalling can be done without affecting the rest of the requirements. Although this is supported by default in ProtoGENI, it was verified that depending how the islands are structured with separated control and management networks, this can be supported by all CMFs.
