Changes between Version 55 and Version 56 of GpoDoc


Ignore:
Timestamp:
03/20/11 12:01:30 (9 years ago)
Author:
Aaron Falk
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GpoDoc

    v55 v56  
    2323
    2424=== GENI Aggregate Provider's Agreement ===
    25 
    26 http://groups.geni.net/geni/attachment/wiki/ComprehensiveSecurityPgm/Aggregate%20Provider%20Agreement%20v3.pdf
    27 [[BR]]
    28 "GENI is a federated network testbed designed to allow researchers to experiment with network applications and ser- vices that benefit from distribution across a wide geographic area. All uses of GENI should be consistent with this high-level goal.
    29 
    30 Management Authorities (MAs), providing aggregates and components operating as a part of GENI, are well-served by having a common set of principles to establish an expected level of service, and methods of cooperation. Such principles, presented in this agreement, benefit the security and stability of the entire GENI suite of infrastructures."
    31 
    32 This document was reviewed and approved by the COMIS working group (see [wiki:Gec9COMISAgenda]), and is adopted for use in GENI Spiral 3.
     25  ''GENI is a federated network testbed designed to allow researchers to experiment with network applications and ser- vices that benefit from distribution across a wide geographic area. All uses of GENI should be consistent with this high-level goal.  Management Authorities (MAs), providing aggregates and components operating as a part of GENI, are well-served by having a common set of principles to establish an expected level of service, and methods of cooperation. Such principles, presented in this agreement, benefit the security and stability of the entire GENI suite of infrastructures.''[[br]]
     26  This document was reviewed and approved by the COMIS working group (see [wiki:Gec9COMISAgenda]), and is adopted for use in GENI Spiral 3.[[br]]
     27  http://groups.geni.net/geni/attachment/wiki/ComprehensiveSecurityPgm/Aggregate%20Provider%20Agreement%20v3.pdf
    3328
    3429=== Emergency Stop Procedure ===
     30  ''One of the essential early operational requirements for the GENI facility is the need to manage and coordinate the stop and/or containment of GENI resources among all GENI projects in the case of an urgent request.  Emergency stop is the system used to respond to incidents of interference or resource exhaustion caused either unintentionally (misconfiguration), or intentionally (malware).  This is intended to protect GENI aggregates when they begin to integrate with other aggregates, and when GENI begins to interconnect with outside networks.  For Spiral 2, GENI aggregates will have active experimentation and increased integration and interconnection with other aggregates or non-GENI networks.  This document will provide an approach for an early emergency stop service in Spiral 2, as well as a potential evolution for emergency stop for future spirals.''[[br]]
     31  This document was reviewed and approved by the OMIS working group (see [wiki:Gec8OmisAgenda]), and is adopted for use in GENI Spiral 2 and 3.[[br]]
     32  http://groups.geni.net/geni/attachment/wiki/GENIMetaOpss/Emergency_Stop_System_Description_v5.1.doc
    3533
    36 http://groups.geni.net/geni/attachment/wiki/GENIMetaOpss/Emergency_Stop_System_Description_v5.1.doc
    37 [[BR]]
    38 "One of the essential early operational requirements for the GENI facility is the need to manage and coordinate the stop and/or containment of GENI resources among all GENI projects in the case of an urgent request.  Emergency stop is the system used to respond to incidents of interference or resource exhaustion caused either unintentionally (misconfiguration), or intentionally (malware).  This is intended to protect GENI aggregates when they begin to integrate with other aggregates, and when GENI begins to interconnect with outside networks.
    39 
    40 For Spiral 2, GENI aggregates will have active experimentation and increased integration and interconnection with other aggregates or non-GENI networks.  This document will provide an approach for an early emergency stop service in Spiral 2, as well as a potential evolution for emergency stop for future spirals."
    41 
    42 This document was reviewed and approved by the OMIS working group (see [wiki:Gec8OmisAgenda]), and is adopted for use in GENI Spiral 2 and 3.
    4334
    4435=== GMOC Concept of Operations ===
     36  ''The GENI facility will require a model of operations moving forward that is both responsive enough to the needs of GENI users and stakeholders (researchers using the facility, users opting-in to GENI, and GENI operators) and flexible enough to evolve with the federated, reconfigurable nature of the facility.  We expect that GENI research users will require a facility that is highly available, with a clear and simple process for getting support, which provides a robust set of highly detailed data about its use and operations, and which communicates maintenance and experiment affecting issues in a responsive and transparent way.''[[br]]
     37  This document was reviewed and approved by the COMIS working group (see [wiki:Gec9COMISAgenda]), and is adopted for use in GENI Spiral 3.[[br]]
     38  http://groups.geni.net/geni/attachment/wiki/GENIMetaOps/GENI-Concept-of-Operations-v2.1.doc
    4539
    46 http://groups.geni.net/geni/attachment/wiki/GENIMetaOps/GENI-Concept-of-Operations-v2.1.doc
    47 
    48 "The GENI facility will require a model of operations moving forward that is both responsive enough to the needs of GENI users and stakeholders (researchers using the facility, users opting-in to GENI, and GENI operators) and flexible enough to evolve with the federated, reconfigurable nature of the facility.
    49 
    50 We expect that GENI research users will require a facility that is highly available, with a clear and simple process for getting support, which provides a robust set of highly detailed data about its use and operations, and which communicates maintenance and experiment affecting issues in a responsive and transparent way."
    51 
    52 This document was reviewed and approved by the COMIS working group (see [wiki:Gec9COMISAgenda]), and is adopted for use in GENI Spiral 3.
    5340
    5441=== Legal, Law Enforcement and Regulatory Plan ===
    55 
    56 http://groups.geni.net/geni/attachment/wiki/ComprehensiveSecurityPgm/LLR%20Responsibilities%20of%20GENI.pdf
    57 
    58 "At first glance, it may appear that the GENI federation and its governance entities have no legal responsibilities of their own since "GENI" owns virtually no infrastructure and researchers are ultimately responsible for the actions of their individual experiments. While both statements are true, there is a subtlety here as (1) lawyers, law enforcement and regulatory agencies (LLR) do not know this, and (2) no one party necessarily has all the information to address inquiries from these entities. Therefore, collaboration will be necessary to resolve some LLR issues and the need for a plan to handle such requests is established.
    59 
    60 This document begins by further motivating this need with several scenarios or use cases, some based on previous experience in other federations and testbeds. These scenarios also drive the need for proactive measures, such as, having a simple mechanism to reach slice owners and heading off future DMCA requests which could discourage campus participation in GENI. Finally, it becomes clear that someone is needed to fulfill a facilitator role to help route LLR requests to the appropriate parties when a single institution is unable to address the request it receives entirely on its own."
    61 
    62 This document was reviewed and approved by the Ops Agreements meeting at GEC10 (see [wiki:GEC10OpsAgreements]), and is adopted for use in GENI Spiral 3.
     42  ''At first glance, it may appear that the GENI federation and its governance entities have no legal responsibilities of their own since "GENI" owns virtually no infrastructure and researchers are ultimately responsible for the actions of their individual experiments. While both statements are true, there is a subtlety here as (1) lawyers, law enforcement and regulatory agencies (LLR) do not know this, and (2) no one party necessarily has all the information to address inquiries from these entities. Therefore, collaboration will be necessary to resolve some LLR issues and the need for a plan to handle such requests is established.  This document begins by further motivating this need with several scenarios or use cases, some based on previous experience in other federations and testbeds. These scenarios also drive the need for proactive measures, such as, having a simple mechanism to reach slice owners and heading off future DMCA requests which could discourage campus participation in GENI. Finally, it becomes clear that someone is needed to fulfill a facilitator role to help route LLR requests to the appropriate parties when a single institution is unable to address the request it receives entirely on its own.''[[br]]
     43  This document was reviewed and approved by the Ops Agreements meeting at GEC10 (see [wiki:GEC10OpsAgreements]), and is adopted for use in GENI Spiral 3.[[br]]
     44  http://groups.geni.net/geni/attachment/wiki/ComprehensiveSecurityPgm/LLR%20Responsibilities%20of%20GENI.pdf
    6345
    6446----
     
    6749
    6850=== GENI Aggregate Manager API ===
    69  GENI-SE-CF-AMAPI-01.0
    70 
    71  ''This document describes a programming interface, known as an API, for allowing GENI experimenters to contact aggregates of GENI resources to learn what resources are available and present requests for resource reservations. The GENI Aggregate Manager API is a common API for reserving disparate resources from multiple GENI aggregates.''
    72 
    73  http://groups.geni.net/geni/attachment/wiki/GeniAggregateManagerApiDoc/GENI-SE-CF-AMAPI-01.0.pdf (updated 9/1/10)
    74 
    75  This document has a wiki page at GeniAggregateManagerApiDoc.
     51  GENI-SE-CF-AMAPI-01.0[[br]]
     52  ''This document describes a programming interface, known as an API, for allowing GENI experimenters to contact aggregates of GENI resources to learn what resources are available and present requests for resource reservations. The GENI Aggregate Manager API is a common API for reserving disparate resources from multiple GENI aggregates.''[[br]]
     53  http://groups.geni.net/geni/attachment/wiki/GeniAggregateManagerApiDoc/GENI-SE-CF-AMAPI-01.0.pdf (updated 9/1/10)[[br]]
     54  This document has a wiki page at GeniAggregateManagerApiDoc.
    7655
    7756=== GENI Spiral 2 Security Plan ===