[core] Chair's review of draft-ietf-core-hop-limit-02.txt

Carsten Bormann <cabo@tzi.org> Thu, 21 February 2019 23:20 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CD4EC12D4ED; Thu, 21 Feb 2019 15:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id AMkj93TtlAod; Thu, 21 Feb 2019 15:20:45 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AFEB126C7E; Thu, 21 Feb 2019 15:20:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x1LNKX7o029490; Fri, 22 Feb 2019 00:20:38 +0100 (CET)
Received: from [] (p54A6C2FE.dip0.t-ipconnect.de []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4459SK4GGSz1Bp8; Fri, 22 Feb 2019 00:20:33 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
Date: Fri, 22 Feb 2019 00:20:32 +0100
Cc: draft-ietf-core-hop-limit@ietf.org
X-Mao-Original-Outgoing-Id: 572484030.3803051-039167e7e724254a73dcb763d8255945
Content-Transfer-Encoding: quoted-printable
Message-Id: <7185933E-6816-435E-B668-2DB1367C279E@tzi.org>
To: core <core@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/_ti-hNLP0SYcdd1kkHUOdbg7NP8>
Subject: [core] Chair's review of draft-ietf-core-hop-limit-02.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Thu, 21 Feb 2019 23:20:47 -0000

In preparation for the impending working-group last call, I have
reviewed draft-ietf-core-hop-limit-02.txt.  Substantive comments are
below; a set of small editorial comments is going to the authors in

# Major

1. Is adding a hop-limit option now a recommendation that applies to
   all CoAP proxies?

2. I don't understand the rule about using cached copies.  As a
   general observation, rules like this should not simply be stated
   without a rationale why they are the way they are.

# Minor

1. The text could include a sentence about what happens when a proxy
   does not understand the option (nothing bad, but loops consisting
   entirely of such proxies will not be terminated).

2. The way the diagnostic payloads are formed seems to rely on a space
   separator, but does not exclude its use inside the separated items.

# Editorial

1. The terminology could be aligned some more (e.g., avoid "agent",
   use "request" or "response" instead of "message" where
   possible). Details in the editorial comments.

Grüße, Carsten