|
Hi Thomas, Thanks for drafting this text. I left a comment on the PR:
https://github.com/core-wg/core-problem-details/pull/43
but copying it here for visibility as well. All: I’ll take the opportunity to remind you that for any other comments or objections, please let me know before the 6th of July. Also: there is a CoRE interim [1] planned
for Wednesday, July 6th at 14:00 UTC with an item on the agenda to finalize this paragraph. To cover all comments I saw on the mailing list, can we add something about future updates not dropping part of the current text? (for example leaving the appendix out) OLD: As with any IANA-registered item, a specification that further updates this registration needs to update the reference column of the IANA registry (see {{iana-tag38}}). Future specifications may update this appendix, other parts of this document, or both. Please consult the registry to obtain the most recent update for this appendix. NEW (suggested): As with any IANA-registered item, a specification that further updates this registration needs to update the reference column of the IANA registry (see {{iana-tag38}}). Future specifications may update this appendix, other parts of this document, or both. Updates to this document need to be clear about what is being altered, and ought not discard this appendix without publishing it as a separate document. Please consult the registry to obtain the most recent update for this appendix. [1]
https://mailarchive.ietf.org/arch/msg/core/H4uDGhQ7MHo4_qflWEHoSQnkZZA/ Thanks,
From: Thomas Fossati <Thomas.Fossati@xxxxxxx> Hi all, Thanks Carsten and Francesca. This is now:
https://github.com/core-wg/core-problem-details/pull/43 > Francesca Palombini <francesca.palombini=40ericsson.com@xxxxxxxxxxxxxx> wrote: > Hi Carsten, >
> Editorial suggestions to the text below: I would remove the “As > always,”. Also rather than “will become visible in” something on the > line of “needs to update” would be better, IMO.
>
> Francesca >
> > Carsten Bormann <cabo@xxxxxxx> wrote: > > On 2022-06-30, at 11:57, Thomas Fossati <tho.ietf@xxxxxxxxx> 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 Cheers, t IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately
and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
|
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
