IETF Logo Mail Archive

Re: [core] [Last-Call] [art] Artart last call review of draft-ietf-core-problem-details-05

Carsten Bormann <cabo@tzi.org> Thu, 30 June 2022 10:23 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 08B5AC14F606; Thu, 30 Jun 2022 03:23:39 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01] autolearn=unavailable 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 jaEwE5r9dw33; Thu, 30 Jun 2022 03:23:33 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (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 1FD14C14F73E; Thu, 30 Jun 2022 03:23:31 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4LYZDJ5kQKzDCgL; Thu, 30 Jun 2022 12:23:28 +0200 (CEST)
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>
In-Reply-To: <CAObGJnOqMAmu32stN11NoTAfvNhXvmGSjscpk8cS5AO6iY4k0Q@mail.gmail.com>
Date: Thu, 30 Jun 2022 12:23:28 +0200
Cc: John C Klensin <john-ietf@jck.com>, Francesca Palombini <francesca.palombini=40ericsson.com@dmarc.ietf.org>, Harald Alvestrand <harald@alvestrand.no>, Applications and Real-Time Area Discussion <art@ietf.org>, "core@ietf.org WG" <core@ietf.org>, draft-ietf-core-problem-details.all@ietf.org, last-call@ietf.org
X-Mao-Original-Outgoing-Id: 678277408.226655-b9f49de3e0c67c129dd070516c7fe3a0
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9C8C465-FE6A-49A6-BA36-EB5756F75463@tzi.org>
References: <165511479760.19573.12671700576299137749@ietfa.amsl.com> <63D13796-758D-469B-AFA8-3050C9F87819@tzi.org> <AS1PR07MB86169230F0D43E82CB2BCA1698AC9@AS1PR07MB8616.eurprd07.prod.outlook.com> <CAObGJnO7kdhO6tzLx2GZH3FVj2iedCU=fWH-w608OAStMMGeLA@mail.gmail.com> <10B6E8EC0FCAFB668F04845E@PSB> <CAObGJnOqMAmu32stN11NoTAfvNhXvmGSjscpk8cS5AO6iY4k0Q@mail.gmail.com>
To: Thomas Fossati <tho.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/H2BsFpbqqeVusSsbEpqeP_27PC8>
Subject: Re: [core] [Last-Call] [art] Artart last call review of draft-ietf-core-problem-details-05
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: Thu, 30 Jun 2022 10:23:39 -0000

On 2022-06-30, at 11:57, Thomas Fossati <tho.ietf@gmail.com> wrote:
> 
>> I think the document would be strengthened by a brief paragraph about
>> possible updates, pointing out that Tag 38 and the rest of the spec
>> might be altered separately and urging that any updating documents be
>> clear about what is being altered (and what is not) and that any
>> replacement document either copy everything or split things up.  That
>> might include an explicit warning against leaving parts of this spec
>> as normative while replacing other parts.
> 

Behind the introductory text, add:

As with any IANA-registered item,
a specification that further updates this registration will become visible in the reference column of the IANA registry (see Section 6.5).
As always, future specifications may update this appendix, other parts of this document, or both.
As always, please consult the registry to obtain the most recent update for this appendix.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email