[core] Fwd: I-D Action: draft-bormann-core-corr-clar-03.txt
Carsten Bormann <cabo@tzi.org> Wed, 28 February 2024 13:30 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 5CB5CC14F614 for <core@ietfa.amsl.com>; Wed, 28 Feb 2024 05:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 XOh47dD4gKTr for <core@ietfa.amsl.com>; Wed, 28 Feb 2024 05:30:43 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75F36C14F5E6 for <core@ietf.org>; Wed, 28 Feb 2024 05:30:43 -0800 (PST)
Received: from [192.168.217.145] (p548dcbf2.dip0.t-ipconnect.de [84.141.203.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4TlFbh5dsFzDCfR; Wed, 28 Feb 2024 14:30:40 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
Date: Wed, 28 Feb 2024 14:30:40 +0100
X-Mao-Original-Outgoing-Id: 730819840.253924-cf3fcb5a203893c3f0d9c0145a9aef44
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9B65508-4CA0-4B9A-96E5-DD70357D2152@tzi.org>
References: <170912666679.51952.8135202609588973651@ietfa.amsl.com>
To: core@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/wbjVCz6sPrcOtAM0YiNt_AGlMJA>
Subject: [core] Fwd: I-D Action: draft-bormann-core-corr-clar-03.txt
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, 28 Feb 2024 13:30:47 -0000
I submitted a small update to draft-bormann-core-corr-clar with a new section that covers one more existing, VERIFIED errata report [1]. [1]: https://www.ietf.org/archive/id/draft-bormann-core-corr-clar-03.html#name-rfc-7252-123-content-format Documenting VERIFIED errata reports can be useful as additional material pertinent to the erratum may be available, enabling a more extensive discussion. This was certainly not the most pressing item on the TO-DO-list, but it was expeditious to get it done before the I-D cutoff date. What we really want to do is work through [2]; maybe we should address one of these in each interim meeting following IETF 119, so we are done within a bit more than a year… Grüße, Carsten [2]: https://github.com/core-wg/corrclar/issues > Begin forwarded message: > > From: internet-drafts@ietf.org > Subject: I-D Action: draft-bormann-core-corr-clar-03.txt > Date: 2024-02-28 at 14:24:26 CET > To: <i-d-announce@ietf.org> > Reply-To: internet-drafts@ietf.org > Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/A581JBSG9ZpbuBvcNZC_sqoDhPA> > Message-Id: <170912666679.51952.8135202609588973651@ietfa.amsl.com> > > Internet-Draft draft-bormann-core-corr-clar-03.txt is now available. > > Title: Constrained Application Protocol (CoAP): Corrections and Clarifications > Author: Carsten Bormann > Name: draft-bormann-core-corr-clar-03.txt > Pages: 10 > Dates: 2024-02-28 > > Abstract: > > RFC 7252 defines the Constrained Application Protocol (CoAP), along > with a number of additional specifications, including RFC 7641, RFC > 7959, RFC 8132, and RFC 8323. RFC 6690 defines the link format that > is used in CoAP self-description documents. > > Some parts of the specification may be unclear or even contain errors > that may lead to misinterpretations that may impair interoperability > between different implementations. The present document provides > corrections, additions, and clarifications to the RFCs cited; this > document thus updates these RFCs. In addition, other clarifications > related to the use of CoAP in other specifications, including RFC > 7390 and RFC 8075, are also provided. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-bormann-core-corr-clar/ > > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-bormann-core-corr-clar-03.html > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-bormann-core-corr-clar-03
- [core] Fwd: I-D Action: draft-bormann-core-corr-c… Carsten Bormann