Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
WG, we have now all the IPR answers and support for adopting the document. Authors, please republish as draft-ietf-bess-evpn-bum-procedure-updates-00 Thank you -m Le 16/08/2016 14:37, Martin Vigoureux a écrit : Hello working group, This email starts a two-week poll on adopting draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group Document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *the 30th of August*. 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 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. No IPR has been disclosed against this Document If you are not listed as an Author or Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you Martin & Thomas bess chairs [1] https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure-updates/ ___ 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Hi, I support the adoption. And I am not aware of any IRP related with the draft. -邮件原件- 发件人: BESS [mailto:bess-boun...@ietf.org] 代表 Martin Vigoureux 发送时间: 2016年10月11日 23:12 收件人: bess@ietf.org 主题: Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03 WG there is support to adopt this document in BESS. *Important note* however, please be informed that we did not get responses, to the IPR question, from two Contributors. So, before we adopt this document I'd like to give you the opportunity to reflect on that and express your opinion on the way forward for this document. target deadline: 25th of October 2016 Thank you -m Le 16/08/2016 14:37, Martin Vigoureux a écrit : > Hello working group, > > This email starts a two-week poll on adopting > draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group > Document. > > Please state on the list if you support adoption or not (in both > cases, please also state the reasons). > > This poll runs until *the 30th of August*. > > 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 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. > No IPR has been disclosed against this Document > > If you are not listed as an Author or Contributor, then please > explicitly respond only if you are aware of any IPR that has not yet > been disclosed in conformance with IETF rules. > > Thank you > > Martin & Thomas > bess chairs > > [1] > https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure- > updates/ > > > ___ > 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
WG there is support to adopt this document in BESS. *Important note* however, please be informed that we did not get responses, to the IPR question, from two Contributors. So, before we adopt this document I'd like to give you the opportunity to reflect on that and express your opinion on the way forward for this document. target deadline: 25th of October 2016 Thank you -m Le 16/08/2016 14:37, Martin Vigoureux a écrit : Hello working group, This email starts a two-week poll on adopting draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group Document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *the 30th of August*. 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 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. No IPR has been disclosed against this Document If you are not listed as an Author or Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you Martin & Thomas bess chairs [1] https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure-updates/ ___ 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Support Arkadiy Gulko -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux Sent: Tuesday, August 16, 2016 8:37 AM To: bess@ietf.org Cc: draft-zzhang-bess-evpn-bum-procedure-upda...@ietf.org Subject: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03 Hello working group, This email starts a two-week poll on adopting draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group Document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *the 30th of August*. 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 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. No IPR has been disclosed against this Document If you are not listed as an Author or Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you Martin & Thomas bess chairs [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dzzhang-2Dbess-2Devpn-2Dbum-2Dprocedure-2Dupdates_=CwICAg=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q=ehSnYXpW1Q0q-mKIFgK7W4u12zTey2bOkBFtIeYOKk4=Xiwx2KbAivF52D3S04U-Gs9g-52KWrEBFx9rfKrD0sw=pVc_nWhDZlVE7ZcTfqlWrD4M_oiwP9EvBQCnhpkLLzc= ___ BESS mailing list BESS@ietf.org https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess=CwICAg=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q=ehSnYXpW1Q0q-mKIFgK7W4u12zTey2bOkBFtIeYOKk4=Xiwx2KbAivF52D3S04U-Gs9g-52KWrEBFx9rfKrD0sw=vHCEI0SbhId50-KVxyYFR7ejuJ6mOrL460yi7GBpYWU= ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
I am not aware of any IPRs related to the draft. Apologies for the delayed response. Best Regards, Keyur > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux > Sent: Tuesday, August 16, 2016 8:37 AM > To: bess@ietf.org > Cc: draft-zzhang-bess-evpn-bum-procedure-upda...@ietf.org > Subject: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure- > updates-03 > > Hello working group, > > This email starts a two-week poll on adopting > draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group > Document. > > Please state on the list if you support adoption or not (in both cases, > please also state the reasons). > > This poll runs until *the 30th of August*. > > 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 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. > No IPR has been disclosed against this Document > > If you are not listed as an Author or Contributor, then please > explicitly respond only if you are aware of any IPR that has not yet > been disclosed in conformance with IETF rules. > > Thank you > > Martin & Thomas > bess chairs > > [1] > https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure- > updates/ > > ___ > 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Hi Arun, It's for EVPN only, but using the same concept that has been developed for L3. If we have both L2 and L3, it would be "ships in the night", and https://tools.ietf.org/html/draft-lin-bess-evpn-irb-mcast-02 is one way to optimize things. That draft talked about using MVPN when a bridge domain is not connected everywhere. Jeffrey > -Original Message- > From: Arun Prakash (arprakas) [mailto:arpra...@cisco.com] > Sent: Friday, September 02, 2016 5:17 PM > To: Jeffrey (Zhaohui) Zhang <zzh...@juniper.net>; Swadesh Agrawal > (swaagraw) <swaag...@cisco.com>; Eric Rosen <ero...@juniper.net>; Martin > Vigoureux <martin.vigour...@nokia.com>; bess@ietf.org > Cc: draft-zzhang-bess-evpn-bum-procedure-upda...@ietf.org; Nikhil Shetty > (nikshett) <niksh...@cisco.com> > Subject: Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum- > procedure-updates-03 > > Hi Jeffrey, > > Thank you for the explanation. Am not clear if this draft is only for L2 > or can it be used for L3 as well? > What if we have both L2 and L3 multicast ? > > Thanks > Arun > > On 8/28/16, 7:08 PM, "BESS on behalf of Jeffrey (Zhaohui) Zhang" > <bess-boun...@ietf.org on behalf of zzh...@juniper.net> wrote: > > >Hi Swadesh, > > > >"Enable MVPN safi and enhance it for EVPN" is not a trivial thing that > >can be cleanly done on top of MVPN. You'd end up complicating MVPN > >procedures a lot for EVPN specific things. Instead, we can apply the same > >principles to EVPN safi and procedures, and that's what this draft is > >about. > > > >BTW, we don't yet see the need of the equivalent of MVPN type-5 routes > >for EVPN. Draft-sajassi-bess-evpn-igmp-mld-proxy already proposed SMET > >route which is very similar to MVPN type-6/7 (to be exact, a combination > >of type-4/6/7). That is explained in > >draft-zzhang-bess-mvpn-evpn-cmcast-enhancements. > > > >Jeffrey > > > >> -Original Message- > >> From: Swadesh Agrawal (swaagraw) [mailto:swaag...@cisco.com] > >> Sent: Friday, August 26, 2016 3:06 AM > >> To: Eric Rosen <ero...@juniper.net>; Martin Vigoureux > >> <martin.vigour...@nokia.com>; bess@ietf.org > >> Cc: draft-zzhang-bess-evpn-bum-procedure-upda...@ietf.org > >> Subject: Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum- > >> procedure-updates-03 > >> > >> Why we need to copy MVPN procedures in EVPN. Why not enable MVPN safi > >>and > >> enhance it for any EVPN specific requiremnt. Also going in this > >>direction > >> may require to add 5,6 and 7 routes as well in future. > >> > >> Regards > >> Swadesh > >> > >> On 8/25/16, 2:22 PM, "Eric C Rosen" <ero...@juniper.net> wrote: > >> > >> >Support. > >> > > >> >MVPN has a number of multicast features that are valuable, but haven't > >> >yet been incorporated into EVPN. This draft takes a comprehensive > look > >> >at the MVPN procedures that provide those features, and shows how to > >> >adapt them to EVPN. This seems quite valuable to me, and thus I > think > >> >the WG should adopt this draft. > >> > > >> >___ > >> >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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Hi Jeffrey, Thank you for the explanation. Am not clear if this draft is only for L2 or can it be used for L3 as well? What if we have both L2 and L3 multicast ? Thanks Arun On 8/28/16, 7:08 PM, "BESS on behalf of Jeffrey (Zhaohui) Zhang" <bess-boun...@ietf.org on behalf of zzh...@juniper.net> wrote: >Hi Swadesh, > >"Enable MVPN safi and enhance it for EVPN" is not a trivial thing that >can be cleanly done on top of MVPN. You'd end up complicating MVPN >procedures a lot for EVPN specific things. Instead, we can apply the same >principles to EVPN safi and procedures, and that's what this draft is >about. > >BTW, we don't yet see the need of the equivalent of MVPN type-5 routes >for EVPN. Draft-sajassi-bess-evpn-igmp-mld-proxy already proposed SMET >route which is very similar to MVPN type-6/7 (to be exact, a combination >of type-4/6/7). That is explained in >draft-zzhang-bess-mvpn-evpn-cmcast-enhancements. > >Jeffrey > >> -Original Message- >> From: Swadesh Agrawal (swaagraw) [mailto:swaag...@cisco.com] >> Sent: Friday, August 26, 2016 3:06 AM >> To: Eric Rosen <ero...@juniper.net>; Martin Vigoureux >> <martin.vigour...@nokia.com>; bess@ietf.org >> Cc: draft-zzhang-bess-evpn-bum-procedure-upda...@ietf.org >> Subject: Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum- >> procedure-updates-03 >> >> Why we need to copy MVPN procedures in EVPN. Why not enable MVPN safi >>and >> enhance it for any EVPN specific requiremnt. Also going in this >>direction >> may require to add 5,6 and 7 routes as well in future. >> >> Regards >> Swadesh >> >> On 8/25/16, 2:22 PM, "Eric C Rosen" <ero...@juniper.net> wrote: >> >> >Support. >> > >> >MVPN has a number of multicast features that are valuable, but haven't >> >yet been incorporated into EVPN. This draft takes a comprehensive look >> >at the MVPN procedures that provide those features, and shows how to >> >adapt them to EVPN. This seems quite valuable to me, and thus I think >> >the WG should adopt this draft. >> > >> >___ >> >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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Why we need to copy MVPN procedures in EVPN. Why not enable MVPN safi and enhance it for any EVPN specific requiremnt. Also going in this direction may require to add 5,6 and 7 routes as well in future. Regards Swadesh On 8/25/16, 2:22 PM, "Eric C Rosen"wrote: >Support. > >MVPN has a number of multicast features that are valuable, but haven't >yet been incorporated into EVPN. This draft takes a comprehensive look >at the MVPN procedures that provide those features, and shows how to >adapt them to EVPN. This seems quite valuable to me, and thus I think >the WG should adopt this draft. > >___ >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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Yes/support Regards, Jeff > > On Tue, Aug 16, 2016 at 5:37 AM -0700, "Martin Vigoureux" >wrote: > >> Hello working group, >> >> This email starts a two-week poll on adopting >> draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group >> Document. >> >> Please state on the list if you support adoption or not (in both cases, >> please also state the reasons). >> >> This poll runs until *the 30th of August*. >> >> 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 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. >> No IPR has been disclosed against this Document >> >> If you are not listed as an Author or Contributor, then please >> explicitly respond only if you are aware of any IPR that has not yet >> been disclosed in conformance with IETF rules. >> >> Thank you >> >> Martin & Thomas >> bess chairs >> >> [1] >> https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure-updates/ >> >> ___ >> 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Support as well. On Tue, Aug 16, 2016 at 5:37 AM -0700, "Martin Vigoureux"wrote: Hello working group, This email starts a two-week poll on adopting draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group Document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *the 30th of August*. 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 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. No IPR has been disclosed against this Document If you are not listed as an Author or Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you Martin & Thomas bess chairs [1] https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure-updates/ ___ 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Support. MVPN has a number of multicast features that are valuable, but haven't yet been incorporated into EVPN. This draft takes a comprehensive look at the MVPN procedures that provide those features, and shows how to adapt them to EVPN. This seems quite valuable to me, and thus I think the WG should adopt this draft. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
As co-author, I support the adoption, and I am not aware of relevant IPRs. Thanks. Jeffrey > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux > Sent: Tuesday, August 16, 2016 8:37 AM > To: bess@ietf.org > Cc: draft-zzhang-bess-evpn-bum-procedure-upda...@ietf.org > Subject: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure- > updates-03 > > Hello working group, > > This email starts a two-week poll on adopting > draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group > Document. > > Please state on the list if you support adoption or not (in both cases, > please also state the reasons). > > This poll runs until *the 30th of August*. > > 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 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. > No IPR has been disclosed against this Document > > If you are not listed as an Author or Contributor, then please > explicitly respond only if you are aware of any IPR that has not yet > been disclosed in conformance with IETF rules. > > Thank you > > Martin & Thomas > bess chairs > > [1] > https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure- > updates/ > > ___ > 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Support. Thanks, Sandy "BESS"写于 2016/08/16 20:37:14: > Hello working group, > > This email starts a two-week poll on adopting > draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group > Document. > > Please state on the list if you support adoption or not (in both cases, > please also state the reasons). > > This poll runs until *the 30th of August*. > > 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 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. > No IPR has been disclosed against this Document > > If you are not listed as an Author or Contributor, then please > explicitly respond only if you are aware of any IPR that has not yet > been disclosed in conformance with IETF rules. > > Thank you > > Martin & Thomas > bess chairs > > [1] > https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure-updates/ > > ___ > 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
support Thanks Nabeel On Tue, Aug 16, 2016 at 8:37 AM, Martin Vigoureux < martin.vigour...@nokia.com> wrote: > Hello working group, > > This email starts a two-week poll on adopting > draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group > Document. > > Please state on the list if you support adoption or not (in both cases, > please also state the reasons). > > This poll runs until *the 30th of August*. > > 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 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. > No IPR has been disclosed against this Document > > If you are not listed as an Author or Contributor, then please explicitly > respond only if you are aware of any IPR that has not yet been disclosed in > conformance with IETF rules. > > Thank you > > Martin & Thomas > bess chairs > > [1] https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum- > procedure-updates/ > > ___ > 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
Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
As coauthor, I fully support this document for WG adoption. It is very much needed to keep expanding the use-cases of EVPN in Operators. I’m not aware of any relevant IPR. Thanks. Jorge On 8/16/16, 5:37 AM, "Martin Vigoureux"wrote: Hello working group, This email starts a two-week poll on adopting draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group Document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *the 30th of August*. 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 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. No IPR has been disclosed against this Document If you are not listed as an Author or Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you Martin & Thomas bess chairs [1] https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure-updates/ ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess