IETF Logo Mail Archive

Re: [Pearg] [irsg] Brian Trammell's Yes on draft-irtf-pearg-numeric-ids-history-09: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 20 June 2022 15:57 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: pearg@ietfa.amsl.com
Delivered-To: pearg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D85E0C15AAEC; Mon, 20 Jun 2022 08:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N49qTb3Ol_Vt; Mon, 20 Jun 2022 08:57:16 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 777CAC15AAE7; Mon, 20 Jun 2022 08:57:16 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id f1so11138597vsv.5; Mon, 20 Jun 2022 08:57:16 -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=BnLvXzTzeE/p0HBSrC+c7cSaey2gCslM9BuywSpsOMU=; b=QUkLZ2gOKibxp6ZdN5yoK7jiy1z8/livsAhsmXuT/6evbzU1EMf0wV77/CmlJWjfg4 11fSwUN4vSSiyd1Apo3IDeAZ3OtjIQPrw6HPeNU2HZMjSTWBUFkqdNsQwZKJVVIL8sN7 jQgjZGo3sCmS41g+IcwJrbQHtdrxyVO9U+o7MbGqeu2bBdT0wKU58Jfr6oy+U116wS9u 1zFkB3DGJrZOMtfV9M86AdqtPelICY16HAHLi8Lv6vHfbMwMYjKAHGWoSU+AcsXRS3nc 4Gm7yvn2upp+8zENotMDxx9DmacEKLjePxAao/R/V07EELEPxCSD5Ygb5m/Hb0wIyst7 c5uQ==
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=BnLvXzTzeE/p0HBSrC+c7cSaey2gCslM9BuywSpsOMU=; b=JmU262rVHb2Gm6JL+o233KfjYiQ48jVqw88VP+kyDCRS8UvmmDT/+Nvax1DZfQJh6s hZzXOoZLePOqDt2gsfNzYmXnENUv8wP1R8jsOmbI91kle3Y9QFq82IW5JcONpKTtzkFh Al/VZuZLtblf1lx3ORsWtrkzmujfo9qAz6IQHcro9Ekc1kYGXdMwb8zbQc83JBxJ+EDD bLVub8t5IoJgdOqWGzi/hs4eVOK+mbRlJcsy/wGTZG+nzzmIflEv37FCOHCN/AuTkixP M2fUPDobXRMhr5aYBvyJ3w25Z9kFTg1M4bKgkGQqjK2447qLKTczq5ervxqhkraA/cFX hAaA==
X-Gm-Message-State: AJIora+UVeot8Rwm8k04eU/Y4Q0r6AEFmWgjd75HmgaKipzljtxR2ke8 gv1XZkyLb/0sGG7ZWPTayakYtdtbhHGsq4DQA6g=
X-Google-Smtp-Source: AGRyM1vq1fmW/WBwT0jZLbawILJr5j6E/1l4WqBz3t/pZnh16yEry5qg4iyxGI0De1dZNeF79fB7f8ftVpBDCJwEky0=
X-Received: by 2002:a05:6102:5709:b0:34b:bc54:cf66 with SMTP id dg9-20020a056102570900b0034bbc54cf66mr9377934vsb.85.1655740635605; Mon, 20 Jun 2022 08:57:15 -0700 (PDT)
MIME-Version: 1.0
References: <165538883599.60682.16650863205769317634@ietfa.amsl.com> <6a1fc831-d355-4b6a-fb4c-9e8b58c3f51a@si6networks.com>
In-Reply-To: <6a1fc831-d355-4b6a-fb4c-9e8b58c3f51a@si6networks.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 20 Jun 2022 10:56:49 -0500
Message-ID: <CAKKJt-cstbQvGo6At2SfRoqXjzQFWXFxqEvi1KBqwBrYv3xh1Q@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: Brian Trammell <trammell@google.com>, The IRSG <irsg@irtf.org>, pearg@irtf.org, draft-irtf-pearg-numeric-ids-history@ietf.org, pearg-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006cf09105e1e32880"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/8dMlr3ZXCR2jRvrJMWqWLbJSeEc>
Subject: Re: [Pearg] [irsg] Brian Trammell's Yes on draft-irtf-pearg-numeric-ids-history-09: (with COMMENT)
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <pearg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/pearg>, <mailto:pearg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pearg/>
List-Post: <mailto:pearg@irtf.org>
List-Help: <mailto:pearg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pearg>, <mailto:pearg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2022 15:57:16 -0000

I'm not Brian, or anyone with an infallible opinion, but ...

On Thu, Jun 16, 2022 at 4:09 PM Fernando Gont <fgont@si6networks.com> wrote:

>
> Although I'm not sure what's the policy here -- e.g., it's clear that
> when a draft-author is adopted by a wg and becomes draft-ietf, the
> draft-ietf document "replaces" the draft-author one. However, in cases
> where a draft-ietf document is kind of based in a draft-author, but not
> fully, I'm not sure if one should mark such draft-author as replaced
> with the "draft-ietf" one. (i.e., this is me asking for input).
>

For these situations, you could reasonably drop a note to the relevant WG
chairs, and ask them to adjust the metadata if they agree that the working
group version replaces the individual version, whether the working group
version is clearly based on the individual version, or "kind of based" on
the individual version.

That's worth doing (and we should probably do it more, IMO), but it can
definitely happen while the document is at the RFC Editor, with any changes
to your references being provided at AUTH48 time.

I hope this is helpful.

Best,

Spencer


> Thanks!
>
> Regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>

v2.23.0 | Report a Bug | By Email