today's NSI conf call
The following is dial-in information for Wednesday's NSI call, time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 23:00 JST 1. Dial Toll-Free Number: 866-740-1260 (U.S. & Canada) 2. International participants dial: Toll Number: 303-248-0285 Or International Toll-Free Number: http://www.readytalk.com/intl 3. Enter 7-digit access code 8937606, followed by "#" Agenda: - Decision on STP - structured vs. opaque - If STP is to be structured rules on parsing _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________
Hi everyone, I won't be able to join the meeting today. On Wed, 4 Jun 2014, Guy Roberts wrote:
Agenda:
- Decision on STP – structured vs. opaque
Just my input on this: We changed this a lot so far... First we had the (domain,port) 2-tuple Then we realized we might need some configuration (vlan, whatever) on it, and added a third parameter). The NML came along, and we got the STP with networkId urn, and port urn, and label. But that was a bit long, so then we just had the port URN and encoding labels on it with query fragments. This no longer adheres to the URN spec, but hey. Then we figured out that no being able to seperate network and port makes path finding painful. So some of us added rules for interpreting URNs. It seems we are going in circles... My take on this, is that we need enough structure to seperate domain, port, and config from the STP.
- If STP is to be structured rules on parsing
And that this is just really small detail after we figured out the decision on top. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
participants (2)
-
Guy Roberts -
Henrik Thostrup Jensen