>> It was pointed out to me that RFC4949 as a normative >> reference here is a downref, and I didn't call that >> out during the IETF LC for this document. (Sorry about >> that.) Oddly, 4949 hasn't previously been added to the >> downref registry. [1] > > That surprises me, given that RFC 4949 is already a normative reference from > draft-ietf-uta-tls-bcp as well as RFC 6749 and RFC 7489 (both of which are > standards-track).
It surprised me too. We missed it for uta-tls-bcp and 6749 (OAuth). 7489 (DMARC) is not Standards Track. >> 2. I re-do the IETF LC just for this point and we put 4949 >> into [1] so this won't be a deal for other drafts in >> future > > Someone needs to blaze this path, so it might as well be us. That's my preference, It's a small delay, less than two weeks... then we add 4949 to the downref registry and we're set for the future. While Joel might like to ignore the process, we can't; RFC 3967 (BCP 97) is explicit: For Standards Track or BCP documents requiring normative reference to documents of lower maturity, the normal IETF Last Call procedure will be issued, with the need for the downward reference explicitly documented in the Last Call itself. Any community comments on the appropriateness of downward references will be considered by the IESG as part of its deliberations. I think we should change that and allow us to do the right thing without having to be, as Peter puts it, process sticklers. I will be happy to AD-sponsor 3967bis, if anyone would like to write it and deal with the discussion. I think no one benefits from this second last call. But we do have a BCP in which we, as a community, set up this process, and until it's changed we have to follow it, at least when we notice that it's needed. Sigh. Barry _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
