RFC Errata
Found 5 records.
Status: Verified (3)
RFC 8650, "Dynamic Subscription to YANG Events and Datastores over RESTCONF", November 2019
Source of RFC: netconf (ops)
Errata ID: 7400
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Mohamed Boucadair
Date Reported: 2023-03-21
Verifier Name: Rob Wilton
Date Verified: 2023-10-02
Section Appendix A.3 says:
POST /restconf/operations
/ietf-subscribed-notifications:establish-subscription
{
"ietf-subscribed-notifications:input": {
"stream": "NETCONF",
"stream-xpath-filter":
"/ietf-vrrp:vrrp-protocol-error-event[
protocol-error-reason='checksum-error']/",
}
}
Figure 16: Establishing a Subscription Error Reason via XPath
...
POST /restconf/operations
/ietf-subscribed-notifications:modify-subscription
{
"ietf-subscribed-notifications:input": {
"stream": "NETCONF",
"stream-subtree-filter": {
"/ietf-vrrp:vrrp-protocol-error-event" : {}
}
}
}
Figure 17: Example "modify-subscription" RPC
It should say:
POST /restconf/operations
/ietf-subscribed-notifications:establish-subscription
{
"ietf-subscribed-notifications:input": {
"stream": "NETCONF",
"stream-xpath-filter":
"/ietf-vrrp:vrrp-protocol-error-event[
protocol-error-reason='checksum-error']/"
}
}
Figure 16: Establishing a Subscription Error Reason via XPath
...
POST /restconf/operations
/ietf-subscribed-notifications:modify-subscription
{
"ietf-subscribed-notifications:input": {
"stream": "NETCONF",
"stream-subtree-filter": {
"/ietf-vrrp:vrrp-protocol-error-event" : {}
}
}
}
Figure 17: Example "modify-subscription" RPC
Notes:
* There is a missing CRLF in both figures as per RFC9112:
--
HTTP-message = start-line CRLF
*( field-line CRLF )
CRLF
[ message-body ]
--
* The last item in the JSON of figure 16 includes a trailing "," while it shouldn't.
Errata ID: 6369
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: Muly Ilan
Date Reported: 2020-12-24
Verifier Name: Robert Wilton
Date Verified: 2024-01-12
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.
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 (2)
RFC 8650, "Dynamic Subscription to YANG Events and Datastores over RESTCONF", November 2019
Source of RFC: netconf (ops)
Errata ID: 6985
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Jernej Tuljak
Date Reported: 2022-06-01
Section A.1.1. says:
HTTP status code - 200
{
"id": 22,
"uri": "https://example.com/restconf/subscriptions/22"
}
It should say:
HTTP status code - 200
{
"ietf-subscribed-notifications:output": {
"id": 22,
"ietf-restconf-subscribed-notifications:uri":
"https://example.com/restconf/subscriptions/22"
}
}
Notes:
Original text for Figure 4 does not comply with RFC8040, Section 3.6.2. Encoding Operation Resource Output Parameters.
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