Re: Should the RFC Editor publish an RFC in less than 2 months?

Harald Tveit Alvestrand <harald@alvestrand.no> Tue, 04 December 2007 03:43 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 1IzOhH-000871-Rz; Mon, 03 Dec 2007 22:43:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzOhG-00086o-UF for ietf@ietf.org; Mon, 03 Dec 2007 22:43:46 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzOhF-0006Qx-Bq for ietf@ietf.org; Mon, 03 Dec 2007 22:43:46 -0500
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 833E32596E1; Tue, 4 Dec 2007 04:43:44 +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 17274-10; Tue, 4 Dec 2007 04:43:39 +0100 (CET)
Received: from [192.168.16.100] (unknown [130.129.85.87]) by eikenes.alvestrand.no (Postfix) with ESMTP id 98E562596DD; Tue, 4 Dec 2007 04:43:38 +0100 (CET)
Date: Mon, 03 Dec 2007 19:40:59 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "Tom.Petch" <sisyphus@dial.pipex.com>, Lixia Zhang <lixia@CS.UCLA.EDU>
Message-ID: <98D4A240EC5A372F3E88BCE4@htat43p-no.corp.google.com>
In-Reply-To: <039701c8359b$e7864ac0$0601a8c0@pc6>
References: <E1IxTPt-0006r4-ST@ietf.org><4751F44D.3050207@isode.com> <E1Iye5A-0002sv-6J@megatron.ietf.org> <D9AE99FE-731F-4F55-B646-B26A6C8A4485@nokia.com> <7AC22E50348D3364BD9C2749@B50854F0A9192E8EC6CDA126> <D1661755189D9C66DADD5ACD@[10.1.129.171]><fiur2s$64q$1@ger.gmane.org> <7C07FB6D-805E-4FF5-8F40-64BA444F065F@cs.ucla.edu> <039701c8359b$e7864ac0$0601a8c0@pc6>
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.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ietf@ietf.org
Subject: Re: Should the RFC Editor publish an RFC in less than 2 months?
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 3. desember 2007 10:09 +0100 "Tom.Petch" <sisyphus@dial.pipex.com> 
wrote:

> At the same time, I see the benefits of having the RFC now rather than in
> February as minimal; early adopters adopt early and are proud to announce
> in their marketing material that their product conforms to I-D
> draft-ietf-wg-enhanced-protocol.  The date of the arrival of an RFC is
> irelevant to them.

The people who actually care about whether something is an I-D or an RFC 
are the people who write specifications (other bodies' standards, RFPs, 
government mandates.... wherever they need a stable identifier).

For the implementors, an I-D + the fact of approval is sufficient. For 
those who write other documents, it's not - they need the RFC number.

              Harald



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