Re: [Bof-srv6ops] Re： Re: Please join the SRv6 OPS Charter update discussion

[Dhruv Dhody <[e-mail]>]

Hi Yisong,

I had some more edits based on my comments to the previous PR that you
already merged (as well as a few more minor changes) --
https://github.com/SRv6-Operations/IETF119-SRv6-Operations-Bof/compare/main...dhruvdhody:IETF119-SRv6-Operations-Bof:main

I tried to align the security text based on your response to Joel. Let me
know what you think.

Thanks!
Dhruv


On Tue, Jan 30, 2024 at 12:47 PM Yisong Liu <[e-mail]>
wrote:

> Hi Dhruv,
>
> Thank you for your comments. It's very helpful for updating the charter. I
> have merged the pull request to the main branch, and please check the
> github link.
>
> Best Regards
> Yisong
>
>
> 发件人: Dhruv Dhody <[e-mail]>
> 时间: 2024/01/29(星期一)16:37
> 收件人: Yisong Liu <[e-mail]>;
> 抄送人: bof-srv6ops <[e-mail]>;程伟强
> <[e-mail]>;warren <[e-mail]>;rwilton
> <[e-mail]>;mjethanandani <[e-mail]>;daniel.voyer
> <[e-mail]>;Suresh <[e-mail]>;aretana.ietf
> <[e-mail]>;james.n.guichard <[e-mail]>
> ;
> 主题: Re: [Bof-srv6ops] Please join the SRv6 OPS Charter update discussion
>
> Hi Yisong,
>
> I have added some comments on the pending PR, that can be viewed at -
> https://github.com/SRv6-Operations/IETF119-SRv6-Operations-Bof/pull/1/files/cac8edf6a3e45acd978c5b7ad2bc4bf3b9bf5740
>
> Thanks!
> Dhruv
>
> On Mon, Jan 29, 2024 at 1:50 PM Yisong Liu <[e-mail]>
> wrote:
>
>> Hi Everyone,
>>
>> We have tried to summarize the comments from the IESG for SRv6 OPS BoF
>> request and WG charter :
>> 1. How to avoid overlap and confliction with other related WG, for
>> example SPRING?
>> 2. Why this work could not be done in the existing WG?
>> 3. What are the key deliverables of the proposed WG?
>>
>> In order to address these comments, we have modified the BOF charter
>> including the following update:
>> 1. Add the clarification that the WG won't define solutions which may
>> have conflictions with the existing WG. If necessary, it could be
>> considered to have the limitation that there will be no standard track RFCs
>> produced in the WG.
>> 2. Update the “work item” to “Key deliverables” with detailed description
>> in order to make the expected output more clear and also to show that the
>> work of proposed WG is not suitable for existing SPRING WG.
>>
>> Highlight the information update of the BOF description:
>> 1.We have added the description in Scope section：The SRv6OPS WG focuses
>> on best practices, deployment guidance, and operational issues. Solutions
>> and protocol extensions are not within its scope.
>> 2.We have changed Work Item section to Key Deliverables section and added
>> specific description as the core output of the WG.
>> Key Deliverables:
>> * SRv6 deployment status and best practice, including deployment
>> scenarios (including metro, core and enterprise networks), scale-up
>> capability, inter-domain practice and so on.
>> * IPv6 address planning for SRv6 SID, especially IPv6 address planning
>> for SRv6 compression. Factors to consider include: IPv6 infrastructure
>> consistence, minimal consumption, flexibility and so on.
>> * SRv6 network configuration and operations, including: information model
>> for configuration, automation, monitoring and troubleshooting.
>> * SRv6 Security: Potential threats and best practice.
>>
>> The updated charter is attached for your review. We would appreciate it
>> if you could spare some time to review it and provide your insights on the
>> improvements needed.
>> Please take the charter update discussion with the pull request and open
>> issues in the github links:
>> https://github.com/SRv6-Operations/IETF119-SRv6-Operations-Bof/blob/main/SRv6OPS-Charter.md.
>> Or please just send your comments and questions in the mailing list.
>>
>> Thank you very much for your support.
>>
>> Best Regards
>> Yisong
>>
>> --
>> Bof-srv6ops mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/bof-srv6ops
>>
> --
> Bof-srv6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bof-srv6ops
>