IETF Logo Mail Archive

[Ltru] Re: Route 66

"Doug Ewell" <dewell@adelphia.net> Sat, 15 October 2005 04:26 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQdcx-00009f-KB; Sat, 15 Oct 2005 00:26:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQdcv-00009V-QT for ltru@megatron.ietf.org; Sat, 15 Oct 2005 00:26:33 -0400
Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18190 for <ltru@lists.ietf.org>; Sat, 15 Oct 2005 00:26:28 -0400 (EDT)
Received: from DEWELL ([68.66.2.217]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20051015042600.IMRJ27774.mta11.adelphia.net@DEWELL> for <ltru@lists.ietf.org>; Sat, 15 Oct 2005 00:26:00 -0400
Message-ID: <002f01c5d140$85a01460$030aa8c0@DEWELL>
From: Doug Ewell <dewell@adelphia.net>
To: LTRU Working Group <ltru@ietf.org>
References: <20051014220102.RDGT29651.edge4.adelphia.net@megatron.ietf.org>
Date: Fri, 14 Oct 2005 21:25:48 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
Content-Transfer-Encoding: 7bit
Subject: [Ltru] Re: Route 66
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

Misha Wolf <Misha dot Wolf at reuters dot com> wrote:

> Will we ask for a number ending in 66?  If so, for which of the RFCs?

I understand that the RFC Editor is solely responsible for issuing RFC
numbers, and can pick any number imaginable.  I don't suppose it would
hurt to ask, though, keeping the 1766 -> 3066 legacy in mind.

I note that the new successor to RFC 2234, often mentioned in this
group, is 4234.

Definitely the appropriate document for this would be draft-registry
(not -initial or -matching).

--
Doug Ewell
Fullerton, California
http://users.adelphia.net/~dewell/



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

v2.23.0 | Report a Bug | By Email