Tom, Thanks for your comment. > > 3.4.1 says > > "The data plane behaviour of MPLS-TP is the same as the best current > practise for MPLS. This includes the setting of the S-Bit. " > > Without a reference, or any detail, I think this can only > muddy the waters. How do I know that your best practice is > my best practice, or his? This is intended to reflect the interpretation of RFC3031 that is commonly deployed. While it is technically possible to have the S-bit set more than once, this is not how it is widely done. We have used the term Best Current Practice in the same sense that it is referred to in RFC2026. draft-ietf-mpls-tp-data-plane-02.txt provides a standards track reference for this behavior. Best regards, Matthew, Stewart and Dan > > Tom Petch > > ----- Original Message ----- > From: "The IESG" <iesg-secretary@xxxxxxxx> > To: "IETF-Announce" <ietf-announce@xxxxxxxx> > Cc: <mpls@xxxxxxxx> > Sent: Wednesday, April 07, 2010 4:33 PM > Subject: [mpls] Last Call: draft-ietf-mpls-tp-framework (A > Framework forMPLS in Transport Networks) to Informational RFC > > > > The IESG has received a request from the Multiprotocol > Label Switching > > WG > > (mpls) to consider the following document: > > > > - 'A Framework for MPLS in Transport Networks ' > > <draft-ietf-mpls-tp-framework-11.txt> as an Informational RFC > > > > The IESG plans to make a decision in the next few weeks, > and solicits > > final comments on this action. Please send substantive comments to > > the ietf@xxxxxxxx mailing lists by 2010-04-21. > Exceptionally, comments > > may be sent to iesg@xxxxxxxx instead. In either case, please retain > > the beginning of the Subject line to allow automated sorting. > > > > The file can be obtained via > > > http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-framework-11.tx > > t > > > > IESG discussion can be tracked via > > > https://datatracker.ietf.org/public/pidtracker.cgi?command=vie > w_id&dTag=18027&rf > c_flag=0 > > > > _______________________________________________ > > mpls mailing list > > mpls@xxxxxxxx > > https://www.ietf.org/mailman/listinfo/mpls > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf