From cc958e460e059eedec79e9fd91733e5523b23a5e Mon Sep 17 00:00:00 2001 From: Miroslav Kovac Date: Tue, 12 Sep 2023 18:06:17 +0000 Subject: [PATCH] Cronjob - daily check of IETF modules. --- .../ietf-isis-flex-algo@2023-03-06.yang | 27 ++- .../ietf-isis-link-attr@2023-03-06.yang | 15 +- .../ietf-isis-msd@2023-03-06.yang | 3 +- ...tf-isis-remaining-lifetime@2023-03-06.yang | 6 +- ....yang => ietf-ospfv3-srv6@2023-09-09.yang} | 195 ++++++++---------- ...ang => ietf-pcep-srpolicy@2023-09-11.yang} | 6 +- ...07.yang => ietf-pcep-srv6@2023-09-11.yang} | 17 +- ...6.yang => ietf-pcep-stats@2023-09-11.yang} | 22 +- ...3-03-06.yang => ietf-pcep@2023-09-11.yang} | 30 +-- .../ietf-rift@2023-07-05.yang | 2 +- ...yang => ietf-te-telemetry@2023-09-11.yang} | 2 +- 11 files changed, 159 insertions(+), 166 deletions(-) rename experimental/ietf-extracted-YANG-modules/{ietf-ospfv3-srv6@2023-03-07.yang => ietf-ospfv3-srv6@2023-09-09.yang} (79%) rename experimental/ietf-extracted-YANG-modules/{ietf-pcep-srpolicy@2023-03-07.yang => ietf-pcep-srpolicy@2023-09-11.yang} (97%) rename experimental/ietf-extracted-YANG-modules/{ietf-pcep-srv6@2023-03-07.yang => ietf-pcep-srv6@2023-09-11.yang} (95%) rename experimental/ietf-extracted-YANG-modules/{ietf-pcep-stats@2023-03-06.yang => ietf-pcep-stats@2023-09-11.yang} (97%) rename experimental/ietf-extracted-YANG-modules/{ietf-pcep@2023-03-06.yang => ietf-pcep@2023-09-11.yang} (99%) rename experimental/ietf-extracted-YANG-modules/{ietf-te-telemetry@2023-03-10.yang => ietf-te-telemetry@2023-09-11.yang} (99%) diff --git a/experimental/ietf-extracted-YANG-modules/ietf-isis-flex-algo@2023-03-06.yang b/experimental/ietf-extracted-YANG-modules/ietf-isis-flex-algo@2023-03-06.yang index 0a0c199d3..3d1100340 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-isis-flex-algo@2023-03-06.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-isis-flex-algo@2023-03-06.yang @@ -70,12 +70,14 @@ module ietf-isis-flex-algo { described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; - reference "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; + reference + "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; revision 2023-03-06 { description "Initial Version"; - reference "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; + reference + "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; } /* Identities */ @@ -185,7 +187,6 @@ module ietf-isis-flex-algo { description "The flex-algo definition flags sub-tlv."; } - grouping fa-ex-srlg-sub-tlv { container fa-ex-srlg-sub-tlv { leaf-list srlgs { @@ -378,6 +379,7 @@ module ietf-isis-flex-algo { description "Use flex-algo prefix metric."; } + leaf priority { type uint8; description @@ -399,7 +401,8 @@ module ietf-isis-flex-algo { "/isis:isis/isis:database/isis:levels/isis:lsp"+ "/isis:router-capabilities" { when "/rt:routing/rt:control-plane-protocols/"+ - "rt:control-plane-protocol/rt:type = 'isis:isis'" { + "rt:control-plane-protocol/"+ + "rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } @@ -412,9 +415,11 @@ module ietf-isis-flex-algo { augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:levels/isis:lsp"+ - "/isis:extended-ipv4-reachability/isis:prefixes" { + "/isis:extended-ipv4-reachability/"+ + "isis:prefixes" { when "/rt:routing/rt:control-plane-protocols/"+ - "rt:control-plane-protocol/rt:type = 'isis:isis'" { + "rt:control-plane-protocol/"+ + "rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } @@ -428,7 +433,8 @@ module ietf-isis-flex-algo { "/isis:isis/isis:database/isis:levels/isis:lsp"+ "/isis:mt-extended-ipv4-reachability/isis:prefixes" { when "/rt:routing/rt:control-plane-protocols/"+ - "rt:control-plane-protocol/rt:type = 'isis:isis'" { + "rt:control-plane-protocol/"+ + "rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } @@ -442,7 +448,8 @@ module ietf-isis-flex-algo { "/isis:isis/isis:database/isis:levels/isis:lsp"+ "/isis:ipv6-reachability/isis:prefixes" { when "/rt:routing/rt:control-plane-protocols/"+ - "rt:control-plane-protocol/rt:type = 'isis:isis'" { + "rt:control-plane-protocol/"+ + "rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } @@ -456,7 +463,8 @@ module ietf-isis-flex-algo { "/isis:isis/isis:database/isis:levels/isis:lsp"+ "/isis:mt-ipv6-reachability/isis:prefixes" { when "/rt:routing/rt:control-plane-protocols/"+ - "rt:control-plane-protocol/rt:type = 'isis:isis'" { + "rt:control-plane-protocol/"+ + "rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } @@ -466,7 +474,6 @@ module ietf-isis-flex-algo { } /* notification */ - notification flex-algo-not-supported { uses isis:notification-instance-hdr; leaf flex-algo-number { diff --git a/experimental/ietf-extracted-YANG-modules/ietf-isis-link-attr@2023-03-06.yang b/experimental/ietf-extracted-YANG-modules/ietf-isis-link-attr@2023-03-06.yang index c3fdbfd9e..a0055c6dd 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-isis-link-attr@2023-03-06.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-isis-link-attr@2023-03-06.yang @@ -69,8 +69,8 @@ module ietf-isis-link-attr { description "Initial version"; reference - "RFC XXXX: A YANG Data Model for IS-IS Application-Specific Link - Attributes."; + "RFC XXXX: A YANG Data Model for IS-IS Application-Specific + Link Attributes."; } identity sabm-bit { @@ -99,8 +99,8 @@ module ietf-isis-link-attr { grouping application-identifier-bit-mask { description - "Identification of the set of applications associated with link - attribute advertisements"; + "Identification of the set of applications associated with + link attribute advertisements"; leaf l-flag { type boolean; @@ -294,7 +294,8 @@ module ietf-isis-link-attr { leaf transition { type empty; description - "Send both application-specific and legacy advertisements."; + "Send both application-specific and legacy + advertisements."; } leaf app-specific{ type empty; @@ -314,7 +315,8 @@ module ietf-isis-link-attr { "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:interfaces/isis:interface" { when "/rt:routing/rt:control-plane-protocols/"+ - "rt:control-plane-protocol/rt:type = 'isis:isis'" { + "rt:control-plane-protocol/"+ + "rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used."; } @@ -325,6 +327,7 @@ module ietf-isis-link-attr { container isis-asla { list interface-asla { key app-id; + leaf app-id { type uint16 { range "0 .. 1023"; diff --git a/experimental/ietf-extracted-YANG-modules/ietf-isis-msd@2023-03-06.yang b/experimental/ietf-extracted-YANG-modules/ietf-isis-msd@2023-03-06.yang index 4e7cdf296..c80ad8ef1 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-isis-msd@2023-03-06.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-isis-msd@2023-03-06.yang @@ -102,7 +102,8 @@ module ietf-isis-msd { + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:router-capabilities" { - when "derived-from-or-self(../../../../../rt:type, 'isis:isis')" { + when "derived-from-or-self(../../../../../rt:type," + + "'isis:isis')" { description "This augment ISIS routing protocol when used"; } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-isis-remaining-lifetime@2023-03-06.yang b/experimental/ietf-extracted-YANG-modules/ietf-isis-remaining-lifetime@2023-03-06.yang index d058bf2cd..d7b3bacfe 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-isis-remaining-lifetime@2023-03-06.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-isis-remaining-lifetime@2023-03-06.yang @@ -1,6 +1,7 @@ module ietf-isis-remaining-lifetime { yang-version 1.1; - namespace "urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime"; + namespace + "urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime"; prefix isis-remaining-lifetime; @@ -48,7 +49,8 @@ module ietf-isis-remaining-lifetime { description "Initial version"; reference - "RFC XXXX: A YANG Data Model for IS-IS Minimum Remaining Lifetime."; + "RFC XXXX: A YANG Data Model for IS-IS Minimum Remaining + Lifetime."; } notification corrupt-remaining-lifetime { diff --git a/experimental/ietf-extracted-YANG-modules/ietf-ospfv3-srv6@2023-03-07.yang b/experimental/ietf-extracted-YANG-modules/ietf-ospfv3-srv6@2023-09-09.yang similarity index 79% rename from experimental/ietf-extracted-YANG-modules/ietf-ospfv3-srv6@2023-03-07.yang rename to experimental/ietf-extracted-YANG-modules/ietf-ospfv3-srv6@2023-09-09.yang index 76f8b9b62..97702af35 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-ospfv3-srv6@2023-03-07.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-ospfv3-srv6@2023-09-09.yang @@ -90,7 +90,7 @@ module ietf-ospfv3-srv6 { described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; - revision 2023-03-07 { + revision 2023-09-09 { description "Initial revision."; reference @@ -196,14 +196,14 @@ module ietf-ospfv3-srv6 { identity s1-bit { base ospf:ospfv3-lsa-option; description - "the S1/S2 bits are dependent on the desired + "The S1/S2 bits are dependent on the desired flooding scope for the LSA."; } identity s2-bit { base ospf:ospfv3-lsa-option; description - "the S1/S2 bits are dependent on the desired + "The S1/S2 bits are dependent on the desired flooding scope for the LSA."; } @@ -240,6 +240,64 @@ module ietf-ospfv3-srv6 { "NSSA External"; } + identity srv6-capability-bit { + description + "Base identity for SRv6 capability TLV bits."; + } + + identity o-bit { + base srv6-capability-bit; + description + "O-flag."; + reference + "RFC 9259: Operations, Administration, and Maintenance (OAM) + in Segment Routing over IPv6 (SRv6)"; + } + + identity srv6-end-sid-bit { + description + "Base identity for SRv6 End SID sub-TLV bits."; + } + + identity srv6-endx-sid-bit { + description + "Base identity for SRv6 End.X SID sub-TLV bits."; + } + + identity b-bit { + base srv6-endx-sid-bit; + description + "B-flag. Backup flag. If set, the End.X sid is + eligible for protection."; + } + + identity s-bit { + base srv6-endx-sid-bit; + description + "S-flag. Set flag. When set, the End.X sid refers to + a set of adjacencies (and therefore May be assigned + to other adjacencies as well."; + } + + identity p-bit { + base srv6-endx-sid-bit; + description + "P-flag. Persistent flag. When set, the End.X sid is + persistently allocated, i.e., the End.x sid value + remains consistent across router restart and/or + interface flap."; + } + + identity ac-bit { + base ospfv3-e-lsa:ospfv3-e-prefix-option; + description + "When the prefix/SRv6 Locator is configured as anycast, + the AC-bit MUST be set. Otherwise, this flag MUST be + clear."; + reference + "draft-ietf-lsr-ospfv3-srv6-extensions"; + } + /* typedef */ typedef srv6-sid-value { type inet:ipv6-address-no-zone; @@ -255,64 +313,18 @@ module ietf-ospfv3-srv6 { } /* Groupings */ - grouping srv6-msds { - description - "Used to advertise node/link specific - values for Maximum Sid Depths(MSD) of various types"; - container srv6-msd { - description - "Maximum SRv6 SID Depths."; - leaf max-segments-left { - type uint8; - description - "The Maximum Segments Left MSD Type specifies - the maximum value of the 'SL' field in the SRH - of a received packet before applying the Endpoint - behavior associated with a SID."; - } - leaf max-end-pop { - type uint8; - description - "The Maximum End Pop MSD Type specifies the maximum - number of SIDs in the SRH to which the router can - apply 'PSP' or 'USP' behavior, as defined in flavors."; - } - leaf max-h-encaps { - type uint8; - description - "The Maximum H.Encaps MSD Type specifies the maximum number - of SIDs that can be included as part of the 'H.Encaps' - behavior"; - } - leaf max-end-d { - type uint8; - description - "The maximum number of SIDs in an SRH when performing - decapsulation associated with 'End.Dx' functions - (e.g., 'End.DX6' and 'End.DT6')."; - } - } - } - grouping srv6-capabilities { description "SRV6 capability grouping."; container srv6-capability { description "SRv6 capability."; - leaf flags { - type bits { - bit o-flag { - position 1; - description - "If set, then router is capable of supporting SRH O-bit - "; - } + leaf-list flags { + type identityref { + base srv6-capability-bit; } description - "Flags."; - reference - "I-D.ali-spring-srv6-oam: OAM in SRv6"; + "SRv6 Capability TLV flag bits list."; } } } @@ -322,11 +334,14 @@ module ietf-ospfv3-srv6 { "This group defines srv6 endpoint function"; container endpoint-func { description - "Srv6 Endpoint function Descriptor."; - leaf fuc-flags { - type uint8; + "SRv6 Endpoint function Descriptor."; + leaf-list flags { + type identityref { + base srv6-end-sid-bit; + } description - "No function flags are currently being defined."; + "SRv6 End SID sub-TLV flag bits list. No flags + are currently being defined."; } leaf endpoint-func { type identityref { @@ -349,10 +364,12 @@ module ietf-ospfv3-srv6 { container srv6-end-sid { description "SRv6 Segment Identifier(SID) with Endpoint functions."; - leaf flags { - type uint8; + leaf-list flags { + type identityref { + base srv6-end-sid-bit; + } description - "NO flags are currently being defined."; + "SRv6 end sid flags."; } uses srv6-endpoint-func; @@ -409,31 +426,13 @@ module ietf-ospfv3-srv6 { "SRv6 sids associated with an adjacency."; uses srv6-endpoint-func; - leaf flags { - type bits { - bit b-flag { - position 0; - description - "Backup Flag. If set, the SID refers to a path that is - eligible for protection"; - } - bit s-flag { - position 1; - description - "Set Flag. When set, the S-Flag indicates that the - End.X SID refers to a set of adjacencies (and therefore - MAY be assigned to other adjacencies as well)."; - } - bit p-flag { - position 2; - description - "Persistent Flag: If set, the SID is persistently - allocated, i.e., the SID value remains consistent - across router restart and session/interface flap."; - } + + leaf-list func-flags { + type identityref { + base srv6-endx-sid-bit; } description - "Flags for end.x subtlv."; + "Flags for SRv6 end x SID."; } leaf algorithm { @@ -471,7 +470,7 @@ module ietf-ospfv3-srv6 { "This group defines srv6 locator tlv."; container srv6-locactor-tlv { description - "This contains a srv6 locator tlv."; + "This contains a SRv6 locator tlv."; leaf route-type { type identityref { base LOCATOR-ROUTE-TYPE; @@ -493,22 +492,9 @@ module ietf-ospfv3-srv6 { prefix as number of bits (1-128)"; } - leaf flags { - type bits { - bit n-flag { - position 0; - description - "When the locator uniquely identifies a node in the - network (i.e. it is provisioned on one and only one - node), the N bit MUST be set. Otherwise, this bit - MUST be clear"; - } - bit a-flag { - position 1; - description - "When the Locator is configured as anycast, the A bit - SHOULD be set. Otherwise, this bit MUST be clear"; - } + leaf-list flags { + type identityref { + base ospfv3-e-lsa:ospfv3-e-prefix-option; } description "Flags for srv6 locator tlv."; @@ -519,7 +505,6 @@ module ietf-ospfv3-srv6 { description "Metric value."; } - leaf-list locator { type inet:ipv6-address-no-zone; description @@ -563,7 +548,8 @@ module ietf-ospfv3-srv6 { + "/srv6:locators/srv6:locator/srv6:name"; } description - "Enable OSPFv3 segment-routing IPv6 with specified Locator."; + "Enable OSPFv3 segment-routing IPv6 with specified + locator."; } leaf persistent-end-x-sid{ type boolean; @@ -654,7 +640,7 @@ module ietf-ospfv3-srv6 { description "This augments OSPFv3 protocol router capability."; uses srv6-capabilities; - uses srv6-msds; + uses srv6:srv6-msd-signaled; } augment "/rt:routing/rt:control-plane-protocols" @@ -665,7 +651,8 @@ module ietf-ospfv3-srv6 { + "/ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router/" + "ospfv3-e-lsa:e-router-tlvs/" + "ospfv3-e-lsa:link-tlv" { - when "../../../../../../../../../../../../rt:type = 'ospf:ospfv3'" { + when "../../../../../../../../../../../../rt:type" + + "= 'ospf:ospfv3'" { description "This augment OSPFv3 routing protocol when used"; } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-pcep-srpolicy@2023-03-07.yang b/experimental/ietf-extracted-YANG-modules/ietf-pcep-srpolicy@2023-09-11.yang similarity index 97% rename from experimental/ietf-extracted-YANG-modules/ietf-pcep-srpolicy@2023-03-07.yang rename to experimental/ietf-extracted-YANG-modules/ietf-pcep-srpolicy@2023-09-11.yang index f04586c7b..a4d4e638b 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-pcep-srpolicy@2023-03-07.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-pcep-srpolicy@2023-09-11.yang @@ -53,7 +53,7 @@ module ietf-pcep-srpolicy { This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2023-03-07 { + revision 2023-09-11 { description "Initial revision."; reference @@ -173,10 +173,10 @@ module ietf-pcep-srpolicy { container cp { uses sr-policy-cp; description - "SR Policy Candidate Path"; + "SR Policy Candidate Path information"; } description - "SR Policy"; + "SR Policy information"; } } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-pcep-srv6@2023-03-07.yang b/experimental/ietf-extracted-YANG-modules/ietf-pcep-srv6@2023-09-11.yang similarity index 95% rename from experimental/ietf-extracted-YANG-modules/ietf-pcep-srv6@2023-03-07.yang rename to experimental/ietf-extracted-YANG-modules/ietf-pcep-srv6@2023-09-11.yang index d52d82ade..9102c9c31 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-pcep-srv6@2023-03-07.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-pcep-srv6@2023-09-11.yang @@ -48,7 +48,7 @@ module ietf-pcep-srv6 { This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2023-03-07 { + revision 2023-09-11 { description "Initial revision."; reference @@ -133,13 +133,6 @@ module ietf-pcep-srv6 { Adjacency Identifier (NAI) to SRv6 Segment Identifier (SID)"; } - leaf msd-limit { - type boolean; - default "false"; - description - "True indicates no limit on MSD, the - list srv6-msd is ignored"; - } list srv6-msd { key "msd-type"; description @@ -224,7 +217,7 @@ module ietf-pcep-srv6 { augment "/pcep:pcep/pcep:entity/pcep:capabilities" { description - "Augmenting SRv6"; + "Augmenting SRv6 capabilities"; uses srv6; uses sid-str; } @@ -232,13 +225,13 @@ module ietf-pcep-srv6 { augment "/pcep:pcep/pcep:entity/pcep:peers/pcep:peer" + "/pcep:capabilities" { description - "Augmenting SRv6"; + "Augmenting SRv6 capabilities for peer"; uses srv6; } augment "/pcep:pcep/pcep:entity/pcep:lsp-db/pcep:lsp" { description - "Augmenting SRv6"; + "Augmenting SRv6 for LSP"; container srv6 { when "derived-from-or-self @@ -250,7 +243,7 @@ module ietf-pcep-srv6 { if-feature "srv6"; uses segment-list; description - "SRv6"; + "SRv6 information"; } } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-pcep-stats@2023-03-06.yang b/experimental/ietf-extracted-YANG-modules/ietf-pcep-stats@2023-09-11.yang similarity index 97% rename from experimental/ietf-extracted-YANG-modules/ietf-pcep-stats@2023-03-06.yang rename to experimental/ietf-extracted-YANG-modules/ietf-pcep-stats@2023-09-11.yang index c9a10af8c..15975b9a6 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-pcep-stats@2023-03-06.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-pcep-stats@2023-09-11.yang @@ -40,7 +40,7 @@ module ietf-pcep-stats { This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2023-03-06 { + revision 2023-09-11 { description "Initial revision."; reference @@ -55,7 +55,7 @@ module ietf-pcep-stats { grouping stats { description "This grouping defines statistics for PCEP. It is used - for both peer and current session."; + for both peer and current sessions."; leaf discontinuity-time { type yang:timestamp; description @@ -186,7 +186,7 @@ module ietf-pcep-stats { leaf corrupt-rcvd { type yang:counter32; description - "The number of corrupted PCEP message received."; + "The number of corrupted PCEP messages received."; } leaf req-sent { when "../../pcep:role = 'pce'" @@ -541,7 +541,7 @@ module ietf-pcep-stats { } type yang:counter32; description - "The number of LSP Reports sent. A LSP report + "The number of LSP Reports sent. An LSP report corresponds 1:1 with an LSP object in a PCRpt message. This might be greater than pcrpt-sent because multiple reports can @@ -556,7 +556,7 @@ module ietf-pcep-stats { } type yang:counter32; description - "The number of LSP Reports received. A LSP report + "The number of LSP Reports received. An LSP report corresponds 1:1 with an LSP object in a PCRpt message. This might be greater than pcrpt-rcvd because @@ -585,7 +585,7 @@ module ietf-pcep-stats { } type yang:counter32; description - "The number of LSP updates sent. A LSP update + "The number of LSP updates sent. An LSP update corresponds 1:1 with an LSP object in a PCUpd message. This might be greater than pcupd-sent because multiple updates can @@ -600,7 +600,7 @@ module ietf-pcep-stats { } type yang:counter32; description - "The number of LSP Updates received. A LSP update + "The number of LSP Updates received. An LSP update corresponds 1:1 with an LSP object in a PCUpd message. This might be greater than pcupd-rcvd because @@ -635,7 +635,7 @@ module ietf-pcep-stats { received. An update to an undelegated LSP is a update whose LSP object does not contain the PLSP-ID of any LSP that is currently - delegated to current PCEP session."; + delegated to the current PCEP session."; } leaf upd-rcvd-error-sent { when "../../../pcep:role = 'pce'" @@ -686,7 +686,7 @@ module ietf-pcep-stats { type yang:counter32; description "The number of LSP Initiation sent via PCE. - A LSP initiation corresponds 1:1 with an LSP + An LSP initiation corresponds 1:1 with an LSP object in a PCInitiate message. This might be greater than pcinitiate-sent because multiple initiations can be batched into a @@ -702,7 +702,7 @@ module ietf-pcep-stats { type yang:counter32; description "The number of LSP Initiation received from - PCE. A LSP initiation corresponds 1:1 with + PCE. An LSP initiation corresponds 1:1 with an LSP object in a PCInitiate message. This might be greater than pcinitiate-rcvd because multiple initiations can be batched @@ -718,7 +718,7 @@ module ietf-pcep-stats { type yang:counter32; description "The number of initiations of LSPs received - that were responded by the local PCEP entity + that were responded to by the local PCEP entity by sending a PCErr message."; } } diff --git a/experimental/ietf-extracted-YANG-modules/ietf-pcep@2023-03-06.yang b/experimental/ietf-extracted-YANG-modules/ietf-pcep@2023-09-11.yang similarity index 99% rename from experimental/ietf-extracted-YANG-modules/ietf-pcep@2023-03-06.yang rename to experimental/ietf-extracted-YANG-modules/ietf-pcep@2023-09-11.yang index 8133d24d0..9a0e6104c 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-pcep@2023-03-06.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-pcep@2023-09-11.yang @@ -83,7 +83,7 @@ module ietf-pcep { described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; - revision 2023-03-06 { + revision 2023-09-11 { description "Initial revision."; reference @@ -176,7 +176,7 @@ module ietf-pcep { - oper-status-going-up(3): Activating - oper-status-going-down(4): Deactivating - oper-status-failed(5): Failed - - oper-status-failed-perm(6): Failed Permanantly"; + - oper-status-failed-perm(6): Failed Permanently"; reference "RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)"; @@ -670,7 +670,7 @@ module ietf-pcep { maybe relevant to both PCC and PCE. This information corresponds to PCE auto-discovery information. - The scope relates to either local entity or a peer."; + The scope relates to either a local entity or a peer."; container domains { description "The domain for the local PCEP entity or a peer."; @@ -687,7 +687,7 @@ module ietf-pcep { container capabilities { description "The PCEP entity or peer capability information. - This maybe relevant to PCE selection as well. + This may be relevant to PCE selection as well. This information corresponds to PCE auto- discovery information."; reference @@ -844,7 +844,7 @@ module ietf-pcep { } } description - "The bits string indicating the capabiliies"; + "The bits string indicating the capabilities"; reference "IANA IGP: Path Computation Element (PCE) Capability Flags in Interior Gateway Protocol (IGP) Parameters @@ -932,7 +932,7 @@ module ietf-pcep { type boolean; default "false"; description - "True indicates capability to resolve Node or + "True indicates the capability to resolve Node or Adjacency Identifier (NAI) to Segment Identifier (SID)"; } @@ -941,7 +941,7 @@ module ietf-pcep { if-feature "stateful"; if-feature "gmpls"; description - "If Stateful GMPLS is supported for local entity + "If Stateful GMPLS is supported for a local entity or a peer"; reference "RFC 8779: Path Computation Element @@ -1016,13 +1016,13 @@ module ietf-pcep { grouping pce-info { description "This grouping specifies all PCE information - which maybe relevant to the PCE selection. + which may be relevant to the PCE selection. This information corresponds to PCE auto-discovery information."; container scope { description "This container defines PCE path computation scope - information which maybe relevant to PCE selection. + information which may be relevant to PCE selection. This information corresponds to PCE auto-discovery information."; leaf path-scope { @@ -1118,7 +1118,7 @@ module ietf-pcep { grouping notification-instance-hdr { description - "This group describes common instance specific data + "This group describes common instance-specific data for notifications."; leaf peer-addr { type leafref { @@ -1594,7 +1594,7 @@ module ietf-pcep { of path computation requests. The aim of the SyncTimer is to avoid the storage of unused synchronized requests should one of - them get lost for some reasons (for example, a + them get lost for some reason (for example, a misbehaving PCC). Zero means that the PCEP entity does not use the SyncTimer."; @@ -1958,9 +1958,9 @@ module ietf-pcep { error-message "The LSP must be PCE-Initiated"; } description - "If the role is PCC, this leaf refer to the PCEP + "If the role is PCC, this leaf refers to the PCEP peer (PCE) that initiated this LSP. If the role - is PCE, this leaf refer to the PCEP peer (PCC) + is PCE, this leaf refers to the PCEP peer (PCC) where the LSP is initiated"; } } @@ -2214,7 +2214,7 @@ module ietf-pcep { config false; description "Indicates whether the local PCEP entity initiates - sessions to this peer, or waits for the peer to + sessions to this peer, or wait for the peer to initiate a session."; } leaf session-exists { @@ -2265,7 +2265,7 @@ module ietf-pcep { leaf initiator { type initiator; description - "The initiator of the session,that is, whether + "The initiator of the session, that is, whether the TCP connection was initiated by the local PCEP entity or the peer. There is a window during session diff --git a/experimental/ietf-extracted-YANG-modules/ietf-rift@2023-07-05.yang b/experimental/ietf-extracted-YANG-modules/ietf-rift@2023-07-05.yang index 0d999879b..00290ba67 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-rift@2023-07-05.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-rift@2023-07-05.yang @@ -69,7 +69,6 @@ module ietf-rift { Editor: Bruno Rijsman "; - // RFC Ed.: replace XXXX with actual RFC number and remove // this note @@ -93,6 +92,7 @@ module ietf-rift { Copyright (c) 2022 IETF Trust and the persons identified as authors of the code. All rights reserved. + Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License diff --git a/experimental/ietf-extracted-YANG-modules/ietf-te-telemetry@2023-03-10.yang b/experimental/ietf-extracted-YANG-modules/ietf-te-telemetry@2023-09-11.yang similarity index 99% rename from experimental/ietf-extracted-YANG-modules/ietf-te-telemetry@2023-03-10.yang rename to experimental/ietf-extracted-YANG-modules/ietf-te-telemetry@2023-09-11.yang index d081713d9..27fae9ccd 100644 --- a/experimental/ietf-extracted-YANG-modules/ietf-te-telemetry@2023-03-10.yang +++ b/experimental/ietf-extracted-YANG-modules/ietf-te-telemetry@2023-09-11.yang @@ -57,7 +57,7 @@ module ietf-te-telemetry { assigned to the RFC once draft-ietf-teas-pm-telemetry- autonomics becomes an RFC.*/ - revision 2023-03-10 { + revision 2023-09-11 { description "Initial revision."; reference