Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Sun, 14 Aug 2005 16:40:27 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2C30F32008E for ; Sun, 14 Aug 2005 16:40:27 +0200 (CEST) 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 29053-04 for ; Sun, 14 Aug 2005 16:40:17 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 661C232008A for ; Sun, 14 Aug 2005 16:40:17 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4JeW-00029f-Cn; Sun, 14 Aug 2005 10:39:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4JeS-00029O-Ko for ltru@megatron.ietf.org; Sun, 14 Aug 2005 10:39:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29151 for ; Sun, 14 Aug 2005 10:39:49 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E4KDM-0006Se-8T for ltru@ietf.org; Sun, 14 Aug 2005 11:15:59 -0400 Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1E4JeK-00073X-62; Sun, 14 Aug 2005 07:39:44 -0700 Message-Id: <6.2.1.2.2.20050814152250.04080180@mail.afrac.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sun, 14 Aug 2005 16:03:58 +0200 To: "Randy Presuhn" , ltru@ietf.org From: r&d afrac Subject: Re: [Ltru] Wrapping up the second WG last calls on the registry and initial registry drafts In-Reply-To: <008101c59fca$b6729560$7f1afea9@oemcomputer> References: <008101c59fca$b6729560$7f1afea9@oemcomputer> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - afrac.org X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: X-BeenThere: ltru@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltru-bounces@lists.ietf.org Errors-To: ltru-bounces@lists.ietf.org X-Virus-Scanned: by amavisd-new at alvestrand.no On 07:49 13/08/2005, Randy Presuhn said: > Then Martin and I will start the process of shepherding these through > the IESG, using the >http://www.ietf.org/internet-drafts/draft-ietf-proto-wgchair-doc-shepherding-05.txt >procedures as directed by our AD. Interesting. FYI: 1) I have a pending proposition to the authors of this draft to make every Sheperding WG Chair work copied to the WG, including the separate mails reporting on formal oppositions, as a LC not subject to consensus, for transparency and editing assistance (this is the WG sales pitch). 2) I have also proposed two additional questions (the Charter which is the Contact with the IESG/IAB is not considered, COI and chapel and status quo effects are only partly addressed): - has the WG initially well understood its Charter? Has it adhered to it? Has it extended it in some manner? Has the WG used a working road map of some sort? Does the presented document fulfills the corresponding part(s) of the WG Charter? Has the WG identified relations with the Charter of other WGs? In such a case have you discussed the matter with the concerned ADs and WG Chairs? - do you feel comfortable that this document is free from competition between technical chapels and represents a genuine, inclusive and open effort to best support all the needs of the state of the art protocols, applications, procedures, of the current or of the documented common practices, and of the disclosed R&D projects? jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru