Re: [core] Erik Kline's Discuss on draft-ietf-core-stateless-06: (with DISCUSS and COMMENT)

Klaus Hartke <hartke@projectcool.de> Tue, 28 April 2020 10:11 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 6256F3A127D; Tue, 28 Apr 2020 03:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 HwljBmBD8mki; Tue, 28 Apr 2020 03:11:42 -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 E0E153A127A; Tue, 28 Apr 2020 03:11:41 -0700 (PDT)
Received: from mail-qt1-f172.google.com ([209.85.160.172]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1jTNDG-00008P-B0; Tue, 28 Apr 2020 12:11:38 +0200
Received: by mail-qt1-f172.google.com with SMTP id i68so16792475qtb.5; Tue, 28 Apr 2020 03:11:38 -0700 (PDT)
X-Gm-Message-State: AGi0PuZfEsIGL9tpMr9Z/XTQaI0aqEmK69XUSIf9oZX+Pp5mXgLcaq1I lryBxRaWZzG7gKpz6dA478lqg6D6vLSxqDy6un0=
X-Google-Smtp-Source: APiQypJprwQHXxzuvqTm5/KcAp4+UrdJS1wbLDYXgLVzmKrgIoChOo7ej0HfOVmd/nLLrnrcDoP1csXScjichm1s7LU=
X-Received: by 2002:ac8:358c:: with SMTP id k12mr28463340qtb.38.1588068697134; Tue, 28 Apr 2020 03:11:37 -0700 (PDT)
MIME-Version: 1.0
References: <158761884340.24804.11461411197672215884@ietfa.amsl.com>
In-Reply-To: <158761884340.24804.11461411197672215884@ietfa.amsl.com>
From: Klaus Hartke <hartke@projectcool.de>
Date: Tue, 28 Apr 2020 12:11:14 +0200
X-Gmail-Original-Message-ID: <CAAzbHvbzHCLNPjM0YLKx5AV+OE=o3gDf8u3JBrC1CPR4skKA6Q@mail.gmail.com>
Message-ID: <CAAzbHvbzHCLNPjM0YLKx5AV+OE=o3gDf8u3JBrC1CPR4skKA6Q@mail.gmail.com>
To: Erik Kline <ek.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, core-chairs@ietf.org, draft-ietf-core-stateless@ietf.org, "core@ietf.org WG" <core@ietf.org>, Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1588068702; ea5def25;
X-HE-SMSGID: 1jTNDG-00008P-B0
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/DWXaT60YMrrnL8MwRcXBZ5W9IMc>
Subject: Re: [core] Erik Kline's Discuss on draft-ietf-core-stateless-06: (with DISCUSS and COMMENT)
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: Tue, 28 Apr 2020 10:11:45 -0000

Erik Kline wrote:
> * I agree with Ben's point about MTU.  Some text about the implications seems
>   warranted.  Even just a link to 7252#4.6 might be fine (and maybe a
>   skull-and-crossbones emoji [☠️] if they can be included now ;-)

I've added the following paragraph:

    In CoAP over UDP, it is often beneficial to keep CoAP messages small
    enough to avoid IP fragmentation. The maximum practical token length
    may therefore also be influenced by the Path MTU. See Section 4.6 of
    RFC 7252 for details.

> * 60 minutes for address changes?  Out of curiosity, upon what was this based?
>   I lack a good deal of context, but this kind of feels like the kind of
>   constant that will get baked into code and come to govern some behaviour
>   that later might need updating.

This was based on the desire to specify something more specific than
"must take address changes into account". I have to admit that I'm not
exactly sure how to express this in the best way.

The specific value of 60 minutes was suggested by Carsten. Maybe he
can chime in?

> * s/along the/along with the/?

Yes. Fixed.

Thank you very much!

Klaus