--- 1/draft-ietf-rtgwg-routing-types-05.txt 2017-06-13 09:13:13.533673169 -0700 +++ 2/draft-ietf-rtgwg-routing-types-06.txt 2017-06-13 09:13:13.593674597 -0700 @@ -1,25 +1,25 @@ Network Working Group X. Liu Internet-Draft Jabil Intended status: Standards Track Y. Qu -Expires: November 25, 2017 Futurewei Technologies, Inc. +Expires: December 15, 2017 Futurewei Technologies, Inc. A. Lindem Cisco Systems C. Hopps Deutsche Telekom L. Berger LabN Consulting, L.L.C. - May 24, 2017 + June 13, 2017 Routing Area Common YANG Data Types - draft-ietf-rtgwg-routing-types-05 + draft-ietf-rtgwg-routing-types-06 Abstract This document defines a collection of common data types using the YANG data modeling language. These derived common types are designed to be imported by other modules defined in the routing area. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -28,74 +28,66 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 - 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 - 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 - 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 + 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. IETF Routing Types YANG Module . . . . . . . . . . . . . . . 6 4. IANA Routing Types YANG Module . . . . . . . . . . . . . . . 18 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 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 8.1. Normative References . . . . . . . . . . . . . . . . . . 30 8.2. Informative References . . . . . . . . . . . . . . . . . 31 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32 1. Introduction The YANG [RFC6020] [RFC7950] is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. The YANG language supports a small set of built-in data types and provides mechanisms to derive other types from the built-in types. This document introduces a collection of common data types derived from the built-in YANG data types. The derived types are designed to be the common types applicable for modeling in the routing area. -1.1. Requirements Language - - 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 +1.1. Terminology The terminology for describing YANG data models is found in [RFC7950]. 2. Overview This document defines the two models for common routing types, ietf- routing-types and iana-routing-types. The only module imports are from [RFC6991]. The ietf-routing-types model contains common routing types other than those corresponding directly to IANA mappings. @@ -251,21 +243,21 @@ [I-D.ietf-idr-bgp-model]. subsequent-address-family This type defines values for use in subsequent address family (SAFI) identifiers. The values are based on the IANA Subsequent Address Family Identifiers (SAFI) Parameters Registry [IANA-SAFI-REGISTRY]. 3. IETF Routing Types YANG Module - file "ietf-routing-types@2017-05-24.yang" + file "ietf-routing-types@2017-06-13.yang" module ietf-routing-types { namespace "urn:ietf:params:xml:ns:yang:ietf-routing-types"; prefix "rt-types"; import ietf-yang-types { prefix "yang"; } import ietf-inet-types { @@ -302,21 +294,21 @@ 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; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2017-05-24 { + revision 2017-06-13 { description "Initial revision."; reference "RFC TBD: Routing YANG Data Types"; } /*** Identities related to MPLS/GMPLS ***/ identity mpls-label-special-purpose-value { description "Base identity for deriving identities describing @@ -818,27 +808,28 @@ description "Route Target value"; } leaf route-target-type { type rt-types:route-target-type; mandatory true; description "Import/export type of the Route Target."; } } + } } 4. IANA Routing Types YANG Module - file "iana-routing-types@2017-05-24.yang" + file "iana-routing-types@2017-06-13.yang" module iana-routing-types { namespace "urn:ietf:params:xml:ns:yang:iana-routing-types"; prefix "iana-rt-types"; organization "IANA"; contact " Internet Assigned Numbers Authority @@ -862,21 +853,21 @@ 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; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2017-05-24 { + revision 2017-06-13 { description "Initial revision."; reference "RFC TBD: IANA Routing YANG Data Types"; } /*** Collection of IANA types related to routing ***/ /*** IANA address family Identities ***/ identity address-family { @@ -1406,24 +1396,23 @@ Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Ebben Aries, Lou Berger, Qin Wu, Rob Shakir, Xufeng Liu, and Yingzhen Qu. Thanks to Martin Bjorkland, Tom Petch, Stewart Bryant, and Radek Krejci for comments on the model and document text. 8. References 8.1. Normative References - [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, - DOI 10.17487/RFC2119, March 1997, - . + [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, + DOI 10.17487/RFC3688, January 2004, + . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, .