draft-ietf-rtgwg-routing-types-05.txt   draft-ietf-rtgwg-routing-types-06.txt 
Network Working Group X. Liu Network Working Group X. Liu
Internet-Draft Jabil Internet-Draft Jabil
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: November 25, 2017 Futurewei Technologies, Inc. Expires: December 15, 2017 Futurewei Technologies, Inc.
A. Lindem A. Lindem
Cisco Systems Cisco Systems
C. Hopps C. Hopps
Deutsche Telekom Deutsche Telekom
L. Berger L. Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
May 24, 2017 June 13, 2017
Routing Area Common YANG Data Types Routing Area Common YANG Data Types
draft-ietf-rtgwg-routing-types-05 draft-ietf-rtgwg-routing-types-06
Abstract Abstract
This document defines a collection of common data types using the This document defines a collection of common data types using the
YANG data modeling language. These derived common types are designed YANG data modeling language. These derived common types are designed
to be imported by other modules defined in the routing area. to be imported by other modules defined in the routing area.
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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 November 25, 2017. This Internet-Draft will expire on December 15, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IETF Routing Types YANG Module . . . . . . . . . . . . . . . 6 3. IETF Routing Types YANG Module . . . . . . . . . . . . . . . 6
4. IANA Routing Types YANG Module . . . . . . . . . . . . . . . 18 4. IANA Routing Types YANG Module . . . . . . . . . . . . . . . 18
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
5.1. IANA-Maintained iana-routing-types Module . . . . . . . . 29 5.1. IANA-Maintained iana-routing-types Module . . . . . . . . 28
6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
8.1. Normative References . . . . . . . . . . . . . . . . . . 30 8.1. Normative References . . . . . . . . . . . . . . . . . . 30
8.2. Informative References . . . . . . . . . . . . . . . . . 31 8.2. Informative References . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
1. Introduction 1. Introduction
The YANG [RFC6020] [RFC7950] is a data modeling language used to The YANG [RFC6020] [RFC7950] is a data modeling language used to
model configuration data, state data, Remote Procedure Calls, and model configuration data, state data, Remote Procedure Calls, and
notifications for network management protocols. The YANG language notifications for network management protocols. The YANG language
supports a small set of built-in data types and provides mechanisms supports a small set of built-in data types and provides mechanisms
to derive other types from the built-in types. to derive other types from the built-in types.
This document introduces a collection of common data types derived This document introduces a collection of common data types derived
from the built-in YANG data types. The derived types are designed to from the built-in YANG data types. The derived types are designed to
be the common types applicable for modeling in the routing area. be the common types applicable for modeling in the routing area.
1.1. Requirements Language 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
1.2. Terminology
The terminology for describing YANG data models is found in The terminology for describing YANG data models is found in
[RFC7950]. [RFC7950].
2. Overview 2. Overview
This document defines the two models for common routing types, ietf- This document defines the two models for common routing types, ietf-
routing-types and iana-routing-types. The only module imports are routing-types and iana-routing-types. The only module imports are
from [RFC6991]. The ietf-routing-types model contains common routing from [RFC6991]. The ietf-routing-types model contains common routing
types other than those corresponding directly to IANA mappings. types other than those corresponding directly to IANA mappings.
skipping to change at page 6, line 26 skipping to change at page 6, line 17
[I-D.ietf-idr-bgp-model]. [I-D.ietf-idr-bgp-model].
subsequent-address-family subsequent-address-family
This type defines values for use in subsequent address family This type defines values for use in subsequent address family
(SAFI) identifiers. The values are based on the IANA Subsequent (SAFI) identifiers. The values are based on the IANA Subsequent
Address Family Identifiers (SAFI) Parameters Registry Address Family Identifiers (SAFI) Parameters Registry
[IANA-SAFI-REGISTRY]. [IANA-SAFI-REGISTRY].
3. IETF Routing Types YANG Module 3. IETF Routing Types YANG Module
<CODE BEGINS> file "ietf-routing-types@2017-05-24.yang" <CODE BEGINS> file "ietf-routing-types@2017-06-13.yang"
module ietf-routing-types { module ietf-routing-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-routing-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-routing-types";
prefix "rt-types"; prefix "rt-types";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-inet-types { import ietf-inet-types {
skipping to change at page 7, line 29 skipping to change at page 7, line 20
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2017-05-24 { revision 2017-06-13 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC TBD: Routing YANG Data Types"; "RFC TBD: Routing YANG Data Types";
} }
/*** Identities related to MPLS/GMPLS ***/ /*** Identities related to MPLS/GMPLS ***/
identity mpls-label-special-purpose-value { identity mpls-label-special-purpose-value {
description description
"Base identity for deriving identities describing "Base identity for deriving identities describing
skipping to change at page 18, line 17 skipping to change at page 18, line 4
description description
"Route Target value"; "Route Target value";
} }
leaf route-target-type { leaf route-target-type {
type rt-types:route-target-type; type rt-types:route-target-type;
mandatory true; mandatory true;
description description
"Import/export type of the Route Target."; "Import/export type of the Route Target.";
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4. IANA Routing Types YANG Module 4. IANA Routing Types YANG Module
<CODE BEGINS> file "iana-routing-types@2017-05-24.yang" <CODE BEGINS> file "iana-routing-types@2017-06-13.yang"
module iana-routing-types { module iana-routing-types {
namespace "urn:ietf:params:xml:ns:yang:iana-routing-types"; namespace "urn:ietf:params:xml:ns:yang:iana-routing-types";
prefix "iana-rt-types"; prefix "iana-rt-types";
organization "IANA"; organization "IANA";
contact contact
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
skipping to change at page 19, line 13 skipping to change at page 18, line 49
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2017-05-24 { revision 2017-06-13 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC TBD: IANA Routing YANG Data Types"; "RFC TBD: IANA Routing YANG Data Types";
} }
/*** Collection of IANA types related to routing ***/ /*** Collection of IANA types related to routing ***/
/*** IANA address family Identities ***/ /*** IANA address family Identities ***/
identity address-family { identity address-family {
skipping to change at page 30, line 32 skipping to change at page 30, line 26
Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Ebben Aries, Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Ebben Aries,
Lou Berger, Qin Wu, Rob Shakir, Xufeng Liu, and Yingzhen Qu. Lou Berger, Qin Wu, Rob Shakir, Xufeng Liu, and Yingzhen Qu.
Thanks to Martin Bjorkland, Tom Petch, Stewart Bryant, and Radek Thanks to Martin Bjorkland, Tom Petch, Stewart Bryant, and Radek
Krejci for comments on the model and document text. Krejci for comments on the model and document text.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC3688, January 2004,
DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc3688>.
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
 End of changes. 14 change blocks. 
25 lines changed or deleted 17 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/