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

Adam Roach <adam@nostrum.com> Tue, 30 April 2019 03:26 UTC

Return-Path: <adam@nostrum.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 73963120122 for <ccamp@ietfa.amsl.com>; Mon, 29 Apr 2019 20:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 qA5YfbGC049A for <ccamp@ietfa.amsl.com>; Mon, 29 Apr 2019 20:26:48 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA05C12001E for <ccamp@ietf.org>; Mon, 29 Apr 2019 20:26:48 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x3U3QbW6023432 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 29 Apr 2019 22:26:39 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1556594800; bh=yluvv0lPlKCLnKAt9eO7Sp+Wjrhl/A1jX60nackPzf4=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=sYFQ8XD6LIFWCVonIzaeicBYS+eDhdgf5iMItOmlI8G4VMkEmpMnv9lWwZ2oq4dZ6 tbuepDa4EZ4IwAmw8miunW6OC/VAYjBQ/uQ7pPukTk+rZeDNTqke16HtrN7HGwiIZK A6fcCHOsGbS29o5CPM2d/qUuLVb8Xl7SWS9kvqio=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: "Yemin (Amy)" <amy.yemin@huawei.com>, Benjamin Kaduk <kaduk@mit.edu>, "magnus.westerlund@ericsson.com" <magnus.westerlund@ericsson.com>
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
References: <155659110848.12971.9733837510692807545@ietfa.amsl.com> <9C5FD3EFA72E1740A3D41BADDE0B461FCFBF07C9@DGGEMM528-MBX.china.huawei.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <9f352f61-c8f8-1b74-c99e-35c58c61f66d@nostrum.com>
Date: Mon, 29 Apr 2019 22:26:31 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <9C5FD3EFA72E1740A3D41BADDE0B461FCFBF07C9@DGGEMM528-MBX.china.huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/5HRGcVPE89O3RxmYL5tXimbk-ys>
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 03:26:51 -0000

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-availability/
> 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-availability/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-ccamp-rsvp-te-bandwidth-availability-15
> https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-rsvp-te-bandwidth-availability-15
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-rsvp-te-bandwidth-availability-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