Re: [Technical Errata Reported] RFC3779 (7653)
Job Snijders <[email protected]> Wed, 27 Sep 2023 18:09:51 +0200
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Message-ID | <ZRRTz8HttwVYHno2@snel> |
Dear Russ, On Wed, Sep 27, 2023 at 11:29:51AM -0400, Russ Housley wrote: > Two thoughts below. > > > The following errata report has been submitted for RFC3779, > > "X.509 Extensions for IP Addresses and AS Identifiers". > > > > -------------------------------------- > > You may review the report below and at: > > https://www.rfc-editor.org/errata/eid7653 > > > > -------------------------------------- > > Type: Technical > > Reported by: Job Snijders <[email protected]> > > > > Section: 3.2.3 > > > > Original Text > > ------------- > > Section 3.2.3.4: > > Any contiguous series of AS identifiers MUST be combined into a single range > > whenever possible. > > > > Section 3.2.3.8: > > The ASRange type is a SEQUENCE consisting of a min and a max element, > > and is used to specify a range of AS identifier values. > > > > Corrected Text > > -------------- > > Section 3.2.3.4: > > Any contiguous series of AS identifiers MUST be combined into a single range > > or, whenever possible, represented as a single ASId. > > I don't like "or, whenever possible". That is not well specified and > thus unlikely to yield a canonical result. In my view, this text is > not an improvement to the existing text. I see your point. Can someone with the right permissions edit the errata to remove the two sentences about section 3.2.3.4? > > Section 3.2.3.8: > > The ASRange type is a SEQUENCE consisting of a min and a max element, > > and is used to specify a range of AS identifier values. The min and max > > elements MUST specify two distinct AS identifiers. > > This statement seems clear to me, and I think it is an improvement over the current text. Thanks Kind regards, Job