Re: [httpapi] RFC7807bis (HTTP Problems)
"Salz, Rich" <rsalz@akamai.com> Fri, 29 January 2021 17:10 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 024F33A118C for <httpapi@ietfa.amsl.com>; Fri, 29 Jan 2021 09:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level:
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 yFgld0mov52Q for <httpapi@ietfa.amsl.com>; Fri, 29 Jan 2021 09:10:12 -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 B625D3A118B for <httpapi@ietf.org>; Fri, 29 Jan 2021 09:10:12 -0800 (PST)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10TGxiso020242; Fri, 29 Jan 2021 17:10:11 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=LqPBk6AXOvlG7zQmDttvWN4hRr+aHBORtvGOrtGumQg=; b=flVbFbbSZ5uZ4bU8APuDn+W5pBcWMrFAoBh+zVLQkuiReSc72K64z8uh4yRBbvD4U25H zYPW5M+X+s/sRZvx0U+YL3c5GRebAZEQ+3XU5MBpIMPdTMPIQFcjdMxsM3LOx03YKcJK G/d6T7C3n7z0LFr+WMplJQwLgJVkIjOeenFuqkRl6pPn4lDEmcD6wqUCVVEABZLEqxAx SaEXM0La/2rfLva0/K+QFa7eWadu9DvYhClkwO6vD9yBSMtDBt3lZSuxeBqdISBHdNkV UYs1/58gQDgoYXcauXJfXjH7HGyw8ITLNeIDHi5y32bPWsgjsJOHIZl8PiCH/e/mz124 kg==
Received: from prod-mail-ppoint3 (a72-247-45-31.deploy.static.akamaitechnologies.com [72.247.45.31] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 369e7gtbsb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 29 Jan 2021 17:10:11 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 10TH3wmn023623; Fri, 29 Jan 2021 12:10:05 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.118]) by prod-mail-ppoint3.akamai.com with ESMTP id 36b7haw4tp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 29 Jan 2021 12:10:05 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb4.msg.corp.akamai.com (172.27.165.122) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 29 Jan 2021 11:10:05 -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; Fri, 29 Jan 2021 11:10:04 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: Mark Nottingham <mnot@mnot.net>, "httpapi@ietf.org" <httpapi@ietf.org>
Thread-Topic: [httpapi] RFC7807bis (HTTP Problems)
Thread-Index: AQHW9g1OYIFbXz3XjkO8Nlf/2rznhqo+59OA
Date: Fri, 29 Jan 2021 17:10:04 +0000
Message-ID: <6A7A29B5-9425-4633-B4B1-B2490770E64E@akamai.com>
References: <E0E4D7EF-FF48-4B12-9A20-7C90B6B7FCC9@mnot.net>
In-Reply-To: <E0E4D7EF-FF48-4B12-9A20-7C90B6B7FCC9@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21011103
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <ED98F698B18EE04CA94A99E7FBB837C6@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-01-29_06:2021-01-29, 2021-01-29 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 bulkscore=0 mlxscore=0 adultscore=0 phishscore=0 spamscore=0 malwarescore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101290083
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-01-29_06:2021-01-29, 2021-01-29 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 clxscore=1015 lowpriorityscore=0 spamscore=0 suspectscore=0 impostorscore=0 mlxlogscore=999 bulkscore=0 mlxscore=0 adultscore=0 phishscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101290083
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.31) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint3
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/wPmUdNFFGJrOFKcysVkco0yX9JI>
Subject: Re: [httpapi] RFC7807bis (HTTP Problems)
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: Fri, 29 Jan 2021 17:10:14 -0000
Just to be clear: the confusion about "call for adoption" versus a call not necessary was one I created. Please discuss on the list if substantive, open github issues and PR's as appropriate. On 1/29/21, 2:06 AM, "Mark Nottingham" <mnot@mnot.net> wrote: Hi everyone, Rich says that a Call for Adoption is not necessary in this case, after discussion with the AD, so he asked us to go ahead and create a repository: https://github.com/ietf-wg-httpapi/rfc7807bis We'll submit the -00 version shortly; it doesn't contain any significant changes from 7807, so that we can verify the diff before we start work. I've already created a few issues; please start discussion there / add new issues as you see fit. Cheers, -- Mark Nottingham https://urldefense.com/v3/__https://www.mnot.net/__;!!GjvTz_vk!A--7ePuftCHkE2qws3PyQQYdtNuRGyreRa5uOQ-OP83M_ZJnRh2DkGx7hO_a$ -- httpapi mailing list httpapi@ietf.org https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/httpapi__;!!GjvTz_vk!A--7ePuftCHkE2qws3PyQQYdtNuRGyreRa5uOQ-OP83M_ZJnRh2DkO__X6H8$
- [httpapi] RFC7807bis (HTTP Problems) Mark Nottingham
- Re: [httpapi] RFC7807bis (HTTP Problems) Salz, Rich