Re: [Acme] Want client-defined callback port

Richard Barnes <rlb@ipv.sx> Thu, 23 April 2015 15:40 UTC

Return-Path: <rlb@ipv.sx>
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 3BDCD1ACD72 for <acme@ietfa.amsl.com>; Thu, 23 Apr 2015 08:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 XIK78n24rt0Z for <acme@ietfa.amsl.com>; Thu, 23 Apr 2015 08:40:32 -0700 (PDT)
Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) (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 51C421ACD31 for <acme@ietf.org>; Thu, 23 Apr 2015 08:40:17 -0700 (PDT)
Received: by lagv1 with SMTP id v1so15598270lag.3 for <acme@ietf.org>; Thu, 23 Apr 2015 08:40:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XX4B5KE4JZm2yhW2HR533GNRhnq4GrFG/xJNV8x2VLQ=; b=AK32p6dzx2yf7TekZaxqKdNE3aMZ6OAuzzAek6b4txcFqqA7m6lv2oOylo19aOqKT1 hB8TZ0Psap3sqsYtbh6fjqABD+UmKVjpBEv+F0sy8PVzws0Y/M0e5Q7v1W49vEiWwiMP 9ki5iFaagSBkgLyrDKsPA5boVkYmMppHqdC6NXCPcpiVyk1ApISHGsI25DVMhGfWR2il ryv7MdaNK5rQeN5Mc/AnlQ3WoKEMtwaEY/FrlZu03YxABD341Gsg+zrQIj8lbsaYlFPq lDQu8mXAYRlC4Oe4DrvvjKVgHbYEd+NPvc3f39ifo/gxHrKHTl6f2pFOHdfkfOCXycEI N1Vw==
X-Gm-Message-State: ALoCoQlcYK93GMC+sWd/b1PTljzuVdozP1BFpv592tlVntCOdo2TNBDBJb/cPa12d+3dUYVMsCl6
MIME-Version: 1.0
X-Received: by 10.112.202.234 with SMTP id kl10mr2928190lbc.51.1429803615884; Thu, 23 Apr 2015 08:40:15 -0700 (PDT)
Received: by 10.25.214.162 with HTTP; Thu, 23 Apr 2015 08:40:15 -0700 (PDT)
In-Reply-To: <CAMm+LwiR2tZVvWYOfKOMKybNNi9f52A_W4QGH6Bxx_haivFz3g@mail.gmail.com>
References: <352DA5FE-AC6F-49A7-8F9F-70A74889204F@apple.com> <CAK3OfOjey4bk02qC_jj2c0AzZ54qnP=KAJnG=mXnO6A5gZ4m9g@mail.gmail.com> <CAL02cgQ94ijVrCM9SStcodRW+XSG2w5Zwu3+ny8HriDBnxjdtg@mail.gmail.com> <FF21526F-BA8D-4F54-AAE3-047632706668@apple.com> <CAL02cgSDk0TNYusEkXA3onmqF7=kaAWhHjpW8WjbiqxgQMdQwQ@mail.gmail.com> <555F6C74-2416-4893-BDEA-A3C2E55A6D57@apple.com> <16985cf1c8c444c48d328fa766ec5ff8@usma1ex-dag1mb2.msg.corp.akamai.com> <DE264105-7317-4343-BCEE-539A73D42544@apple.com> <CAL02cgTv5Zi4wP0gJPvcrty6N96pAaLRkCveyvMNfoyjQrrEyw@mail.gmail.com> <0609C348-A6D8-46D5-AF58-5BE69910D261@apple.com> <CAL02cgT_DPY-Bn9A=UtCx+g2FKHON-TXGCWfH-gL8rR4yEFHZg@mail.gmail.com> <CA+9kkMAqte7O0k0KVRLRaEOmJL-wK0ncoruv3yoqKBjZVnc99g@mail.gmail.com> <CABkgnnVP4as97fXe7XTFpC=rw6ETdXY5s=1cRj1Xan1sgDsx3A@mail.gmail.com> <CAMm+Lwg5GiknSceb1Ocs=VxA1cZpmcrmZbPeXpgfAHbOC3CUcw@mail.gmail.com> <CAL02cgReRXAu4QjvsDYYkJN-WKS2bZeWNtZK-AoVndTncMQvag@mail.gmail.com> <CAMm+Lwi97VeE7j72oCXTeqEJWSQ=RTM3VH6hZ_GapbtZ9bmfwQ@mail.gmail.com> <CAL02cgTeztSb2B2pfweQfUL8Ty0XfiBLbtCLTrHwLNZ2LTQPVQ@mail.gmail.com> <CAMm+LwiR2tZVvWYOfKOMKybNNi9f52A_W4QGH6Bxx_haivFz3g@mail.gmail.com>
Date: Thu, 23 Apr 2015 11:40:15 -0400
Message-ID: <CAL02cgRTApJML9Pta8CtV3Z4UOeZx0tcDUp_EbW-Gq95MzTb=w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary=001a11c367ec9fabc8051466180b
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/GZzhgFRNKdmOMfcrSxZy6V3Y3MI>
Cc: Ted Hardie <ted.ietf@gmail.com>, "Salz, Rich" <rsalz@akamai.com>, "acme@ietf.org" <acme@ietf.org>, Bruce Gaya <gaya@apple.com>, Nico Williams <nico@cryptonector.com>, Martin Thomson <martin.thomson@gmail.com>
Subject: Re: [Acme] Want client-defined callback port
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: Thu, 23 Apr 2015 15:40:35 -0000

On Thu, Apr 23, 2015 at 11:28 AM, Phillip Hallam-Baker <
phill@hallambaker.com>; wrote:

> On Thu, Apr 23, 2015 at 10:16 AM, Richard Barnes <rlb@ipv.sx>; wrote:
>
> > We can design mechanisms here that we believe have a sufficient level of
> > security.  CABF and the individual CAs are free to opine on whether those
> > mechanisms are suitable for a given context.
> >
> > In other words, it is my earnest hope that the validation methods listed
> in
> > Section 11.1.1 of the BRs [1] will not be designed by the CABF, but
> selected
> > from a list that IETF defines.  CABF is not an engineering organization,
> > after all.
>
> I think we can decide on a mechanism. But getting into long arguments
> as to whether ports other then 443 should be accepted or if so which
> ones seems to be unnecessary.
>
> IETF should deliver
>
> * A mechanism with sufficient agility and flexibility
> * Security considerations explaining the consequences of a CA
> permitting various approaches
>

I think what we're arguing about here is what constitutes "sufficient
flexibility".  That is, if there's not a need to open up arbitrary ports,
then a scheme with a single reserved non-443 port might provide sufficient
flexibility.

--Richard



>
> Then let the decision of which ports are to be allowed and when to
> CABForum.
>
> This is exactly what happens with crypto algorithms. IETF has
> described dozens of algorithms and curves for ECC, CABForum has chosen
> RSA plus three of the NIST curves.
>
>
> What I am saying is let CABForum select the color to paint the bike
> shed but point out where the choice has consequences.
>