[newtrk] Last Call comments on draft-ietf-newtrk-decruft-experiment-01.txt
Brian E Carpenter <brc@zurich.ibm.com> Sun, 06 November 2005 15:52 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYmpH-0007vl-KC for newtrk-archive@megatron.ietf.org; Sun, 06 Nov 2005 10:52:59 -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 KAA03632 for <newtrk-archive@lists.ietf.org>; Sun, 6 Nov 2005 10:52:34 -0500 (EST)
Received: from mailapps.uoregon.edu (IDENT:U2FsdGVkX19JvCLIEHD18GHEAKxthvlciCbnNatGFsQ@localhost [127.0.0.1]) by mailapps.uoregon.edu (8.13.4/8.13.4) with ESMTP id jA6FoiB1029133; Sun, 6 Nov 2005 07:50:44 -0800
Received: (from majordom@localhost) by mailapps.uoregon.edu (8.13.4/8.13.4/Submit) id jA6FoiEp029132; Sun, 6 Nov 2005 07:50:44 -0800
Received: from mtagate4.uk.ibm.com (mtagate4.uk.ibm.com [195.212.29.137]) by mailapps.uoregon.edu (8.13.4/8.13.4) with ESMTP id jA6FogMJ029106 for <newtrk@lists.uoregon.edu>; Sun, 6 Nov 2005 07:50:43 -0800
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id jA6Foa34204676 for <newtrk@lists.uoregon.edu>; Sun, 6 Nov 2005 15:50:36 GMT
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id jA6FoavN215390 for <newtrk@lists.uoregon.edu>; Sun, 6 Nov 2005 15:50:36 GMT
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id jA6FoauM010379 for <newtrk@lists.uoregon.edu>; Sun, 6 Nov 2005 15:50:36 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id jA6FoaFx010376 for <newtrk@lists.uoregon.edu>; Sun, 6 Nov 2005 15:50:36 GMT
Received: from zurich.ibm.com (sig-9-145-135-33.de.ibm.com [9.145.135.33]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id QAA31144 for <newtrk@lists.uoregon.edu>; Sun, 6 Nov 2005 16:50:34 +0100
Message-ID: <436E1D8B.3050709@zurich.ibm.com>
Date: Sun, 06 Nov 2005 16:13:15 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: New Track <newtrk@lists.uoregon.edu>
Subject: [newtrk] Last Call comments on draft-ietf-newtrk-decruft-experiment-01.txt
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit
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] Last Call comments on draft-ietf-newtrk-… Brian E Carpenter
- Re: [newtrk] Last Call comments on draft-ietf-new… Pekka Savola
- Re: [newtrk] Last Call comments on draft-ietf-new… Spencer Dawkins
- Re: [newtrk] Last Call comments on draft-ietf-new… C. M. Heard
- Re: [newtrk] Last Call comments on draft-ietf-new… Pekka Savola
- Re: [newtrk] Last Call comments on draft-ietf-new… Eliot Lear
- Re: [newtrk] Last Call comments on draft-ietf-new… C. M. Heard
- Re: [newtrk] Last Call comments on draft-ietf-new… Eliot Lear
- Re: [newtrk] Last Call comments on draft-ietf-new… Harald Tveit Alvestrand
- Re: [newtrk] Last Call comments on draft-ietf-new… Eliot Lear
- Re: [newtrk] Last Call comments on draft-ietf-new… C. M. Heard
- Re: [newtrk] Last Call comments on draft-ietf-new… Harald Tveit Alvestrand
- Re: [newtrk] Last Call comments on draft-ietf-new… Brian E Carpenter
- Re: [newtrk] Last Call comments on draft-ietf-new… Eliot Lear
- Re: [newtrk] Last Call comments on draft-ietf-new… Brian E Carpenter
- Re: [newtrk] Last Call comments on draft-ietf-new… Scott Bradner