Hi, Ketan:

I prefer to “BGP based SRv6 Overlay Service”. This document defines the SRv6 
service SID and its control procedures.
Anyway, I know the contents, just want it more understandable.

Aijun Wang
China Telecom

> On Dec 9, 2020, at 12:25, Ketan Talaulikar (ketant) 
> <[email protected]> wrote:
> 
> 
> Hi Aijun,
>  
> Did you actually mean to say that the title should be “SRv6-based BGP Overlay 
> Services”? If so, I agree.
>  
> Thanks,
> Ketan
>  
> From: BESS <[email protected]> On Behalf Of Aijun Wang
> Sent: 09 December 2020 08:43
> To: 'Bocci, Matthew (Nokia - GB)' <[email protected]>; 
> [email protected]; [email protected]
> Subject: Re: [bess] WG Last Call, IPR and Implementation Poll for 
> draft-ietf-bess-srv6-services-05
>  
> Hi, All:
>  
> Support its publication.
>  
> One comments for the document:
> Should the name of document be changed to “BGP based SRv6 overlay services” 
> to reflect its actual scope?
> This document discusses just the distribution of SRv6 service label 
> distribution via BGP.  As also stated in the document, it also applies in the 
> plain IPv6 forwarding environment.
>  
>  
> Best Regards
>  
> Aijun Wang
> China Telecom
>  
>  
> From: [email protected] <[email protected]> On Behalf Of Bocci, 
> Matthew (Nokia - GB)
> Sent: Tuesday, December 1, 2020 1:16 AM
> To: [email protected]; [email protected]
> 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
> [email protected]
> https://www.ietf.org/mailman/listinfo/bess
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to