Re: [Acme] Content-Type and file extensions for HTTP01 challenges

Martin Thomson <martin.thomson@gmail.com> Wed, 18 November 2015 20:01 UTC

Return-Path: <martin.thomson@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 E57031ACC87 for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 12:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 dB6Shl1m7a4g for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 12:01:27 -0800 (PST)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 8DBEF1ACE02 for <acme@ietf.org>; Wed, 18 Nov 2015 12:00:59 -0800 (PST)
Received: by igbxm8 with SMTP id xm8so47179089igb.1 for <acme@ietf.org>; Wed, 18 Nov 2015 12:00:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TqcFYzJ5GGk6Hp6fDXyKrBVHMoSKn2jmw3kwDPzDh+g=; b=g8FSzFn3A65KExjsX3eFewWTIBHzP1PIoF8UGkcfTsZYuBmlbpib/DckSodQc7AdSR 3UcaAuJlw2S7mDYwTdzGb+XNBhKZFaMO73+w253bSITSr+N8WVlHl7w9qzQoe+wWyz+y 6IjJMhhe6QQC3RNAKktauLZZowYNoUD5H/+FdjbMx8WFKrUaHhKLLp2DK5I9JeqHLnoV 4d/679KnJ9ra2y4/pG4vu+pvAtxyy0Y1fJP5mHx0AcE/esSFZ10E5s5xOOEXZncHFfjf SY86Ltw1rJJ+dAggUDrE+77ysRvPt3Cz+jgCioEajcE/DS1gNqGAypD4EKD04evbIzsO ocuQ==
MIME-Version: 1.0
X-Received: by 10.50.30.6 with SMTP id o6mr10093401igh.94.1447876858661; Wed, 18 Nov 2015 12:00:58 -0800 (PST)
Received: by 10.36.155.139 with HTTP; Wed, 18 Nov 2015 12:00:58 -0800 (PST)
In-Reply-To: <CANUQDCizmx=22WwwyVCs55mYYWQ02mYyiGaiC19GG39F9JkViQ@mail.gmail.com>
References: <20151113004436.GB18430@eff.org> <CABkgnnU5EzaPA4o7OgnTBpSQCZxjD+QsSV=4_L2rOBeFAoauKA@mail.gmail.com> <20151113011259.GC18430@eff.org> <1F85B447-6C45-4E5A-BB10-F1AD5CB2C3F3@vigilsec.com> <CABsBmKM9t3dX0_zq-EwsTOo7HpeMF6meiw9PhBaQLbHOCpGVGg@mail.gmail.com> <CAHw9_iJwqqhMb+7+aj6Sszfi6_K9=rREEK3dbpQ6yddrmHSKsg@mail.gmail.com> <CANUQDCgDeaLtaNfeEUQ3D=7EOwjL-Q0i6Q1FKxMTVtfY9d-bow@mail.gmail.com> <20151118180011.GW18430@eff.org> <CA+9kkMARw2Y86fjFyxoJJU6GJGYmorhJZqCGdns7-CV142v_qA@mail.gmail.com> <CANUQDCizmx=22WwwyVCs55mYYWQ02mYyiGaiC19GG39F9JkViQ@mail.gmail.com>
Date: Wed, 18 Nov 2015 12:00:58 -0800
Message-ID: <CABkgnnV8=0TVyBU4ugM-R1-izHTx2ugNmOq+MbthQ=qw-r36Hw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Niklas Keller <me@kelunik.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/W0Sv5z25lF_NgBKEcnQl2Cl1Tz8>
Cc: Ted Hardie <ted.ietf@gmail.com>, Peter Eckersley <pde@eff.org>, IETF ACME <acme@ietf.org>, Russ Housley <housley@vigilsec.com>, Bryan Livingston <bryanlivingston@gmail.com>, Warren Kumari <warren@kumari.net>
Subject: Re: [Acme] Content-Type and file extensions for HTTP01 challenges
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 18 Nov 2015 20:01:31 -0000

On 18 November 2015 at 11:03, Niklas Keller <me@kelunik.com> wrote:
> How would the transition work? Which URI does the server query then? Both?
> Or would the client just send the extension in the challenge answer?


Presumably, this would be a -02 or -03 version of the protocol and the
challenge would be identified as "http-02".