Re: [Ltru] Consensus call: extlang

"Randy Presuhn" <randy_presuhn@mindspring.com> Thu, 29 May 2008 18:47 UTC

Return-Path: <ltru-bounces@ietf.org>
X-Original-To: ltru-archive@megatron.ietf.org
Delivered-To: ietfarch-ltru-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24F733A6895; Thu, 29 May 2008 11:47:44 -0700 (PDT)
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 B53C83A6886 for <ltru@core3.amsl.com>; Thu, 29 May 2008 11:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599]
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 tbQLUHrCiXjL for <ltru@core3.amsl.com>; Thu, 29 May 2008 11:47:41 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id 934A73A688B for <ltru@ietf.org>; Thu, 29 May 2008 11:47:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=k0fwHa+aagh/we30lBGt8l8Nj2q9SgDFWioh98q21cMJOnHOGGrAEPAapkl9/xxv; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.84.252] (helo=oemcomputer) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1K1nA2-0004J4-Km for ltru@ietf.org; Thu, 29 May 2008 14:47:38 -0400
Message-ID: <007601c8c1bc$84d93920$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: LTRU Working Group <ltru@ietf.org>
References: <01c301c8bbe5$8c2810c0$6801a8c0@oemcomputer><008a01c8bedc$72b97b20$6801a8c0@oemcomputer><30b660a20805252132g28ff50b0kd5b04d6f47ca35d2@mail.gmail.com><002001c8bef3$e0497520$6801a8c0@oemcomputer><6.0.0.20.2.20080527170755.05bd89c0@localhost><002f01c8c024$0dcdb5c0$6801a8c0@oemcomputer><6.0.0.20.2.20080528163346.074fac80@localhost> <001f01c8c122$0cbcae80$6801a8c0@oemcomputer> <4D25F22093241741BC1D0EEBC2DBB1DA013A84C314@EX-SEA5-D.ant.amazon.com>
Date: Thu, 29 May 2008 11:47:59 -0700
MIME-Version: 1.0
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
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a63b7957ab9b23b37772ef212c118cca476d67a4502254f9350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.84.252
Subject: Re: [Ltru] Consensus call: extlang
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

Hi -

> From: "Phillips, Addison" <addison@amazon.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>; "LTRU Working Group" <ltru@ietf.org>
> Sent: Thursday, May 29, 2008 7:51 AM
> Subject: RE: [Ltru] Consensus call: extlang
>

> > One was sent after the deadline.
> 
> If this was my vote (sent yesterday prior to your message),
> your "revised totals" appear wrong, as I voted "A,B".

The summary (with the late response) was sent out before
your much later response.  Including the three late responses
I've seen, it now comes to 
Q1 a-6 b-9 c-4 
Q2 a-8 b-6 c-5

Not the clear-cut result any of us would have liked.
(And for me, having a clear decision is much more important
than the decision itself!)

...
> This is not a situation in which either camp has a totally
> decisive argument up its sleeve.

This has been apparent for many, many months.

> While I think this is the wrong way to go (obviously, as I
> supported removing extlang), some kind of decision is desirable.

Agreed.  However, the recent discussion indicates that the group
doesn't feel much urgency in moving on.  If the decision were
solely up to me, I'd recommend shutting down the working group,
letting the people that care about it fight it out, and then let
them request a BOF at some future IETF meeting when they think
they're ready to resume work as a working group.  (This is
what happened when the SNMPv2 working group missed its charter
deadline by a far, far smaller margin.)

> As co-editor, my immediate concern is how to implement this.
> Assuming that we don't do a new round of voting and persuasion,
> I can hardly restore the text we had prior to removing extlang
> because some serious editing has occurred since then.

Agreed.

> We will need to decide what criteria are used to register and
> maintain extlangs as a result (a problem we were struggling with
> prior to the decision to remove extlang). What will be necessary,
> I think, is a stem-to-stern restore-and-edit pass with the particular
> notes of interest sent to the list. The resulting draft will then
> need to be reviewed by the list.

Sounds reasonable.
 
> If there is some doubt about whether the results of this consensus call
> will hold, I would point out that this might be a useful exercise in
> any event, as we can compare this putative "draft-15" (incorporating
> feedback from the list, of course) to the current draft-14 more directly:
> we can compare each other's cherry picking machines for elegance :-).

:-)  Since we're in "the lesser of the evils" mode, I agree it would be helpful
to work through the devilish details.
 
> Is this the decision, Randy and Martin? Or should we waffle along a bit longer?

Creating such a draft sounds good to me.  Martin, any insights?

Randy

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