Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Ali Sajassi (sajassi)]

Hi Matthew,

Done and it is waiting for your check-in.

Cheers,
Ali

From: Matthew Bocci (Nokia) 
Date: Tuesday, June 20, 2023 at 2:24 AM
To: Ali Sajassi (sajassi) , Linda Dunbar 
, Lukas Krattiger (lkrattig) 
, bess-cha...@ietf.org 

Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org 

Subject: Re: [bess] WG Adoption and IPR poll for 
draft-sajassi-bess-secure-evpn-06
This email closes the WG adoption poll.

Authors: Please make the updates as agreed below and post a new WG version of 
the document:  draft-ietf-bess-secure-evpn-00.

Regards

Matthew


From: Ali Sajassi (sajassi) 
Date: Monday, 12 June 2023 at 07:17
To: Linda Dunbar , Lukas Krattiger (lkrattig) 
, Matthew Bocci (Nokia) 
, bess-cha...@ietf.org 
Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org 

Subject: Re: [bess] WG Adoption and IPR poll for 
draft-sajassi-bess-secure-evpn-06

CAUTION: This is an external email. Please be very careful when clicking links 
or opening attachments. See the URL nok.it/ext for additional information.


Linda,

Thanks for your comments. Please refer to my replies inline …

From: Linda Dunbar 
Date: Tuesday, May 30, 2023 at 9:36 AM
To: Lukas Krattiger (lkrattig) , Matthew 
Bocci (Nokia) , bess-cha...@ietf.org 

Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org 

Subject: RE: [bess] WG Adoption and IPR poll for 
draft-sajassi-bess-secure-evpn-06
I support the WG adoption with the following questions and comments:


  *   Section 5: How is the IPsec Databases (SPD, SAD, and generating Keying 
material for IPsec SAs) different from the traditional IPsec Data Base 
generation described in the RFC 4301? Can you please emphasize the differences?
IKE is P2P; whereas, key generation and re-keying describes is this document is 
adapted for P2MP BGP signaling. We will emphasize the differences in future 
revision.

  *   Section 8 Second paragraph states that the Device-Controller trust model 
is using the peer-to-peer protocol such as IKEv2. If the devices are already 
support EVPN, are they already have trust connection to their corresponding 
controller? Can TLS be used for Devices to exchange BGP messages with the 
controller?
Absolutely. TLS can also be used for devices-controller trust model for 
securing the exchange of BGP messages. I will mention that in the next rev.

  *   -  If a SA is required per pair of IP addresses on two separate PEs, why 
it is not enough to have the existing ESP tunnel mode encapsulation for the 
packet exchanged between the two PEs like the following?

Outer IP header:
+---+
|protocol = 50(IPsec ESP)   |
|src = source-PE   |
|dst = dest-PE  |
+---+  < --+
 |SPI(Security Parameter Idx)|Authenticated
+---+  |
|sequence number|  |
+---+   <-+|
| payload IP header:| ||
|  src =  source-ip | ||
|  dst =  dest-ip  | ||
+---+  Encrypted   |
|   TCP header +| ||
~payload (variable) ~ ||
|   | ||
+===+   <-+ ---+
|   Authentication Data |
+---+


Is it necessary to have any outer tunnel header (other than the IPsec's ESP 
encapsulation) wrapping around the payload?

Ali> I am guessing you are referring to figure 10, “per IP address”. If so, 
this is overlay IP address and thus they are defined in context of a VNI which 
means we need VxLAN header. Also, for encap consistency, across different level 
of granularity, we are keeping VxLAN header. The encap is not cast in stone and 
if we can improve efficiency without complicating data-plane processing, then 
we should discuss the options.

Cheers,
Ali

  *

Thank you very much

Linda


> On May 25, 2023, at 5:35 AM, Matthew Bocci (Nokia) 
> mailto:matthew.bo...@nokia.com>> wrote:
>
> Hello,
>  This email begins a two-week WG adoption poll for 
> draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
> Currently, there is currently no IPR disclosure against this document.
> If you are not listed as an author or a contributor, then please explicitly 
> respond only if you a

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Matthew Bocci (Nokia)]

This email closes the WG adoption poll.

Authors: Please make the updates as agreed below and post a new WG version of 
the document:  draft-ietf-bess-secure-evpn-00.

Regards

Matthew


From: Ali Sajassi (sajassi) 
Date: Monday, 12 June 2023 at 07:17
To: Linda Dunbar , Lukas Krattiger (lkrattig) 
, Matthew Bocci (Nokia) 
, bess-cha...@ietf.org 
Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org 

Subject: Re: [bess] WG Adoption and IPR poll for 
draft-sajassi-bess-secure-evpn-06

CAUTION: This is an external email. Please be very careful when clicking links 
or opening attachments. See the URL nok.it/ext for additional information.


Linda,

Thanks for your comments. Please refer to my replies inline …

From: Linda Dunbar 
Date: Tuesday, May 30, 2023 at 9:36 AM
To: Lukas Krattiger (lkrattig) , Matthew 
Bocci (Nokia) , bess-cha...@ietf.org 

Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org 

Subject: RE: [bess] WG Adoption and IPR poll for 
draft-sajassi-bess-secure-evpn-06
I support the WG adoption with the following questions and comments:


  *   Section 5: How is the IPsec Databases (SPD, SAD, and generating Keying 
material for IPsec SAs) different from the traditional IPsec Data Base 
generation described in the RFC 4301? Can you please emphasize the differences?
IKE is P2P; whereas, key generation and re-keying describes is this document is 
adapted for P2MP BGP signaling. We will emphasize the differences in future 
revision.

  *   Section 8 Second paragraph states that the Device-Controller trust model 
is using the peer-to-peer protocol such as IKEv2. If the devices are already 
support EVPN, are they already have trust connection to their corresponding 
controller? Can TLS be used for Devices to exchange BGP messages with the 
controller?
Absolutely. TLS can also be used for devices-controller trust model for 
securing the exchange of BGP messages. I will mention that in the next rev.

  *   -  If a SA is required per pair of IP addresses on two separate PEs, why 
it is not enough to have the existing ESP tunnel mode encapsulation for the 
packet exchanged between the two PEs like the following?

Outer IP header:
+---+
|protocol = 50(IPsec ESP)   |
|src = source-PE   |
|dst = dest-PE  |
+---+  < --+
 |SPI(Security Parameter Idx)|Authenticated
+---+  |
|sequence number|  |
+---+   <-+|
| payload IP header:| ||
|  src =  source-ip | ||
|  dst =  dest-ip  | ||
+---+  Encrypted   |
|   TCP header +| ||
~payload (variable) ~ ||
|   | ||
+===+   <-+ ---+
|   Authentication Data |
+---+


Is it necessary to have any outer tunnel header (other than the IPsec's ESP 
encapsulation) wrapping around the payload?

Ali> I am guessing you are referring to figure 10, “per IP address”. If so, 
this is overlay IP address and thus they are defined in context of a VNI which 
means we need VxLAN header. Also, for encap consistency, across different level 
of granularity, we are keeping VxLAN header. The encap is not cast in stone and 
if we can improve efficiency without complicating data-plane processing, then 
we should discuss the options.

Cheers,
Ali

  *

Thank you very much

Linda


> On May 25, 2023, at 5:35 AM, Matthew Bocci (Nokia) 
> mailto:matthew.bo...@nokia.com>> wrote:
>
> Hello,
>  This email begins a two-week WG adoption poll for 
> draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
> Currently, there is currently no IPR disclosure 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 June 9th 2023  Regards, Matthew and
> Stephane  [1]
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata<https://data/>
> tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-sajassi-bess-secure-evpn=05
> %7C01%7Clinda.dunbar%40f

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Ali Sajassi (sajassi)]

Linda,

Thanks for your comments. Please refer to my replies inline …

From: Linda Dunbar 
Date: Tuesday, May 30, 2023 at 9:36 AM
To: Lukas Krattiger (lkrattig) , Matthew 
Bocci (Nokia) , bess-cha...@ietf.org 

Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org 

Subject: RE: [bess] WG Adoption and IPR poll for 
draft-sajassi-bess-secure-evpn-06
I support the WG adoption with the following questions and comments:


  *   Section 5: How is the IPsec Databases (SPD, SAD, and generating Keying 
material for IPsec SAs) different from the traditional IPsec Data Base 
generation described in the RFC 4301? Can you please emphasize the differences?
IKE is P2P; whereas, key generation and re-keying describes is this document is 
adapted for P2MP BGP signaling. We will emphasize the differences in future 
revision.

  *   Section 8 Second paragraph states that the Device-Controller trust model 
is using the peer-to-peer protocol such as IKEv2. If the devices are already 
support EVPN, are they already have trust connection to their corresponding 
controller? Can TLS be used for Devices to exchange BGP messages with the 
controller?
Absolutely. TLS can also be used for devices-controller trust model for 
securing the exchange of BGP messages. I will mention that in the next rev.

  *   -  If a SA is required per pair of IP addresses on two separate PEs, why 
it is not enough to have the existing ESP tunnel mode encapsulation for the 
packet exchanged between the two PEs like the following?

Outer IP header:
+---+
|protocol = 50(IPsec ESP)   |
|src = source-PE   |
|dst = dest-PE  |
+---+  < --+
 |SPI(Security Parameter Idx)|Authenticated
+---+  |
|sequence number|  |
+---+   <-+|
| payload IP header:| ||
|  src =  source-ip | ||
|  dst =  dest-ip  | ||
+---+  Encrypted   |
|   TCP header +| ||
~payload (variable) ~ ||
|   | ||
+===+   <-+ ---+
|   Authentication Data |
+---+


Is it necessary to have any outer tunnel header (other than the IPsec's ESP 
encapsulation) wrapping around the payload?

Ali> I am guessing you are referring to figure 10, “per IP address”. If so, 
this is overlay IP address and thus they are defined in context of a VNI which 
means we need VxLAN header. Also, for encap consistency, across different level 
of granularity, we are keeping VxLAN header. The encap is not cast in stone and 
if we can improve efficiency without complicating data-plane processing, then 
we should discuss the options.

Cheers,
Ali

  *

Thank you very much

Linda


> On May 25, 2023, at 5:35 AM, Matthew Bocci (Nokia) 
> mailto:matthew.bo...@nokia.com>> wrote:
>
> Hello,
>  This email begins a two-week WG adoption poll for 
> draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
> Currently, there is currently no IPR disclosure 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 June 9th 2023  Regards, Matthew and
> Stephane  [1]
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata<https://data/>
> tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-sajassi-bess-secure-evpn=05
> %7C01%7Clinda.dunbar%40futurewei.com%7Cad6059875d30470c56a908db6117f33
> d%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638210527722676515%7CUn
> known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW
> wiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=DwjLIezroZxS%2Fw8vyDe6ypUP3RSGq
> hqOLuLcvsMAkho%3D=0
> ___
> BESS mailing list
> BESS@ietf.org<mailto:BESS@ietf.org>
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww<https://www/>.
> ietf.org%2Fmailman%2Flistinfo%2Fbess=05%7C01%7Clinda.dunbar%40fut
> urewei.com%7Cad6059875d30470c56a908db6117f33d%7C0fee8ff2a3b240189c75

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Linda Dunbar]

Can the authors address my comments for the WG Adoption posted on May 30?

Attached for the convenience.

Thank you,

Linda

From: BESS  On Behalf Of Matthew Bocci (Nokia)
Sent: Friday, June 9, 2023 9:31 AM
To: bess@ietf.org
Cc: draft-sajassi-bess-secure-e...@ietf.org; bess-cha...@ietf.org
Subject: Re: [bess] WG Adoption and IPR poll for 
draft-sajassi-bess-secure-evpn-06

WG

I think there is consensus to adopt the draft from a technical point of view. 
However, the IPR disclosure was only posted on 8th June, so I will give the 
working group another week to consider this and then, if there are no 
objections, close the adoption poll on Friday 16th June 2023.

Regards

Matthew

From: Matthew Bocci (Nokia) 
mailto:matthew.bo...@nokia.com>>
Date: Thursday, 25 May 2023 at 11:35
To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>
Cc: 
draft-sajassi-bess-secure-e...@ietf.org<mailto:draft-sajassi-bess-secure-e...@ietf.org>
 
mailto:draft-sajassi-bess-secure-e...@ietf.org>>,
 bess-cha...@ietf.org<mailto:bess-cha...@ietf.org> 
mailto:bess-cha...@ietf.org>>
Subject: WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

--- Begin Message ---
I support the WG adoption with the following questions and comments:

-   Section 5: How is the IPsec Databases (SPD, SAD, and generating Keying 
material for IPsec SAs)  different from the traditional IPsec Data Base 
generation described in the RFC 4301? Can you please emphasize the differences?
-   Section 8 Second paragraph states that the Device-Controller trust 
model is using the peer-to-peer protocol such as IKEv2. If the devices are 
already support EVPN, are they already have trust connection to their 
corresponding controller? Can TLS be used for Devices to exchange BGP messages 
with the controller?
-   -  If a SA is required per pair of IP addresses on two separate PEs, 
why it is not enough to have the existing ESP tunnel mode encapsulation for the 
packet exchanged between the two PEs like the following?

  Outer IP header:
  +---+
  |protocol = 50(IPsec ESP)   |
  |src = source-PE|
  |dst = dest-PE  |
  +---+  < --+
  |SPI(Security Parameter Idx)|Authenticated
  +---+  |
  |sequence number|  |
  +---+   <-+|
  | payload IP header:| ||
  |  src =  source-ip | ||
  |  dst =  dest-ip   | ||
  +---+  Encrypted   |
  |   TCP header +| ||
  ~payload (variable) ~ ||
  |   | ||
  +===+   <-+ ---+
  |   Authentication Data |
  +---+


 Is it necessary to have any outer tunnel header (other than the IPsec's ESP 
encapsulation) wrapping around the payload?

-

Thank you very much

Linda


> On May 25, 2023, at 5:35 AM, Matthew Bocci (Nokia) 
> mailto:matthew.bo...@nokia.com>> wrote:
>
> Hello,
>  This email begins a two-week WG adoption poll for 
> draft-sajassi-bess-secure-evpn-06 [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 

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Matthew Bocci (Nokia)]

WG

I think there is consensus to adopt the draft from a technical point of view. 
However, the IPR disclosure was only posted on 8th June, so I will give the 
working group another week to consider this and then, if there are no 
objections, close the adoption poll on Friday 16th June 2023.

Regards

Matthew

From: Matthew Bocci (Nokia) 
Date: Thursday, 25 May 2023 at 11:35
To: bess@ietf.org 
Cc: draft-sajassi-bess-secure-e...@ietf.org 
, bess-cha...@ietf.org 

Subject: WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Eduard Metz]

Support adoption of this draft.

Few editorial comments
The draft seems related closely to "draft-ietf-bess-bgp-sdwan-usage", but
does not seem to refer to this. Shouldn't a reference be included and
terminology be aligned?
The main use case is the use of the public Internet for transport
- In this context I found the term PE a bit confusing (bgp-sdwan uses c-pe)
- Does this imply secure EVPN applicability is IP based underlays ?
Restrictions regarding underlay technology could be included for clarity

cheers,
  Eduard



On Thu, May 25, 2023 at 12:36 PM Matthew Bocci (Nokia) <
matthew.bo...@nokia.com> wrote:

> Hello,
>
>
>
> This email begins a two-week
> WG adoption poll for draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
>
> Currently, there is currently no IPR disclosure 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 June 9th 2023
>
>
>
> Regards,
>
> Matthew and Stephane
>
>
>
> [1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn
>
>
> ___
> 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 and IPR poll for draft-sajassi-bess-secure-evpn-06

[Luay Jalil]

Support adoption

Regards,
Luay

On Thu, May 25, 2023 at 5:36 AM Matthew Bocci (Nokia) <
matthew.bo...@nokia.com> wrote:

> Hello,
>
>
>
> This email begins a two-week
> WG adoption poll for draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
>
> Currently, there is currently no IPR disclosure 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 June 9th 2023
>
>
>
> Regards,
>
> Matthew and Stephane
>
>
>
> [1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn
>
>
> ___
> 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 and IPR poll for draft-sajassi-bess-secure-evpn-06

[Gyan Mishra]

I reviewed the draft and support adoption.

Thanks

Gyan

On Thu, May 25, 2023 at 6:35 AM Matthew Bocci (Nokia) <
matthew.bo...@nokia.com> wrote:

> Hello,
>
>
>
> This email begins a two-week
> WG adoption poll for draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
>
> Currently, there is currently no IPR disclosure 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 June 9th 2023
>
>
>
> Regards,
>
> Matthew and Stephane
>
>
>
> [1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn
>
>
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>
-- 



*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mis...@verizon.com *



*M 301 502-1347*
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Brian Weis]

Support as a co-author. I’m not aware of any of any undisclosed IPR other than 
what Ali has mentioned.

Thanks,
Brian

> On May 30, 2023, at 10:22 AM, Jorge Rabadan (Nokia)  
> wrote:
> 
> I support this document for WG adoption.
> Thanks.
> Jorge
>  
> From: BESS  on behalf of Matthew Bocci (Nokia) 
> 
> Date: Thursday, May 25, 2023 at 3:36 AM
> To: bess@ietf.org 
> Cc: draft-sajassi-bess-secure-e...@ietf.org 
> , bess-cha...@ietf.org 
> 
> Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
> 
> Hello,
>  
> This email begins a two-week WG adoption poll for 
> draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
> Currently, there is currently no IPR disclosure 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 June 9th 2023
>  
> Regards,
> Matthew and Stephane
>  
> [1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn 
> 
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Jorge Rabadan (Nokia)]

I support this document for WG adoption.
Thanks.
Jorge

From: BESS  on behalf of Matthew Bocci (Nokia) 

Date: Thursday, May 25, 2023 at 3:36 AM
To: bess@ietf.org 
Cc: draft-sajassi-bess-secure-e...@ietf.org 
, bess-cha...@ietf.org 

Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Linda Dunbar]

I support the WG adoption with the following questions and comments:

-   Section 5: How is the IPsec Databases (SPD, SAD, and generating Keying 
material for IPsec SAs)  different from the traditional IPsec Data Base 
generation described in the RFC 4301? Can you please emphasize the differences?
-   Section 8 Second paragraph states that the Device-Controller trust 
model is using the peer-to-peer protocol such as IKEv2. If the devices are 
already support EVPN, are they already have trust connection to their 
corresponding controller? Can TLS be used for Devices to exchange BGP messages 
with the controller?
-   -  If a SA is required per pair of IP addresses on two separate PEs, 
why it is not enough to have the existing ESP tunnel mode encapsulation for the 
packet exchanged between the two PEs like the following?

  Outer IP header:
  +---+
  |protocol = 50(IPsec ESP)   |
  |src = source-PE|
  |dst = dest-PE  |
  +---+  < --+
  |SPI(Security Parameter Idx)|Authenticated
  +---+  |
  |sequence number|  |
  +---+   <-+|
  | payload IP header:| ||
  |  src =  source-ip | ||
  |  dst =  dest-ip   | ||
  +---+  Encrypted   |
  |   TCP header +| ||
  ~payload (variable) ~ ||
  |   | ||
  +===+   <-+ ---+
  |   Authentication Data |
  +---+


 Is it necessary to have any outer tunnel header (other than the IPsec's ESP 
encapsulation) wrapping around the payload?

-

Thank you very much

Linda


> On May 25, 2023, at 5:35 AM, Matthew Bocci (Nokia) 
> mailto:matthew.bo...@nokia.com>> wrote:
>
> Hello,
>  This email begins a two-week WG adoption poll for 
> draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
> Currently, there is currently no IPR disclosure 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 June 9th 2023  Regards, Matthew and
> Stephane  [1]
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata
> tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-sajassi-bess-secure-evpn=05
> %7C01%7Clinda.dunbar%40futurewei.com%7Cad6059875d30470c56a908db6117f33
> d%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638210527722676515%7CUn
> known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW
> wiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=DwjLIezroZxS%2Fw8vyDe6ypUP3RSGq
> hqOLuLcvsMAkho%3D=0
> ___
> BESS mailing list
> BESS@ietf.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fbess=05%7C01%7Clinda.dunbar%40fut
> urewei.com%7Cad6059875d30470c56a908db6117f33d%7C0fee8ff2a3b240189c753a
> 1d5591fedc%7C1%7C0%7C638210527722676515%7CUnknown%7CTWFpbGZsb3d8eyJWIj
> oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
> %7C%7C=WGFVPLLGBKaSYnXDz7ATs1AII8JKBFfBalE7MeIsY7M%3D=0


___
BESS mailing list
BESS@ietf.org
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fbess=05%7C01%7Clinda.dunbar%40futurewei.com%7Cad6059875d30470c56a908db6117f33d%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638210527722676515%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=WGFVPLLGBKaSYnXDz7ATs1AII8JKBFfBalE7MeIsY7M%3D=0

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Lukas Krattiger (lkrattig)]

I red the draft and support the adoption
-Lukas


> On May 25, 2023, at 5:35 AM, Matthew Bocci (Nokia)  
> wrote:
> 
> Hello,
>  This email begins a two-week WG adoption poll for 
> draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
> Currently, there is currently no IPR disclosure 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 June 9th 2023
>  Regards,
> Matthew and Stephane
>  [1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn
>  ___
> 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 and IPR poll for draft-sajassi-bess-secure-evpn-06

[Samir Thoria (sthoria)]

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

Thanks,
Samir



From: BESS  on behalf of Matthew Bocci (Nokia) 

Date: Thursday, May 25, 2023 at 3:36 AM
To: bess@ietf.org 
Cc: draft-sajassi-bess-secure-e...@ietf.org 
, bess-cha...@ietf.org 

Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Satya Mohanty (satyamoh)]

I have read the draft and support its adoption.

Thanks,
--Satya

From: BESS  on behalf of Matthew Bocci (Nokia) 

Date: Thursday, May 25, 2023 at 3:36 AM
To: bess@ietf.org 
Cc: draft-sajassi-bess-secure-e...@ietf.org 
, bess-cha...@ietf.org 

Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Patrice Brissette (pbrisset)]

Hi,

I support the adoption
Regards,
Patrice Brissette
Distinguished Engineer
Cisco Systems




From: BESS  on behalf of "Matthew Bocci (Nokia)" 

Date: Thursday, May 25, 2023 at 06:36
To: "bess@ietf.org" 
Cc: "draft-sajassi-bess-secure-e...@ietf.org" 
, "bess-cha...@ietf.org" 

Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[David Carrel]

I am not aware of any undisclosed IPR.

David Carrel


On Thu, May 25, 2023 at 3:35 AM Matthew Bocci (Nokia) <
matthew.bo...@nokia.com> wrote:

> Hello,
>
>
>
> This email begins a two-week
> WG adoption poll for draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
>
> Currently, there is currently no IPR disclosure 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 June 9th 2023
>
>
>
> Regards,
>
> Matthew and Stephane
>
>
>
> [1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn
>
>
> ___
> 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 and IPR poll for draft-sajassi-bess-secure-evpn-06

[Ali Sajassi (sajassi)]

Support as a co-author. There is an IPR associated with this draft and I have 
already asked our legal department to register it with IETF.

Regards,
Ali

From: BESS  on behalf of Matthew Bocci (Nokia) 

Date: Thursday, May 25, 2023 at 3:36 AM
To: bess@ietf.org 
Cc: draft-sajassi-bess-secure-e...@ietf.org 
, bess-cha...@ietf.org 

Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Krishnaswamy Ananthamurthy (kriswamy)]

I have read and reviewed the draft and support the WG adoption.

Thanks
Krishna


From: BESS  on behalf of "Matthew Bocci (Nokia)" 

Date: Thursday, May 25, 2023 at 5:36 AM
To: "bess@ietf.org" 
Cc: "draft-sajassi-bess-secure-e...@ietf.org" 
, "bess-cha...@ietf.org" 

Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Mankamana Mishra (mankamis)]

Support the adoption.

From: BESS  on behalf of Matthew Bocci (Nokia) 

Date: Thursday, May 25, 2023 at 3:36 AM
To: bess@ietf.org 
Cc: draft-sajassi-bess-secure-e...@ietf.org 
, bess-cha...@ietf.org 

Subject: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[Ayan Banerjee (ayabaner)]

I am not aware of any undisclosed IPR.

Thanks,
Ayan

From: Matthew Bocci (Nokia) 
Date: Thursday, May 25, 2023 at 3:36 AM
To: bess@ietf.org 
Cc: draft-sajassi-bess-secure-e...@ietf.org 
, bess-cha...@ietf.org 

Subject: WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06
Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn

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

Re: [bess] WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[John E Drake]

I'm not aware of any of any undisclosed IPR.

Yours Irrespectively,

John

From: Matthew Bocci (Nokia) 
Sent: Thursday, May 25, 2023 6:35 AM
To: bess@ietf.org
Cc: draft-sajassi-bess-secure-e...@ietf.org; bess-cha...@ietf.org
Subject: WG Adoption and IPR poll for draft-sajassi-bess-secure-evpn-06

[External Email. Be cautious of content]

Hello,

This email begins a two-week WG adoption poll for 
draft-sajassi-bess-secure-evpn-06 [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 the authors and contributors.
Currently, there is currently no IPR disclosure 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 June 9th 2023

Regards,
Matthew and Stephane

[1] 
https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn



Juniper Business Use Only
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess