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

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