IETF Logo Mail Archive

[pkix] [Technical Errata Reported] RFC3779 (7653)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 September 2023 12:17 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C99A8C14CE33 for <pkix@ietfa.amsl.com>; Fri, 22 Sep 2023 05:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g4aPJA9sd9Bc for <pkix@ietfa.amsl.com>; Fri, 22 Sep 2023 05:17:46 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21449C1519A4 for <pkix@ietf.org>; Fri, 22 Sep 2023 05:17:46 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id D1D50E5F67; Fri, 22 Sep 2023 05:17:45 -0700 (PDT)
To: CLynn@BBN.Com, Kent@BBN.Com, KSeo@BBN.Com, rdd@cert.org, paul.wouters@aiven.io, kent@bbn.com, stefan@aaa-sec.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: job@fastly.com, pkix@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230922121745.D1D50E5F67@rfcpa.amsl.com>
Date: Fri, 22 Sep 2023 05:17:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/YHgmts2NQkwqfD-7LFRX2GejSJE>
Subject: [pkix] [Technical Errata Reported] RFC3779 (7653)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2023 12:17:50 -0000

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 <job@fastly.com>

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.

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.

Notes
-----
The introduction in section 1 stresses that the objective of the encoding rules in section 2 and section 3
is to produce unique encoding and minimal size encoding of the information.

Allowing ASRanges where the minimum value is the same as the maximum value clearly violates the
objective of specifying a canonical form (in order to produce a unique representation); however the
specification as-is doesn't forbid min & max to be the same value. The corrected text addresses this.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC3779 (draft-ietf-pkix-x509-ipaddr-as-extn-03)
--------------------------------------
Title               : X.509 Extensions for IP Addresses and AS Identifiers
Publication Date    : June 2004
Author(s)           : C. Lynn, S. Kent, K. Seo
Category            : PROPOSED STANDARD
Source              : Public-Key Infrastructure (X.509)
Area                : Security
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email