Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)

John C Klensin <john-ietf@jck.com> Tue, 18 June 2013 17:09 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810A921E805D for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level:
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unvc7dJU1g+k for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2013 10:09:52 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9A00521E8090 for <ietf@ietf.org>; Tue, 18 Jun 2013 10:09:52 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UozPi-000O83-SE; Tue, 18 Jun 2013 13:09:50 -0400
Date: Tue, 18 Jun 2013 13:09:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
Message-ID: <4CF0E73F6EEFC35F39F2E616@JcK-HP8200.jck.com>
In-Reply-To: <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
References: <F14A1FD640A19C37C743AFC2@JcK-HP8200.jck.com> <CAL9jLaZncSO_nnpe0wPgfsEY9zGnCj=N0tE_8MyXZ1gL6re+cA@mail.gmail.com> <4357630D-9FF4-4A6E-91E9-4731B02FD4FA@piuha.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 17:09:58 -0000

--On Tuesday, June 18, 2013 19:54 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

> Chris: The last call on RFC 2050 bis has ended. The draft will
> be shortly on the IESG telechat, up for an approval decision
> and/or suggestion for changes. I personally think it is ready
> to move forward. That is not to say that we wouldn't take
> comments, if you have some.

Jari,

For the record, I still believe that 2050bis should be
published.  Regardless of what I think of some of the things it
says, I think it is reasonably reflective of reality and that
reality is always worth documenting.

> As for the rest of the discussion - I'm sure there are things
> to be improved in ICANN. I'd suggest though that some of the
> feedback might be better placed in an ICANN discussion than on
> IETF list. And is not like there'd be nothing to improve on
> our side :-) Lets focus on IETF aspects here. For what it is
> worth, I have limited experience about ICANN, but it has all
> been very positive.

As to my more general comments, they were not really addressed
to 2050bis and I have no desire to start a discussion of them
here.  However, some assertions about how well ICANN is working
were made on this list by people who do not usually participate
actively in IETF's technical work.  In part because some ICANN
decisions and behaviors does affect the fate of IETF protocols
and the state of the Internet generally, I concluded after a lot
of consideration that those assertions should be responded to on
this list.  I would welcome a discussion (definitely somewhere
else) about that difference in perceptions if it were possible
that it would bring about either improved understanding or
changes that would make the various decision-making processes
that affect the Internet more open and/or more based on a
general understanding of Internet technical reality.  That would
include an offlist discussion of why your perceptions and mine
may differ should you find such a discussion useful.

best,
   john