Re: [Acme] Support for domains with redundant but not immediately synchronized servers

"Salz, Rich" <rsalz@akamai.com> Thu, 21 January 2016 14:13 UTC

Return-Path: <rsalz@akamai.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 E17A21A8838 for <acme@ietfa.amsl.com>; Thu, 21 Jan 2016 06:13:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 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_LOW=-0.7, RP_MATCHES_RCVD=-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 dlnz81A2IGP2 for <acme@ietfa.amsl.com>; Thu, 21 Jan 2016 06:13:35 -0800 (PST)
Received: from prod-mail-xrelay05.akamai.com (prod-mail-xrelay05.akamai.com [23.79.238.179]) by ietfa.amsl.com (Postfix) with ESMTP id 4224A1A8831 for <acme@ietf.org>; Thu, 21 Jan 2016 06:13:35 -0800 (PST)
Received: from prod-mail-xrelay05.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 0B07C423783; Thu, 21 Jan 2016 14:13:34 +0000 (GMT)
Received: from prod-mail-relay10.akamai.com (prod-mail-relay10.akamai.com [172.27.118.251]) by prod-mail-xrelay05.akamai.com (Postfix) with ESMTP id E86D142377C; Thu, 21 Jan 2016 14:13:33 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1453385613; bh=vYZNLIFk0UMhaBmZbW7A4J2QuG6VA56XdBw0aup2FQY=; l=501; h=From:To:Date:References:In-Reply-To:From; b=CD5p7j6a50zVZDMJbEeVH5AOkLQglty68SheeIEmgadJLda5VPLEb/ewTcSqgl8lf +jHLcNjsttn6mT9fuM63rwzjpVY548JS6t+Dyax+Cthu+15A4DIhIyjLh9s311vhAw cNckE4EqiUsXHxZ0ssx4UtrFIx9gx+0dBD+XNWD4=
Received: from email.msg.corp.akamai.com (ecp.msg.corp.akamai.com [172.27.123.34]) by prod-mail-relay10.akamai.com (Postfix) with ESMTP id E5BBB2029; Thu, 21 Jan 2016 14:13:33 +0000 (GMT)
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Thu, 21 Jan 2016 09:13:33 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1076.000; Thu, 21 Jan 2016 09:13:33 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Jonas Wielicki <jonas@wielicki.name>, "acme@ietf.org" <acme@ietf.org>
Thread-Topic: [Acme] Support for domains with redundant but not immediately synchronized servers
Thread-Index: AQHRVEGTaJgtiZRTw0K3dtOVX6aP7p8GAvOw
Date: Thu, 21 Jan 2016 14:13:32 +0000
Message-ID: <046f30469e8d4cdfafb01b7e7f9d4608@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <565C84A1.9040102@wielicki.name> <20151204084601.GQ18430@eff.org> <255B9BB34FB7D647A506DC292726F6E13BB473EFFB@WSMSG3153V.srv.dir.telstra.com> <56A0C558.2070202@wielicki.name>
In-Reply-To: <56A0C558.2070202@wielicki.name>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.42.69]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/79nWyiEW-4tLnvOVfaUFOunDIE8>
Subject: Re: [Acme] Support for domains with redundant but not immediately synchronized servers
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: Thu, 21 Jan 2016 14:13:37 -0000

> I am not at all familiar with the processes in an IETF WG. What is the way
> forward to get my proposal either into the protocol or officially dismissed?

This is the way it works. :)  People post to the mailing list and there's discussion.  At some point, the chairs will see if there is consensus to do it.

So things are working as designed.  It's informal and a bit messy.

What might help focus discussion is if you made a pull request with your specific wording changes.