[core] Suresh Krishnan's No Objection on draft-ietf-core-hop-limit-06: (with COMMENT)
Suresh Krishnan via Datatracker <noreply@ietf.org> Tue, 15 October 2019 03:08 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 75F65120077; Mon, 14 Oct 2019 20:08:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-core-hop-limit@ietf.org, Jaime Jimenez <jaime@iki.fi>, core-chairs@ietf.org, jaime@iki.fi, core@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Suresh Krishnan <suresh@kaloom.com>
Message-ID: <157110890042.24804.1786615660069135136.idtracker@ietfa.amsl.com>
Date: Mon, 14 Oct 2019 20:08:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/jp0ebgMyjhfiIHFwjIhC9T8YBhA>
Subject: [core] Suresh Krishnan's No Objection on draft-ietf-core-hop-limit-06: (with COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 03:08:20 -0000
Suresh Krishnan has entered the following ballot position for draft-ietf-core-hop-limit-06: 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-core-hop-limit/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- * Section 3 "CoAP messages received with a Hop-Limit option ... ***greater than '255'*** MUST be rejected" Since the field is only 8 bits long this will never happen, right? If so, this text about >255 needs to be removed. * I would have expected that a CoAP option with NoCacheKey bits all zero would need to match in order to be served from the cache. Checking also for smaller values of Hop Limit for sending stored responses seems to (IMHO) complicate things for little benefit.
- [core] Suresh Krishnan's No Objection on draft-ie… Suresh Krishnan via Datatracker
- Re: [core] Suresh Krishnan's No Objection on draf… mohamed.boucadair