[Acme] Remove new-authz fields "existing" and "accept". #275
Jacob Hoffman-Andrews <jsha@eff.org> Sun, 12 March 2017 19:11 UTC
Return-Path: <jsha@eff.org>
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 9E9AF12949D for <acme@ietfa.amsl.com>; Sun, 12 Mar 2017 12:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.004
X-Spam-Level:
X-Spam-Status: No, score=-7.004 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eff.org
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 VYXlQLcdRAld for <acme@ietfa.amsl.com>; Sun, 12 Mar 2017 12:11:50 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1D25129484 for <acme@ietf.org>; Sun, 12 Mar 2017 12:11:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:Subject:From:To; bh=nJQko/qtH9TH/0njyVO7t63wRVPjTCt1eWo+qjYaxLM=; b=QDpT7Iz0N2WNUI7NrVRWRzgmgOR/07iKn0mx2rDuDo5PEBF3rIXT7mO9zgkdpgdQmUFusy5IskhhWtWbsJZGib/WG4cloU2Sf++EOmSlW1TdLjQnRADfFtjP55x4eI96uJcY2n/8ekPk9Ukk4SJ4sglzebmHkDwtpvA6Zu506fA=;
Received: ; Sun, 12 Mar 2017 12:11:52 -0700
To: "acme@ietf.org" <acme@ietf.org>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <7f7ec33f-0c84-d1df-c5b3-1016445f2f37@eff.org>
Date: Sun, 12 Mar 2017 12:11:50 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Received-SPF: skipped for local relay
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/D_LY5Xgg19Nc3pTajNJbkhFLC-c>
Subject: [Acme] Remove new-authz fields "existing" and "accept". #275
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 12 Mar 2017 19:11:51 -0000
https://github.com/ietf-wg-acme/acme/pull/275 Remove new-authz fields "existing" and "accept". #275 I believe they are unnecessary. The server can set its own policy on whether to give back an existing or a new authz, and the client can choose to accept or reject that. Hugo also pointed out on-list that the status codes for these are inconsistent with the status codes for new-account. If we keep these, we'd want to fix that. But simpler to delete, I think.
- [Acme] Remove new-authz fields "existing" and "ac… Jacob Hoffman-Andrews