|
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 |
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
