Section 1 (Introduction) was also updated.  So the I-D is not 100% RFC 7950...


The RFC 8407 reference was updated here: 

        
https://github.com/netmod-wg/yang2/commit/3ba121d620b9d850c32e1fa9f4f069b12d290dc6

per Qiufang's comment here:

        https://github.com/netmod-wg/yang2/pull/4#discussion_r3193386548


Kent


> On May 6, 2026, at 7:54 PM, Qin Wu <[email protected]> 
> wrote:
> 
> +1,
> I think the main difference with 7950 is
> Outdate reference update, one reference is still outdated which is RFC8407,
> I think it should be updated as RFC9907 now.
> 
> -Qin
> -----邮件原件-----
> 发件人: Michael Richardson [mailto:[email protected]] 
> 发送时间: 2026年5月6日 21:24
> 收件人: NetMod WG <[email protected]>
> 主题: [netmod] Re: WG adoption call: draft-yn-netmod-yang2-02
> 
> 
> Rob Wilton \(rwilton\) <[email protected]> wrote:
>> I don't think we need or should delay the adoption poll for
>> draft-yn-netmod-yang2-02 (the subject of this thread), but instead this
>> could probably happen in parallel.
> 
> Agreed.... I think that a regular pattern of design-team/virtual-interim 
> meetings are needed to get a group through Rob's issue document.
> I would discourage use of side meetings to do this.
> 
> One of the categories for the issues should be: bring up at plenary week 
> meeting.
> 
> 
> Particularly since this document is just 7950 reformatted as -00.
> (If I were chair, I would have just adopted it by chair fiat power, since it 
> contains no text that wasn't previously published)
> 
> --
> Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> **       My working hours and your working hours may be different.         **
> ** Please do not feel obligated to reply outside your normal working hours **
> 
> 
> 
> 
> _______________________________________________
> netmod mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

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

Reply via email to