< draft-ietf-rtgwg-routing-types-03.txt   draft-ietf-rtgwg-routing-types-04.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: November 11, 2017 Futurewei Technologies, Inc. Expires: November 17, 2017 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.
May 10, 2017 May 16, 2017
Routing Area Common YANG Data Types Routing Area Common YANG Data Types
draft-ietf-rtgwg-routing-types-03 draft-ietf-rtgwg-routing-types-04
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 November 11, 2017. This Internet-Draft will expire on November 17, 2017.
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 19 skipping to change at page 2, line 19
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IETF Routing Types YANG Module . . . . . . . . . . . . . . . 6 3. IETF Routing Types YANG Module . . . . . . . . . . . . . . . 6
4. IANA Routing Types YANG Module . . . . . . . . . . . . . . . 18 4. IANA Routing Types YANG Module . . . . . . . . . . . . . . . 18
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
6. Security Considerations . . . . . . . . . . . . . . . . . . . 28 5.1. IANA-Maintained iana-routing-types Module . . . . . . . . 28
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 29 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30
8.1. Normative References . . . . . . . . . . . . . . . . . . 29 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
8.2. Informative References . . . . . . . . . . . . . . . . . 29 8.1. Normative References . . . . . . . . . . . . . . . . . . 30
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 31 8.2. Informative References . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
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 3, line 18 skipping to change at page 3, line 18
routing-types and iana-routing-types. The only module imports are routing-types and iana-routing-types. The only module imports are
from [RFC6021]. The ietf-routing-types model contains common routing from [RFC6021]. The ietf-routing-types model contains common routing
types other than those corresponding directly to IANA mappings. types other than those corresponding directly to IANA mappings.
These include: These include:
router-id router-id
Router Identifiers are commonly used to identify a nodes in Router Identifiers are commonly used to identify a nodes in
routing and other control plane protocols. An example usage of routing and other control plane protocols. An example usage of
router-id can be found in [I-D.ietf-ospf-yang]. router-id can be found in [I-D.ietf-ospf-yang].
address-family
This type defines values for use in address family identifiers.
The values are based on the IANA Address Family Numbers Registry
[1]. An example usage can be found in [I-D.ietf-idr-bgp-model].
route-target route-target
Route Targets (RTs) are commonly used to control the distribution Route Targets (RTs) are commonly used to control the distribution
of virtual routing and forwarding (VRF) information, see of virtual routing and forwarding (VRF) information, see
[RFC4364], in support of virtual private networks (VPNs). An [RFC4364], in support of virtual private networks (VPNs). An
example usage can be found in [I-D.ietf-bess-l2vpn-yang]. example usage can be found in [I-D.ietf-bess-l2vpn-yang].
route-target-type route-target-type
This type defines the import and export rules of Route Targets, as This type defines the import and export rules of Route Targets, as
descibed in Section 4.3.1 of [RFC4364]. An example usage can be descibed in Section 4.3.1 of [RFC4364]. An example usage can be
found in [I-D.ietf-idr-bgp-model]. found in [I-D.ietf-idr-bgp-model].
skipping to change at page 6, line 20 skipping to change at page 6, line 15
representing Route Target import-export rules used in the BGP representing Route Target import-export rules used in the BGP
enabled Virtual Private Networks (VPNs). [RFC4364][RFC4664]. An enabled Virtual Private Networks (VPNs). [RFC4364][RFC4664]. An
example usage can be found in [I-D.ietf-bess-l2vpn-yang]. example usage can be found in [I-D.ietf-bess-l2vpn-yang].
The iana-routing-types model contains common routing types The iana-routing-types model contains common routing types
corresponding directly to IANA mappings. These include: corresponding directly to IANA mappings. These include:
address-family address-family
This type defines values for use in address family identifiers. This type defines values for use in address family identifiers.
The values are based on the IANA Address Family Numbers Registry The values are based on the IANA Address Family Numbers Registry
[2]. An example usage can be found in [I-D.ietf-idr-bgp-model]. [IANA-ADDRESS-FAMILY-REGISTRY]. An example usage can be found in
[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 Registry [3]. Address Family Identifiers (SAFI) Parameters Registry
[IANA-SAFI-REGISTRY].
3. IETF Routing Types YANG Module 3. IETF Routing Types YANG Module
<CODE BEGINS> file "ietf-routing-types@2017-05-10.yang" <CODE BEGINS> file "ietf-routing-types@2017-05-10.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 {
skipping to change at page 28, line 42 skipping to change at page 28, line 42
reference: RFC XXXX reference: RFC XXXX
-------------------------------------------------------------------- --------------------------------------------------------------------
-------------------------------------------------------------------- --------------------------------------------------------------------
name: iana-routing-types name: 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
reference: RFC XXXX reference: RFC XXXX
-------------------------------------------------------------------- --------------------------------------------------------------------
5.1. IANA-Maintained iana-routing-types Module
This document defines the initial version of the IANA-maintained
iana-routing-types YANG module.
The iana-routing-types YANG module is intended to reflect the
"Address Family Numbers" registry [IANA-ADDRESS-FAMILY-REGISTRY] and
"Subsequent Address Family Identifiers (SAFI) Parameters" registry
[IANA-SAFI-REGISTRY].
IANA has added this notes to the "iana-routing-types YANG Module"
registry:
Address Families and Subsequent Address Families must not be
directly added to the iana-routing-types YANG module. They must
instead be respectively added to the "Address Family Numbers"
and "Subsequent Address Family Identifiers (SAFI) Parameters"
registries.
When an Address Family or Subsequent Address Family is respectively
added to the "Address Family Numbers" registry or the "Subsequent
Address Family Identifiers (SAFI) Parameters" registry, a new
"identity" statement must be added to the iana-routing-types YANG
module. The name of the "identity" is the same as the corresponding
address family or SAFI only it willl be a valid YANG identifier in
all lowercase and with hyphens separating individual words in
compound identifiers. The following substatements to the "identity"
statement should be defined:
"base": Contains the value "address-family" for address families
or "bgp-safi" for subsequent address families.
"status": Include only if a registration has been deprecated (use
the value "deprecated") or obsoleted (use the value
"obsolete").
"description": Replicate the description from the registry,
if any. Insert line breaks as needed so that the
line does not exceed 72 characters.
"reference": Replicate the reference from the registry, if any,
and add the title of the document.
Unassigned or reserved values are not present in these modules.
When the iana-routing-types YANG module is updated, a new "revision"
statement must be added in front of the existing revision statements.
IANA has added this new note to the the "Address Family Numbers" and
"Subsequent Address Family Identifiers (SAFI) Parameters" registries:
When this registry is modified, the YANG module
iana-routing-types must be updated as defined in RFC XXXX.
6. Security Considerations 6. Security Considerations
This document defines common data types using the YANG data modeling This document defines common data types using the YANG data modeling
language. The definitions themselves have no security impact on the language. The definitions themselves have no security impact on the
Internet, but the usage of these definitions in concrete YANG modules Internet, but the usage of these definitions in concrete YANG modules
might have. The security considerations spelled out in the YANG might have. The security considerations spelled out in the YANG
specification [RFC7950] apply for this document as well. specification [RFC7950] apply for this document as well.
7. Acknowledgements 7. Acknowledgements
The Routing Area Yang Architecture design team members included Acee The Routing Area Yang Architecture design team members included Acee
Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Ebben Aries, Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Ebben Aries,
Lou Berger, Qin Wu, Rob Shakir, Xufeng Liu, and Yingzhen Qu. Lou Berger, Qin Wu, Rob Shakir, Xufeng Liu, and Yingzhen Qu.
Thanks to Martin Bjorkland, Tom Petch, Stewart Bryant, and Radek
Krejci for comments on the model and document text.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[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,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC [RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",
6021, DOI 10.17487/RFC6021, October 2010, RFC 6021, DOI 10.17487/RFC6021, October 2010,
<http://www.rfc-editor.org/info/rfc6021>. <http://www.rfc-editor.org/info/rfc6021>.
[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>. <http://www.rfc-editor.org/info/rfc7950>.
[IANA-ADDRESS-FAMILY-REGISTRY]
"IANA Address Family Registry",
<https://www.iana.org/assignments/address-family-numbers/
address-family-numbers.xhtml#address-family-numbers-2>.
[IANA-SAFI-REGISTRY]
"IANA Subsequent Address Family Identities (SAFI)
Parameters Registry", <https://www.iana.org/assignments/
safi-namespace/safi-namespace.xhtml#safi-namespace-2>.
8.2. Informative References 8.2. Informative References
[IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", IEEE [IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", IEEE
Std 754-2008, August 2008. Std 754-2008, August 2008.
[I-D.ietf-bfd-yang] [I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Networks, J., Jethanandani, M., and Rahman, R., Zheng, L., Networks, J., Jethanandani, M., and
G. Mirsky, "Yang Data Model for Bidirectional Forwarding G. Mirsky, "Yang Data Model for Bidirectional Forwarding
Detection (BFD)", draft-ietf-bfd-yang-05 (work in Detection (BFD)", draft-ietf-bfd-yang-05 (work in
progress), March 2017. progress), March 2017.
skipping to change at page 31, line 6 skipping to change at page 32, line 22
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>. <http://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>. <http://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", RFC Switching (GMPLS) Signaling Functional Description",
3471, DOI 10.17487/RFC3471, January 2003, RFC 3471, DOI 10.17487/RFC3471, January 2003,
<http://www.rfc-editor.org/info/rfc3471>. <http://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, <http://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, DOI 2 Virtual Private Networks (L2VPNs)", RFC 4664,
10.17487/RFC4664, September 2006, DOI 10.17487/RFC4664, September 2006,
<http://www.rfc-editor.org/info/rfc4664>. <http://www.rfc-editor.org/info/rfc4664>.
[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>. <http://www.rfc-editor.org/info/rfc5880>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
[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, DOI and Retiring Special-Purpose MPLS Labels", RFC 7274,
10.17487/RFC7274, June 2014, DOI 10.17487/RFC7274, June 2014,
<http://www.rfc-editor.org/info/rfc7274>. <http://www.rfc-editor.org/info/rfc7274>.
8.3. URIs
[1] http://www.iana.org/assignments/address-family-numbers/address-
family-numbers.xhtml
[2] http://www.iana.org/assignments/address-family-numbers/address-
family-numbers.xhtml
[3] https://www.iana.org/assignments/safi-namespace/safi-
namespace.xhtml#safi-namespace-2
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
Yingzhen Qu Yingzhen Qu
Futurewei Technologies, Inc. Futurewei Technologies, Inc.
2330 Central Expressway 2330 Central Expressway
Santa Clara CA 95050 Santa Clara CA 95050
USA USA
EMail: yingzhen.qu@huawei.com EMail: yingzhen.qu@huawei.com
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
 End of changes. 20 change blocks. 
42 lines changed or deleted 95 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/