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

Mahesh Jethanandani <mjethanandani@gmail.com> Thu, 01 February 2024 15:47 UTC

From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <54A01396-A05B-4C88-8911-2ADE6A7140EF@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_08CDC7F8-3641-42A6-A3E9-CDF3AE866AA1"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
Date: Thu, 01 Feb 2024 07:47:05 -0800
In-Reply-To: <0759C743-43EB-4382-970F-DD77CBB669DE@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-netconf-https-notif@ietf.org, netconf-chairs@ietf.org, netconf@ietf.org, maqiufang1@huawei.com
To: Francesca Palombini <francesca.palombini@ericsson.com>
References: <170669711304.61715.4383969207518582579@ietfa.amsl.com> <0759C743-43EB-4382-970F-DD77CBB669DE@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/_3egsEdJDHVDm1Z3fZHD7QdD7zA>
Subject: Re: [netconf] Francesca Palombini's No Objection on draft-ietf-netconf-https-notif-14: (with COMMENT)
Precedence: list

Hi Francesca,

Just posted a -15 version of the document that updates the reference of HTTP/1.1 to 9112.

Thanks.

> On Jan 31, 2024, at 12:39 PM, Mahesh Jethanandani <mjethanandani@gmail.com> wrote:
> 
> Hi Francesca,
> 
>> On Jan 31, 2024, at 2:31 AM, Francesca Palombini via Datatracker <noreply@ietf.org <mailto:noreply@ietf.org>> 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/ <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/ <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
> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>

Mahesh Jethanandani
mjethanandani@gmail.com

[netconf] Francesca Palombini's No Objection on d… Francesca Palombini via Datatracker
Re: [netconf] Francesca Palombini's No Objection … Mahesh Jethanandani
Re: [netconf] Francesca Palombini's No Objection … Mahesh Jethanandani