Re: [core] [Technical Errata Reported] RFC7252 (5429)

Achim Kraus <achimkraus@gmx.net> Wed, 23 November 2022 17:10 UTC

Return-Path: <achimkraus@gmx.net>
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 C9F88C1522AE for <core@ietfa.amsl.com>; Wed, 23 Nov 2022 09:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KrbJu2pqiBEn for <core@ietfa.amsl.com>; Wed, 23 Nov 2022 09:10:10 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09F74C14F733 for <core@ietf.org>; Wed, 23 Nov 2022 09:10:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=s31663417; t=1669223378; bh=SrZZAeZMawAG7oP6J7he6ELWZLCZDrOu98F9eg65a8E=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From:In-Reply-To; b=PPgbO1n0vagLXNy80APMpmqyWPchUMdLicbeKavppoe/wU+h+bqcYaC6XbTFxyaHb 53LpmAs2z28ZhEVyNJtMstcnF3qarmIS9ZvNvt3Zo54Ti9b9qVKfS31H6yEZhsb+iZ aTidQaXYlwqf05gSFF36hK/d8/2LnpMsxu+6CkZQzZjtWnh9j+R1LPdG7YwiciR6co fIamph4vs/sj/sIKWmUWU+5gR0gJdvSv6K9gqT4blGooX+DL063xEbK2ZzadK5Gtmg TE/Fzj/G3keBWumx74RlZTqmpDYoCpykv4el/GU+lM4n2IHrU4FEdxNeYWm0TcP9r+ A4F0ZoFZyp7ng==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from [192.168.178.10] ([88.152.184.228]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MGQjH-1ohhAl2rxl-00GmHp; Wed, 23 Nov 2022 18:09:38 +0100
Message-ID: <e8b05389-6439-b666-8fc3-d1c3503afc79@gmx.net>
Date: Wed, 23 Nov 2022 18:09:37 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Content-Language: de-AT-frami, en-US
To: Carsten Bormann <cabo@tzi.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jaime.jimenez@ericsson.com, hartke@tzi.org, aamelnikov@fastmail.fm, ben@nostrum.com, marian.buschsieweke@ovgu.de, core@ietf.org
References: <20180718144754.8CFA2B810BB@rfc-editor.org> <FA7560FC-255D-4CE0-BEB5-2741887EBA40@tzi.org>
From: Achim Kraus <achimkraus@gmx.net>
In-Reply-To: <FA7560FC-255D-4CE0-BEB5-2741887EBA40@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:or5ITwdxXRxrH9ZPw/bR4B9EAvi+WbAVOTTAav5RxctRLcmojY5 yQOgThJWMvXHQWcOY0cKVnjh7e6OrGTM5fK9XE+Muey5+AuKz4KcaEIQDrlKf/sMjqhnuU7 o9xWeLzwdZxYPL0qVabPGPU/eDRRYGRhmSrQ3SaMQMFFj77UClAUPjI7Kuou1PNyy66i6nk gXVHJo5jMrqudSGob3/Eg==
UI-OutboundReport: notjunk:1;M01:P0:jkrJPsMlX2w=;TRDK+E53efEPL2eEmvbY69sC+tY 2jcFajWYADcDZKW1xXR7PBLe0LWDTFDxu7wBivrv0NRDyNj1xp6TesYCfLXuDvNy31biRBPEI Z8YbF4Hq8nwp6K2wxMHzYMcoXBQcz37zUcjpaC14vvjIbIvOqq+PGvKuxHA1u8MkRWgudiODN HAteFKbnEXSkXVvXD78t5W64W8Lo7HAxewLcbj3IcoQQuKVTKmujE8uq5h49Re8rHDewvHqXp VCX3QT9XxngXkplyoCckYctbgihVnKEid/gPCwY+VedrZTHMpR4W5K6bbd0oeGNKgLNk6yeD5 WfrHsrlhUXf9rr/v1UF5ClYn2zuY91lpLxXJsvrFHqRKPLrSp7aU8qH+BakN2+Y1OiCOP5Fmt 6SpxCrqEdU9by2qk9ZByBBWK2Jg/B0vDRuN6qGSYsh5/piQwxbfEVJPQ+dGeofstVbP4tfvxa BIBKWYG5kMIMeNtopaZt8v0ppRiQHgPr9jznYduPKALBy/NJJ3nnoaeeS0tx87MSWrG52yWnv ON+2aitruQlS0qRsYv0QHcvqSpGC3Foiiz7f/y8kQAs5j3/aZTInhGjiySVvevxmL/Qb/5xvm DqoOgpdxqfQcOUvN4WR87DH05WVPPecnHZPzFwgA4wnWwN8fkcrgFATrUq2EVC2qvheTUTC6U xCdnUJgBg/5n9IEBq5Eyvne/BJMpd1s9hD22HWOOQGDcKtGbEU69LD4QJHytH27krVIOhTzv4 t2qQXe3fVujzMUaA83Y8Nd1Wu544OhdnLLKU8JZMAnjPxPnQjlBZ1eqOo6lLmITR5KLf5lcqk nioCLPtuHg+eAmwkvhU+jpTikSmdxc2FynNIjSxoVcYlTyxxrSFBQDikJrxcbYiRUBG51gmr5 rO1l57FrWx01bttNVv70ECxcXpWxhT/m8x4+91fyxuacHOL+oA+SqIh1iEAnqBwngGsluYEUl tu+I6w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/SqWgb2ngAGRDyxFF9vm35IcPeaI>
Subject: Re: [core] [Technical Errata Reported] RFC7252 (5429)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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, 23 Nov 2022 17:10:14 -0000

Hi Carsten,
Hi List,

 > which the CoRE WG might want to reinvigorate:
 > https://datatracker.ietf.org/doc/draft-bormann-core-corr-clar/

It's already an issue there:

https://github.com/core-wg/corrclar/issues/6

best regards
Achim


Am 23.11.22 um 17:31 schrieb Carsten Bormann:
> We picked up this errata report in the CoRE interim meeting today.
>
> Main content, with some typos corrected:
>> […]
>> Corrected Text
>> --------------
>> An Acknowledgement or Reset message is related to a Confirmable
>> message or Non-confirmable message by means of a Message ID along
>> with additional address information of the corresponding endpoint.
>> The Message ID is a 16-bit unsigned integer that is generated by the
>> sender of a Confirmable or Non-confirmable message and included in
>> the CoAP header.  Message IDs of subsequent messages sent to the
>> same endpoint within EXCHANGE_LIFETIME MUST be strictly ascending
>> (wrapping around at a value of 65535).  Additionally, two
>> subsequently send Message IDs to the same endpoint SHOULD have a
>> difference of at most 16.
> […]
>
> This is clearly a new technical proposal, which is different from what the WG intended.
> So it does not make good errata material.
>
> Note that there is extensive discussion of CoAP message ID usage in
> draft-ietf-lwig-coap, see:
> https://datatracker.ietf.org/doc/html/draft-ietf-lwig-coap-06#section-2.3
> and in particular
> https://datatracker.ietf.org/doc/html/draft-ietf-lwig-coap-06#section-3.5
>
> While draft-ietf-lwig-coap is not currently moving forward in the LWIG WG, some of its content might make a good fit to the clarifications part of the corr-clar document, which the CoRE WG might want to reinvigorate:
> https://datatracker.ietf.org/doc/draft-bormann-core-corr-clar/
>
> This (or an LWIG-coap actually taken to completion) then might provide a space to further discuss the technical proposal buried in this errata report.
>
> Grüße, Carsten
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core