Re: [netconf] [Editorial Errata Reported] RFC8650 (6369)

["Per Andersson (perander)" <[e-mail]>]

Hi!

In Section A.1.1 there is an example where id 22 is used with
the URI https://example.com/restconf/subscriptions/22 .

It is confusing to have examples which are conflicting in
content. On the same server, these subscriptions would not
be possible at the same time. Probably not a requirement
for a document, but it makes it simpler to read and understand.

Reading the rest of the document it seems that the intention
throughout is to append the subscription id to the URI.


--
Per

________________________________________
From: netconf <[e-mail]> on behalf of Rob Wilton (rwilton) <rwilton=[e-mail]>
Sent: Friday, January 12, 2024 15:16
To: RFC Errata System; Eric Voit (evoit); Reshad Rahman (rrahman); Einar Nilsen-Nygaard (einarnn); [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
Cc: [e-mail]
Subject: Re: [netconf] [Editorial Errata Reported] RFC8650 (6369)

Hi Authors, Netconf WG,

As I try and get through some of the errata backlog, I would like your input on this one.

I don't think that the RFC is technically wrong here (since the server can choose to use whatever URI they wish), I think that verifying this errata would probably be most helpful.  Otherwise, I will probably move it to "Hold for Document Update".  Any opinions?

Regards,
Rob


> -----Original Message-----
> From: RFC Errata System <[e-mail]>
> Sent: Thursday, December 24, 2020 7:52 PM
> To: Eric Voit (evoit) <[e-mail]>; Reshad Rahman (rrahman)
> <[e-mail]>; Einar Nilsen-Nygaard (einarnn)
> <[e-mail]>; [e-mail]; [e-mail];
> [e-mail]; Rob Wilton (rwilton) <[e-mail]>;
> [e-mail]; [e-mail]
> Cc: [e-mail]; [e-mail]; [e-mail]
> Subject: [Editorial Errata Reported] RFC8650 (6369)
>
> The following errata report has been submitted for RFC8650,
> "Dynamic Subscription to YANG Events and Datastores over RESTCONF".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6369
>
> --------------------------------------
> Type: Editorial
> Reported by: Muly Ilan <[e-mail]>
>
> Section: A.2.1
>
> Original Text
> -------------
> A.2.1.  "subscription-modified"
>
>    A "subscription-modified" encoded in JSON would look like:
>
>    {
>      "ietf-restconf:notification" : {
>        "eventTime": "2007-09-01T10:00:00Z",
>        "ietf-subscribed-notifications:subscription-modified": {
>          "id": 39,
>          "uri": "https://example.com/restconf/subscriptions/22"
>          "stream-xpath-filter": "/example-module:foo",
>          "stream": {
>             "ietf-netconf-subscribed-notifications" : "NETCONF"
>          }
>        }
>      }
>    }
>
> Corrected Text
> --------------
> A.2.1.  "subscription-modified"
>
>    A "subscription-modified" encoded in JSON would look like:
>
>    {
>      "ietf-restconf:notification" : {
>        "eventTime": "2007-09-01T10:00:00Z",
>        "ietf-subscribed-notifications:subscription-modified": {
>          "id": 39,
>          "uri": "https://example.com/restconf/subscriptions/39"
>          "stream-xpath-filter": "/example-module:foo",
>          "stream": {
>             "ietf-netconf-subscribed-notifications" : "NETCONF"
>          }
>        }
>      }
>    }
>
> Notes
> -----
> Change the URI to match the ID.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC8650 (draft-ietf-netconf-restconf-notif-15)
> --------------------------------------
> Title               : Dynamic Subscription to YANG Events and Datastores over
> RESTCONF
> Publication Date    : November 2019
> Author(s)           : E. Voit, R. Rahman, E. Nilsen-Nygaard, A. Clemm, A. Bierman
> Category            : PROPOSED STANDARD
> Source              : Network Configuration
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
_______________________________________________
netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf