Where we stand and where we are going

John C Klensin <klensin@jck.com> Wed, 26 June 2002 07:46 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYA00204YWTCA@eListX.com> (original mail from klensin@jck.com); Wed, 26 Jun 2002 03:46:05 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYA00201YWTC8@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 26 Jun 2002 03:46:05 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYA00201YWSC7@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 26 Jun 2002 03:46:04 -0400 (EDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GYA0020NYWS7Y@eListX.com> for ietf-irnss@lists.elistx.com; Wed, 26 Jun 2002 03:46:04 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=localhost) by bs.jck.com with esmtp (Exim 3.35 #1) id 17N7Us-000Kjq-00 for ietf-irnss@lists.elistx.com; Wed, 26 Jun 2002 07:45:51 +0000
Date: Tue, 25 Jun 2002 12:55:47 -0400
From: John C Klensin <klensin@jck.com>
Subject: Where we stand and where we are going
To: ietf-irnss@lists.elistx.com
Message-id: <3579417.1025009747@localhost>
MIME-version: 1.0
X-Mailer: Mulberry/2.2.1 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>

Hi.

Well, as usual, we have an IETF coming up, the publication
deadline is very near, I haven't accomplished as much as I would
like, and most others appear to not be publishing quickly either.
I am working on getting another version of "dns-search" out
before next Monday's deadline.  While it contains a number of
clarifications and updates, the important material is in several
new (or almost-new) sections.  I will circulate those to this
group as they are ready, in the hope of getting comments before I
fold them into the document or, at least, of giving the rest of
you some time to think about them before Yokohama.

I have realized as I have been working on it that it presents an
abstract model, but perhaps too many undefined choices.  Would it
be helpful to have drafts that identify and specify implementable
protocols (even if they are wrong) as a means of getting comments
and moving forward?  If so, we need to figure out how to get
those written -- I can certainly produce some text for people to
revise and replace, but that may not be the most efficient way to
move forward.

Several people have asked about a BOF (or even a WG) in Yokohama.
The problem, unfortunately, remains what it was in Minneapolis:
especially for a WG, I don't think we have quite enough material
on the table to ask the IESG to set one up: the only relevant
draft I've seen since Minneapolis has been the Chinese name
string proposal.  As most of you know, I would like to have
enough substantive material ready before we try for general
meetings to avoid one of the problems that has hindered the work
of the IDN WG: too many people talking about too many different
topics and not really understanding that they are not
communicating with each other.

Suggestions as to how to proceed, comments on drafts, etc., are,
of  course, welcome at any time.

regards,
    john