Re: [CCAMP] I-D Action: draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt

"Yemin (Amy)" <amy.yemin@huawei.com> Tue, 30 April 2019 09:32 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 2CF93120288 for <ccamp@ietfa.amsl.com>; Tue, 30 Apr 2019 02:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xg8-Vyf3El5F for <ccamp@ietfa.amsl.com>; Tue, 30 Apr 2019 02:32:42 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D193120297 for <ccamp@ietf.org>; Tue, 30 Apr 2019 02:32:42 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E8D1DE63DD8AB888679C; Tue, 30 Apr 2019 10:32:39 +0100 (IST)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 30 Apr 2019 10:32:34 +0100
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Tue, 30 Apr 2019 10:32:34 +0100
Received: from DGGEMM423-HUB.china.huawei.com (10.1.198.40) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Tue, 30 Apr 2019 10:32:34 +0100
Received: from DGGEMM528-MBX.china.huawei.com ([169.254.8.72]) by dggemm423-hub.china.huawei.com ([10.1.198.40]) with mapi id 14.03.0415.000; Tue, 30 Apr 2019 17:32:28 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: Adam Roach <adam@nostrum.com>, Benjamin Kaduk <kaduk@mit.edu>, "magnus.westerlund@ericsson.com" <magnus.westerlund@ericsson.com>
CC: "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [CCAMP] I-D Action: draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt
Thread-Index: AQHU/vw51twdDi0+S0SYGeH2GA0wKqZT/phQ//+GVYCAAOqdMA==
Date: Tue, 30 Apr 2019 09:32:28 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461FCFBF09B4@DGGEMM528-MBX.china.huawei.com>
References: <155659110848.12971.9733837510692807545@ietfa.amsl.com> <9C5FD3EFA72E1740A3D41BADDE0B461FCFBF07C9@DGGEMM528-MBX.china.huawei.com> <9f352f61-c8f8-1b74-c99e-35c58c61f66d@nostrum.com>
In-Reply-To: <9f352f61-c8f8-1b74-c99e-35c58c61f66d@nostrum.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.169.30.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/3GuxVuuAsoKzobe_xf9-9-bScjQ>
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Apr 2019 09:32:44 -0000

Hi Adam, 

In order to be aligned with RFC8330, it's better to use binary 32 here. 
How about "a 32-bit format floating-point number in binary interchange format [IEEE754]..."?

BR,
Amy
-----Original Message-----
From: Adam Roach [mailto:adam@nostrum.com] 
Sent: Tuesday, April 30, 2019 11:27 AM
To: Yemin (Amy) <amy.yemin@huawei.com>;; Benjamin Kaduk <kaduk@mit.edu>;; magnus.westerlund@ericsson.com
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt

Thanks for the update!

I apologize for not being clearer in my DISCUSS that "binary interchange format" is as important as "IEEE 754-2008." The issues are twofold: 
IEEE-754 defines both binary and decimal formats; you presumably want to specify the use of the binary format. The standard also defines arithmetic formats, meant for efficiency of computation, and interchange formats, meant for unambiguous transmission between processors. You'll want to specify the second one.

/a

On 4/29/19 9:48 PM, Yemin (Amy) wrote:
> Hi Ben, Adam and Magnus,
>
> The draft is now updated to address all the Discuss & Comments 
> received in IESG review. Please review. 
> https://datatracker.ietf.org/doc/draft-ietf-ccamp-rsvp-te-bandwidth-av
> ailability/ Sorry for the late update due to my travelling in the past 
> weeks.
>
> BR,
> Amy (on behalf of co-authors)
>
> -----Original Message-----
> From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of 
> internet-drafts@ietf.org
> Sent: Tuesday, April 30, 2019 10:25 AM
> To: i-d-announce@ietf.org
> Cc: ccamp@ietf.org
> Subject: [CCAMP] I-D Action: 
> draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Common Control and Measurement Plane WG of the IETF.
>
>          Title           : Ethernet Traffic Parameters with Availability Information
>          Authors         : Hao Long
>                            Min Ye
>                            Greg Mirsky
>                            Alessandro D'Alessandro
>                            Himanshu Shah
> 	Filename        : draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt
> 	Pages           : 12
> 	Date            : 2019-04-29
>
> Abstract:
>     A packet switching network may contain links with variable
>     bandwidth, e.g., copper, radio, etc. The bandwidth of such links is
>     sensitive to external environment (e.g., climate). Availability is
>     typically used for describing these links when doing network
>     planning. This document introduces an optional Bandwidth
>     Availability TLV in Resource ReSerVation Protocol - Traffic Engineer
>     (RSVP-TE) signaling. This extension can be used to set up a
>     Generalized Multi-Protocol Label Switching (GMPLS) Label Switched
>     Path (LSP) in conjunction with the Ethernet SENDER_TSPEC object.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ccamp-rsvp-te-bandwidth-av
> ailability/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-ccamp-rsvp-te-bandwidth-availab
> ility-15
> https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-rsvp-te-bandwid
> th-availability-15
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-rsvp-te-bandwidth-a
> vailability-15
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp