Re: [lamps] I-D Action: draft-ietf-lamps-rfc7030-csrattrs-08.txt

Russ Housley <housley@vigilsec.com> Mon, 04 March 2024 15:06 UTC

Return-Path: <housley@vigilsec.com>
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 B6689C14F5E3 for <spasm@ietfa.amsl.com>; Mon, 4 Mar 2024 07:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=vigilsec.com
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 EU3R_PL0aTXD for <spasm@ietfa.amsl.com>; Mon, 4 Mar 2024 07:06:50 -0800 (PST)
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0FADC14F6A0 for <spasm@ietf.org>; Mon, 4 Mar 2024 07:06:50 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id E0C6514EB0E for <spasm@ietf.org>; Mon, 4 Mar 2024 10:06:49 -0500 (EST)
Received: from smtpclient.apple (pfs.iad.rg.net [198.180.150.6]) (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 C905E14EA14 for <spasm@ietf.org>; Mon, 4 Mar 2024 10:06:49 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Mon, 04 Mar 2024 10:06:39 -0500
References: <170951366354.6144.9138649357211538117@ietfa.amsl.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <170951366354.6144.9138649357211538117@ietfa.amsl.com>
Message-Id: <77BEC813-D6E7-428B-AAA8-0E4358EC80CE@vigilsec.com>
X-Mailer: Apple Mail (2.3731.700.6)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:content-type:content-transfer-encoding:mime-version:subject:date:references:to:in-reply-to:message-id; s=pair-202402141609; bh=Dg3WYoKf9kUaGJCqMzAGXipFtrL29l2UHQquDyz7g4c=; b=nE/pPtRXfek5J1yDdBU2fFbaf6Pyj4rY7RL6/gKkVhTVTo4ikh4bbg/1OcqGjAQFcR2mDrI3/Pg4wKN3rD1lHSRhSzlOh0vTEeBnFniovYPZ27aHCxlfiEb5maTeDjI25rTfEjGr02go7AQZgQMxgXZTXXZTYyQtkyGNdZ1g8GPEI1+PDR9v7LWD2fEx9gDRsepkdFOH6bSwnLf5gXV2J/U+DlkISy/lXNZoZxMLeihF3xosziNwZEbTY3xPfzkl9bgewqdmuttc/n0W2qbPNuAo0oCP6CaJKXTyAMh7nfcLjxUrRkf5wn7eBKMejJrrs9p/zxQJuFubrF0dnzh8UQ==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/L1uUteiIRVSKwLI6JpDT_ZGQWE4>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-rfc7030-csrattrs-08.txt
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: Mon, 04 Mar 2024 15:06:54 -0000

Authors:

It looks like this text resolves the open issues that I know about.
Is this ready for WG Last Call?

Russ


> On Mar 3, 2024, at 7:54 PM, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-ietf-lamps-rfc7030-csrattrs-08.txt is now available. It
> is a work item of the Limited Additional Mechanisms for PKIX and SMIME (LAMPS)
> WG of the IETF.
> 
>   Title:   Clarification of RFC7030 CSR Attributes definition
>   Authors: Michael Richardson
>            Owen Friel
>            Dr. David von Oheimb
>            Dan Harkins
>   Name:    draft-ietf-lamps-rfc7030-csrattrs-08.txt
>   Pages:   20
>   Dates:   2024-03-03
> 
> Abstract:
> 
>   The Enrollment over Secure Transport (EST, RFC7030) is ambiguous in
>   its specification of the CSR Attributes Response.  This has resulted
>   in implementation challenges and implementor confusion.
> 
>   This document updates RFC7030 (EST) and clarifies how the CSR
>   Attributes Response can be used by an EST server to specify both CSR
>   attribute OIDs and also CSR attribute values, in particular X.509
>   extension values, that the server expects the client to include in
>   subsequent CSR request.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc7030-csrattrs/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-lamps-rfc7030-csrattrs-08.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lamps-rfc7030-csrattrs-08
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm