draft-ietf-netmod-rfc6021-bis-01.txt   draft-ietf-netmod-rfc6021-bis-02.txt 
Network Working Group J. Schoenwaelder, Ed. Network Working Group J. Schoenwaelder, Ed.
Internet-Draft Jacobs University Internet-Draft Jacobs University
Obsoletes: 6021 (if approved) March 25, 2013 Obsoletes: 6021 (if approved) May 8, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: September 26, 2013 Expires: November 9, 2013
Common YANG Data Types Common YANG Data Types
draft-ietf-netmod-rfc6021-bis-01 draft-ietf-netmod-rfc6021-bis-02
Abstract Abstract
This document introduces a collection of common data types to be used This document introduces a collection of common data types to be used
with the YANG data modeling language. This document obsoletes RFC with the YANG data modeling language. This document obsoletes RFC
6021. 6021.
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 33 skipping to change at page 1, line 33
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 September 26, 2013. This Internet-Draft will expire on November 9, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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
skipping to change at page 6, line 11 skipping to change at page 6, line 11
+----------------------+--------------------------------------------+ +----------------------+--------------------------------------------+
Table 2: ietf-inet-types Table 2: ietf-inet-types
3. Core YANG Derived Types 3. Core YANG Derived Types
The ietf-yang-types YANG module references [IEEE802], [ISO9834-1], The ietf-yang-types YANG module references [IEEE802], [ISO9834-1],
[RFC2578], [RFC2579], [RFC2856], [RFC3339], [RFC4122], [RFC4502], [RFC2578], [RFC2579], [RFC2856], [RFC3339], [RFC4122], [RFC4502],
[RFC6020], [XPATH], and [XSD-TYPES]. [RFC6020], [XPATH], and [XSD-TYPES].
<CODE BEGINS> file "ietf-yang-types@2013-03-25.yang" <CODE BEGINS> file "ietf-yang-types@2013-05-08.yang"
module ietf-yang-types { module ietf-yang-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types";
prefix "yang"; prefix "yang";
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
skipping to change at page 6, line 51 skipping to change at page 6, line 51
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
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.";
revision 2013-03-25 { revision 2013-05-08 {
description description
"This revision adds the following new data types: "This revision adds the following new data types:
- yang-identifier - yang-identifier
- hex-string - hex-string
- uuid - uuid
- dotted-quad"; - dotted-quad";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC XXXX: Common YANG Data Types";
} }
skipping to change at page 15, line 14 skipping to change at page 15, line 14
description of the schema node MUST specify the XPath description of the schema node MUST specify the XPath
context in which the XPath expression is evaluated."; context in which the XPath expression is evaluated.";
reference reference
"XPATH: XML Path Language (XPath) Version 1.0"; "XPATH: XML Path Language (XPath) Version 1.0";
} }
/*** collection of string types ***/ /*** collection of string types ***/
typedef hex-string { typedef hex-string {
type string { type string {
pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*'; pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?';
} }
description description
"A hexadecimal string with octets represented as hex digits "A hexadecimal string with octets represented as hex digits
separated by colons. The canonical representation uses separated by colons. The canonical representation uses
lowercase characters."; lowercase characters.";
} }
typedef uuid { typedef uuid {
type string { type string {
pattern '[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-' pattern '[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-'
skipping to change at page 17, line 13 skipping to change at page 17, line 13
<CODE ENDS> <CODE ENDS>
4. Internet-Specific Derived Types 4. Internet-Specific Derived Types
The ietf-inet-types YANG module references [RFC0768], [RFC0791], The ietf-inet-types YANG module references [RFC0768], [RFC0791],
[RFC0793], [RFC0952], [RFC1034], [RFC1123], [RFC1930], [RFC2460], [RFC0793], [RFC0952], [RFC1034], [RFC1123], [RFC1930], [RFC2460],
[RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3492], [RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3492],
[RFC3595], [RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291], [RFC3595], [RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291],
[RFC4340], [RFC4960], [RFC5017], [RFC5891], [RFC5952], and [RFC6793]. [RFC4340], [RFC4960], [RFC5017], [RFC5891], [RFC5952], and [RFC6793].
<CODE BEGINS> file "ietf-inet-types@2013-03-25.yang" <CODE BEGINS> file "ietf-inet-types@2013-05-08.yang"
module ietf-inet-types { module ietf-inet-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types";
prefix "inet"; prefix "inet";
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
skipping to change at page 18, line 5 skipping to change at page 18, line 5
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
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.";
revision 2013-03-25 { revision 2013-05-08 {
description description
"This revision adds the following new data types: "This revision adds the following new data types:
- ip-address-no-zone - ip-address-no-zone
- ipv4-address-no-zone - ipv4-address-no-zone
- ipv6-address-no-zone"; - ipv6-address-no-zone";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC XXXX: Common YANG Data Types";
} }
revision 2010-09-24 { revision 2010-09-24 {
skipping to change at page 22, line 44 skipping to change at page 22, line 44
IP version neutral. The format of the textual representation IP version neutral. The format of the textual representation
implies the IP version. This type does not support scoped implies the IP version. This type does not support scoped
addresses since it does not allow zone identifiers in the addresses since it does not allow zone identifiers in the
address format."; address format.";
reference reference
"RFC 4007: IPv6 Scoped Address Architecture"; "RFC 4007: IPv6 Scoped Address Architecture";
} }
typedef ipv4-address-no-zone { typedef ipv4-address-no-zone {
type inet:ipv4-address { type inet:ipv4-address {
pattern '[\.0-9]*'; pattern '[0-9\.]*';
} }
description description
"An IPv4 address without a zone index. This type may be used "An IPv4 address without a zone index. This type derived from
in situations where the zone is known from the context and ipv4-address may be used in situations where the zone is known
hence no zone index is needed."; from the context and hence no zone index is needed.";
} }
typedef ipv6-address-no-zone { typedef ipv6-address-no-zone {
type inet:ipv6-address { type inet:ipv6-address {
pattern '[0-9a-fA-F:]*'; pattern '[0-9a-fA-F:\.]*';
} }
description description
"An IPv6 address without a zone index. This type may be used "An IPv6 address without a zone index. This type derived from
in situations where the zone is known from the context and ipv6-address may be used in situations where the zone is known
hence no zone index is needed."; from the context and hence no zone index is needed.";
reference reference
"RFC 4291: IP Version 6 Addressing Architecture "RFC 4291: IP Version 6 Addressing Architecture
RFC 4007: IPv6 Scoped Address Architecture RFC 4007: IPv6 Scoped Address Architecture
RFC 5952: A Recommendation for IPv6 Address Text RFC 5952: A Recommendation for IPv6 Address Text
Representation"; Representation";
} }
typedef ip-prefix { typedef ip-prefix {
type union { type union {
type inet:ipv4-prefix; type inet:ipv4-prefix;
skipping to change at page 28, line 12 skipping to change at page 28, line 12
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 5. IANA Considerations
This document registers two URIs in the IETF XML registry [RFC3688]. This document registers two URIs in the IETF XML registry [RFC3688].
Following the format in RFC 3688, the following registrations have Following the format in RFC 3688, the following registrations have
been made. been made.
URI: urn:ietf:params:xml:ns:yang:ietf-yang-types URI: urn:ietf:params:xml:ns:yang:ietf-yang-types
Registrant Contact: The NETMOD WG of the IETF. Registrant Contact: The NETMOD WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-inet-types URI: urn:ietf:params:xml:ns:yang:ietf-inet-types
Registrant Contact: The NETMOD WG of the IETF. Registrant Contact: The NETMOD WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers two YANG modules in the YANG Module Names This document registers two YANG modules in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-yang-types name: ietf-yang-types
namespace: urn:ietf:params:xml:ns:yang:ietf-yang-types namespace: urn:ietf:params:xml:ns:yang:ietf-yang-types
prefix: yang prefix: yang
reference: RFC 6021 reference: RFC XXXX
name: ietf-inet-types name: ietf-inet-types
namespace: urn:ietf:params:xml:ns:yang:ietf-inet-types namespace: urn:ietf:params:xml:ns:yang:ietf-inet-types
prefix: inet prefix: inet
reference: RFC 6021 reference: RFC XXXX
6. Security Considerations 6. Security Considerations
This document defines common data types using the YANG data modeling This document defines common data types using the YANG data modeling
language. The definitions themselves have no security impact on the language. The definitions themselves have no security impact on the
Internet but the usage of these definitions in concrete YANG modules Internet but the usage of these definitions in concrete YANG modules
might have. The security considerations spelled out in the YANG might have. The security considerations spelled out in the YANG
specification [RFC6020] apply for this document as well. specification [RFC6020] apply for this document as well.
7. Contributors 7. Contributors
skipping to change at page 31, line 9 skipping to change at page 31, line 9
- Andy Bierman (Brocade) - Andy Bierman (Brocade)
- Martin Bjorklund (Tail-f Systems) - Martin Bjorklund (Tail-f Systems)
- Balazs Lengyel (Ericsson) - Balazs Lengyel (Ericsson)
- David Partain (Ericsson) - David Partain (Ericsson)
- Phil Shafer (Juniper Networks) - Phil Shafer (Juniper Networks)
8. Acknowledgments 8. Acknowledgments
The editor wishes to thank the following individuals for providing The editor wishes to thank the following individuals for providing
helpful comments on various versions of this document: Andy Bierman, helpful comments on various versions of this document: Andy Bierman,
Martin Bjorklund, Ladislav Lhotka, Lars-Johan Liman, and Dan Martin Bjorklund, Benoit Claise, Joel M. Halpern, Ladislav Lhotka,
Romascanu. Lars-Johan Liman, and Dan Romascanu.
Juergen Schoenwaelder was partly funded by Flamingo, a Network of Juergen Schoenwaelder was partly funded by Flamingo, a Network of
Excellence project (ICT-318488) supported by the European Commission Excellence project (ICT-318488) supported by the European Commission
under its Seventh Framework Programme. under its Seventh Framework Programme.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 20 change blocks. 
25 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/