draft-ietf-isis-sr-yang-07.txt | draft-ietf-isis-sr-yang-08.txt | |||
---|---|---|---|---|
IS-IS Working Group S. Litkowski | IS-IS Working Group S. Litkowski | |||
Internet-Draft Cisco Systems | Internet-Draft Cisco Systems | |||
Intended status: Standards Track Y. Qu | Intended status: Standards Track Y. Qu | |||
Expires: July 12, 2020 Futurewei | Expires: January 13, 2021 Futurewei | |||
P. Sarkar | P. Sarkar | |||
Individual | Individual | |||
I. Chen | I. Chen | |||
The MITRE Corporation | The MITRE Corporation | |||
J. Tantsura | J. Tantsura | |||
Apstra | Apstra | |||
January 9, 2020 | July 12, 2020 | |||
YANG Data Model for IS-IS Segment Routing | YANG Data Model for IS-IS Segment Routing | |||
draft-ietf-isis-sr-yang-07 | draft-ietf-isis-sr-yang-08 | |||
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 IS-IS Segment Routing. | and manage IS-IS Segment Routing. | |||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
skipping to change at page 1, line 38 ¶ | skipping to change at page 1, line 38 ¶ | |||
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 July 12, 2020. | This Internet-Draft will expire on January 13, 2021. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2020 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 2, line 21 ¶ | skipping to change at page 2, line 21 ¶ | |||
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 | 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 | |||
3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 3 | 3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
4. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3 | 4. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3 | |||
5. IS-IS Segment Routing configuration . . . . . . . . . . . . . 6 | 5. IS-IS Segment Routing configuration . . . . . . . . . . . . . 6 | |||
5.1. Segment Routing activation . . . . . . . . . . . . . . . 6 | 5.1. Segment Routing activation . . . . . . . . . . . . . . . 6 | |||
5.2. Advertising mapping server policy . . . . . . . . . . . . 6 | 5.2. Advertising mapping server policy . . . . . . . . . . . . 6 | |||
5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6 | 5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6 | |||
6. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6 | 6. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6 | |||
7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 | |||
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 | 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 | |||
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 | 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 | |||
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 | 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 | |||
11. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 22 | 11. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 22 | |||
11.1. From version -03 to version -04 . . . . . . . . . . . . 22 | 11.1. From version -03 to version -04 . . . . . . . . . . . . 22 | |||
11.2. From version -02 to version -03 . . . . . . . . . . . . 22 | 11.2. From version -02 to version -03 . . . . . . . . . . . . 22 | |||
11.3. From isis-sr document version -01 to version -02 . . . . 22 | 11.3. From isis-sr document version -01 to version -02 . . . . 23 | |||
11.4. From isis-sr document version -00 to version -01 . . . . 23 | 11.4. From isis-sr document version -00 to version -01 . . . . 23 | |||
11.5. From isis document version -12 to isis-sr document | 11.5. From isis document version -12 to isis-sr document | |||
version -00 . . . . . . . . . . . . . . . . . . . . . . 23 | version -00 . . . . . . . . . . . . . . . . . . . . . . 23 | |||
11.6. From isis document version -12 to version -13 . . . . . 23 | 11.6. From isis document version -12 to version -13 . . . . . 23 | |||
11.7. From isis document version -09 to version -11 . . . . . 23 | 11.7. From isis document version -09 to version -11 . . . . . 23 | |||
11.8. From isis document version -08 to version -09 . . . . . 23 | 11.8. From isis document version -08 to version -09 . . . . . 23 | |||
11.9. From isis document version -07 to version -08 . . . . . 23 | 11.9. From isis document version -07 to version -08 . . . . . 23 | |||
12. Normative References . . . . . . . . . . . . . . . . . . . . 23 | 12. Normative References . . . . . . . . . . . . . . . . . . . . 23 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 | |||
1. Overview | 1. Overview | |||
YANG [RFC6020] [RFC7950] is a data definition language used to define | YANG [RFC6020] [RFC7950] is a data definition language used to define | |||
the contents of a conceptual data store that allows networked devices | the contents of a conceptual data store that allows networked devices | |||
to be managed using NETCONF [RFC6241]. YANG is proving relevant | to be managed using NETCONF [RFC6241]. YANG is proving relevant | |||
beyond its initial confines, as bindings to other interfaces (e.g., | beyond its initial confines, as bindings to other interfaces (e.g., | |||
ReST) and encodings other than XML (e.g., JSON) are being defined. | ReST) and encodings other than XML (e.g., JSON) are being defined. | |||
Furthermore, YANG data models can be used as the basis for | Furthermore, YANG data models can be used as the basis for | |||
implementation of other interfaces, such as CLI and programmatic | implementation of other interfaces, such as CLI and programmatic | |||
skipping to change at page 6, line 48 ¶ | skipping to change at page 6, line 48 ¶ | |||
5.3. IP Fast reroute | 5.3. IP Fast reroute | |||
IS-IS SR model augments the fast-reroute container under interface. | IS-IS SR model augments the fast-reroute container under interface. | |||
It brings the ability to activate TI-LFA (topology independent LFA) | It brings the ability to activate TI-LFA (topology independent LFA) | |||
and also enhances remote LFA to use segment-routing tunneling instead | and also enhances remote LFA to use segment-routing tunneling instead | |||
of LDP. | of LDP. | |||
6. IS-IS Segment Routing YANG Module | 6. IS-IS Segment Routing YANG Module | |||
<CODE BEGINS> file "ietf-isis-sr@2020-01-09.yang" | <CODE BEGINS> file "ietf-isis-sr@2020-07-12.yang" | |||
module ietf-isis-sr { | module ietf-isis-sr { | |||
yang-version 1.1; | ||||
namespace "urn:ietf:params:xml:ns:" | namespace "urn:ietf:params:xml:ns:" | |||
+ "yang:ietf-isis-sr"; | + "yang:ietf-isis-sr"; | |||
prefix isis-sr; | prefix isis-sr; | |||
import ietf-routing { | import ietf-routing { | |||
prefix "rt"; | prefix "rt"; | |||
reference "RFC 8349 - A YANG Data Model for Routing | ||||
Management (NMDA Version)"; | ||||
} | } | |||
import ietf-segment-routing-common { | import ietf-segment-routing-common { | |||
prefix "sr-cmn"; | prefix "sr-cmn"; | |||
} | } | |||
import ietf-segment-routing-mpls { | import ietf-segment-routing-mpls { | |||
prefix "sr-mpls"; | prefix "sr-mpls"; | |||
} | } | |||
import ietf-isis { | import ietf-isis { | |||
prefix "isis"; | prefix "isis"; | |||
} | } | |||
import iana-routing-types { | import iana-routing-types { | |||
prefix "iana-rt-types"; | prefix "iana-rt-types"; | |||
reference "RFC 8294 - Common YANG Data Types for the | ||||
Routing Area"; | ||||
} | } | |||
organization | organization | |||
"IETF LSR - LSR Working Group"; | "IETF LSR - LSR Working Group"; | |||
contact | contact | |||
"WG List: <mailto:lsr@ietf.org> | "WG List: <mailto:lsr@ietf.org> | |||
Editor: Stephane Litkowski | Editor: Stephane Litkowski | |||
<mailto:stephane.litkowski@orange.com> | <mailto:stephane.litkowski@orange.com> | |||
skipping to change at page 7, line 51 ¶ | skipping to change at page 8, line 8 ¶ | |||
<mailto:pushpasis.ietf@gmail.com> | <mailto:pushpasis.ietf@gmail.com> | |||
Author: Ing-Wher Chen | Author: Ing-Wher Chen | |||
<mailto:ingwherchen@mitre.org> | <mailto:ingwherchen@mitre.org> | |||
Author: Jeff Tantsura | Author: Jeff Tantsura | |||
<mailto:jefftant.ietf@gmail.com> | <mailto:jefftant.ietf@gmail.com> | |||
"; | "; | |||
description | description | |||
"The YANG module defines a generic configuration model for | "The YANG module defines a generic configuration model for | |||
Segment routing ISIS extensions common across all of the vendor | Segment routing ISIS extensions common across all of the vendor | |||
implementations | implementations. | |||
Copyright (c) 2020 IETF Trust and the persons identified as | ||||
authors of the code. All rights reserved. | ||||
Redistribution and use in source and binary forms, with or | This YANG model conforms to the Network Management | |||
without modification, is permitted pursuant to, and subject | Datastore Architecture (NMDA) as described in RFC 8242. | |||
to the license terms contained in, the Simplified BSD License | ||||
set forth in Section 4.c of the IETF Trust's Legal Provisions | ||||
Relating to IETF Documents | ||||
(http://trustee.ietf.org/license-info). | ||||
This version of this YANG module is part of RFC XXXX; | Copyright (c) 2020 IETF Trust and the persons identified as | |||
see the RFC itself for full legal notices."; | authors of the code. All rights reserved. | |||
Redistribution and use in source and binary forms, with or | ||||
without modification, is permitted pursuant to, and subject to | ||||
the license terms contained in, the Simplified BSD License set | ||||
forth in Section 4.c of the IETF Trust's Legal Provisions | ||||
Relating to IETF Documents | ||||
(https://trustee.ietf.org/license-info). | ||||
This version of this YANG module is part of RFC XXXX | ||||
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself | ||||
for full legal notices. | ||||
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL | ||||
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', | ||||
'MAY', and 'OPTIONAL' in this document are to be interpreted as | ||||
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, | ||||
they appear in all capitals, as shown here. | ||||
This version of this YANG module is part of RFC XXXX; | ||||
see the RFC itself for full legal notices."; | ||||
reference "RFC XXXX"; | reference "RFC XXXX"; | |||
revision 2020-01-09 { | revision 2020-07-12 { | |||
description | description | |||
"Initial revision."; | "Initial revision."; | |||
reference "RFC XXXX"; | reference "RFC XXXX"; | |||
} | } | |||
/* Identities */ | /* Identities */ | |||
identity sr-capability { | identity sr-capability { | |||
description | description | |||
"Base identity for ISIS SR-Capabilities sub-TLV flgs"; | "Base identity for ISIS SR-Capabilities sub-TLV flgs"; | |||
} | } | |||
End of changes. 16 change blocks. | ||||
22 lines changed or deleted | 40 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |