Re: [Idr] RFC911 to Historic

Susan Hares <shares@ndzh.com> Sat, 26 March 2022 13:39 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942EA3A0D71; Sat, 26 Mar 2022 06:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.061
X-Spam-Level:
X-Spam-Status: No, score=-4.061 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XRjhrh2eRmRr; Sat, 26 Mar 2022 06:39:50 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 17C343A0D72; Sat, 26 Mar 2022 06:39:49 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.107.114.225;
From: Susan Hares <shares@ndzh.com>
To: 'Greg Skinner' <gregskinner0@icloud.com>
Cc: 'Alvaro Retana' <aretana.ietf@gmail.com>, idr@ietf.org, rtg-ads@ietf.org
References: <CAMMESszn=+u+fyY6703P72HOuu21s5LW3VeZsCOpKHbHoFH0sw@mail.gmail.com> <01d301d81210$a3be15f0$eb3a41d0$@ndzh.com> <1591B4EB-A9ED-4A51-A3BA-F177ECA79840@icloud.com>
In-Reply-To: <1591B4EB-A9ED-4A51-A3BA-F177ECA79840@icloud.com>
Date: Sat, 26 Mar 2022 09:39:43 -0400
Message-ID: <06cc01d84116$f3a1c1e0$dae545a0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06CD_01D840F5.6C9244C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGcVlRA0oeNo1YcgXWfGSIn4lY3IQI/yMpvAku2V5qtJSJw8A==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/WLlIGLI0O3WQNeMcD5gW7MIFqZE>
Subject: Re: [Idr] RFC911 to Historic
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2022 13:39:55 -0000

Greg: 

 

I serve as both an IDR chair and a member of the Independent Streams Editor board.    As part of the ISE editor board, this question is resurfacing to me.   So in that role, can you tell me a little bit about why you requested RFC911 being placed in historic status?  RFC904 is the protocol specification.  RFC911 is an implementation report on RFC904.    

 

What is the need driving this request?   

 

Sue 

 

 

 

From: Greg Skinner [mailto:gregskinner0@icloud.com] 
Sent: Saturday, January 29, 2022 1:19 AM
To: Susan Hares
Cc: Alvaro Retana; idr@ietf.org; rtg-ads@ietf.org
Subject: Re: [Idr] RFC911 to Historic

 

How would all of you feel about bundling this request along with other related requests and/or actions to change the status of RFCs, as was discussed at IETF 30 <https://www.ietf.org/ietf-ftp/ietf-online-proceedings/94jul/area.and.wg.reports/rtg/idr/idr-minutes-94jul.txt> ?  Could this also be done in conjunction with an IDR working group milestone such as progressing RFC4271 as an Internet Standard?  Based on what has been discussed on the Last Call for this request so far, bundling status changes in conjunction with significant working group tasks seems to be more acceptable.

 

Greg





On Jan 25, 2022, at 9:26 AM, Susan Hares <shares@ndzh.com> wrote:

 

Alvaro: 

This is a detail that IDR should have  taken care of years ago. 

Sue 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Alvaro Retana
Sent: Wednesday, January 12, 2022 10:30 AM
To: idr@ietf.org
Cc: rtg-ads@ietf.org; Greg Skinner
Subject: [Idr] RFC911 to Historic

Dear idr WG:


Greg Skinner (cc'd) approached us with the suggestion to reclassify
rfc911 as Historic.  Here's the justification:

=====
  RFC 911 [RFC911] describes an implementation of the Exterior Gateway
  Protocol (EGP) [RFC904] for 4.2 BSD Unix.  It also provides examples of
  its use at the time of its publication.  RFC 904 is currently classified
  as Historic. Experience gained with EGP led to the development of the
  Border Gateway Protocol (BGP) [RFC1105], and eventually to the current
  BGP version 4 [RFC4271].  Also, the example network topologies given in
  RFC 911 include IPv4 networks such as “ARPANET 10”, which is now part of
  private address space [RFC1918], and “UCI-ICS”, which has been reassigned
  to the Ford Motor Company.
=====


The process to reclassify requires an IETF Last Call and balloting by the IESG.

idr is not explicitly chartered with anything related to EGP, but I
figured it is the closest we have. :-)

Does anyone have comments about this action?  I plan to start the IETF
Last Call on Jan/20 -- you can comment then too.

Thanks!

Alvaro.

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr