< draft-ietf-bfd-rfc9127-bis-02.txt   draft-ietf-bfd-rfc9127-bis-03.txt >
Network Working Group M. Jethanandani, Ed. Network Working Group M. Jethanandani, Ed.
Internet-Draft Xoriant Corporation Internet-Draft Xoriant Corporation
Updates: 9127 (if approved) R. Rahman, Ed. Updates: 9127 (if approved) R. Rahman, Ed.
Intended status: Standards Track Intended status: Standards Track
Expires: 15 August 2022 L. Zheng, Ed. Expires: 8 October 2022 L. Zheng, Ed.
Huawei Technologies Huawei Technologies
S. Pallagatti S. Pallagatti
VMware VMware
G. Mirsky G. Mirsky
Ericsson Ericsson
11 February 2022 6 April 2022
YANG Data Model for Bidirectional Forwarding Detection (BFD) YANG Data Model for Bidirectional Forwarding Detection (BFD)
draft-ietf-bfd-rfc9127-bis-02 draft-ietf-bfd-rfc9127-bis-03
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 YANG
Data Model for Bidirectional Forwarding Detection (BFD) (RFC 9127). Data Model for Bidirectional Forwarding Detection (BFD) (RFC 9127).
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 15 August 2022. This Internet-Draft will expire on 8 October 2022.
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 (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Note to RFC Editor . . . . . . . . . . . . . . . . . . . 4
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 4 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 4
2.1. Design of the Configuration Model . . . . . . . . . . . . 5 2.1. Design of the Configuration Model . . . . . . . . . . . . 5
2.1.1. Common BFD Configuration Parameters . . . . . . . . . 6 2.1.1. Common BFD Configuration Parameters . . . . . . . . . 6
2.1.2. Single-Hop IP . . . . . . . . . . . . . . . . . . . . 6 2.1.2. Single-Hop IP . . . . . . . . . . . . . . . . . . . . 7
2.1.3. Multihop IP . . . . . . . . . . . . . . . . . . . . . 7 2.1.3. Multihop IP . . . . . . . . . . . . . . . . . . . . . 7
2.1.4. MPLS Label Switched Paths . . . . . . . . . . . . . . 7 2.1.4. MPLS Label Switched Paths . . . . . . . . . . . . . . 8
2.1.5. Link Aggregation Groups . . . . . . . . . . . . . . . 8 2.1.5. Link Aggregation Groups . . . . . . . . . . . . . . . 8
2.2. Design of the Operational State Model . . . . . . . . . . 8 2.2. Design of the Operational State Model . . . . . . . . . . 8
2.3. Notifications . . . . . . . . . . . . . . . . . . . . . . 9 2.3. Notifications . . . . . . . . . . . . . . . . . . . . . . 9
2.4. RPC Operations . . . . . . . . . . . . . . . . . . . . . 9 2.4. RPC Operations . . . . . . . . . . . . . . . . . . . . . 9
2.5. BFD Top-Level Hierarchy . . . . . . . . . . . . . . . . . 9 2.5. BFD Top-Level Hierarchy . . . . . . . . . . . . . . . . . 9
2.6. BFD IP Single-Hop Hierarchy . . . . . . . . . . . . . . . 9 2.6. BFD IP Single-Hop Hierarchy . . . . . . . . . . . . . . . 10
2.7. BFD IP Multihop Hierarchy . . . . . . . . . . . . . . . . 11 2.7. BFD IP Multihop Hierarchy . . . . . . . . . . . . . . . . 12
2.8. BFD-over-LAG Hierarchy . . . . . . . . . . . . . . . . . 13 2.8. BFD-over-LAG Hierarchy . . . . . . . . . . . . . . . . . 14
2.9. BFD-over-MPLS-LSPs Hierarchy . . . . . . . . . . . . . . 16 2.9. BFD-over-MPLS-LSPs Hierarchy . . . . . . . . . . . . . . 17
2.10. Interaction with other YANG Modules . . . . . . . . . . . 19 2.10. Interaction with other YANG Modules . . . . . . . . . . . 19
2.10.1. "ietf-interfaces" Module . . . . . . . . . . . . . . 19 2.10.1. "ietf-interfaces" Module . . . . . . . . . . . . . . 19
2.10.2. "ietf-ip" Module . . . . . . . . . . . . . . . . . . 19 2.10.2. "ietf-ip" Module . . . . . . . . . . . . . . . . . . 20
2.10.3. "ietf-mpls" Module . . . . . . . . . . . . . . . . . 19 2.10.3. "ietf-mpls" Module . . . . . . . . . . . . . . . . . 20
2.11. BFD Types YANG Module . . . . . . . . . . . . . . . . . . 20 2.11. BFD Types YANG Module . . . . . . . . . . . . . . . . . . 20
2.12. BFD Top-Level YANG Module . . . . . . . . . . . . . . . . 34 2.12. BFD Top-Level YANG Module . . . . . . . . . . . . . . . . 35
2.13. BFD IP Single-Hop YANG Module . . . . . . . . . . . . . . 36 2.13. BFD IP Single-Hop YANG Module . . . . . . . . . . . . . . 37
2.14. BFD IP Multihop YANG Module . . . . . . . . . . . . . . . 40 2.14. BFD IP Multihop YANG Module . . . . . . . . . . . . . . . 40
2.15. BFD-over-LAG YANG Module . . . . . . . . . . . . . . . . 43 2.15. BFD-over-LAG YANG Module . . . . . . . . . . . . . . . . 44
2.16. BFD-over-MPLS YANG Module . . . . . . . . . . . . . . . . 47 2.16. BFD-over-MPLS YANG Module . . . . . . . . . . . . . . . . 48
3. Data Model Examples . . . . . . . . . . . . . . . . . . . . . 52 3. Data Model Examples . . . . . . . . . . . . . . . . . . . . . 53
3.1. IP Single-Hop . . . . . . . . . . . . . . . . . . . . . . 52 3.1. IP Single-Hop . . . . . . . . . . . . . . . . . . . . . . 53
3.2. IP Multihop . . . . . . . . . . . . . . . . . . . . . . . 53 3.2. IP Multihop . . . . . . . . . . . . . . . . . . . . . . . 54
3.3. LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.3. LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4. Security Considerations . . . . . . . . . . . . . . . . . . . 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . 57
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 61 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.1. Normative References . . . . . . . . . . . . . . . . . . 61 6.1. Normative References . . . . . . . . . . . . . . . . . . 62
6.2. Informative References . . . . . . . . . . . . . . . . . 64 6.2. Informative References . . . . . . . . . . . . . . . . . 65
Appendix A. Echo Function Configuration Example . . . . . . . . 65
Appendix A. Echo Function Configuration Example . . . . . . . . 64
A.1. Example YANG Module for BFD Echo Function A.1. Example YANG Module for BFD Echo Function
Configuration . . . . . . . . . . . . . . . . . . . . . . 65 Configuration . . . . . . . . . . . . . . . . . . . . . . 66
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 67 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 68
Updates since RFC 9127 . . . . . . . . . . . . . . . . . . . . . 67 Updates since RFC 9127 . . . . . . . . . . . . . . . . . . . . . 68
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 68
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
skipping to change at page 4, line 10 skipping to change at page 4, line 15
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, and so the BFD
data model is split into multiple YANG modules where each module 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
skipping to change at page 20, line 17 skipping to change at page 20, line 43
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]. identity from [RFC8349].
<CODE BEGINS> file "ietf-bfd-types@2022-02-11.yang" <CODE BEGINS> file "ietf-bfd-types@2022-04-06.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 32 skipping to change at page 22, line 10
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 to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified 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 9127; see the This version of this YANG module is part of RFC XXXX; 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 9127: YANG Data Model for Bidirectional Forwarding RFC XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-02-11 { revision 2022-04-06 {
description description
"This revision is non-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
skipping to change at page 34, line 26 skipping to change at page 35, line 4
} }
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-02-11.yang" <CODE BEGINS> file "ietf-bfd@2022-04-06.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 XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
skipping to change at page 35, line 44 skipping to change at page 36, line 22
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 to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified 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 9127; see the This version of this YANG module is part of RFC XXXX; 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 9127: YANG Data Model for Bidirectional Forwarding RFC XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-02-11 { revision 2022-04-06 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC XXXX.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC XXXX: 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
skipping to change at page 36, line 43 skipping to change at page 37, line 21
} }
<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-02-11.yang" <CODE BEGINS> file "ietf-bfd-ip-sh@2022-04-06.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 XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
skipping to change at page 38, line 12 skipping to change at page 38, line 37
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 to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified 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 9127; see the This version of this YANG module is part of RFC XXXX; 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 9127: YANG Data Model for Bidirectional Forwarding RFC XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-02-11 { revision 2022-04-06 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC XXXX.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC XXXX: 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
skipping to change at page 40, line 4 skipping to change at page 40, line 30
notification singlehop-notification { notification singlehop-notification {
description description
"Notification for BFD single-hop session state change. An "Notification for BFD single-hop session state change. An
implementation may rate-limit notifications, e.g., when a implementation may rate-limit notifications, e.g., when a
session is continuously changing state."; session is continuously changing state.";
uses bfd-types:notification-parms; uses bfd-types:notification-parms;
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description description
"Interface to which this BFD session belongs."; "Interface to which this BFD session belongs.";
} }
leaf echo-enabled { leaf echo-enabled {
type boolean; type boolean;
description description
"Indicates whether Echo was enabled for BFD."; "Indicates whether Echo was enabled for BFD.";
} }
} }
} }
<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-02-11.yang" <CODE BEGINS> file "ietf-bfd-ip-mh@2022-04-06.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 XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
skipping to change at page 41, line 31 skipping to change at page 42, line 15
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 to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified 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 9127; see the This version of this YANG module is part of RFC XXXX; 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 9127: YANG Data Model for Bidirectional Forwarding RFC XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-02-11 { revision 2022-04-06 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC XXXX.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC XXXX: 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
skipping to change at page 43, line 39 skipping to change at page 44, line 22
} }
<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-02-11.yang" <CODE BEGINS> file "ietf-bfd-lag@2022-04-06.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 XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
skipping to change at page 45, line 6 skipping to change at page 45, line 37
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 to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified 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 9127; see the This version of this YANG module is part of RFC XXXX; 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 9127: YANG Data Model for Bidirectional Forwarding RFC XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-02-11 { revision 2022-04-06 {
description description
"Updating reference to RFC XXXX."; "Updating reference to RFC XXXX.";
reference reference
"RFC XXXX: YANG Data Model for Bidirectional Forwarding "RFC XXXX: 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
skipping to change at page 48, line 5 skipping to change at page 48, line 35
} }
<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-02-11.yang" <CODE BEGINS> file "ietf-bfd-mpls@2022-04-06.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 XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
skipping to change at page 49, line 15 skipping to change at page 49, line 46
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 to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified 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 9127; see the This version of this YANG module is part of RFC XXXX; 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 XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)"; Detection (BFD)";
revision 2022-02-11 { revision 2022-04-06 {
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 XXXX: YANG Data Model for Bidirectional Forwarding
Detection (BFD)."; Detection (BFD).";
} }
revision 2021-10-21 { revision 2021-10-21 {
description description
"Initial revision."; "Initial revision.";
skipping to change at page 55, line 30 skipping to change at page 56, line 30
bfd-types:bfdv1 bfd-types:bfdv1
</type> </type>
<name>name:BFD</name> <name>name:BFD</name>
<bfd xmlns="urn:ietf:params:xml:ns:yang:ietf-bfd"> <bfd xmlns="urn:ietf:params:xml:ns:yang:ietf-bfd">
<lag xmlns="urn:ietf:params:xml:ns:yang:ietf-bfd-lag"> <lag xmlns="urn:ietf:params:xml:ns:yang:ietf-bfd-lag">
<sessions> <sessions>
<session> <session>
<lag-name>Bundle-Ether1</lag-name> <lag-name>Bundle-Ether1</lag-name>
<ipv6-dest-addr>2001:db8:112::16</ipv6-dest-addr> <ipv6-dest-addr>2001:db8:112::16</ipv6-dest-addr>
<desired-min-tx-interval> <desired-min-tx-interval>
100000 10000
</desired-min-tx-interval> </desired-min-tx-interval>
<required-min-rx-interval> <required-min-rx-interval>
100000 10000
</required-min-rx-interval> </required-min-rx-interval>
<use-ipv6>true</use-ipv6> <use-ipv6>true</use-ipv6>
</session> </session>
</sessions> </sessions>
</lag> </lag>
</bfd> </bfd>
</control-plane-protocol> </control-plane-protocol>
</control-plane-protocols> </control-plane-protocols>
</routing> </routing>
</config> </config>
 End of changes. 41 change blocks. 
59 lines changed or deleted 72 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/