RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Reported (1)

RFC 8639, "Subscription to YANG Notifications", September 2019

Source of RFC: netconf (ops)

Errata ID: 8073
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Andy Bierman
Date Reported: 2024-08-11

Section 4 says: 

  identity configurable-encoding {
    description
      "If a transport identity derives from this identity, it means
       that it supports configurable encodings.  An example of a
       configurable encoding might be a new identity such as

It should say:

  identity configurable-encoding {
    base transport;
    description
      "If a transport identity derives from this identity, it means
       that it supports configurable encodings.  An example of a
       configurable encoding might be a new identity such as

Notes:

This identity is incorrectly located in the section 'identities for encodings'
It is actually an identity for the 'transport' leaf.
The base is missing making it incorrect
(page 44)

Status: Held for Document Update (1)

RFC 8639, "Subscription to YANG Notifications", September 2019

Source of RFC: netconf (ops)

Errata ID: 6211
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: kent watsen
Date Reported: 2020-06-22
Held for Document Update by: Robert Wilton
Date Held: 2024-01-12

Section 7 says: 

   A specification for a transport MUST identify any encodings that are
   supported.  If a configured subscription's transport allows different
   encodings, the specification MUST identify the default encoding.

It should say:

   A specification for a transport MUST identify any encodings that are
   supported.  If a configured subscription's transport allows different
   encodings, the specification MUST identify the default encoding, or
   provide a mechanism whereby supported encodings can be discovered.

Notes:

https://mailarchive.ietf.org/arch/msg/netconf/XBpoFqtRynfc0zaRggMEiEMBW2M/

Status: Rejected (1)

RFC 8639, "Subscription to YANG Notifications", September 2019

Source of RFC: netconf (ops)

Errata ID: 6366
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Muly Ilan
Date Reported: 2020-12-24
Rejected by: RFC Editor
Date Rejected: 2021-01-19

Section 4. says: 

  feature subtree {
    description
      "This feature indicates support for YANG subtree filtering.";
    reference
      "RFC 6241: Network Configuration Protocol (NETCONF),
                 Section 6";
  }

  feature supports-vrf {
    description
      "This feature indicates that a publisher supports VRF
       configuration for configured subscriptions.  VRF support for
       dynamic subscriptions does not require this feature.";
    reference
      "RFC 8529: YANG Data Model for Network Instances,
                 Section 6";
  }

It should say:

  feature subtree {
    description
      "This feature indicates support for YANG subtree filtering.";
    reference
      "RFC 6241: Network Configuration Protocol (NETCONF),
                 Section 6";
  }

  feature supports-vrf {
    description
      "This feature indicates that a publisher supports VRF
       configuration for configured subscriptions.  VRF support for
       dynamic subscriptions does not require this feature.";
    reference
      "RFC 8529: YANG Data Model for Network Instances,
                 Section 6";
  }

Notes:

In the HTML version the two hyperlinks "Section 6" (for 'subtree' feature and for 'supports-vrf' feature) point to wrong RFCs.

--VERIFIER NOTES--
This is regarding the link generated in the rfc2html output, not the RFC itself (https://www.rfc-editor.org/rfc/rfc8639.txt).

Report New Errata



Advanced Search