Re: [netconf] Francesca Palombini's No Objection on draft-ietf-netconf-https-notif-14: (with COMMENT)

[Mahesh Jethanandani <[e-mail]>]

Hi Francesca,

> On Jan 31, 2024, at 2:31 AM, Francesca Palombini via Datatracker <[e-mail]> wrote:
> 
> Francesca Palombini has entered the following ballot position for
> draft-ietf-netconf-https-notif-14: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-https-notif/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thank you for the work on this document.
> 
> I strongly agree with John's DISCUSS. As he says, RFC required is probably what
> you want, also given that the "Reference" field specifically ask for "The RFC
> that defined the URN.".

I responded to John to say the next update will revert the change back to “RFC Required”.

> 
> In Section 1: Please update the reference to HTTP/1.1: 7230 has been obsoleted
> by 9110 and 9112 (you already have the ref to 9110, so here it is enough to
> change 7230 to 9112).

Will do in the next update.

> 
> Just a note from someone who is not experienced with YANG, so most likely OK to
> ignore, especially since IANA will most likely know how to deal with this, but
> by quickly scanning for the "YANG Notifications" registry group, I am not
> really sure where to find it. 3553 doesn't really point me to it. But again,
> happy to be educated.
> 

It is a new registry, and that is why you do not see it. IANA will create it once the document is approved.

Thanks

> 
> 


Mahesh Jethanandani
[e-mail]