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

Klaus Hartke <hartke@projectcool.de> Wed, 29 August 2018 14:53 UTC

Return-Path: <hartke@projectcool.de>
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 56F55130DED for <core@ietfa.amsl.com>; Wed, 29 Aug 2018 07:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001] autolearn=no 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 6teNuyJEEy7o for <core@ietfa.amsl.com>; Wed, 29 Aug 2018 07:53:57 -0700 (PDT)
Received: from wp382.webpack.hosteurope.de (wp382.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8597::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D5DE130DD1 for <core@ietf.org>; Wed, 29 Aug 2018 07:53:56 -0700 (PDT)
Received: from mail-qt0-f170.google.com ([209.85.216.170]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1fv1r0-0001xa-Fj; Wed, 29 Aug 2018 16:53:54 +0200
Received: by mail-qt0-f170.google.com with SMTP id n6-v6so6043658qtl.4 for <core@ietf.org>; Wed, 29 Aug 2018 07:53:54 -0700 (PDT)
X-Gm-Message-State: APzg51Ao4V7zislXGi6dFakBqmelNu7yoB+i0nvGg+Z1Xs45+Uws4/La 4TIjVRiCBvmNHS9iVpTDDX3686osXdrPvSq4JaQ=
X-Google-Smtp-Source: ANB0VdY3loxSQheKIzBCvesnQKn9ZSLLyTW5MhvM1oos1FUuyYKJo7wyGykB2qPNQ6Nqr8cPWtXOzwqlOBXA5e/APIU=
X-Received: by 2002:ac8:544c:: with SMTP id d12-v6mr7278503qtq.150.1535554433421; Wed, 29 Aug 2018 07:53:53 -0700 (PDT)
MIME-Version: 1.0
References: <C886421F-B826-427F-B3E6-8B21EC99A474@tzi.org>
In-Reply-To: <C886421F-B826-427F-B3E6-8B21EC99A474@tzi.org>
From: Klaus Hartke <hartke@projectcool.de>
Date: Wed, 29 Aug 2018 16:53:17 +0200
X-Gmail-Original-Message-ID: <CAAzbHvbHUc=o-xN2V9kUHpMumznPZ72w8+3D+QNUM=jPkO=0RA@mail.gmail.com>
Message-ID: <CAAzbHvbHUc=o-xN2V9kUHpMumznPZ72w8+3D+QNUM=jPkO=0RA@mail.gmail.com>
To: "core@ietf.org WG" <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1535554437; b2eca465;
X-HE-SMSGID: 1fv1r0-0001xa-Fj
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/UKqc6toDzv55WzAlGZe7cFsBvzI>
Subject: Re: [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: Wed, 29 Aug 2018 14:53:59 -0000

The interim meeting today (starting in 7 minutes) will take place on
Jitsi: <https://jitsi.tools.ietf.org/interim-2018-core-02>

Klaus

On Thu, 23 Aug 2018 at 09:13, Carsten Bormann <cabo@tzi.org> wrote:
>
> 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
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core