Re: [bess] Poll to progress draft-ietf-bess-evpn-bum-procedure-updates without implementation

["Rabadan, Jorge (Nokia - US/Mountain View)" <[e-mail]>]

Dear chairs and WG,

I strongly believe we should progress draft-ietf-bess-evpn-bum-procedure-updates for the following reasons:


  *   The draft defines a number of fundamental routes that are critical for the deployment of multicast technologies in EVPN, especially the S-PMSI A-D and Leaf-AD routes.



  *   Those two routes have equivalent routes and procedures for the VPLS (RFC7117) and MVPN (RFC6513/6514) families. There are implementations for both families, draft-ietf-bess-evpn-bum-procedure-updates is just extending their use to EVPN. So the procedures should be proven, and it’s only a question of time before they get implemented and deployed.



  *   These routes are not only used in draft-ietf-bess-evpn-optimized-ir but in other WG documents.

Thank you.
Jorge


From: BESS <[e-mail]> on behalf of "[e-mail]" <[e-mail]>
Date: Tuesday, January 22, 2019 at 7:19 AM
To: LITKOWSKI Stephane OBS/OINIS <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: [bess] Poll to progress draft-ietf-bess-evpn-bum-procedure-updates without implementation

Hi,

We have now cleared the IPR poll for this draft and it is ready to progress. We do not have implementations yet (some are in roadmap).
Based on our implementation policy, we should not progress the draft. However we have “draft-ietf-bess-evpn-optimized-ir” which has a normative reference to draft-ietf-bess-evpn-bum-procedure-updates. draft-ietf-bess-evpn-optimized-ir is already submitted to IESG.

We, chairs, would like to know if the WG agrees to progress draft-ietf-bess-evpn-bum-procedure-updates without an implementation to help the publication of draft-ietf-bess-evpn-optimized-ir.

Feel free to raise any concern.

This poll runs until January 28th.

Brgds,

Stephane



From: BESS [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Tuesday, January 08, 2019 14:29
To: LITKOWSKI Stephane OBS/OINIS; [e-mail]
Subject: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates

Hi WG,

This poll is now ended but we are missing some replies for the IPR poll.
We also haven’t heard about an implementation. If there is an implementation, please let us know.

We will move forward after clearing this.

Brgds,

From: BESS [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Monday, December 17, 2018 13:50
To: [e-mail]
Subject: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates


Hello Working Group,



This email starts a three weeks Working Group Last Call on  draft-ietf-bess-evpn-bum-procedure-updates [1]. The poll period is longer than usual due to the coming vacation period.



This poll runs until *the 7th of January*.



We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors.



There is currently no IPR disclosed.



If you are not listed as an Author or a Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.



We are also polling for any existing implementation as per [2].



    Thank you,

    Stephane & Matthew



    [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-bum-procedure-updates/



    [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw


_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________



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.