< draft-ietf-netmod-rfc6991-bis-07.txt   draft-ietf-netmod-rfc6991-bis-08.txt >
Network Working Group J. Schoenwaelder, Ed. Network Working Group J. Schoenwaelder, Ed.
Internet-Draft Jacobs University Internet-Draft Jacobs University
Obsoletes: 6991 (if approved) July 9, 2021 Obsoletes: 6991 (if approved) November 7, 2021
Intended status: Standards Track Intended status: Standards Track
Expires: January 10, 2022 Expires: May 11, 2022
Common YANG Data Types Common YANG Data Types
draft-ietf-netmod-rfc6991-bis-07 draft-ietf-netmod-rfc6991-bis-08
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
6991. 6991.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 January 10, 2022. This Internet-Draft will expire on May 11, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 5, line 38 skipping to change at page 5, line 38
+----------------------+--------------------------------------------+ +----------------------+--------------------------------------------+
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],
[RFC7950], [RFC8294], [XPATH], and [XSD-TYPES]. [RFC7950], [RFC8294], [XPATH], and [XSD-TYPES].
<CODE BEGINS> file "ietf-yang-types@2021-07-09.yang" <CODE BEGINS> file "ietf-yang-types@2021-11-07.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 Network Modeling (NETMOD) Working Group"; "IETF Network Modeling (NETMOD) Working Group";
contact contact
skipping to change at page 6, line 29 skipping to change at page 6, line 29
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
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision 2021-07-09 { revision 2021-11-07 {
description description
"This revision adds the following new data types: "This revision adds the following new data types:
- date, time - date, time
- hours32, minutes32, seconds32, centiseconds32, milliseconds32, - hours32, minutes32, seconds32, centiseconds32, milliseconds32,
- microseconds32, microseconds64, nanoseconds32, nanoseconds64 - microseconds32, microseconds64, nanoseconds32, nanoseconds64
- revision-identifier - revision-identifier
- percent, percent-i32, percent-u32"; - percent, percent-i32, percent-u32";
reference reference
"RFC XXXX: Common YANG Data Types"; "RFC XXXX: Common YANG Data Types";
} }
skipping to change at page 14, line 16 skipping to change at page 14, line 16
reference reference
"RFC 3339: Date and Time on the Internet: Timestamps "RFC 3339: Date and Time on the Internet: Timestamps
XSD-TYPES: XML Schema Definition Language (XSD) 1.1 XSD-TYPES: XML Schema Definition Language (XSD) 1.1
Part 2: Datatypes"; Part 2: Datatypes";
} }
typedef hours32 { typedef hours32 {
type int32; type int32;
units "hours"; units "hours";
description description
"A period of time, measured in units of hours. "A period of time, measured in units of hours.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [89478485 days 08:00:00 to 89478485 days 07:00:00]. range [-89478485 days 08:00:00 to 89478485 days 07:00:00].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef minutes32 { typedef minutes32 {
type int32; type int32;
units "minutes"; units "minutes";
description description
"A period of time, measured in units of minutes. "A period of time, measured in units of minutes.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-1491308 days 2:08:00 to 1491308 days 2:07:00]. range [-1491308 days 2:08:00 to 1491308 days 2:07:00].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef seconds32 { typedef seconds32 {
type int32; type int32;
units "seconds"; units "seconds";
description description
"A period of time, measured in units of seconds. "A period of time, measured in units of seconds.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-24855 days 03:14:08 to 24855 days 03:14:07]. range [-24855 days 03:14:08 to 24855 days 03:14:07].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef centiseconds32 { typedef centiseconds32 {
type int32; type int32;
units "centiseconds"; units "centiseconds";
description description
"A period of time, measured in units of 10^-2 seconds. "A period of time, measured in units of 10^-2 seconds.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-248 days 13:13:56 to 248 days 13:13:56]. range [-248 days 13:13:56 to 248 days 13:13:56].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef milliseconds32 { typedef milliseconds32 {
type int32; type int32;
units "milliseconds"; units "milliseconds";
description description
"A period of time, measured in units of 10^-3 seconds. "A period of time, measured in units of 10^-3 seconds.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-24 days 20:31:23 to 24 days 20:31:23]. range [-24 days 20:31:23 to 24 days 20:31:23].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef microseconds32 { typedef microseconds32 {
type int32; type int32;
units "microseconds"; units "microseconds";
description description
"A period of time, measured in units of 10^-6 seconds. "A period of time, measured in units of 10^-6 seconds.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-00:35:47 to 00:35:47]. range [-00:35:47 to 00:35:47].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef microseconds64 { typedef microseconds64 {
type int64; type int64;
units "microseconds"; units "microseconds";
description description
"A period of time, measured in units of 10^-6 seconds. "A period of time, measured in units of 10^-6 seconds.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-106751991 days 04:00:54 to 106751991 days 04:00:54]. range [-106751991 days 04:00:54 to 106751991 days 04:00:54].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef nanoseconds32 { typedef nanoseconds32 {
type int32; type int32;
units "nanoseconds"; units "nanoseconds";
description description
"A period of time, measured in units of 10^-9 seconds. "A period of time, measured in units of 10^-9 seconds.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-00:00:02 to 00:00:02]. range [-00:00:02 to 00:00:02].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef nanoseconds64 { typedef nanoseconds64 {
type int64; type int64;
units "nanoseconds"; units "nanoseconds";
description description
"A period of time, measured in units of 10^-9 seconds. "A period of time, measured in units of 10^-9 seconds.
The maximum time period that can be expressed is in the The maximum time period that can be expressed is in the
range [-106753 days 23:12:44 to 106752 days 0:47:16]. range [-106753 days 23:12:44 to 106752 days 0:47:16].
This type should be range restricted in situations This type should be range restricted in situations
where only non-negative time periods are desirable, where only non-negative time periods are desirable,
(i.e., range '0..max')."; (i.e., range '0..max').";
} }
typedef timeticks { typedef timeticks {
type uint32; type uint32;
description description
"The timeticks type represents a non-negative integer that "The timeticks type represents a non-negative integer that
represents the time, modulo 2^32 (4294967296 decimal), in represents the time, modulo 2^32 (4294967296 decimal), in
hundredths of a second between two epochs. When a schema hundredths of a second between two epochs. When a schema
node is defined that uses this type, the description of node is defined that uses this type, the description of
the schema node identifies both of the reference epochs. the schema node identifies both of the reference epochs.
skipping to change at page 21, line 20 skipping to change at page 21, line 20
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], [RFC2317], [RFC0793], [RFC0952], [RFC1034], [RFC1123], [RFC1930], [RFC2317],
[RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3595], [RFC2474], [RFC2780], [RFC2782], [RFC3289], [RFC3305], [RFC3595],
[RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291], [RFC4340], [RFC3986], [RFC4001], [RFC4007], [RFC4271], [RFC4291], [RFC4340],
[RFC4592] [RFC4960], [RFC5017], [RFC5322], [RFC5890], [RFC5952], [RFC4592] [RFC4960], [RFC5017], [RFC5322], [RFC5890], [RFC5952],
[RFC6793], and [RFC8200]. [RFC6793], and [RFC8200].
<CODE BEGINS> file "ietf-inet-types@2021-07-09.yang" <CODE BEGINS> file "ietf-inet-types@2021-11-07.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 Network Modeling (NETMOD) Working Group"; "IETF Network Modeling (NETMOD) Working Group";
contact contact
skipping to change at page 22, line 12 skipping to change at page 22, line 12
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
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision 2021-07-09 { revision 2021-11-07 {
description description
"This revision adds the following new data types: "This revision adds the following new data types:
- inet:ip-address-and-prefix - inet:ip-address-and-prefix
- inet:ipv4-address-and-prefix - inet:ipv4-address-and-prefix
- inet:ipv6-address-and-prefix - inet:ipv6-address-and-prefix
- inet:protocol-number - inet:protocol-number
- inet:host-name - inet:host-name
- inet:email-address - inet:email-address
The inet:host union was changed to use inet:host-name instead The inet:host union was changed to use inet:host-name instead
of inet:domain-name."; of inet:domain-name.";
 End of changes. 35 change blocks. 
62 lines changed or deleted 62 lines changed or added

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