[CCAMP] Mirja Kühlewind's No Objection on draft-ietf-ccamp-rsvp-te-bandwidth-availability-14: (with COMMENT)
Mirja Kühlewind via Datatracker <noreply@ietf.org> Wed, 03 April 2019 10:06 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 5797312007C; Wed, 3 Apr 2019 03:06:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind 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.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Mirja Kühlewind <ietf@kuehlewind.net>
Message-ID: <155428596335.22989.3373026547343406741.idtracker@ietfa.amsl.com>
Date: Wed, 03 Apr 2019 03:06:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/VbGwVvO4B_kAeFBSQE3qCyfyS8c>
Subject: [CCAMP] Mirja Kühlewind'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: Wed, 03 Apr 2019 10:06:03 -0000
Mirja Kühlewind 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: ---------------------------------------------------------------------- Just one quick question I was wondering about in section 3.2.: "When a node receives 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." Why is that? Is it not valid to also send some requests without availability? I thought that would make sense because it's basically saying, "just give me whatever you have because I don't know the availability requirements anyway", no?
- [CCAMP] Mirja Kühlewind's No Objection on draft-i… Mirja Kühlewind via Datatracker
- Re: [CCAMP] Mirja Kühlewind's No Objection on dra… Yemin (Amy)