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