Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Sure Martin, Will do. Sami Sent from my iPhone > On Jun 1, 2016, at 12:26 AM, Martin Vigoureux > wrote: > > WG, > > we have now received an answer from all the authors and to their knowledge > there is no undisclosed IPR that relates to this draft. > > Sami, please update the draft and ma

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

WG, we have now received an answer from all the authors and to their knowledge there is no undisclosed IPR that relates to this draft. Sami, please update the draft and make sure that *all* the authors are identified on the submission page, with their latest address, before submitting the dr

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Martin, I am not aware of any relevant undisclosed IPR. Thomas -Ursprüngliche Nachricht- Von: BESS [mailto:bess-boun...@ietf.org] Im Auftrag von Martin Vigoureux Gesendet: Donnerstag, 5. Mai 2016 12:54 An: BESS Betreff: [bess] WG Last Call (including implem status & shepherd)

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

I will be updating the draft with the necessary changes. Thanks, Sami > On May 24, 2016, at 1:05 AM, Martin Vigoureux > wrote: > > WG, Authors, > > we are past the deadline for this WG LC. > I am still waiting for statements from authors. > In the meantime could you update the draft to reflec

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Martin, I’m not aware of any relevant undisclosed IPR. Thanks, Jeff On 5/5/16, 3:54 AM, "BESS on behalf of Martin Vigoureux" wrote: >Hello Working Group, > >Please read carefully, this e-mail contains new elements compared to >other WG LCs. > >This email starts a Working Group Last Call

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

WG, Authors, we are past the deadline for this WG LC. I am still waiting for statements from authors. In the meantime could you update the draft to reflect the necessary changes which were identified as part of the WG LC. In doing so, could you trim the list of authors to max 5 on the first pag

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux > Sent: Thursday, May 05, 2016 6:54 AM > To: BESS > Subject: [bess] WG Last Call (including implem status & shepherd) for > draft-ietf-bess-evpn- > vpws-03 > > Hello Working Group, > > P

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Jorge, all, While looking at pending shepherd write-ups, I noticed that draft-ietf-bess-evpn-etree is also asking for the same sub-type (0x04) [1]. Hopefully there will be a nice way to sort this out, but the lesson is that we collectively fail to get the benefits that a First Come First

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Jorge, all, Jorge: 11) IANA considerations: the authors have agreed to request the value ‘4’ for the Extended Community Sub-Type, since there are existing implementations using that value. Note that given the FCFS policy of this part of the registry [1], you could ask for this value now

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

I support WG LC for this draft as a co-author and I am not aware of any IPR that hasn’t already been disclosed. This draft is important to Service Providers who want to offer P2P services with additional feature/functionality that EVPN provides. Cisco has implemented EVPN-VPWS based on this draf

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

As co-author, I support that draft. It is solid and ready to go. Regards, Patrice Patrice Brissette TECHNICAL LEADER.ENGINEERING pbris...@cisco.com Phone: +1 613 254 3336 Cisco Systems Canada Co. / Les Systemes Cisco Canada CIE Canada Cisco.com Think bef

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Support. Regards, Nabeel > On May 5, 2016, at 6:54 AM, Martin Vigoureux > wrote: > > Hello Working Group, > > Please read carefully, this e-mail contains new elements compared to other WG > LCs. > > This email starts a Working Group Last Call on draft-ietf-bess-evpn-vpws-03 > [1]. > > ¤

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

+1 Jim Uttaro -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Rabadan, Jorge (Nokia - US) Sent: Thursday, May 05, 2016 1:16 PM To: Vigoureux, Martin (Nokia - FR) ; BESS Subject: Re: [bess] WG Last Call (including implem status & shepherd) for draft-

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

As a co-author, I fully support this document for publication as Proposed Standard RFC and I’m not aware of any undisclosed IPR related to it. It is a fundamental technology that will allow Operators to keep deploying EVPN, now also for ELINE services. The document is ready for publication, howe

[bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hello Working Group, Please read carefully, this e-mail contains new elements compared to other WG LCs. This email starts a Working Group Last Call on draft-ietf-bess-evpn-vpws-03 [1]. ¤ Please read the document if you haven't read the most recent version yet, and send your comments to the