Re: [newtrk] Last Call comments on draft-ietf-newtrk-decruft-experiment-01.txt

Eliot Lear <lear@cisco.com> Thu, 17 November 2005 16:44 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ecmro-000129-DL for newtrk-archive@megatron.ietf.org; Thu, 17 Nov 2005 11:44:08 -0500
Received: from mailapps.uoregon.edu (mailapps.uoregon.edu [128.223.142.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05507 for <newtrk-archive@lists.ietf.org>; Thu, 17 Nov 2005 11:43:33 -0500 (EST)
Received: from mailapps.uoregon.edu (IDENT:U2FsdGVkX19RDesxl4XuHVnJnK21Xj6cf0KME2j07M0@localhost [127.0.0.1]) by mailapps.uoregon.edu (8.13.5/8.13.5) with ESMTP id jAHGXvOD001590; Thu, 17 Nov 2005 08:33:57 -0800
Received: (from majordom@localhost) by mailapps.uoregon.edu (8.13.5/8.13.5/Submit) id jAHGXvTN001589; Thu, 17 Nov 2005 08:33:57 -0800
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70]) by mailapps.uoregon.edu (8.13.5/8.13.5) with ESMTP id jAHGXuKF001581 for <newtrk@lists.uoregon.edu>; Thu, 17 Nov 2005 08:33:56 -0800
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 17 Nov 2005 08:33:51 -0800
X-IronPort-AV: i="3.97,343,1125903600"; d="scan'208"; a="676192456:sNHT28856044"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jAHGXnpM028776; Thu, 17 Nov 2005 08:33:49 -0800 (PST)
Received: from [212.254.247.3] (ams-clip-vpn-dhcp4222.cisco.com [10.61.80.125]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id jAHGgOsb015173; Thu, 17 Nov 2005 08:42:25 -0800
Message-ID: <437CB0EB.4000100@cisco.com>
Date: Thu, 17 Nov 2005 17:33:47 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051025)
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
CC: New Track <newtrk@lists.uoregon.edu>
Subject: Re: [newtrk] Last Call comments on draft-ietf-newtrk-decruft-experiment-01.txt
References: <436E1D8B.3050709@zurich.ibm.com>
In-Reply-To: <436E1D8B.3050709@zurich.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=5274; t=1132245746; x=1132677946; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:Re=3A=20[newtrk]=20Last=20Call=20comments=20on=20draft-ietf-newtrk-decru ft-experiment-01.txt| From:Eliot=20Lear=20<lear@cisco.com>| Date:Thu,=2017=20Nov=202005=2017=3A33=3A47=20+0100| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=kezZTcCgXO5jAbSlFsIJ9DmrJlwuQT98eddnlYmh8pnBD+/sQIwv2j8PiW1Wu0/c/jZfdPp1 UwZcb+4C2NGP49wJiZlXJnGln5ogMLAQ2aY0TZWMGCezcDSCZeLt/KEYb+4hyse1P37ba6MTeMi 8HQ9C/Itf+okrt4/sL8qIEsU=
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Virus-Scanned: ClamAV 0.87.1/1177/Thu Nov 17 00:35:37 2005 on mailapps
X-Virus-Status: Clean
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

Brian,

I have submitted draft-ietf-newtrk-decruft-experiment-02.txt for 
publication with the five RFCs removed, a comment added regarding them, 
and the text that Harald provided for IANA considerations.

Eliot

Brian E Carpenter wrote:
> AD hat on.
> 
> Since none of these were copied to the WG, here is
> a compilation of the Last Call comments, including responses
> to IANA's question.
> 
> I request the authors and WG to reach consensus on
> 
> 1. whether to remove the 5 RFCs mentioned by Orly from the list
> (note his second message at the end that only mentions two of them).
> 
> 2. how to respond to IANA
> 
> If some RFCs are removed, I would like to see a revised I-D,
> since it would be very confusing to have them removed during
> the editorial process.
> 
>    Brian
> 
> -------- Original Message --------
> Subject: Re: [newtrk] Last Call: 'Getting rid of the cruft: an 
> experiment to    identify obsolete standards document' to Informational RFC
> Date: Fri, 21 Oct 2005 14:35:25 -0500
> From: Spencer Dawkins <spencer@mcsr-labs.org>
> To: <iesg@ietf.org>
> References: <E1ET2Hy-0007gQ-1l@newodin.ietf.org>
> 
> I support this action, FWIW...
> 
> Spencer
> 
> -------- Original Message --------
> Subject: FW: FW: Last Call: 'Getting rid of the cruft: an experiment 
> to    identify obsolete standards document' to Informational RFC
> Date: Sun, 23 Oct 2005 23:26:27 +0200
> From: Orly Nicklass <orly_n@rad.com>
> To: <iesg@ietf.org>
> 
> 
> - 1381, 1382:
> - 1471, 1472, 1473:
> are still in active use by some of our products.
> 
> -------- Original Message --------
> Subject: RE: Last Call: 'Getting rid of the cruft: an experiment to 
> identify    obsolete standards document' to Informational RFC 
> [I06-051024-0011]
> Date: Mon, 24 Oct 2005 20:44:53 -0700
> From: iana-drafts@icann.org
> Reply-To: iana-drafts@icann.org
> To: iesg@ietf.org
> CC: harald@alvestrand.no, sob@harvard.edu, lear@cisco.com
> 
> 
> IESG:
> 
> The IANA has reviewed the following Internet-Draft which is in Last
> Call:  draft-ietf-newtrk-decruft-experiment-01.txt,  and has the following
> with regards to the publication of this document:
> 
> Upon approval of this document the IANA will review all the IANA 
> registries and update the references to be this document for the all 
> documents described in section 3.  Should all the actual assignments 
> also be marked as OBSOLETE or should the reference only be changed?
> 
> Thank you.
> 
> Michelle Cotton
> (on behalf of IANA)
> 
> -------- Original Message --------
> Subject: Re: Last Call: 'Getting rid of the cruft: an experiment to 
> identify obsolete standards document' to Informational RFC 
> [I06-051024-0011]
> Date: Tue, 25 Oct 2005 08:27:50 +0200
> From: Eliot Lear <lear@cisco.com>
> To: Brian E Carpenter <brc@zurich.ibm.com>
> CC: iana-drafts@icann.org, harald@alvestrand.no, sob@harvard.edu
> References: <200510250344.j9P3ir4i027366@g13.icann.org> 
> <435DC75C.1050700@zurich.ibm.com>
> 
> Michelle,
> 
> My recommendation would be to simply add the notation "Historic" to the
> reference.  Or if you like,  Historic, see RFCs (original, cruft).  Just
> because these documents are marked HISTORIC doesn't mean someone out
> there isn't using them.  We don't make that claim and there's no need to
> cause those people grief.
> 
> There is potentially a separate effort that should be undertaken to
> attempt to clean up some of the IANA databases.  For example, I'm pretty
> sure that HEMS implementations never got out of labs.  And SGMP is listed.
> 
> What do you think?
> 
> Eliot
> 
> 
> -------- Original Message --------
> Subject: RE: Last Call: 'Getting rid of the cruft: an experiment to 
> identify    obsolete standards document' to Informational RFC 
> [I06-051024-0011]
> Date: Tue, 25 Oct 2005 05:38:09 -0400 (EDT)
> From: sob@harvard.edu (Scott Bradner)
> To: iana-drafts@icann.org
> CC: harald@alvestrand.no, iesg@ietf.org, lear@cisco.com
> 
> 
> I hnk that the references should be changed and that is all that
> should happen - I do not think teh status of the assignments should
> change
> 
> Scott
> 
> 
> -------- Original Message --------
> Subject: RE: Last Call: 'Getting rid of the cruft: an experiment to 
> identify obsolete standards document' to Informational RFC 
> [I06-051024-0011]
> Date: Tue, 25 Oct 2005 05:44:05 -0700
> From: Harald Tveit Alvestrand <harald@alvestrand.no>
> To: iana-drafts@icann.org, iesg@ietf.org
> CC: sob@harvard.edu, lear@cisco.com
> References: <200510250344.j9P3ir4i027366@g13.icann.org>
> 
> My immediate thought would be that IANA should not change the references in
> the registries at all - the correct interpretation of the values in the
> registries is still the defining RFC, not the one that declares them
> Historical.
> 
> I believe the port number registry, for instance, has many references to
> documents that are not standards-track RFCs already.
> 
> If you want to add annotations saying "Historical" to such references,
> that's reasonable, but then you should also add "Informational",
> "Experimental" or "Standards-track" to the other references in the
> registries - and as far as I know, there's no such marking now.
> 
> Don't make work you don't have to.....
> 
>                               Harald
> 
> 
> 
> -------- Original Message --------
> Subject: RE: Last Call: 'Getting rid of the cruft: an experiment to 
> identify    obsolete standards document' to Informational RFC 
> [I06-051024-0011]
> Date: Tue, 25 Oct 2005 17:12:29 -0400 (EDT)
> From: sob@harvard.edu (Scott Bradner)
> To: harald@alvestrand.no, iana-drafts@icann.org, iesg@ietf.org
> CC: sob@harvard.edu, lear@cisco.com
> 
>  > the registries at all - the correct interpretation of the values in 
> the=20
>  > registries is still the defining RFC, not the one that declares them=20
>  > Historical.
> 
> good point
> 
> Scott
> 
> 
> 
> -------- Original Message --------
> Subject: FW: [newtrk] I-D 
> ACTION:draft-ietf-newtrk-decruft-experiment-00.txt
> Date: Sun, 30 Oct 2005 18:43:46 +0200
> From: Orly Nicklass <orly_n@rad.com>
> To: <iesg@ietf.org>
> 
> - RFC1471 - RFC1473 - are used by our products
> 
> (end of Last Call comments)
> 
> 
> 
> 
> 
> 
> 
> .
> newtrk resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html
> 
.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html