RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Verified (1)

RFC 8650, "Dynamic Subscription to YANG Events and Datastores over RESTCONF", November 2019

Source of RFC: netconf (ops)

Errata ID: 6379
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML

Reported By: Muly Ilan
Date Reported: 2021-01-03
Verifier Name: Rob Wilton
Date Verified: 2021-01-05

Section A.1.1 says:

   Upon receipt of the successful response, the subscriber does a GET to
   the provided URI to start the flow of notification messages.  When
   the publisher receives this, the subscription is moved to the active
   state (c).

   GET /restconf/subscriptions/22

             Figure 5: "establish-subscription" Subsequent POST

It should say:

   Upon receipt of the successful response, the subscriber does a GET to
   the provided URI to start the flow of notification messages.  When
   the publisher receives this, the subscription is moved to the active
   state (c).

   GET /restconf/subscriptions/22

             Figure 5: "establish-subscription" Subsequent GET

Notes:

Substitute POST by GET in the figure caption

Status: Reported (3)

RFC 8650, "Dynamic Subscription to YANG Events and Datastores over RESTCONF", November 2019

Source of RFC: netconf (ops)

Errata ID: 6367
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Muly Ilan
Date Reported: 2020-12-24

Section A.1.3 says:

A.1.3.  Deleting Dynamic Subscriptions

   The following demonstrates deleting a subscription.  This
   subscription may have been to either a stream or a datastore.

   POST /restconf/operations
        /ietf-subscribed-notifications:delete-subscription

   {
    "delete-subscription": {
       "id": "22"
    }
   }

It should say:

A.1.3.  Deleting Dynamic Subscriptions

   The following demonstrates deleting a subscription.  This
   subscription may have been to either a stream or a datastore.

   POST /restconf/operations
        /ietf-subscribed-notifications:delete-subscription

   {
    "ietf-subscribed-notifications:input": {
       "id": "22"
    }
   }

Notes:

Encoding of RPC input parameters should follow RFC 8040 section 3.6.1

Errata ID: 6368
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Muly Ilan
Date Reported: 2020-12-24

Section A.2.1 says:

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"
         }
       }
     }
   }

It should say:

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": 22,
         "uri": "https://example.com/restconf/subscriptions/22"
         "stream-xpath-filter": "/example-module:foo",
         "stream": {
            "ietf-netconf-subscribed-notifications" : "NETCONF"
         }
       }
     }
   }

Notes:

Subscription ID should be 22 instead of 39.

An existing subscription ID cannot be changed. According to the previous examples in Appendix A the subscription got the ID 22. Also the example URI indicates ID of 22.

Errata ID: 6369
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Muly Ilan
Date Reported: 2020-12-24

Section A.2.1 says:

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"
         }
       }
     }
   }

It should say:

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.

Report New Errata