Re: Revising full standards

Harald Tveit Alvestrand <harald@alvestrand.no> Tue, 11 December 2007 17:00 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J28Su-0008St-6z; Tue, 11 Dec 2007 12:00:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J28Ss-0008R9-JP for ietf@ietf.org; Tue, 11 Dec 2007 12:00:14 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J28Sr-0004YN-1s for ietf@ietf.org; Tue, 11 Dec 2007 12:00:14 -0500
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3AD9C259780; Tue, 11 Dec 2007 18:00:12 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29603-01; Tue, 11 Dec 2007 18:00:06 +0100 (CET)
Received: from [192.168.16.100] (216-239-45-4.google.com [216.239.45.4]) by eikenes.alvestrand.no (Postfix) with ESMTP id 378A1259787; Tue, 11 Dec 2007 17:59:58 +0100 (CET)
Date: Tue, 11 Dec 2007 08:16:07 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Iain Calder <ic56@rogers.com>, ietf@ietf.org, "Hallam-Baker, Phillip" <pbaker@verisign.com>
Message-ID: <413D96A9947CFAA3DEE951C7@B50854F0A9192E8EC6CDA126>
In-Reply-To: <E1J23Bz-0008K3-QA@hephaestus>
References: <2788466ED3E31C418E9ACC5C31661557084F7F@mou1wnexmb09.vcorp.ad.vrsn.com> <E1J23Bz-0008K3-QA@hephaestus>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: -0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: John C Klensin <john-ietf@jck.com>, Bob Braden <braden@ISI.EDU>
Subject: Re: Revising full standards
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org


--On 11. desember 2007 06:22 -0500 Iain Calder <ic56@rogers.com> wrote:

> I think that, for implementors and adopters alike, a
> single, absolute definition is too simplistic a view to
> be meaningful in today's world.  Merely renaming the STD
> series won't solve the problem of deciding when/if the
> STD-10 / IETF-EMAIL pointer should be changed from RFC-821
> to RFC-2821.  But that's a bigger can of worms.
>
> BTW, can anyone point me to documentation of previous
> attempts to solve that bigger can of worms?

The archives and meeting notes from the late NEWTRK working group should 
prove interesting, albeit not uplifting, reading.

In particular, draft-ietf-newtrk-repurposing-isd and 
draft-otis-newtrk-rfc-set should be entertaining.

The WG was shut down without reaching a conclusion.

              Harald




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf