Re: [Acme] Proposed ACME Charter Language

hallam@gmail.com Sat, 25 April 2015 20:20 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 936A51B3010 for <acme@ietfa.amsl.com>; Sat, 25 Apr 2015 13:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 KBC6V-THeMvF for <acme@ietfa.amsl.com>; Sat, 25 Apr 2015 13:20:22 -0700 (PDT)
Received: from mail-vn0-x230.google.com (mail-vn0-x230.google.com [IPv6:2607:f8b0:400c:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFD5A1B300E for <acme@ietf.org>; Sat, 25 Apr 2015 13:20:21 -0700 (PDT)
Received: by vnbg190 with SMTP id g190so7497732vnb.8 for <acme@ietf.org>; Sat, 25 Apr 2015 13:20:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yh8nUlefmKIl5cz+F/qR59jFa6aFMneYSU9K7KHi2eU=; b=NiM2SJbOAoieB7QB1scAwhYzAfyG/ZiZDm1DjpZzIgsO57Y+ZaYHtgoDBSijsi+jP9 Gul7xITfKYC3pN0Q9Ii39u2Fiqn9DaWAGB8xMsECrMtCA9q/W1OOaAEPezh57ikXxz9U jH5nv7wHglPgOw3anVrqwOgrKDw5tR0zKlNaFJ6C4YzqCRp6RQTh4FPKen7v3MMJR8Sg neT2XHHKXRloDnZ/ONUj/t9rYDXiG1IkWoguxomP3DJN6gYPzpG+PKF1lyhjkyE1/g6f 804Pza92/GCHiAbQNPsr7fM+auvcSOcMaZbxq8OkmYMekvbTZza8JxHCXbpOiZKtgxnP gDbA==
X-Received: by 10.52.74.161 with SMTP id u1mr10524381vdv.72.1429993220973; Sat, 25 Apr 2015 13:20:20 -0700 (PDT)
Received: from [10.112.106.79] (mobile-107-107-56-146.mycingular.net. [107.107.56.146]) by mx.google.com with ESMTPSA id s2sm12484173vdh.8.2015.04.25.13.20.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Apr 2015 13:20:19 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-DBE57E3B-7BC8-45AC-8136-4B30F6D58EBB
Mime-Version: 1.0 (1.0)
From: hallam@gmail.com
X-Mailer: iPhone Mail (12F70)
In-Reply-To: <CABcZeBOy2yBEMGMxcDy=E3fvc+OF1sZfvOV7twJHAvKqtrxtLg@mail.gmail.com>
Date: Sat, 25 Apr 2015 16:20:16 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <28919F11-9336-41F6-9922-4E3E2DC4E935@gmail.com>
References: <6A9C3116-8CC9-472C-8AA8-F555D060834C@vigilsec.com> <55351EAB.1060905@cs.tcd.ie> <E81896AA-245F-48B7-9B38-86AC30D2F82A@vigilsec.com> <553523E4.2090808@cs.tcd.ie> <84718B26-1DA3-4D46-8B6F-B615806229D7@vigilsec.com> <CABcZeBOy2yBEMGMxcDy=E3fvc+OF1sZfvOV7twJHAvKqtrxtLg@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/OLAgHDv9JYUvijv0nNB9kfIjQS0>
X-Mailman-Approved-At: Sat, 25 Apr 2015 13:47:02 -0700
Cc: IETF ACME <acme@ietf.org>, Russ Housley <housley@vigilsec.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Acme] Proposed ACME Charter Language
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Apr 2015 20:20:24 -0000

+1

Arguments as to whether something is new get tedious. 

Sent from my iPhone

> On Apr 25, 2015, at 4:05 PM, Eric Rescorla <ekr@rtfm.com>; wrote:
> 
> 
> 
>> On Mon, Apr 20, 2015 at 9:11 AM, Russ Housley <housley@vigilsec.com>; wrote:
>> Stephen:
>> 
>> If that paragraph were removed, would you be happier with the charter?  If so, consider it gone.  I'm willing to assume that an attempt to replace things that people are using will meet with vigorous discussion.
> 
> I would suggest we do as you propose and remove this text. I think there will
> be plenty of occasion for people in the WG to argue about using existing stuff
> versus building anew.
> 
> -Ekr
>  
>> 
>> Russ
>> 
>> 
>> On Apr 20, 2015, at 12:05 PM, Stephen Farrell wrote:
>> 
>> >
>> >
>> > On 20/04/15 16:57, Russ Housley wrote:
>> >> Stephen:
>> >>
>> >> I did not see the ACME effort as trying to throw everything out.
>> >
>> > If it is not used, then I don't think we're throwing it out:-)
>> >
>> >> Rather, throw out the parts that have been an impediment to the kind
>> >> of automation proposed by ACME, but document the shortcoming.
>> >
>> > Sorry, I'm still not getting it. I don't see any need for ACME
>> > to document why CMP etc failed or what was wrong with CMP that
>> > may have caused it to fail. And the same for CMC etc. BTW by
>> > "fail" here I mean: not used by the major deployed PKIs on the
>> > public Internet.
>> >
>> > I also see no need at all to even try to re-use ASN.1 PDU
>> > structures that are defined in CRMF etc.
>> >
>> > I do think that ACME ought learn from the past of course, and
>> > am confident that there will be enough participants involved
>> > who have that history for that to not be problematic.
>> >
>> > But I do not think ACME ought be required to re-use any ASN.1
>> > PDU definitions from any previous RFCs on this topic.
>> >
>> > Do we agree or disagree on that last? (I'm trying to get to
>> > quite specific meanings for "duplicate.")
>> >
>> > Cheers,
>> > S.
>> >
>> >
>> >
>> >>
>> >> Russ
>> >>
>> >> On Apr 20, 2015, at 11:43 AM, Stephen Farrell wrote:
>> >>
>> >>>
>> >>> Hi Russ,
>> >>>
>> >>> This bit puzzles me a lot, other bits puzzle me a little:-)
>> >>>
>> >>> On 20/04/15 16:23, Russ Housley wrote:
>> >>>> The ACME WG will not duplicate work from previous IETF
>> >>>> certificate management efforts.
>> >>>
>> >>> If accepted, that would seem to me to nullify the entire effort.
>> >>> Can you explain why I'm reading it wrong?
>> >>>
>> >>> ACME absolutely will duplicate work from previous IETF certificate
>> >>> management efforts that have failed to get traction over the last
>> >>> decade and a half. That is entirely fine IMO and needs no explicit
>> >>> justification whatsoever since we have 15 years of crystal clear
>> >>> non-use, outside of niche environments. (It is true that what is
>> >>> now considered a niche was not so considered back then.)
>> >>>
>> >>> In fact I believe anyone who claims such duplication is a problem
>> >>> should be the one to provide evidence for that by documenting
>> >>> exactly why and at what scale.
>> >>>
>> >>> It is just not credible for us to pretend that CMC, CMP, or EST are
>> >>> widely used for certificate management on the public Internet. If
>> >>> I'm wrong there I would really love to see the evidence but absent
>> >>> such, duplicating bits of functionality present in current RFCs
>> >>> that are not at all widely used is what is needed for this effort
>> >>> and needs to be encouraged.
>> >>>
>> >>> I think we really ought bottom out on this aspect before chartering
>> >>> - it'd be dumb of us to charter an ACME WG that has to fight all
>> >>> the CRMF battles over again, or the ASN.1 vs. whatever issues. So I
>> >>> hope lots of voices chime in and say what they think.
>> >>>
>> >>> S.
>> >>>
>> >>> _______________________________________________ Acme mailing list
>> >>> Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
>> >>
>> >>
>> >>
>> 
>> _______________________________________________
>> Acme mailing list
>> Acme@ietf.org
>> https://www.ietf.org/mailman/listinfo/acme
> 
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme