< draft-ietf-teas-yang-te-types-09.txt   draft-ietf-teas-yang-te-types-10.txt >
TEAS Working Group T. Saad TEAS Working Group T. Saad
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track R. Gandhi Intended status: Standards Track R. Gandhi
Expires: November 3, 2019 Cisco Systems Inc Expires: January 6, 2020 Cisco Systems Inc
X. Liu X. Liu
Volta Networks Volta Networks
V. Beeram V. Beeram
Juniper Networks Juniper Networks
I. Bryskin I. Bryskin
Huawei Technologies Huawei Technologies
May 02, 2019 July 05, 2019
Traffic Engineering Common YANG Types Traffic Engineering Common YANG Types
draft-ietf-teas-yang-te-types-09 draft-ietf-teas-yang-te-types-10
Abstract Abstract
This document defines a collection of common data types and groupings This document defines a collection of common data types and groupings
in YANG data modeling language. These derived common types and in YANG data modeling language. These derived common types and
groupings are intended to be imported by modules that model Traffic groupings are intended to be imported by modules that model Traffic
Engineering (TE) configuration and state capabilities. Engineering (TE) configuration and state capabilities.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 November 3, 2019. This Internet-Draft will expire on January 6, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 2, line 21 skipping to change at page 2, line 21
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3
2. Acronyms and Abbreviations . . . . . . . . . . . . . . . . . 3 2. Acronyms and Abbreviations . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. TE Types Module Contents . . . . . . . . . . . . . . . . 4 3.1. TE Types Module Contents . . . . . . . . . . . . . . . . 4
3.2. Packet TE Types Module Contents . . . . . . . . . . . . . 8 3.2. Packet TE Types Module Contents . . . . . . . . . . . . . 8
4. TE Types YANG Module . . . . . . . . . . . . . . . . . . . . 8 4. TE Types YANG Module . . . . . . . . . . . . . . . . . . . . 8
5. Packet TE Types YANG Module . . . . . . . . . . . . . . . . . 69 5. Packet TE Types YANG Module . . . . . . . . . . . . . . . . . 68
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 78 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76
7. Security Considerations . . . . . . . . . . . . . . . . . . . 78 7. Security Considerations . . . . . . . . . . . . . . . . . . . 77
8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 79 8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 77
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 79 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 78
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 79 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 78
10.1. Normative References . . . . . . . . . . . . . . . . . . 79 10.1. Normative References . . . . . . . . . . . . . . . . . . 78
10.2. Informative References . . . . . . . . . . . . . . . . . 81 10.2. Informative References . . . . . . . . . . . . . . . . . 79
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 86
1. Introduction 1. Introduction
YANG [RFC6020] and [RFC7950] is a data modeling language used to YANG [RFC6020] and [RFC7950] is a data modeling language used to
model configuration data, state data, Remote Procedure Calls, and model configuration data, state data, Remote Procedure Calls, and
notifications for network management protocols such as NETCONF notifications for network management protocols such as NETCONF
[RFC6241]. The YANG language supports a small set of built-in data [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 and provides mechanisms to derive other types from the built-in
types. types.
skipping to change at page 9, line 11 skipping to change at page 9, line 11
o ietf-yang-types and ietf-inet-types defined in [RFC6991] o ietf-yang-types and ietf-inet-types defined in [RFC6991]
o ietf-routing-types defined in [RFC8294] o ietf-routing-types defined in [RFC8294]
In addition to the references cross-referenced in Section 3.1, this In addition to the references cross-referenced in Section 3.1, this
model also references the following RFCs in defining the types and model also references the following RFCs in defining the types and
YANG grouping of the YANG module: [RFC3272], [RFC4202], [RFC4328], YANG grouping of the YANG module: [RFC3272], [RFC4202], [RFC4328],
[RFC4657], [RFC5817], [RFC6004], [RFC6511], [RFC6205], [RFC7139], [RFC4657], [RFC5817], [RFC6004], [RFC6511], [RFC6205], [RFC7139],
[RFC7308], [RFC7551], [RFC7571], [RFC7579], [RFC4090], [RFC4561] and [RFC7308], [RFC7551], [RFC7571], [RFC7579], [RFC4090], [RFC4561] and
[RFC7951]. [RFC7951].
<CODE BEGINS> file "ietf-te-types@2019-04-09.yang" <CODE BEGINS> file "ietf-te-types@2019-07-05.yang"
module ietf-te-types { module ietf-te-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-types";
/* Replace with IANA when assigned */ /* Replace with IANA when assigned */
prefix "te-types"; prefix "te-types";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference "RFC6991: Common YANG Data Types"; reference "RFC6991: Common YANG Data Types";
skipping to change at page 10, line 44 skipping to change at page 10, line 44
(https://trustee.ietf.org/license-info). (https://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 // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2019-04-09" { revision "2019-07-05" {
description "Latest revision of TE types"; description "Latest revision of TE types";
reference reference
"RFC XXXX: A YANG Data Model for Common Traffic Engineering "RFC XXXX: A YANG Data Model for Common Traffic Engineering
Types"; Types";
} }
/** /**
* Typedefs * Typedefs
*/ */
typedef admin-group { typedef admin-group {
skipping to change at page 43, line 35 skipping to change at page 43, line 35
base path-computation-srlg-type; base path-computation-srlg-type;
description description
"Include preferred SRLG check in path computation"; "Include preferred SRLG check in path computation";
} }
identity srlg-weighted { identity srlg-weighted {
base path-computation-srlg-type; base path-computation-srlg-type;
description description
"Include weighted SRLG check in path computation"; "Include weighted SRLG check in path computation";
} }
identity otn-rate-type {
description
"Base type to identify OTN bit rates of various information
structures.";
}
identity odu0 {
base otn-rate-type;
description
"ODU0 bit rate.";
reference "RFC7139";
}
identity odu1 {
base otn-rate-type;
description
"ODU1 bit rate.";
reference "RFC7139";
}
identity odu2 {
base otn-rate-type;
description
"ODU2 bit rate.";
reference "RFC7139";
}
identity odu3 {
base otn-rate-type;
description
"ODU3 bit rate.";
reference "RFC7139";
}
identity odu4 {
base otn-rate-type;
description
"ODU4 bit rate.";
reference "RFC7139";
}
identity odu2e {
base otn-rate-type;
description
"ODU2e bit rate.";
reference "RFC7139";
}
identity oducn {
base otn-rate-type;
description
"ODUCn bit rate.";
reference "RFC7139";
}
identity oduflex {
base otn-rate-type;
description
"ODUflex bit rate.";
reference "RFC7139";
}
identity wdm-spectrum-type {
description
"Base type to identify WDM spectrum type.";
}
identity cwdm {
base wdm-spectrum-type;
description "CWDM.";
reference "RFC6205";
}
identity dwdm {
base wdm-spectrum-type;
description "DWDM.";
reference "RFC6205";
}
identity flexible-grid {
base wdm-spectrum-type;
description "Flexible grid.";
reference "RFC6205";
}
/** /**
* TE bandwidth groupings * TE bandwidth groupings
**/ **/
grouping te-bandwidth { grouping te-bandwidth {
description description
"This grouping defines the generic TE bandwidth. "This grouping defines the generic TE bandwidth.
For some known data plane technologies, specific modeling For some known data plane technologies, specific modeling
structures are specified. The string encoded te-bandwidth structures are specified. The string encoded te-bandwidth
type is used for un-specified technologies. type is used for un-specified technologies.
The modeling structure can be augmented later for other The modeling structure can be augmented later for other
skipping to change at page 59, line 15 skipping to change at page 57, line 36
Each bit-position in the range-bitmap hex-string maps to a Each bit-position in the range-bitmap hex-string maps to a
label in the range derived from the label-start. label in the range derived from the label-start.
For example, assuming label-start=16000 and For example, assuming label-start=16000 and
range-bitmap=0x01000001, then: range-bitmap=0x01000001, then:
- bit-position(0) is set, and the corresponding mapped label - bit-position(0) is set, and the corresponding mapped label
from the range is: 16000 + (0 * label-step) or from the range is: 16000 + (0 * label-step) or
16000 for default label-step=1. 16000 for default label-step=1.
- bit-position(24) is set, and the corresponding mapped label - bit-position(24) is set, and the corresponding mapped label
from the range is: 16000 + (24 * label-step) or from the range is: 16000 + (24 * label-step) or
16024 for defautl label-step=1"; 16024 for default label-step=1";
} }
} }
grouping label-set-info { grouping label-set-info {
description description
"Grouping for List of label restrictions specifying what labels "Grouping for List of label restrictions specifying what labels
may or may not be used on a link connectivity."; may or may not be used on a link connectivity.";
container label-restrictions { container label-restrictions {
description description
"The label restrictions container"; "The label restrictions container";
skipping to change at page 69, line 35 skipping to change at page 68, line 11
<CODE ENDS> <CODE ENDS>
Figure 1: TE basic types YANG module Figure 1: TE basic types YANG module
5. Packet TE Types YANG Module 5. Packet TE Types YANG Module
The ietf-te-packet-types module imports from the following modules: The ietf-te-packet-types module imports from the following modules:
o ietf-te-types defined in this document. o ietf-te-types defined in this document.
<CODE BEGINS> file "ietf-te-packet-types@2019-04-09.yang" <CODE BEGINS> file "ietf-te-packet-types@2019-07-05.yang"
module ietf-te-packet-types { module ietf-te-packet-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-packet-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-packet-types";
/* Replace with IANA when assigned */ /* Replace with IANA when assigned */
prefix "te-packet-types"; prefix "te-packet-types";
/* Import TE generic types */ /* Import TE generic types */
import ietf-te-types { import ietf-te-types {
prefix te-types; prefix te-types;
skipping to change at page 71, line 12 skipping to change at page 69, line 35
(https://trustee.ietf.org/license-info). (https://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 // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2019-04-09" { revision "2019-07-05" {
description "Latest revision of TE MPLS types"; description "Latest revision of TE MPLS types";
reference reference
"RFC XXXX: A YANG Data Model for Common Traffic Engineering "RFC XXXX: A YANG Data Model for Common Traffic Engineering
Types"; Types";
} }
/** /**
* Typedefs * Typedefs
*/ */
typedef te-bandwidth-requested-type { typedef te-bandwidth-requested-type {
 End of changes. 11 change blocks. 
92 lines changed or deleted 18 lines changed or added

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