On Thu, Aug 24, 2023 at 3:33 AM Mario Loffredo <[email protected]>
wrote:

> > It looks as though draft-ietf-jsonpath-base should be a Normative
> reference. In
> > fact, this is explicitly mentioned in the shepherd writeup (thank you!):
> >
> >          > 15. Should any informative references be normative or
> vice-versa? See
> >          the [IESG >     Statement on Normative and Informative
> References][16].
> >
> >          JSON Paths are depended on normatively in the document, but the
> >          reference for them is to I-D.ietf-jsonpath-base, which is why
> that
> >          reference is informative.  (This is in keeping with e.g. RFC
> 8977,
> >          though in that case the reference was to the original
> description of
> >          the JSON Path behaviour at
> https://goessner.net/articles/JsonPath/.)
> >
> > However, that rationale doesn't make sense to me. If a normative
> reference is a
> > downref, "just stick it in the informative references section instead"
> is not
> > the appropriate fix, the usual thing is to keep it in the normative
> references
> > and then the RFC Editor deals with the mismatch by holding off on
> publication
> > of the dependent document, until the dependency is published (a so-called
> > "cluster").  In this case, draft-ietf-jsonpath-base is on the same IESG
> agenda
> > as draft-ietf-regext-rdap-reverse-search is, so there isn't even much
> reason to
> > worry that draft-ietf-regext-rdap-reverse-search will be stalled for
> long if at
> > all, the two will likely move together.
> >
> > The easiest way to resolve this DISCUSS would be to change the reference
> to
> > Normative. If for some reason that's considered unacceptable, I'd
> appreciate a
> > discussion explaining why, and why "make it an informative reference"
> should be
> > acceptable.
> >
> >
> [ML]  I fully agree with you.
>
> That reference is informative because I literally interpreted Note 4 but
> it should be normative.
>
> I'll move it to the Normative References.
>

Thanks John for noticing this (and pardon my amazement that I missed this
detail, which is something I normally look for), and Mario for the fix.

-MSK
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

Reply via email to