Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Miles Fidelman <mfidelman@meetinghouse.net> Thu, 06 November 2014 16:25 UTC

Return-Path: <mfidelman@meetinghouse.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 1E7A81A8832 for <ianaplan@ietfa.amsl.com>; Thu, 6 Nov 2014 08:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 rseM7QasMSU0 for <ianaplan@ietfa.amsl.com>; Thu, 6 Nov 2014 08:25:30 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id D12C61A8769 for <ianaplan@ietf.org>; Thu, 6 Nov 2014 08:25:29 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 362CACC092 for <ianaplan@ietf.org>; Thu, 6 Nov 2014 11:25:29 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dVIwFMSe9J8t for <ianaplan@ietf.org>; Thu, 6 Nov 2014 11:25:20 -0500 (EST)
Received: from new-host-3.home (pool-96-237-159-213.bstnma.fios.verizon.net [96.237.159.213]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A9D18CC096 for <ianaplan@ietf.org>; Thu, 6 Nov 2014 11:25:17 -0500 (EST)
Message-ID: <545BA0ED.9010608@meetinghouse.net>
Date: Thu, 06 Nov 2014 11:25:17 -0500
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30
MIME-Version: 1.0
CC: "ianaplan@ietf.org" <ianaplan@ietf.org>
References: <GLEAIDJPBJDOLEICCGMNIEOJCNAA.rhill@hill-a.ch> <54594A50.4090305@meetinghouse.net> <20141105001731.GA30186@mx1.yitter.info> <54597BDB.7040305@meetinghouse.net> <5459BA98.1070006@gmail.com> <545A208A.7040304@meetinghouse.net> <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <20141105154903.GI30379@mx1.yitter.info> <498a39b81b774192bd2d609b3feab35f@EX13-MBX-13.ad.syr.edu> <20141105234444.GM31320@crankycanuck.ca> <545ABCB0.5080206@meetinghouse.net> <8f3dcda6c3db4cd8be1b77444f987d59@EX13-MBX-13.ad.syr.edu> <D0805C27.136BE7%jon.peterson@neustar.biz> <7F52A930-DD6F-4D0D-8278-A021CF8A466C@istaff.org> <D080D78C.136C6E%jon.peterson@neustar.biz> <D8680FE5-1088-4842-ADB8-EB8E6F6CF681@istaff.org>
In-Reply-To: <D8680FE5-1088-4842-ADB8-EB8E6F6CF681@istaff.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/MxQVmhuC_mhZPX-ez9iuPOy2OC0
Subject: Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
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: Thu, 06 Nov 2014 16:25:31 -0000

John Curran wrote:
> On Nov 6, 2014, at 3:54 PM, Peterson, Jon <jon.peterson@neustar.biz> wrote:
>>> Jon -
>>>
>>>   I have no view on whether the IETF should assert any position with
>>>   respect to intended future use of the IANA marks or domain name (and
>>>   do understand how asserting a position, absent constructive
>>> engagement,
>>>   could be misunderstood by others in the stewardship transition planning
>>>   process.)
>>>
>>>   However, I cannot tell if you are also against any mention of the
>>> IETF's
>>>   _present and existing use_ of the IANA marks and domain name in the
>>> ICG
>>>   RFP response...  could you opine specifically on this question?
>> I'm totally fine with detailing the IETF's present and existing use of the
>> IANA - we would be kind of missing the point of the questionnaire if we
>> didn't.
> Agreed.
>
>> And I think it would be great if that relationship continued along
>> past lines.
> I think it would be great if cooperation in the use of the domain name
> and marks (to serve multiple communities) was achieved even absent NTIA's
> present IANA stewardship; how do you proposed this should be achieved?
>

Cooperation is great, until it fails.  Isn't the point of clear 
understandings (particularly in contracts) to avoid confusion that might 
lead to lack of cooperation, and to deal with situations where 
cooperation fails, in a smooth a way as possible?  Clarity in advance is 
generally a good way to avoid a lot of the pain when cooperation fails - 
the more wiggle room in a contract (or MoU, or protocol spec, or what 
have you) - the more room for folks working at cross purposes, and for 
drawn out litigation when things go drastically wrong.  (Granted that 
too much specificity can also be a straightjacket that impinges on 
day-to-day flexibility among cooperating parties - also something to be 
avoided.)

Miles Fidelmn



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra