Re: [Ltru] Good news: draft-ietf-ltru-matching approved by the IESG

Martin Duerst <duerst@it.aoyama.ac.jp> Sun, 09 July 2006 08:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzV4W-00025k-Rh; Sun, 09 Jul 2006 04:55:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzV4V-00025f-Np for ltru@ietf.org; Sun, 09 Jul 2006 04:55:23 -0400
Received: from scmailgw1.scop.aoyama.ac.jp ([133.2.251.194]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzV4R-0004da-3L for ltru@ietf.org; Sun, 09 Jul 2006 04:55:23 -0400
Received: from scmse1.scbb.aoyama.ac.jp (scmse1 [133.2.253.16]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id k698tEqw029724; Sun, 9 Jul 2006 17:55:14 +0900 (JST)
Received: from (133.2.210.1) by scmse1.scbb.aoyama.ac.jp via smtp id 5624_a2f293cc_0f28_11db_9b99_0014221fa3c9; Sun, 09 Jul 2006 17:55:13 +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 k698t5MO020598; Sun, 9 Jul 2006 17:55:08 +0900
Message-Id: <6.0.0.20.2.20060708141213.080016f0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Sat, 08 Jul 2006 14:22:40 +0900
To: Mark Davis <mark.davis@icu-project.org>
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: [Ltru] Good news: draft-ietf-ltru-matching approved by the IESG
In-Reply-To: <30b660a20607070827g88c9daak2048987e087a3530@mail.gmail.com >
References: <6.0.0.20.2.20060707211933.07869b40@localhost> <30b660a20607070827g88c9daak2048987e087a3530@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: LTRU Working Group <ltru@ietf.org>
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

At 00:27 06/07/08, Mark Davis wrote:

>BTW, any word on when the two RFCs will be published?

No. At the minimum, we have to wait for two months for potential
appeals. Then, if there is an appeal, we have to wait for it to
be dealt with. After that, things are up to the RFC Editor. You
can check their queue at http://www.rfc-editor.org/queue.html.

Then one day the editors will get a notice that the RFC Editor
has prepared their document for publication, with information
(diff) on what they changed. The editors then have to check these
changes very carefully (in my own experience, some of them are
just formatting changes, some are helpful wording improvements,
some don't actually change anything, but some others easily
may change the meaning of the document in a way not intended
at all) and communicate back to the RFC Editor. This is supposed
to be a very short period, that's why it's caled "authors 48 hours",
although in general it's a bit longer. It's very important that:
a) you check carefully and exactly tell the RFC Editor (in their
   format) what needs to be fixed, usally in several rounds, and
b) ALL editors of a document explicitly acknowledge that the
   final version can be published. If one editor is on vacation
   or otherwise unreachable, the publication waits.

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