Re: [OPSAWG] [Technical Errata Reported] RFC8886 (6299)

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 13 April 2021 18:00 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6BA93A2117 for <opsawg@ietfa.amsl.com>; Tue, 13 Apr 2021 11:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DF-QdpIZO0Gs for <opsawg@ietfa.amsl.com>; Tue, 13 Apr 2021 11:00:07 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C45813A2111 for <opsawg@ietf.org>; Tue, 13 Apr 2021 11:00:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id F376E38FDA for <opsawg@ietf.org>; Tue, 13 Apr 2021 14:07:17 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8mS-sZ-Ty0gI for <opsawg@ietf.org>; Tue, 13 Apr 2021 14:07:17 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8C7DF38FD2 for <opsawg@ietf.org>; Tue, 13 Apr 2021 14:07:17 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 005D0375 for <opsawg@ietf.org>; Tue, 13 Apr 2021 14:00:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "opsawg@ietf.org" <opsawg@ietf.org>
In-Reply-To: <MN2PR11MB4366A200DDDDBCA78A3971A3B5709@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <20201005192449.5CC98F406D0@rfc-editor.org> <MN2PR11MB436697A1F966B91BC8A35C43B5709@MN2PR11MB4366.namprd11.prod.outlook.com> <BN6PR11MB16672778E922DCD780FBA5E6B8709@BN6PR11MB1667.namprd11.prod.outlook.com> <MN2PR11MB4366A200DDDDBCA78A3971A3B5709@MN2PR11MB4366.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 13 Apr 2021 14:00:04 -0400
Message-ID: <27083.1618336804@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/XvpWjeG_ly6Hc9Q3mI1gtXYurWc>
Subject: Re: [OPSAWG] [Technical Errata Reported] RFC8886 (6299)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 18:00:12 -0000

Rob Wilton \(rwilton\) <rwilton=40cisco.com@dmarc.ietf.org> wrote:
    > Stephane or Warren can probably can correct me as a butcher the
    > explanation, but ...
    > ... I think that the issue is that the appendix is given as sequence of
    > steps to follow, and in Step 1 (A.1), the certificate is generated
    > using an elliptical curve algorithm, which means that by the time that
    > you get to the step in A 2.2 ,the openssl command fails because openssl
    > doesn't allow you to S/MIME encrypt with the certificate generated in
    > A.1 that is based on an elliptic curve algorithm.

    > The solution to fix this would be to change the type of algorithm used
    > in Step 1 (A.1) to RSA, in which case this step would succeed.

That's one way to do it.
ECIES would also work, but maybe openssl CMS can't do that.

Given that
a) it's non-normative example.
b) in practice doing this with openssl shell commands is not a good solution
   (error handling, database access, etc.)

I suggest that we acknowledge the error (should use RSA), but that there
isn't a simple text change.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide