| < draft-ietf-bfd-yang-02.txt | draft-ietf-bfd-yang-03.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 8, 2017 Cisco Systems | Expires: January 9, 2017 Cisco Systems | |||
| S. Pallagatti | S. Pallagatti | |||
| M. Jethanandani | M. Jethanandani | |||
| Cisco Systems | Cisco Systems | |||
| G. Mirsky | G. Mirsky | |||
| Ericsson | Ericsson | |||
| July 7, 2016 | July 8, 2016 | |||
| Yang Data Model for Bidirectional Forwarding Detection (BFD) | Yang Data Model for Bidirectional Forwarding Detection (BFD) | |||
| draft-ietf-bfd-yang-02.txt | draft-ietf-bfd-yang-03.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 8, 2017. | This Internet-Draft will expire on January 9, 2017. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2016 IETF Trust and the persons identified as the | Copyright (c) 2016 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 | |||
| skipping to change at page 3, line 7 ¶ | skipping to change at page 3, line 7 ¶ | |||
| 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 . . . . . . . . . . . . . . . . . 46 | |||
| 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 -01 and -02 . . . . . . . . . . 49 | A.1. Changes between versions -02 and -03 . . . . . . . . . . 49 | |||
| A.2. Changes between versions -00 and -01 . . . . . . . . . . 49 | A.2. Changes between versions -01 and -02 . . . . . . . . . . 49 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 49 | A.3. Changes between versions -00 and -01 . . . . . . . . . . 49 | |||
| 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 | |||
| be used as the basis of implementation for other interfaces, such as | be used as the basis of implementation for other interfaces, such as | |||
| skipping to change at page 32, line 28 ¶ | skipping to change at page 32, line 28 ¶ | |||
| "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 IP single-hop | "This module contains the YANG definition for BFD IP single-hop | |||
| as per RFC5881."; | as per RFC5881."; | |||
| revision 2016-01-04 { | revision 2016-07-04 { | |||
| 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"; | |||
| } | } | |||
| augment "/bfd:bfd" { | augment "/bfd:bfd" { | |||
| description "BFD augmentation for IP single-hop"; | description "BFD augmentation for IP single-hop"; | |||
| container ip-sh { | container ip-sh { | |||
| description "BFD IP single-hop top level container"; | description "BFD IP single-hop top level container"; | |||
| container config { | container config { | |||
| skipping to change at page 48, line 45 ¶ | skipping to change at page 48, line 45 ¶ | |||
| [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-14 (work in | Protocol", draft-ietf-netconf-restconf-15 (work in | |||
| progress), June 2016. | progress), July 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-22 (work in | |||
| progress), July 2016. | progress), July 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 | "Network Instance Model", draft-ietf-rtgwg-ni-model-00 | |||
| (work in progress), June 2016. | (work in progress), June 2016. | |||
| skipping to change at page 49, line 25 ¶ | skipping to change at page 49, line 25 ¶ | |||
| [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., Chen, | |||
| X., Jones, R., and B. Wen, "A YANG Data Model for Traffic | X., Jones, R., and B. Wen, "A YANG Data Model for Traffic | |||
| Engineering Tunnels and Interfaces", draft-ietf-teas-yang- | Engineering Tunnels and Interfaces", draft-ietf-teas-yang- | |||
| te-03 (work in progress), March 2016. | te-03 (work in progress), March 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 -01 and -02 | A.1. Changes between versions -02 and -03 | |||
| o Fixed YANG compilation warning due to incorrect revision date in | ||||
| ietf-bfd-ip-sh module. | ||||
| A.2. 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.2. Changes between versions -00 and -01 | A.3. 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 | |||
| End of changes. 9 change blocks. | ||||
| 12 lines changed or deleted | 18 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/ | ||||