draft-ietf-rtgwg-routing-types-09.txt   draft-ietf-rtgwg-routing-types-10.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: February 20, 2018 Futurewei Technologies, Inc. Expires: March 6, 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.
August 19, 2017 September 2, 2017
Routing Area Common YANG Data Types Routing Area Common YANG Data Types
draft-ietf-rtgwg-routing-types-09 draft-ietf-rtgwg-routing-types-10
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 February 20, 2018. This Internet-Draft will expire on March 6, 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 2, line 17 skipping to change at page 2, line 17
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. IETF Routing Types YANG Module . . . . . . . . . . . . . . . 6 3. IETF Routing Types YANG Module . . . . . . . . . . . . . . . 6
4. IANA Routing Types YANG Module . . . . . . . . . . . . . . . 22 4. IANA Routing Types YANG Module . . . . . . . . . . . . . . . 22
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
5.1. IANA-Maintained iana-routing-types Module . . . . . . . . 34 5.1. IANA-Maintained iana-routing-types Module . . . . . . . . 32
6. Security Considerations . . . . . . . . . . . . . . . . . . . 35 6. Security Considerations . . . . . . . . . . . . . . . . . . . 33
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.1. Normative References . . . . . . . . . . . . . . . . . . 35 8.1. Normative References . . . . . . . . . . . . . . . . . . 34
8.2. Informative References . . . . . . . . . . . . . . . . . 36 8.2. Informative References . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
The YANG [RFC6020] [RFC7950] is a data modeling language used to The YANG [RFC6020] [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. The YANG language notifications for network management protocols. The YANG language
supports a small set of built-in data types and provides mechanisms supports a small set of built-in data types and provides mechanisms
to derive other types from the built-in types. to derive other types from the built-in types.
This document introduces a collection of common data types derived This document introduces a collection of common data types derived
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-08-16.yang" <CODE BEGINS> file "ietf-routing-types@2017-09-02.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;
} }
organization organization
"IETF RTGWG - Routing Area Working Group"; "IETF RTGWG - Routing Area Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/rtgwg/> "WG Web: <http://tools.ietf.org/wg/rtgwg/>
WG List: <mailto:rtgwg@ietf.org> WG List: <mailto:rtgwg@ietf.org>
Editor: Xufeng Lui Editor: Xufeng Liu
<mailto:Xufeng_Lui@jabail.com> <mailto:Xufeng_Liu@jabail.com>
Yingzhen Qu Yingzhen Qu
<mailto:yingzhen.qu@huawei.com> <mailto:yingzhen.qu@huawei.com>
Acee Lindem Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Christian Hopps Christian Hopps
<mailto:chopps@chopps.org> <mailto:chopps@chopps.org>
Lou Berger Lou Berger
<mailto:lberger@labn.com>"; <mailto:lberger@labn.com>";
description description
"This module contains a collection of YANG data types "This module contains a collection of YANG data types
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-06-29 { revision 2017-09-02 {
description description "Initial revision.";
"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
values."; values.";
skipping to change at page 14, line 14 skipping to change at page 14, line 13
+ '[0-5]?[0-9]{0,3}[0-9]))|' + '[0-5]?[0-9]{0,3}[0-9]))|'
+ '(2:(429496729[0-5]|42949672[0-8][0-9]|' + '(2:(429496729[0-5]|42949672[0-8][0-9]|'
+ '4294967[01][0-9]{2}|' + '4294967[01][0-9]{2}|'
+ '429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|' + '429496[0-6][0-9]{3}|42949[0-5][0-9]{4}|'
+ '4294[0-8][0-9]{5}|' + '4294[0-8][0-9]{5}|'
+ '429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|' + '429[0-3][0-9]{6}|42[0-8][0-9]{7}|4[01][0-9]{8}|'
+ '[0-3]?[0-9]{0,8}[0-9]):' + '[0-3]?[0-9]{0,8}[0-9]):'
+ '(6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|' + '(6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|'
+ '6[0-4][0-9]{3}|' + '6[0-4][0-9]{3}|'
+ '[0-5]?[0-9]{0,3}[0-9]))|' + '[0-5]?[0-9]{0,3}[0-9]))|'
+ '(6:[a-fA-F0-9]{1,2}){6}|' + '(6(:[a-fA-F0-9]{2}){6})|'
+ '(([3-57-9a-fA-F]|[1-9a-fA-F][0-9a-fA-F]{1,3}):' + '(([3-57-9a-fA-F]|[1-9a-fA-F][0-9a-fA-F]{1,3}):'
+ '[0-9a-fA-F]{1,12})'; + '[0-9a-fA-F]{1,12})';
} }
description description
"A route origin is an 8-octet BGP extended community "A route origin is an 8-octet BGP extended community
identifying the set of sites where the BGP route identifying the set of sites where the BGP route
originated (RFC 4364). A route target consists of two originated (RFC 4364). A route target consists of two
or three fields: a 2-octet type field, an administrator or three fields: a 2-octet type field, an administrator
field, and, optionally, an assigned number field. field, and, optionally, an assigned number field.
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
"A grouping that specifies an MPLS label stack. List "This grouping specifies an MPLS label stack. List
entries are ordered with the first entry being the entries are in ascending order of ID with the first entry
top of stack, the next entry being the next entry being the leftmost label in the Network-Byte-Order (NBO)
on the stack, and so on."; MPLS header, i.e., the top of the label stack. The next
entry is the next label in MPLS header label stack, and
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 an MPLS label
stack entries. An entry with smaller ID value is stack entries. An entry with smaller ID value
precedes an entry in the label stack with a smaller precedes an entry with a larger value in the
ID. The value of this id has no semantic meaning other Network-Byte-Order (NBO) MPLS header. The value of
than ordering and referencing the entry."; this ID has no semantic meaning other than ordering
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
"Time to Live (TTL)."; "Time to Live (TTL).";
skipping to change at page 22, line 35 skipping to change at page 22, line 39
"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-06-29.yang" <CODE BEGINS> file "iana-routing-types@2017-09-02.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 22 skipping to change at page 23, line 26
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-06-29 { revision 2017-09-02 {
description description "Initial revision.";
"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 Identities ***/ /*** IANA address family enumeration ***/
identity address-family { typedef address-family {
description type enumeration {
"Base identity from which identities describing address enum ipv4 {
families are derived."; value 1;
} description "IPv4 Address Family";
}
identity ipv4 { enum ipv6 {
base address-family; value 2;
description description "IPv6 Address Family";
"IPv4 Address Family - IANA Registry Assigned Number: 1"; }
}
identity ipv6 { enum nsap {
base address-family; value 3;
description description "OSI Network Service Access Point (NSAP)
"IPv6 Address Family - IANA Registry Assigned Number: 2"; Address Family";
} }
identity nsap { enum hdlc {
base address-family; value 4;
description description "High-Level Data Link Control (HDLC)
"OSI Network Service Access Point (NSAP) Address Family - Address Family";
IANA Registry Assigned Number: 3";
}
identity hdlc { }
base address-family;
description
"High-Level Data Link Control (HDLC) Address Family -
IANA Registry Assigned Number: 4";
}
identity bbn1822 { enum bbn1822 {
base address-family; value 5;
description description "Bolt, Beranek, and Newman Report
"Bolt, Beranek, and Newman Report 1822 (BBN 1822) 1822 (BBN 1822) Address Family";
Address Family - IANA Registry Assigned Number: 5"; }
}
identity ieee802 { enum ieee802 {
base address-family; value 6;
description description "IEEE 802 Committee Address Family (aka,
"IEEE 802 Committee Address Family (aka, MAC address) - MAC address)";
IANA Registry Assigned Number: 6"; }
}
identity e163 { enum e163 {
base address-family; value 7;
description description "ITU-T E.163 Address Family";
"ITU-T E.163 Address Family - }
IANA Registry Assigned Number: 7";
}
identity e164 { enum e164 {
base address-family; value 8;
description description "ITU-T E.164 (SMDS, Frame Relay, ATM)
"ITU-T E.164 (SMDS, Frame Relay, ATM) Address Family - Address Family";
IANA Registry Assigned Number: 8"; }
}
identity f69 { enum f69 {
base address-family; value 9;
description description "ITU-T F.69 (Telex) Address Family";
"ITU-T F.69 (Telex) Address Family - }
IANA Registry Assigned Number: 9";
}
identity x121 { enum x121 {
base address-family; value 10;
description description "ITU-T X.121 (X.25, Frame Relay)
"ITU-T X.121 (X.25, Frame Relay) Address Family - Address Family";
IANA Registry Assigned Number: 10"; }
}
identity ipx { enum ipx {
base address-family; value 11;
description description "Novell Internetwork Packet Exchange (IPX)
"Novell Internetwork Packet Exchange (IPX) Address Family";
Address Family - IANA Registry Assigned Number: 11"; }
}
identity appletalk { enum appletalk {
base address-family; value 12;
description description "Apple AppleTalk Address Family";
"Apple AppleTalk Address Family - }
IANA Registry Assigned Number: 12";
}
identity decnet-iv { enum decnet-iv {
base address-family; value 13;
description description "Digital Equipment DECnet Phase IV
"Digital Equipment DECnet Phase IV Address Family - Address Family";
IANA Registry Assigned Number: 13"; }
}
identity vines { enum vines {
base address-family; value 14;
description description "Banyan Vines Address Family";
"Banyan Vines Address Family - }
IANA Registry Assigned Number: 14";
}
identity e164-nsap { enum e164-nsap {
base address-family; value 15;
description description "ITU-T E.164 with NSAP sub-address
"ITU-T E.164 with NSAP sub-address Address Family - Address Family";
IANA Registry Assigned Number: 15"; }
}
identity dns { enum dns {
base address-family; value 16;
description description "Domain Name System (DNS) Address
"Domain Name System (DNS) Address Family - Family";
IANA Registry Assigned Number: 16"; }
}
identity distinguished-name { enum distinguished-name {
base address-family; value 17;
description description "Distinguished Name Address Family";
"Distinguished Name Address Family - }
IANA Registry Assigned Number: 17";
}
identity as-num { enum as-num {
base address-family; value 18;
description description "AS Number Address Family";
"AS Number Family - }
IANA Registry Assigned Number: 18";
}
identity xtp-v4 { enum xtp-v4 {
base address-family; value 19;
description description "Xpress Transport Protocol (XTP) over IPv4
"Xpress Transport Protocol (XTP) over IPv4 Address Family";
Address Family - IANA Registry Assigned Number: 19"; }
}
identity xtp-v6 { enum xtp-v6 {
base address-family; value 20;
description description "Xpress Transport Protocol (XTP) over IPv6
"Xpress Transport Protocol (XTP) over IPv4 Address Family";
Address Family - IANA Registry Assigned Number: 20"; }
} enum xtp-native {
value 21;
description "Xpress Transport Protocol (XTP) native mode
Address Family";
}
identity xtp-native { enum fc-port {
base address-family; value 22;
description description "Fibre Channel (FC) World-Wide Port Name
"Xpress Transport Protocol (XTP) native mode Address Family";
Address Family - IANA Registry Assigned Number: 21"; }
}
identity fc-port { enum fc-node {
base address-family; value 23;
description description "Fibre Channel (FC) World-Wide Node Name
"Fibre Channel (FC) World-Wide Port Name Address Family";
Address Family - IANA Registry Assigned Number: 22"; }
}
identity fc-node { enum gwid {
base address-family; value 24;
description description
"Fibre Channel (FC) World-Wide Node Name "ATM Gateway Identifier (GWID) Number Address Family";
Address Family - IANA Registry Assigned Number: 23"; }
}
identity gwid {
base address-family;
description
"ATM Gateway Identifier (GWID) Number Family -
IANA Registry Assigned Number: 24";
}
identity l2vpn { enum l2vpn {
base address-family; value 25;
description description "Layer-2 VPN (L2VPN) Address Family";
"Layer-2 VPN (L2VPN) Address Family - }
IANA Registry Assigned Number: 25";
}
identity mpls-tp-section-eid { enum mpls-tp-section-eid {
base address-family; value 26;
description description "MPLS-TP Section Endpoint Identifier
"MPLS-TP Section Endpoint Identifier Address Family - Address Family";
IANA Registry Assigned Number: 26"; }
}
identity mpls-tp-lsp-eid { enum mpls-tp-lsp-eid {
base address-family; value 27;
description description "MPLS-TP LSP Endpoint Identifier
"MPLS-TP LSP Endpoint Identifier Address Family - Address Family";
IANA Registry Assigned Number: 27"; }
}
identity mpls-tp-pwe-eid { enum mpls-tp-pwe-eid {
base address-family; value 28;
description description "MPLS-TP Pseudowire Endpoint Identifier
"MPLS-TP Pseudowire Endpoint Identifier Address Family";
Address Family - IANA Registry Assigned Number: 28"; }
}
identity mt-v4 { enum mt-v4 {
base address-family; value 29;
description description "Multi-Topology IPv4 Address Family";
"Multi-Topology IPv4 Address Family - }
Address Family - IANA Registry Assigned Number: 29";
}
identity mt-v6 { enum mt-v6 {
base address-family; value 30;
description description "Multi-Topology IPv6 Address Family";
"Multi-Topology IPv6 Address Family - }
Address Family - IANA Registry Assigned Number: 30";
}
identity eigrp-common-sf {
base address-family;
description
"Enhanced Interior Gateway Routing Protocol (EIGRP)
Common Service Family Address Family -
IANA Registry Assigned Number: 16384";
}
identity eigrp-v4-sf { enum eigrp-common-sf {
base address-family; value 16384;
description description "Enhanced Interior Gateway Routing Protocol
"Enhanced Interior Gateway Routing Protocol (EIGRP) (EIGRP) Common Service Family Address
IPv4 Service Family Address Family - Family";
IANA Registry Assigned Number: 16385"; }
}
identity eigrp-v6-sf { enum eigrp-v4-sf {
base address-family; value 16385;
description description "Enhanced Interior Gateway Routing Protocol
"Enhanced Interior Gateway Routing Protocol (EIGRP) (EIGRP) IPv4 Service Family Address Family";
IPv6 Service Family Address Family - }
IANA Registry Assigned Number: 16386";
}
identity lcaf { enum eigrp-v6-sf {
base address-family; value 16386;
description description "Enhanced Interior Gateway Routing Protocol
"LISP Canonical Address Format (LCAF) (EIGRP) IPv6 Service Family Address Family";
Address Family - IANA Registry Assigned Number: 16387"; }
}
identity bgp-ls { enum lcaf {
base address-family; value 16387;
description description "LISP Canonical Address Format (LCAF)
"Border Gatway Protocol - Link State (BGP-LS) Address Family";
Address Family - IANA Registry Assigned Number: 16388"; }
}
identity mac-48 { enum bgp-ls {
base address-family; value 16388;
description description "Border Gatway Protocol - Link State (BGP-LS)
"IEEE 48-bit Media Access Control (MAC) Address Family";
Address Family - IANA Registry Assigned Number: 16389"; }
}
identity mac-64 { enum mac-48 {
base address-family; value 16389;
description description "IEEE 48-bit Media Access Control (MAC)
"IEEE 64-bit Media Access Control (MAC) Address Family";
Address Family - IANA Registry Assigned Number: 16390"; }
}
identity trill-oui { enum mac-64 {
base address-family; value 16390;
description description "IEEE 64-bit Media Access Control (MAC)
"TRILL IEEE Organizationally Unique Identifier (OUI) - Address Family";
Address Family - IANA Registry Assigned Number: 16391"; }
}
identity trill-mac-24 { enum trill-oui {
base address-family; value 16391;
description description "TRILL IEEE Organizationally Unique
"TRILL Final 3 octets of 48-bit MAC address Identifier (OUI) Address Family";
Address Family - IANA Registry Assigned Number: 16392"; }
}
identity trill-mac-48 { enum trill-mac-24 {
base address-family; value 16392;
description description "TRILL Final 3 octets of 48-bit MAC
"TRILL Final 5 octets of 64-bit MAC address address Address Family";
Address Family - IANA Registry Assigned Number: 16393"; }
}
identity trill-rbridge-port-id { enum trill-mac-40 {
base address-family; value 16393;
description description "TRILL Final 5 octets of 64-bit MAC
"TRILL Remote Bridge (RBridge) Port ID address Address Family";
Address Family - IANA Registry Assigned Number: 16394"; }
}
identity trill-nickname { enum ipv6-64 {
base address-family; value 16394;
description description "First 8 octects (64-bits) of an IPv6
"TRILL Nickname address Address Family";
Address Family - IANA Registry Assigned Number: 16395"; }
}
/*** SAFIs for Multi-Protocol BGP Identities ***/ enum trill-rbridge-port-id {
value 16395;
description "TRILL Remote Bridge (RBridge) Port ID
Address Family";
}
identity bgp-safi { enum trill-nickname {
description value 16396;
"Base identity from which identities describing BGP description "TRILL Nickname Address Family";
Subsequent Address Family Identifier (SAFI) - RFC 4760."; }
} }
description "Enumeration containing all the IANA
defined address families.";
identity unicast-safi {
base bgp-safi;
description
"Unicast SAFI -
IANA Registry Assigned Number: 1";
} }
identity multicast-safi { /*** SAFIs for Multi-Protocol BGP enumeration ***/
base bgp-safi;
description
"Multicast SAFI -
IANA Registry Assigned Number: 2";
}
identity labeled-unicast-safi { typedef bgp-safi {
base bgp-safi; type enumeration {
description enum unicast-safi {
"Labeled Unicast SAFI - value 1;
IANA Registry Assigned Number: 4"; description "Unicast SAFI";
} }
identity multicast-vpn-safi { enum multicast-safi {
base bgp-safi; value 2;
description description "Multicast SAFI";
"Multicast VPN SAFI - }
IANA Registry Assigned Number: 5";
}
identity pseudowire-safi { enum labeled-unicast-safi {
base bgp-safi; value 4;
description description "Labeled Unicast SAFI";
"Multi-segment Pseudowire VPN SAFI - }
IANA Registry Assigned Number: 6";
}
identity tunnel-enap-safi { enum multicast-vpn-safi {
base bgp-safi; value 5;
description description "Multicast VPN SAFI";
"Tunnel Encap SAFI - }
IANA Registry Assigned Number: 7";
}
identity mcast-vpls-safi { enum pseudowire-safi {
base bgp-safi; value 6;
description description "Multi-segment Pseudowire VPN SAFI";
"Multicast Virtual Private LAN Service (VPLS) SAFI - }
IANA Registry Assigned Number: 8";
}
identity tunnel-safi {
base bgp-safi;
description
"Tunnel SAFI -
IANA Registry Assigned Number: 64";
}
identity vpls-safi { enum tunnel-enap-safi {
base bgp-safi; value 7;
description description "Tunnel Encap SAFI";
"Virtual Private LAN Service (VPLS) SAFI - }
IANA Registry Assigned Number: 65";
}
identity mdt-safi { enum mcast-vpls-safi {
base bgp-safi; value 8;
description description "Multicast Virtual Private LAN Service
"Multicast Distribution Tree (MDT) SAFI - (VPLS) SAFI";
IANA Registry Assigned Number: 66"; }
}
identity v4-over-v6-safi { enum tunnel-safi {
base bgp-safi; value 64;
description description "Tunnel SAFI";
"IPv4 over IPv6 SAFI - }
IANA Registry Assigned Number: 67";
}
identity v6-over-v4-safi { enum vpls-safi {
base bgp-safi; value 65;
description description "Virtual Private LAN Service (VPLS) SAFI";
"IPv6 over IPv4 SAFI - }
IANA Registry Assigned Number: 68";
}
identity l1-vpn-auto-discovery-safi { enum mdt-safi {
base bgp-safi; value 66;
description description "Multicast Distribution Tree (MDT) SAFI";
"Layer-1 VPN Auto Discovery SAFI - }
IANA Registry Assigned Number: 69";
}
identity evpn-safi { enum v4-over-v6-safi {
base bgp-safi; value 67;
description description "IPv4 over IPv6 SAFI";
"Ethernet VPN (EVPN) SAFI - }
IANA Registry Assigned Number: 70";
}
identity bgp-ls-safi {
base bgp-safi;
description
"BGP Link-State (BGP-LS) SAFI -
IANA Registry Assigned Number: 71";
}
identity bgp-ls-vpn-safi { enum v6-over-v4-safi {
base bgp-safi; value 68;
description description "IPv6 over IPv4 SAFI";
"BGP Link-State (BGP-LS) VPN SAFI - }
IANA Registry Assigned Number: 72";
}
identity sr-te-safi { enum l1-vpn-auto-discovery-safi {
base bgp-safi; value 69;
description description "Layer-1 VPN Auto Discovery SAFI";
"Segment Routing - Traffic Engineering (SR-TE) SAFI - }
IANA Registry Assigned Number: 73";
}
identity labeled-vpn-safi { enum evpn-safi {
base bgp-safi; value 70;
description description "Ethernet VPN (EVPN) SAFI";
"MPLS Labeled VPN SAFI - }
IANA Registry Assigned Number: 128";
}
identity multicast-mpls-vpn-safi { enum bgp-ls-safi {
base bgp-safi; value 71;
description description "BGP Link-State (BGP-LS) SAFI";
"Multicast for BGP/MPLS IP VPN SAFI - }
IANA Registry Assigned Number: 129";
}
identity route-target-safi { enum bgp-ls-vpn-safi {
base bgp-safi; value 72;
description description "BGP Link-State (BGP-LS) VPN SAFI";
"Route Target SAFI - }
IANA Registry Assigned Number: 132";
}
identity ipv4-flow-spec-safi { enum sr-te-safi {
base bgp-safi; value 73;
description description "Segment Routing - Traffic Engineering
"IPv4 Flow Specification SAFI - (SR-TE) SAFI";
IANA Registry Assigned Number: 133"; }
}
identity vpnv4-flow-spec-safi { enum labeled-vpn-safi {
base bgp-safi; value 128;
description description "MPLS Labeled VPN SAFI";
"IPv4 VPN Flow Specification SAFI - }
IANA Registry Assigned Number: 134";
enum multicast-mpls-vpn-safi {
value 129;
description "Multicast for BGP/MPLS IP VPN SAFI";
}
enum route-target-safi {
value 132;
description "Route Target SAFI";
}
enum ipv4-flow-spec-safi {
value 133;
description "IPv4 Flow Specification SAFI";
}
enum vpnv4-flow-spec-safi {
value 134;
description "IPv4 VPN Flow Specification SAFI";
}
enum vpn-auto-discovery-safi {
value 140;
description "VPN Auto-Discovery SAFI";
}
}
description "Enumeration for BGP Subsequent Address
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).
skipping to change at page 35, line 35 skipping to change at page 34, line 10
Thanks to Martin Bjorkland, Tom Petch, Stewart Bryant, and Radek Thanks to Martin Bjorkland, Tom Petch, Stewart Bryant, and Radek
Krejci for comments on the model and document text. Thanks to Jeff Krejci for comments on the model and document text. Thanks to Jeff
Haas and Robert Raszuk for suggestions for additional common routing Haas and Robert Raszuk for suggestions for additional common routing
types. types.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[IANA-ADDRESS-FAMILY-REGISTRY] [IANA-ADDRESS-FAMILY-REGISTRY]
"IANA Address Family Registry", "IANA Address Family Registry",
<https://www.iana.org/assignments/address-family-numbers/ <https://www.iana.org/assignments/address-family-numbers/
address-family-numbers.xhtml#address-family-numbers-2>. address-family-numbers.xhtml#address-family-numbers-2>.
[IANA-SAFI-REGISTRY] [IANA-SAFI-REGISTRY]
"IANA Subsequent Address Family Identities (SAFI) "IANA Subsequent Address Family Identities (SAFI)
Parameters Registry", <https://www.iana.org/assignments/ Parameters Registry", <https://www.iana.org/assignments/
safi-namespace/safi-namespace.xhtml#safi-namespace-2>. safi-namespace/safi-namespace.xhtml#safi-namespace-2>.
skipping to change at page 37, line 32 skipping to change at page 35, line 49
[I-D.ietf-mpls-base-yang] [I-D.ietf-mpls-base-yang]
Raza, K., Gandhi, R., Liu, X., Beeram, V., Saad, T., Raza, K., Gandhi, R., Liu, X., Beeram, V., Saad, T.,
Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data
Model for MPLS Base", draft-ietf-mpls-base-yang-05 (work Model for MPLS Base", draft-ietf-mpls-base-yang-05 (work
in progress), July 2017. in progress), July 2017.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,
<http://www.rfc-editor.org/info/rfc3032>. <https://www.rfc-editor.org/info/rfc3032>.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<http://www.rfc-editor.org/info/rfc3209>. <https://www.rfc-editor.org/info/rfc3209>.
[RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", Switching (GMPLS) Signaling Functional Description",
RFC 3471, DOI 10.17487/RFC3471, January 2003, RFC 3471, DOI 10.17487/RFC3471, January 2003,
<http://www.rfc-editor.org/info/rfc3471>. <https://www.rfc-editor.org/info/rfc3471>.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <http://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer [RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer
2 Virtual Private Networks (L2VPNs)", RFC 4664, 2 Virtual Private Networks (L2VPNs)", RFC 4664,
DOI 10.17487/RFC4664, September 2006, DOI 10.17487/RFC4664, September 2006, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4664>. editor.org/info/rfc4664>.
[RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community [RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community
Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009, Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009,
<http://www.rfc-editor.org/info/rfc5701>. <https://www.rfc-editor.org/info/rfc5701>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<http://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
[RFC7274] Kompella, K., Andersson, L., and A. Farrel, "Allocating [RFC7274] Kompella, K., Andersson, L., and A. Farrel, "Allocating
and Retiring Special-Purpose MPLS Labels", RFC 7274, and Retiring Special-Purpose MPLS Labels", RFC 7274,
DOI 10.17487/RFC7274, June 2014, DOI 10.17487/RFC7274, June 2014, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7274>. editor.org/info/rfc7274>.
[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
2015, <http://www.rfc-editor.org/info/rfc7432>. 2015, <https://www.rfc-editor.org/info/rfc7432>.
Authors' Addresses Authors' Addresses
Xufeng Liu Xufeng Liu
Jabil Jabil
8281 Greensboro Drive, Suite 200 8281 Greensboro Drive, Suite 200
McLean VA 22102 McLean VA 22102
USA USA
EMail: Xufeng_Liu@jabil.com EMail: Xufeng_Liu@jabil.com
 End of changes. 89 change blocks. 
443 lines changed or deleted 364 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/