IETF Logo Mail Archive

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

Fernando Gont <fgont@si6networks.com> Tue, 21 June 2022 05:20 UTC

Return-Path: <fgont@si6networks.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 1A6DBC15D86D; Mon, 20 Jun 2022 22:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.773
X-Spam-Level:
X-Spam-Status: No, score=-3.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 V3M0C39tUMLX; Mon, 20 Jun 2022 22:20:44 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 54892C15D867; Mon, 20 Jun 2022 22:20:41 -0700 (PDT)
Received: from [IPV6:2001:67c:27e4:c::1000] (unknown [IPv6:2001:67c:27e4:c::1000]) (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 fgont.go6lab.si (Postfix) with ESMTPSA id 5B6E6282EB2; Tue, 21 Jun 2022 05:20:32 +0000 (UTC)
Message-ID: <20388fca-4d55-8905-405a-3578f1ff92e5@si6networks.com>
Date: Tue, 21 Jun 2022 02:20:28 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-US
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.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
References: <165538883599.60682.16650863205769317634@ietfa.amsl.com> <6a1fc831-d355-4b6a-fb4c-9e8b58c3f51a@si6networks.com> <CAKKJt-cstbQvGo6At2SfRoqXjzQFWXFxqEvi1KBqwBrYv3xh1Q@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
In-Reply-To: <CAKKJt-cstbQvGo6At2SfRoqXjzQFWXFxqEvi1KBqwBrYv3xh1Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/26mc17dHitEnAewMf8izXF6Twug>
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: Tue, 21 Jun 2022 05:20:45 -0000

Hi, Spencer,

Thanks a lot for your comments! In-line....

On 20/6/22 12:56, Spencer Dawkins at IETF wrote:
> 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 
> <mailto: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.

There might be a few references (not many, tough) for which this would 
be doable... So I'll do this before/when submitting the next rev of this 
I-D.

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