Re: [bess] WG adoption for draft-skr-bess-evpn-redundant-mcast-source

[Nabeel Cocker]

> Support
>

Thanks
Nabeel


>
>

>
>
>
> *From: *slitkows.i...@gmail.com 
> *Date: *Tuesday, December 1, 2020 at 10:31 AM
> *To: *bess@ietf.org ,
> draft-skr-bess-evpn-redundant-mcast-sou...@ietf.org <
> draft-skr-bess-evpn-redundant-mcast-sou...@ietf.org>
> *Subject: *WG adoption for draft-skr-bess-evpn-redundant-mcast-source
>
> Hello,
>
>
>
> This email begins a two-weeks WG adoption poll for
> draft-skr-bess-evpn-redundant-mcast-source
> 
> [1].
>
>
>
> Please review the draft and post any comments to the BESS working group
> list.
>
>
>
> 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, copying the BESS mailing list. The document will
> not  progress without answers from all of the authors and contributors.
>
>
>
> Currently, there are no IPR disclosures against this document.
>
>
>
> 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.
>
>
>
> This poll for adoption closes on 15th December 2020.
>
>
>
> Regards,
>
> Matthew and Stephane
>
>
>
> [1]
> https://datatracker.ietf.org/doc/draft-skr-bess-evpn-redundant-mcast-source/
> 
>
>
>
>
>
>
>
>
>
>
>
> Juniper Business Use Only
>
>
>
> Juniper Business Use Only
>
>
>
> Juniper Business Use Only
>
> Juniper Business Use Only
> ___
> 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] Second WG Last Call on draft-ietf-bess-vpls-multihoming-02

[Nabeel Cocker]

Support. 

Regards,
Nabeel

> On Sep 24, 2018, at 11:16 AM, Rabadan, Jorge (Nokia - US/Mountain View) 
>  wrote:
> 
> I fully support the publication of this document.
> It should have been an RFC long time back. I don’t understand why it took so 
> long.
>  
> Nokia has an implementation of this draft in SROS.
>  
> Thanks.
> Jorge
>  
> From: BESS  on behalf of "Bocci, Matthew (Nokia - GB)" 
> 
> Date: Monday, September 24, 2018 at 1:04 PM
> To: "bess@ietf.org" 
> Subject: [bess] Second WG Last Call on draft-ietf-bess-vpls-multihoming-02
>  
> All
>  
> Since we have received a recent IPR declaration on this draft and the first 
> WG last call was so long ago, we are running a second last call to reaffirm 
> WG consensus to publish the draft as an RFC.
>  
> Therefore, this email begins a two-week working group last call for 
> draft-ietf-bess-vpls-multihoming-02.txt
>  
> Please review the draft and post any comments to the BESS working group list.
>  
> Currently there is one IPR declaration against this document.
>  
> We are also polling for any existing implementations.
>  
> The working group last call closes on Monday 8th Oct 2018. 
>  
> Regards,
> Matthew and Stéphane
>  
>  
>  
> ___
> 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] WG Last Call and IPR Poll for draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

[Nabeel Cocker]

support
thanks
nabeel


On Wed, Mar 28, 2018 at 8:50 AM, Bocci, Matthew (Nokia - GB) <
matthew.bo...@nokia.com> wrote:

> This email begins a two-week working group last call for
> draft-ietf-bess-evpn-vpls-seamless-integ-01.txt
>
>
>
> Please review the draft and post any comments to the BESS working group
> list.
>
>
>
> 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, copying the BESS mailing list. The document won't
> progress without answers from all the authors and contributors.
>
> Currently there is one IPR declaration against this document.
>
> 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 implementations.
>
> The working group last call closes on Wednesday 11th April.
>
>
>
> Regards,
>
> Matthew and Stéphane
>
> ___
> 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] Call for adoption: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Feb 26, 2018, at 8:01 AM,  
>  wrote:
> 
> Hello working group,
>  
> This email starts a two-week call for adoption on
> draft-zzhang-bess-mvpn-msdp-sa-interoperation-01 [1] as a BESS Working Group 
> Document.
>  
> Please state on the list if you support the adoption or not (in both cases, 
> please also state the reasons).
>  
> This poll runs until *the 19th of March*.
>  
> 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.
>  
> Currently no IPR has been disclosed against this Document.
>  
> 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.
>  
> Thank you
>  
> (Martin), Matthew, Stéphane
> bess chairs
>  
> [1] 
> https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-msdp-sa-interoperation/
>  
> _
> 
> 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.
> ___
> 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] I-D Action: draft-ietf-bess-evpn-ac-df-03.txt

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Jan 18, 2018, at 8:47 AM, internet-dra...@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the BGP Enabled ServiceS WG of the IETF.
> 
>Title   : AC-Influenced Designated Forwarder Election for EVPN
>Authors : Jorge Rabadan
>  Kiran Nagaraj
>  Senthil Sathappan
>  Vinod Prabhu
>  Autumn Liu
>  Wen Lin
>Filename: draft-ietf-bess-evpn-ac-df-03.txt
>Pages   : 10
>Date: 2018-01-18
> 
> Abstract:
>   The Designated Forwarder (DF) in EVPN networks is the PE responsible
>   for sending multicast, broadcast and unknown unicast traffic to a
>   multi-homed CE, on a given Ethernet Tag on a particular Ethernet
>   Segment (ES). The DF is selected based on the list of PEs that
>   advertise the Ethernet Segment Identifier (ESI) to the EVPN network.
>   While PE node or link failures trigger the DF re-election for a given
>   , individual Attachment Circuit (AC) or MAC-VRF failures do
>   not trigger such DF re-election and the traffic may therefore be
>   permanently impacted, even though there is an alternative path. This
>   document improves the DF election algorithm so that the AC status can
>   influence the result of the election and this type of "logical"
>   failures can be protected too.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ac-df/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-bess-evpn-ac-df-03
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-ac-df-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-ac-df-03
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> ___
> 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] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

[Nabeel Cocker]

Support 

Regards,
Nabeel

> On Jan 29, 2018, at 3:51 AM, Rabadan, Jorge (Nokia - US/Mountain View) 
>  wrote:
> 
> Support this document, as co-author, for publication as Informational RFC.
> Not aware of any related IPR.
>  
> Nokia SROS has a full implementation of this draft.
>  
> Thank you.
> Jorge
>  
>  
> From: "stephane.litkow...@orange.com" 
> Date: Monday, January 29, 2018 at 9:27 AM
> To: "bess@ietf.org" , 
> "draft-ietf-bess-evpn-ac-df.auth...@ietf.org" 
> 
> Subject: WG Last Call (including implem status) for 
> draft-ietf-bess-evpn-ac-df 
> Resent-From: 
> Resent-To: , , 
> , , , 
> 
> Resent-Date: Monday, January 29, 2018 at 9:27 AM
>  
> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-ac-df-03 [1] which is considered mature and
> ready for a final working group review.
>
> Please read this document if you haven't read the most recent version
> yet, and send your comments to the list, no later than *12th of February*.
> Note that this is *not only* a call for comments on the document; it is
> also a call for support (or not) to publish this document as an 
> Informational
> RFC.
>
> In addition, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-ac-df, 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 a document Author or Contributor of the draft
> please respond to this email and indicate whether or not you are aware
> of any relevant IPR.
>
> Note that, as of today, no IPR has been disclosed against this document
> or its earlier versions.
>
> We are **also polling for knowledge of implementations** of part or all
> of what this document specifies. This information is expected as per [2].
> Please inform the mailing list, or the chairs, or only one of the chairs.
>
> Thank you,
> Stephane & Martin
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ac-df/
> [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.
> ___
> 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] Call for adoption: draft-lin-bess-evpn-irb-mcast

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Jan 11, 2018, at 5:11 AM, Martin Vigoureux  
> wrote:
> 
> Hello working group,
> 
> This email starts a two-week call for adoption on 
> draft-lin-bess-evpn-irb-mcast-04 [1] as a BESS Working Group Document.
> 
> Please state on the list if you support the adoption or not (in both cases, 
> please also state the reasons).
> 
> This poll runs until *the 26th 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.
> 
> Currently no IPR has been disclosed against this Document.
> 
> 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.
> 
> Thank you
> 
> Martin & Stéphane
> bess chairs
> 
> [1] https://datatracker.ietf.org/doc/draft-lin-bess-evpn-irb-mcast/
> 
> ___
> 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] Call for adoption: draft-snr-bess-evpn-na-flags

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Sep 12, 2017, at 3:35 AM, Martin Vigoureux  
> wrote:
> 
> Hello working group,
> 
> This email starts a two-week call for adoption on 
> draft-snr-bess-evpn-na-flags-07 [1] as a Working Group Document.
> 
> Please state on the list if you support the adoption or not (in both cases, 
> please also state the reasons).
> 
> This poll runs until *the 26th of September*.
> 
> 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.
> 
> Currently no IPR has been disclosed against this Document.
> 
> 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.
> 
> Thank you
> 
> Martin & Thomas
> bess chairs
> 
> [1] https://datatracker.ietf.org/doc/draft-snr-bess-evpn-na-flags/
> 
> ___
> 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] WG Last Call for draft-ietf-bess-evpn-optimized-ir

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Jun 16, 2017, at 9:43 AM,  
>  wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on 
> draft-ietf-bess-evpn-optimized-ir-01 [1] which is considered mature and ready 
> for a final working group review.
> 
> Please read this document if you haven't read the most recent version yet, 
> and send your comments to the list, no later than *30th of June*.
> Note that this is *not only* a call for comments on the document; it is also 
> a call for support (or not) to publish this document as a Standard Track RFC.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-evpn-optimized-ir, 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 a document Author or Contributor of the draft please 
> respond to this email and indicate whether or not you are aware of any 
> relevant IPR.
> 
> Note that, as of today, no IPR has been disclosed against this document or 
> its earlier versions.
> 
> We are **also polling for knowledge of implementations** of part or all of 
> what this document specifies. This information is expected as per [2].
> Please inform the mailing list, or the chairs, or only one of the chairs.
> 
> Thank you,
> T&M
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-optimized-ir/
> [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.
> 
> ___
> 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] WG Last Call for draft-ietf-bess-fat-pw-bgp

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Jun 12, 2017, at 12:27 PM, Martin Vigoureux  
> wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on draft-ietf-bess-fat-pw-bgp-02 
> [1] which is considered mature and ready for a final working group review.
> 
> ¤ Please read this document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *26th of June*.
> Note that this is *not only* a call for comments on the document; it is also 
> a call for support (or not) to publish this document as a Proposed Standard 
> RFC.
> 
> ¤ *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-fat-pw-bgp, 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 a document Author or Contributor of
> draft-ietf-bess-fat-pw-bgp-02 please respond to this email and indicate 
> whether or not you are aware of any relevant IPR.
> 
> Note that, as of today, no IPR has been disclosed against this document or 
> its earlier versions.
> 
> ¤ We are also polling for knowledge of implementations of part or all of what 
> this document specifies. This information is expected as per [2]. Please 
> inform the mailing list, or the chairs, or only one of the chairs.
> 
> 
> Thank you,
> M&T
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
> [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

Re: [bess] Call for adoption: draft-rabadan-bess-evpn-pref-df

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Jun 6, 2017, at 11:48 AM, Sathappan, Senthil (Nokia - US/Mountain View) 
>  wrote:
> 
> Support as co-author.
> Not aware of any relevant IPR related to this document.
> Thanks,
> Senthil.
> 
> -Original Message-
> From: thomas.mo...@orange.com [mailto:thomas.mo...@orange.com] 
> Sent: Tuesday, June 06, 2017 6:45 AM
> To: bess@ietf.org
> Cc: draft-rabadan-bess-evpn-pref...@ietf.org
> Subject: Call for adoption: draft-rabadan-bess-evpn-pref-df
> 
> Hello working group,
> 
> This email starts a two-week call for adoption on
> draft-rabadan-bess-evpn-pref-df-02 [1] as a Working Group Document.
> 
> Please state on the list if you support the adoption or not (in both cases, 
> please also state the reasons).
> 
> This poll runs until *the 20th of June*.
> 
> 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.
> 
> 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-rabadan-bess-evpn-pref-df/
> 
> _
> 
> 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.
> 
> ___
> 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] WG Last Call for draft-ietf-bess-evpn-usage

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Jun 6, 2017, at 10:11 AM, Martin Vigoureux  
> wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on draft-ietf-bess-evpn-usage-04 
> [1] which is considered mature and ready for a final working group review.
> 
> Please read this document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *20th of June*.
> Note that this is *not only* a call for comments on the document; it is also 
> a call for support (or not) to publish this document as an Informational RFC.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-evpn-usage, 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 a document Author or Contributor of
> draft-ietf-bess-evpn-usage-04 please respond to this email and indicate 
> whether or not you are aware of any relevant IPR.
> 
> Note that, as of today, no IPR has been disclosed against this document or 
> its earlier versions.
> 
> As opposed to the policy [2], we are not polling for knowledge of 
> implementations as it does not seem to make sense in that case. If you feel 
> otherwise, please let us know.
> 
> Thank you,
> M&T
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> [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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

[Nabeel Cocker]

Support

Regards,
Nabeel



> On Feb 13, 2017, at 5:07 PM, Martin Vigoureux  
> wrote:
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on 
> draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered 
> mature and ready for a final working group review.
> Note that this call is longer than usual because we are pushing two 
> correlated documents together.
> 
> Please read this document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *5th of March*.
> Note that this is *not only* a call for comments on the document; it is also 
> a call for support (or not) to publish this document as a Proposed Standard 
> RFC.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to draft-ietf-bess-evpn-inter-subnet-forwarding, 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 a document author or contributor of
> draft-ietf-bess-evpn-inter-subnet-forwarding-03 please respond to this email 
> and indicate whether or not you are aware of any relevant IPR.
> 
> Note that, as of today, no IPR has been disclosed against this document or 
> its earlier versions.
> 
> We are also polling for knowledge of implementations of part or all of what 
> this document specifies. This information is expected as per [2]. Please 
> inform the mailing list, or the chairs, or only one of the chairs.
> 
> Thank you,
> M&T
> 
> [1] 
> https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-inter-subnet-forwarding/
> [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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Feb 17, 2017, at 5:25 PM, Ali Sajassi (sajassi)  wrote:
> 
> Hi Jeffrey,
> 
> Thanks for your comments, please refer inline for my responses ...
> 
> On 2/17/17, 10:42 AM, "BESS on behalf of Jeffrey (Zhaohui) Zhang"
>  wrote:
> 
>> Hi,
>> 
>> I have the following nits/questions/comments. This email is only about
>> the asymmetric section  - I may send another one about symmetric section.
>> 
>> "inter-subnet switching" is confusing. Shouldn't it be "inter-subnet
>> routing" instead of "intra-subnet switching"? While it's EVPN aware, it
>> still goes through routing first.
> 
> The term ³switching² applies to both L2 and L3; whereas, the term
> ³bridging² applies to only L2 and the term ³routing² applies to only L3.
> 
>> 
>> Isn't requirement R1 covered by R2?
> 
> Yup, will remove R1.
> 
>> 
>>  This is an environment where all NVEs to which an EVPN instance could
>>  potentially be attached (or moved)
>> 
>> Strike the "(or moved)"?
> 
> OK.
> 
>> 
>>> From RFC 7432:
>> 
>> 10.1.  Default Gateway
>>  ...
>>  The IP Address field of the MAC/IP Advertisement route is set to the
>>  default gateway IP address for that subnet (e.g., an EVPN instance).
>>  For a given subnet (e.g., a VLAN or EVPN instance), the default
>>  gateway IP address is the same across all the participant PEs. The
>>  inclusion of this IP address enables the receiving PE to check its
>>  configured default gateway IP address against the one received in the
>>  MAC/IP Advertisement route for that subnet (or EVPN instance), and if
>>  there is a discrepancy, then the PE SHOULD notify the operator and
>>  log an error message.
>> 
>> This draft:
>> 
>>  2. Each NVE of a given EVPN instance uses its own default gateway IP
>>  and MAC addresses, and these addresses are aliased to the same
>>  conceptual gateway through the use of the Default Gateway extended
>>  community as specified in [EVPN], which is carried in the EVPN MAC
>>  Advertisement routes. On each NVE, this default gateway IP/MAC
>>  address correspond to the IRB interface connecting the MAC-VRF of
>>  that EVI to the corresponding IP-VRF.
>> 
>> The above 2nd model seems to be conflicting with RFC 7432?
> 
> 
> Thanks for catching it. The 2nd case is supposed to be ³the same IP
> anycast address but different MAC addresses" - ie, the two use cases in
> this draft correspond to the two uses cases in section 10.1 of RFC 7432.
> So, the new text reads as follow:
> 
> ³2. Each NVE of a given EVPN instance uses the same anycast default
> gateway IP address but its own MAC address. These MAC addresses are
> aliased to the same anycast default gateway IP address through the use of
> the Default Gateway extended community as specified in [EVPN], which is
> carried in the EVPN MAC/IP Advertisement routes. On each NVE, this default
> gateway IP address along with its associated MAC addresses correspond to
> the IRB interface connecting the MAC-VRF of that EVI to the corresponding
> IP-VRF.²
> 
> 
>> Also, what does "this default gateway" refer to? Each NVE's "own default
>> gateway" or "the same conceptual gateway"?
> 
> Default gateway with respect to TS¹s as mentioned in the 2nd para of
> section 3.1
> 
> 
>> Is it that besides their own default gateway, an additional common
>> gateway is advertised using that extended community? If so, what's the
>> purpose to call those different IP addresses on the IRB interfaces
>> "default gateway"? I assume the hosts will be using the common gateway
>> address?
> 
> This comment should be already addressed by above clarification.
> 
>> 
>>  It is worth noting that if the applications that are running on the
>>  TS's are employing or relying on any form of MAC security, then the
>>  first model (i.e. using anycast addresses) would be required to
>>  ensure that the applications receive traffic from the same source MAC
>>  address that they are sending to.
>> 
>> Why is that? As long as an NVE changes the source MAC to the one it sends
>> in the ARP reply, it should work even with the 2nd model?
> 
> If it changes, yes but if it doesn¹t change it, it creates issue for MAC
> security. Modified the paragraph to provide further clarification:
> 
> "It is worth noting that if the applications that are running on the TS's
> are employing or relying on any form of MAC security, then either the
> first model (i.e. using anycast MAC address) should be used to ensure that
> the applications receive traffic from the same IRB interface MAC address
> that they are sending to, or if the second model is used, then the IRB
> interface MAC address MUST be the one used in the initial ARP reply for
> that TS."
> 
> 
>> 
>> 3.2 Heterogeneous Environment
>> 
>>  .. Even though policies
>>  among multiple subnets belonging to same tenant can be simpler,
>> 
>> s/simpler/simple/?
> 
> Done.
> 
>> 
>>  ... Therefore, there can be a mixed environment where an NVE
>>  performs inter-subnet switching for some EVPN instances and the L3GW
>> 

Re: [bess] WG Last Call for draft-ietf-bess-dci-evpn-overlay-04

[Nabeel Cocker]

support

thanks
nabeel


On Mon, Feb 6, 2017 at 8:07 AM, Martin Vigoureux  wrote:

> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-dci-evpn-overlay-04 [1] which is considered mature and
> ready for a final working group review.
>
> Please read the document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *19th of February*.
> Note that this is *not only* a call for comments on the document; it is
> also a call for support (or not) to publish this document as a Proposed
> Standard RFC.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-dci-evpn-overlay, 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 a document author or contributor of
> draft-ietf-bess-dci-evpn-overlay-04 please respond to this email and
> indicate whether or not you are aware of any relevant IPR.
>
> Note that IPR exists and has been disclosed against this document [2].
>
> Thank you,
> M&T
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-dci-evpn-overlay/
> [2] https://datatracker.ietf.org/ipr/search/?submit=draft&id=dra
> ft-ietf-bess-dci-evpn-overlay
>
> ___
> 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-rabadan-bess-evpn-ac-df

[Nabeel Cocker]

support

thanks
Nabeel

On Tue, Aug 30, 2016 at 4:45 AM, Thomas Morin 
wrote:

> Hello working group,
>
> This email starts a two-week poll on adopting
> draft-rabadan-bess-evpn-ac-df-05 [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 *September 14th*.
>
> 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.
>
> At this date, 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-rabadan-bess-evpn-ac-df
>
> ___
> 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

[Nabeel Cocker]

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] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

[Nabeel Cocker]

Support. 

Regards,
Nabeel

> On Jun 13, 2016, at 8:25 AM,  
>  wrote:
> 
> Hello Working Group,
> 
> (Please read carefully, this e-mail contains new elements compared to WG LCs 
> we were doing in a still recent past.)
> 
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-overlay [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
> *27th of June*.
> 
> 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-overlay-04, 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.
> 
> * We are also polling for knowledge of implementations of part or all of what 
> this document specifies. This information is expected as per [2]. Please 
> inform the mailing list, the chairs, or only one of the chairs.
> 
> * Finally, if you want to volunteer to be Document Shepherd for this 
> document, please let us know.
> 
> Thank you,
> 
> Thomas/Martin
> 
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-overlay
> [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.
> 
> ___
> 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] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

[Nabeel Cocker]

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].
> 
> ¤ 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

Re: [bess] Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02

[Nabeel Cocker]

I support this draft.

thanks,
Nabeel


On Fri, Feb 5, 2016 at 11:56 AM,  wrote:

> Hello working group,
>
> This email starts a two-week poll on adopting
> draft-snr-bess-evpn-proxy-arp-nd [1] as a working group item.
>
> Please send comments to the list and state if you support adoption or not
> (in the later case, please also state the reasons).
>
> This poll runs until **February 19th**.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to this draft, 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 a document author or contributor please respond
> to this email and indicate whether or not you are aware of any relevant IPR.
>
> The draft will not be adopted until a response has been received from each
> author and contributor.
>
> 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://tools.ietf.org/html/draft-snr-bess-evpn-proxy-arp-nd-02
>
> _
>
> 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.
>
>
> ___
> 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] Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02

[Nabeel Cocker]

Support

Regards,
Nabeel

> On Feb 5, 2016, at 11:56 AM,  
>  wrote:
> 
> Hello working group,
> 
> This email starts a two-week poll on adopting 
> draft-snr-bess-evpn-proxy-arp-nd [1] as a working group item.
> 
> Please send comments to the list and state if you support adoption or not (in 
> the later case, please also state the reasons).
> 
> This poll runs until **February 19th**.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to this draft, 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 a document author or contributor please respond to 
> this email and indicate whether or not you are aware of any relevant IPR.
> 
> The draft will not be adopted until a response has been received from each 
> author and contributor.
> 
> 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://tools.ietf.org/html/draft-snr-bess-evpn-proxy-arp-nd-02
> 
> _
> 
> 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.
> ___
> 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-rabadan-bess-evpn-optimized-ir-02

[Nabeel Cocker]

I support this draft. 

Regards,
Nabeel

> On Jan 26, 2016, at 3:12 AM, Thomas Morin  wrote:
> 
> Hello working group,
> 
> This email starts a two-week poll on adopting
> draft-rabadan-bess-evpn-optimized-ir-02 [1] as a working group item.
> 
> Please send comments to the list and state if you support adoption or
> not (in the later case, please also state the reasons).
> 
> This poll runs until **February 9th**.
> 
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to this draft, 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 a document author or contributor please
> respond to this email and indicate whether or not you are aware of any 
> relevant IPR.
> 
> The draft will not be adopted until a response has been received from
> each author and contributor.
> 
> 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://tools.ietf.org/html/draft-rabadan-bess-evpn-optimized-ir-02
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> 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] Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02

[Nabeel Cocker]

I Support this draft. 

Regards,
Nabeel

> On Feb 5, 2016, at 11:56 AM,  
>  wrote:
> 
> Hello working group,
> 
> This email starts a two-week poll on adopting 
> draft-snr-bess-evpn-proxy-arp-nd [1] as a working group item.
> 
> Please send comments to the list and state if you support adoption or not (in 
> the later case, please also state the reasons).
> 
> This poll runs until **February 19th**.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies 
> to this draft, 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 a document author or contributor please respond to 
> this email and indicate whether or not you are aware of any relevant IPR.
> 
> The draft will not be adopted until a response has been received from each 
> author and contributor.
> 
> 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://tools.ietf.org/html/draft-snr-bess-evpn-proxy-arp-nd-02
> 
> _
> 
> 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.
> ___
> 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-morin-bess-mvpn-fast-failover

[Nabeel Cocker]

support..

Nabeel

On Fri, Oct 2, 2015 at 6:29 AM, Martin Vigoureux <
martin.vigour...@alcatel-lucent.com> wrote:

> Hello working group,
>
> This email starts a two-week poll on adopting
> draft-morin-bess-mvpn-fast-failover [1] as a working group item.
>
> Please send comments to the list and state if you support adoption or
> not (in the later case, please also state the reasons).
>
> This poll runs until the *16th of October*.
>
> Currently there is no IPR disclosed against this document.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to this draft, 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 a document author or contributor* please respond to
> this email and indicate whether or not you are aware of any relevant IPR.
>
> The draft will not be adopted until a response has been received from each
> author and contributor.
>
> 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://tools.ietf.org/html/draft-morin-bess-mvpn-fast-failover
>
> ___
> 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-keyupate-l2vpn-fat-pw-bgp

[Nabeel Cocker]

support.

Nabeel Cocker

On Fri, Jun 12, 2015 at 12:27 PM, Rabadan, Jorge (Jorge) <
jorge.raba...@alcatel-lucent.com> wrote:

> I support this document for WG adoption as co-author.
> Not aware of any related IPR.
>
> Thanks.
> Jorge
>
> -Original Message-
> From: Martin Vigoureux 
> Date: Friday, June 12, 2015 at 8:58 AM
> To: "bess@ietf.org" 
> Subject: [bess] Poll for adoption: draft-keyupate-l2vpn-fat-pw-bgp
>
> >Hello working group,
> >
> >This email starts a two-week poll on adopting
> >draft-keyupate-l2vpn-fat-pw-bgp [1] as a working group item.
> >
> >Please send comments to the list and state if you support adoption or
> >not (in the later case, please also state the reasons).
> >
> >This poll runs until **June the 26th**.
> >
> >
> >*Coincidentally*, we are also polling for knowledge of any IPR that
> >applies to this draft, 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 a document author or contributor* please respond
> >to this email and indicate whether or not you are aware of any relevant
> >IPR.
> >
> >The draft will not be adopted until a response has been received from
> >each author and contributor.
> >
> >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://tools.ietf.org/html/draft-keyupate-l2vpn-fat-pw-bgp
> >
> >___
> >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-sajassi-bess-evpn-vpls-seamless-integ

[Nabeel Cocker]

support!

thanks,
Nabeel Cocker


On Mon, Jan 26, 2015 at 4:46 AM, Martin Vigoureux <
martin.vigour...@alcatel-lucent.com> wrote:

> Hello working group,
>
> This email starts a two-week poll on adopting
> draft-sajassi-bess-evpn-vpls-seamless-integ [1] as a working group item.
>
> Please send comments to the list and state if you support adoption or
> not (in the later case, please also state the reasons).
>
> This poll runs until **February 9th**.
>
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to this draft, 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 a document author or contributor* please
> respond to this email and indicate whether or not you are aware of any
> relevant IPR.
>
> The draft will not be adopted until a response has been received from
> each author and contributor.
>
> 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.
>
> Note that an IPR disclosure [2] exists for this document.
>
> Thank you,
>
> Martin & Thomas
> bess chairs
>
> [1] https://tools.ietf.org/html/draft-sajassi-bess-evpn-vpls-
> seamless-integ
> [2] https://datatracker.ietf.org/ipr/2472/
>
> ___
> 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-morin-bess-multicast-damping

[Nabeel Cocker]

Support!
Nabeel Cocker

On Mon, Jan 26, 2015 at 4:47 AM, Martin Vigoureux <
martin.vigour...@alcatel-lucent.com> wrote:

> Hello working group,
>
> This email starts a two-week poll on adopting
> draft-morin-bess-multicast-damping [1] as a working group item.
>
> Please send comments to the list and state if you support adoption or
> not (in the later case, please also state the reasons).
>
> This poll runs until **February 9th**.
>
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to this draft, 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 a document author or contributor* please
> respond to this email and indicate whether or not you are aware of any
> relevant IPR.
>
> The draft will not be adopted until a response has been received from
> each author and contributor.
>
> 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://tools.ietf.org/html/draft-morin-bess-multicast-damping
>
> ___
> 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-rabadan-bess-dci-evpn-overlay

[Nabeel Cocker]

Support...

Nabeel Cocker

On Tue, Dec 16, 2014 at 11:00 PM, Haoweiguo  wrote:
>
> This draft provides VLAN-based hand-off (option-A) and PW-based
> hand-off(similar to option-B,but MAC VRFs are created on DC GW)
> interconnection solution between NVO3 and MPLS L2VPN network(VPLS,EVPN,and
> etc). It is very beneficial and helpful for NVO3 DCI. So I support this
> adoption, i'm also not aware of IPR.
>
> BTW:In draft-hao-l2vpn-inter-nvo3-evpn-00, vanilla option-B solution is
> provided for NVO3 and MPLS EVPN network interconnection. In this solution,
> MAC VRFs is not required on DC GW, only MPLS VPN Label and VNID switching
> is needed,it's another different and helpful solution.
> Thanks,
> weiguo
> 
> From: BESS [bess-boun...@ietf.org] on behalf of Dennis Cai (dcai) [
> d...@cisco.com]
> Sent: Saturday, December 13, 2014 0:48
> To: Anil Lohiya; EXT - thomas.mo...@orange.com; bess@ietf.org
> Cc: draft-rabadan-bess-dci-evpn-over...@tools.ietf.org
> Subject: Re: [bess] Poll for adoption: draft-rabadan-bess-dci-evpn-overlay
>
> Btw, I'm not aware of IPR.
>
> -Original Message-
> From: Dennis Cai (dcai)
> Sent: Thursday, December 11, 2014 8:02 PM
> To: Anil Lohiya; EXT - thomas.mo...@orange.com; bess@ietf.org
> Cc: draft-rabadan-bess-dci-evpn-over...@tools.ietf.org
> Subject: RE: [bess] Poll for adoption: draft-rabadan-bess-dci-evpn-overlay
>
> Support as co-author !
>
> -Original Message-
> From: Anil Lohiya [mailto:aloh...@juniper.net]
> Sent: Monday, December 08, 2014 2:27 PM
> To: EXT - thomas.mo...@orange.com; bess@ietf.org
> Cc: draft-rabadan-bess-dci-evpn-over...@tools.ietf.org
> Subject: Re: [bess] Poll for adoption: draft-rabadan-bess-dci-evpn-overlay
>
>
> support as a co-author. I am not aware of any IPR.
>
> - Anil
>
> -Original Message-
> From: Thomas Morin 
> Organization: Orange
> Date: Friday, December 5, 2014 5:13 AM
> To: "bess@ietf.org" 
> Cc: "draft-rabadan-bess-dci-evpn-over...@tools.ietf.org"
> 
> Subject: [bess]  Poll for adoption: draft-rabadan-bess-dci-evpn-overlay
>
> >Hello working group,
> >
> >This email starts a two-week poll on adopting
> >draft-rabadan-bess-dci-evpn-overlay [1] as a working group item.
> >
> >Please send comments to the list and state if you support adoption or
> >not (in the later case, please also state the reasons).
> >
> >This poll runs until **December 19th**.
> >
> >
> >*Coincidentally*, we are also polling for knowledge of any IPR that
> >applies to this draft, 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 a document author or contributor* please
> >respond to this email and indicate whether or not you are aware of any
> >relevant IPR.
> >
> >The draft will not be adopted until a response has been received from
> >each author and contributor.
> >
> >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://tools.ietf.org/html/draft-rabadan-bess-dci-evpn-overlay
> >
> >___
> >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
>
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess