Re: [Last-Call] Last call comments on draft-ietf-sedate-datetime-extended-08

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi John,

Thank you for your comments!
I’ll address them in installments, let me start at the end now.

> On 2023-06-14, at 06:53, John C Klensin <john-ietf@xxxxxxx> wrote:
[…]
> (3) Robert Sparks's Genart review [1] identifies several other
> places where the specification is ambiguous as to what is
> actually allowed.   I disagree with him only in that I do not
> believe that list adds up to "Ready with Issues" but, instead,
> that his list identifies things that the community (and the IESG
> on its behalf) should insist on being clarified before the I-D
> is approved.  For most or all of them, I believe that making
> decisions and getting them clearly expressed is more important
> than what the decisions actually are.  […]

Please see 
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/ZTQH7yDmPme66lyN-LmNwJKqBZg>

…and the interesting thread that started from Robert’s comments.

So far, I have created
https://github.com/ietf-wg-sedate/draft-ietf-sedate-datetime-extended/issues/46
from the thread, which I think is a good point to discuss.

> p.s. as a strictly editorial matter that would not be worth
> mentioning except insofar as it is a symptom that the authors
> and WG were not quite finished with this document before asking
> that an IETF Last Call be initiated, there are five BCP
> documents (six entries) listed as Normative References.  Two of
> them are listed by BCP numbers, the others, including two that
> make up one BCP, are listed by RFC numbers.  Is there any reason
> for that distinction other than to confuse the reader?

The reason is (a) that we forgot one [2], but (b) mainly didn’t make this fully consistent because the referencegroup support in today’s RFCXML/xml2rfc is awful.
I’d rather fix BCP13 together with the RPC, and not at this stage.
(I don’t think we want to fix BCP14 because we have agreed text in RFC 8174 that does not use a BCP reference.)

[2]: https://github.com/ietf-wg-sedate/draft-ietf-sedate-datetime-extended/pull/47

More later…

Grüße, Carsten

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux