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

Ran Atkinson <ran.atkinson@gmail.com> Fri, 09 February 2024 19:52 UTC

Return-Path: <ran.atkinson@gmail.com>
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 12D8EC14F736; Fri, 9 Feb 2024 11:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 nuUYERJx2jNq; Fri, 9 Feb 2024 11:52:08 -0800 (PST)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (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 C4A05C14F5EE; Fri, 9 Feb 2024 11:52:08 -0800 (PST)
Received: by mail-vk1-xa2f.google.com with SMTP id 71dfb90a1353d-4c01ac04569so456511e0c.1; Fri, 09 Feb 2024 11:52:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707508327; x=1708113127; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=MW0yhsLc8fWVSuxQ1xsAZrRZW9LaOIEfUAxCnYPZIII=; b=ZTezIx085WDDnIHLZqN5Mxhdo9fV+D370Q/KsGCnHXq4MheOMnP4789qJoKK5nxIyP 5x0c3zDoaWm0kIbpZusihndSH3CvgcnwmeeWEFHkEJMyqPL2KqINd+LLsmN1xYDJ9PWg aU3+bQIk1BAsBx7EESWXjhrNdkNzCLiwDbrVRpHX9wFuta5qEWqTE3o9jQL5+zNrmHto R571MrKHdZ7bkUWq34XpDGNh5EmhGAVvS+NLklZawm//vOPPaCB6kYnj43GwfY5b2W10 OTxU9TVxoEZHOowmBjxnkhpCTo70Erwm06Js8pHAkyt3XfA5OJ9g1tGDr+wtBlZz5HS9 otRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707508327; x=1708113127; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=MW0yhsLc8fWVSuxQ1xsAZrRZW9LaOIEfUAxCnYPZIII=; b=ojvWegwYNWCFGD72J3zQiAP79gQmHqephF3FEaseFfXvXZsvCC/eXlXseQwyY/TSzj Q1WmcVXy10h9LLYybb1lpXENaZy7QSmla3Mnxqvi++siVuJX50vi+m1eFHpJL1OMYbuX duiu/smF3f7pEPkzUpJ3f5iDOh//wxLMHik7mWqPeH05DRBiGgM+U6DHcFm/Xp6ALiOm z5Aqj65TsLKk0Nos1OzK7FVjrRpylW4dPKlXoo+MUqV4lMgAMcKa0UxjYwIMID3TnAMY WtRWsOycd3lYAp3QuyKNJNfeWhhRsjH2kF+GmuIRBHCPXIECYl8ZkF0zRrgioPsizCAl rhjQ==
X-Forwarded-Encrypted: i=1; AJvYcCWrxivZSCGOLawZG8Cad7/xfytOnjjxHTAKJyS3xmiDyy0Tp5PvrYxPXqLCy2fM8eJ9CnBySqBSU99q/NDX4IDIpVP0uHjeunIaN6mpdYJMRNocnCOriVMR56fUScuD0g+xucaeMxQ81Q9WkPchiAUBI3kP7zGHTMgnk+jDOknG6z5WYJu2TERuHv8=
X-Gm-Message-State: AOJu0YzNUZ1ATQ9PgsSGrXIwfXiGirMhsBHvIYhBuN+SQRIa9owQa6++ IktXbG+kQYrchi45vn/4UhJxD3XFNweEPiJ+Hf2UwNyzKhxoH+E=
X-Google-Smtp-Source: AGHT+IF9X4JduCQug3Rl+duTw+ht0Gw/n/CHCAZ2WcRuotonH+aqcDLDISePQfunVoZsvxJCYA4d2Q==
X-Received: by 2002:a1f:e742:0:b0:4c0:2a9f:d3ec with SMTP id e63-20020a1fe742000000b004c02a9fd3ecmr418507vkh.6.1707508327548; Fri, 09 Feb 2024 11:52:07 -0800 (PST)
X-Forwarded-Encrypted: i=1; AJvYcCVWxoPYBJ+jK2IOHJAwxsM7JV7mrdiyyKiXlRfdhmIslb09UO5anKQQfxc3zur61JU3mNXI7a4tptS2l6vKfM63uamw2A8nLFUCZ82jUuNWaYOCqTjHQ67yBh6bIbULCjDAECmTTwr2OwwL4aWBHfv0zDi2GtM74CG6jVDoD7+58nT1xYciLMLGM/EZIISlQkPAf8R9RX6idr9sqmEif7T6dQWwlf3qNwjxJbcq5Z1L1UhokPFsMrOFAOPUhozi6wvlulqM6v3AlrFmsFU=
Received: from smtpclient.apple (pool-108-28-83-193.washdc.fios.verizon.net. [108.28.83.193]) by smtp.gmail.com with ESMTPSA id mc3-20020a056214554300b0068cc3a7a59dsm1097952qvb.106.2024.02.09.11.52.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Feb 2024 11:52:07 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Ran Atkinson <ran.atkinson@gmail.com>
In-Reply-To: <029e29c0-f40d-4eda-8830-a62dae68957f@tropicalstormsoftware.com>
Date: Fri, 09 Feb 2024 14:51:56 -0500
Cc: Ran Atkinson <ran.atkinson@gmail.com>, "scott@solarnetone.org" <scott@solarnetone.org>, Russ Housley <housley@vigilsec.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dtn-ipn-update.all@ietf.org" <draft-ietf-dtn-ipn-update.all@ietf.org>, "dtn@ietf.org" <dtn@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, irtf-chair@irtf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/ts91C0LdTnhY0pxDhCkPSl_4xeQ>
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 19:52:11 -0000


> 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.

Yours,

Ran