[Nsi-wg] nordunet and am path VLAN issue

[John MacAuley]

I do gracefully handle your naughty label, but you end up becoming an island since you do not connect to anyone.  Not very fun for path finding.

Thank you,
John

Thumb typed on my iPad.

> On Sep 27, 2013, at 6:29 AM, Henrik Thostrup Jensen <htj at nordu.net> wrote:
> 
>> On Wed, 25 Sep 2013, John MacAuley wrote:
>> 
>> I just downloaded updated topologies from some of the OpenNSA sources and noticed you are still using http://schemas.ogf.org/nml/2013/05/ethernet#vlan instead of http://schemas.ogf.org/nml/2012/10/ethernet#vlan.
> 
> Been down sick. Also you didn't answer my question :-)
> 
> I'll use the old one. However there will probably be some labels out in the world that you won't understand, so your topology module should really be able to deal with this (sure pathfinding won't include the networks).
> 
>> Also, port urn:ogf:network:nordu.net:2013:ampath-in indicates connectivity to urn:ogf:network:ampath.net:2013:ndn-out but this port saying it is connected to urn:ogf:network:nordu.net:2013:aruba-in. Looks like the aruba-in/out within the am path topology needs to point to ampath-in/ampath-out.
> 
> I'll talk to Jeronimo and get this fixed.
> 
> 
>    Best regards, Henrik
> 
> Henrik Thostrup Jensen <htj at nordu.net>
> Software Developer, NORDUnet
> 
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg