IETF Logo Mail Archive

Re: [Anima] rfc822Name use in Autonomic Control Plane document

Russ Housley <housley@vigilsec.com> Sun, 21 June 2020 16:36 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31F9F3A0DD9 for <anima@ietfa.amsl.com>; Sun, 21 Jun 2020 09:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 Ub3lYXVhjQJ4 for <anima@ietfa.amsl.com>; Sun, 21 Jun 2020 09:36:11 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 990963A0DD8 for <anima@ietf.org>; Sun, 21 Jun 2020 09:36:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id EC05E300B1A for <anima@ietf.org>; Sun, 21 Jun 2020 12:36:08 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZPChNyi-SnPE for <anima@ietf.org>; Sun, 21 Jun 2020 12:36:07 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id DB25C300AF9; Sun, 21 Jun 2020 12:36:06 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <3A92516D-B980-4231-9059-EF7234BA8610@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F9224FF7-7BDB-49AE-8F48-8D28E7616F23"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Sun, 21 Jun 2020 12:36:06 -0400
In-Reply-To: <9406.1592756905@localhost>
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, Ben Kaduk <kaduk@mit.edu>, anima@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <11428.1592266833@localhost> <a0face89-da68-f75d-4a57-4deb9d0f244d@gmail.com> <20200617024412.GA11992@kduck.mit.edu> <9584c5cd-c68d-ddc3-0704-da672842e359@gmail.com> <FB6127DD-A111-4E40-A095-5E3C03AA6660@vigilsec.com> <9406.1592756905@localhost>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/WNCyTAKHdJTXiTenrvtdEjjfNJY>
Subject: Re: [Anima] rfc822Name use in Autonomic Control Plane document
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jun 2020 16:36:13 -0000


> On Jun 21, 2020, at 12:28 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Russ Housley <housley@vigilsec.com> wrote:
>> One cannot send email to the character string in this specification, so
>> it should not be carried in the rfc822name.
> 
> You can send email to that character string if you configure the MX.
> It was designed specifically to accomodate that.
> 
> I objected at the time: I thought it was a stupid feature, that no sensible IKEv2 daemon
> was going to have to send/receive email.
> 
> But, Toerless was paranoid that if we did anything at all out of the
> ordinary, that the corporate CA people, in order to protect their fiefdom,
> would freak out and throw some huge roadblock in the way of deploying the ACP.
> 
> And, now have an ACME method past WGLC that does certificate validation by
> SMTP.

Looking at the email certificate enrollment work in the ACME WG (draft-ietf-acme-email-smime-08), I have a hard time seeing how the device that knows the private key could participate in such a protocol.  How do you see it working?

Russ

v2.23.0 | Report a Bug | By Email