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

Russ Housley <housley@vigilsec.com> Fri, 30 September 2022 16:40 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 A9E2CC1524A1 for <spasm@ietfa.amsl.com>; Fri, 30 Sep 2022 09:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 YAmX8Rlt6Eow for <spasm@ietfa.amsl.com>; Fri, 30 Sep 2022 09:40:46 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5D98C1522A7 for <spasm@ietf.org>; Fri, 30 Sep 2022 09:40:45 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id B33C3C7612 for <spasm@ietf.org>; Fri, 30 Sep 2022 12:40:44 -0400 (EDT)
Received: from [10.0.1.2] (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 A23F3C71F2 for <spasm@ietf.org>; Fri, 30 Sep 2022 12:40:44 -0400 (EDT)
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 12.4 \(3445.104.21\))
Date: Fri, 30 Sep 2022 12:40:44 -0400
References: <166455529121.57946.12490739958683425020@ietfa.amsl.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <166455529121.57946.12490739958683425020@ietfa.amsl.com>
Message-Id: <75552DF2-990C-4444-99F4-C905BEB230B5@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/p6HvSUxK-pIDAQ2hjJZE-hB4ywY>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-rfc7030-csrattrs-01.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <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: Fri, 30 Sep 2022 16:40:49 -0000

You are using very different formats to show the examples in Section 5.1 and Section 5.2.  Can you pick one?

Russ


> On Sep 30, 2022, at 12:28 PM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Limited Additional Mechanisms for PKIX and SMIME WG of the IETF.
> 
>        Title           : Clarification of RFC7030 CSR Attributes definition
>        Authors         : Michael Richardson
>                          Owen Friel
>                          Dr. David von Oheimb
>                          Dan Harkins
>  Filename        : draft-ietf-lamps-rfc7030-csrattrs-01.txt
>  Pages           : 9
>  Date            : 2022-09-30
> 
> 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 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-01.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-lamps-rfc7030-csrattrs-01
> 
> 
> 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