I was asking to determine optionality of attributes when labelSwapping="false". The default behaviour is that if there is not a SwitchingService for a specific label type then only identical labels can be connected. I think we need to extend that to the pair <encoding type, label type> must be identical otherwise an adaptation would be required to connect them. Is that a bridge too far? John On 2013-11-01, at 10:10 AM, Henrik Thostrup Jensen <htj@nordu.net> wrote:
On Fri, 1 Nov 2013, John MacAuley wrote:
Is there a valid scenario where we would define a switching service and not have a label value specified?
I assume you mean label type and not value.
label type = http://schemas.ogf.org/nml/2012/10/ethernet label value = 1780
(AFAIK)
But I guess most switching services would have a label type defined.
However I can up with a pedantic example: If you want to show, that you can NOT switch any labels an encoding, you could have a switching service that has an encoding and labelSwapping="false".
This also raises a question regarding the default behaviour in NML. Can all ports (of the same encoding) be connected by default (this is what we have now), or should there be a switching service explicitely stating which ports can be cross-connected?
Best regards, Henrik
Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg