On 23. Apr 2024, at 20:47, Salz, Rich <rsalz=40akamai.com@xxxxxxxxxxxxxx> wrote: > >> So it sounds like I should just cite the component RFCs, possibly in a nested reference to BCP 195. I can do that, and > it’s probably safer from a possible-future-changes perspective. > > FWIW, the markdown tooling does this: > "as described in BCP 14 [RFC2119] [RFC8174] ..." > > And then the entries have the RFC and BCP number: > [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>. Yes, but that is the wrong way forward. Given that we now have good referencegroup support, the reference should look like https://www.ietf.org/archive/id/draft-ietf-core-href-15.html#section-1.1-1 This is not the letter, but the spirit of RFC 8174… It also shows how a multi-RFC BCP reference looks like. Grüße, Carsten
