IETF Logo Mail Archive

[lamps] CMP vs RFC5280

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 19 March 2024 02:10 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11BA5C151095 for <spasm@ietfa.amsl.com>; Mon, 18 Mar 2024 19:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 y6c5F1EaFmIR for <spasm@ietfa.amsl.com>; Mon, 18 Mar 2024 19:10:10 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 1C693C15108B for <spasm@ietf.org>; Mon, 18 Mar 2024 19:10:09 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [111.65.68.203]) by relay.sandelman.ca (Postfix) with ESMTPS id A3A2A1F4A8 for <spasm@ietf.org>; Tue, 19 Mar 2024 02:10:06 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="Pw9sB6Pj"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 8543EA17CB; Tue, 19 Mar 2024 12:09:59 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1710814199; bh=PFYExCz97DvtuLpWkmj7ERrDhj6ZQN9fZvuT4zuuJV8=; h=From:To:Subject:Date:From; b=Pw9sB6PjO1+fkg52GLxz2H69G5zjTWoqskzO/n//nfaVap6yQS8fUefuqVhrXdt2J u7X9VmFIEftAudQlOxuB4DAJq+hsyv7H+V4wr+kp0I/6n/wF49Yi3/H+uwrBZ/nT9/ H0moV9vtEgDqpSt2Ks3XZtQjoKk/oE8DN6irJBrMvv7RihodH0D9R6MmKYDAtaxEML l6ewzyti5ts0bfGtPhkYj55a1tjJTWLNkXWj2mWS0SjSnKWTYPytZmuH9trOvBDL2m 26wSNPnnFdXqWaAJ1K5eXtY+6ziYiMELoeiFOcen1fziSJhtbXjD3pbc4hYCGP6ikK TB83+3ltTA5rA==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 82CD9A053B for <spasm@ietf.org>; Tue, 19 Mar 2024 12:09:59 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: spasm@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 19 Mar 2024 12:09:59 +1000
Message-ID: <93275.1710814199@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/HLKh0HPcWR_LPPaa4lyl00W1yck>
Subject: [lamps] CMP vs RFC5280
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2024 02:10:14 -0000

In https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc4210bis/  it says:

   The term
   "certificate" in this document refers to an X.509v3 Certificate as
   defined in [ITU.X509.2000].

and I wondered why an ITU document is referred to, rather than RFC5280.
Further, why the 2000 era document, when I think there is a 2019 one.

{at least, the 2019 version is freely available, but I can't find the 2000
era document easily}

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.23.0 | Report a Bug | By Email