Rechartering terminology (was: [Ltru] Charter Discussion)

Martin Duerst <duerst@it.aoyama.ac.jp> Thu, 22 June 2006 00:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtD3y-000369-Kg; Wed, 21 Jun 2006 20:28:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtD3x-00034b-47 for ltru@ietf.org; Wed, 21 Jun 2006 20:28:49 -0400
Received: from scmailgw1.scop.aoyama.ac.jp ([133.2.251.194]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtD3p-0002Qu-3R for ltru@ietf.org; Wed, 21 Jun 2006 20:28:45 -0400
Received: from scmse1.scbb.aoyama.ac.jp (scmse1 [133.2.253.16]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id k5M0SKhM021535; Thu, 22 Jun 2006 09:28:20 +0900 (JST)
Received: from (133.2.210.1) by scmse1.scbb.aoyama.ac.jp via smtp id 29d5_018bee48_0186_11db_97c5_0014221fa3c9; Thu, 22 Jun 2006 09:28:19 +0900
Received: from Tanzawa.it.aoyama.ac.jp (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.13.6/8.13.1) with ESMTP id k5M0SFPw031345; Thu, 22 Jun 2006 09:28:18 +0900
Message-Id: <6.0.0.20.2.20060621140734.03b71070@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Wed, 21 Jun 2006 14:15:05 +0900
To: Addison Phillips <addison@yahoo-inc.com>, 'Debbie Garside' <debbie@ictmarketing.co.uk>, 'LTRU Working Group' <ltru@ietf.org>
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Rechartering terminology (was: [Ltru] Charter Discussion)
In-Reply-To: <001501c694c6$a5ff1130$9fcd15ac@ds.corp.yahoo.com>
References: <200606202305.k5KN5cU6009088@mta6.iomartmail.com> <001501c694c6$a5ff1130$9fcd15ac@ds.corp.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc:
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>
Errors-To: ltru-bounces@ietf.org

[co-chair hat on]


At 09:07 06/06/21, Addison Phillips wrote:

Debbie Garside wrote:

>> I'll take that as a vote for re-Charter then!

[aside: in the IETF, we don't count votes]

>That is a vote for doing 3066ter in this group, soon-ish, with quite limited
>scope for change---almost a RFC3066bis "second edition" or errata,
>rechartering if necessary.

Just a small terminology correction:

"Rechartering", in the context of the IETF, and as far as I can
remember, refers to changing a group's charter, usually when
extending a group's duration. Because both of our current deliverables
are (mostly) done, if we want to continue work in this group, we
need to change the charter, which means that we need to recharter.

Closing the group, with the option of later creating a new group
(which would have a new acronym, e.g. ultru (update of language
tag registry update :-)) is different from rechartering.

Regards,   Martin.



#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     


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