draft-ietf-ccamp-rsvp-te-bandwidth-availability-09.txt   draft-ietf-ccamp-rsvp-te-bandwidth-availability-10.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
ZTE ZTE
A.D'Alessandro A.D'Alessandro
Telecom Italia S.p.A Telecom Italia S.p.A
H. Shah H. Shah
Ciena Ciena
Expires: January 2019 July 24, 2018 Expires: March 2019 September 27, 2018
Ethernet Traffic Parameters with Availability Information Ethernet Traffic Parameters with Availability Information
draft-ietf-ccamp-rsvp-te-bandwidth-availability-09.txt draft-ietf-ccamp-rsvp-te-bandwidth-availability-10.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 Switched Path (LSP) in a Packet Switched be used to set up a Generalized Multi-Protocol Label Switching
Network (PSN) that contains links with discretely variable (GMPLS) Label Switched Path (LSP) using the Ethernet SENDER_TSPEC
bandwidth. object.
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-
Drafts. Drafts.
skipping to change at page 2, line 4 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 January 24, 2019. This Internet-Draft will expire on March 27, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 2, line 49
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
LSP Label Switched Path LSP Label Switched Path
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 Switched Path in a PSN network. setting up a Label Switched Path in a packet switching 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 The parameter availability [G.827], [F.1703], [P.530] is often used
to describe the link capacity during network planning. The to describe the link capacity during network planning. The
availability is a time scale, which is a proportion of the operating availability is a time scale, which is a proportion of the operating
time that the requested bandwidth is ensured. A more detailed time that the requested bandwidth is ensured. A more detailed
example on the bandwidth availability can be found in Appendix A. example on the bandwidth availability can be found in Appendix A.
Assigning different availability classes to different types of Assigning different availability classes to different types of
service over such kind of links provides more efficient planning of service over such kind of links provides more efficient planning of
skipping to change at page 4, line 5 skipping to change at page 3, line 50
99.999% availability, while the available bandwidth with 99.999% 99.999% availability, while the available bandwidth with 99.999%
availability is only 100 Mbps, therefore the LSP path cannot be set availability is only 100 Mbps, therefore the LSP path cannot be set
up. But in fact, video application doesn't need 99.999% availability; up. But in fact, video application doesn't need 99.999% availability;
99.99% availability is enough. In this case, the LSP could be set up 99.99% availability is enough. In this case, the LSP could be set up
if availability is specified in the signaling message. if availability is specified in the signaling message.
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 by
the Ethernet SENDER_TSPEC object. the Ethernet SENDER_TSPEC object [RFC6003]. Since the Ethernet
FLOWSPEC object has the same format as the Ethernet SENDER_TSPEC
object [RFC6003], the Availability TLV can also be carried by the
Ethernet FLOWSPEC object.
2. Overview 2. Overview
A PSN tunnel may span one or more links in a network. To setup a A tunnel in a packet switching network may span one or more links in
Label Switched Path (LSP), a node may collect link information which a network. To setup a Label Switched Path (LSP), a node may collect
is spread in routing message, e.g., OSPF TE LSA message, by network link information which is spread in routing message, e.g., OSPF TE
nodes to get to know about the network topology, and calculate out LSA message, by network nodes to get to know about the network
an LSP route based on the network topology, and send the calculated topology, and calculate out an LSP route based on the network
LSP route to signaling to initiate a PATH/RESV message for setting topology, and send the calculated LSP route to signaling to initiate
up the LSP. a PATH/RESV message for setting 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
skipping to change at page 4, line 44 skipping to change at page 4, line 45
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
3.1. Availability TLV 3.1. Availability TLV
An Availability TLV is defined as a TLV of the Ethernet An Availability TLV is defined as a TLV of the Ethernet SENDER_TSPEC
SENDEDR_TSPEC object [RFC6003] in this document. The Ethernet object [RFC6003] in this document. The Ethernet SENDER_TSPEC object
SENDER_TSPEC object MAY include more than one Availability TLV. The MAY include more than one Availability TLV. The Availability TLV has
Availability TLV has the following format: the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index | Reserved | | Index | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Availability | | Availability |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Availability TLV Figure 1: Availability TLV
 End of changes. 11 change blocks. 
23 lines changed or deleted 24 lines changed or added

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