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

Gyan Mishra <hayabusagsm@gmail.com> Sat, 16 April 2022 13:45 UTC

Return-Path: <hayabusagsm@gmail.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 0AD5F3A0DAE for <ippm@ietfa.amsl.com>; Sat, 16 Apr 2022 06:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vtzGCpkLYn8K for <ippm@ietfa.amsl.com>; Sat, 16 Apr 2022 06:45:19 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FA6F3A0D9B for <ippm@ietf.org>; Sat, 16 Apr 2022 06:45:19 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id k62so4881610pgd.2 for <ippm@ietf.org>; Sat, 16 Apr 2022 06:45:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dKy88tVJR72i4uZs0g0iaDn9ZUYR8Wm3/BXE7SKHRZ8=; b=BEOPKRncgYRP21+PJGhqM1dBB2dI/KX02HgqMoUHhQf4n71jKzhnSF/IFgzmVpmkf8 JgDnuGgmFuigwyUc54ExNFmuQKIKoUZu0QLDfLrkMjWLh3ESm8eUjPbG/Uy+uI60MJOp 7x9/Kp9KTcN65x/S+PYV0hdJL3L/PoY2PoOw5RO+cqXvl/Avj6YlJ7E/9EoJNaOq7Qio HATojCyZ9YV98rxzz/2jfNMPsbohwwN1Ikv6uWf37k+Q6GCAeNJEmC6S8ey15kmjOO2P OTesG22PcxPAkrDJnyZJUlb8Mcp//tErwjBYDFQqr08wtc06tbR3HQZtf8jZqOvK4CmH 7xOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dKy88tVJR72i4uZs0g0iaDn9ZUYR8Wm3/BXE7SKHRZ8=; b=D8Icsc0aSLv3RjMk6sqKaKptYUIGORNdHgFO09cGaSyP25ZQAf6cOJueP8PbSH7V4c ZrRCGooj2CqubNTyfb6yBjDKrPFbD4Z/TFatxdQbV/scPlZhImPBRvJ5PHBrIVGKXHcF 4JjL6g3Mhs8DN4XLQ0DYa9ijNnwrXnjaAMJbScumrs3Q9jEaWXCHepo1mAE62DcxvzOU BDDTt6E4xDup7b27+NWZdFXr+m6fhHzl4UtOHRlm32KO1YpfhqN7poT7FnipofX1EeU9 BmBf5KEsaqr/0jseTU0VyfiVHgXLYEHmQJ7axFGbVMnFGzIDaHvMcLqOBARK6PWBnQbS VnCQ==
X-Gm-Message-State: AOAM530oiAhHnUdmt93Xhhtd8uG5HFfJRelEL38MRyQH+B/sthFFafMQ fqieFMH/3xWbdkUayr4uS1Rsz1pwdfklwxFg940Pd1IU
X-Google-Smtp-Source: ABdhPJyurfnSr4uYeOiEtZ3/kNg5xn71e75M7PDZnLPJ40Aw2Jk1XGcA2tQM+y2/VNtvDuegQlRYcAoSTC1SJVpS6Js=
X-Received: by 2002:a63:7446:0:b0:398:36ed:daf1 with SMTP id e6-20020a637446000000b0039836eddaf1mr2949920pgn.415.1650116717677; Sat, 16 Apr 2022 06:45:17 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxQHrH7onttT6MV+DGuM24cQW99pZ83wOAK_88BcAP43Rw@mail.gmail.com> <17AA8D9D-CDEC-4CF3-938A-4280CE08A51A@apple.com>
In-Reply-To: <17AA8D9D-CDEC-4CF3-938A-4280CE08A51A@apple.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 16 Apr 2022 09:45:06 -0400
Message-ID: <CABNhwV1d-99eojSC2YN2G4NnNFyvq3f1+3BSM0h3gt7pd8EAcw@mail.gmail.com>
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Cc: IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cb91d205dcc5bc36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/IH48rzHcFXTdX2pvGbzYnRw7TB4>
Subject: Re: [ippm] WG adoption call for RFC8321bis and 8889bis
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 16 Apr 2022 13:45:24 -0000

Dear IPPM WG

I have read the two drafts and support WG adoption.

Regards

Gyan

On Thu, Apr 7, 2022 at 8:03 PM Tommy Pauly <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> 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-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=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=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
> https://www.ietf.org/mailman/listinfo/ippm
>
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*