On 3/24/2016 11:17 AM, [email protected] wrote:
I don't see why the IETF would want to create a bis which is not compatible
with the original RFC,
It's typical in a bis draft to remove features that haven't been used.
especially since this incompatibility may be very disruptive in existing
networks.
My belief is that existing deployments don't use or support the multiple
labels feature, and that any attempt to use it as specified in RFC3107
will itself be disruptive to existing networks, because it will have
interoperability issues and unpredictable results. Adding the "multiple
labels" capability is a way to make the feature deployable without
causing disruption.
"As far as I know" all the implementations claim to be compliant with RFC 3107,
i.e. are expected to be able to receive multiple labels.
I'm quite sure you have deployed implementations, from several
prominent vendors, that will not properly handle this case.
If you do have a deployed implementation that can receive multiple
labels, what would you expect it to do with those labels? RFC 3107
doesn't say anything about what to do in this case, it just provides an
encoding.
Have you ever tried to use the "multiple labels" feature?
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess
