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 <http://www.cisco.com/global/CA/> Think before you print.This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Please click here <http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for Company Registration Information. On 2016-05-05, 1:15 PM, "BESS on behalf of Rabadan, Jorge (Nokia - US)" <bess-boun...@ietf.org on behalf of jorge.raba...@nokia.com> wrote: >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, however I have two LC comments >that are already agreed with the authors: > >1) Section 2.4 "Flexible CrossConnect" Service has to be removed from the >final text. The requirements of this special service type are not in-line >with the ones explained in section 1.2 and must be tackled separately. > > >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. > >Once both comments are addressed, the text is ready for publication. > >Thank you. >Jorge > > > > >On 5/5/16, 12:54 PM, "BESS on behalf of EXT Martin Vigoureux" ><bess-boun...@ietf.org on behalf of martin.vigour...@nokia.com> 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]. >> >>¤ Please read the document if you haven't read the most recent >>version yet, and send your comments to the list, no later than >>*20th of May*. >>Note that this is *not only* a call for comments on the document, but >>also a call for support (or not) publishing this document as a Proposed >>Standard RFC. >> >>¤ We are also polling for knowledge of any undisclosed IPR that applies >>to draft-ietf-bess-evpn-vpws-03, to ensure that IPR has been disclosed >>in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 >>for more details) prior to moving forward. >>If you are listed as a document Author or 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. >>Two IPR disclosures exist against previous revisions of this document >>[2]. >> >>¤ We are also polling for knowledge of implementations of part or all of >>what this document specifies. This information is expected as per [3]. >>Please inform the mailing list, the chairs, or only one of the chairs. >> >>¤ Finally, if someone wishes to volunteer to be Document Shepherd for >>this document, please let us know. >> >>Thank you >>M&T >> >> >>[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-vpws/ >>[2] >>https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-bess- >>evpn-vpws >>[2] >>https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw >> >>_______________________________________________ >>BESS mailing list >>BESS@ietf.org >>https://www.ietf.org/mailman/listinfo/bess >_______________________________________________ >BESS mailing list >BESS@ietf.org >https://www.ietf.org/mailman/listinfo/bess _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
