Re: [Acme] WGLC for ACME Integrations

"Salz, Rich" <rsalz@akamai.com> Mon, 03 May 2021 18:29 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 7B9493A1F92 for <acme@ietfa.amsl.com>; Mon, 3 May 2021 11:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 EOLvzeXm_SNt for <acme@ietfa.amsl.com>; Mon, 3 May 2021 11:29:20 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 48E833A1F96 for <acme@ietf.org>; Mon, 3 May 2021 11:29:20 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 143IKHgf000626; Mon, 3 May 2021 19:29:18 +0100
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 : mime-version; s=jan2016.eng; bh=4pbvUmjGoML/3Zhaf4wwdSBU46x+rETUMGQ6AVPeFMU=; b=Am+qRSQKwOeWXWuv+I455wbyF6VIg6UR+UCSzfv361MFlumpXqztqntOKoYWpNHjsXjj JZVvUqdcNN/zx675hgxxFm7mQwqHA9ZVJdp5rjmG8lvxGD0so6FudzeW+xdn4zviYXP2 SUX4I8//WKjqefGCHbkMC/2KdeCFiKcprk+PbuGcM/geSyyNmkCKNAM5w4vSUVTOIRrM DB6/XUrNhz3NCYLL5B9w7H9TycCj5oO78WDAjgAi55wWMEF4PwfOa5pi+UQVwPDUDcrz z2H0qFYLcIciyIIAIqZRxhxNCEJ6kgmFqxryvnw1ha5ysny1ucV0743LDYD0Lzt74fqe Ww==
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 389x553pmw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 03 May 2021 19:29:18 +0100
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 143I6wUC022992; Mon, 3 May 2021 14:29:11 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint6.akamai.com with ESMTP id 3892ayrjxm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 03 May 2021 14:29:11 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 3 May 2021 14:29:11 -0400
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.1497.012; Mon, 3 May 2021 14:29:11 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Yoav Nir <ynir.ietf@gmail.com>, IETF ACME <acme@ietf.org>
Thread-Topic: [Acme] WGLC for ACME Integrations
Thread-Index: AQHXPgP98vbsushgIUmaCez38DTkyqrSGGGA
Date: Mon, 03 May 2021 18:29:10 +0000
Message-ID: <4D5528ED-06F3-4081-823C-1F4BA41A2EC9@akamai.com>
References: <50B79A61-40D1-4F15-A5C9-668DD4CF0284@gmail.com> <A3A70B61-1216-482B-9191-6CB7A1FBCFC2@gmail.com>
In-Reply-To: <A3A70B61-1216-482B-9191-6CB7A1FBCFC2@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.48.21041102
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_4D5528ED06F34081823C1F4BA41A2EC9akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-05-03_16:2021-05-03, 2021-05-03 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 mlxlogscore=672 bulkscore=0 suspectscore=0 mlxscore=0 adultscore=0 malwarescore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2105030120
X-Proofpoint-GUID: 8n9HTvFxgRIFBmeQ8B3RDF5sTFXHzArP
X-Proofpoint-ORIG-GUID: 8n9HTvFxgRIFBmeQ8B3RDF5sTFXHzArP
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-05-03_16:2021-05-03, 2021-05-03 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 priorityscore=1501 impostorscore=0 malwarescore=0 adultscore=0 mlxscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxlogscore=604 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2105030122
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.61) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint6
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/ax-eLo18nkW4ra3PsSMhX-S1DfY>
Subject: Re: [Acme] WGLC for ACME Integrations
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: Mon, 03 May 2021 18:29:25 -0000

Speaking as an individual, I read the doc. It’s a good starting point.  I think the authors should go to the “other” working groups and get them to drum up support over in ACME for their doc.

I think ACME is going to have a problem handling not-widely-applicable things like this. I don’t have any suggestions on how to handle it.