Changes between Version 66 and Version 67 of clusterdvlan


Ignore:
Timestamp:
12/07/09 12:59:52 (12 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • clusterdvlan

    v66 v67  
    292292== 5.3.4  First Phase:  Connect Cluster D Aggregates via NLR FrameNet Service ==
    293293
    294  The first phase will be to connect Cluster D aggregates via the NLR FrameNet service, as shown in Figure 5.  [[BR]]
     294 The first phase will connect Cluster D aggregates via the NLR FrameNet service, as shown in Figure 5.  [[BR]]
    295295 
    296296 Figure 5,  Connections Between Cluster D Aggregates via NLR FrameNet Service
     
    311311  See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figures 6-2, 6-3 and 6-4]].[[BR]]
    312312
    313  Similarly, the suggested approach to connectivity specification at [[http://groups.geni.net/syseng/wiki/RspecConnectivity RSpec Connectivity]], was:  “we give the backbone priority in selecting a network's VLAN ID and aggregates must map the ID within their local network by whatever means is most convenient for them. This way, the experimenter need only know what backbone the aggregate is connected to, and can design the network from there.”
    314 
    315 
    316 
    317 == 5.3.5  Second Phase:  Interconnect Backbones via iGENI Crossconnect ==
    318 
    319  See Fig 6
    320 
    321  The iGENI (Starlight) crossconnect includes the Starlight L2 crossconnect service in Chicago, which connects to multiple backbone networks, both domestic and international, including NLR and Internet2.
    322  See [[http://www.startap.net/starlight/NETWORKS/   Starlight]]
    323  See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  Starlight GLIF GOLE May, 2006]]
    324  The Starlight service should be able to bridge connections between multiple backbone networks, allowing access to distant testbeds.  It may be able to bridge VLANs between NLR and Internet2, if allowed.
     313 Similarly, the suggested approach to connectivity specification at [[http://groups.geni.net/syseng/wiki/RspecConnectivity RSpec Connectivity]], was:  “we give the backbone priority in selecting a network's VLAN ID and aggregates must map the ID within their local network by whatever means is most convenient for them. This way, the experimenter need only know what backbone the aggregate is connected to, and can design the network from there.”[[BR]]
     314
     315
     316
     317== 5.3.5  Second Phase:  Use iGENI Crossconnect to Interconnect Backbones and to Connect to International Testbeds ==
     318
     319 The second phase will use the iGENI crossconnect to interconnect backbones, and to connect endpoint aggregates to international testbeds, as shown in Figure 6.[[BR]]
     320
     321 Figure 6,  Use of iGENI Crossconnect to Interconnect Backbones and to Connect to International Testbeds
     322 
     323 
     324 
     325 The iGENI (Starlight) crossconnect service includes the Starlight L2 crossconnect service in Chicago, which connects to multiple backbone networks, including NLR FramewNet and Internet2 GENI WAVE and NLR C-Wave, and to multiple international testbeds, including Japan, Korea, South America and Europe.[[BR]]
     326 See [[http://www.startap.net/starlight/NETWORKS/   for more detail on Starlight facility]] [[BR]]
     327 See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  for more detail on Starlight GLIF GOLE May, 2006]][[BR]]
     328 The Starlight crossconnect service should be able to bridge connections between multiple backbone networks, to enable connection of:
     329  Cluster D endpoint aggergate via Internet2 GENI WAVE
     330  Cluster D endpoint aggergate via NLR C-Wave
     331  Aggregate from another cluster, i.e., Cluster C (ProtoGENI) aggregate, via Internet2 GENI WAVE
     332 The Starlight crossconnect service should be able to bridge connections between a backbone networks and an international tesbed, to enable connection of:
     333  Cluster D endpoint aggragate to an international testbed
     334  Aggregate from another cluster, i.e., Cluster C (ProtoGENI) aggregate, to an international testbed.
     335