draft-ietf-bfd-yang-03.txt   draft-ietf-bfd-yang-04.txt 
Network Working Group L. Zheng, Ed. Network Working Group L. Zheng, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track R. Rahman, Ed. Intended status: Standards Track R. Rahman, Ed.
Expires: January 9, 2017 Cisco Systems Expires: July 12, 2017 Cisco Systems
S. Pallagatti S. Pallagatti
M. Jethanandani M. Jethanandani
Cisco Systems Cisco Systems
G. Mirsky G. Mirsky
Ericsson Ericsson
July 8, 2016 January 8, 2017
Yang Data Model for Bidirectional Forwarding Detection (BFD) Yang Data Model for Bidirectional Forwarding Detection (BFD)
draft-ietf-bfd-yang-03.txt draft-ietf-bfd-yang-04.txt
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).
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 January 9, 2017. This Internet-Draft will expire on July 12, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 49 skipping to change at page 2, line 49
2.9. BFD over MPLS LSPs hierarchy . . . . . . . . . . . . . . 15 2.9. BFD over MPLS LSPs hierarchy . . . . . . . . . . . . . . 15
2.10. BFD over MPLS-TE hierarchy . . . . . . . . . . . . . . . 17 2.10. BFD over MPLS-TE hierarchy . . . . . . . . . . . . . . . 17
2.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 19 2.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 19
2.12. Interaction with other YANG modules . . . . . . . . . . . 19 2.12. Interaction with other YANG modules . . . . . . . . . . . 19
2.13. BFD top-level Yang Module . . . . . . . . . . . . . . . . 19 2.13. BFD top-level Yang Module . . . . . . . . . . . . . . . . 19
2.14. BFD IP single-hop Yang Module . . . . . . . . . . . . . . 31 2.14. BFD IP single-hop Yang Module . . . . . . . . . . . . . . 31
2.15. BFD IP multi-hop Yang Module . . . . . . . . . . . . . . 34 2.15. BFD IP multi-hop Yang Module . . . . . . . . . . . . . . 34
2.16. BFD over LAG Yang Module . . . . . . . . . . . . . . . . 37 2.16. BFD over LAG Yang Module . . . . . . . . . . . . . . . . 37
2.17. BFD over MPLS Yang Module . . . . . . . . . . . . . . . . 41 2.17. BFD over MPLS Yang Module . . . . . . . . . . . . . . . . 41
2.18. BFD over MPLS-TE Yang Module . . . . . . . . . . . . . . 44 2.18. BFD over MPLS-TE Yang Module . . . . . . . . . . . . . . 44
2.19. Security Considerations . . . . . . . . . . . . . . . . . 46 2.19. Security Considerations . . . . . . . . . . . . . . . . . 47
2.20. IANA Considerations . . . . . . . . . . . . . . . . . . . 47 2.20. IANA Considerations . . . . . . . . . . . . . . . . . . . 47
2.21. Acknowledgements . . . . . . . . . . . . . . . . . . . . 47 2.21. Acknowledgements . . . . . . . . . . . . . . . . . . . . 47
3. References . . . . . . . . . . . . . . . . . . . . . . . . . 47 3. References . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.1. Normative References . . . . . . . . . . . . . . . . . . 47 3.1. Normative References . . . . . . . . . . . . . . . . . . 47
3.2. Informative References . . . . . . . . . . . . . . . . . 48 3.2. Informative References . . . . . . . . . . . . . . . . . 48
Appendix A. Change log . . . . . . . . . . . . . . . . . . . . . 49 Appendix A. Change log . . . . . . . . . . . . . . . . . . . . . 49
A.1. Changes between versions -02 and -03 . . . . . . . . . . 49 A.1. Changes between versions -03 and -04 . . . . . . . . . . 49
A.2. Changes between versions -01 and -02 . . . . . . . . . . 49 A.2. Changes between versions -02 and -03 . . . . . . . . . . 49
A.3. Changes between versions -00 and -01 . . . . . . . . . . 49 A.3. Changes between versions -01 and -02 . . . . . . . . . . 49
A.4. Changes between versions -00 and -01 . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50
1. Introduction 1. Introduction
YANG [RFC6020] is a data definition language that was introduced to YANG [RFC6020] is a data definition language that was introduced to
define the contents of a conceptual data store that allows networked define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF [RFC6241]. YANG is proving devices to be managed using NETCONF [RFC6241]. YANG is proving
relevant beyond its initial confines, as bindings to other interfaces relevant beyond its initial confines, as bindings to other interfaces
(e.g RESTCONF [I-D.ietf-netconf-restconf]) and encodings other than (e.g RESTCONF [I-D.ietf-netconf-restconf]) and encodings other than
XML (e.g JSON) are being defined. Furthermore, YANG data models can XML (e.g JSON) are being defined. Furthermore, YANG data models can
skipping to change at page 37, line 49 skipping to change at page 37, line 49
leaf network-instance { leaf network-instance {
type string; type string;
description "Network instance"; description "Network instance";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
2.16. BFD over LAG Yang Module 2.16. BFD over LAG Yang Module
<CODE BEGINS> file "ietf-bfd-lag@2016-02-17.yang" <CODE BEGINS> file "ietf-bfd-lag@2017-01-07.yang"
module ietf-bfd-lag { module ietf-bfd-lag {
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-lag"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-lag";
// replace with IANA namespace when assigned // replace with IANA namespace when assigned
prefix "bfd-lag"; prefix "bfd-lag";
import ietf-bfd { import ietf-bfd {
prefix "bfd"; prefix "bfd";
} }
import ietf-interfaces { import ietf-interfaces {
skipping to change at page 38, line 32 skipping to change at page 38, line 32
"WG Web: <http://tools.ietf.org/wg/bfd> "WG Web: <http://tools.ietf.org/wg/bfd>
WG List: <rtg-bfd@ietf.org> WG List: <rtg-bfd@ietf.org>
WG Chair: Jeff Haas WG Chair: Jeff Haas
WG Chair: Reshad Rahman WG Chair: Reshad Rahman
Editor: Lianshu Zheng and Reshad Rahman"; Editor: Lianshu Zheng and Reshad Rahman";
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 RFC7130."; interfaces as per RFC7130.";
revision 2017-01-07 {
description
"* Update author information
* Fixed error with when use-ipv4/use-ipv6 statements
";
reference "RFC XXXX: A YANG data model for BFD over LAG";
}
revision 2016-02-17 { revision 2016-02-17 {
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";
} }
augment "/bfd:bfd" { augment "/bfd:bfd" {
description "BFD augmentation for LAG"; description "BFD augmentation for LAG";
container lag { container lag {
description "BFD over LAG top level container"; description "BFD over LAG top level container";
skipping to change at page 40, line 13 skipping to change at page 40, line 22
key "member-link"; key "member-link";
description description
"Micro-BFD over LAG. This represents one member link"; "Micro-BFD over LAG. This represents one member link";
leaf member-link { leaf member-link {
type if:interface-ref; type if:interface-ref;
description description
"Member link on which micro-BFD is running"; "Member link on which micro-BFD is running";
} }
container micro-bfd-ipv4 { container micro-bfd-ipv4 {
when "../use-ipv4 = 'true'" { when "../../use-ipv4 = 'true'" {
description "Needed only if IPv4 is used."; description "Needed only if IPv4 is used.";
} }
description description
"Micro-BFD IPv4 session state on member link"; "Micro-BFD IPv4 session state on member link";
uses bfd:bfd-all-session; uses bfd:bfd-all-session;
} }
container micro-bfd-ipv6 { container micro-bfd-ipv6 {
when "../use-ipv6 = 'true'" { when "../../use-ipv6 = 'true'" {
description "Needed only if IPv6 is used."; description "Needed only if IPv6 is used.";
} }
description description
"Micro-BFD IPv6 session state on member link"; "Micro-BFD IPv6 session state on member link";
uses bfd:bfd-all-session; uses bfd:bfd-all-session;
} }
} }
} }
} }
} }
skipping to change at page 48, line 45 skipping to change at page 48, line 50
[RFC7130] Bhatia, M., Ed., Chen, M., Ed., Boutros, S., Ed., [RFC7130] Bhatia, M., Ed., Chen, M., Ed., Boutros, S., Ed.,
Binderberger, M., Ed., and J. Haas, Ed., "Bidirectional Binderberger, M., Ed., and J. Haas, Ed., "Bidirectional
Forwarding Detection (BFD) on Link Aggregation Group (LAG) Forwarding Detection (BFD) on Link Aggregation Group (LAG)
Interfaces", RFC 7130, DOI 10.17487/RFC7130, February Interfaces", RFC 7130, DOI 10.17487/RFC7130, February
2014, <http://www.rfc-editor.org/info/rfc7130>. 2014, <http://www.rfc-editor.org/info/rfc7130>.
3.2. Informative References 3.2. Informative References
[I-D.ietf-netconf-restconf] [I-D.ietf-netconf-restconf]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", draft-ietf-netconf-restconf-15 (work in Protocol", draft-ietf-netconf-restconf-18 (work in
progress), July 2016. progress), October 2016.
[I-D.ietf-netmod-routing-cfg] [I-D.ietf-netmod-routing-cfg]
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", draft-ietf-netmod-routing-cfg-22 (work in Management", draft-ietf-netmod-routing-cfg-25 (work in
progress), July 2016. progress), November 2016.
[I-D.ietf-rtgwg-ni-model] [I-D.ietf-rtgwg-ni-model]
Berger, L., Hopps, C., Lindem, A., and D. Bogdanovic, Berger, L., Hopps, C., Lindem, A., and D. Bogdanovic,
"Network Instance Model", draft-ietf-rtgwg-ni-model-00 "YANG Network Instances", draft-ietf-rtgwg-ni-model-01
(work in progress), June 2016. (work in progress), October 2016.
[I-D.ietf-rtgwg-yang-key-chain] [I-D.ietf-rtgwg-yang-key-chain]
Lindem, A., Qu, Y., Yeung, D., Chen, I., Zhang, Z., and Y. Lindem, A., Qu, Y., Yeung, D., Chen, I., Zhang, Z., and Y.
Yang, "Routing Key Chain YANG Data Model", draft-ietf- Yang, "Routing Key Chain YANG Data Model", draft-ietf-
rtgwg-yang-key-chain-06 (work in progress), June 2016. rtgwg-yang-key-chain-11 (work in progress), November 2016.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., Chen, Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H.,
X., Jones, R., and B. Wen, "A YANG Data Model for Traffic Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data
Engineering Tunnels and Interfaces", draft-ietf-teas-yang- Model for Traffic Engineering Tunnels and Interfaces",
te-03 (work in progress), March 2016. draft-ietf-teas-yang-te-05 (work in progress), October
2016.
Appendix A. Change log Appendix A. Change log
RFC Editor: Remove this section upon publication as an RFC. RFC Editor: Remove this section upon publication as an RFC.
A.1. Changes between versions -02 and -03 A.1. Changes between versions -03 and -04
o Updated author information.
o Fixed YANG compile error in ietf-bfd-lag.yang which was due to
incorrect when statement.
A.2. 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.
A.2. Changes between versions -01 and -02 A.3. Changes between versions -01 and -02
o Replace routing-instance, which has been removed from o Replace routing-instance, which has been removed from
[I-D.ietf-netmod-routing-cfg], with network-instance from [I-D.ietf-netmod-routing-cfg], with network-instance from
[I-D.ietf-rtgwg-ni-model] [I-D.ietf-rtgwg-ni-model]
A.3. Changes between versions -00 and -01 A.4. 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 key-chain in o For BFD authentication we now use key-chain in
skipping to change at page 50, line 32 skipping to change at page 50, line 45
Email: santosh.pallagatti@gmail.com Email: santosh.pallagatti@gmail.com
Mahesh Jethanandani Mahesh Jethanandani
Cisco Systems Cisco Systems
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
Greg Mirsky Greg Mirsky
Ericsson Ericsson
Email: gregory.mirsky@ericsson.com Email: gregimirsky@gmail.com
 End of changes. 20 change blocks. 
26 lines changed or deleted 43 lines changed or added

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