[CCAMP] Alexey Melnikov's No Objection on draft-ietf-ccamp-rsvp-te-bandwidth-availability-14: (with COMMENT)
Alexey Melnikov via Datatracker <noreply@ietf.org> Thu, 11 April 2019 08:14 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: ccamp@ietf.org
Delivered-To: ccamp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C05361204ED; Thu, 11 Apr 2019 01:14:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ccamp-rsvp-te-bandwidth-availability@ietf.org, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, ccamp-chairs@ietf.org, daniele.ceccarelli@ericsson.com, ccamp@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <155497048377.12789.13305027449937989152.idtracker@ietfa.amsl.com>
Date: Thu, 11 Apr 2019 01:14:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/mKwEWhhehwIqBGNPvF68MVADRxw>
Subject: [CCAMP] Alexey Melnikov's No Objection on draft-ietf-ccamp-rsvp-te-bandwidth-availability-14: (with COMMENT)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 11 Apr 2019 08:14:48 -0000
Alexey Melnikov has entered the following ballot position for draft-ietf-ccamp-rsvp-te-bandwidth-availability-14: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-ccamp-rsvp-te-bandwidth-availability/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for a well written document. I have a few easy to address comments. Other people already commented on the lack of reference for the float format. In the following text: When a node does not support the Availability TLV, the node SHOULD generate a PathErr message with the error code "Extended Class-Type Error" and the error value "Class-Type mismatch" (see [RFC2205]). When a node receives Availability TLVs which mixed of zero index and non-zero index, the message MAY be ignored and SHOULD NOT be What does “MAY ignore” mean here and what are the implications of not ignoring? I tend to think that this shoukd be MUST for interoperability, so either changing this to MUST or adding explanatory text for MAY would address my concern. propagated. When a node receives Availability TLVs (non-zero index) with no matching index value among the bandwidth-TLVs, the message MAY be ignored and SHOULD NOT be propagated. When a node receives Same comment as above. several <bandwidth, availability> pairs, but there're are extra bandwidth-TLVs without matching index Availability-TLV, the extra bandwidth-TLVs MAY be ignored and SHOULD NOT be propagated.
- [CCAMP] Alexey Melnikov's No Objection on draft-i… Alexey Melnikov via Datatracker
- Re: [CCAMP] Alexey Melnikov's No Objection on dra… Yemin (Amy)