draft-ietf-ccamp-rsvp-te-bandwidth-availability-01.txt   draft-ietf-ccamp-rsvp-te-bandwidth-availability-02.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: September 2015 March 4, 2015 Expires: January 2016 July 2, 2015
RSVP-TE Signaling Extension for Links with Variable Discrete RSVP-TE Signaling Extension for Links with Variable Discrete
Bandwidth Bandwidth
draft-ietf-ccamp-rsvp-te-bandwidth-availability-01.txt draft-ietf-ccamp-rsvp-te-bandwidth-availability-02.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 Extended Ethernet Bandwidth Profile TLV and an introduces an Extended Ethernet Bandwidth Profile TLV and an
OPTIONAL Availability sub-TLV in RSVP-TE signaling. This extension OPTIONAL Availability sub-TLV in RSVP-TE signaling. This extension
can be used to set up a label switching path (LSP) in a Packet can be used to set up a label switching path (LSP) in a Packet
Switched Network (PSN) that contains links with discretely variable Switched Network (PSN) that contains links with discretely variable
bandwidth. bandwidth.
Status of this Memo Status of this Memo
skipping to change at page 1, line 45 skipping to change at page 2, line 4
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 September 6, 2015.
This Internet-Draft will expire on January 6, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................ 3
2. Overview .................................................... 4 2. Overview .................................................... 4
3. Extension to RSVP-TE Signaling............................... 5 3. Extension to RSVP-TE Signaling............................... 4
3.1.1. Extended Ethernet Bandwidth Profile TLV............ 5 3.1.1. Extended Ethernet Bandwidth Profile TLV............ 5
3.1.2. Availability sub-TLV............................... 6 3.1.2. Availability sub-TLV............................... 6
3.2. FLOWSPEC Object......................................... 6 3.2. FLOWSPEC Object......................................... 6
3.3. Signaling Process....................................... 6 3.3. Signaling Process....................................... 6
4. Security Considerations...................................... 7 4. Security Considerations...................................... 7
5. IANA Considerations ......................................... 7 5. IANA Considerations ......................................... 7
5.1 Ethernet Sender TSpec TLVs ............................. 7 5.1 Ethernet Sender TSpec TLVs ............................. 7
5.2 Extended Ethernet Bandwidth Profile TLV ................ 8 5.2 Extended Ethernet Bandwidth Profile TLV ................ 8
6. References .................................................. 8 6. References .................................................. 8
6.1. Normative References.................................... 8 6.1. Normative References.................................... 8
6.2. Informative References.................................. 9 6.2. Informative Reference .................................. 9
7. Appendix: Bandwidth Availability Example..................... 9 7. Appendix: Bandwidth Availability Example..................... 9
8. Acknowledgments ............................................ 10 8. Acknowledgments ............................................ 11
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"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
skipping to change at page 3, line 22 skipping to change at page 3, line 27
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 switching 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.
For example, in mobile backhaul network, microwave links are very
popular for providing connection of last hops. In case of heavy rain,
to maintain the link connectivity, the microwave link MAY lower the
modulation level since demodulating the lower modulation level needs
a lower Signal-to-Noise Ratio (SNR). This is called adaptive
modulation technology [EN 302 217]. However, a lower modulation
level also means lower link bandwidth. When link bandwidth is
reduced because of modulation down-shifting, high-priority traffic
can be maintained, while lower-priority traffic is dropped.
Similarly, the copper links MAY change their link bandwidth due to
external interference.
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 to
describe the link capacity during network planning. A more detailed describe the link capacity during network planning. The availability
example on the bandwidth availability can be found in Appendix A. is a time scale that the requested bandwidth is ensured. A more
Assigning different availability classes to different types of detailed example on the bandwidth availability can be found in
service over such kind of links provides more efficient planning of Appendix A. Assigning different availability classes to different
link capacity. To set up an LSP across these links, availability types of service over such kind of links provides more efficient
information is required for the nodes to verify bandwidth planning of link capacity. To set up an LSP across these links,
satisfaction and make bandwidth reservation. The availability availability information is required for the nodes to verify
information SHOULD be inherited from the availability requirements bandwidth satisfaction and make bandwidth reservation. The
of the services expected to be carried on the LSP. For example, availability information SHOULD be inherited from the availability
voice service usually needs "five nines" availability, while non- requirements of the services expected to be carried on the LSP. For
real time services MAY adequately perform at four or three nines example, voice service usually needs ''five nines'' availability,
availability. Since different service types MAY need different while non-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 5, line 43 skipping to change at page 5, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CBS | | CBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EIR | | EIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EBS | | EBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-TLV(OPTIONAL) | | sub-TLV(OPTIONAL) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: A new "AF" filed in Extended Ethernet Bandwidth Profile TLV Figure 1: A new ''AF'' filed in Extended Ethernet Bandwidth Profile TLV
The difference between the Extended Ethernet Bandwidth Profile TLV The difference between the Extended Ethernet Bandwidth Profile TLV
and Ethernet Bandwidth Profile TLV is that a new AF field to and Ethernet Bandwidth Profile TLV is that a new AF field to
indicate the sub-TLV is defined in the Extended Ethernet Bandwidth indicate the sub-TLV is defined in the Extended Ethernet Bandwidth
Profile TLV. The rest definitions are the same. Profile TLV. The rest definitions are the same.
A new filed is defined in this document: A new filed is defined in this document:
AF filed (bit 2): Availability Field (AF) AF filed (bit 2): Availability Field (AF)
skipping to change at page 7, line 43 skipping to change at page 7, line 40
existing RSVP-TE signaling protocol. existing RSVP-TE signaling protocol.
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 new sub-registry called ''Ethernet Sender TSpec
TLVs / Ethernet Flowspec TLVs" to contain the TLV type values for TLVs / Ethernet Flowspec TLVs'' to contain the TLV type values for
TLVs carried in the Ethernet SENDER_TSPEC object. A new value is as TLVs carried in the Ethernet SENDER_TSPEC object. A new value is as
follow: follow:
Type Description Reference Type Description Reference
----- ----------------------------------- --------- ----- ----------------------------------- ---------
TBD Extended Ethernet Bandwidth Profile [This ID] TBD Extended Ethernet Bandwidth Profile [This ID]
5.2 Extended Ethernet Bandwidth Profile TLV 5.2 Extended Ethernet Bandwidth Profile TLV
IANA has created a new sub-registry called "Extended Ethernet IANA has created a new sub-registry called ''Extended Ethernet
Bandwidth Profiles" to contain bit flags carried in the Extended Bandwidth Profiles'' to contain bit flags carried in the Extended
Ethernet Bandwidth Profile TLV of the Ethernet SENDER_TSPEC object. Ethernet Bandwidth Profile TLV of the Ethernet SENDER_TSPEC object.
Bits are to be allocated by Standards Action. Bits are numbered from Bits are to be allocated by Standards Action. Bits are numbered from
bit 0 as the low order bit. A new bit field is as follow: bit 0 as the low order bit. A new bit field is as follow:
Bit Hex Description Reference Bit Hex Description Reference
--- ---- ------------------ ----------- --- ---- ------------------ -----------
0 0x01 Coupling Flag (CF) [RFC6003] 0 0x01 Coupling Flag (CF) [RFC6003]
skipping to change at page 8, line 45 skipping to change at page 8, line 42
--- ---- ------------------ ----------- --- ---- ------------------ -----------
0 - Reserved Reserved value 0 - Reserved Reserved value
0x01 4 see Section 3.1.2 of this ID Availability 0x01 4 see Section 3.1.2 of this ID Availability
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated [RFC2210] Wroclawski, J., ''The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997. Services'', RFC 2210, 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.
[G.827] ITU-T Recommendation, "Availability performance parameters [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, February, 2014 Bandwidth'', Work in Progress, February, 2014
6.2. Informative References 6.2. Informative References
[MCOS] Minei, I., Gan, D., Kompella, K., and X. Li, "Extensions [MCOS] Minei, I., Gan, D., Kompella, K., and X. Li, "Extensions
for Differentiated Services-aware Traffic Engineered for Differentiated Services-aware Traffic Engineered
LSPs", Work in Progress, June 2006. LSPs", Work in Progress, June 2006.
7. Appendix: Bandwidth Availability Example 7. Appendix: Bandwidth Availability Example
In mobile backhaul network, microwave links are very popular for
providing connection of last hops. In case of heavy rain, to
maintain the link connectivity, the microwave link MAY lower the
modulation level since demodulating the lower modulation level needs
a lower Signal-to-Noise Ratio (SNR). This is called adaptive
modulation technology [EN 302 217]. However, a lower modulation
level also means lower link bandwidth. When link bandwidth is
reduced because of modulation down-shifting, high-priority traffic
can be maintained, while lower-priority traffic is dropped.
Similarly, the copper links MAY change their link bandwidth due to
external interference.
Presuming that a link has three discrete bandwidth levels: Presuming that a link has three discrete bandwidth levels:
The link bandwidth under modulation level 1, e.g., QPSK, is 100 Mbps; The link bandwidth under modulation level 1, e.g., QPSK, is 100 Mbps;
The link bandwidth under modulation level 2, e.g., 16QAM, is 200 The link bandwidth under modulation level 2, e.g., 16QAM, is 200
Mbps; Mbps;
The link bandwidth under modulation level 3, e.g., 256QAM, is 400 The link bandwidth under modulation level 3, e.g., 256QAM, is 400
Mbps. Mbps.
In sunny day, the modulation level 3 can be used to achieve 400 Mbps In sunny day, the modulation level 3 can be used to achieve 400 Mbps
link bandwidth. link bandwidth.
A light rain with X mm/h rate triggers the system to change the A light rain with X mm/h rate triggers the system to change the
modulation level from level 3 to level 2, with bandwidth changing modulation level from level 3 to level 2, with bandwidth changing
from 400 Mbps to 200 Mbps. The probability of X mm/h rain in the from 400 Mbps to 200 Mbps. The probability of X mm/h rain in the
local area is 52 minutes in a year. Then the dropped 200 Mbps local area is 52 minutes in a year. Then the dropped 200 Mbps
 End of changes. 29 change blocks. 
54 lines changed or deleted 55 lines changed or added

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