The -07 rev of draft-ietf-bess-mvpn-expl-track has the following changes
from the -06 version:
1. The draft now says that it updates RFCs 6514 and 7524 as well as RFC
6625. I think this is now necessary because the draft modifies the
ingress node processing of received Leaf A-D routes that carry a PTA
with the LIR-pF flag set. I'm not sure what the objective criteria are
supposed to be for "updates", but it makes sense that anyone trying to
implement RFC 6514 or 7524 read this document as well.
2. There are a number of textual changes and clarifications in response
to comments by Stephane Litkowski.
3. The boilerplate is updated to be in accord with RFC 8174.
4. There is now a warning that the LIR-pF flag should not be set unless
it is known a priori that all nodes support it.
5. It is now REQUIRED that the LIR flag be set whenever the LIR-pF flag
is set in the PTA carried by an S-PMSI A-D route.
6. The peculiar idea of modifying the RD of a Leaf A-D route originated
in response to the LIR-pF flag has been eliminated. (Mea culpa.)
7. A Leaf A-D route originated in response to the LIR-pF flag is now
REQUIRED to carry a PTA with the LIR-pF flag set.
8. Text has been added specifying when such a PTA should specify "no
tunnel info" and when it should specify a tunnel type.
9. Text has been added to deal with the case where a wildcard S-PMSI A-D
route has (a) LIR-pF set in its PTA, and (b) also specifies a tunnel
type of Ingress Replication. The new text allows a Leaf A-D route sent
in response to the LIR-pF bit to carry a PTA specifying an MPLS label.
10. Text has been added to say that the specifications for how to use
new "tunnel types" with MVPN must specify procedures for originating
Leaf A-D routes in response to S-PMSI A-D routes whose PTAs specify the
given tunnel type and have the LIR-pF flag set. An informational
reference to the bier-mvpn draft has been added as an example.
11. A section has been added discussing how an ingress node responds to
a Leaf A-D route that carries a PTA with the LIR-pF bit set.
I hope those who are interested will review the diffs and send feedback
to the list.
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
