Re: [httpapi] resolving issues
"Salz, Rich" <rsalz@akamai.com> Fri, 16 April 2021 16:58 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 CEABA3A2C8C for <httpapi@ietfa.amsl.com>; Fri, 16 Apr 2021 09:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 f1_cvjCsIGqA for <httpapi@ietfa.amsl.com>; Fri, 16 Apr 2021 09:58:26 -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 50BC53A2C87 for <httpapi@ietf.org>; Fri, 16 Apr 2021 09:58:26 -0700 (PDT)
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 13GGrPHO013661; Fri, 16 Apr 2021 17:57:40 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=6dnZgO9ob8pGpgadBbJ3WMNAmVJ8BYerZtBcRvXvTac=; b=mqhVdInUbzuIQHqjFB9qCh408/3yZTczCHzkKAFYrW74aT0EyMA+2NZOI97fiIr3VCMw yAefcnTOMBKIM7xSJ8taO9S0oKUM26MVGv0/KgnqJut5NAeELtSaT3FAte4NKULe0lei O30nALTZvkfkKsC0Qbf/hVAJUkHxYDv6z/WTDKOOD9US47dSa+8gxBum5DZrS0xvY5Xd WOHR9dpr2gEQoPnCgxKgzJchgi2l4dYx9kJ2Nho2g8OaupzFjVXkYgAeP8NsHUHNkP08 fc1SuAueR9tgwDSylm6jOj/lxeMLh7lQDDf8vd0SEyxhVKnhkEaz/17jyCN6kRIePrIA vw==
Received: from prod-mail-ppoint8 (a72-247-45-34.deploy.static.akamaitechnologies.com [72.247.45.34] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 37y0dh82tt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 16 Apr 2021 17:57:40 +0100
Received: from pps.filterd (prod-mail-ppoint8.akamai.com [127.0.0.1]) by prod-mail-ppoint8.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 13GGoX53003484; Fri, 16 Apr 2021 12:57:39 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.114]) by prod-mail-ppoint8.akamai.com with ESMTP id 37wvb3rpfa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 16 Apr 2021 12:57:39 -0400
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, 16 Apr 2021 11:57:38 -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; Fri, 16 Apr 2021 11:57:38 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Sanjay Dalal <sanjay.dalal@cal.berkeley.edu>, "mnot@mnot.net" <mnot@mnot.net>, Erik Wilde <erik.wilde@dret.net>, "Darrel.Miller@microsoft.com" <Darrel.Miller@microsoft.com>
CC: "httpapi@ietf.org" <httpapi@ietf.org>
Thread-Topic: resolving issues
Thread-Index: AQHXMs0orFSstZd8bEiYQqwq1SIKxKq3bl6A
Date: Fri, 16 Apr 2021 16:57:37 +0000
Message-ID: <F8B8E93D-335E-4676-8251-686EF1DB4D1F@akamai.com>
References: <CAC5fHGOBPgqWbkSaT=7ohq4+fbQ4XaMA-3=XDnCsK9yz5Z3NxA@mail.gmail.com>
In-Reply-To: <CAC5fHGOBPgqWbkSaT=7ohq4+fbQ4XaMA-3=XDnCsK9yz5Z3NxA@mail.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_F8B8E93D335E46768251686EF1DB4D1Fakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-04-16_08:2021-04-16, 2021-04-16 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 phishscore=0 bulkscore=0 malwarescore=0 spamscore=0 mlxlogscore=999 adultscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104160120
X-Proofpoint-ORIG-GUID: bV1mZRXMbCjAS7RfMfPye5M-J7DYGMnP
X-Proofpoint-GUID: bV1mZRXMbCjAS7RfMfPye5M-J7DYGMnP
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-04-16_08:2021-04-16, 2021-04-16 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 mlxlogscore=999 adultscore=0 lowpriorityscore=0 clxscore=1011 phishscore=0 malwarescore=0 suspectscore=0 impostorscore=0 mlxscore=0 spamscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104160121
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.34) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint8
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/zwWgeJS8XNVEpR3OOn0ft_C_eNs>
Subject: Re: [httpapi] resolving issues
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, 16 Apr 2021 16:58:31 -0000
* What is the process to bring an issue to its resolution? There are many issues opened and discussed on the Deprecation header and rfc7807bis. How do we bring them to conclusion so we have clarity in preparing a new draft? Please advise and also inform the maillist. If the authors have a thoughts on how to address an issue (or issues), make a PR. If it’s just an editorial change (wordsmithing, move paragraphs, etc), feel free to merge once the co-authors agree. If it is a substantive change make a PR, and post a description to the mailing list encouraging feedback. If it’s a “big honkin change” then tell the chairs in the same message that you thinkg the WG should get consensus before being merged. WG chairs generally have flexibility to “do the right thing,” so if these processes don’t make sense, let us know. Hope this helps.
- Re: [httpapi] resolving issues Salz, Rich
- Re: [httpapi] resolving issues Herbert Van de Sompel