[CCAMP] 答复: 答复: draft-long-ccamp-rsvp-te-bandwidth-availability-01

"Yemin (Amy)" <amy.yemin@huawei.com> Tue, 24 September 2013 02:22 UTC

Return-Path: <amy.yemin@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B41621F9FE9 for <ccamp@ietfa.amsl.com>; Mon, 23 Sep 2013 19:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.65
X-Spam-Level: ***
X-Spam-Status: No, score=3.65 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JqiPGA+qPrNc for <ccamp@ietfa.amsl.com>; Mon, 23 Sep 2013 19:22:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1A32921F9D92 for <ccamp@ietf.org>; Mon, 23 Sep 2013 19:22:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AVU17291; Tue, 24 Sep 2013 02:22:23 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 24 Sep 2013 03:21:39 +0100
Received: from SZXEMA409-HUB.china.huawei.com (10.82.72.41) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 24 Sep 2013 03:22:21 +0100
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.229]) by SZXEMA409-HUB.china.huawei.com ([10.82.72.41]) with mapi id 14.03.0146.000; Tue, 24 Sep 2013 10:22:18 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: Autumn Liu <autumn.liu@ericsson.com>, Yuji Tochio <tochio@jp.fujitsu.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: =?gb2312?B?W0NDQU1QXSC08Li0OiAgZHJhZnQtbG9uZy1jY2FtcC1yc3ZwLXRlLWJhbmR3?= =?gb2312?Q?idth-availability-01?=
Thread-Index: AQHOtOhl+fZ/cAxv10OIHrH1b/3FwpnULY+R
Date: Tue, 24 Sep 2013 02:22:16 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461F73D3E83F@szxema506-mbs.china.huawei.com>
References: <42AD3B5FE67D4090B41F24C617A55395@china.huawei.com> <52381894.1030705@jp.fujitsu.com> <9C5FD3EFA72E1740A3D41BADDE0B461F73D3E1E6@szxema506-mbs.china.huawei.com>, <E4F89EAEF1386F42AA8E6FB5C35399A61C0665E3@eusaamb103.ericsson.se>
In-Reply-To: <E4F89EAEF1386F42AA8E6FB5C35399A61C0665E3@eusaamb103.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.46.73.105]
Content-Type: multipart/alternative; boundary="_000_9C5FD3EFA72E1740A3D41BADDE0B461F73D3E83Fszxema506mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [CCAMP] =?gb2312?b?tPC4tDogILTwuLQ6ICBkcmFmdC1sb25nLWNjYW1wLXJz?= =?gb2312?b?dnAtdGUtYmFuZHdpZHRoLWF2YWlsYWJpbGl0eS0wMQ==?=
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2013 02:22:30 -0000

Hi Autumn,



Thanks for the comments.

Sorry for the late reply, we just had a mid-autumn holiday. Please see my reply below.



BR,

Amy

________________________________
发件人: Autumn Liu [autumn.liu@ericsson.com]
发送时间: 2013年9月19日 11:28
收件人: Yemin (Amy); Yuji Tochio; ccamp@ietf.org
主题: RE: [CCAMP] 答复: draft-long-ccamp-rsvp-te-bandwidth-availability-01

Hi Amy,

If the bandwidth on the link between B and C could not meet the requirement for PATH message, why the PATH is forwarded to C at the first place?
[Amy] When A initiates the PATH message, if bandwidth on the link between B and C could not meet the requirement, C should return the PATHERR to A, the PATH is not forwarded to C. Maybe some misunderstanding here.

There are existing SENDER TSPEC objects, can they co-exist with new tspec object? It does not seem so. The same question applies to flowspec.
[Amy] We don't want to introduce a new tspec nor flowspec object. The availability TLV is proposed to use as the sub_TLV of Ethernet banwidth profiles. I guess the inconsistent with existing SENDER TSPEC, the "class-specific information", leads to this question. I will fix it.

Is it assumed that the nodes along the path will all support <availability, bandwidth>? If not, it will be good to describe how old sender tspec objects can pass the cac with <availablity, banddith>, or new object goes through the cac without taking the availablity into account.
[Amy] The nodes along the path are not required to support the <bandwidth, availability>. The descripation on how to ignore will be added in next version.

section 3.1, class-num for sender_tspec should be tbd, 12 is used for ethernet tspec object already.
[Amy] 12 is the class-num for generic sender_tspec. class type 6 is used to ethernet tspec. So I think it's ok to use 12.
                 class-specific information : what is this?
[Amy]  I will modify it to make sure it's consisten with RFC 6003.

3.1.1  Where will availability sub-TLV in new bandwidth profile TLV, before traffic parameter or after? It seems the draft is extending RFC 6003 ethernet sender tspec, so flag 3 is used on profile.
[Amy] I perfer to put the availability sub_TLV after the traffic parameter. Yes, the draft is extending RFC6003.

Thanks,
Autumn


________________________________
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of Yemin (Amy)
Sent: Wednesday, September 18, 2013 1:21 AM
To: Yuji Tochio; ccamp@ietf.org
Subject: [CCAMP] 答复: draft-long-ccamp-rsvp-te-bandwidth-availability-01

Hi Yuji,

Thanks for the question clarification.

Presuming the link blow:
A------ B - - - - C ------D

The dash line represents the link with discrete variable bandwidth.

When the bandwidth requirements couldn't be satisfied on the link between B and C,  it should be C to return the PATHERR message.

It might be not clear in the current draft, I will update the draft to make it clear.

BR,
Amy
发件人: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] 代表 Yuji Tochio
发送时间: 2013年9月17日 16:54
收件人: ccamp@ietf.org
主题: Re: [CCAMP] draft-long-ccamp-rsvp-te-bandwidth-availability-01

Hi all

FYI:
As to #4 (comment from me) below, I had offline talk with Amy via e-mail and
she has understood the point.
So I believe the editors will update the draft per my comments.

Thanks, Yuji

(2013/08/01 17:59), Amy wrote:
Hi CCAMPers,

There were some questions and comments after the presentation of draft-long-ccamp-rsvp-te-bandwidth-availability and draft-long-ccamp-ospf-availability-extension.

Below are the comments and replies:

1. The motivation
[Authors] For the links with variable discrete bandwidth, availability is used to decribe the bandwidth. It's proposed to add the availability as an paramter along with the bandwidth request. Without this extension, the link bandwidth cannot get good utilization: for example, the node may reserve the bandwidth with 99.999% availability while the actual requirement is only 99.9%, and consequently it can not reserve the bandwidth when the real requirement with 99.999% availability comes.

2. The mechanism, how to use the availability profile
[Authors] Once the link is set up, the information on availability and bandwidth is saved in the link bandwidth capacity table on local node, and should also be propagated in the routing message to calculate a path. When the bandwidth request comes, the node will compare the request with the link capacity table. If the request can be satisfied, the bandwidth is reserved and the link capacity table is updated.
3. What will happen if there are two links between C and D(see the figure in the slides), will it end up with multiple path?
[Authors] When there are multiple links between two nodes, the link aggregation may be used so that the two links can be treated as one logic link.  And the link aggregation should be transparent to resource resveration as it belongs to the link layer technology,

4. When the requirements in the PATH message couldn't be satisfied, D should send the PATHERR message.
[Authors] If the requirements couldn't be satisfied, to keep the consistent with the normal process, the resv process is terminated at C, C should send the PATHERR message,  and RESV message won't be passed to D.

5. In TSVWG, there's a draft on multiple-TSPEC which might be useful in this case.
[Authors] After looking into the draft-ietf-tsvwg-intserv-multiple-tspec-02, it might work to add a availability field in the TSPEC instead of having a sub-TLV in bandwidht profile TLV ( if I understand correlty).


Thank Khuzema, Lou, Yuji, Dieter to give their comments. And more comments are appreciated.

BR,
Amy Ye(on behalf of co-authors)






_______________________________________________

CCAMP mailing list

CCAMP@ietf.org<mailto:CCAMP@ietf.org>

https://www.ietf.org/mailman/listinfo/ccamp