On Thu, Oct 23, 2025 at 04:34:44PM -0400, StJohns, Michael wrote: > Yes but… > > What does a reference to an asn1 module look like in the reference > section? E.g. RFC5911 has a bunch of modules. I could use only that, but > sometimes a more precise reference would be useful.
For modules that appear in RFC 5911 or 5912 I'd rather see two references: one to RFC 5911 or 5912, yes, and one to the most recent original (e.g., RFC 5280). Between the module name (and OID if it has one) and a comment with the relevant RFC(s) it should be enough. > Specific example - I’d like to reference in the text where ATTRIBUTE is > declared given that simple searches for it in 5912 most end up finding the > sub declarations that depend on ATTRIBUTE. I agree, I too have seen references to ASN.1 types w/o much in the way of clues as to where to find the canonical specification for it. > There are work arounds, but they feel a bit like hacks. Maybe we should ask for the ITU-T SG 17 to extend `IMPORTS`'s GlobalModuleReference to provide additional details, like a URI, and then we should make use of it. It's 2025 and using URIs (and URNs) should be all the rage for this. Nico -- _______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
