draft-ietf-netmod-yang-types-08.txt   draft-ietf-netmod-yang-types-09.txt 
Network Working Group J. Schoenwaelder, Ed. Network Working Group J. Schoenwaelder, Ed.
Internet-Draft Jacobs University Internet-Draft Jacobs University
Intended status: Standards Track April 14, 2010 Intended status: Standards Track April 26, 2010
Expires: October 16, 2010 Expires: October 28, 2010
Common YANG Data Types Common YANG Data Types
draft-ietf-netmod-yang-types-08 draft-ietf-netmod-yang-types-09
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. with the YANG data modeling language.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 16, 2010. This Internet-Draft will expire on October 28, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 4, line 7 skipping to change at page 4, line 7
The derived types are generally designed to be applicable for The derived types are generally designed to be applicable for
modeling all areas of management information. modeling all areas of management information.
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]. 14, [RFC2119].
2. Overview 2. Overview
This section provides a short overview over the types defined in This section provides a short overview of the types defined in
subsequent sections and their equivalent Structure of Management subsequent sections and their equivalent Structure of Management
Information Version 2 (SMIv2) [RFC2578][RFC2579] data types. A YANG Information Version 2 (SMIv2) [RFC2578][RFC2579] data types. A YANG
data type is equivalent to an SMIv2 data type if the data types have data type is equivalent to an SMIv2 data type if the data types have
the same set of values and the semantics of the values are the same set of values and the semantics of the values are
equivalent. equivalent.
Table 1 lists the types defined in the ietf-yang-types YANG module Table 1 lists the types defined in the ietf-yang-types YANG module
and the corresponding SMIv2 types (if any). and the corresponding SMIv2 types (- indicates there is no
corresponding SMIv2 type).
ietf-yang-types ietf-yang-types
+-----------------------+--------------------------------+ +-----------------------+--------------------------------+
| YANG type | Equivalent SMIv2 type (module) | | YANG type | Equivalent SMIv2 type (module) |
+-----------------------+--------------------------------+ +-----------------------+--------------------------------+
| counter32 | Counter32 (SNMPv2-SMI) | | counter32 | Counter32 (SNMPv2-SMI) |
| zero-based-counter32 | ZeroBasedCounter32 (RMON2-MIB) | | zero-based-counter32 | ZeroBasedCounter32 (RMON2-MIB) |
| counter64 | Counter64 (SNMPv2-SMI) | | counter64 | Counter64 (SNMPv2-SMI) |
| zero-based-counter64 | ZeroBasedCounter64 (HCNUM-TC) | | zero-based-counter64 | ZeroBasedCounter64 (HCNUM-TC) |
skipping to change at page 6, line 7 skipping to change at page 6, line 7
| ipv6-prefix | - | | ipv6-prefix | - |
| domain-name | - | | domain-name | - |
| host | - | | host | - |
| uri | Uri (URI-TC-MIB) | | uri | Uri (URI-TC-MIB) |
+-----------------+-----------------------------------------------+ +-----------------+-----------------------------------------------+
Table 2 Table 2
3. Core YANG Derived Types 3. Core YANG Derived Types
<CODE BEGINS> file "ietf-yang-types@2010-04-14.yang" <CODE BEGINS> file "ietf-yang-types@2010-04-24.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 48 skipping to change at page 6, line 48
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.";
// RFC Ed.: replace XXXX with actual RFC number and remove this note // RFC Ed.: replace XXXX with actual RFC number and remove this note
revision 2010-04-14 { revision 2010-04-24 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC XXXX: Common YANG Data Types";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this note // RFC Ed.: replace XXXX with actual RFC number and remove this note
/*** collection of counter and gauge types ***/ /*** collection of counter and gauge types ***/
skipping to change at page 10, line 40 skipping to change at page 10, line 40
description description
"The object-identifier type represents administratively "The object-identifier type represents administratively
assigned names in a registration-hierarchical-name tree. assigned names in a registration-hierarchical-name tree.
Values of this type are denoted as a sequence of numerical Values of this type are denoted as a sequence of numerical
non-negative sub-identifier values. Each sub-identifier non-negative sub-identifier values. Each sub-identifier
value MUST NOT exceed 2^32-1 (4294967295). Sub-identifiers value MUST NOT exceed 2^32-1 (4294967295). Sub-identifiers
are separated by single dots and without any intermediate are separated by single dots and without any intermediate
white space. white space.
The ASN.1 standard restricts the value space of the first
sub-identifier to 0, 1, or 2. Furthermore, the value space
of the second sub-identifier is restricted to the range
0 to 39 if the first sub-identifier is 0 or 1. Finally,
the ASN.1 standard requires that an object identifier
has always at least two sub-identifier. The pattern
captures these restrictions.
Although the number of sub-identifiers is not limited, Although the number of sub-identifiers is not limited,
module designers should realize that there may be module designers should realize that there may be
implementations that stick with the SMIv2 limit of 128 implementations that stick with the SMIv2 limit of 128
sub-identifiers. sub-identifiers.
This type is a superset of the SMIv2 OBJECT IDENTIFIER type This type is a superset of the SMIv2 OBJECT IDENTIFIER type
since it is not restricted to 128 sub-identifiers. Hence, since it is not restricted to 128 sub-identifiers. Hence,
this type SHOULD NOT be used to represent the SMIv2 OBJECT this type SHOULD NOT be used to represent the SMIv2 OBJECT
IDENTIFIER type, the object-identifier-128 type SHOULD be IDENTIFIER type, the object-identifier-128 type SHOULD be
used instead."; used instead.";
skipping to change at page 11, line 33 skipping to change at page 11, line 41
/*** collection of date and time related types ***/ /*** collection of date and time related types ***/
typedef date-and-time { typedef date-and-time {
type string { type string {
pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?' pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?'
+ '(Z|[\+|-]\d{2}:\d{2})'; + '(Z|[\+|-]\d{2}:\d{2})';
} }
description description
"The date-and-time type is a profile of the ISO 8601 "The date-and-time type is a profile of the ISO 8601
standard for representation of dates and times using the standard for representation of dates and times using the
Gregorian calendar. The format is most easily described Gregorian calendar. The profile is defined by the
using the following ABFN (replacing double quotes with date-time production in section 5.6 of RFC 3339.
single quotes):
date-fullyear = 4DIGIT
date-month = 2DIGIT ; 01-12
date-mday = 2DIGIT ; 01-28, 01-29, 01-30, 01-31
time-hour = 2DIGIT ; 00-23
time-minute = 2DIGIT ; 00-59
time-second = 2DIGIT ; 00-58, 00-59, 00-60
time-secfrac = '.' 1*DIGIT
time-numoffset = ('+' / '-') time-hour ':' time-minute
time-offset = 'Z' / time-numoffset
partial-time = time-hour ':' time-minute ':' time-second
[time-secfrac]
full-date = date-fullyear '-' date-month '-' date-mday
full-time = partial-time time-offset
date-time = full-date 'T' full-time
The date-and-time type is consistent with the semantics defined The date-and-time type is compatible with the dateTime XML
in RFC 3339. The date-and-time type is compatible with the schema type with the following notable exceptions:
dateTime XML schema type with the following two notable
exceptions:
(a) The date-and-time type does not allow negative years. (a) The date-and-time type does not allow negative years.
(b) The date-and-time time-offset -00:00 indicates an unknown (b) The date-and-time time-offset -00:00 indicates an unknown
time zone (see RFC 3339) while -00:00 and +00:00 and Z all time zone (see RFC 3339) while -00:00 and +00:00 and Z all
represent the same time zone in dateTime. represent the same time zone in dateTime.
(c) The canonical format (see below) of data-and-time values (c) The canonical format (see below) of data-and-time values
differs from the canonical format used by the dateTime XML differs from the canonical format used by the dateTime XML
schema type, which requires all times to be in UTC using the schema type, which requires all times to be in UTC using the
skipping to change at page 14, line 13 skipping to change at page 13, line 48
type string { type string {
pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}'; pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}';
} }
description description
"The mac-address type represents an IEEE 802 MAC address. "The mac-address type represents an IEEE 802 MAC address.
The canonical representation uses lower-case characters. The canonical representation uses lower-case characters.
This type is in the value set and its semantics equivalent to This type is in the value set and its semantics equivalent to
the MacAddress textual convention of the SMIv2."; the MacAddress textual convention of the SMIv2.";
reference reference
"IEEE 802: IEEE Standard for Local and Metropolitan Area "IEEE 802: IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture Networks: Overview and Architecture
RFC 2579: Textual Conventions for SMIv2"; RFC 2579: Textual Conventions for SMIv2";
} }
/*** collection of XML specific types ***/ /*** collection of XML specific types ***/
typedef xpath1.0 { typedef xpath1.0 {
type string; type string;
description description
"This type represents an XPATH 1.0 expression. "This type represents an XPATH 1.0 expression.
When a schema node is defined which uses this type, the When a schema node is defined which uses this type, the
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.";
skipping to change at page 14, line 29 skipping to change at page 14, line 15
typedef xpath1.0 { typedef xpath1.0 {
type string; type string;
description description
"This type represents an XPATH 1.0 expression. "This type represents an XPATH 1.0 expression.
When a schema node is defined which uses this type, the When a schema node is defined which uses this type, the
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
"W3C REC-xpath-19991116: XML Path Language (XPath) Version 1.0"; "XPATH: XML Path Language (XPath) Version 1.0";
} }
} }
<CODE ENDS> <CODE ENDS>
4. Internet Specific Derived Types 4. Internet Specific Derived Types
<CODE BEGINS> file "ietf-inet-types@2010-04-14.yang" <CODE BEGINS> file "ietf-inet-types@2010-04-24.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 15, line 48 skipping to change at page 15, line 48
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.";
// RFC Ed.: replace XXXX with actual RFC number and remove this note // RFC Ed.: replace XXXX with actual RFC number and remove this note
revision 2010-04-14 { revision 2010-04-24 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC XXXX: Common YANG Data Types";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this note // RFC Ed.: replace XXXX with actual RFC number and remove this note
/*** collection of protocol field related types ***/ /*** collection of protocol field related types ***/
skipping to change at page 17, line 27 skipping to change at page 17, line 27
This type is in the value set and its semantics equivalent This type is in the value set and its semantics equivalent
to the IPv6FlowLabel textual convention of the SMIv2."; to the IPv6FlowLabel textual convention of the SMIv2.";
reference reference
"RFC 3595: Textual Conventions for IPv6 Flow Label "RFC 3595: Textual Conventions for IPv6 Flow Label
RFC 2460: Internet Protocol, Version 6 (IPv6) Specification"; RFC 2460: Internet Protocol, Version 6 (IPv6) Specification";
} }
typedef port-number { typedef port-number {
type uint16 { type uint16 {
range "1..65535"; range "0..65535";
} }
description description
"The port-number type represents a 16-bit port number of an "The port-number type represents a 16-bit port number of an
Internet transport layer protocol such as UDP, TCP, DCCP or Internet transport layer protocol such as UDP, TCP, DCCP or
SCTP. Port numbers are assigned by IANA. A current list of SCTP. Port numbers are assigned by IANA. A current list of
all assignments is available from <http://www.iana.org/>. all assignments is available from <http://www.iana.org/>.
Note that the value zero is not a valid port number. A union Note that the port number value zero is reserved by IANA. In
type might be used in situations where the value zero is situations where the value zero does not make sense, it can
meaningful. be excluded by subtyping the port-number type.
This type is in the value set and its semantics equivalent This type is in the value set and its semantics equivalent
to the InetPortNumber textual convention of the SMIv2."; to the InetPortNumber textual convention of the SMIv2.";
reference reference
"RFC 768: User Datagram Protocol "RFC 768: User Datagram Protocol
RFC 793: Transmission Control Protocol RFC 793: Transmission Control Protocol
RFC 4960: Stream Control Transmission Protocol RFC 4960: Stream Control Transmission Protocol
RFC 4340: Datagram Congestion Control Protocol (DCCP) RFC 4340: Datagram Congestion Control Protocol (DCCP)
RFC 4001: Textual Conventions for Internet Network Addresses"; RFC 4001: Textual Conventions for Internet Network Addresses";
} }
skipping to change at page 18, line 47 skipping to change at page 18, line 47
type inet:ipv6-address; type inet:ipv6-address;
} }
description description
"The ip-address type represents an IP address and is IP "The ip-address type represents an IP address and is IP
version neutral. The format of the textual representations version neutral. The format of the textual representations
implies the IP version."; implies the IP version.";
} }
typedef ipv4-address { typedef ipv4-address {
type string { type string {
pattern '(([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\.){3}' pattern
+ '([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])' '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
+ '(%[\p{N}\p{L}]+)?'; + '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])'
+ '(%[\p{N}\p{L}]+)?';
} }
description description
"The ipv4-address type represents an IPv4 address in "The ipv4-address type represents an IPv4 address in
dotted-quad notation. The IPv4 address may include a zone dotted-quad notation. The IPv4 address may include a zone
index, separated by a % sign. index, separated by a % sign.
The zone index is used to disambiguate identical address The zone index is used to disambiguate identical address
values. For link-local addresses, the zone index will values. For link-local addresses, the zone index will
typically be the interface index number or the name of an typically be the interface index number or the name of an
interface. If the zone index is not present, the default interface. If the zone index is not present, the default
skipping to change at page 20, line 22 skipping to change at page 20, line 24
type inet:ipv6-prefix; type inet:ipv6-prefix;
} }
description description
"The ip-prefix type represents an IP prefix and is IP "The ip-prefix type represents an IP prefix and is IP
version neutral. The format of the textual representations version neutral. The format of the textual representations
implies the IP version."; implies the IP version.";
} }
typedef ipv4-prefix { typedef ipv4-prefix {
type string { type string {
pattern '(([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\.){3}' pattern
+ '([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])' '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
+ '/(([0-9])|([1-2][0-9])|(3[0-2]))'; + '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])'
+ '/(([0-9])|([1-2][0-9])|(3[0-2]))';
} }
description description
"The ipv4-prefix type represents an IPv4 address prefix. "The ipv4-prefix type represents an IPv4 address prefix.
The prefix length is given by the number following the The prefix length is given by the number following the
slash character and must be less than or equal to 32. slash character and must be less than or equal to 32.
A prefix length value of n corresponds to an IP address A prefix length value of n corresponds to an IP address
mask which has n contiguous 1-bits from the most mask which has n contiguous 1-bits from the most
significant bit (MSB) and all other bits set to 0. significant bit (MSB) and all other bits set to 0.
skipping to change at page 22, line 23 skipping to change at page 22, line 25
The description clause of schema nodes using the domain-name The description clause of schema nodes using the domain-name
type MUST describe when and how these names are resolved to type MUST describe when and how these names are resolved to
IP addresses. Note that the resolution of a domain-name value IP addresses. Note that the resolution of a domain-name value
may require to query multiple DNS records (e.g., A for IPv4 may require to query multiple DNS records (e.g., A for IPv4
and AAAA for IPv6). The order of the resolution process and and AAAA for IPv6). The order of the resolution process and
which DNS record takes precedence can either be defined which DNS record takes precedence can either be defined
explicitely or it may depend on the configuration of the explicitely or it may depend on the configuration of the
resolver. resolver.
The canonical format for domain-name values uses the Domain-name values use the US-ASCII encoding. Their canonical
US-ASCII encoding and case-insensitive characters are set format uses lowercase US-ASCII characters. Internationalized
to lowercase."; domain names MUST be encoded in punycode as described in RFC
3492";
reference reference
"RFC 952: DoD Internet Host Table Specification "RFC 952: DoD Internet Host Table Specification
RFC 1034: Domain Names - Concepts and Facilities RFC 1034: Domain Names - Concepts and Facilities
RFC 1123: Requirements for Internet Hosts -- Application RFC 1123: Requirements for Internet Hosts -- Application
and Support and Support
RFC 2782: A DNS RR for specifying the location of services
(DNS SRV)
RFC 3490: Internationalizing Domain Names in Applications RFC 3490: Internationalizing Domain Names in Applications
(IDNA)
RFC 3492: Punycode: A Bootstring encoding of Unicode for
Internationalized Domain Names in Applications
(IDNA)"; (IDNA)";
} }
typedef host { typedef host {
type union { type union {
type inet:ip-address; type inet:ip-address;
type inet:domain-name; type inet:domain-name;
} }
description description
"The host type represents either an IP address or a DNS "The host type represents either an IP address or a DNS
skipping to change at page 28, line 12 skipping to change at page 28, line 12
helpful comments on various versions of this document: Ladislav helpful comments on various versions of this document: Ladislav
Lhotka, Lars-Johan Liman, Dan Romascanu. Lhotka, Lars-Johan Liman, Dan Romascanu.
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002.
[RFC3492] Costello, A., "Punycode: A Bootstring encoding of Unicode
for Internationalized Domain Names in Applications
(IDNA)", RFC 3492, March 2003.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
March 2005.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath)
Version 1.0", World Wide Web Consortium
Recommendation REC-xpath-19991116, November 1999,
<http://www.w3.org/TR/1999/REC-xpath-19991116>.
[YANG] Bjorklund, M., Ed., "YANG - A data modeling language for [YANG] Bjorklund, M., Ed., "YANG - A data modeling language for
NETCONF", draft-ietf-netmod-yang-12 (work in progress). NETCONF", draft-ietf-netmod-yang-12 (work in progress).
9.2. Informative References 9.2. Informative References
[IDv6TREP] [IDv6TREP]
Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", Address Text Representation",
draft-ietf-6man-text-addr-representation-06 (work in draft-ietf-6man-text-addr-representation-07 (work in
progress). progress).
[IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area [IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture", IEEE Std. 802-2001. Networks: Overview and Architecture", IEEE Std. 802-2001.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
skipping to change at page 29, line 22 skipping to change at page 29, line 45
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
Values In the Internet Protocol and Related Headers", Values In the Internet Protocol and Related Headers",
BCP 37, RFC 2780, March 2000. BCP 37, RFC 2780, March 2000.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782,
February 2000.
[RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual
Conventions for Additional High Capacity Data Types", Conventions for Additional High Capacity Data Types",
RFC 2856, June 2000. RFC 2856, June 2000.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information
Base for the Differentiated Services Architecture", Base for the Differentiated Services Architecture",
RFC 3289, May 2002. RFC 3289, May 2002.
[RFC3305] Mealling, M. and R. Denenberg, "Report from the Joint W3C/ [RFC3305] Mealling, M. and R. Denenberg, "Report from the Joint W3C/
IETF URI Planning Interest Group: Uniform Resource IETF URI Planning Interest Group: Uniform Resource
Identifiers (URIs), URLs, and Uniform Resource Names Identifiers (URIs), URLs, and Uniform Resource Names
(URNs): Clarifications and Recommendations", RFC 3305, (URNs): Clarifications and Recommendations", RFC 3305,
August 2002. August 2002.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002.
[RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello,
"Internationalizing Domain Names in Applications (IDNA)", "Internationalizing Domain Names in Applications (IDNA)",
RFC 3490, March 2003. RFC 3490, March 2003.
[RFC3595] Wijnen, B., "Textual Conventions for IPv6 Flow Label", [RFC3595] Wijnen, B., "Textual Conventions for IPv6 Flow Label",
RFC 3595, September 2003. RFC 3595, September 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
March 2005.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram
Congestion Control Protocol (DCCP)", RFC 4340, March 2006. Congestion Control Protocol (DCCP)", RFC 4340, March 2006.
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management [RFC4502] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2", RFC 4502, May 2006. Information Base Version 2", RFC 4502, May 2006.
[RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741, [RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741,
December 2006. December 2006.
[RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS
 End of changes. 30 change blocks. 
66 lines changed or deleted 76 lines changed or added

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