[Nsi-wg] NML issues
John MacAuley
jmacauley at gmail.com
Mon Sep 23 11:20:20 EDT 2013
I talked myself through this:
PortGroup == VLAN range in LabelGroup
Port == Single VLAN Label
Therefore, the ampath and nordunet topologies are generated incorrectly as they are mixing up definitions.
John
On 2013-09-23, at 11:16 AM, John MacAuley <john.macauley at surfnet.nl> wrote:
> I thought Label is a single value, so they vlan range cannot be specified in there. If it was a single port with one vlan then it might be viable, however, using a vlan range in the label file is semantically incorrect.
>
> On 2013-09-23, at 11:04 AM, Hans Trompert <hans.trompert at surfnet.nl> wrote:
>
>> The same goes for the unidirectional port declarations, some use Port and Label:
>>
>> <nml:Port id="urn:ogf:network:nordu.net:2013:netherlight-out">
>> <nml:Label labeltype="http://schemas.ogf.org/nml/2013/05/ethernet#vlan">1780-1783</nml:Label>
>> <nml:Relation type="http://schemas.ogf.org/nml/2013/05/base#isAlias">
>> <nml:Port id="urn:ogf:network:netherlight.net:2013:port:a-gole:testbed:nordu.net:1:in"/>
>> </nml:Relation>
>> </nml:Port>
>>
>> While others use PortGroup and LabelGroup:
>>
>> <nml:PortGroup id="urn:ogf:network:netherlight.net:2013:port:a-gole:testbed:nordu.net:1:out">
>> <nml:LabelGroup labeltype="http://schemas.ogf.org/nml/2012/10/ethernet#vlan">1779-1799</nml:LabelGroup>
>> <nml:Relation type="http://schemas.ogf.org/nml/2013/05/base#isAlias">
>> <nml:PortGroup id="urn:ogf:network:nordu.net:2013:netherlight-in"/>
>> </nml:Relation>
>> </nml:PortGroup>
>>
>> Can both ways be used?
>>
>> HansT.
>>
>> On 9/23/13 4:46 PM, John MacAuley wrote:
>>> Can someone explain to me which of the following two segments are correct?
>>>
>>> <nml:BidirectionalPort id="urn:ogf:network:netherlight.net:2013:port:a-gole:testbed:232">
>>> <nml:PortGroup id="urn:ogf:network:netherlight.net:2013:port:a-gole:testbed:232:in"/>
>>> <nml:PortGroup id="urn:ogf:network:netherlight.net:2013:port:a-gole:testbed:232:out"/>
>>> </nml:BidirectionalPort>
>>>
>>> or
>>>
>>> <nml:BidirectionalPort id="urn:ogf:network:ampath.net:2013:ndn">
>>> <nml:name>ndn</nml:name>
>>> <nml:Port id="urn:ogf:network:ampath.net:2013:ndn-in"/>
>>> <nml:Port id="urn:ogf:network:ampath.net:2013:ndn-out"/>
>>> </nml:BidirectionalPort>
>>>
>>> Should Port or PortGroup be used? We have a mix right now in our topologies.
>>>
>>> Thanks,
>>> John
>>>
>>>
>>> _______________________________________________
>>> nsi-wg mailing list
>>> nsi-wg at ogf.org
>>> https://www.ogf.org/mailman/listinfo/nsi-wg
>>
>> _______________________________________________
>> nsi-wg mailing list
>> nsi-wg at ogf.org
>> https://www.ogf.org/mailman/listinfo/nsi-wg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20130923/c836ab58/attachment.html>
More information about the nsi-wg
mailing list