Changes between Version 36 and Version 37 of clusterdvlan

Timestamp:

10/28/09 17:47:05 (15 years ago)

Author:

hmussman@bbn.com

Comment:

--

clusterdvlan

@@ -211 +211 @@
 b)  L3 service  See [[http://www.nlr.net/packetnet.php  PacketNet]]
 
+PacketNet is a barebones service providing high-speed access to other things which happen to be on PacketNet.
 Details?
 Reach?
@@ -224 +225 @@
 
 ORCA plans to provide an interface into the Sherpa GCI by 2/1/10.
+
+FrameNet/SHERPA is used to create dedicated static
+VLANs between sites with NLR access.  NLR does *not* (afaik)
+provide any sort of VLAN translation or tunnelling support, so
+you are entirely responsible for arriving at your NLR endpoint
+with your VLANs intact, as it were.  This seems likely to cause
+problems for some sites, given NLR's relatively small number of
+endpoints.  It has certainly caused some problems for us.  RENCI
+controls their access all the way to their NLR switch port, which
+gives them a lot more flexibility.  (And note that, since they
+can be flexible and do arbitrary VLAN translation on their own
+equipment, people who want to talk to them (like us), don't have
+to be as flexible.)
 
 d)  VLANs via C-Wave service?