Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

2023-09-28 Thread Krishnaswamy Ananthamurthy (kriswamy) 
I support for adoption.

Thanks
Krishna


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

Date: Thursday, September 28, 2023 at 9:51 AM
To: "bess@ietf.org" 
Cc: "draft-trr-bess-bgp-srv6-a...@ietf.org" 

Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

This email begins a two-week WG adoption and IPR poll for 
draft-trr-bess-bgp-srv6-args-02 [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 to the IPR poll 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 Thursday 12th October 2023.

[1] draft-trr-bess-bgp-srv6-args-02 - SRv6 Argument Signaling for BGP Services 
(ietf.org)
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

2023-09-28 Thread Mankamana Mishra (mankamis) 
Support the adoption of this draft.

From: BESS  on behalf of Matthew Bocci (Nokia) 

Date: Thursday, September 28, 2023 at 7:51 AM
To: bess@ietf.org 
Cc: draft-trr-bess-bgp-srv6-a...@ietf.org 

Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
This email begins a two-week WG adoption and IPR poll for 
draft-trr-bess-bgp-srv6-args-02 [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 to the IPR poll 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 Thursday 12th October 2023.

[1] draft-trr-bess-bgp-srv6-args-02 - SRv6 Argument Signaling for BGP Services 
(ietf.org)
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

2023-09-28 Thread Kamran Raza (skraza) 
As a co-author, I support the WG adoption of this document.
I am not aware of any IPR associated with this document/draft.

Thanks.

From: Ketan Talaulikar 
Date: Thursday, September 28, 2023 at 1:36 PM
To: Matthew Bocci (Nokia) 
Cc: bess@ietf.org , draft-trr-bess-bgp-srv6-a...@ietf.org 

Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi All,

I am not aware of any IPR associated with this document.

As a co-author, I would request the WG to support adoption - this updates the 
RFC9252 that was produced by our WG and provides clarifications that were found 
to be required during the multi-vendor interop.

Thanks,
Ketan


On Thu, Sep 28, 2023 at 8:19 PM Matthew Bocci (Nokia) 
mailto:matthew.bo...@nokia.com>> wrote:
This email begins a two-week WG adoption and IPR poll for 
draft-trr-bess-bgp-srv6-args-02 [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 to the IPR poll 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 Thursday 12th October 2023.

[1] draft-trr-bess-bgp-srv6-args-02 - SRv6 Argument Signaling for BGP Services 
(ietf.org)
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

2023-09-28 Thread Ketan Talaulikar 
Hi All,

I am not aware of any IPR associated with this document.

As a co-author, I would request the WG to support adoption - this updates
the RFC9252 that was produced by our WG and provides clarifications that
were found to be required during the multi-vendor interop.

Thanks,
Ketan


On Thu, Sep 28, 2023 at 8:19 PM Matthew Bocci (Nokia) <
matthew.bo...@nokia.com> wrote:

> This email begins a two-week WG adoption and IPR poll for
> draft-trr-bess-bgp-srv6-args-02 [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 to the IPR poll 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 Thursday 12th October 2023.
>
>
>
> [1] draft-trr-bess-bgp-srv6-args-02 - SRv6 Argument Signaling for BGP
> Services (ietf.org)
> 
>
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

2023-09-28 Thread Jorge Rabadan (Nokia) 
Hi,

As co-author, I support the document for WG adoption. It is important to have 
this adopted as soon as possible to make sure all EVPN SRv6 multi-homing 
implementations follow the same procedures.
Not aware of any relevant IPR.

Thanks.
Jorge

From: Matthew Bocci (Nokia) 
Date: Thursday, September 28, 2023 at 7:50 AM
To: bess@ietf.org 
Cc: draft-trr-bess-bgp-srv6-a...@ietf.org 

Subject: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
This email begins a two-week WG adoption and IPR poll for 
draft-trr-bess-bgp-srv6-args-02 [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 to the IPR poll 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 Thursday 12th October 2023.

[1] draft-trr-bess-bgp-srv6-args-02 - SRv6 Argument Signaling for BGP Services 
(ietf.org)
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02

2023-09-28 Thread Matthew Bocci (Nokia) 
This email begins a two-week WG adoption and IPR poll for 
draft-trr-bess-bgp-srv6-args-02 [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 to the IPR poll 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 Thursday 12th October 2023.

[1] draft-trr-bess-bgp-srv6-args-02 - SRv6 Argument Signaling for BGP Services 
(ietf.org)
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] Mail regarding draft-ietf-bess-secure-evpn

2023-09-28 Thread Zhuangshunwan 
Dear Co-Authors,

Regarding the "ID Length" in the Base (Minimal Set) DIM Sub-TLV, Figure 6 of 
draft-ietf-bess-secure-evpn shows the following:
0   1   2   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   ID Length   |   Nonce Length|I|   Flags |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Rekey |
   |Counter|
   +---+
   |   |
   ~  Originator ID + (Tenant ID) + (Subnet ID) + (Tenant Address) ~
   |   |
   +---+
   |   |
   ~  Nonce Data   ~
   |   |
   +---+

  Figure 6


And the corresponding description is as follows:
"ID Length (16 bits) is the length of the Originator ID + (Tenant ID)
   + (Subnet ID) + (Tenant Address) in bytes.  Nonce Length (8 bits) is
..."

Question: Per my understanding, should "ID length (16 bits)" be "ID length (8 
bits)"?

Best Regards,
Shunwan



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

[bess] Mail regarding draft-ietf-bess-bgp-sdwan-usage

2023-09-28 Thread Zhuangshunwan 

Dear authors,

Some of the text in the section 5.2 of draft-ietf-bess-bgp-sdwan-usage-15 
describes the following:
"
5.2. BGP Walk Through for Homogeneous Encrypted SD-WAN
...

   UPDATE U1:



 - MP-NLRI Path Attribute:

 192.0.2.4/30

 192.0.2.8/30

 - Nexthop: 192.0.2.2 (C-PE2)

 - Encapsulation Extended Community: TYPE = IPsec





   UPDATE U2:

 - MP-NLRI Path Attribute:

 192.0.2.2 (C-PE2)

 - Tunnel Encapsulation Path Attributes (as described in the

 [SECURE-EVPN]) for IPsec SA detailed attributes, including the WAN

 address to be used as the IP address of the IPsec encrypted

 packets.



   If different client routes attached to C-PE2 need to be reached by

   separate IPsec tunnels, the Color-Extended-Community [RFC9012] is

   used to associate routes with the tunnels. See Section 8 of

   [RFC9012].
...
"

I have one comment on the above text:
Regarding the "Encapsulation Extended Community: TYPE = IPsec" in UPDATE U1, 
maybe the possible TYPE should be ESP-Transport or ESP-in-UDP-Transport as 
described in Sections 9.1 and 9.2 of [Security-EVPN]?


Best Regards,
Shunwan



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

[bess] Publication has been requested for draft-ietf-bess-evpn-virtual-eth-segment-14

2023-09-28 Thread Matthew Bocci via Datatracker 
Matthew Bocci has requested publication of 
draft-ietf-bess-evpn-virtual-eth-segment-14 as Proposed Standard on behalf of 
the BESS working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/


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