[Ianaplan] Everybody, take a breather (Was: Re: CWG draft and its impact on the IETF)

Jari Arkko <jari.arkko@piuha.net> Fri, 22 May 2015 20:58 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 071361A8883 for <ianaplan@ietfa.amsl.com>; Fri, 22 May 2015 13:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level:
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hQrDe6VQ14Y for <ianaplan@ietfa.amsl.com>; Fri, 22 May 2015 13:58:46 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C40421A8881 for <ianaplan@ietf.org>; Fri, 22 May 2015 13:58:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 247562CC5F for <ianaplan@ietf.org>; Fri, 22 May 2015 23:58:45 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hOUjzmhAtdKe for <ianaplan@ietf.org>; Fri, 22 May 2015 23:58:44 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 951742CC5A for <ianaplan@ietf.org>; Fri, 22 May 2015 23:58:44 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_109B6E8F-33F8-4C0E-9200-E6C8389266F7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Message-Id: <7434A5BB-4189-4515-8A6B-DC460B05BBF6@piuha.net>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Date: Fri, 22 May 2015 23:58:43 +0300
References: <5550F809.80200@cisco.com> <88F741BF3D4C2A597622A70C@JcK-HP8200.jck.com> <44A0F230-A98C-4060-88E2-B20FE1DE1FC5@isoc.org> <14ff00ba1aae45f2a8f4befb896e2a08@EX13-MBX-13.ad.syr.edu> <D17525F2-190B-4D00-AEBE-5AD96BA79E79@arin.net> <A026656644A030B7130B94B5@JcK-HP8200.jck.com> <ad1d0707ff1b44eb9e48fef18d8e1268@EX13-MBX-13.ad.syr.edu> <687222FF507C0D3EDBD9CAAA@JcK-HP8200.jck.com> <000001d091f7$266de3f0$7349abd0$@ch> <51ce19bc2a93443586adcdd2fac3888a@EX13-MBX-13.ad.syr.edu> <555BD28F.10402@gmail.com> <97E5874491A30994EC386C37@JcK-HP8200.jck.com> <555CEDFF.5010601@gmail.com> <51E8C05D9CFB07754ECD13F5@JcK-HP8200.jck.com> <DM2PR0301MB065543B4DCBCB7 51656B563DA8C20@DM2PR0301MB0655.namprd03.prod.outlook.com> <a78386a2666240d48be0aba1fb543e75@EX13-MBX-13.ad.syr.edu> <9F5DADEC7B0F069BA5BCB67A@JcK-HP8200.jck.com> <90712DBB-A97F-48AA-91D5-E1E18A395B33@istaff.org> <748A065C2DEF6DC717B0E802@JcK-HP8200.jck.com> <B8A5D91B-68E7-4EE1-BFA5-40764EF84F86@istaff.org> <555EA874.5040804@gmail.com> < 035805E649EA5F8EEB12269C@JcK-HP8200.jck.com>
To: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
In-Reply-To: <035805E649EA5F8EEB12269C@JcK-HP8200.jck.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/AHsa1f9S597GTPd3I-ycYvDoGMs>
Subject: [Ianaplan] Everybody, take a breather (Was: Re: CWG draft and its impact on the IETF)
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2015 20:58:48 -0000

Folks,

I think it is time to cool down the discussion a bit.
Please take a pause before deciding to comment
on individual posters, use unnecessarily polarised
words (such as seceding, utter), casting a behavioural
pattern on organisations, or painting a very black
and white picture of the road ahead.

We are trying to bring about a significant transition
in the Internet. Parts of this transition are easier,
other parts are harder. At the IETF we are lucky
to be on the easier side, but we also want best
for the whole Internet, and not just for us. While
there are significant challenges still ahead in the
names side, one observation that I would like
to make is that the effort is unprecedented in
how much it is community driven. But work
is still needed,  As Lynn pointed out, we need
to work together.

I would like to separate the discussion about the
rationale and commentary of the names proposal
a bit from the effects to the IETF. 

As for the commentary on the names proposal,
I think it is quite appropriate to make comments
and ask questions. Even hard ones. I am
absolutely certain that the names community
is happy about receiving such input and feedback.
Lets work through that.

But the other question, perhaps even more
immediate for the IETF, is whether the arrangements
have an impact on us. My own view is similar to what
Bob, Brian, and others have stated on the list. That
is, the IETF can work with existing MoUs and that it
isn’t fundamentally incompatible with internal
organisational changes on where the IANA department
actually lives inside ICANN. This is also supported
by what Avri said. However, as several posters have
noted, the names proposal is not complete yet. So 
can we work together on finding the details that
work for us?

I wanted to highlight also that the largest
part of coordination between the three IANA
communities happens indeed between the
communities. Not through IANA. Take the discussions
from a couple years back when we talked about
expanding the private address range, for instance.
There was a lot of back and forth between the IETF
and the RIRs. In the end we made a decision and
communicated it to IANA, which executed it with
the help of the IETF and RIRs doing the right thing.

Jari