IETF Logo Mail Archive

Re: [dtn] Genart last call review of draft-ietf-dtn-ipn-update-09

Colin Perkins <csp@csperkins.org> Fri, 09 February 2024 20:03 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0DAFC14F61D; Fri, 9 Feb 2024 12:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=csperkins.org
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 i3kfswR5qZ94; Fri, 9 Feb 2024 12:03:52 -0800 (PST)
Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 487D1C14F6BA; Fri, 9 Feb 2024 12:02:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=Date:Subject:To:From; bh=xYu0KuOOw1QTHuCj8JjOnGYHTWzOurk+RWiPSu10y7o=; b=zUzcPmItt8DScf0BUFY5EN6dUE N88Oabema1Rxx/cjsvwDQy2LwuKUc38dq6D3okrSUnS0GBVpjQWvfuTIDLxXu0lvrcnysx9CInMhB lXeizpT38F7VZIIitz/9tX2o9Wr/0ezKU6UH6fqfbK+Tfza8DzKsf6VTlp3/2pnqiTISYBjSwzAdF 57LXnTtRP6HuNbg3klITX1ZUWfOuV9losHmeqTTvXT5JTjoeICwe53nTp8pb6hpzPtt8C4aF9dEEM SnTOjFWJTca/YwrjSYzZa639lmo7YvfCyFVhMZYWeIbLMT5WCLfC5WTmagDbrAs8530akNc4iNPTv ik6HkLkA==;
Received: by mailhub-hex-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <csp@csperkins.org>) id 1rYX4W-00DHvr-0s; Fri, 09 Feb 2024 20:02:04 +0000
From: Colin Perkins <csp@csperkins.org>
To: Ran Atkinson <ran.atkinson@gmail.com>
Cc: Rick Taylor <rick@tropicalstormsoftware.com>, scott@solarnetone.org, Russ Housley <housley@vigilsec.com>, gen-art@ietf.org, draft-ietf-dtn-ipn-update.all@ietf.org, dtn@ietf.org, last-call@ietf.org, irtf-chair@irtf.org
Date: Fri, 09 Feb 2024 20:01:44 +0000
X-Mailer: MailMate (1.14r6022)
Message-ID: <D3FD9406-6658-4DC7-AFED-6F4011D6CB91@csperkins.org>
In-Reply-To: <1F5C9ABC-5F54-4874-B603-42B98821F216@gmail.com>
References: <170682590663.11138.2099663199307035145@ietfa.amsl.com> <d427e715-7bf7-4e5b-9b7e-e24a8fa9261c@tropicalstormsoftware.com> <d8b8b2b3-8fa9-bda6-52b9-76a0df1e6f6b@solarnetone.org> <029e29c0-f40d-4eda-8830-a62dae68957f@tropicalstormsoftware.com> <1F5C9ABC-5F54-4874-B603-42B98821F216@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; markup="markdown"
Content-Transfer-Encoding: quoted-printable
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/CDMw93nJ3d0F8g7-eP2Sp9f7Xw8>
Subject: Re: [dtn] Genart last call review of draft-ietf-dtn-ipn-update-09
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Feb 2024 20:03:57 -0000

Hi,

On 9 Feb 2024, at 19:51, Ran Atkinson wrote:

>> On Feb 7, 2024, at 06:46, Rick Taylor <rick@tropicalstormsoftware.com> wrote:
>>
>> The main point of discussion here is about IETF process: obsoleting IRTF
>> documents by the IETF is considered unusual. Finding a simple way around
>> this, such as not obsoleting 7116 is an approach we could consider, it's
>> just a matter of determining a valid reason why the ipn update doesn't
>> obsolete 7116.
>
> Rick,
>
> I apologize if this sounds unreasonable, but I really think you are making this process much too complex.
>
> First, maybe you open a conversation with the IRTF Chair and describe the situation as you see it.
> Then ask if the IRTF Chair or IRSG would agree to move that IRTF document to Historic status ?
>
> It is possible that someone (might be them or might be you) would need to create a short "IRTF Track" document which explains the background and then changes the status of the applicable documents to “Historic” or whatever is deemed sensible by the IRTF Chair.

We wrote https://www.irtf.org/policies/cross-stream-updates.html the last time a similar issue came up. Does it address your concern? (The "other stream manager" would be the IETF Chair, if this is an IETF document)

Colin

v2.23.0 | Report a Bug | By Email