< draft-ietf-rtgwg-routing-types-10.txt   draft-ietf-rtgwg-routing-types-11.txt >
Network Working Group X. Liu Network Working Group X. Liu
Internet-Draft Jabil Internet-Draft Jabil
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: March 6, 2018 Futurewei Technologies, Inc. Expires: March 15, 2018 Futurewei Technologies, Inc.
A. Lindem A. Lindem
Cisco Systems Cisco Systems
C. Hopps C. Hopps
Deutsche Telekom Deutsche Telekom
L. Berger L. Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
September 2, 2017 September 11, 2017
Routing Area Common YANG Data Types Routing Area Common YANG Data Types
draft-ietf-rtgwg-routing-types-10 draft-ietf-rtgwg-routing-types-11
Abstract Abstract
This document defines a collection of common data types using the This document defines a collection of common data types using the
YANG data modeling language. These derived common types are designed YANG data modeling language. These derived common types are designed
to be imported by other modules defined in the routing area. to be imported by other modules defined in the routing area.
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 39 skipping to change at page 1, line 39
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 March 6, 2018. This Internet-Draft will expire on March 15, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 45 skipping to change at page 6, line 45
[I-D.ietf-idr-bgp-model]. [I-D.ietf-idr-bgp-model].
subsequent-address-family subsequent-address-family
This type defines values for use in subsequent address family This type defines values for use in subsequent address family
(SAFI) identifiers. The values are based on the IANA Subsequent (SAFI) identifiers. The values are based on the IANA Subsequent
Address Family Identifiers (SAFI) Parameters Registry Address Family Identifiers (SAFI) Parameters Registry
[IANA-SAFI-REGISTRY]. [IANA-SAFI-REGISTRY].
3. IETF Routing Types YANG Module 3. IETF Routing Types YANG Module
<CODE BEGINS> file "ietf-routing-types@2017-09-02.yang" <CODE BEGINS> file "ietf-routing-types@2017-09-11.yang"
module ietf-routing-types { module ietf-routing-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-routing-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-routing-types";
prefix rt-types; prefix rt-types;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
skipping to change at page 7, line 44 skipping to change at page 7, line 44
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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2017-09-02 { revision 2017-09-11 {
description "Initial revision."; description "Initial revision.";
reference "RFC TBD: Routing YANG Data Types"; reference "RFC TBD: Routing YANG Data Types";
} }
/*** Identities related to MPLS/GMPLS ***/ /*** Identities related to MPLS/GMPLS ***/
identity mpls-label-special-purpose-value { identity mpls-label-special-purpose-value {
description description
"Base identity for deriving identities describing "Base identity for deriving identities describing
special-purpose Multiprotocol Label Switching (MPLS) label special-purpose Multiprotocol Label Switching (MPLS) label
skipping to change at page 21, line 6 skipping to change at page 21, line 6
description description
"The 20-bit label values in an MPLS label stack entry, "The 20-bit label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live)."; the encodings of Traffic Class and TTL (time to live).";
reference "RFC3032: MPLS Label Stack Encoding."; reference "RFC3032: MPLS Label Stack Encoding.";
} }
/*** Groupings **/ /*** Groupings **/
grouping mpls-label-stack { grouping mpls-label-stack {
description description
"This grouping specifies an MPLS label stack. List "This grouping specifies an MPLS label stack. The label
entries are in ascending order of ID with the first entry stack is encoded as a list of label stack entries. The
being the leftmost label in the Network-Byte-Order (NBO) list key is an identifier which indicates relative
MPLS header, i.e., the top of the label stack. The next ordering of each entry, with the lowest value identifier
entry is the next label in MPLS header label stack, and corresponding to the top of the label stack.";
so on.";
container mpls-label-stack { container mpls-label-stack {
description description
"Container for a list of MPLS label stack entries."; "Container for a list of MPLS label stack entries.";
list entry { list entry {
key "id"; key "id";
description description
"List of MPLS label stack entries."; "List of MPLS label stack entries.";
leaf id { leaf id {
type uint8; type uint8;
description description
"Identifies the entry in a sequence of an MPLS label "Identifies the entry in a sequence of MPLS label
stack entries. An entry with smaller ID value stack entries. An entry with a smaller identifier
precedes an entry with a larger value in the value precedes an entry with a larger identifier
Network-Byte-Order (NBO) MPLS header. The value of value in the label stack. The value of this ID has
this ID has no semantic meaning other than ordering no semantic meaning other than relative ordering
and referencing the entry."; and referencing the entry.";
} }
leaf label { leaf label {
type rt-types:mpls-label; type rt-types:mpls-label;
description description
"Label value."; "Label value.";
} }
leaf ttl { leaf ttl {
type uint8; type uint8;
description description
skipping to change at page 22, line 39 skipping to change at page 22, line 38
"Import/export type of the Route Target."; "Import/export type of the Route Target.";
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4. IANA Routing Types YANG Module 4. IANA Routing Types YANG Module
<CODE BEGINS> file "iana-routing-types@2017-09-02.yang" <CODE BEGINS> file "iana-routing-types@2017-09-11.yang"
module iana-routing-types { module iana-routing-types {
namespace "urn:ietf:params:xml:ns:yang:iana-routing-types"; namespace "urn:ietf:params:xml:ns:yang:iana-routing-types";
prefix iana-rt-types; prefix iana-rt-types;
organization organization
"IANA"; "IANA";
contact contact
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
skipping to change at page 23, line 26 skipping to change at page 23, line 24
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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2017-09-02 { revision 2017-09-11 {
description "Initial revision."; description "Initial revision.";
reference "RFC TBD: IANA Routing YANG Data Types"; reference "RFC TBD: IANA Routing YANG Data Types";
} }
/*** Collection of IANA types related to routing ***/ /*** Collection of IANA types related to routing ***/
/*** IANA address family enumeration ***/ /*** IANA address family enumeration ***/
typedef address-family { typedef address-family {
type enumeration { type enumeration {
enum ipv4 { enum ipv4 {
skipping to change at page 31, line 25 skipping to change at page 31, line 25
value 134; value 134;
description "IPv4 VPN Flow Specification SAFI"; description "IPv4 VPN Flow Specification SAFI";
} }
enum vpn-auto-discovery-safi { enum vpn-auto-discovery-safi {
value 140; value 140;
description "VPN Auto-Discovery SAFI"; description "VPN Auto-Discovery SAFI";
} }
} }
description "Enumeration for BGP Subsequent Address description "Enumeration for BGP Subsequent Address
Family Identifier (SAFI) - RFC 4760."; Family Identifier (SAFI) - RFC 4760.";
} }
} }
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 5. IANA Considerations
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note). actual RFC number (and remove this note).
 End of changes. 11 change blocks. 
20 lines changed or deleted 19 lines changed or added

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