RFC Errata
Found 3 records.
Status: Verified (2)
RFC 6244, "An Architecture for Network Management Using NETCONF and YANG", June 2011
Source of RFC: netmod (ops)
Errata ID: 3012
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Martin Bjorklund
Date Reported: 2011-11-04
Verifier Name: Dan Romascanu
Date Verified: 2011-11-07
Section 2.2.1 says:
| reference | Value must appear elsewhere in the data |
It should say:
| type leafref | Value must appear elsewhere in the data |
Notes:
The "reference" statement is used as a reference to some other specification.
The column heading is "Statement". It is not obvious that "type leafref" is a Statement, so I am not sure if the proposed corrected text is enough.
Errata ID: 5760
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ram Polisetty
Date Reported: 2019-06-22
Verifier Name: Ignas Bagdonas
Date Verified: 2019-07-09
Section 2.1 says:
configuration datastore where configuration changes can be made that will not affect the device until a "commit-configuration" operation is invoked.
It should say:
configuration datastore where configuration changes can be made that will not affect the device until a "<commit/>" operation is invoked.
Notes:
Netconf RPC for commit-configuration is <commit/>
Status: Held for Document Update (1)
RFC 6244, "An Architecture for Network Management Using NETCONF and YANG", June 2011
Source of RFC: netmod (ops)
Errata ID: 3356
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Benoit Claise
Date Reported: 2012-09-17
Held for Document Update by: Benoit Claise
Section 2.2.3 says:
augment /ospf:ospf/ospf:area/ospf:interfaces { leaf no-neighbor-down-notification { type empty; description "Don't inform other protocols about" + " neighbor down events";
It should say:
augment /ospf:ospf/ospf:area/ospf:interface { leaf no-neighbor-down-notification { type empty; description "Don't inform other protocols about" + " neighbor down events";
Notes:
Section 2.2.3
For example, if the above OSPF configuration were the standard, a
vendor module may augment this with vendor-specific extensions.
module vendorx-ospf {
namespace "http://vendorx.example.com/ospf";
prefix vendorx;
import example-ospf {
prefix ospf;
}
augment /ospf:ospf/ospf:area/ospf:interfaces {
leaf no-neighbor-down-notification {
type empty;
description "Don't inform other protocols about"
+ " neighbor down events";
}
}
}
While the "above OSPF configuration" refers to interface and not interfaces
module example-ospf {
namespace "http://example.org/netconf/ospf";
prefix ospf;
import network-types { // Access another module's def'ns
prefix nett;
}
container ospf { // Declare the top-level tag
list area { // Declare a list of "area" nodes
key name; // The key "name" identifies list members
leaf name {
type nett:area-id;
}
list interface {
key name;
leaf name {
type nett:interface-name;
}
leaf priority {
description "Designated router priority";
type uint8; // The type is a constraint on
// valid values for "priority".
}
leaf metric {
type uint16 {
range 1..65535;
}
}
leaf dead-interval {
units seconds;
type uint16 {
range 1..65535;
}
}
}
}
}
}