Opened 10 years ago

Closed 10 years ago

#176 closed (wontfix)

Document plan for VLAN integration

Reported by: hdempsey@bbn.com Owned by: Srini Seetharaman
Priority: major Milestone: ENTGENI: S1.c Integrate EntGENI with GENI virtual ethernets
Component: GPO Version: SPIRAL1
Keywords: Cc: nickm@stanford.edu, matt@internet2.edu, appenz@cs.stanford.edu
Dependencies:

Description

Please document your plans for Ethernet VLAN integration on the GENI network, including how multiple Enterprise GENI sites may be connected over Internet2 via tunnelling or other means. Please include your schedule for completing integration with a prototype Ethernet VLAN. (BBN may be available as an end site if you require a second site for integration).

Change History (4)

comment:1 Changed 10 years ago by Srini Seetharaman

Owner: changed from appenz@cs.stanford.edu to Srini Seetharaman

comment:2 Changed 10 years ago by Srini Seetharaman

As far the integration demo is concerned, we used TCP port based virtualization across both E-GENI and PL-GENI. Heidi, could you please clarify the requirement here?

comment:3 Changed 10 years ago by hdempsey@bbn.com

The original requirement was to show how two or more sites (such as the Princeton and Stanford demo sites) would interconnect Enterprise GENI VLANs with Ethernet VLANS in I2 on the GENI wave. It was assumed that some tunneling might be required to connect all three types of VLANs. Obviously the demo did not pursue this option. I believe Stanford has no plans to pursue this type of integration, but will support interconnections with OpenFlow VLANS in the I2 and NLR infrastructure when those projects install their OpenFlow switches.

comment:4 Changed 10 years ago by Srini Seetharaman

Cc: appenz@cs.stanford.edu added
Resolution: wontfix
Status: newclosed

This is correct. We will allow interconnection through other means in the future. I will mark the ticket as wontfix. Please re-open if there is any concern.

Note: See TracTickets for help on using tickets.