IETF Logo Mail Archive

Re: [Acme] Hyphens in parameter names of ACME CAA extensions

"Salz, Rich" <rsalz@akamai.com> Fri, 19 January 2018 15:18 UTC

Return-Path: <rsalz@akamai.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 4E98F12D961 for <acme@ietfa.amsl.com>; Fri, 19 Jan 2018 07:18:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 knmlLwG488Nq for <acme@ietfa.amsl.com>; Fri, 19 Jan 2018 07:18:00 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 C463712D958 for <acme@ietf.org>; Fri, 19 Jan 2018 07:18:00 -0800 (PST)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0JFH4jW011458; Fri, 19 Jan 2018 15:17:56 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=KvISlwGpcwe5EOWAJ29kNnt2iO4sI7s9g3gGaYUA87M=; b=Kipy+ZFV2dfqOIxQRfdtoXZrTO44GttBfGFCn0HD2HmwI2yPx3CZcOFlH+EsdfCogjoE Dkr/s1q6yRD+OoBqo0KGTgBkil/Qk8gQI4SmqjTkZSi/1lW4k6lz74qd8vxrywWNQp2q 4ynYx8ZVcFcLTZrAAKaF7c6nq3unOFso/A6dTm8PwE8JnY7/Q7WlD9a/nC76PgkxtO6U lsJHM0x6mD+BnVEASKHVit70nlNGm5YUP4Pa0dshW9hIwI65ja60NdJ76IcxQ/Rj3yTu umdwj1UWD/zQOjC460ltYZIwzaAODcnrP7GkcSdD49IkGfiVnFpfd7FiLJvyuxkRs74g PQ==
Received: from prod-mail-ppoint3 ([96.6.114.86]) by mx0b-00190b01.pphosted.com with ESMTP id 2fhtcc6eu0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 19 Jan 2018 15:17:56 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w0JFGnEw011052; Fri, 19 Jan 2018 10:17:55 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint3.akamai.com with ESMTP id 2ffebfgyw1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 19 Jan 2018 10:17:55 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 19 Jan 2018 10:17:54 -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.1263.000; Fri, 19 Jan 2018 10:17:54 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Tim Hollebeek <tim.hollebeek@digicert.com>, Corey Bonnell <CBonnell@trustwave.com>, Jacob Hoffman-Andrews <jsha@eff.org>, Ivan Vyshnevskyi <ivan@vyshnevskyi.com>, "acme@ietf.org" <acme@ietf.org>
Thread-Topic: [Acme] Hyphens in parameter names of ACME CAA extensions
Thread-Index: AQHTkHe88rQKeSZLmka6X8EFco+gDaN6sOAAgADSGQCAACAbgIAAASiA
Date: Fri, 19 Jan 2018 15:17:53 +0000
Message-ID: <A13E4CE7-1840-4BDB-935C-9A37CE7A2246@akamai.com>
References: <1516287365.2992847.1239759288.6198D1F4@webmail.messagingengine.com> <38b34229-2137-1bed-b96e-37b91babddbb@eff.org> <E41721D9-9BF5-4877-A69C-A43F370A1773@trustwave.com> <DM5PR14MB12891525E84FB7EDABAF729A83EF0@DM5PR14MB1289.namprd14.prod.outlook.com>
In-Reply-To: <DM5PR14MB12891525E84FB7EDABAF729A83EF0@DM5PR14MB1289.namprd14.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.45.179]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1870E4CA742B8E4CA486E02DD3739106@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-19_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=632 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801190198
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-19_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=561 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801190199
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/SjziMzuNz5MelCKtQtRIU817J2w>
Subject: Re: [Acme] Hyphens in parameter names of ACME CAA extensions
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 19 Jan 2018 15:18:02 -0000

➢ The implementation of CAA by major CAs has revealed a large number of
    serious defects with the current text of RFC 6844, and I think it's time for a 
    RFC 6844-bis effort.
    

This is happening, in the LAMPS working group.  Phil Hallam-Baker has stepped up.

v2.23.0 | Report a Bug | By Email