Re: [mpls] Working Group adoption poll on draft-rosen-mpls-rfc3107bis

Hi all,

I support WG adoption: multiple aspects of RFC 3107 would benefit from clarification.

However, I note that the edition of this bis is probably driven by the advertisement of multiple MPLS labels for a prefix. But this technical point was clearly specified in RFC 3107. The problem we have is not a specification issue, but an implementation issue where some vendors shipped implementations not following RFC 3107. I'm not sure whether the problem is/was on the IETF side or on the implementations side. Have we learnt from this issue and improved for the future? If so, I'd be interested in a summary

Thanks,
--Bruno

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
> Sent: Tuesday, August 30, 2016 2:10 AM
> To: mpls@ietf.org
> Cc: draft-rosen-mpls-rfc3107bis.all@ietf.org; mpls-chairs@ietf.org
> Subject: [mpls] Working Group adoption poll on draft-rosen-mpls-rfc3107bis
> 
> Working Group,
> 
> This is to start a two week poll on adopting draft-rosen-mpls-rfc3107bis
> as an MPLS working group document.
> 
> Please send your comments (support/not support) to the mpls working
> group mailing list (mpls@ietf.org). Please give a technical
> motivation for your support/not support, especially if you think that
> the document should not be adopted as a working group document.
> 
> There are no IPR disclosures against this document.
> 
> All the authors has stated on the on the mpls wg mailing list that they
> are not aware of any IPRs that relate to this document.
> 
> The working group adoption poll ends September 14, 2016.
> 
> /Loa
> 
> MPLS wg co-chair.
> --
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

_________________________________________________________________________________________________________________________

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,
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, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.