[Acme] vestige of certificate GET

Felipe Gasper <felipe@felipegasper.com> Tue, 06 November 2018 12:15 UTC

Return-Path: <felipe@felipegasper.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C7E12958B for <acme@ietfa.amsl.com>; Tue, 6 Nov 2018 04:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.701
X-Spam-Level:
X-Spam-Status: No, score=-1.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=felipegasper.com
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 CwqkXCapkEJ8 for <acme@ietfa.amsl.com>; Tue, 6 Nov 2018 04:15:23 -0800 (PST)
Received: from web1.siteocity.com (web1.siteocity.com [67.227.147.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56A8412D4F1 for <acme@ietf.org>; Tue, 6 Nov 2018 04:15:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=felipegasper.com; s=default; h=To:Date:Message-Id:Subject:Mime-Version: Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=w557YqAZpVL4hcqxeKWllq5d+tXB0xbNEnayndsL2Rc=; b=P1yVBu2+f5ESnx8gsBqe4KW/FQ szSDB8/X3OjjnC9ZAV8IRLZmc8A/4GpCDfHvWL1mtJ0aTqSdm1t2pkSk3w7M/BkB4aY2zVWMFaLCo 4KDxjUkJyyZE05ENQITePTe5ecH5sMTVYYL8B3zacASsVRt1fdChCiMFL2V4sgstAxoVEE9/P50uL OF8GGqJQvjSqaTyzIjwVPi4FHIt5ULjyodnoOtyDzOXdI9dLqcgj2XuFAD+Z8mK+cOxJr0Z9U5cG1 rivMm08pCulIHzTW6mwGelhs4HApTKfRJFcda1nglZvUcVe2A5VDG/WYMYff/XPrs9EW2v2DFEPPB p6r5z5+w==;
Received: from cpe9050cab50823-cm9050cab50820.cpe.net.cable.rogers.com ([99.248.56.67]:54073 helo=[192.168.0.13]) by web1.siteocity.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <felipe@felipegasper.com>) id 1gK0GD-0003gl-Na for acme@ietf.org; Tue, 06 Nov 2018 06:15:10 -0600
From: Felipe Gasper <felipe@felipegasper.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Message-Id: <EFAED084-BC2C-432F-AA4A-2A316A9EEC45@felipegasper.com>
Date: Tue, 06 Nov 2018 07:15:12 -0500
To: IETF ACME <acme@ietf.org>
X-Mailer: Apple Mail (2.3445.101.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - web1.siteocity.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - felipegasper.com
X-Get-Message-Sender-Via: web1.siteocity.com: authenticated_id: fgasper/from_h
X-Authenticated-Sender: web1.siteocity.com: felipe@felipegasper.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/-Tin2by6SFBe8RRTxTB_eOlfKHk>
Subject: [Acme] vestige of certificate GET
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 06 Nov 2018 12:15:25 -0000

Hi all,

	Draft 16 has this:

-----
   An ACME client MAY attempt to fetch the certificate with a GET
   request.  If the server does not allow GET requests for certificate
   resources, then it will return an error as described in 
Section 6.3
.
   On receiving such an error, the client SHOULD fall back to a POST-as-
   GET request.
-----

	From what I can discern from this list’s most recent posts on the topic, I’m under the impression that plain GET for certificates is not to be part of the principal ACME spec; should the above, then, be removed?

-FG