< draft-ietf-lsr-isis-srv6-yang-00.txt   draft-ietf-lsr-isis-srv6-yang-01.txt >
Network Working Group Z. Hu Network Working Group Z. Hu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track D. Ye Intended status: Standards Track D. Ye
Expires: 19 February 2022 Cisco Expires: 27 September 2022 Cisco
Y. Qu Y. Qu
Futurewei Futurewei Technologies
X. Geng X. Geng
Q. Ma Q. Ma
Huawei Huawei
18 August 2021 26 March 2022
YANG Data Model for IS-IS SRv6 YANG Data Model for IS-IS SRv6
draft-ietf-lsr-isis-srv6-yang-00 draft-ietf-lsr-isis-srv6-yang-01
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 SRv6 [I-D.ietf-lsr-isis-srv6-extensions]. and manage IS-IS SRv6 [I-D.ietf-lsr-isis-srv6-extensions].
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 43 skipping to change at page 1, line 43
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 19 February 2022. This Internet-Draft will expire on 27 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 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 Simplified BSD License text extracted from this document must include Revised BSD License text as
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 Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IS-IS SRv6 . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. IS-IS SRv6 . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. IS-IS SRv6 configuration . . . . . . . . . . . . . . . . . . 5 3. IS-IS SRv6 configuration . . . . . . . . . . . . . . . . . . 5
3.1. SRv6 activation . . . . . . . . . . . . . . . . . . . . . 5 3.1. SRv6 activation . . . . . . . . . . . . . . . . . . . . . 5
3.2. Locator setting . . . . . . . . . . . . . . . . . . . . . 5 3.2. Locator setting . . . . . . . . . . . . . . . . . . . . . 5
3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 5 3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 5
3.4. Microloop avoidance . . . . . . . . . . . . . . . . . . . 6 3.4. Microloop avoidance . . . . . . . . . . . . . . . . . . . 6
4. IS-IS SRv6 YANG Module . . . . . . . . . . . . . . . . . . . 6 4. IS-IS SRv6 YANG Module . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 19 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
Appendix A. Configuration examples . . . . . . . . . . . . . . . 22 Appendix A. Configuration examples . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
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 13 skipping to change at page 6, line 13
ability to activate ipv6 TI-LFA (topology independent LFA). ability to activate ipv6 TI-LFA (topology independent LFA).
3.4. Microloop avoidance 3.4. Microloop avoidance
IS-IS SRv6 model augments the micro-loop-avoidance container, this IS-IS SRv6 model augments the micro-loop-avoidance container, this
container including the leaf "srv6-enable" brings the ability to container including the leaf "srv6-enable" brings the ability to
activate SRv6 avoid-microloop. activate SRv6 avoid-microloop.
4. IS-IS SRv6 YANG Module 4. IS-IS SRv6 YANG Module
<CODE BEGINS> file "ietf-isis-srv6@2020-07-13.yang" <CODE BEGINS> file "ietf-isis-srv6@2022-03-26.yang"
module ietf-isis-srv6 { module ietf-isis-srv6 {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:" namespace "urn:ietf:params:xml:ns:"
+ "yang:ietf-isis-srv6"; + "yang:ietf-isis-srv6";
prefix isis-srv6; prefix isis-srv6;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC8349: A YANG Data Model for reference "RFC8349: A YANG Data Model for
Routing Management (NMDA Version)"; Routing Management (NMDA Version)";
skipping to change at page 6, line 39 skipping to change at page 6, line 39
Data Model for IS-IS Protocol"; Data Model for IS-IS Protocol";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6991:Common YANG Data Types"; reference "RFC 6991:Common YANG Data Types";
} }
import ietf-segment-routing { import ietf-segment-routing {
prefix sr; prefix sr;
reference "draft-ietf-spring-sr-yang: YANG Data reference "RFC 9020: YANG Data Model for Segment
Model for Segment Routing"; Routing";
} }
import ietf-srv6-base { import ietf-srv6-base {
prefix "srv6"; prefix "srv6";
reference "draft-ietf-spring-srv6-yang: YANG Data reference "draft-ietf-spring-srv6-yang: YANG Data
Model for SRv6 Base and Static"; Model for SRv6 Base and Static";
} }
organization organization
"IETF LSR Working Group"; "IETF LSR Working Group";
skipping to change at page 7, line 15 skipping to change at page 7, line 15
Author: Zhibo Hu Author: Zhibo Hu
<mailto:huzhibo@huawei.com> <mailto:huzhibo@huawei.com>
Author: Dan Ye Author: Dan Ye
<mailto:daye@cisco.com> <mailto:daye@cisco.com>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yingzhen.qu@futurewei.com> <mailto:yingzhen.qu@futurewei.com>
Author: Qiufang Ma Author: Qiufang Ma
<mailto:maqiufang1@huawei.com> <mailto:maqiufang1@huawei.com>
"; ";
description description
"The YANG module defines a generic configuration model for "The YANG module defines the configuration and operatioanl state
Segment IPV6 routing ISIS extensions common across all of for IS-IS extension to support Segment Routing over IPv6 data
the vendor implementations."; plane.
revision 2020-07-13 { This YANG model conforms to the Network Management
Datastore Architecture (NDMA) as described in RFC 8342.
Copyright (c) 2022 IETF Trust and the persons identified as
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
(http://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.";
revision 2022-03-26 {
description description
"Initial revision."; "Initial revision.";
reference "draft-ietf-lsr-isis-srv6-extensions-08"; reference "draft-ietf-lsr-isis-srv6-extensions-08";
} }
/* Identities */ /* Identities */
identity SRV6_END_FUNC_TYPE { identity SRV6_END_FUNC_TYPE {
description description
"Base identity type for srv6 endpoint function code points."; "Base identity type for srv6 endpoint function code points.";
} }
identity SRV6_END_FUNC_PSP_USP_USD { identity SRV6_END_FUNC_PSP_USP_USD {
base "SRV6_END_FUNC_TYPE"; base "SRV6_END_FUNC_TYPE";
description description
"End (May support PSP, USP, USD)."; "End (May support PSP, USP, USD).";
} }
identity SRV6_END_X_FUNC_PSP_USP_USD { identity SRV6_END_X_FUNC_PSP_USP_USD {
base "SRV6_END_FUNC_TYPE"; base "SRV6_END_FUNC_TYPE";
skipping to change at page 20, line 46 skipping to change at page 21, line 16
Litkowski, S., Yeung, D., Lindem, A., Zhang, J., and L. Litkowski, S., Yeung, D., Lindem, A., Zhang, J., and L.
Lhotka, "YANG Data Model for IS-IS Protocol", Work in Lhotka, "YANG Data Model for IS-IS Protocol", Work in
Progress, Internet-Draft, draft-ietf-isis-yang-isis-cfg- Progress, Internet-Draft, draft-ietf-isis-yang-isis-cfg-
42, 15 October 2019, <https://www.ietf.org/archive/id/ 42, 15 October 2019, <https://www.ietf.org/archive/id/
draft-ietf-isis-yang-isis-cfg-42.txt>. draft-ietf-isis-yang-isis-cfg-42.txt>.
[I-D.ietf-lsr-isis-srv6-extensions] [I-D.ietf-lsr-isis-srv6-extensions]
Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and
Z. Hu, "IS-IS Extensions to Support Segment Routing over Z. Hu, "IS-IS Extensions to Support Segment Routing over
IPv6 Dataplane", Work in Progress, Internet-Draft, draft- IPv6 Dataplane", Work in Progress, Internet-Draft, draft-
ietf-lsr-isis-srv6-extensions-17, 18 June 2021, ietf-lsr-isis-srv6-extensions-18, 20 October 2021,
<https://www.ietf.org/archive/id/draft-ietf-lsr-isis-srv6- <https://www.ietf.org/archive/id/draft-ietf-lsr-isis-srv6-
extensions-17.txt>. extensions-18.txt>.
[I-D.ietf-spring-sr-yang] [I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J. Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J.
Tantsura, "YANG Data Model for Segment Routing", Work in Tantsura, "YANG Data Model for Segment Routing", Work in
Progress, Internet-Draft, draft-ietf-spring-sr-yang-30, 25 Progress, Internet-Draft, draft-ietf-spring-sr-yang-30, 25
January 2021, <https://www.ietf.org/archive/id/draft-ietf- January 2021, <https://www.ietf.org/archive/id/draft-ietf-
spring-sr-yang-30.txt>. spring-sr-yang-30.txt>.
[I-D.ietf-spring-srv6-yang] [I-D.ietf-spring-srv6-yang]
Raza, K., Agarwal, S., Liu, X., Hu, Z., Hussain, I., Shah, Raza, K., Agarwal, S., Liu, X., Hu, Z., Hussain, I., Shah,
H., Voyer, D., Matsushima, S., Horiba, K., AbdelSalam, A., H., Voyer, D., Matsushima, S., Horiba, K., Rajamanickam,
and J. Rajamanickam, "YANG Data Model for SRv6 Base and J., and A. AbdelSalam, "YANG Data Model for SRv6 Base and
Static", Work in Progress, Internet-Draft, draft-ietf- Static", Work in Progress, Internet-Draft, draft-ietf-
spring-srv6-yang-00, 9 September 2020, spring-srv6-yang-01, 14 January 2022,
<https://www.ietf.org/archive/id/draft-ietf-spring-srv6- <https://www.ietf.org/archive/id/draft-ietf-spring-srv6-
yang-00.txt>. yang-01.txt>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
skipping to change at page 23, line 46 skipping to change at page 24, line 46
} }
Authors' Addresses Authors' Addresses
Zhibo Hu Zhibo Hu
Huawei Huawei
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing Beijing
100095 100095
China China
Email: huzhibo@huawei.com Email: huzhibo@huawei.com
Dan Ye Dan Ye
Cisco Cisco
170 W. Tasman Dr. San Jose, 170 W. Tasman Dr. San Jose,
California, 95134 California, 95134
United States of America United States of America
Email: daye@cisco.com Email: daye@cisco.com
Yingzhen Qu Yingzhen Qu
Futurewei Futurewei Technologies
2330 Central Express Way 2330 Central Express Way
Santa Clara, 950950 Santa Clara, 950950
United States of America United States of America
Email: yingzhen.qu@futurewei.com Email: yingzhen.qu@futurewei.com
Xuesong Geng Xuesong Geng
Huawei Huawei
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing Beijing
100095 100095
China China
Email: gengxuesong@huawei.com Email: gengxuesong@huawei.com
Qiufang Ma Qiufang Ma
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing Nanjing
Jiangsu, 210012 Jiangsu, 210012
China China
Email: maqiufang1@huawei.com Email: maqiufang1@huawei.com
 End of changes. 26 change blocks. 
31 lines changed or deleted 49 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/