draft-ietf-ccamp-rsvp-te-bandwidth-availability-04.txt   draft-ietf-ccamp-rsvp-te-bandwidth-availability-05.txt 
Network Working Group H. Long, M. Ye Network Working Group H. Long, M. Ye
Internet Draft Huawei Technologies Co., Ltd Internet Draft Huawei Technologies Co., Ltd
Intended status: Standards Track G. Mirsky Intended status: Standards Track G. Mirsky
Ericsson Ericsson
A.D'Alessandro A.D'Alessandro
Telecom Italia S.p.A Telecom Italia S.p.A
H. Shah H. Shah
Ciena Ciena
Expires: August 2016 February 19, 2016 Expires: February 2017 August 19, 2016
Ethernet Traffic Parameters with Availability Information Ethernet Traffic Parameters with Availability Information
draft-ietf-ccamp-rsvp-te-bandwidth-availability-04.txt draft-ietf-ccamp-rsvp-te-bandwidth-availability-05.txt
Abstract Abstract
A Packet switching network may contain links with variable bandwidth, A Packet switching network may contain links with variable bandwidth,
e.g., copper, radio, etc. The bandwidth of such links is sensitive e.g., copper, radio, etc. The bandwidth of such links is sensitive
to external environment. Availability is typically used for to external environment. Availability is typically used for
describing the link during network planning. This document describing the link during network planning. This document
introduces an optional Availability TLV in Resource ReSerVation introduces an optional Availability TLV in Resource ReSerVation
Protocol -- Traffic Engineer (RSVP-TE) signaling. This extension can Protocol - Traffic Engineer (RSVP-TE) signaling. This extension can
be used to set up a label switching path (LSP) in a Packet Switched be used to set up a Label Switched Path (LSP) in a Packet Switched
Network (PSN) that contains links with discretely variable bandwidth. Network (PSN) that contains links with discretely variable bandwidth.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
skipping to change at page 1, line 46 skipping to change at page 2, line 4
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on February 19, 2017.
This Internet-Draft will expire on August 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 49 skipping to change at page 3, line 4
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
The following acronyms are used in this draft: The following acronyms are used in this draft:
RSVP-TE Resource Reservation Protocol-Traffic Engineering RSVP-TE Resource Reservation Protocol-Traffic Engineering
LSP Label Switched Path LSP Label Switched Path
PSN Packet Switched Network PSN Packet Switched Network
SNR Signal-to-noise Ratio SNR Signal-to-noise Ratio
TLV Type Length Value TLV Type Length Value
LSA Link State Advertisement LSA Link State Advertisement
1. Introduction 1. Introduction
The RSVP-TE specification [RFC3209] and GMPLS extensions [RFC3473] The RSVP-TE specification [RFC3209] and GMPLS extensions [RFC3473]
specify the signaling message including the bandwidth request for specify the signaling message including the bandwidth request for
setting up a label switching path in a PSN network. setting up a Label Switched Path in a PSN network.
Some data communication technologies allow seamless change of Some data communication technologies allow seamless change of
maximum physical bandwidth through a set of known discrete values. maximum physical bandwidth through a set of known discrete values.
The parameter availability [G.827, F.1703, P.530] is often used to The parameter availability [G.827], [F.1703], [P.530] is often used
describe the link capacity during network planning. The availability to describe the link capacity during network planning. The
is a time scale that the requested bandwidth is ensured. A more availability is a time scale, which is a proportion of the operating
detailed example on the bandwidth availability can be found in time that the requested bandwidth is ensured. A more detailed
Appendix A. Assigning different availability classes to different example on the bandwidth availability can be found in Appendix A.
types of service over such kind of links provides more efficient Assigning different availability classes to different types of
planning of link capacity. To set up an LSP across these links, service over such kind of links provides more efficient planning of
availability information is required for the nodes to verify link capacity. To set up an LSP across these links, availability
bandwidth satisfaction and make bandwidth reservation. The information is required for the nodes to verify bandwidth
availability information should be inherited from the availability satisfaction and make bandwidth reservation. The availability
requirements of the services expected to be carried on the LSP. For information should be inherited from the availability requirements
example, voice service usually needs ''five nines'' availability, of the services expected to be carried on the LSP. For example,
while non-real time services may adequately perform at four or three voice service usually needs "five nines" availability, while non-
nines availability. Since different service types may need different real time services may adequately perform at four or three nines
availability. Since different service types may need different
availabilities guarantees, multiple <availability, bandwidth> pairs availabilities guarantees, multiple <availability, bandwidth> pairs
may be required when signaling. may be required when signaling.
If the availability requirement is not specified in the signaling If the availability requirement is not specified in the signaling
message, the bandwidth will be reserved as the highest availability. message, the bandwidth will be reserved as the highest availability.
For example, the bandwidth with 99.999% availability of a link is For example, the bandwidth with 99.999% availability of a link is
100 Mbps; the bandwidth with 99.99% availability is 200 Mbps. When a 100 Mbps; the bandwidth with 99.99% availability is 200 Mbps. When a
video application requests for 120 Mbps without availability video application requests for 120 Mbps without availability
requirement, the system will consider the request as 120 Mbps with requirement, the system will consider the request as 120 Mbps with
99.999% availability, while the available bandwidth with 99.999% 99.999% availability, while the available bandwidth with 99.999%
skipping to change at page 4, line 8 skipping to change at page 4, line 11
To fulfill LSP setup by signaling in these scenarios, this document To fulfill LSP setup by signaling in these scenarios, this document
specifies an Availability TLV. The Availability TLV can be specifies an Availability TLV. The Availability TLV can be
applicable to any kind of physical links with variable discrete applicable to any kind of physical links with variable discrete
bandwidth, such as microwave or DSL. Multiple Availability TLVs bandwidth, such as microwave or DSL. Multiple Availability TLVs
together with multiple Ethernet Bandwidth Profiles can be carried in together with multiple Ethernet Bandwidth Profiles can be carried in
the Ethernet SENDER_TSPEC object. the Ethernet SENDER_TSPEC object.
2. Overview 2. Overview
A PSN tunnel may span one or more links in a network. To setup a A PSN tunnel may span one or more links in a network. To setup a
label switching path (LSP), a node may collect link information Label Switched Path (LSP), a node may collect link information which
which is spread in routing message, e.g., OSPF TE LSA message, by is spread in routing message, e.g., OSPF TE LSA message, by network
network nodes to get to know about the network topology, and nodes to get to know about the network topology, and calculate out
calculate out an LSP route based on the network topology, and send an LSP route based on the network topology, and send the calculated
the calculated LSP route to signaling to initiate a PATH/RESV LSP route to signaling to initiate a PATH/RESV message for setting
message for setting up the LSP. up the LSP.
In case that there is(are) link(s) with variable discrete bandwidth In case that there is(are) link(s) with variable discrete bandwidth
in a network, a <bandwidth, availability> requirement list should be in a network, a <bandwidth, availability> requirement list should be
specified for an LSP. Each <bandwidth, availability> pair in the specified for an LSP. Each <bandwidth, availability> pair in the
list means that listed bandwidth with specified availability is list means that listed bandwidth with specified availability is
required. The list could be inherited from the results of service required. The list could be inherited from the results of service
planning for the LSP. planning for the LSP.
A node which has link(s) with variable discrete bandwidth attached A node which has link(s) with variable discrete bandwidth attached
should contain a <bandwidth, availability> information list in its should contain a <bandwidth, availability> information list in its
OSPF TE LSA messages. The list provides the information that how OSPF TE LSA messages. The list provides the mapping between the link
much bandwidth a link can support for a specified availability. This nominal bandwidth and its availability level. This information is
information is used for path calculation by the node(s). The routing used for path calculation by the node(s). The routing extension for
extension for availability can be found in [ARTE]. availability can be found in [ARTE].
When a node initiates a PATH/RESV signaling to set up an LSP, the When a node initiates a PATH/RESV signaling to set up an LSP, the
PATH message should carry the <bandwidth, availability> requirement PATH message should carry the <bandwidth, availability> requirement
list as bandwidth request. Intermediate node(s) will allocate the list as bandwidth request. Intermediate node(s) will allocate the
bandwidth resource for each availability requirement from the bandwidth resource for each availability requirement from the
remaining bandwidth with corresponding availability. An error remaining bandwidth with corresponding availability. An error
message may be returned if any <bandwidth, availability> request message may be returned if any <bandwidth, availability> request
cannot be satisfied. cannot be satisfied.
3. Extension to RSVP-TE Signaling 3. Extension to RSVP-TE Signaling
skipping to change at page 5, line 33 skipping to change at page 5, line 33
Index field. If all the bandwidth requirements in the Ethernet Index field. If all the bandwidth requirements in the Ethernet
Bandwidth Profile have the same Availability requirement, one Bandwidth Profile have the same Availability requirement, one
Availability TLV SHOULD be carried. In this case, the Index field Availability TLV SHOULD be carried. In this case, the Index field
is set to 0. is set to 0.
Reserved (3 octets): These bits SHOULD be set to zero when sent Reserved (3 octets): These bits SHOULD be set to zero when sent
and MUST be ignored when received. and MUST be ignored when received.
Availability (4 octets): a 32-bit floating number describes the Availability (4 octets): a 32-bit floating number describes the
decimal value of availability requirement for this bandwidth decimal value of availability requirement for this bandwidth
request. The value MUST be less than 1. request. The value MUST be less than 1and is usually expressed in
the value of 0.99/0.999/0.9999/0.99999.
3.2. Signaling Process 3.2. Signaling Process
The source node initiates PATH messages which carry a number of The source node initiates PATH messages which carry a number of
bandwidth request information, including one or more Ethernet bandwidth request information, including one or more Ethernet
Bandwidth Profile TLVs and one or more Availability TLVs. Each Bandwidth Profile TLVs and one or more Availability TLVs. Each
Ethernet Bandwidth Profile TLV corresponds to an availability Ethernet Bandwidth Profile TLV corresponds to an availability
parameter in the Availability TLV. parameter in the Availability TLV.
The intermediate and destination nodes check whether they can The intermediate and destination nodes check whether they can
skipping to change at page 6, line 32 skipping to change at page 6, line 32
ID, the node with the higher node ID will win the contention. More ID, the node with the higher node ID will win the contention. More
details can be found in [RFC3473]. details can be found in [RFC3473].
If a node does not support Availability TLV, it SHOULD generate If a node does not support Availability TLV, it SHOULD generate
PathErr message with the error code "Extended Class-Type Error" and PathErr message with the error code "Extended Class-Type Error" and
the error value "Class-Type mismatch" (see [RFC2205]). the error value "Class-Type mismatch" (see [RFC2205]).
4. Security Considerations 4. Security Considerations
This document does not introduce new security considerations to the This document does not introduce new security considerations to the
existing RSVP-TE signaling protocol. existing RSVP-TE signaling protocol. [RFC5920] provides an overview
of security vulnerabilities and protection mechanisms for the GMPLS
control plane.
5. IANA Considerations 5. IANA Considerations
IANA maintains registries and sub-registries for RSVP-TE used by IANA maintains registries and sub-registries for RSVP-TE used by
GMPLS. IANA is requested to make allocations from these registries GMPLS. IANA is requested to make allocations from these registries
as set out in the following sections. as set out in the following sections.
5.1 Ethernet Sender TSpec TLVs 5.1 Ethernet Sender TSpec TLVs
IANA maintains a registry of GMPLS parameters called ''Generalized IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters''. Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA has created a new sub-registry called ''Ethernet Sender TSpec IANA has created a sub-registry called "Ethernet Sender TSpec TLVs /
TLVs / Ethernet Flowspec TLVs'' to contain the TLV type values for Ethernet Flowspec TLVs" to contain the TLV type values for TLVs
TLVs carried in the Ethernet SENDER_TSPEC object. A new type for carried in the Ethernet SENDER_TSPEC object. The sub-registry is
Availability TLV is defined as follow: needed to be updated to include the Availability TLV which is
defined as follow. This document proposes a suggested value for the
Availability sub-TLV; it is recommended that the suggested value be
granted by IANA.
Type Description Reference Type Description Reference
----- ----------------------------------- --------- ----- ----------------------------------- ---------
TBD Availability [This ID] 0x04 Availability [This ID]
The registration procedure for this registry is Standards Action as
defined in [RFC5226].
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and
S.Jamin, "Resource ReSerVation Protocol (RSVP) - Version 1
Functional Specification", RFC 2205, September 1997.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V.,and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP V.,and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Resource ReserVation Protocol-Traffic (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC6003] Papadimitriou, D. ''Ethernet Traffic Parameters'', RFC 6003, [RFC6003] Papadimitriou, D. "Ethernet Traffic Parameters", RFC 6003,
October 2010. October 2010.
6.2. Informative References 6.2. Informative References
[G.827] ITU-T Recommendation, ''Availability performance parameters [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997.
[RFC5226] Narten,T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226, May 2008.
[RFC5920] Fang, L., "Security Framework for MPLS and GMPLS Networks",
RFC 5920, July 2010.
[G.827] ITU-T Recommendation, "Availability performance parameters
and objectives for end-to-end international constant bit- and objectives for end-to-end international constant bit-
rate digital paths'', September, 2003. rate digital paths", September, 2003.
[F.1703] ITU-R Recommendation, ''Availability objectives for real [F.1703] ITU-R Recommendation, "Availability objectives for real
digital fixed wireless links used in 27 500 km digital fixed wireless links used in 27 500 km
hypothetical reference paths and connections'', January, hypothetical reference paths and connections", January,
2005. 2005.
[P.530] ITU-R Recommendation,'' Propagation data and prediction [P.530] ITU-R Recommendation," Propagation data and prediction
methods required for the design of terrestrial line-of- methods required for the design of terrestrial line-of-
sight systems'', February, 2012 sight systems", February, 2012
[EN 302 217] ETSI standard, ''Fixed Radio Systems; Characteristics [EN 302 217] ETSI standard, "Fixed Radio Systems; Characteristics
and requirements for point-to-point equipment and and requirements for point-to-point equipment and
antennas'', April, 2009 antennas", April, 2009
[ARTE] H., Long, M., Ye, Mirsky, G., Alessandro, A., Shah, H., [ARTE] H., Long, M., Ye, Mirsky, G., Alessandro, A., Shah, H.,
''OSPF Routing Extension for Links with Variable Discrete "OSPF Routing Extension for Links with Variable Discrete
Bandwidth'', Work in Progress, June, 2015 Bandwidth", Work in Progress, June, 2015
7. Appendix: Bandwidth Availability Example 7. Appendix: Bandwidth Availability Example
In mobile backhaul network, microwave links are very popular for In mobile backhaul network, microwave links are very popular for
providing connection of last hops. In case of heavy rain, to providing connection of last hops. In case of heavy rain, to
maintain the link connectivity, the microwave link MAY lower the maintain the link connectivity, the microwave link MAY lower the
modulation level since demodulating the lower modulation level needs modulation level since demodulating the lower modulation level needs
a lower Signal-to-Noise Ratio (SNR). This is called adaptive a lower Signal-to-Noise Ratio (SNR). This is called adaptive
modulation technology [EN 302 217]. However, a lower modulation modulation technology [EN 302 217]. However, a lower modulation
level also means lower link bandwidth. When link bandwidth is level also means lower link bandwidth. When link bandwidth is
 End of changes. 26 change blocks. 
56 lines changed or deleted 78 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/