rfc9314.original   rfc9314.txt 
Network Working Group M. Jethanandani, Ed. Internet Engineering Task Force (IETF) M. Jethanandani, Ed.
Internet-Draft Xoriant Corporation Request for Comments: 9314 Xoriant Corporation
Updates: 9127 (if approved) R. Rahman, Ed. Updates: 9127 R. Rahman, Ed.
Intended status: Standards Track Category: Standards Track
Expires: 8 October 2022 L. Zheng, Ed. ISSN: 2070-1721 L. Zheng, Ed.
Huawei Technologies Huawei Technologies
S. Pallagatti S. Pallagatti
VMware VMware
G. Mirsky G. Mirsky
Ericsson Ericsson
6 April 2022 September 2022
YANG Data Model for Bidirectional Forwarding Detection (BFD) YANG Data Model for Bidirectional Forwarding Detection (BFD)
draft-ietf-bfd-rfc9127-bis-04
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage Bidirectional Forwarding Detection (BFD). and manage Bidirectional Forwarding Detection (BFD).
The YANG modules in this document conform to the Network Management The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA) (RFC 8342). This document updates YANG Datastore Architecture (NMDA) (RFC 8342). This document updates
Data Model for Bidirectional Forwarding Detection (BFD) (RFC 9127). "YANG Data Model for Bidirectional Forwarding Detection (BFD)" (RFC
9127).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 8 October 2022. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9314.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction
1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Tree Diagrams
1.2. Note to RFC Editor . . . . . . . . . . . . . . . . . . . 4 2. Design of the Data Model
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 4 2.1. Design of the Configuration Model
2.1. Design of the Configuration Model . . . . . . . . . . . . 5 2.1.1. Common BFD Configuration Parameters
2.1.1. Common BFD Configuration Parameters . . . . . . . . . 6 2.1.2. Single-Hop IP
2.1.2. Single-Hop IP . . . . . . . . . . . . . . . . . . . . 7 2.1.3. Multihop IP
2.1.3. Multihop IP . . . . . . . . . . . . . . . . . . . . . 7 2.1.4. MPLS Label Switched Paths
2.1.4. MPLS Label Switched Paths . . . . . . . . . . . . . . 8 2.1.5. Link Aggregation Groups
2.1.5. Link Aggregation Groups . . . . . . . . . . . . . . . 8 2.2. Design of the Operational State Model
2.2. Design of the Operational State Model . . . . . . . . . . 8 2.3. Notifications
2.3. Notifications . . . . . . . . . . . . . . . . . . . . . . 9 2.4. RPC Operations
2.4. RPC Operations . . . . . . . . . . . . . . . . . . . . . 9 2.5. BFD Top-Level Hierarchy
2.5. BFD Top-Level Hierarchy . . . . . . . . . . . . . . . . . 9 2.6. BFD IP Single-Hop Hierarchy
2.6. BFD IP Single-Hop Hierarchy . . . . . . . . . . . . . . . 10 2.7. BFD IP Multihop Hierarchy
2.7. BFD IP Multihop Hierarchy . . . . . . . . . . . . . . . . 12 2.8. BFD-over-LAG Hierarchy
2.8. BFD-over-LAG Hierarchy . . . . . . . . . . . . . . . . . 14 2.9. BFD-over-MPLS-LSPs Hierarchy
2.9. BFD-over-MPLS-LSPs Hierarchy . . . . . . . . . . . . . . 17 2.10. Interaction with Other YANG Modules
2.10. Interaction with other YANG Modules . . . . . . . . . . . 19 2.10.1. "ietf-interfaces" Module
2.10.1. "ietf-interfaces" Module . . . . . . . . . . . . . . 19 2.10.2. "ietf-ip" Module
2.10.2. "ietf-ip" Module . . . . . . . . . . . . . . . . . . 20 2.10.3. "ietf-mpls" Module
2.10.3. "ietf-mpls" Module . . . . . . . . . . . . . . . . . 20 2.11. BFD Types YANG Module
2.11. BFD Types YANG Module . . . . . . . . . . . . . . . . . . 20 2.12. BFD Top-Level YANG Module
2.12. BFD Top-Level YANG Module . . . . . . . . . . . . . . . . 35 2.13. BFD IP Single-Hop YANG Module
2.13. BFD IP Single-Hop YANG Module . . . . . . . . . . . . . . 37 2.14. BFD IP Multihop YANG Module
2.14. BFD IP Multihop YANG Module . . . . . . . . . . . . . . . 40 2.15. BFD-over-LAG YANG Module
2.15. BFD-over-LAG YANG Module . . . . . . . . . . . . . . . . 44 2.16. BFD-over-MPLS YANG Module
2.16. BFD-over-MPLS YANG Module . . . . . . . . . . . . . . . . 48 3. Data Model Examples
3. Data Model Examples . . . . . . . . . . . . . . . . . . . . . 53 3.1. IP Single-Hop
3.1. IP Single-Hop . . . . . . . . . . . . . . . . . . . . . . 53 3.2. IP Multihop
3.2. IP Multihop . . . . . . . . . . . . . . . . . . . . . . . 54 3.3. LAG
3.3. LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.4. MPLS
3.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4. Security Considerations
4. Security Considerations . . . . . . . . . . . . . . . . . . . 57 5. IANA Considerations
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 6. References
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 62 6.1. Normative References
6.1. Normative References . . . . . . . . . . . . . . . . . . 62 6.2. Informative References
6.2. Informative References . . . . . . . . . . . . . . . . . 65 Appendix A. Echo Function Configuration Example
Appendix A. Echo Function Configuration Example . . . . . . . . 66 A.1. Example YANG Module for BFD Echo Function Configuration
A.1. Example YANG Module for BFD Echo Function Appendix B. Updates since RFC 9127
Configuration . . . . . . . . . . . . . . . . . . . . . . 66 Acknowledgments
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 68 Authors' Addresses
Updates since RFC 9127 . . . . . . . . . . . . . . . . . . . . . 68
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69
1. Introduction 1. Introduction
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage Bidirectional Forwarding Detection (BFD) [RFC5880]. BFD and manage Bidirectional Forwarding Detection (BFD) [RFC5880]. BFD
is a network protocol that is used for liveness detection of is a network protocol that is used for liveness detection of
arbitrary paths between systems. Some examples of different types of arbitrary paths between systems. Some examples of different types of
paths over which we have BFD are as follows: paths over which we have BFD are as follows:
1. Two systems directly connected via IP. This is known as BFD over 1. Two systems directly connected via IP. This is known as BFD over
single-hop IP, a.k.a. BFD for IPv4 and IPv6 [RFC5881]. single-hop IP, which is also known as BFD for IPv4 and IPv6
[RFC5881].
2. Two systems connected via multiple hops as described in 2. Two systems connected via multiple hops as described in
"Bidirectional Forwarding Detection (BFD) for Multihop Paths" "Bidirectional Forwarding Detection (BFD) for Multihop Paths"
[RFC5883]. [RFC5883].
3. Two systems connected via MPLS Label Switched Paths (LSPs) as 3. Two systems connected via MPLS Label Switched Paths (LSPs) as
described in "Bidirectional Forwarding Detection (BFD) for MPLS described in "Bidirectional Forwarding Detection (BFD) for MPLS
Label Switched Paths (LSPs)" [RFC5884]. Label Switched Paths (LSPs)" [RFC5884].
4. Two systems connected via a Link Aggregation Group (LAG) 4. Two systems connected via a Link Aggregation Group (LAG)
interface as described in "Bidirectional Forwarding Detection interface as described in "Bidirectional Forwarding Detection
(BFD) on Link Aggregation Group (LAG) Interfaces" [RFC7130]. (BFD) on Link Aggregation Group (LAG) Interfaces" [RFC7130].
5. Two systems connected via pseudowires (PWs). This is known as 5. Two systems connected via pseudowires (PWs). This is known as
Virtual Circuit Connectivity Verification (VCCV), as described in Virtual Circuit Connectivity Verification (VCCV) as described in
"Bidirectional Forwarding Detection (BFD) for the Pseudowire "Bidirectional Forwarding Detection (BFD) for the Pseudowire
Virtual Circuit Connectivity Verification (VCCV)" [RFC5885]. Virtual Circuit Connectivity Verification (VCCV)" [RFC5885].
This scenario is not addressed in this document. This scenario is not addressed in this document.
BFD typically does not operate on its own. Various control BFD typically does not operate on its own. Various control
protocols, also known as BFD clients, use the services provided by protocols, also known as BFD clients, use the services provided by
BFD for their own operation, as described in "Generic Application of BFD for their own operation, as described in "Generic Application of
Bidirectional Forwarding Detection (BFD)" [RFC5882]. The obvious Bidirectional Forwarding Detection (BFD)" [RFC5882]. The obvious
candidates that use BFD are those that do not have "hellos" to detect candidates that use BFD are those that do not have "hellos" to detect
failures, e.g., static routes, and routing protocols whose "hellos" failures, e.g., static routes, and routing protocols whose "hellos"
skipping to change at page 4, line 15 skipping to change at line 148
The YANG modules in this document conform to the Network Management The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA) [RFC8342]. This means that the data Datastore Architecture (NMDA) [RFC8342]. This means that the data
models do not have separate top-level or sibling containers for models do not have separate top-level or sibling containers for
configuration data and operational state data. configuration data and operational state data.
1.1. Tree Diagrams 1.1. Tree Diagrams
This document uses the graphical representation of data models, as This document uses the graphical representation of data models, as
defined in [RFC8340]. defined in [RFC8340].
1.2. Note to RFC Editor
This section is to be removed before publishing as an RFC.
This document uses several placeholder values throughout the
document. Please replace them as follows and remove this note before
publication.
RFC XXXX, where XXXX is the number assigned to this document at the
time of publication.
2022-04-06 with the actual date of the publication of this document.
2. Design of the Data Model 2. Design of the Data Model
Since BFD is used for liveness detection of various forwarding paths, Since BFD is used for liveness detection of various forwarding paths,
there is no uniform key to identify a BFD session, and so the BFD there is no uniform key to identify a BFD session. Therefore, the
data model is split into multiple YANG modules where each module BFD data model is split into multiple YANG modules where each module
corresponds to one type of forwarding path. For example, BFD for IP corresponds to one type of forwarding path. For example, BFD for IP
single-hop is in one YANG module, and BFD for MPLS is in another YANG single-hop is in one YANG module, and BFD for MPLS is in another YANG
module. The main difference between these modules is how a BFD module. The main difference between these modules is how a BFD
session is uniquely identified, i.e., the key for the list containing session is uniquely identified, i.e., the key for the list containing
the BFD sessions for that forwarding path. To avoid duplication of the BFD sessions for that forwarding path. To avoid duplication of
BFD definitions, we have common types and groupings that are used by BFD definitions, we have common types and groupings that are used by
all the modules. all the modules.
A new control-plane protocol, "bfdv1", is defined, and a "bfd" A new control plane protocol, "bfdv1", is defined, and a "bfd"
container is created under "control-plane-protocol" as specified in container is created under "control-plane-protocol" as specified in
"A YANG Data Model for Routing Management (NMDA Version)" [RFC8349]. "A YANG Data Model for Routing Management (NMDA Version)" [RFC8349].
This new "bfd" container is augmented by the following YANG modules This new "bfd" container is augmented by the following YANG modules
for their respective specific information: for their respective specific information:
1. The "ietf-bfd-ip-sh" module (Section 2.13) augments "/routing/ 1. The "ietf-bfd-ip-sh" module (Section 2.13) augments "/routing/
control-plane-protocols/control-plane-protocol/bfd/" with the control-plane-protocols/control-plane-protocol/bfd/" with the
"ip-sh" container for BFD sessions over IP single-hop. "ip-sh" container for BFD sessions over IP single-hop.
2. The "ietf-bfd-ip-mh" module (Section 2.14) augments "/routing/ 2. The "ietf-bfd-ip-mh" module (Section 2.14) augments "/routing/
skipping to change at page 5, line 19 skipping to change at line 185
3. The "ietf-bfd-lag" module (Section 2.15) augments "/routing/ 3. The "ietf-bfd-lag" module (Section 2.15) augments "/routing/
control-plane-protocols/control-plane-protocol/bfd/" with the control-plane-protocols/control-plane-protocol/bfd/" with the
"lag" container for BFD sessions over a LAG. "lag" container for BFD sessions over a LAG.
4. The "ietf-bfd-mpls" module (Section 2.16) augments "/routing/ 4. The "ietf-bfd-mpls" module (Section 2.16) augments "/routing/
control-plane-protocols/control-plane-protocol/bfd/" with the control-plane-protocols/control-plane-protocol/bfd/" with the
"mpls" container for BFD-over-MPLS LSPs. "mpls" container for BFD-over-MPLS LSPs.
BFD can operate in the following contexts: BFD can operate in the following contexts:
1. At the network device level. 1. At the network-device level.
2. In logical network elements (LNEs) as described in "YANG Model 2. In logical network elements (LNEs) as described in "YANG Model
for Logical Network Elements" [RFC8530]. for Logical Network Elements" [RFC8530].
3. In network instances as described in "YANG Data Model for Network 3. In network instances as described in "YANG Data Model for Network
Instances" [RFC8529]. Instances" [RFC8529].
When used at the network device level, the BFD YANG data model is When used at the network device level, the BFD YANG data model is
used "as is". When the BFD YANG data model is used in an LNE or used "as is". When the BFD YANG data model is used in an LNE or
network instance, the BFD YANG data model augments the mounted network instance, the BFD YANG data model augments the mounted
skipping to change at page 19, line 30 skipping to change at line 861
+--ro remote-discr? discriminator +--ro remote-discr? discriminator
+--ro new-state? state +--ro new-state? state
+--ro state-change-reason? iana-bfd-types:diagnostic +--ro state-change-reason? iana-bfd-types:diagnostic
+--ro time-of-last-state-change? yang:date-and-time +--ro time-of-last-state-change? yang:date-and-time
+--ro dest-addr? inet:ip-address +--ro dest-addr? inet:ip-address
+--ro source-addr? inet:ip-address +--ro source-addr? inet:ip-address
+--ro session-index? uint32 +--ro session-index? uint32
+--ro path-type? identityref +--ro path-type? identityref
+--ro mpls-dest-address? inet:ip-address +--ro mpls-dest-address? inet:ip-address
2.10. Interaction with other YANG Modules 2.10. Interaction with Other YANG Modules
"Generic YANG Data Model for the Management of Operations, "Generic YANG Data Model for the Management of Operations,
Administration, and Maintenance (OAM) Protocols That Use Administration, and Maintenance (OAM) Protocols That Use
Connectionless Communications" [RFC8532] describes how the Layer- Connectionless Communications" [RFC8532] describes how the Layer-
Independent OAM Management in the Multi-Layer Environment (LIME) Independent OAM Management in the Multi-Layer Environment (LIME)
connectionless OAM model could be extended to support BFD. connectionless OAM model could be extended to support BFD.
Also, the operation of the BFD data model depends on configuration Also, the operation of the BFD data model depends on configuration
parameters that are defined in other YANG modules. parameters that are defined in other YANG modules.
skipping to change at page 20, line 31 skipping to change at line 907
/if:interfaces/if:interface/ip:ipv6/ip:forwarding /if:interfaces/if:interface/ip:ipv6/ip:forwarding
If this configuration is set to "false", no BFD IPv6 packets can If this configuration is set to "false", no BFD IPv6 packets can
be transmitted or received on that interface. be transmitted or received on that interface.
2.10.3. "ietf-mpls" Module 2.10.3. "ietf-mpls" Module
The following boolean configuration is defined in "A YANG Data Model The following boolean configuration is defined in "A YANG Data Model
for MPLS Base" [RFC8960]: for MPLS Base" [RFC8960]:
/rt:routing/mpls:mpls/mpls:interfaces/mpls:interface/ /rt:routing/mpls:mpls/mpls:interfaces/mpls:interface/mpls:mpls-
mpls:mpls-enabled enabled
If this configuration is set to "false", no BFD MPLS packets can If this configuration is set to "false", no BFD MPLS packets can
be transmitted or received on that interface. be transmitted or received on that interface.
2.11. BFD Types YANG Module 2.11. BFD Types YANG Module
This YANG module imports typedefs from [RFC6991] and [RFC8177]. It This YANG module imports typedefs from [RFC6991] and [RFC8177]. It
also imports definitions from [RFC5880], [RFC5881], [RFC5883], also imports definitions from [RFC5880], [RFC5881], [RFC5883],
[RFC5884], and [RFC7130], as well as the "control-plane-protocol" [RFC5884], and [RFC7130], as well as the "control-plane-protocol"
identity from [RFC8349], and references [RFC9127]. identity from [RFC8349], and references [RFC9127].
<CODE BEGINS> file "ietf-bfd-types@2022-04-06.yang" <CODE BEGINS> file "ietf-bfd-types@2022-09-22.yang"
module ietf-bfd-types { module ietf-bfd-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-types";
prefix bfd-types; prefix bfd-types;
import iana-bfd-types { import iana-bfd-types {
prefix iana-bfd-types; prefix iana-bfd-types;
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
skipping to change at page 21, line 48 skipping to change at line 972
Editor: Lianshu Zheng Editor: Lianshu Zheng
<mailto:veronique_cheng@hotmail.com> <mailto:veronique_cheng@hotmail.com>
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>"; <mailto:mjethanandani@gmail.com>";
description description
"This module contains a collection of BFD-specific YANG data type "This module contains a collection of BFD-specific YANG data type
definitions, as per RFC 5880, and also groupings that are common definitions, as per RFC 5880, and also groupings that are common
to other BFD YANG modules. to other BFD YANG modules.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject
the license terms contained in, the Simplified BSD License set to the license terms contained in, the Revised BSD License
forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9314; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
reference reference
"RFC 5880: Bidirectional Forwarding Detection (BFD) "RFC 5880: Bidirectional Forwarding Detection (BFD)
RFC XXXX: YANG Data Model for Bidirectional Forwarding RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-04-06 { revision 2022-09-22 {
description description
"This revision is not backwards compatible with the "This revision is not backwards compatible with the
previous version of this model. previous version of this model.
This revision adds an 'if-feature' statement called This revision adds an 'if-feature' statement called
'client-base-cfg-parms' for client configuration parameters. 'client-base-cfg-parms' for client configuration parameters.
Clients expecting to use those parameters now need to Clients expecting to use those parameters now need to
verify that the server declares support of the feature verify that the server declares support of the feature
before depending on the presence of the parameters. before depending on the presence of the parameters.
The change was introduced for clients that do not need The change was introduced for clients that do not need
them, and have to deviate to prevent them from being them and have to deviate to prevent them from being
included."; included.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
revision 2021-10-21 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
skipping to change at page 23, line 39 skipping to change at line 1058
reference reference
"RFC 5880: Bidirectional Forwarding Detection (BFD), "RFC 5880: Bidirectional Forwarding Detection (BFD),
Section 6.4"; Section 6.4";
} }
feature client-base-cfg-parms { feature client-base-cfg-parms {
description description
"This feature allows protocol models to configure BFD client "This feature allows protocol models to configure BFD client
session parameters."; session parameters.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
/* /*
* Identity definitions * Identity definitions
*/ */
identity bfdv1 { identity bfdv1 {
base rt:control-plane-protocol; base rt:control-plane-protocol;
description description
skipping to change at page 35, line 4 skipping to change at line 1600
} }
leaf source-addr { leaf source-addr {
type inet:ip-address; type inet:ip-address;
description description
"BFD local address."; "BFD local address.";
} }
leaf session-index { leaf session-index {
type uint32; type uint32;
description description
"An index used to uniquely identify BFD sessions."; "An index used to uniquely identify BFD sessions.";
} }
leaf path-type { leaf path-type {
type identityref { type identityref {
base path-type; base path-type;
} }
description description
"BFD path type."; "BFD path type.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
2.12. BFD Top-Level YANG Module 2.12. BFD Top-Level YANG Module
This YANG module imports and augments "/routing/control-plane- This YANG module imports and augments "/routing/control-plane-
protocols/control-plane-protocol" from [RFC8349]. It also references protocols/control-plane-protocol" from [RFC8349]. It also references
[RFC5880]. [RFC5880].
<CODE BEGINS> file "ietf-bfd@2022-04-06.yang" <CODE BEGINS> file "ietf-bfd@2022-09-22.yang"
module ietf-bfd { module ietf-bfd {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd";
prefix bfd; prefix bfd;
import ietf-bfd-types { import ietf-bfd-types {
prefix bfd-types; prefix bfd-types;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-routing { import ietf-routing {
prefix rt; prefix rt;
reference reference
"RFC 8349: A YANG Data Model for Routing Management "RFC 8349: A YANG Data Model for Routing Management
(NMDA Version)"; (NMDA Version)";
} }
organization organization
skipping to change at page 36, line 12 skipping to change at line 1655
Editor: Lianshu Zheng Editor: Lianshu Zheng
<mailto:veronique_cheng@hotmail.com> <mailto:veronique_cheng@hotmail.com>
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>"; <mailto:mjethanandani@gmail.com>";
description description
"This module contains the YANG definition for BFD parameters as "This module contains the YANG definition for BFD parameters as
per RFC 5880. per RFC 5880.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject
the license terms contained in, the Revised BSD License set to the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9314; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
reference reference
"RFC 5880: Bidirectional Forwarding Detection (BFD) "RFC 5880: Bidirectional Forwarding Detection (BFD)
RFC XXXX: YANG Data Model for Bidirectional Forwarding RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-04-06 { revision 2022-09-22 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC 9314.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
revision 2021-10-21 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" { + "rt:control-plane-protocol" {
when "derived-from-or-self(rt:type, 'bfd-types:bfdv1')" { when "derived-from-or-self(rt:type, 'bfd-types:bfdv1')" {
description description
"This augmentation is only valid for a control-plane protocol "This augmentation is only valid for a control plane protocol
instance of BFD (type 'bfdv1')."; instance of BFD (type 'bfdv1').";
} }
description description
"BFD augmentation."; "BFD augmentation.";
container bfd { container bfd {
description description
"BFD top-level container."; "BFD top-level container.";
uses bfd-types:session-statistics-summary; uses bfd-types:session-statistics-summary;
} }
} }
} }
<CODE ENDS> <CODE ENDS>
2.13. BFD IP Single-Hop YANG Module 2.13. BFD IP Single-Hop YANG Module
This YANG module imports "interface-ref" from [RFC8343] and typedefs This YANG module imports "interface-ref" from [RFC8343] and typedefs
from [RFC6991]. It also imports and augments "/routing/control- from [RFC6991]. It also imports and augments "/routing/control-
plane-protocols/control-plane-protocol" from [RFC8349], and it plane-protocols/control-plane-protocol" from [RFC8349], and it
references [RFC5881]. references [RFC5881].
<CODE BEGINS> file "ietf-bfd-ip-sh@2022-04-06.yang" <CODE BEGINS> file "ietf-bfd-ip-sh@2022-09-22.yang"
module ietf-bfd-ip-sh { module ietf-bfd-ip-sh {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh";
prefix bfd-ip-sh; prefix bfd-ip-sh;
import ietf-bfd-types { import ietf-bfd-types {
prefix bfd-types; prefix bfd-types;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-bfd { import ietf-bfd {
prefix bfd; prefix bfd;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"RFC 8343: A YANG Data Model for Interface Management"; "RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
skipping to change at page 38, line 27 skipping to change at line 1765
Editor: Lianshu Zheng Editor: Lianshu Zheng
<mailto:veronique_cheng@hotmail.com> <mailto:veronique_cheng@hotmail.com>
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>"; <mailto:mjethanandani@gmail.com>";
description description
"This module contains the YANG definition for BFD IP single-hop "This module contains the YANG definition for BFD IP single-hop
as per RFC 5881. as per RFC 5881.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject
the license terms contained in, the Revised BSD License set to the license terms contained in, the Revised BSD License
forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9314; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
reference reference
"RFC 5881: Bidirectional Forwarding Detection (BFD) "RFC 5881: Bidirectional Forwarding Detection (BFD)
for IPv4 and IPv6 (Single Hop) for IPv4 and IPv6 (Single Hop)
RFC XXXX: YANG Data Model for Bidirectional Forwarding RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-04-06 { revision 2022-09-22 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC 9314.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
revision 2021-10-21 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
skipping to change at page 41, line 5 skipping to change at line 1880
} }
} }
<CODE ENDS> <CODE ENDS>
2.14. BFD IP Multihop YANG Module 2.14. BFD IP Multihop YANG Module
This YANG module imports typedefs from [RFC6991]. It also imports This YANG module imports typedefs from [RFC6991]. It also imports
and augments "/routing/control-plane-protocols/control-plane- and augments "/routing/control-plane-protocols/control-plane-
protocol" from [RFC8349], and it references [RFC5883]. protocol" from [RFC8349], and it references [RFC5883].
<CODE BEGINS> file "ietf-bfd-ip-mh@2022-04-06.yang" <CODE BEGINS> file "ietf-bfd-ip-mh@2022-09-22.yang"
module ietf-bfd-ip-mh { module ietf-bfd-ip-mh {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh";
prefix bfd-ip-mh; prefix bfd-ip-mh;
import ietf-bfd-types { import ietf-bfd-types {
prefix bfd-types; prefix bfd-types;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-bfd { import ietf-bfd {
prefix bfd; prefix bfd;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix rt; prefix rt;
reference reference
skipping to change at page 42, line 5 skipping to change at line 1928
Editor: Lianshu Zheng Editor: Lianshu Zheng
<mailto:veronique_cheng@hotmail.com> <mailto:veronique_cheng@hotmail.com>
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>"; <mailto:mjethanandani@gmail.com>";
description description
"This module contains the YANG definition for BFD IP multihop "This module contains the YANG definition for BFD IP multihop
as per RFC 5883. as per RFC 5883.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Revised BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9314; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
reference reference
"RFC 5883: Bidirectional Forwarding Detection (BFD) for "RFC 5883: Bidirectional Forwarding Detection (BFD) for
Multihop Paths Multihop Paths
RFC XXXX: YANG Data Model for Bidirectional Forwarding RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-04-06 { revision 2022-09-22 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC 9314.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
revision 2021-10-21 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
skipping to change at page 44, line 22 skipping to change at line 2041
} }
<CODE ENDS> <CODE ENDS>
2.15. BFD-over-LAG YANG Module 2.15. BFD-over-LAG YANG Module
This YANG module imports "interface-ref" from [RFC8343] and typedefs This YANG module imports "interface-ref" from [RFC8343] and typedefs
from [RFC6991]. It also imports and augments "/routing/control- from [RFC6991]. It also imports and augments "/routing/control-
plane-protocols/control-plane-protocol" from [RFC8349]. plane-protocols/control-plane-protocol" from [RFC8349].
Additionally, it references [RFC7130]. Additionally, it references [RFC7130].
<CODE BEGINS> file "ietf-bfd-lag@2022-04-06.yang" <CODE BEGINS> file "ietf-bfd-lag@2022-09-22.yang"
module ietf-bfd-lag { module ietf-bfd-lag {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-lag"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-lag";
prefix bfd-lag; prefix bfd-lag;
import ietf-bfd-types { import ietf-bfd-types {
prefix bfd-types; prefix bfd-types;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-bfd { import ietf-bfd {
prefix bfd; prefix bfd;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"RFC 8343: A YANG Data Model for Interface Management"; "RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
skipping to change at page 45, line 27 skipping to change at line 2094
Editor: Lianshu Zheng Editor: Lianshu Zheng
<mailto:veronique_cheng@hotmail.com> <mailto:veronique_cheng@hotmail.com>
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>"; <mailto:mjethanandani@gmail.com>";
description description
"This module contains the YANG definition for BFD-over-LAG "This module contains the YANG definition for BFD-over-LAG
interfaces as per RFC 7130. interfaces as per RFC 7130.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject
the license terms contained in, the Revised BSD License set to the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9314; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
reference reference
"RFC 7130: Bidirectional Forwarding Detection (BFD) on "RFC 7130: Bidirectional Forwarding Detection (BFD) on
Link Aggregation Group (LAG) Interfaces Link Aggregation Group (LAG) Interfaces
RFC XXXX: YANG Data Model for Bidirectional Forwarding RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-04-06 { revision 2022-09-22 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC 9314.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
revision 2021-10-21 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
skipping to change at page 48, line 35 skipping to change at line 2247
} }
<CODE ENDS> <CODE ENDS>
2.16. BFD-over-MPLS YANG Module 2.16. BFD-over-MPLS YANG Module
This YANG module imports typedefs from [RFC6991]. It also imports This YANG module imports typedefs from [RFC6991]. It also imports
and augments "/routing/control-plane-protocols/control-plane- and augments "/routing/control-plane-protocols/control-plane-
protocol" from [RFC8349]. Additionally, it references [RFC5586] and protocol" from [RFC8349]. Additionally, it references [RFC5586] and
[RFC5884]. [RFC5884].
<CODE BEGINS> file "ietf-bfd-mpls@2022-04-06.yang" <CODE BEGINS> file "ietf-bfd-mpls@2022-09-22.yang"
module ietf-bfd-mpls { module ietf-bfd-mpls {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls";
prefix bfd-mpls; prefix bfd-mpls;
import ietf-bfd-types { import ietf-bfd-types {
prefix bfd-types; prefix bfd-types;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-bfd { import ietf-bfd {
prefix bfd; prefix bfd;
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix rt; prefix rt;
reference reference
skipping to change at page 49, line 36 skipping to change at line 2295
Editor: Lianshu Zheng Editor: Lianshu Zheng
<mailto:veronique_cheng@hotmail.com> <mailto:veronique_cheng@hotmail.com>
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>"; <mailto:mjethanandani@gmail.com>";
description description
"This module contains the YANG definition for BFD parameters for "This module contains the YANG definition for BFD parameters for
MPLS LSPs as per RFC 5884. MPLS LSPs as per RFC 5884.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject
the license terms contained in, the Revised BSD License set to the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9314; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
reference reference
"RFC 5884: Bidirectional Forwarding Detection (BFD) "RFC 5884: Bidirectional Forwarding Detection (BFD)
for MPLS Label Switched Paths (LSPs) for MPLS Label Switched Paths (LSPs)
RFC XXXX: YANG Data Model for Bidirectional Forwarding RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-04-06 { revision 2022-09-22 {
description description
"Updates to use base-cfg-parms instead of client-cfg-parms, "Updates to use base-cfg-parms instead of client-cfg-parms,
and add the enabled flag."; and add the enabled flag.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC 9314: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
revision 2021-10-21 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
/* /*
* Identity definitions * Identity definitions
*/ */
identity encap-gach { identity encap-gach {
base bfd-types:encap-type; base bfd-types:encap-type;
description description
"BFD with G-ACh encapsulation as per RFC 5586."; "BFD with Generic Associated Channel (G-ACh) encapsulation
as per RFC 5586.";
reference reference
"RFC 5586: MPLS Generic Associated Channel"; "RFC 5586: MPLS Generic Associated Channel";
} }
identity encap-ip-gach { identity encap-ip-gach {
base bfd-types:encap-type; base bfd-types:encap-type;
description description
"BFD with IP and G-ACh encapsulation as per RFC 5586."; "BFD with IP and G-ACh encapsulation as per RFC 5586.";
} }
skipping to change at page 61, line 31 skipping to change at line 2804
session-groups/session-group/sessions: session-groups/session-group/sessions:
Access to data nodes "local-discriminator" and "remote- Access to data nodes "local-discriminator" and "remote-
discriminator" (combined with the data nodes in the session discriminator" (combined with the data nodes in the session
group's authentication container) provides the ability to spoof group's authentication container) provides the ability to spoof
BFD-over-MPLS-LSPs packets. BFD-over-MPLS-LSPs packets.
This document does not define any RPC operations. This document does not define any RPC operations.
5. IANA Considerations 5. IANA Considerations
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the "IETF XML
in the "IETF XML Registry" [RFC3688]: Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-bfd-types URI: urn:ietf:params:xml:ns:yang:ietf-bfd-types
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-bfd URI: urn:ietf:params:xml:ns:yang:ietf-bfd
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh URI: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh
skipping to change at page 62, line 15 skipping to change at line 2837
URI: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls URI: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document registers the following YANG modules in the "YANG This document registers the following YANG modules in the "YANG
Module Names" registry [RFC6020]: Module Names" registry [RFC6020]:
Name: ietf-bfd-types Name: ietf-bfd-types
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-types Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-types
Prefix: bfd-types Prefix: bfd-types
Reference: RFC XXXX Reference: RFC 9314
Name: ietf-bfd Name: ietf-bfd
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd
Prefix: bfd Prefix: bfd
Reference: RFC XXXX Reference: RFC 9314
Name: ietf-bfd-ip-sh Name: ietf-bfd-ip-sh
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh
Prefix: bfd-ip-sh Prefix: bfd-ip-sh
Reference: RFC XXXX Reference: RFC 9314
Name: ietf-bfd-ip-mh Name: ietf-bfd-ip-mh
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh
Prefix: bfd-ip-mh Prefix: bfd-ip-mh
Reference: RFC XXXX Reference: RFC 9314
Name: ietf-bfd-lag Name: ietf-bfd-lag
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-lag Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-lag
Prefix: bfd-lag Prefix: bfd-lag
Reference: RFC XXXX Reference: RFC 9314
Name: ietf-bfd-mpls Name: ietf-bfd-mpls
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls
Prefix: bfd-mpls Prefix: bfd-mpls
Reference: RFC XXXX Reference: RFC 9314
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5586] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed., [RFC5586] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed.,
skipping to change at page 65, line 10 skipping to change at line 2970
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC8960] Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A [RFC8960] Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A
YANG Data Model for MPLS Base", RFC 8960, YANG Data Model for MPLS Base", RFC 8960,
DOI 10.17487/RFC8960, December 2020, DOI 10.17487/RFC8960, December 2020,
<https://www.rfc-editor.org/info/rfc8960>. <https://www.rfc-editor.org/info/rfc8960>.
[RFC9127] Rahman, R., Zheng, L., Jethanandani, M., Pallagatti, S., [RFC9127] Rahman, R., Ed., Zheng, L., Ed., Jethanandani, M., Ed.,
and G. Mirsky, "YANG Data Model for Bidirectional Pallagatti, S., and G. Mirsky, "YANG Data Model for
Forwarding Detection (BFD)", RFC 9127, Bidirectional Forwarding Detection (BFD)", RFC 9127,
DOI 10.17487/RFC9127, October 2021, DOI 10.17487/RFC9127, October 2021,
<https://www.rfc-editor.org/info/rfc9127>. <https://www.rfc-editor.org/info/rfc9127>.
6.2. Informative References 6.2. Informative References
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, Label Switching Architecture", RFC 3031,
DOI 10.17487/RFC3031, January 2001, DOI 10.17487/RFC3031, January 2001,
<https://www.rfc-editor.org/info/rfc3031>. <https://www.rfc-editor.org/info/rfc3031>.
skipping to change at page 67, line 18 skipping to change at line 3073
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
<mailto:mjethanandani@gmail.com>"; <mailto:mjethanandani@gmail.com>";
description description
"This module contains an example YANG augmentation for "This module contains an example YANG augmentation for
configuration of the BFD Echo function. configuration of the BFD Echo function.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2021 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject
the license terms contained in, the Revised BSD License set to the license terms contained in, the Revised BSD License
forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 9127; see the This version of this YANG module is part of RFC 9127; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2021-09-03 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding "RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
} }
/* /*
* Groupings * Groupings
*/ */
skipping to change at page 68, line 27 skipping to change at line 3131
"Augmentation for the BFD Echo function."; "Augmentation for the BFD Echo function.";
container echo { container echo {
if-feature "bfd-types:echo-mode"; if-feature "bfd-types:echo-mode";
description description
"BFD Echo function container."; "BFD Echo function container.";
uses echo-cfg-parms; uses echo-cfg-parms;
} }
} }
} }
Acknowledgments Appendix B. Updates since RFC 9127
We would like to thank Nobo Akiya and Jeff Haas for their
encouragement on this work. We would also like to thank Tom Petch
for his comments on the document. We would also like to thank Acee
Lindem for his guidance. Thanks also to Jürgen Schönwälder, who was
instrumental in improving the YANG modules.
Updates since RFC 9127
This version of the draft updates the 'ietf-bfd-types' module to This document updates the 'ietf-bfd-types' module to define a new
define a new feature called 'client-base-cfg-parms and a 'if-feature' feature called 'client-base-cfg-parms and an 'if-feature' statement
statement that conditionally includes definition of parameters such that conditionally includes definitions of parameters, such as
as 'multiplier' or 'desired-min-tx-interval'. The feature statement 'multiplier' or 'desired-min-tx-interval'. The feature statement
allows YANG implementations of protocol such as OSPF, ISIS, PIM and allows YANG implementations of protocols, such as OSPF, IS-IS, PIM,
BGP, to support both a model where such parameters are not needed, and BGP, to support both a model where such parameters are not
such as when multiple BFD sessions are supported over a given needed, such as when multiple BFD sessions are supported over a given
interface, as well as when they need to be defined per session. As a interface, as well as when they need to be defined per session. As a
result, the BFD MPLS module has to use the base-cfg-parms instead of result, the BFD MPLS module has to use the base-cfg-parms instead of
client-cfg-parms to be able to include all the parameters client-cfg-parms to be able to include all the parameters
unconditionally. unconditionally.
The iana-bfd-types module, created in RFC 9127, was delegated to IANA The iana-bfd-types module, created in RFC 9127, was delegated to IANA
for maintenance. No changes are requested from IANA as part of this for maintenance. No changes are requested from IANA as part of this
update. update.
Acknowledgments
We would like to thank Nobo Akiya and Jeff Haas for their
encouragement on this work. We would also like to thank Tom Petch
for his comments on the document. We would also like to thank Acee
Lindem for his guidance. Thanks also to Jürgen Schönwälder, who was
instrumental in improving the YANG modules.
Authors' Addresses Authors' Addresses
Mahesh Jethanandani (editor) Mahesh Jethanandani (editor)
Xoriant Corporation Xoriant Corporation
1248 Reamwood Ave 1248 Reamwood Ave
Sunnyvale, California 94089 Sunnyvale, CA 94089
United States of America United States of America
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
Reshad Rahman (editor) Reshad Rahman (editor)
Canada Canada
Email: reshad@yahoo.com Email: reshad@yahoo.com
Lianshu Zheng (editor) Lianshu Zheng (editor)
Huawei Technologies Huawei Technologies
China China
 End of changes. 90 change blocks. 
192 lines changed or deleted 176 lines changed or added

This html diff was produced by rfcdiff 1.48.