Re: [Ianaplan] Proposed text reflecting IETF91 discussion

Miles Fidelman <mfidelman@meetinghouse.net> Mon, 17 November 2014 00:27 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 E78B31A0264 for <ianaplan@ietfa.amsl.com>; Sun, 16 Nov 2014 16:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 Y50QmlDQCMQv for <ianaplan@ietfa.amsl.com>; Sun, 16 Nov 2014 16:27:11 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0FC1A0081 for <ianaplan@ietf.org>; Sun, 16 Nov 2014 16:27:11 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 5B70DCC09E for <ianaplan@ietf.org>; Sun, 16 Nov 2014 19:27:10 -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 cAooYwYfDsF0 for <ianaplan@ietf.org>; Sun, 16 Nov 2014 19:27:01 -0500 (EST)
Received: from new-host-3.home (pool-173-76-231-196.bstnma.fios.verizon.net [173.76.231.196]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 81172CC095 for <ianaplan@ietf.org>; Sun, 16 Nov 2014 19:27:01 -0500 (EST)
Message-ID: <546940D5.80104@meetinghouse.net>
Date: Sun, 16 Nov 2014 19:27:01 -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
To: ianaplan@ietf.org
References: <2A9AA299-83BE-4984-B6DC-957B67C253FF@cooperw.in> <GLEAIDJPBJDOLEICCGMNIEFKCOAA.rhill@hill-a.ch> <128d7c1fc7a0469fb964ba4f36f9f6d4@EX13-MBX-13.ad.syr.edu> <D08E2C1D.13A7F3%jon.peterson@neustar.biz> <CAJkfFBwDi_T_2bHdSS7fAP5d3D+UbHqf=S=fH6HnbYW1aisKkQ@mail.gmail.com> <20141116213738.GE4455@mx1.yitter.info> <54692052.7000602@meetinghouse.net> <546923D1.3070006@cs.tcd.ie> <54693483.3090601@meetinghouse.net> <546939FC.8010902@cs.tcd.ie>
In-Reply-To: <546939FC.8010902@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/3Z-HpTYu433O7wP8qU-89WryVhA
Subject: Re: [Ianaplan] Proposed text reflecting IETF91 discussion
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: Mon, 17 Nov 2014 00:27:13 -0000

Stephen Farrell wrote:
>
> On 16/11/14 23:34, Miles Fidelman wrote:
>> The legal and contractual stuff matters.  A lot.  I remain puzzled that
>> this "does not seem to sink in despite having been explained a number of
>> ways by a number of people."
> People have tried to help you I think. The legal stuff matters far less
> if we have a work around that means any legal attack is going to be
> ineffective or legal problem is going to be avoided. In this case, and
> as stated numerous times and still unacknowledged by you, we do have
> that possibility as a fine back up in the event of problems. (Not that
> we expect to need to exercise it, but it's pretty obvious we could.)

With all due respect, I don't need "help" to understand the issues or 
the opinions.  We simply disagree.

And, I'm not sure that's an accurate representation of a consensus 
opinion.  I've heard three different forms of "work around:"

- put all the protocol number info in the public domain, if necessary 
start publishing under a different domain -- I've seen a wide range of 
opinions as to whether that would be a satisfactory or sufficient 
work-around

- leave legal and contractual matters to others (let's not deal with the 
issue in this WG)

- the IAB and IAOC can deal with contractual and legal conflicts in the 
future

>
> And I'd be grateful if you'd at least have the good grace to
> acknowledge that the position that the IETF can avoid potential legal
> silliness here is tenable, even if you do not agree that that's in
> itself a sound basis for planning.

I'm actually not sure I can, in good consciousness, do that.  Of course 
the group can decide to avoid dealing with "legal silliness" now.  But, 
to me, that is practically a guarantee of having to deal with it at some 
point in the future.

Miles Fidelman


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