Re: [Ltru] RFC 3282: should we revise it?

"Doug Ewell" <doug@ewellic.org> Thu, 06 August 2009 05:29 UTC

Return-Path: <doug@ewellic.org>
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 640943A6B48 for <ltru@core3.amsl.com>; Wed, 5 Aug 2009 22:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.496
X-Spam-Level:
X-Spam-Status: No, score=-1.496 tagged_above=-999 required=5 tests=[AWL=1.102, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdwuVgYLLm4F for <ltru@core3.amsl.com>; Wed, 5 Aug 2009 22:29:07 -0700 (PDT)
Received: from p3plsmtpa01-06.prod.phx3.secureserver.net (p3plsmtpa01-06.prod.phx3.secureserver.net [72.167.82.86]) by core3.amsl.com (Postfix) with SMTP id 4FB5D3A6A06 for <ltru@ietf.org>; Wed, 5 Aug 2009 22:28:39 -0700 (PDT)
Received: (qmail 24532 invoked from network); 6 Aug 2009 05:28:42 -0000
Received: from unknown (67.166.27.148) by p3plsmtpa01-06.prod.phx3.secureserver.net (72.167.82.86) with ESMTP; 06 Aug 2009 05:28:41 -0000
Message-ID: <DAB87004F2524683827A9CF792178948@DGBP7M81>
From: "Doug Ewell" <doug@ewellic.org>
To: "LTRU Working Group" <ltru@ietf.org>
References: <mailman.77.1249498812.3028.ltru@ietf.org> <292E8A1E354941089DE14D0A4B506207@DGBP7M81> <4D25F22093241741BC1D0EEBC2DBB1DA01AC46657F@EX-SEA5-D.ant.amazon.com>
Date: Wed, 5 Aug 2009 23:28:38 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [Ltru] RFC 3282: should we revise it?
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2009 05:29:08 -0000

"Phillips, Addison" <addison at amazon dot com> wrote (slightly 
rearranged):

>> As we now know, 4646bis took a year or so longer than 4646.
>
> No it didn't. Mark and I started 4646 on the very first day of the 
> Iraq war. You forget that there were a dozen or so 
> draft-davis-phillips documents before the WG even started.

I didn't forget.  My copy of draft-phillips-langtags-00 is dated 
2003-12-17.  The final draft which became RFC 4646, 
draft-ietf-ltru-registry-14, was approved by IESG on 2005-11-15, or 699 
days later.  We did wait another 10 months for RFC numbers, but that 
time was mostly spent working on the relatively uncontroversial 
draft-4647 and planning for LTRU 2.0.

Draft-ietf-ltru-4646bis-00, the first LTRU 2.0 draft, was dated 
2006-09-11 -- perhaps coincidentally, the same date RFC 4646 was 
published.  Draft-ietf-ltru-4646bis-23 was approved by IESG on 
2009-06-18 (the formal announcement came a week later).  That's a span 
of 1,011 days, or 315 days longer for LTRU 2.0 than for LTRU 1.0.  And 
of course, we're still waiting for RFC numbers.

I'd be willing to bet we spent more days actually *working* on the first 
set of drafts than on the second, but we had a LOT of downtime over the 
past 3 years.  Some issues were left unresolved and undiscussed for 
weeks at a time.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ