Re: [ippm] WG adoption call for RFC8321bis and 8889bis

Tommy Pauly <tpauly@apple.com> Tue, 26 April 2022 20:13 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4117C1D24D4; Tue, 26 Apr 2022 13:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.67
X-Spam-Level:
X-Spam-Status: No, score=-7.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.575, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9T1v-ANcsAQx; Tue, 26 Apr 2022 13:13:00 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp14.apple.com (rn-mailsvcp-ppex-lapp14.rno.apple.com [17.179.253.33]) (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 79E9AC1D24CF; Tue, 26 Apr 2022 13:12:57 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp14.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp14.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 23QK43XM009313; Tue, 26 Apr 2022 13:12:56 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=rK2vOXi0N7+SN9aMYc8kazP+MZsYDTYclL4bmgbtvd8=; b=vkaaxYqmj6+Cmr9qnm763CnhjRpTEw8Fbj+/DrMIAbhh8NuO3WjaPEYIM/o6oaNpoDbH FZsrYCC0lC4AIALkRjKEiFJQGxzm3T6TTNw9aTjmlIFZsr7yy8gIazO9AoDkxCdIty1N biKJ/r3NW3RxbVVSRpHC5E7dAVXat/06H589TbAJ2QkBHQjq+pXqo/3ze//iEKNRpcfT H1YDUjqGsWlHT6cOgG/44NmQswub69EO+0ob56luuagE0VfZefveLxwkkmBDVQjDMy5c Quya7BQG26XyM5mgY/4hGNNTZEV18Uq3vGWEsMRzusQhKZnngTZ6TQIDqJjJ7VLjSaSO Jg==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by rn-mailsvcp-ppex-lapp14.rno.apple.com with ESMTP id 3fmebdt6bx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 26 Apr 2022 13:12:56 -0700
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) with ESMTPS id <0RAY00MJFQTKPN70@rn-mailsvcp-mta-lapp02.rno.apple.com>; Tue, 26 Apr 2022 13:12:56 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) id <0RAY00H00QSTLI00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 26 Apr 2022 13:12:56 -0700 (PDT)
X-Va-A:
X-Va-T-CD: def81ff6fed7e58b6d193c197db4a743
X-Va-E-CD: c14cdde55355a6328701ccd2c45ef560
X-Va-R-CD: eae0cbf5ae1fd5c0e2ac623ca2d8b46f
X-Va-CD: 0
X-Va-ID: 8def00a5-8c33-401f-906e-a1c771a37bd7
X-V-A:
X-V-T-CD: def81ff6fed7e58b6d193c197db4a743
X-V-E-CD: c14cdde55355a6328701ccd2c45ef560
X-V-R-CD: eae0cbf5ae1fd5c0e2ac623ca2d8b46f
X-V-CD: 0
X-V-ID: 5d89f80a-d395-490d-a1e6-f80e982ca725
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486, 18.0.858 definitions=2022-04-26_06:2022-04-26, 2022-04-26 signatures=0
Received: from smtpclient.apple (unknown [17.11.160.131]) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) with ESMTPSA id <0RAY0066TQTJKZ00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 26 Apr 2022 13:12:56 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <519D8E5D-2342-4226-B53A-A303D8FAE968@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_B36E1CFD-5BF1-46AD-AC1F-E9147F0F2D50"
MIME-version: 1.0 (Mac OS X Mail 15.0 \(3691.0.3\))
Date: Tue, 26 Apr 2022 13:12:55 -0700
In-reply-to: <9d89c35a42fa46d095cdd1e91b90248d@huawei.com>
Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
To: Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org>
References: <CAM4esxQHrH7onttT6MV+DGuM24cQW99pZ83wOAK_88BcAP43Rw@mail.gmail.com> <17AA8D9D-CDEC-4CF3-938A-4280CE08A51A@apple.com> <1A5D1777-01C2-43FD-A3D2-688BDD0CF5FB@apple.com> <9d89c35a42fa46d095cdd1e91b90248d@huawei.com>
X-Mailer: Apple Mail (2.3691.0.3)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486, 18.0.858 definitions=2022-04-26_06:2022-04-26, 2022-04-26 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/ldzP_cWDgbousO4ZKIjyE4gqMVo>
Subject: Re: [ippm] WG adoption call for RFC8321bis and 8889bis
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2022 20:13:04 -0000

Hi Giuseppe,

Sounds good, thanks! Once you’ve pushed the -01 versions, let me know and I’ll kick off the WGLC.

Best,
Tommy


> On Apr 26, 2022, at 9:53 AM, Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org> wrote:
> 
> Hi Tommy, All,
> Thank you for the update.
> I have just published draft-ietf-ippm-rfc8321bis-00 and draft-ietf-ippm-rfc8889bis-00.
> I plan to publish the -01 versions by this week to address the comments received during the adoption call.
>  
> Regards,
>  
> Giuseppe
>  
>  
> From: ippm <ippm-bounces@ietf.org> On Behalf Of Tommy Pauly
> Sent: Tuesday, April 26, 2022 6:03 PM
> To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>; IETF IPPM WG <ippm@ietf.org>
> Subject: Re: [ippm] WG adoption call for RFC8321bis and 8889bis
>  
> Hello all,
>  
> Thanks to everyone who provided feedback! Based on the input, we will formally adopt these documents. 
>  
> We are expecting a revision this week, and then we’ll kick off a working group last call.
>  
> Best,
> Tommy
> 
> 
> On Apr 7, 2022, at 5:03 PM, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org <mailto:tpauly=40apple.com@dmarc.ietf.org>> wrote:
>  
> Hello IPPM,
>  
> This email starts an adoption call for draft-fioccola-rfc8321bis and draft-fioccola-rfc8889bis. Please see Martin’s emails below for details — the main idea here is that we’re moving two IPPM RFCs from Experimental to Proposed Standard.
>  
> The chairs would like to have a short amount of time spent in the WG processing these documents. If we adopt, we’d plan to very shortly thereafter do a working group last call.
>  
> Please reply to this email by Thursday, April 21 and indicate if you support adopting this document.
>  
> Best,
> Tommy & Marcus
> 
> 
> On Apr 7, 2022, at 1:16 PM, Martin Duke <martin.h.duke@gmail.com <mailto:martin.h.duke@gmail.com>> wrote:
>  
> Hello IPPM,
>  
> You may recall that there was a need to progress RFC8321 and RFC8889 from Experimental to Proposed Standard. There was a feeling that the update would be trivial and we could therefore do it as an AD sponsored document.
>  
> I've done 3 rounds of AD review and I've seen the need to substantially adjust the scope of these documents and tweak the design in places. The changes are not revolutionary, but I'm a non-practitioner and have driven some design changes with minimal review. At this point I think it's important to get good IPPM review; if we're going to do that anyway, we might as well do the (expedited) working group process so that there's no confusion as to why IPPM didn't formally review an update to its own documents.
>  
> So, as first step, I invite the working group to adopt these two drafts:
> https://datatracker.ietf.org/doc/draft-fioccola-rfc8321bis/ <https://datatracker.ietf.org/doc/draft-fioccola-rfc8321bis/>
> https://datatracker.ietf.org/doc/draft-fioccola-rfc8889bis/ <https://datatracker.ietf.org/doc/draft-fioccola-rfc8889bis/>
> Any objections to adoption, as always, should be to the value of doing the work at all, and the general direction of the drafts. I hope to follow up the adoption call with an immediate WGLC to shake out any detailed objections, though we will take as long as we need to address concerns that people have.
>  
> I invite you to consult the changelogs on both of these documents, which are not long, to get a sense of what we've done.
>  
> For those of you who like diffs, there was a big reorganization between draft-02 and -03 that is hard to follow in a diff. So here is a set of diffs that exclude the -02 to -03 transition:
> https://www.ietf.org/rfcdiff?url1=rfc8321.txt&url2=draft-fioccola-rfc8321bis-02.txt <https://www.ietf.org/rfcdiff?url1=rfc8321.txt&url2=draft-fioccola-rfc8321bis-02.txt>
> https://www.ietf.org/rfcdiff?url1=draft-fioccola-rfc8321bis-03.txt&url2=draft-fioccola-rfc8321bis-04.txt <https://www.ietf.org/rfcdiff?url1=draft-fioccola-rfc8321bis-03.txt&url2=draft-fioccola-rfc8321bis-04.txt>
>  
> https://www.ietf.org/rfcdiff?url1=rfc8889.txt&url2=draft-fioccola-rfc8889bis-02.txt <https://www.ietf.org/rfcdiff?url1=rfc8889.txt&url2=draft-fioccola-rfc8889bis-02.txt>
> https://www.ietf.org/rfcdiff?url1=draft-fioccola-rfc8889bis-03.txt&url2=draft-fioccola-rfc8889bis-04.txt <https://www.ietf.org/rfcdiff?url1=draft-fioccola-rfc8889bis-03.txt&url2=draft-fioccola-rfc8889bis-04.txt>
>  
> I believe it's up to the chairs to start the adoption call. If people are good about reading the document during WGLC, I would like to think we could be done before IETF 114.
>  
> Your friendly Area Director,
> Martin
>  
> _______________________________________________
> ippm mailing list
> ippm@ietf.org <mailto:ippm@ietf.org>
> https://www.ietf.org/mailman/listinfo/ippm <https://www.ietf.org/mailman/listinfo/ippm>
>  
> _______________________________________________
> ippm mailing list
> ippm@ietf.org <mailto:ippm@ietf.org>
> https://www.ietf.org/mailman/listinfo/ippm <https://www.ietf.org/mailman/listinfo/ippm>
>  
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm