< draft-ietf-rtgwg-routing-types-01.txt   draft-ietf-rtgwg-routing-types-02.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: August 23, 2017 Futurewei Technologies, Inc. Expires: September 4, 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.
February 19, 2017 March 3, 2017
Routing Area Common YANG Data Types Routing Area Common YANG Data Types
draft-ietf-rtgwg-routing-types-01 draft-ietf-rtgwg-routing-types-02
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 August 23, 2017. This Internet-Draft will expire on September 4, 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 4, line 17 skipping to change at page 4, line 17
This type also allows the indication of wildcard sources, i.e., This type also allows the indication of wildcard sources, i.e.,
"*". An example of where this type may/will be used is "*". An example of where this type may/will be used is
[I-D.ietf-pim-yang]. [I-D.ietf-pim-yang].
ipv6-multicast-source-address ipv6-multicast-source-address
IPv6 source address type for use in multicast control protocols. IPv6 source address type for use in multicast control protocols.
This type also allows the indication of wildcard sources, i.e., This type also allows the indication of wildcard sources, i.e.,
"*". An example of where this type may/will be used is "*". An example of where this type may/will be used is
[I-D.ietf-pim-yang]. [I-D.ietf-pim-yang].
ieee-bandwidth bandwidth-ieee-float32
Bandwidth in IEEE 754 floating point 32-bit binary format Bandwidth in IEEE 754 floating point 32-bit binary format
[IEEE754]. Commonly used in Traffic Engineering control plane [IEEE754]. Commonly used in Traffic Engineering control plane
protocols. An example of where this type may/will be used is protocols. An example of where this type may/will be used is
[I-D.ietf-ospf-yang]. [I-D.ietf-ospf-yang].
link-access-type link-access-type
This type identifies the IGP link type. An example of where this This type identifies the IGP link type. An example of where this
type may/will be used is [I-D.ietf-ospf-yang]. type may/will be used is [I-D.ietf-ospf-yang].
timer-multiplier timer-multiplier
skipping to change at page 5, line 41 skipping to change at page 5, line 41
label values. An example usage can be found in label values. An example usage can be found in
[I-D.ietf-mpls-base-yang]. [I-D.ietf-mpls-base-yang].
This document defines the following YANG groupings: This document defines the following YANG groupings:
mpls-label-stack mpls-label-stack
This grouping defines a reusable collection of schema nodes This grouping defines a reusable collection of schema nodes
representing an MPLS label stack [RFC3032]. An example usage can representing an MPLS label stack [RFC3032]. An example usage can
be found in [I-D.ietf-mpls-base-yang]. be found in [I-D.ietf-mpls-base-yang].
vpn-route-target-rules vpn-route-targets
This grouping defines a reusable collection of schema nodes This grouping defines a reusable collection of schema nodes
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].
3. YANG Module 3. YANG Module
<CODE BEGINS> file "ietf-routing-types@2017-02-19.yang" <CODE BEGINS> file "ietf-routing-types@2017-02-27.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 6, line 24 skipping to change at page 6, line 24
organization "IETF Routing Area Working Group (rtgwg)"; organization "IETF Routing Area Working Group (rtgwg)";
contact contact
"Routing Area Working Group - <rtgwg@ietf.org>"; "Routing Area Working Group - <rtgwg@ietf.org>";
description description
"This module contains a collection of YANG data types "This module contains a collection of YANG data types
considered generally useful for routing protocols."; considered generally useful for routing protocols.";
revision 2017-02-19 { revision 2017-02-27 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC TBD: Routing YANG Data Types"; "RFC TBD: Routing YANG Data Types";
} }
/*** collection of types related to routing ***/ /*** collection of types related to routing ***/
typedef router-id { typedef router-id {
type yang:dotted-quad; type yang:dotted-quad;
description description
skipping to change at page 14, line 8 skipping to change at page 14, line 8
"Any source address."; "Any source address.";
} }
} }
type inet:ipv6-address; type inet:ipv6-address;
} }
description description
"Multicast source IPv6 address type."; "Multicast source IPv6 address type.";
} }
/*** collection of types common to protocols ***/ /*** collection of types common to protocols ***/
typedef ieee-bandwidth { typedef bandwidth-ieee-float32 {
type string { type string {
pattern pattern
'0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|' '0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|'
+ '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|' + '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|'
+ '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}'; + '1[01]\d|0?\d?\d)?)';
} }
description description
"Bandwidth in IEEE 754 floating point 32-bit binary format: "Bandwidth in IEEE 754 floating point 32-bit binary format:
(-1)**(S) * 2**(Exponent-127) * (1 + Fraction), (-1)**(S) * 2**(Exponent-127) * (1 + Fraction),
where Exponent uses 8 bits, and Fraction uses 23 bits. where Exponent uses 8 bits, and Fraction uses 23 bits.
The units are octets per second. The units are octets per second.
The encoding format is the external hexadecimal-significand The encoding format is the external hexadecimal-significand
character sequences specified in IEEE 754 and C99, character sequences specified in IEEE 754 and C99,
restricted to be normalized, non-negative, and non-fraction: restricted to be normalized, non-negative, and non-fraction:
0x1.hhhhhhp{+}d or 0X1.HHHHHHP{+}D 0x1.hhhhhhp{+}d or 0X1.HHHHHHP{+}D
skipping to change at page 22, line 30 skipping to change at page 22, line 30
ietf-idr-bgp-model-02 (work in progress), July 2016. ietf-idr-bgp-model-02 (work in progress), July 2016.
[I-D.ietf-ospf-yang] [I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
"Yang Data Model for OSPF Protocol", draft-ietf-ospf- "Yang Data Model for OSPF Protocol", draft-ietf-ospf-
yang-06 (work in progress), October 2016. yang-06 (work in progress), October 2016.
[I-D.ietf-pim-yang] [I-D.ietf-pim-yang]
Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu,
Y., and f. hu, "A YANG data model for Protocol-Independent Y., and f. hu, "A YANG data model for Protocol-Independent
Multicast (PIM)", draft-ietf-pim-yang-03 (work in Multicast (PIM)", draft-ietf-pim-yang-05 (work in
progress), October 2016. progress), February 2017.
[I-D.ietf-teas-yang-rsvp] [I-D.ietf-teas-yang-rsvp]
Beeram, V., Saad, T., Gandhi, R., Liu, X., Shah, H., Chen, Beeram, V., Saad, T., Gandhi, R., Liu, X., Shah, H., Chen,
X., Jones, R., and B. Wen, "A YANG Data Model for Resource X., Jones, R., and B. Wen, "A YANG Data Model for Resource
Reservation Protocol (RSVP)", draft-ietf-teas-yang-rsvp-06 Reservation Protocol (RSVP)", draft-ietf-teas-yang-rsvp-06
(work in progress), October 2016. (work in progress), October 2016.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H.,
Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data
 End of changes. 11 change blocks. 
12 lines changed or deleted 12 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/