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

Miles Fidelman <mfidelman@meetinghouse.net> Mon, 10 November 2014 01:01 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 59AA41A8827 for <ianaplan@ietfa.amsl.com>; Sun, 9 Nov 2014 17:01:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level:
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_75=0.6, 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 zCGKK8puG_Ay for <ianaplan@ietfa.amsl.com>; Sun, 9 Nov 2014 17:01:43 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id BD22D1A87DB for <ianaplan@ietf.org>; Sun, 9 Nov 2014 17:01:43 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 0775CCC083 for <ianaplan@ietf.org>; Sun, 9 Nov 2014 20:01:43 -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 wkSc-PZrjZKA for <ianaplan@ietf.org>; Sun, 9 Nov 2014 20:01:37 -0500 (EST)
Received: from Miles-Fidelmans-MacBook-Pro.local (ool-6c3a30e2.static.optonline.net [108.58.48.226]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A75A6CC04F for <ianaplan@ietf.org>; Sun, 9 Nov 2014 20:01:37 -0500 (EST)
Message-ID: <54600E59.5050207@meetinghouse.net>
Date: Sun, 09 Nov 2014 20:01:13 -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
References: <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <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> <059f2b06a7b44f09b7568d8966861fb8@EX13-MBX-13.ad.syr.edu> <D0824FAD.137A42%jon.peterson@neustar.biz> <E314302D-5179-4899-9DB7-A3AF18C134E8@gmail.com> <20141108155153.GB37292@mx1.yitter.info> <D083864D.138D18%jon.peterson@neustar.biz> <A6D94EF5-BD92-4080-8C18-E415BD0BB880@isi.edu> <C78A1523-316F-46A1-9FCE-D0D205679C84@gmail.com> <13B26DE5-315D-453F-B89B-377CCD338ED9@isi.edu> <A7BD5ECF-11E4-42F1-A2B7-BF9B399635C3@gmail.com> <14D42443-53E7-49FA-88DD-7F4BB6BC2DF4@istaff.org> <545F69FB.5000501@meetinghouse.net> <7B719509-5A93-4B85-B7E2-262DDCB64461@istaff.org> <545F955C.5040405@meetinghouse.net> <CAD_dc6i=OisQcQG-v9con0xc6ng4HY+ctzuh+z77RN13iae_ZA@mail.gmail.com>
In-Reply-To: <CAD_dc6i=OisQcQG-v9con0xc6ng4HY+ctzuh+z77RN13iae_ZA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/QRbAWWPVHoN8GmtmqraDBkWDEw0
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: Mon, 10 Nov 2014 01:01:45 -0000

Seun Ojedeji wrote:
>
> sent from Google nexus 4
> kindly excuse brevity and typos.
> On 9 Nov 2014 17:25, "Miles Fidelman" <mfidelman@meetinghouse.net 
> <mailto:mfidelman@meetinghouse.net>> wrote:
> >
> > John Curran wrote:
> >>
> >> On Nov 9, 2014, at 3:19 AM, Miles Fidelman 
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
> >>>
> >
> > At the very least, I'd like to see something in our proposal that 
> says that this is an issue that has to be addressed clearly as part of 
> final transition arrangements.  I'd personally like to see the IETF 
> lawyers weigh in and suggest a proposed approach to put forward to the 
> ICG (when flagging a problem, it's always nice to be able to offer a 
> solution).
> >
> I did like to add a +1 to this. However I wonder the basis by which 
> IETF will be making such recommendation[1] especially considering the 
> role it's playing in this process(being a protocol parameter only 
> community).
>

The basis being that IETF is one of the "users" of the IANA.org mark and 
domain - essentially the same basis as the other communities.

> Cheers
> 1. However by the word "recommendation" implies that the ICG could 
> perhaps decide to mute. Making it a component of the proposal would 
> have been desirable.
>

There's no reason a recommendation can't be part of the proposal. In 
essence, I see three things being stated, in the relevant parts of the 
document:

1.  that IETF uses the IANA mark and domain, and how

2.  that there are potential issues that could come up during the 
current and/or future transitions - specifically
--- making provisions for clear and smooth transition of 
ownership/control/licensing/delegation of the mark and name
--- anticipating the possibility that, at some future point, there may 
be different contractors performing different parts of the IANA 
function, which would require somewhat more complicated 
ownership/control/delegation/day-to-day management of the domain

3.  that, the final, combined, consensus proposal that the ICG delivers 
to NTIA, should include specific mechanisms, supplemental agreements, 
what-have-you that address the issues identified above, to be put in 
place as part of the transition process, and then go on to say:
- IETF has identified several options, including:
--- concluding supplemental agreements that provide for the transition 
of ownership/control/registration/etc. in the event of a change in IANA 
functions contractor(s)
--- placing ownership/control/etc. of the marks and domain in the hands 
of an entity other than the IANA functions contractor, such as,
------ the IETF Trust
------ an escrow account with a fiduciary institution, controlled 
jointly by the IETF, and the other stakeholder communities that rely on 
the IANA functions contractor
------ a joint entity created by, and controlled jointly by the IETF and 
the other.....
- and optionally, include a statement that, the IETF's lawyers and IAOC 
recommend option <x> as the one they see as most likely to support 
smooth transitions in IANA functions contractor(s)

Identify the issue.
Identify several solutions that we've identified.
Identify the one our lawyers recommend.
Then leave it to the ICG to manage reconciliation with anything the 
other communities come up with, as part of the next step in the process 
of getting to a proposal.

Anyway, that's how I'd approach it.

Miles Fidelman

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