Re: [httpapi] linkset draft ready for next steps

"Salz, Rich" <rsalz@akamai.com> Tue, 08 June 2021 14:17 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A53053A3221 for <httpapi@ietfa.amsl.com>; Tue, 8 Jun 2021 07:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.495
X-Spam-Level:
X-Spam-Status: No, score=-3.495 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=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 RS7s3Cj1Hgo7 for <httpapi@ietfa.amsl.com>; Tue, 8 Jun 2021 07:17:36 -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 45F0C3A321F for <httpapi@ietf.org>; Tue, 8 Jun 2021 07:17:36 -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 158EFabn014061; Tue, 8 Jun 2021 15:17:32 +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 : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=EH20jHj0J3aPCPpnuKe8LLf3LcpV3ES32ohGNnjgLVk=; b=QWiuQv3Wm+yvcuFgTe7oIe7qiMg3N2IH8Neg0X39tJX7GRTIwqnx4RRN2ARn/rKMDCIH P+8PLJuf9jOMt3Q7BxOxnNFmap/HjLeXD456XuBtd0AVKf4aR0BKtq2GE/Z4vQANXOiw tJN9ZqabCpfyoSgPuFEI54qRBQl56LQl43hlUvMgIgepI9h8rXnlNMwHXbe8nUTqNi80 Eqn16asW/adqocFrm4WaP9FaSB8cx4oG/4qN8HWGVTXynLzDUW0W+1olFfpOIQeLiboB iuGbtVpLuXWiyLud633B1ikaPXUVoOa5AfgY4wImXj5DPxHQKIkC0ItoPWxjbrjTBb0Y ww==
Received: from prod-mail-ppoint7 (a72-247-45-33.deploy.static.akamaitechnologies.com [72.247.45.33] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 391re13xvh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 08 Jun 2021 15:17:32 +0100
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 158E6gVk024552; Tue, 8 Jun 2021 10:17:31 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.115]) by prod-mail-ppoint7.akamai.com with ESMTP id 3904m01524-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 08 Jun 2021 10:17:31 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.165.123) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Tue, 8 Jun 2021 09:17:30 -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 mapi id 15.00.1497.018; Tue, 8 Jun 2021 09:17:30 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Julian Reschke <julian.reschke@gmx.de>, "httpapi@ietf.org" <httpapi@ietf.org>
Thread-Topic: [httpapi] linkset draft ready for next steps
Thread-Index: AQHXXDJjOvn6a8qECEGNawuAp/BNgasKDGaAgAAt/4A=
Date: Tue, 08 Jun 2021 14:17:30 +0000
Message-ID: <52BC49CD-015D-402D-B4D3-34FE87C7A03C@akamai.com>
References: <625dc350-44bd-2a72-5258-612ddbea8f37@dret.net> <6b4033a1-a68a-d540-e9be-b03270c8e946@gmx.de>
In-Reply-To: <6b4033a1-a68a-d540-e9be-b03270c8e946@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.49.21050901
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <649F1D48C35B14438E86A67E7797F130@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-06-08_09:2021-06-04, 2021-06-08 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 mlxlogscore=999 phishscore=0 suspectscore=0 bulkscore=0 malwarescore=0 spamscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104190000 definitions=main-2106080092
X-Proofpoint-GUID: syImWMWrGQwxwvpsdjJvexryqf5Y7j4l
X-Proofpoint-ORIG-GUID: syImWMWrGQwxwvpsdjJvexryqf5Y7j4l
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-06-08_09:2021-06-04, 2021-06-08 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 bulkscore=0 phishscore=0 mlxscore=0 lowpriorityscore=0 adultscore=0 suspectscore=0 priorityscore=1501 impostorscore=0 clxscore=1015 mlxlogscore=999 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104190000 definitions=main-2106080093
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/httpapi/IbwUunXO8eD3JKM5zxN3MvIObDI>
Subject: Re: [httpapi] linkset draft ready for next steps
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2021 14:17:42 -0000

Thanks, Julian!

So I think that this is the plan we should follow.  Julian will post his comments (ideally this week, perhaps next) and the authors will respond and perhaps post a new draft. If there's disagreement or controversy, we'll repeat that cycle until issues are settled.  Once that's done, we'll issue a working group last call (WGLC) and proceed.  The rest of this note describes the process for those not familiar with how the IETF works.

WGLC is a time, at least a week, for WG members to raise issues. If there's anything substantive, we restart the process.

We are in the "ART, Applications and Real Time" area and our AD is Francesca Palombini. She will read the document, perhaps provide another round of feedback, and then request that it is put on the IESG tele-chat. The IESG is all AD's, and they have technical review/oversight of all IETF RFC's. The telechat is every two weeks, and there will be at least that amount of time to give other AD's time to read the document. Many Areas have "directorates" which is volunteers familiar with the area who read and offer input to their AD. This will result in another round of feedback.

Often the issues are just editorial: "this wasn't clear to me." That happens often when someone reads a draft for the first time, compared to those who have been working with it for a while. If an IESG member puts a "DISCUSS" vote on the draft, then the issues they raise *must* be addressed by the authors and WG. Sometimes that results in a new WGLC if the changes are substantive. The WG chairs decide.

Once the IESG approves the document, it is given to the RFC Editor staff. They do final copy-editing, work with other registration authorities if needed, and consult with the authors.  Because of the backlog, going from IESG to publication can take months.

Hope this helps!
	/r$