On Fri, 6 Sep 2013, John MacAuley wrote:
When we moved from using the label field in the STP for specifying VLANs to the explicit VLAN element in the EVTS service element we lost the ability to specify an acceptable range of VLAN identifiers. Does anyone see an issue with this?
As we do not currently have a way to indiciate which resource are used and not (and I don't having that would be a good idea), this can make it somewhat difficult to create paths when VLANs are sparse. A somewhat related issue. We (and I assume most else) can provide a VPN service with a range of VLANs, e.g., 1000-1100 in a single VPN. And we use this towards some of our customers. I have a somewhat difficult time seeing it being used in NSI, at least for now. That doesn't mean it is not relevant. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet