draft-ietf-teas-yang-te-types-12.txt   draft-ietf-teas-yang-te-types-13.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: May 5, 2020 Cisco Systems Inc Expires: May 21, 2020 Cisco Systems Inc
X. Liu X. Liu
Volta Networks Volta Networks
V. Beeram V. Beeram
Juniper Networks Juniper Networks
I. Bryskin I. Bryskin
Individual Individual
November 02, 2019 November 18, 2019
Traffic Engineering Common YANG Types Traffic Engineering Common YANG Types
draft-ietf-teas-yang-te-types-12 draft-ietf-teas-yang-te-types-13
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 May 5, 2020. This Internet-Draft will expire on May 21, 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 25 skipping to change at page 2, line 25
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 . . . . . . . . . . . . . . . . . 67 5. Packet TE Types YANG Module . . . . . . . . . . . . . . . . . 67
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76
7. Security Considerations . . . . . . . . . . . . . . . . . . . 77 7. Security Considerations . . . . . . . . . . . . . . . . . . . 77
8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 77 8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 77
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 77 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 78
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 78 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 78
10.1. Normative References . . . . . . . . . . . . . . . . . . 78 10.1. Normative References . . . . . . . . . . . . . . . . . . 78
10.2. Informative References . . . . . . . . . . . . . . . . . 79 10.2. Informative References . . . . . . . . . . . . . . . . . 79
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 86 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
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], [G709]. [RFC7951], [G709].
<CODE BEGINS> file "ietf-te-types@2019-11-02.yang" <CODE BEGINS> file "ietf-te-types@2019-11-18.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 38 skipping to change at page 10, line 38
(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-11-02" { revision "2019-11-18" {
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 {
type yang:hex-string { type yang:hex-string {
/* 01:02:03:04 */ /* 01:02:03:04 */
length "1..11"; length "1..11";
} }
description description
"Administrative group/Resource class/Color representation in "Administrative group/Resource class/Color representation in
hex-string type. hex-string type.
The Most Significant Byte (MSB) is the farthest to the The Most Significant Byte (MSB) is the farthest to the left
left in the byte sequence."; in the byte sequence. Leading zero bytes in the configured
value may be omitted for brevity.";
reference "RFC3630 and RFC5305"; reference "RFC3630 and RFC5305";
} }
typedef admin-groups { typedef admin-groups {
type union { type union {
type admin-group; type admin-group;
type extended-admin-group; type extended-admin-group;
} }
description "TE administrative group derived type"; description "TE administrative group derived type";
} }
typedef extended-admin-group { typedef extended-admin-group {
type yang:hex-string; type yang:hex-string;
description description
"Extended administrative group/Resource class/Color "Extended administrative group/Resource class/Color
representation in hex-string type. representation in hex-string type.
The MSB is the farthest to the left in the byte sequence."; The MSB is the farthest to the left in the byte sequence.
Leading zero bytes in the configured value may be omitted
for brevity.";
reference "RFC7308"; reference "RFC7308";
} }
typedef path-attribute-flags { typedef path-attribute-flags {
type union { type union {
type identityref { type identityref {
base session-attributes-flags; base session-attributes-flags;
} }
type identityref { type identityref {
base lsp-attributes-flags; base lsp-attributes-flags;
skipping to change at page 57, line 18 skipping to change at page 57, line 20
} }
} }
leaf range-bitmap { leaf range-bitmap {
type yang:hex-string; type yang:hex-string;
description description
"When there are gaps between label-start and label-end, "When there are gaps between label-start and label-end,
this attribute is used to specify the positions this attribute is used to specify the positions
of the used labels. This is represented in big-endian as of the used labels. This is represented in big-endian as
hex-string. hex-string.
The MSB is the farthest to the left in the byte sequence. The MSB is the farthest to the left in the byte sequence.
Leading zero bytes in the configured value may be omitted
for brevity.
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
skipping to change at page 67, line 49 skipping to change at page 68, line 5
<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-11-02.yang" <CODE BEGINS> file "ietf-te-packet-types@2019-11-18.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 69, line 20 skipping to change at page 69, line 23
(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-11-02" { revision "2019-11-18" {
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. 12 change blocks. 
12 lines changed or deleted 17 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/