Hi Kent,

> On May 14, 2025, at 2:57 PM, Kent Watsen <[email protected] 
> <mailto:[email protected]>> wrote:
> 
> Hi Med,
> 
> If this document, in Section 3.1, moves 
> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-25#section-5.2
>  
> <https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-25#section-5.2>,
>  how come it doesn't also move "the template necessary for registration in 
> Appendix B"?

Good point.

rfc8407bis is in RFC Editor queue. I will ask them to hold the document to make 
the move.

Another question to consider is, do we need to move Appendix C?

Cheers.

> 
> Also, where in rfc8407bis is Section 3.2 coming from?
>  
> Kent // contributor
> 
> 
>> On May 14, 2025, at 5:50 PM, Kent Watsen <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> This email begins a 1-week WGLC on:
>> 
>>      Update to YANG Module Names Registration
>>      https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc6020-iana-update 
>> <https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc6020-iana-update>
>> 
>> If this draft seems unfamiliar to you, it is because it skipped the adoption 
>> process and became a WG document yesterday.  Please note that this document 
>> extracts content from 8407bis, which is already submitted to IESG for 
>> publication, and hence why Mahesh felt 1-week would be okay.
>> 
>> Please send comments to the list by May 21.
>> 
>> Kent // chair
>> 
>> _______________________________________________
>> netmod mailing list -- [email protected] <mailto:[email protected]>
>> To unsubscribe send an email to [email protected] 
>> <mailto:[email protected]>
> 
> _______________________________________________
> netmod mailing list -- [email protected] <mailto:[email protected]>
> To unsubscribe send an email to [email protected] 
> <mailto:[email protected]>


Mahesh Jethanandani
[email protected] <mailto:[email protected]>






_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to