--- 1/draft-ietf-netmod-rfc6021-bis-00.txt 2013-03-25 19:57:29.632207382 +0100 +++ 2/draft-ietf-netmod-rfc6021-bis-01.txt 2013-03-25 19:57:29.680207403 +0100 @@ -1,19 +1,19 @@ Network Working Group J. Schoenwaelder, Ed. Internet-Draft Jacobs University -Obsoletes: 6021 (if approved) February 6, 2013 +Obsoletes: 6021 (if approved) March 25, 2013 Intended status: Standards Track -Expires: August 10, 2013 +Expires: September 26, 2013 Common YANG Data Types - draft-ietf-netmod-rfc6021-bis-00 + draft-ietf-netmod-rfc6021-bis-01 Abstract This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. Status of this Memo This Internet-Draft is submitted in full conformance with the @@ -22,21 +22,21 @@ 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 August 10, 2013. + This Internet-Draft will expire on September 26, 2013. Copyright Notice Copyright (c) 2013 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 @@ -57,29 +57,29 @@ not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Core YANG Derived Types . . . . . . . . . . . . . . . . . . . 6 4. Internet-Specific Derived Types . . . . . . . . . . . . . . . 17 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 28 - 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 - 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 - 9.1. Normative References . . . . . . . . . . . . . . . . . . . 31 - 9.2. Informative References . . . . . . . . . . . . . . . . . . 31 - Appendix A. Changes from RFC 6021 . . . . . . . . . . . . . . . . 35 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 36 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 29 + 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30 + 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 9.1. Normative References . . . . . . . . . . . . . . . . . . . 32 + 9.2. Informative References . . . . . . . . . . . . . . . . . . 32 + Appendix A. Changes from RFC 6021 . . . . . . . . . . . . . . . . 36 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 37 1. Introduction YANG [RFC6020] is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF) [RFC6241]. 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 @@ -164,21 +164,21 @@ +----------------------+--------------------------------------------+ Table 2: ietf-inet-types 3. Core YANG Derived Types The ietf-yang-types YANG module references [IEEE802], [ISO9834-1], [RFC2578], [RFC2579], [RFC2856], [RFC3339], [RFC4122], [RFC4502], [RFC6020], [XPATH], and [XSD-TYPES]. - file "ietf-yang-types@2013-01-20.yang" + file "ietf-yang-types@2013-03-25.yang" module ietf-yang-types { namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types"; prefix "yang"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact @@ -204,21 +204,21 @@ 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; see the RFC itself for full legal notices."; - revision 2013-01-20 { + revision 2013-03-25 { description "This revision adds the following new data types: - yang-identifier - hex-string - uuid - dotted-quad"; reference "RFC XXXX: Common YANG Data Types"; } @@ -649,21 +649,21 @@ 4. Internet-Specific Derived Types The ietf-inet-types YANG module references [RFC0768], [RFC0791], [RFC0793], [RFC0952], [RFC1034], [RFC1123], [RFC1930], [RFC2460], [RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3492], [RFC3595], [RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291], [RFC4340], [RFC4960], [RFC5017], [RFC5891], [RFC5952], and [RFC6793]. - file "ietf-inet-types@2013-01-20.yang" + file "ietf-inet-types@2013-03-25.yang" module ietf-inet-types { namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types"; prefix "inet"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact @@ -689,21 +689,21 @@ 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; see the RFC itself for full legal notices."; - revision 2013-01-20 { + revision 2013-03-25 { description "This revision adds the following new data types: - ip-address-no-zone - ipv4-address-no-zone - ipv6-address-no-zone"; reference "RFC XXXX: Common YANG Data Types"; } revision 2010-09-24 { @@ -836,22 +836,25 @@ /*** collection of IP address and hostname related types ***/ typedef ip-address { type union { type inet:ipv4-address; type inet:ipv6-address; } description "The ip-address type represents an IP address and is IP - version neutral. The format of the textual representations - implies the IP version."; + version neutral. The format of the textual representation + implies the IP version. This type supports scoped addresses + by allowing zone identifiers in the address format."; + reference + "RFC 4007: IPv6 Scoped Address Architecture"; } typedef ipv4-address { type string { pattern '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}' + '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])' + '(%[\p{N}\p{L}]+)?'; } description @@ -908,43 +911,51 @@ RFC 5952: A Recommendation for IPv6 Address Text Representation"; } typedef ip-address-no-zone { type union { type inet:ipv4-address-no-zone; type inet:ipv6-address-no-zone; } description - "The ip-address-no-zone type represents an IP address without - zone information in an IP version neutral way. The format - of the textual representations implies the IP version."; + "The ip-address-no-zone type represents an IP address and is + IP version neutral. The format of the textual representation + implies the IP version. This type does not support scoped + addresses since it does not allow zone identifiers in the + address format."; + reference + "RFC 4007: IPv6 Scoped Address Architecture"; } typedef ipv4-address-no-zone { type inet:ipv4-address { - pattern "[\.0-9]*"; + pattern '[\.0-9]*'; } description "An IPv4 address without a zone index. This type may be used in situations where the zone is known from the context and hence no zone index is needed."; } - typedef ipv6-address-no-zone { type inet:ipv6-address { pattern '[0-9a-fA-F:]*'; } description "An IPv6 address without a zone index. This type may be used in situations where the zone is known from the context and hence no zone index is needed."; + reference + "RFC 4291: IP Version 6 Addressing Architecture + RFC 4007: IPv6 Scoped Address Architecture + RFC 5952: A Recommendation for IPv6 Address Text + Representation"; } typedef ip-prefix { type union { type inet:ipv4-prefix; type inet:ipv6-prefix; } description "The ip-prefix type represents an IP prefix and is IP version neutral. The format of the textual representations @@ -1338,19 +1347,37 @@ December 2012. [XSD-TYPES] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028, October 2004, . Appendix A. Changes from RFC 6021 - This version adds new type definitions to the YANG modules. For the - further details, see the revision statement of the YANG modules. + This version adds new type definitions to the YANG modules. The + following new data types have been added to the ietf-yang-types + module: + + o yang-identifier + + o hex-string + + o uuid + + o dotted-quad + + The following new data types have been added to the ietf-inet-types + module: + + o ip-address-no-zone + + o ipv4-address-no-zone + + o ipv6-address-no-zone Author's Address Juergen Schoenwaelder (editor) Jacobs University Email: j.schoenwaelder@jacobs-university.de