[pkix] Re: [Technical Errata Reported] RFC3280 (9097)

Russ Housley <housley@vigilsec.com> Mon, 10 August 2026 18:42 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: pkix@mail2.ietf.org
Delivered-To: pkix@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F3CE3127558B9 for <pkix@mail2.ietf.org>; Mon, 10 Aug 2026 11:42:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786387374; bh=EizMLb1PSF3RMqSj9YiXIL/zfAzeQVgDHft/iy98D5Q=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=vmESmHH171jd7TM+87SPirVBDaxq8xDAxaQ18CiEH6OPuxyjW9V3DHJ3urLdmX8wl WmJGLoSvuftyN4ktuTxjySoUWNpzsOPBFTuc4UukAkBxBw8bogrxbj1PuPUeiDJsOb ULBBCLtsqe22NMSWfoZYlXlWzw2283xDcmelH2DQ=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6RpApM7qgYzG for <pkix@mail2.ietf.org>; Mon, 10 Aug 2026 11:42:54 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6508C127558B1 for <pkix@ietf.org>; Mon, 10 Aug 2026 11:42:54 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 391471A1350; Mon, 10 Aug 2026 14:42:54 -0400 (EDT)
Received: from smtpclient.apple (unknown [47.132.26.223]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 8A7511A14B6; Mon, 10 Aug 2026 14:42:53 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <178638013060.15.1586891668281190866@rfc-editor.org>
Date: Mon, 10 Aug 2026 14:42:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <12F9F721-4119-4DA0-B668-B2CD5E5BA075@vigilsec.com>
References: <178638013060.15.1586891668281190866@rfc-editor.org>
To: rfc-editor@rfc-editor.org
X-Mailer: Apple Mail (2.3864.600.51.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=pair-202402141609; bh=T0eRcXUrg3G4zRaqYxw4w5W1qAiP9OQBPBwN/CixjWo=; b=hJLf6hYQgU+B/hmqAScDNiUCG02irHJTYjsROUgtnppKg9E4PFR57ZlTABtzAu7O4rXo+K4LSqQpxgvJ7y5rqQOH3TDvmyuzcnI2BqtYUWWiPGgqHcW2LF0M3yN7hh0KV+I5oZ+4A7eccAKlLFxhGBKdDE3T1UU8yFWCeZTl97OuC1R7BbfNSSdEbil/WOXs8/JrHv2RHayQnBBZsRsrWdox+H5dU3PtnIQPWtPFX+QBL/oxr8YbcLMy3Bxoy2Qj+q9x4LjQtkIx6znu1j+AVHE2bmH1m3ZQj01SDlZ2mXeTJdy9t09mP+xyu1s6y+pgfSmibgIS+Ns0LsxbiciIjw==
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Message-ID-Hash: ZSRAPHPW6FNMXGXKKBLTVNKVHYS6Y7VQ
X-Message-ID-Hash: ZSRAPHPW6FNMXGXKKBLTVNKVHYS6Y7VQ
X-MailFrom: housley@vigilsec.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pkix.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tim.polk@nist.gov, dsolo@alum.mit.edu, Chris Inacio <stndrds-inacio@andrew.cmu.edu>, 1174804262@qq.com, IETF PKIX <pkix@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [pkix] Re: [Technical Errata Reported] RFC3280 (9097)
List-Id: PKIX Working Group <pkix.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/YUo7UD_dTHxzbGBJvLo-FzF48TM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Owner: <mailto:pkix-owner@ietf.org>
List-Post: <mailto:pkix@ietf.org>
List-Subscribe: <mailto:pkix-join@ietf.org>
List-Unsubscribe: <mailto:pkix-leave@ietf.org>

RRC 3280 is obsolete; it has been replaced by RFC 5280.  I do not see any reason to process this errata.

Russ

> On Aug 10, 2026, at 12:42 PM, rfc-editor@rfc-editor.org wrote:
> 
> The following errata report has been submitted for RFC3280,
> "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"
> 
> --------------------------------------
> You may review the report below and at:
> https://errata.rfc-editor.org/eid9097/
> 
> --------------------------------------
> Type: Technical
> Reported by: Peng Yuan <1174804262@qq.com>
> 
> Section 4.1.2.2 says:
> 
> Original Text
> -------------
> The serial number MUST be a positive integer assigned by the CA to
>   each certificate.  It MUST be unique for each certificate issued by a
>   given CA (i.e., the issuer name and serial number identify a unique
>   certificate).  CAs MUST force the serialNumber to be a non-negative
>   integer.
> 
> Corrected Text
> --------------
> The serial number MUST be a positive integer assigned by the CA to
>   each certificate.  It MUST be unique for each certificate issued by
>   a given CA (i.e., the issuer name and serial number identify a
>   unique certificate).  CAs MUST force the serialNumber to be
>   positive integer.
> 
> Notes
> -----
> r/non-negative/positive
> The text contains inconsistent requirements for the certificate
> serialNumber. The first sentence requires the serial number to be a
> positive integer, which excludes zero. However, the last sentence
> requires CAs to force the serialNumber to be a non-negative integer,
> which permits zero. These two requirements are contradictory and may
> cause ambiguity for certificate issuers regarding whether a serial
> number of zero is permitted. The last sentence should use "positive
> integer" instead of "non-negative integer" to maintain consistency
> within this section.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC3280 (draft-ietf-pkix-new-part1)
> --------------------------------------
> Title               : Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
> Publication Date    : May 2002
> Author(s)           : R. Housley, W. Polk, W. Ford, D. Solo
> Category            : Proposed Standard
> Source              : pkix (sec)
> Stream              : IETF
> Verifying Party     : IESG