draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt   draft-ietf-ccamp-rsvp-te-bandwidth-availability-16.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: October 2019 April 30, 2019 Expires: November 2019 May 5, 2019
Ethernet Traffic Parameters with Availability Information Ethernet Traffic Parameters with Availability Information
draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt draft-ietf-ccamp-rsvp-te-bandwidth-availability-16.txt
Abstract Abstract
A packet switching network may contain links with variable A packet switching network may contain links with variable
bandwidth, e.g., copper, radio, etc. The bandwidth of such links is bandwidth, e.g., copper, radio, etc. The bandwidth of such links is
sensitive to external environment (e.g., climate). Availability is sensitive to external environment (e.g., climate). Availability is
typically used for describing these links when doing network typically used for describing these links when doing network
planning. This document introduces an optional Bandwidth planning. This document introduces an optional Bandwidth
Availability TLV in Resource ReSerVation Protocol - Traffic Engineer Availability TLV in Resource ReSerVation Protocol - Traffic Engineer
(RSVP-TE) signaling. This extension can be used to set up a (RSVP-TE) signaling. This extension can be used to set up a
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 October 30, 2019. This Internet-Draft will expire on November 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 5, line 49 skipping to change at page 5, line 49
case, the Bandwidth Availability TLV has a one to one case, the Bandwidth Availability TLV has a one to one
correspondence with the Ethernet Bandwidth Profile TLV by having correspondence with the Ethernet Bandwidth Profile TLV by having
the same value of Index field. If all the bandwidth requirements the same value of Index field. If all the bandwidth requirements
in the Ethernet Bandwidth Profile have the same Availability in the Ethernet Bandwidth Profile have the same Availability
requirement, one Bandwidth Availability TLV SHOULD be carried. In requirement, one Bandwidth Availability TLV SHOULD be carried. In
this case, the Index field is set to 0. this case, the Index field 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-point number [IEEE754] Availability (4 octets): a 32-bit floating-point number in binary
describes the decimal value of the availability requirement for interchange format [IEEE754] describes the decimal value of the
this bandwidth request. The value MUST be less than 1 and is availability requirement for this bandwidth request. The value
usually expressed in the value of 0.99/0.999/0.9999/0.99999. The MUST be less than 1 and is usually expressed in the value of
IEEE floating-point number is used here to align with [RFC8330]. 0.99/0.999/0.9999/0.99999. The IEEE floating-point number is used
However when representing values higher than 0.999999, the here to align with [RFC8330]. However when representing values
floating-point number starts to introduce errors in relation to higher than 0.999999, the floating-point number starts to
intended precision. However in reality, 0.99999 is normally introduce errors in relation to intended precision. However in
considered as the highest availability value (5 minutes outage in reality, 0.99999 is normally considered as the highest
a year) in telecom network, therefore the use of floating-point availability value (5 minutes outage in a year) in telecom
number in availability is acceptable. network, therefore the use of floating-point number in
availability is acceptable.
3.2. Signaling Process 3.2. Signaling Process
The source node initiates a PATH message which may carry a number of The source node initiates a PATH message which may carry a number of
bandwidth requests, including one or more Ethernet Bandwidth Profile bandwidth requests, including one or more Ethernet Bandwidth Profile
TLVs and one or more Bandwidth Availability TLVs. Each Ethernet TLVs and one or more Bandwidth Availability TLVs. Each Ethernet
Bandwidth Profile TLV corresponds to an availability parameter in Bandwidth Profile TLV corresponds to an availability parameter in
the associated Bandwidth Availability TLV. the associated Bandwidth Availability TLV.
The intermediate and destination nodes check whether they can The intermediate and destination nodes check whether they can
 End of changes. 4 change blocks. 
14 lines changed or deleted 15 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/