[core] Interim meeting at 2018-08-29, draft-boucadair-core-hop-limit

Carsten Bormann <cabo@tzi.org> Thu, 23 August 2018 07:13 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35D3130DEE for <core@ietfa.amsl.com>; Thu, 23 Aug 2018 00:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qHGipz8b59PI for <core@ietfa.amsl.com>; Thu, 23 Aug 2018 00:13:14 -0700 (PDT)
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 8B6881292F1 for <core@ietf.org>; Thu, 23 Aug 2018 00:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w7N7DANV014064 for <core@ietf.org>; Thu, 23 Aug 2018 09:13:10 +0200 (CEST)
Received: from [192.168.217.102] (p54A6C24D.dip0.t-ipconnect.de [84.166.194.77]) (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 41wwc607lKzDWwB; Thu, 23 Aug 2018 09:13:09 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
X-Mao-Original-Outgoing-Id: 556701187.26882-eca8ac528cbdc1429100bebc498b482d
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 23 Aug 2018 09:13:09 +0200
Message-Id: <C886421F-B826-427F-B3E6-8B21EC99A474@tzi.org>
To: Core <core@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/6JprVk7PKPlbYS-yVYswHo2K5hs>
Subject: [core] Interim meeting at 2018-08-29, draft-boucadair-core-hop-limit
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
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, 23 Aug 2018 07:13:15 -0000

Neither Jaime nor me will be available at the next interim meeting.
Klaus has volunteered to be stand-in chair for this meeting.

My proposal would be that we focus on the DOTS work.  
To prepare, it would be useful to get one more review of draft-boucadair-core-hop-limit before the meeting — who can do that?
The objective should be to be ready for adoption at the interim meeting (Jaime can then run the process from there).
One question was what response code should be used when the hop limit is reached.

We also should look at the way a DOTS server responds requests it cannot handle at the moment.
Again, the response code is one issue; it seems to me that the current draft has already covered the response payload well.
Having one or two reviews of that specific part of draft-ietf-dots-signal-channel would be useful as well.

Grüße, Carsten