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 draft and it has been available since H2/2015.
There are a few nits that need to be taken care before RFC publication and they can be done as part of WG LC comment resolutions: 1) There has been an agreement among the co-authors to move section 2.4 to another draft which is at works and covers the topic of Flexible Cross Connect comprehensively. 2) Section 10 should be expanded to describe why there are no additional security requirements. 3) Section 11 should be expanded to list the IANA allocation for the EC defined in section 3.1. Regards, Ali On 5/5/16, 3:54 AM, "BESS on behalf of Vigoureux, Martin (Nokia - FR)" <[email protected] on behalf of [email protected]> 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-e >vpn-vpws >[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > >_______________________________________________ >BESS mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/bess _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
