< draft-mahesh-spring-srv6-mobile-yang-00.txt   draft-mahesh-bess-srv6-mup-yang-00.txt >
Spring M. Jethanandani, Ed. Spring M. Jethanandani, Ed.
Internet-Draft T. Murakami Internet-Draft T. Murakami
Intended status: Standards Track Arrcus, Inc Intended status: Standards Track Arrcus, Inc
Expires: 4 September 2022 3 March 2022 Expires: 21 September 2022 20 March 2022
A YANG Model for SRv6 Mobile User Plane A YANG Model for SRv6 Mobile User Plane
draft-mahesh-spring-srv6-mobile-yang-00 draft-mahesh-bess-srv6-mup-yang-00
Abstract Abstract
This document defines a YANG data model for configuration and This document defines a YANG data model for configuration and
management of SRv6 for the mobile network. management of SRv6 for the Mobile User Plane (MUP).
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.
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 4 September 2022. This Internet-Draft will expire on 21 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 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 Revised BSD License text as extracted from this document must include Revised BSD License text 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 Revised BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Note to RFC Editors . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . . . 4
4. YANG Model . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. YANG Model . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1. Normative References . . . . . . . . . . . . . . . . . . 18 7.1. Normative References . . . . . . . . . . . . . . . . . . 18
7.2. Informative References . . . . . . . . . . . . . . . . . 21 7.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. Appendix 1 Complete Tree Diagram . . . . . . . . . . 21 Appendix A. Appendix 1 Complete Tree Diagram . . . . . . . . . . 21
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 22 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 22
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 22
skipping to change at page 3, line 13 skipping to change at page 3, line 13
The model conforms to the NMDA [RFC8342] architecture. The model conforms to the NMDA [RFC8342] architecture.
1.1. Requirements Language 1.1. 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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1.2. Note to RFC Editors
This document uses several placeholder values throughout the
document. Please replace them as follows and remove this note before
publication.
RFC XXXX, where XXXX is the number assigned to this document at the
time of publication.
2022-03-08 with the actual date of the publication of this document.
2. Terminology 2. Terminology
This document references terms defined in other documents. In This document references terms defined in other documents. In
particular, it imports definitions for the following terms from particular, it imports definitions for the following terms from
Segment Routing Architecture [RFC8402], and IPv6 Segment Routing Segment Routing Architecture [RFC8402], and IPv6 Segment Routing
Header (SRH) [RFC8754]. Header (SRH) [RFC8754].
* Active Segment * Active Segment
* BGP-Prefix Segment * BGP-Prefix Segment
skipping to change at page 6, line 13 skipping to change at page 6, line 13
Figure 1: Tree Diagram for SRv6 YANG Model Figure 1: Tree Diagram for SRv6 YANG Model
4. YANG Model 4. YANG Model
The YANG model is divided into two parts. The first part of the The YANG model is divided into two parts. The first part of the
model augments the BGP model in BGP Model for Service Provider model augments the BGP model in BGP Model for Service Provider
Network [I-D.ietf-idr-bgp-model] for the BGP configuration, while the Network [I-D.ietf-idr-bgp-model] for the BGP configuration, while the
second part augments the BGP Routing Policy model in BGP Model for second part augments the BGP Routing Policy model in BGP Model for
Service Provider Network [I-D.ietf-idr-bgp-model]. Service Provider Network [I-D.ietf-idr-bgp-model].
The BGP model is augmented both at a global level to add SRv6 This model defines a new SAFI called 'srv6-mup'. The BGP model is
configuration, and at the route selection option. The BGP policy augmented both at a global level to add SRv6 configuration, and at
model is augemented to add a defined set, a set of match options, and the route selection option. The BGP policy model is augemented to
a set of actions. add a defined set, a set of match options, and a set of actions.
The model imports Common YANG Data Types [RFC6991], A YANG Data Model The model imports Common YANG Data Types [RFC6991], A YANG Data Model
for Routing Management(NMDA Version) [RFC8349], A YANG Data Model for for Routing Management(NMDA Version) [RFC8349], A YANG Data Model for
Routing Policy [RFC9067], YANG Data Model for Segment Routing Routing Policy [RFC9067], YANG Data Model for Segment Routing
[RFC9020], YANG Data Model for SRv6 Base and Static [RFC9020], YANG Data Model for SRv6 Base and Static
[I-D.ietf-spring-srv6-yang], and BGP Model for Service Provider [I-D.ietf-spring-srv6-yang], and BGP Model for Service Provider
Network [I-D.ietf-idr-bgp-model]. Network [I-D.ietf-idr-bgp-model].
<CODE BEGINS> file "ietf-srv6-mobile@2022-03-03.yang" <CODE BEGINS> file "ietf-srv6-mobile@2022-03-08.yang"
module ietf-srv6-mobile { module ietf-srv6-mobile {
yang-version "1.1"; yang-version "1.1";
namespace "urn:ietf:params:xml:ns:yang:ietf-srv6-mobile"; namespace "urn:ietf:params:xml:ns:yang:ietf-srv6-mobile";
prefix "srv6-mob"; prefix "srv6-mob";
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference reference
"RFC 6991: Common YANG Data Types."; "RFC 6991: Common YANG Data Types.";
} }
skipping to change at page 8, line 25 skipping to change at page 8, line 25
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices. for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
revision "2022-03-03" { revision "2022-03-08" {
description description
"Initial Version."; "Initial Version.";
reference reference
"RFC XXXX, A YANG Model for BGP configuration in mobile "RFC XXXX, A YANG Model for BGP configuration in mobile
networks."; networks.";
} }
/* /*
* Features * Features
*/ */
skipping to change at page 20, line 41 skipping to change at page 20, line 41
DOI 10.17487/RFC9020, May 2021, DOI 10.17487/RFC9020, May 2021,
<https://www.rfc-editor.org/info/rfc9020>. <https://www.rfc-editor.org/info/rfc9020>.
[RFC9067] Qu, Y., Tantsura, J., Lindem, A., and X. Liu, "A YANG Data [RFC9067] Qu, Y., Tantsura, J., Lindem, A., and X. Liu, "A YANG Data
Model for Routing Policy", RFC 9067, DOI 10.17487/RFC9067, Model for Routing Policy", RFC 9067, DOI 10.17487/RFC9067,
October 2021, <https://www.rfc-editor.org/info/rfc9067>. October 2021, <https://www.rfc-editor.org/info/rfc9067>.
[I-D.ietf-idr-bgp-model] [I-D.ietf-idr-bgp-model]
Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP
YANG Model for Service Provider Networks", Work in YANG Model for Service Provider Networks", Work in
Progress, Internet-Draft, draft-ietf-idr-bgp-model-12, 25 Progress, Internet-Draft, draft-ietf-idr-bgp-model-13, 6
October 2021, <https://datatracker.ietf.org/doc/html/ March 2022, <https://datatracker.ietf.org/doc/html/draft-
draft-ietf-idr-bgp-model-12>. ietf-idr-bgp-model-13>.
[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., Rajamanickam, H., Voyer, D., Matsushima, S., Horiba, K., Rajamanickam,
J., and A. AbdelSalam, "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-01, 14 January 2022, spring-srv6-yang-01, 14 January 2022,
<https://datatracker.ietf.org/doc/html/draft-ietf-spring- <https://datatracker.ietf.org/doc/html/draft-ietf-spring-
srv6-yang-01>. srv6-yang-01>.
 End of changes. 11 change blocks. 
14 lines changed or deleted 26 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/