Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05

[Ketan Talaulikar (ketant)]

Hi Matthew/Stephane,

I support the publication of this draft as standards track RFC. As a co-author, 
I am not aware of any IPR other than the one that has already been disclosed on 
the draft.

I would also like to report Cisco having implementations of this draft for 
L3VPN (IPv4/IPv6), Internet v4/v6 and EVPN services. Some of these 
implementations are already shipping and deployed in production networks.

Some of these implementation and deployment details have been captured in 
https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/

Thanks,
Ketan

From: Bocci, Matthew (Nokia - GB) 
Sent: 30 November 2020 22:46
To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org
Subject: WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-srv6-services-05

This email starts a two-week working group last call for 
draft-ietf-bess-srv6-services-05 [1]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until Monday 14th December 2020.

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.
There is currently one IPR disclosure.

In addition, we are polling for knowledge of implementations of this draft, per 
the BESS policy in [2].

Thank you,
Matthew & Stephane


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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

Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05

[Gaurav Dawra]

Hi Chairs,

I’m not aware of non-disclosed IPR.

As a co-author and editor, I support publishing this draft as a standards track 
RFC.

Gaurav
LinkedIn


> On Nov 30, 2020, at 9:15 AM, Bocci, Matthew (Nokia - GB) 
>  wrote:
> 
> 
> This email starts a two-week working group last call for 
> draft-ietf-bess-srv6-services-05 [1]
>  
> Please review the draft and send any comments to the BESS list. Also, please 
> indicate if you support publishing the draft as a standards track RFC.
>  
> This poll runs until Monday 14th December 2020.
>  
> 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. 
> There is currently one IPR disclosure.
>  
> In addition, we are polling for knowledge of implementations of this draft, 
> per the BESS policy in [2].   
>  
> Thank you,
> Matthew & Stephane
>  
>  
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>  
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05

[Wanghaibo (Rainsword)]

Dear authors and all,



 I find the following changes in the new version, which may cause incompatible 
changes in the implemented version.
[cid:image001.png@01D6C95C.F862B140]


The label field described in RFC4364:

4.3.4. How VPN-IPv4 NLRI Is Carried in BGP

   The labeled VPN-IPv4 NLRI itself is encoded as specified in

   [MPLS-BGP], where the 
prefix consists of an 8-byte RD followed by an

   IPv4 prefix.


 RFC 3107 describe the label field:

3. Carrying Label Mapping Information

  b) Label:



 The Label field carries one or more labels (that corresponds to

 the stack of labels 
[MPLS-ENCAPS]).  Each 
label is encoded as 3

 octets, where the high-order 20 bits contain the label value,

 and the low order bit contains "Bottom of Stack" (as defined in

 [MPLS-ENCAPS]).


According to the definition, the label field in RFC 4364 should be 3 bytes,  
but only 20 bits are used as the label value. So we may also use the entire 3 
octets.

On the other hand,  if only 20 bits are used, do we need to add the BoS flag to 
the part when do the transposition?



Best Regards,

Haibo

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - 
GB)
Sent: Tuesday, December 1, 2020 1:16 AM
To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org
Subject: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-srv6-services-05

This email starts a two-week working group last call for 
draft-ietf-bess-srv6-services-05 [1]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until Monday 14th December 2020.

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.
There is currently one IPR disclosure.

In addition, we are polling for knowledge of implementations of this draft, per 
the BESS policy in [2].

Thank you,
Matthew & Stephane


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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

Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05

[Zhuangshunwan]

Matthew, Stephane and WG,

I'm not aware of any relevant IPR.
As a co-author, I support publishing this draft as a standards track RFC.
I know that there are many implementations and interoperability tests that have 
already been listed in the document: 
https://tools.ietf.org/id/draft-matsushima-spring-srv6-deployment-status-09.txt

Regards,
--Shunwan

From: Bocci, Matthew (Nokia - GB) [mailto:matthew.bo...@nokia.com]
Sent: Tuesday, December 1, 2020 1:16 AM
To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org
Subject: WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-srv6-services-05

This email starts a two-week working group last call for 
draft-ietf-bess-srv6-services-05 [1]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until Monday 14th December 2020.

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.
There is currently one IPR disclosure.

In addition, we are polling for knowledge of implementations of this draft, per 
the BESS policy in [2].

Thank you,
Matthew & Stephane


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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

[bess] I-D Action: draft-ietf-bess-mvpn-evpn-sr-p2mp-01.txt

[internet-drafts]

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   : Multicast and Ethernet VPN with Segment Routing 
Point-to-Multipoint Trees
Authors : Rishabh Parekh
  Clarence Filsfils
  Arvind Venkateswaran
  Hooman Bidgoli
  Daniel Voyer
  Zhaohui Zhang
Filename: draft-ietf-bess-mvpn-evpn-sr-p2mp-01.txt
Pages   : 15
Date: 2020-12-02

Abstract:
   A Point-to-Multipoint (P2MP) Tree in a Segment Routing domain
   efficiently carries traffic from a Root to a set of Leaves.  This
   document describes extensions to BGP encodings and procedures for
   P2MP trees used in BGP/MPLS IP VPNs and Ethernet VPNs.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-evpn-sr-p2mp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-mvpn-evpn-sr-p2mp-01
https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-evpn-sr-p2mp-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-mvpn-evpn-sr-p2mp-01


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