[bess] Re: Rtgdir early review of draft-ietf-bess-mvpn-evpn-sr-p2mp-11

2024-11-15 Thread Rishabh Parekh
I will change non-assigned values to TBD in the next revision. On Fri, Nov 15, 2024 at 8:48 AM Jonathan Hardwick < jonathan.e.hardw...@gmail.com> wrote: > Hi Rishabh > > Thanks for the reply. For the code points in section 8 that you don't have > an early allocation for, it's best to replace the

[bess] Re: Rtgdir early review of draft-ietf-bess-mvpn-evpn-sr-p2mp-11

2024-11-15 Thread Rishabh Parekh (riparekh)
Jonathan, We will fix the NITS in next revision. We have already obtained early IANA allocations for the "SR-MPLS P2MP Tree". For "SRv6 P2MP Tree", the document just proposes a value.If you prefer, I can change the column to "Proposed Value" in "SRv6 Endpoint Behaviors" table for End.DTMC4/6.

[bess] Rtgdir early review of draft-ietf-bess-mvpn-evpn-sr-p2mp-11

2024-11-15 Thread Jonathan Hardwick via Datatracker
Reviewer: Jonathan Hardwick Review result: Has Nits Hi there I have conducted an Early Review of this document on behalf of the routing directorate. In my opinion, this document is ready to progress subject to resolution of a few nits. Please attend to these along with the next published version

[bess] Re: Rtgdir early review of draft-ietf-bess-mvpn-evpn-sr-p2mp-11

2024-11-15 Thread Jonathan Hardwick
Hi Rishabh Thanks for the reply. For the code points in section 8 that you don't have an early allocation for, it's best to replace the literal values you've specified with "TBD" and just leave it to IANA to fill in. Unless you actually do need them to be those specific values, in which case you s