Re: [Ianaplan] Our impossible job, was Where we're at/going forward

Eliot Lear <lear@cisco.com> Wed, 26 August 2015 08:03 UTC

Return-Path: <lear@cisco.com>
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 9FA251A902B for <ianaplan@ietfa.amsl.com>; Wed, 26 Aug 2015 01:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.612
X-Spam-Level:
X-Spam-Status: No, score=-12.612 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 hO8Y_Z4MQh9p for <ianaplan@ietfa.amsl.com>; Wed, 26 Aug 2015 01:03:29 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E541A8A74 for <ianaplan@ietf.org>; Wed, 26 Aug 2015 01:03:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2909; q=dns/txt; s=iport; t=1440576209; x=1441785809; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=q9kZwNVPteh9p5/aI65A30pJt7CbsS55hODgjGYejsw=; b=B0aTxzFSkBsaH/dIwQzwuh7VzP4fCOkWWRHC/CVocU2oBuya3s3idVJ/ ntrJRQ6xvkRK09KtamGxApJ20MBeegDK3+8kffzKTLEDvZaFKpym3ZS9T Lm44C7kBDJg4ZA7u/SEU6aN3KZDnpxNNHJI25hCrzffeDKM+6iQ3UbiCs I=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CiBADicd1V/xbLJq1dh3vCZgKBdRABAQEBAQEBgQqEIwEBAQMBI0kDAwQICwsYCSECAg8CRgYBDAgBARCIEgizGpR/AQEBAQEBAQMBAQEBAQEBG4tbhRGCaYFDBYxriEyCQIFciFaId49jggEmhAA8gn8BAQE
X-IronPort-AV: E=Sophos;i="5.17,415,1437436800"; d="asc'?scan'208";a="629320643"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 26 Aug 2015 08:03:27 +0000
Received: from [10.61.210.101] ([10.61.210.101]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t7Q83R2v022180; Wed, 26 Aug 2015 08:03:27 GMT
To: John Levine <johnl@taugh.com>, ianaplan@ietf.org
References: <20150825214212.60865.qmail@ary.lan>
From: Eliot Lear <lear@cisco.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <55DD72CE.40403@cisco.com>
Date: Wed, 26 Aug 2015 10:03:26 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150825214212.60865.qmail@ary.lan>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NhuUunTRSjx9mqIVrFOVSlU852jBUdrHj"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/HTtimQ0fkknYuxgRGBtoEHytxsE>
Subject: Re: [Ianaplan] Our impossible job, was Where we're at/going forward
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 26 Aug 2015 08:03:30 -0000

Hi John,

On 8/25/15 11:42 PM, John Levine wrote:
> The IETF interacts indirectly with IANA via the names world in lots of
> ways.  The obvious recent example is the discussion about .onion and
> other non-DNS name use, but there are technical stability issues for
> changes to top level records (.google asked for a wildcard last year),
> for DNSSEC (will we ever invent a workable way to provision it) and
> all of the various ways to bundle names that are semantically related,
> a problem that the marketing community appears to believe is trivial,
> but that we have found intractable.

Indeed, and you haven't even touched on Unicode.

>   So far we've managed to dodge the
> bullets, but that seems to me largely due to the moral suasion that we
> have over ICANN, due in no small part to personal relationships with
> leaders who, although vigorous, are not immortal.

Yes.
>
> So if we're going to make a statement about the combined proposal, we
> need to make it clear that we endorse the parameter parts and make no
> statement either way about the rest of it.  If the press spins that as
> saying the IETF doesn't endorse the names PTI, they wouldn't be wrong.

The problem is that you continue to treat this proposal as three.  It's
not.  It's one integrated proposal.  Further, a binary decision will
eventually be made.  Ours is as follows: do we support it or not, and
why or why not?  Does the ICG have more information if we simply support
only our portion of the proposal?  I would say not.  They gain a little
information if we tell them that they haven't cocked it up.  But a very
little more.  We have the opportunity to say more.  If we pass on that
opportunity, the decision will be ceded to others; and we may not like
their view or their goals at all.

Thus we perform a risk analysis.  Are the risks of not supporting the
proposal outweighed by the risks of supporting it?  Note "it" and not
"them".

Eliot