GPN Network Program Planning 2010
From GPNWiki
The Great Plains Network Executive Council charged the Network Program Committee to formulate a plan to address the following key networking objectives:
1.1.1: Provide connectivity to national high performance research and education networks with the capacity, reliability and services needed to support the requirements of the GPN members.
1.1.2: Take advantage of opportunities to create partnerships and to interconnect with other regional next-generation network(s).
1.3.2: Lead the discussion among GPN members with respect to issues raised in national networking forums, e.g. the Quilt, Internet2, to both inform our members and to establish GPN’s position on these issues.
1.3.3: Participate in and take leadership roles in activities of selected advance networking organizations (regional, national and international).
Contents |
Status Report
Milestone 1. Set "Committed Bandwidth headroom trigger" for adding more bandwidth. (6 Gig @ 95th percentile on the monthly graph will prompt an investigation into whether more bandwidth is needed.){Completed}
Minutes
Committee Members
The members of the Planning Sub-Committee are
- Cort Buffington, KanREN,
- Shannon Sperling, MORENET,
- P. J. Clayton, MORENET,
- Von Royal, ONEnet,
- Brad Fleming, KanREN, and
- Kent Christensen, UNL
Focus Areas for Planning
- Research network bandwidth needs
- Ongoing high-bandwidth research needs
- One-time high-bandwidth needs
- Scheduled high-bandwidth application needs
- Other research bandwidth needs
- Commodity bandwidth needs and cost-effective ways to meet them
- I2 CPS
- NLR Transit Rail
- WiscNet Peering Service
- Group Commodity Internet purchases and bandwidth sharing
- Direct peering with other R&E networks
- Other approaches
- Committed ‘ headroom’ triggers for adding bandwidth
- Downstream connections (other entities connected ‘behind’ a GPN Connector)
- GPN connection services and pricing
- Currently flat pricing/one size fits all
- Differentiate pricing for research and commodity?
- Usage-based?
- Tiered – minimum floor that each connector pays for x bandwidth, then tiered pricing above the floor?
- ??
- Identify the relevant network-related organizations, meetings, working groups, etc. that GPN should be engaged with and assign a primary and secondary contact
- Determine what information should be disseminated from these events, to who (e.g. Executive Committee, Network Technical Committee, member contacts), and in what fashion
- Review the Network Program structure and recommend changes, if any that would make it more effective.
- Other areas as discovered
Method of Work
- Network Program and Technical Committee members prioritize the list of issues to addressed (there may not be sufficient time to resolve all of these issues this FY)
- Review current utilization statistics and forecast bandwidth needs
- Hold a GPN Networking Summit with interested parties and Internet2 staff and selected Internet 2 Advisory Committee Members to understand Internet2’s future directions
- Consult with other R&E networks on how they are addressing these issues
- Draft plan by GPN Network Program Committee
- Executive Council Approval
Tentative Milestones
1. Set "Committed Bandwidth headroom trigger" for adding more bandwidth. (6 Gig @ 95th percentile on the monthly graph will prompt an investigation into whether more bandwidth is needed.)
2. Get Bandwidth projections from members. (Received information from 5 members, waiting for information from 2 members){02/26}
3. Size connection to I2 based on the bandwidth projections and relevant calculations. {March 5}
4. Identify the relevant network-related organizations, meetings, working groups, etc. that GPN should be engaged with and assign a primary and secondary contact. Determine what information should be disseminated from these events, to who (e.g. Executive Committee, Network Program Committee, Network Technical Committee, member contacts), and in what fashion. {March 12}
5. Suggest Network Equipment upgrades needed for increased bandwidth and connections. {March 26}
6. Look at NOC management and futures. {March 31}
