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

Brian E Carpenter <> Fri, 19 June 2020 05:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DC5493A0E14 for <>; Thu, 18 Jun 2020 22:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VB1b-XQQ6lL6 for <>; Thu, 18 Jun 2020 22:11:35 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::1041]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 470593A0E10 for <>; Thu, 18 Jun 2020 22:11:35 -0700 (PDT)
Received: by with SMTP id k2so3595986pjs.2 for <>; Thu, 18 Jun 2020 22:11:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=HGbiWU8PvtfEoReYCxJ5e+VJccq97/l9NMKIaN7gug0=; b=Zn6hPZOILg0rKDF5XILrBYtSAYQp/Wqh5tB/7ibP3e8+rzzcxz7lKfg2hxxReM9Csk kVQUGQgokkh8ViXj8scR6PfF0yda1q2ifTjUVubWjqyULUApPLiW2i2YFWoD5YdmpMq7 UJSFRejZB0BMn7t/eeUfak9MYYRjZSGzbUwxCwZwhcFrQaxnkGNBYodApxTWF+1B8bSz lVb54wwsrzMST9d9jO1GX4KfU57VDhivyGcUnq5PVxugMm+Mz5/X6TDmsWuCJu4SQ8Bz +rlNgCELaA+iHAKK5Uj1lPmwaiSmN3GBLZstxTRWOaYT/udnxgiFhdIpDR0SLqiiR8dR l6Cw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HGbiWU8PvtfEoReYCxJ5e+VJccq97/l9NMKIaN7gug0=; b=dFarpJ8N1KtVKRSuWGZFB3CXIHLbfDH4Jp8fsjThgAvb3cCZCPHrs6XFkmXN9zbxgF iDMvEz/BZWN1SqYqy90JY91ldQU4PElttbO3zOVBAibfHSnJUJWL/TSxRuRrtzbgT3Dp TsFMK8jRMWqqlCJGo7d80kmAYzkSaU+u7jibvLhMRtz9z1ey1RDNxKjEWJuEjwz+1/Wm v4GX9m4/d+e3ZamKYoJqCh9vPms8+3HtN6JL2HXLoHeA/T8p91iJa760+KmZjHI/Fxuy +78TOrHWoGDm7OyIyXXnt9itao6GM19EhcKY47MyXlPfLze+yfdQ6UlEpWGh1cHhjvA+ loMA==
X-Gm-Message-State: AOAM533C7vWjry7XS3JCr3/vOGrGMK9FzoiTxkIoQQaK+Y9jqiJORzeg 461CqR+MNOKTY5rgV3RixYY=
X-Google-Smtp-Source: ABdhPJwV9IIdtd7tdlPCdvUiJzy8L6pg9e1UumcmNF9ltizVk7C2ScHwShzp58SWJKl4YwfMSwPmug==
X-Received: by 2002:a17:90a:7c07:: with SMTP id v7mr1773844pjf.38.1592543494437; Thu, 18 Jun 2020 22:11:34 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id a63sm3075424pfd.111.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Jun 2020 22:11:33 -0700 (PDT)
To: Benjamin Kaduk <>
Cc: Michael Richardson <>,, Russ Housley <>,
References: <11428.1592266833@localhost> <> <>
From: Brian E Carpenter <>
Message-ID: <>
Date: Fri, 19 Jun 2020 17:11:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Anima] rfc822Name use in Autonomic Control Plane document
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 19 Jun 2020 05:11:37 -0000

Hi Ben,

(Back on line after a couple of days spent moving apartments.)

On 17-Jun-20 14:44, Benjamin Kaduk wrote:
> Hi Brian, Michael,
> On Tue, Jun 16, 2020 at 02:14:24PM +1200, Brian E Carpenter wrote:
>> On 16-Jun-20 12:20, Michael Richardson wrote:
>>> Hi, I have had a few conversations with Toerless who is trying to deal with
>>> the feedback on the ACP document.
>>> An item that has come up is the use, or claimed abuse of the rfc822Name SAN.
>>> We already had this debate.
>>> Some time ago.  The WG decided.
> With all due respect, this is not the sole decision of the ANIMA WG to
> make.  If WGs had such authority then why bother with cross-area review?

Yes, but that was exactly the reason we had the discussion a year ago.

>>> Three or four years ago, I think.
>> Yes, this is relitigating an issue that was resolved a long time ago in discussing Ben's DISCUSS:
> I'm not sure I understand why you use the word "resolved" here:
> In this message, I say that "I still feel like this is not the best
> architectural choice" and that I will provide a sketch of an alternative in
> my (then-)forthcoming ballot position; that ballot position retains the
> Discuss-level concern about rfc822Name usage along with the promised
> alternative.
"Not the best choice" is not a DISCUSS criterion according to the IESG's own rules at

It was exactly this sort of endless debate over "best choice" disagreements that caused the IESG to adopt the DISCUSS criteria rules in the first place.

If you are saying that one of the criteria in applies, that's a different matter, of course. But really, no AD should hold a DISCUSS over "not the best choice".

Not to mention that this is only a Proposed Standard discussion; perfection not required.

I don't consider myself enough of a subject matter expert to comment on the technical issue itself.


>> The explanation is at
> I appreciate that the attempted justification is clearly written; however,
> I do not find it compelling.  Russ did not, either, and I just heard back
> from Sean Turner a few days ago to confirm that he supports Russ's
> comments.  (There should be a few other editorial-ish comments that came
> out of that review that are still pending.)
>> I believe it is incorrect IETF process to rediscuss this point yet again.
> (I'm not sure if the "yet again" refers to "after the WG decided" or "after
> the (alleged) resolution of my first Discuss point".)
> If you believe the technical answer is clear and that I am in error to
> continue to hold my Discuss point for it, are there not also clear IETF
> processes to follow?  E.g., asking for the "Single Discuss" ballot procedure
> described at  I
> believe I have mentioned this option to Toerless previously; my apologies
> if that is not the case.  While I'm willing to continue discussing the
> topic and pull in additional PKIX experts to weigh in, there is perhaps
> some consideration to matters of expediency.
>>> I sure wish that we could use something else.
>>> But, CAs and CA software make that very difficult.
>>> Given that the era of publically anchored Enterprise CAs is dead, there are
>>> only two ways an (Enterprise) ACP Registrar is going to occur.
>>> 1) by running a private CA.
>>>    Sure anything is possible if you are writing your own code, but
>>>    most will not be doing that. (I've supported otherName in my code for
>>>    other purposes, and it's not that difficult, but it's not trivial either)
>>>    My experience with COTS CA systems it that it's really hard to
>>>    get them to do it.    Please prove me wrong.
> (Sadly, I have zero experience with COTS CA systems; I know too much about
> openssl at this point and would presumably be writing my own, in this
> position.)
>>>    The most popular Enterprise CA software is the Microsoft CA.
>>> 2) by using ACME to speak to a hosted CA.  Maybe WebPKI, maybe not.
>>>    Either way, getting otherName supported is even harder, because
>>>    nobody else uses it.
> Is the concern the ACME protocol support or just getting the hosted CA to
> cope with it?  The former seems like something that we could make happen in
> the IETF, and the latter seems to have high overlap with point (1).
>>> If we can't depend upon otherName being filled in, then we have to look for
>>> two things.  That means more code paths (two more) to test, more test
>>> vectors, and what exactly does an end point do when both are present, BUT
>>> THEY DO NOT MATCH?  So three more pages of text there.
>>> Remember, that just rejecting the certificate means that we have to send out
>>> a truck, which is what ACP aims to avoid, so that won't be popular.
>>> And of course, there could also be bugs (maybe even CVEs) in the code that
>>> tries to deal with the tie.
> To be honest, this argument feels like a stronger one to me than the bits
> in the -24.  I'm still not willing to accept into the RFC Series a document
> that violates the rules set down by the specification for the technology
> it's making use of, but the refocus on the "running code" aspect is
> appreciated.
> -Ben