[Acme] Status updates, working toward an agenda

"Salz, Rich" <rsalz@akamai.com> Thu, 25 February 2021 16:36 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 78A8B3A1C16 for <acme@ietfa.amsl.com>; Thu, 25 Feb 2021 08:36:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.668
X-Spam-Level:
X-Spam-Status: No, score=-2.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.57, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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 4h8Ec7BqsSno for <acme@ietfa.amsl.com>; Thu, 25 Feb 2021 08:36:56 -0800 (PST)
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 0BA163A207F for <acme@ietf.org>; Thu, 25 Feb 2021 08:35:44 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 11PGAVjC011883 for <acme@ietf.org>; Thu, 25 Feb 2021 16:35:44 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=uds+Y8PmbvJ7X3PO3W9gX02SgQH4y9Nt7GMeyPTRb4o=; b=d57lEbcb6JJLiIm/wDjexuyUubcK3Asys5XeX5paJYU/sZ4WEMXvk00DEdUafvMg+j8v TZHyoIoJYoCLbiOS1tIU+NFLstn3CrvDSY43W7Y76REDTnUMRBa+U6htHzQ9QDcdz/pS vbzcyXjIPCVWDHPxxEjrcUV/gdICQXyO2fvmofFv5uS4ZqdcHSh6W6pA7MdkYFdczaEW 7vfjVMD1gftWHl9AZhGHgTUIho7M5gJH9BQ/DpVg3TsFymCF2YCuE0eDdAs6t6JTaFyj hkwnQLQTEV5480Kowv5B1Br2Le0tFfVF8hopEF88EmNBlDKkrj85B3psArlXaRfCAh6p RA==
Received: from prod-mail-ppoint7 (a72-247-45-33.deploy.static.akamaitechnologies.com [72.247.45.33] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 36va1g4tcq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <acme@ietf.org>; Thu, 25 Feb 2021 16:35:44 +0000
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 11PGZA8D009551 for <acme@ietf.org>; Thu, 25 Feb 2021 11:35:43 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.117]) by prod-mail-ppoint7.akamai.com with ESMTP id 36txn4pxxe-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <acme@ietf.org>; Thu, 25 Feb 2021 11:35:43 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb1.msg.corp.akamai.com (172.27.165.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 25 Feb 2021 10:35:42 -0600
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.010; Thu, 25 Feb 2021 10:35:42 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: "acme@ietf.org" <acme@ietf.org>
Thread-Topic: Status updates, working toward an agenda
Thread-Index: AQHXC5RCeblLicqi0EGD3Ya3eaSt2Q==
Date: Thu, 25 Feb 2021 16:35:42 +0000
Message-ID: <F1C19763-7B8E-437B-88D7-7D05F2C5FDDE@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.46.21021202
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_F1C197637B8E437B88D77D05F2C5FDDEakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-02-25_10:2021-02-24, 2021-02-25 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 mlxlogscore=966 adultscore=0 spamscore=0 mlxscore=0 bulkscore=0 suspectscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2102250128
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-02-25_09:2021-02-24, 2021-02-25 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 mlxlogscore=883 mlxscore=0 phishscore=0 adultscore=0 clxscore=1015 impostorscore=0 lowpriorityscore=0 suspectscore=0 spamscore=0 malwarescore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2102250127
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.33) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint7
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/JE_SjO-FkyFQFDh2sJNUseSVQTE>
Subject: [Acme] Status updates, working toward an agenda
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: Thu, 25 Feb 2021 16:36:59 -0000

I think the WG should start to think about its future.  Below are some updates and questions.  Let’s discuss onlist and at the meeting in March.

If you look at our status page, https://datatracker.ietf.org/wg/acme/documents/, most of the adopted documents are well along.  To summarize:

    draft-ietf-acme-uthority-token waiting for IESG review
    draft-ietf-acme-Authority-token-tnauthlist update just submitted, waiting for AD review
    draft-ietf-acme-dtnnodeid Dependent drafts now in RFC pipeline, update coming
    draft-ietf-acme-email-smime in RFC pipeline
    draft-ietf-acme-star-delegation new draft coming to address AD feedback
    draft-ietf-acme-integrations some discussion, https://mailarchive.ietf.org/arch/browse/acme/?q=integrations
    draft-ietf-acme-client No update or discussions recently.

What should we do about the last two documents?

We have a couple of documents that the WG has not adopted. There hasn’t been much discussion of any of them since the last IETF virtual meeting.

    draft-biggs-acme-sso
    draft-friel-acme-subdomians
    draft-tweedale-acme-discovery
    draft-tweedale-acme-server-capabilities
(The last two are inter-related).

What should we do about these?

Do we want to say “we’re done, we’re successful, please move all new challenges to an appropriate group?”