Re: [mpls] MPLS-RT review of draft-raza-mpls-ldp-applicability-label-adv

I have just read the draft as well, and I echo Thomas's comment that it's well written and clear.

One thing I think it needs is some language for future LDP applications.  You define mode-based and mode-independent, and you classify existing applications into one of two buckets.  It seems like a good idea to add some text that requires any future LDP application to assign itself to one of these two categories, so that future apps clearly fit into the existing architecture.

eric

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> thomas.morin@orange.com
> Sent: Wednesday, July 11, 2012 11:47 AM
> To: draft-raza-mpls-ldp-applicability-label-adv@tools.ietf.org; mpls-
> chairs@tools.ietf.org; Martin Vigoureux
> Cc: mpls@ietf.org
> Subject: [mpls] MPLS-RT review of draft-raza-mpls-ldp-applicability-label-adv
> 
> Hi,
> 
> I have reviewed the draft and agree with others reviewers: this document
> is straightforward, useful, well written, and ready for adoption.
> 
> Simple as it is, it might even be ready for a WGLC ;-).
> 
> I have however, one comment.  It was suggested that the document should
> make it MANDATORY for future LDP application to state the applicability
> of the negotiated mode.  I wonder if a simpler solution could be
> considered: say that by default, unless a new application says that the
> negotiated mode applies, then by default it the negotiated mode would
> not apply.  This would possibly reduce the overhead for authors of
> future specs, and avoid possible confusion raising forgetting to apply
> this MUST.  Of course, this approach is only valid if we believe that
> applications that need to rely on the negotiated mode are rare and
> easily identified.
> 
> -Thomas
> 
> 
> 2012-06-20, Ross Callon :
> > You have been selected as an MPLS Review team reviewers for
> > draft-raza-mpls-ldp-applicability-label-adv.
> > Reviews should comment on whether the document is coherent, is it
> useful
> > (ie, is it likely to be actually useful in operational networks), and is
> > the document technically sound? We are interested in knowing whether
> the
> > document is ready to be considered for WG adoption (ie, it doesn’t
> > have to
> > be perfect at this point, but should be a good start).
> > Reviews should be sent to the document authors, WG co-chairs and
> > secretary,
> > and CC’d to the MPLS WG email list. If necessary, comments may be sent
> > privately to only the WG chairs.
> > Are you able to review this draft by July 11, 2012 (this is giving you an
> > extra week due to the July 4th holiday)?
> > Thanks, Ross
> > (as MPLS WG chair)
> 
> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
> message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete
> altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete
> this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for messages
> that have been modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls