Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Sami Boutros]

Support as a co-author, not aware of any IPR.

Thanks,

Sami
> On May 7, 2019, at 12:36 AM,  
>  wrote:
> 
> Hi,
>  
> This email begins a two-week poll for adoption of 
> draft-jain-bess-evpn-lsp-ping-08[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 won't 
> progress without answers from all 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 21th May 2019.  
>  
> Regards,
> Stephane and Matthew
>  
> [1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/ 
> 
> _
> 
> 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 adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[zhang.zheng]

Support the adoption.






Thanks,


Sandy











原始邮件



发件人：stephane.litkow...@orange.com 
收件人：bess@ietf.org ;
日 期 ：2019年05月07日 15:37
主 题 ：[bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping


___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

  

Hi,


 

This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't  progress 
without answers from all 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 21th May 2019.  


 


Regards,


Stephane and Matthew


 


[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/


_
 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

Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Reshad Rahman (rrahman)]

I support adoption of this document by the WG.

Regards,
Reshad.

From: BESS  on behalf of "stephane.litkow...@orange.com" 

Date: Tuesday, May 7, 2019 at 3:37 AM
To: "bess@ietf.org" 
Subject: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

Hi,


This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't progress 
without answers from all 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 21th May 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/

_



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

Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Ali Sajassi (sajassi)]

Support as a co-author. I am not aware of any undisclosed IPR.

Cheers,
Ali

From: BESS  on behalf of "stephane.litkow...@orange.com" 

Date: Tuesday, May 7, 2019 at 12:37 AM
To: "bess@ietf.org" 
Subject: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

Hi,


This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't progress 
without answers from all 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 21th May 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/

_



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

Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Parag Jain (paragj)]

Forgot to add that I am not aware of any IPR related to this draft.

Thanks
Parag

From: BESS  on behalf of "Parag Jain (paragj)" 

Date: Tuesday, May 7, 2019 at 9:17 AM
To: "stephane.litkow...@orange.com" , 
"bess@ietf.org" 
Subject: Re: [bess] WG adoption call & IPR poll for 
draft-jain-bess-evpn-lsp-ping

Support as coauthor of the draft.

Thanks
Parag

From: BESS  on behalf of "stephane.litkow...@orange.com" 

Date: Tuesday, May 7, 2019 at 3:37 AM
To: "bess@ietf.org" 
Subject: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

Hi,


This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't progress 
without answers from all 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 21th May 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/

_



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

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-mvpn-fast-failover

[Jeffrey (Zhaohui) Zhang]

Hi Greg,

Most of changes are fine; though I suggest to replace the following:

   For P-tunnels of type P2MP MPLS-TE, the status of the P-tunnel is
   considered up if one or more of the P2MP RSVP-TE LSPs to the same PE,
   identified by the P-tunnel Attribute, are in Up state.

With the following:

   For P-tunnels of type P2MP MPLS-TE, the status of the P-tunnel is
   considered up if the sub-LSP to this downstream PE is in Up state.

Not all comments have been addressed, though. I trimmed some text below and 
highlighted the outstanding ones with “=”. You may need to refer to 
my previous email for correlation/details.

Jeffrey

On Thu, Mar 14, 2019 at 3:04 AM Jeffrey (Zhaohui) Zhang 
mailto:zzh...@juniper.net>> wrote:
Thomas, Bob,

Some questions below for you. Some old, and some new.
 ==


Zzh> It’s not that the “rules … are not consistent”. It’s that by nature some 
PEs may think the tunnel is down while the others may think the tunnel is still 
up (because they’re on different tunnel branches), even when they follow the 
same rules. Traffic duplication in this case is also only with inclusive 
tunnels – so how about the following?

   Because all PEs may arrive at a different
   conclusion regarding the state of the tunnel,
   procedures described in Section 9.1.1 of [RFC 6513] MUST be used
   when using inclusive tunnels.
===
 Additionally, the text in section 3 seems to be more biased on Single 
Forwarder Election choosing the UMH with the highest IP address. Section 5 of 
RFC6513 also describes two other options, hashing or based on “installed UMH 
route” (aka unicast-based). It is not clear how the text in this document 
applies to hashing based selection, and I don’t see how the text applies to 
unicast-based selection. Some rewording/clarification are needed here.
GIM>> How would the use of an alternative UMH selection algorithm change 
documented use of p2mp BFD? Do you think that if the Upstream PE selected 
using, for example, hashing then defined use of BGP-BFD and p2mp BFD itself no 
longer applicable?

Zzh> It’s not that the alternative UMH selection algorithm change documented 
use of p2mp BFD. It’s the other way around – tunnel state changes the selection 
result. I guess hashing can still be used (this document only controls what 
goes into the candidate pool). For unicast based selection I thought it’d no 
longer work, but then I noticed the following:

   o  second, the UMH candidates that advertise a PMSI bound to a tunnel
  that is "down" -- these will thus be used as a last resort to
  ensure a graceful fallback to the basic MVPN UMH selection
  procedures in the hypothetical case where a false negative would
  occur when determining the status of all tunnels

Zzh> So this should still work, although Ideally, the PE advertising the next 
best route should be considered before going to the last resort (of using the 
PE advertising the best route but whose tunnel is down).

zzh> BTW, the same applies to 3.1.7 as well.
GIM>> Agree

==

3.1.7.  Per PE-CE link BFD Discriminator

   The following approach is defined for the fast failover in response
   to the detection of PE-CE link failures, in which UMH selection for a
   given C-multicast route takes into account the state of the BFD
   session associated with the state of the upstream PE-CE link.

3.1.7.1.  Upstream PE Procedures

   For each protected PE-CE link, the upstream PE initiates a multipoint
   BFD session [I-D.ietf-bfd-multipoint] as MultipointHead toward
   downstream PEs.  A downstream PE monitors the state of the p2mp
   session as MultipointTail and MAY interpret transition of the BFD
   session into Down state as the indication of the associated PE-CE
   link being down.

Since the BFD packets are sent over the P2MP tunnel not the PE-CE link, my 
understanding is that the BFD discriminator is still for the tunnel and not 
tied to the PE-CE link; but different from the previous case, the root will 
stop sending BFD messages when it detects the PE-CE link failure. As far as the 
egress PEs are concerned, they don’t know if it is the tunnel failure or PE-CE 
link failure.

If my understanding is correct, the wording should be changed.
GIM>> There are other than stopping transmission of BFD control packets ways to 
distinguish two conditions for the egress PE. For example, the MultipointHead 
MAY set the State to AdminDown and continue sending BFD control packets. If and 
when PE-CE link restored to Up, the MultipointHead can set the state to Up in 
the BFD control packet.
= this needs more discussion =
= should be clear on which way is done – stop sending BFD message or use 
AdminDown
= an PMSI may be used for many flows, which may use different PE-CE 
interfaces on the ingress PE. A downstream PE would not know which interface it 

Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Greg Mirsky]

Dear Stephane, at al.,
as the co-author, I'm not aware of any IPR related to the draft.

yes/support the adoption by the BESS WG.

Regards,
Greg

On Tue, May 7, 2019 at 12:37 AM  wrote:

> Hi,
>
>
>
> This email begins a two-week poll for adoption of 
> draft-jain-bess-evpn-lsp-ping-08[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 won't
> progress without answers from all 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 21th May 2019.
>
>
>
> Regards,
>
> Stephane and Matthew
>
>
>
> [1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/
>
> _
>
> 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 adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Parag Jain (paragj)]

Support as coauthor of the draft.

Thanks
Parag

From: BESS  on behalf of "stephane.litkow...@orange.com" 

Date: Tuesday, May 7, 2019 at 3:37 AM
To: "bess@ietf.org" 
Subject: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

Hi,


This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't progress 
without answers from all 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 21th May 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/

_



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

Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Acee Lindem (acee)]

I support WG adoption.
Thanks,
Acee

From: BESS  on behalf of Stephane Litkowski 

Date: Tuesday, May 7, 2019 at 3:37 AM
To: "bess@ietf.org" 
Subject: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

Hi,


This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't progress 
without answers from all 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 21th May 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/

_



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

Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[Mankamana Mishra (mankamis)]

Support adoption .

Sent from my iPhone

On May 7, 2019, at 02:37, 
"stephane.litkow...@orange.com" 
mailto:stephane.litkow...@orange.com>> wrote:

Hi,


This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't progress 
without answers from all 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 21th May 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/

_

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

[bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

[stephane.litkowski]

Hi,


This email begins a two-week poll for adoption of 
draft-jain-bess-evpn-lsp-ping-08[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 won't progress 
without answers from all 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 21th May 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-jain-bess-evpn-lsp-ping/

_

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