On Tue, Nov 17, 2026 at 04:30:57PM -0500, Russ Housley wrote:
> This looks right to me.  That said, for many years this terminology 
> disconnect has not prevented successful implementation.  I recommend "Hold 
> for Document Update".
> 
> Russ
> 
> > On Nov 16, 2026, at 1:48 PM, [email protected] wrote:
> > 
> > The following errata report has been submitted for RFC6487,
> > "A Profile for X.509 PKIX Resource Certificates"
> > 
> > --------------------------------------
> > You may review the report below and at:
> > https://errata.rfc-editor.org/eid9315/
> > 
> > --------------------------------------
> > Type: Technical
> > Reported by: Job Snijders <[email protected]>

What makes this change a technical erratum, not an editorial one?

> > Throughout the document, when it says:
> > 
> > Original Text
> > -------------
> > "IP Resources"
> > "AS Resources"
> > 
> > Corrected Text
> > --------------
> > "IP Address delegation"
> > "Autonomous System Identifier delegation"
> > 
> > Notes
> > -----
> > The phrases "IP Resources" or "AS Resources" were not used in RFC 3779, 
> > this corrigendum aligns the terminology to the actual specification.

The suggested capitalization in the Corrected Text is strange and does
not appear as such anywhere in RFC 3779.

While I'm sure it's one "correct" way to "fix" this per the IETF rules,
I never liked the inconsistent use of abbreviations chosen in RFC 3779
and I wish those could be fixed instead. It seems to me that with this
erratum two perfectly clear descriptions in RFC 6487 are replaced by
something rather clumsy.
_______________________________________________
sidr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to