< draft-ietf-bfd-yang-15.txt   draft-ietf-bfd-yang-16.txt >
Network Working Group R. Rahman, Ed. Network Working Group R. Rahman, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track L. Zheng, Ed. Intended status: Standards Track L. Zheng, Ed.
Expires: December 20, 2018 Huawei Technologies Expires: December 23, 2018 Huawei Technologies
M. Jethanandani, Ed. M. Jethanandani, Ed.
Xoriant Corporation
S. Pallagatti S. Pallagatti
G. Mirsky G. Mirsky
ZTE Corporation ZTE Corporation
June 18, 2018 June 21, 2018
YANG Data Model for Bidirectional Forwarding Detection (BFD) YANG Data Model for Bidirectional Forwarding Detection (BFD)
draft-ietf-bfd-yang-15 draft-ietf-bfd-yang-16
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). Datastore Architecture (NMDA).
Status of This Memo Status of This Memo
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 December 20, 2018. This Internet-Draft will expire on December 23, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 3, line 7
2.18. BFD over MPLS YANG Module . . . . . . . . . . . . . . . . 51 2.18. BFD over MPLS YANG Module . . . . . . . . . . . . . . . . 51
2.19. BFD over MPLS-TE YANG Module . . . . . . . . . . . . . . 55 2.19. BFD over MPLS-TE YANG Module . . . . . . . . . . . . . . 55
3. Data Model examples . . . . . . . . . . . . . . . . . . . . . 58 3. Data Model examples . . . . . . . . . . . . . . . . . . . . . 58
3.1. IP single-hop . . . . . . . . . . . . . . . . . . . . . . 58 3.1. IP single-hop . . . . . . . . . . . . . . . . . . . . . . 58
3.2. IP multihop . . . . . . . . . . . . . . . . . . . . . . . 59 3.2. IP multihop . . . . . . . . . . . . . . . . . . . . . . . 59
3.3. LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.3. LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 60 3.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4. Security Considerations . . . . . . . . . . . . . . . . . . . 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . 61
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64
5.1. IANA-Maintained iana-bfd-types module . . . . . . . . . . 65 5.1. IANA-Maintained iana-bfd-types module . . . . . . . . . . 68
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 66 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 68
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 66 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.1. Normative References . . . . . . . . . . . . . . . . . . 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 68
7.2. Informative References . . . . . . . . . . . . . . . . . 68 7.2. Informative References . . . . . . . . . . . . . . . . . 71
Appendix A. Echo function configuration example . . . . . . . . 69 Appendix A. Echo function configuration example . . . . . . . . 71
A.1. Example YANG module for BFD echo function configuration . 69 A.1. Example YANG module for BFD echo function configuration . 71
Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 71 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 74
B.1. Changes between versions -13 and -14 . . . . . . . . . . 71 B.1. Changes between versions -15 and -16 . . . . . . . . . . 74
B.2. Changes between versions -12 and -13 . . . . . . . . . . 71 B.2. Changes between versions -14 and -15 . . . . . . . . . . 74
B.3. Changes between versions -11 and -12 . . . . . . . . . . 71 B.3. Changes between versions -13 and -14 . . . . . . . . . . 74
B.4. Changes between versions -10 and -11 . . . . . . . . . . 71 B.4. Changes between versions -12 and -13 . . . . . . . . . . 74
B.5. Changes between versions -09 and -10 . . . . . . . . . . 72 B.5. Changes between versions -11 and -12 . . . . . . . . . . 74
B.6. Changes between versions -08 and -09 . . . . . . . . . . 72 B.6. Changes between versions -10 and -11 . . . . . . . . . . 74
B.7. Changes between versions -07 and -08 . . . . . . . . . . 72 B.7. Changes between versions -09 and -10 . . . . . . . . . . 74
B.8. Changes between versions -06 and -07 . . . . . . . . . . 72 B.8. Changes between versions -08 and -09 . . . . . . . . . . 74
B.9. Changes between versions -05 and -06 . . . . . . . . . . 72 B.9. Changes between versions -07 and -08 . . . . . . . . . . 75
B.10. Changes between versions -04 and -05 . . . . . . . . . . 73 B.10. Changes between versions -06 and -07 . . . . . . . . . . 75
B.11. Changes between versions -03 and -04 . . . . . . . . . . 73 B.11. Changes between versions -05 and -06 . . . . . . . . . . 75
B.12. Changes between versions -02 and -03 . . . . . . . . . . 73 B.12. Changes between versions -04 and -05 . . . . . . . . . . 75
B.13. Changes between versions -01 and -02 . . . . . . . . . . 73 B.13. Changes between versions -03 and -04 . . . . . . . . . . 75
B.14. Changes between versions -00 and -01 . . . . . . . . . . 73 B.14. Changes between versions -02 and -03 . . . . . . . . . . 76
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 73 B.15. Changes between versions -01 and -02 . . . . . . . . . . 76
B.16. Changes between versions -00 and -01 . . . . . . . . . . 76
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76
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 which is used for liveness detection of is a network protocol which 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: paths over which we have BFD:
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 23, line 26 skipping to change at page 23, line 26
The following configuration is defined in the "ietf-te" YANG module The following configuration is defined in the "ietf-te" YANG module
YANG Data Model for TE Topology [I-D.ietf-teas-yang-te]: YANG Data Model for TE Topology [I-D.ietf-teas-yang-te]:
/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:config/ietf- /ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:config/ietf-
te:admin-status te:admin-status
If this configuration is not set to "state-up", no BFD MPLS If this configuration is not set to "state-up", no BFD MPLS
packets can be transmitted or received on that tunnel. packets can be transmitted or received on that tunnel.
2.12. IANA BFD YANG Module 2.12. IANA BFD YANG Module
<CODE BEGINS> file "iana-bfd-types@2018-06-18.yang" <CODE BEGINS> file "iana-bfd-types@2018-06-21.yang"
module iana-bfd-types { module iana-bfd-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:iana-bfd-types"; namespace "urn:ietf:params:xml:ns:yang:iana-bfd-types";
prefix "iana-bfd-types"; prefix "iana-bfd-types";
organization "IANA"; organization "IANA";
skipping to change at page 24, line 24 skipping to change at page 24, line 24
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove // RFC Ed.: replace XXXX with actual RFC number and remove
// this note // this note
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: IANA BFD YANG Data Types."; reference "RFC XXXX: IANA BFD YANG Data Types.";
} }
/* /*
* Type Definitions * Type Definitions
*/ */
typedef diagnostic { typedef diagnostic {
type enumeration { type enumeration {
enum none { enum none {
skipping to change at page 26, line 25 skipping to change at page 26, line 25
} }
} }
<CODE ENDS> <CODE ENDS>
2.13. BFD types YANG Module 2.13. BFD types YANG Module
This YANG module imports typedefs from [RFC6991], [RFC8177] and the This YANG module imports typedefs from [RFC6991], [RFC8177] and the
"control-plane-protocol" identity from [RFC8349]. "control-plane-protocol" identity from [RFC8349].
<CODE BEGINS> file "ietf-bfd-types@2018-06-18.yang" <CODE BEGINS> file "ietf-bfd-types@2018-06-21.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";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 27, line 46 skipping to change at page 27, line 46
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for BFD";
} }
/* /*
* Feature definitions * Feature definitions
*/ */
feature single-minimum-interval { feature single-minimum-interval {
description description
"This feature indicates that the server supports configuration "This feature indicates that the server supports configuration
skipping to change at page 39, line 14 skipping to change at page 39, line 14
} }
<CODE ENDS> <CODE ENDS>
2.14. BFD top-level YANG Module 2.14. 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]. protocols/control-plane-protocol" from [RFC8349].
<CODE BEGINS> file "ietf-bfd@2018-06-18.yang" <CODE BEGINS> file "ietf-bfd@2018-06-21.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";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 40, line 20 skipping to change at page 40, line 20
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for 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').";
skipping to change at page 40, line 50 skipping to change at page 40, line 50
} }
<CODE ENDS> <CODE ENDS>
2.15. BFD IP single-hop YANG Module 2.15. BFD IP single-hop YANG Module
This YANG module imports "interface-ref" from [RFC8343], typedefs This YANG module imports "interface-ref" from [RFC8343], typedefs
from [RFC6991] and augments "/routing/control-plane-protocols/ from [RFC6991] and augments "/routing/control-plane-protocols/
control-plane-protocol" from [RFC8349]. control-plane-protocol" from [RFC8349].
<CODE BEGINS> file "ietf-bfd-ip-sh@2018-06-18.yang" <CODE BEGINS> file "ietf-bfd-ip-sh@2018-06-21.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";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
// remove this note // remove this note
skipping to change at page 42, line 22 skipping to change at page 42, line 22
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD IP single-hop"; reference "RFC XXXX: A YANG data model for BFD IP single-hop";
} }
/* /*
* Augments * Augments
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" { + "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for IP single-hop"; description "BFD augmentation for IP single-hop";
skipping to change at page 44, line 12 skipping to change at page 44, line 12
} }
<CODE ENDS> <CODE ENDS>
2.16. BFD IP multihop YANG Module 2.16. BFD IP multihop YANG Module
This YANG module imports typedefs from [RFC6991] and augments This YANG module imports typedefs from [RFC6991] and augments
"/routing/control-plane-protocols/control-plane-protocol" from "/routing/control-plane-protocols/control-plane-protocol" from
[RFC8349]. [RFC8349].
<CODE BEGINS> file "ietf-bfd-ip-mh@2018-06-18.yang" <CODE BEGINS> file "ietf-bfd-ip-mh@2018-06-21.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";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 45, line 27 skipping to change at page 45, line 27
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD IP multihop."; reference "RFC XXXX: A YANG data model for BFD IP multihop.";
} }
/* /*
* Augments * Augments
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" { + "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for IP multihop."; description "BFD augmentation for IP multihop.";
skipping to change at page 47, line 17 skipping to change at page 47, line 17
} }
<CODE ENDS> <CODE ENDS>
2.17. BFD over LAG YANG Module 2.17. BFD over LAG YANG Module
This YANG module imports "interface-ref" from [RFC8343], typedefs This YANG module imports "interface-ref" from [RFC8343], typedefs
from [RFC6991] and augments "/routing/control-plane-protocols/ from [RFC6991] and augments "/routing/control-plane-protocols/
control-plane-protocol" from [RFC8349]. control-plane-protocol" from [RFC8349].
<CODE BEGINS> file "ietf-bfd-lag@2018-06-18.yang" <CODE BEGINS> file "ietf-bfd-lag@2018-06-21.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";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 48, line 38 skipping to change at page 48, line 38
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD over LAG"; reference "RFC XXXX: A YANG data model for BFD over LAG";
} }
/* /*
* Augments * Augments
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" { + "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for LAG"; description "BFD augmentation for LAG";
skipping to change at page 51, line 12 skipping to change at page 51, line 12
} }
} }
<CODE ENDS> <CODE ENDS>
2.18. BFD over MPLS YANG Module 2.18. BFD over MPLS YANG Module
This YANG module imports typedefs from [RFC6991] and augments This YANG module imports typedefs from [RFC6991] and augments
"/routing/control-plane-protocols/control-plane-protocol" from "/routing/control-plane-protocols/control-plane-protocol" from
[RFC8349]. [RFC8349].
<CODE BEGINS> file "ietf-bfd-mpls@2018-06-18.yang" <CODE BEGINS> file "ietf-bfd-mpls@2018-06-21.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";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 52, line 27 skipping to change at page 52, line 27
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD over MPLS LSPs"; reference "RFC XXXX: A YANG data model for BFD over MPLS LSPs";
} }
/* /*
* Identity definitions * Identity definitions
*/ */
identity encap-gach { identity encap-gach {
base bfd-types:encap-type; base bfd-types:encap-type;
description description
skipping to change at page 55, line 10 skipping to change at page 55, line 10
} }
} }
<CODE ENDS> <CODE ENDS>
2.19. BFD over MPLS-TE YANG Module 2.19. BFD over MPLS-TE YANG Module
This YANG module imports and augments "/te/tunnels/tunnel" from This YANG module imports and augments "/te/tunnels/tunnel" from
[I-D.ietf-teas-yang-te]. [I-D.ietf-teas-yang-te].
<CODE BEGINS> file "ietf-bfd-mpls-te@2018-06-18.yang" <CODE BEGINS> file "ietf-bfd-mpls-te@2018-06-21.yang"
module ietf-bfd-mpls-te { module ietf-bfd-mpls-te {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls-te"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls-te";
prefix "bfd-mpls-te"; prefix "bfd-mpls-te";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 56, line 33 skipping to change at page 56, line 33
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD over MPLS-TE"; reference "RFC XXXX: A YANG data model for BFD over MPLS-TE";
} }
/* /*
* Augments * Augments
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" { + "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for MPLS-TE."; description "BFD augmentation for MPLS-TE.";
skipping to change at page 64, line 15 skipping to change at page 64, line 15
access. access.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls-te/ /routing/control-plane-protocols/control-plane-protocol/bfd/mpls-te/
summary: access to this information discloses the number of BFD summary: access to this information discloses the number of BFD
sessions over MPLS-TE which are up, down and admin-down. The sessions over MPLS-TE which are up, down and admin-down. The
counters include BFD sessions for which the user does not have read- counters include BFD sessions for which the user does not have read-
access. access.
5. IANA Considerations 5. IANA Considerations
The IANA is requested to as assign a new namespace URI from the IETF This document registers the following namespace URIs in the IETF XML
XML registry.
This document registers the following namesace URIs in the IETF XML
registry [RFC3688]: registry [RFC3688]:
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:iana-bfd-types
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
--------------------------------------------------------------------
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.
-------------------------------------------------------------------- --------------------------------------------------------------------
-------------------------------------------------------------------- --------------------------------------------------------------------
skipping to change at page 65, line 42 skipping to change at page 65, line 50
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls-te URI: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls-te
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 Module
Names registry [RFC6020]:
RFC Editor: Replace RFC XXXX with actual RFC number and remove this
note.
--------------------------------------------------------------------
Name: iana-bfd-types
Namespace: urn:ietf:params:xml:ns:yang:iana-bfd-types
Prefix: iana-bfd-types
Reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
Name: ietf-bfd-types
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-types
Prefix: bfd-types
Reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
Name: ietf-bfd
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd
Prefix: bfd
Reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
Name: ietf-bfd-ip-sh
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh
Prefix: bfd-ip-sh
Reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
Name: ietf-bfd-ip-mh
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh
Prefix: bfd-ip-mh
Reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
Name: ietf-bfd-lag
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-lag
Prefix: bfd-lag
Reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
Name: ietf-bfd-mpls
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls
Prefix: bfd-mpls
Reference: RFC XXXX
--------------------------------------------------------------------
--------------------------------------------------------------------
Name: ietf-bfd-mpls-te
Namespace: urn:ietf:params:xml:ns:yang:ietf-bfd-mpls-te
Prefix: bfd-mpls-te
Reference: RFC XXXX
--------------------------------------------------------------------
5.1. IANA-Maintained iana-bfd-types module 5.1. IANA-Maintained iana-bfd-types module
This document defines the initial version of the IANA-maintained This document defines the initial version of the IANA-maintained
iana-bfd-types YANG module. iana-bfd-types YANG module.
The iana-bfd-types YANG module mirrors the "BFD Diagnostic Codes" The iana-bfd-types YANG module mirrors the "BFD Diagnostic Codes"
registry and "BFD Authentication Types" registry at registry and "BFD Authentication Types" registry at
https://www.iana.org/assignments/bfd-parameters/bfd-parameters.xhtml. https://www.iana.org/assignments/bfd-parameters/bfd-parameters.xhtml.
Whenever that registry changes, IANA must update the iana-bfd-types Whenever that registry changes, IANA must update the iana-bfd-types
YANG module. YANG module.
skipping to change at page 67, line 30 skipping to change at page 69, line 39
"Bidirectional Forwarding Detection (BFD) for MPLS Label "Bidirectional Forwarding Detection (BFD) for MPLS Label
Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884, Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884,
June 2010, <https://www.rfc-editor.org/info/rfc5884>. June 2010, <https://www.rfc-editor.org/info/rfc5884>.
[RFC5885] Nadeau, T., Ed. and C. Pignataro, Ed., "Bidirectional [RFC5885] Nadeau, T., Ed. and C. Pignataro, Ed., "Bidirectional
Forwarding Detection (BFD) for the Pseudowire Virtual Forwarding Detection (BFD) for the Pseudowire Virtual
Circuit Connectivity Verification (VCCV)", RFC 5885, Circuit Connectivity Verification (VCCV)", RFC 5885,
DOI 10.17487/RFC5885, June 2010, DOI 10.17487/RFC5885, June 2010,
<https://www.rfc-editor.org/info/rfc5885>. <https://www.rfc-editor.org/info/rfc5885>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
skipping to change at page 70, line 28 skipping to change at page 72, line 47
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 without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2018-06-18 { revision 2018-06-21 {
description "Initial revision."; description "Initial revision.";
reference reference
"RFC XXXX: A YANG data model example augmentation for BFD echo "RFC XXXX: A YANG data model example augmentation for BFD echo
function"; function";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note // note
/* /*
* Groupings * Groupings
*/ */
grouping echo-cfg-parms { grouping echo-cfg-parms {
description "BFD grouping for echo config parameters"; description "BFD grouping for echo config parameters";
skipping to change at page 71, line 28 skipping to change at page 74, line 4
container echo { container echo {
if-feature bfd-types:echo-mode; if-feature bfd-types:echo-mode;
description "BFD echo function container"; description "BFD echo function container";
uses echo-cfg-parms; uses echo-cfg-parms;
} }
} }
} }
Appendix B. Change log Appendix B. Change log
RFC Editor: Remove this section upon publication as an RFC. RFC Editor: Remove this section upon publication as an RFC.
B.1. Changes between versions -13 and -14 B.1. Changes between versions -15 and -16
o Added list of modules for YANG module registry.
B.2. Changes between versions -14 and -15
o Added missing ietf-bfd-types in XML registry.
B.3. Changes between versions -13 and -14
o Addressed missing/incorrect references in import statements. o Addressed missing/incorrect references in import statements.
B.2. Changes between versions -12 and -13 B.4. Changes between versions -12 and -13
o Updated references for drafts which became RFCs recently. o Updated references for drafts which became RFCs recently.
B.3. Changes between versions -11 and -12 B.5. Changes between versions -11 and -12
o Addressed comments from YANG Doctor review of rev11. o Addressed comments from YANG Doctor review of rev11.
B.4. Changes between versions -10 and -11 B.6. Changes between versions -10 and -11
o Added 2 examples. o Added 2 examples.
o Added a container around some lists. o Added a container around some lists.
o Fixed some indentation nits. o Fixed some indentation nits.
B.5. Changes between versions -09 and -10 B.7. Changes between versions -09 and -10
o Addressed comments from YANG Doctor review. o Addressed comments from YANG Doctor review.
o Addressed comments from WGLC. o Addressed comments from WGLC.
B.6. Changes between versions -08 and -09 B.8. Changes between versions -08 and -09
o Mostly cosmetic changes to abide by draft-ietf-netmod-rfc6087bis. o Mostly cosmetic changes to abide by draft-ietf-netmod-rfc6087bis.
o Specified yang-version 1.1. o Specified yang-version 1.1.
o Added data model examples. o Added data model examples.
o Some minor changes. o Some minor changes.
B.7. Changes between versions -07 and -08 B.9. Changes between versions -07 and -08
o Timer intervals in client-cfg-parms are not mandatory anymore. o Timer intervals in client-cfg-parms are not mandatory anymore.
o Added list of interfaces under "ip-sh" node for authentication o Added list of interfaces under "ip-sh" node for authentication
parameters. parameters.
o Renamed replay-protection to meticulous. o Renamed replay-protection to meticulous.
B.8. Changes between versions -06 and -07 B.10. Changes between versions -06 and -07
o New ietf-bfd-types module. o New ietf-bfd-types module.
o Grouping for BFD clients to have BFD multiplier and interval o Grouping for BFD clients to have BFD multiplier and interval
values. values.
o Change in ietf-bfd-mpls-te since MPLS-TE model changed. o Change in ietf-bfd-mpls-te since MPLS-TE model changed.
o Removed bfd- prefix from many names. o Removed bfd- prefix from many names.
B.9. Changes between versions -05 and -06 B.11. Changes between versions -05 and -06
o Adhere to NMDA-guidelines. o Adhere to NMDA-guidelines.
o Echo function config moved to appendix as example. o Echo function config moved to appendix as example.
o Added IANA YANG modules. o Added IANA YANG modules.
o Addressed various comments. o Addressed various comments.
B.10. Changes between versions -04 and -05 B.12. Changes between versions -04 and -05
o "bfd" node in augment of control-plane-protocol. o "bfd" node in augment of control-plane-protocol.
o Removed augment of network-instance. Replaced by schema-mount. o Removed augment of network-instance. Replaced by schema-mount.
o Added information on interaction with other YANG modules. o Added information on interaction with other YANG modules.
B.11. Changes between versions -03 and -04 B.13. Changes between versions -03 and -04
o Updated author information. o Updated author information.
o Fixed YANG compile error in ietf-bfd-lag.yang which was due to o Fixed YANG compile error in ietf-bfd-lag.yang which was due to
incorrect when statement. incorrect when statement.
B.12. Changes between versions -02 and -03 B.14. Changes between versions -02 and -03
o Fixed YANG compilation warning due to incorrect revision date in o Fixed YANG compilation warning due to incorrect revision date in
ietf-bfd-ip-sh module. ietf-bfd-ip-sh module.
B.13. Changes between versions -01 and -02 B.15. Changes between versions -01 and -02
o Replace routing-instance with network-instance from YANG Network o Replace routing-instance with network-instance from YANG Network
Instances [I-D.ietf-rtgwg-ni-model] Instances [I-D.ietf-rtgwg-ni-model]
B.14. Changes between versions -00 and -01 B.16. Changes between versions -00 and -01
o Remove BFD configuration parameters from BFD clients, all BFD o Remove BFD configuration parameters from BFD clients, all BFD
configuration parameters in BFD configuration parameters in BFD
o YANG module split in multiple YANG modules (one per type of o YANG module split in multiple YANG modules (one per type of
forwarding path) forwarding path)
o For BFD over MPLS-TE we augment MPLS-TE model o For BFD over MPLS-TE we augment MPLS-TE model
o For BFD authentication we now use YANG Data Model for Key Chains o For BFD authentication we now use YANG Data Model for Key Chains
skipping to change at page 74, line 4 skipping to change at page 76, line 35
o For BFD authentication we now use YANG Data Model for Key Chains o For BFD authentication we now use YANG Data Model for Key Chains
[RFC8177] [RFC8177]
Authors' Addresses Authors' Addresses
Reshad Rahman (editor) Reshad Rahman (editor)
Cisco Systems Cisco Systems
Canada Canada
Email: rrahman@cisco.com Email: rrahman@cisco.com
Lianshu Zheng (editor) Lianshu Zheng (editor)
Huawei Technologies Huawei Technologies
China China
Email: vero.zheng@huawei.com Email: vero.zheng@huawei.com
Mahesh Jethanandani (editor) Mahesh Jethanandani (editor)
Xoriant Corporation
1248 Reamwood Ave
Sunnyvale, California 94089
USA
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
Santosh Pallagatti Santosh Pallagatti
India India
Email: santosh.pallagatti@gmail.com Email: santosh.pallagatti@gmail.com
Greg Mirsky Greg Mirsky
ZTE Corporation ZTE Corporation
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com
 End of changes. 46 change blocks. 
65 lines changed or deleted 191 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/