[Ltru] Fwd: Response to Part 1 of the appeal by JFC Morfin dated 2006-08-17

Martin Duerst <duerst@it.aoyama.ac.jp> Wed, 23 August 2006 09:14 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFooO-0002qG-E6; Wed, 23 Aug 2006 05:14:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFooN-0002q9-2X for ltru@ietf.org; Wed, 23 Aug 2006 05:14:11 -0400
Received: from scmailgw2.scop.aoyama.ac.jp ([133.2.251.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFooJ-00071L-D4 for ltru@ietf.org; Wed, 23 Aug 2006 05:14:11 -0400
Received: from scmse2.scbb.aoyama.ac.jp (scmse2 [133.2.253.17]) by scmailgw2.scop.aoyama.ac.jp (secret/secret) with SMTP id k7N9E4Sv027370 for <ltru@ietf.org>; Wed, 23 Aug 2006 18:14:04 +0900 (JST)
Received: from (133.2.210.1) by scmse2.scbb.aoyama.ac.jp via smtp id 7763_b9263446_3287_11db_9bd0_0014221f2a2d; Wed, 23 Aug 2006 18:14:03 +0900
Received: from Tanzawa.it.aoyama.ac.jp (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.13.7/8.13.1) with ESMTP id k7N9DVpD020245 for <ltru@ietf.org>; Wed, 23 Aug 2006 18:14:03 +0900
Message-Id: <6.0.0.20.2.20060823180516.18837b20@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Wed, 23 Aug 2006 18:06:29 +0900
To: ltru@ietf.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Subject: [Ltru] Fwd: Response to Part 1 of the appeal by JFC Morfin dated 2006-08-17
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

Dear LTRU WG member,

This should be of interest to you if you follow the progress
of our documents.

Regards,     Martin.

>To: JFC Morfin <jefsey@online.fr>
>From: IESG Secretary <iesg-secretary@ietf.org>
>Date: Tue, 22 Aug 2006 12:05:42 -0400
>Cc: iesg@ietf.org, ietf-announce@ietf.org
>Subject: Response to Part 1 of the appeal by JFC Morfin dated 2006-08-17 

>Response to Part 1 of the appeal by JFC Morfin dated 2006-08-17
>
>This is the IESG response to Part 1 of the appeal by JFC Morfin
>sent on 2006-08-17 and posted at
>http://www.ietf.org/IESG/APPEALS/jefsey-appeal-to-iesg-08-17-2006.pdf
>
>This was considered during the IESG teleconference
>on the same date. Part 1 of the appeal is summarized as:
>
>"Appeal against the decision to consider a request to the RFC Editor
>to expedite the publication of draft-ietf-ltru-registry,
>draft-ietf-ltru-matching and draft-ietf-ltru-initial"
>
>followed by various arguments.
>
>As discussed in the July 10 response to the appeal from Dean Anderson
>against draft-ietf-grow-anycast, the appeals process is designed to
>handle disputes that cannot be handled through other means. The IESG
>cannot come up with a situation where it would be appropriate to
>appeal the consideration of some action before a decision is made;
>this is certainly not such a case. Instead, participants should
>provide input to that consideration. We interpret this appeal in that
>light: we interpret part 1 of the appeal as arguments why the IESG
>should choose to delay a decision to expedite this BCP.
>
>The IESG makes such requests regularly when another SDO's publication
>schedule requires the ability to cite a forthcoming RFC normatively.
>There is nothing exceptional or discriminatory about doing so in the
>case of Unicode. It would not be sufficient for Unicode to refer
>generically to BCP 47; the reference needs to be to specific text
>and hence to the RFCs.
>
>We note that RFC 2026 does not require appeals to have suspensive effect.
>If an appeal against the approval of a published RFC were to succeed,
>that RFC could be reclassified as Historic.
>
>We find no merit in the arguments in Part 1 of the appeal, which is
>dismissed.
>
>[The response to Part 2 of the appeal will be published later.]
>
>_______________________________________________
>IETF-Announce mailing list
>IETF-Announce@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf-announce


#-#-#  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