IETF Logo Mail Archive

Re: [httpapi] [dispatch] HTTP profile negotiation -- implementation evidence (was: HTTP profile negotiation - httpapi?)

"Salz, Rich" <rsalz@akamai.com> Sun, 21 March 2021 15:56 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 DE9C53A0E4D; Sun, 21 Mar 2021 08:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.449
X-Spam-Level:
X-Spam-Status: No, score=-0.449 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.251, 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=unavailable 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 m51znJJDLvnS; Sun, 21 Mar 2021 08:56:39 -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 ECB343A0E4B; Sun, 21 Mar 2021 08:56:38 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 12LFtlMp025452; Sun, 21 Mar 2021 15:56:34 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=BKMuCvszWmctbYo5LZ0Fjyw/9LBRT91Z/twtoDhncto=; b=Z/0RsLjdV6i5uPoHbm6y/ugPLqoT3UNVP6M55zVszs+u0jqUCdbQslBCkKiwSYE5Cmgd ZJBbrey5ofXh5GKCIlN95lIrm2EWd0ZDpBgFMStV9h8lAuYdNf+EvKwkBHAfTAiyYeKI qUnhZRkGmatUgTyjg6MdJuzrIEgKM1MecQOM5IPBYSUgs5b0UUqr4krhWr92jkJI8vZ8 6ZPNyFMqEiSZrYRrkWvy3Q71fwlZZCxXu0XJPzW6IHmsWPQ+V7dGM2l0dz7Wj2MxEO7P Wpj2YwJwxirSx3827SwCZyR9ExYVTdEJwpk5TQ5ritWBtINgWR2/nNRTYk53XBJEh9K9 iw==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 37d9fcfce4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 21 Mar 2021 15:56:34 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 12LFo6ZM022795; Sun, 21 Mar 2021 11:56:33 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.113]) by prod-mail-ppoint1.akamai.com with ESMTP id 37dccyjmnc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 21 Mar 2021 11:56:33 -0400
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; Sun, 21 Mar 2021 10:56:31 -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.012; Sun, 21 Mar 2021 10:56:31 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Darrel Miller <Darrel.Miller=40microsoft.com@dmarc.ietf.org>, "lars.svensson@web.de" <lars.svensson@web.de>, "Kirsty.p@ncsc.gov.uk" <Kirsty.p@ncsc.gov.uk>, "dispatch@ietf.org" <dispatch@ietf.org>
CC: "Ruben Verborgh (UGent-imec)" <ruben.verborgh@ugent.be>, "httpapi@ietf.org" <httpapi@ietf.org>, "hvdsomp@gmail.com" <hvdsomp@gmail.com>
Thread-Topic: [httpapi] [dispatch] HTTP profile negotiation -- implementation evidence (was: HTTP profile negotiation - httpapi?)
Thread-Index: AQHXHmrCbWd3z/W3wEmakZ6gYtsigg==
Date: Sun, 21 Mar 2021 15:56:31 +0000
Message-ID: <2F6F286F-C53A-4145-862B-964C10768E83@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.47.21031401
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_2F6F286FC53A4145862B964C10768E83akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-21_02:2021-03-19, 2021-03-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 phishscore=0 spamscore=0 mlxlogscore=989 adultscore=0 suspectscore=0 mlxscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2103210125
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-21_02:2021-03-19, 2021-03-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 mlxlogscore=908 phishscore=0 spamscore=0 lowpriorityscore=0 suspectscore=0 impostorscore=0 malwarescore=0 clxscore=1011 adultscore=0 priorityscore=1501 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2103210126
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.18) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint1
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/1OUzbFITjwXufIzJe6SKSXjdLfI>
Subject: Re: [httpapi] [dispatch] HTTP profile negotiation -- implementation evidence (was: HTTP profile negotiation - httpapi?)
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: Sun, 21 Mar 2021 15:56:43 -0000

  *   I have zero technical objections to the principles presented in the RFC, in fact I support them.  But I strongly believe that history has demonstrated that they will not get mainstream adoption and hence I am reluctant to support the httpapi working group spending time on the standardization effort.

I strongly agree.

We’d like to see commitments from implementors to support this.

v2.23.0 | Report a Bug | By Email