Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-response-01
Miles Fidelman <mfidelman@meetinghouse.net> Sun, 26 October 2014 18:58 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 2176C1A010F for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 11:58:08 -0700 (PDT)
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 LCqhZpCkFk3z for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 11:58:06 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA621A0393 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 11:58:06 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 8F4EACC085 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 14:58:05 -0400 (EDT)
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 ESijAQ7Pr+G0 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 14:58:00 -0400 (EDT)
Received: from new-host.home (pool-96-237-159-213.bstnma.fios.verizon.net [96.237.159.213]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7F6EACC081 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 14:58:00 -0400 (EDT)
Message-ID: <544D4437.7080108@meetinghouse.net>
Date: Sun, 26 Oct 2014 14:57:59 -0400
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" <ianaplan@ietf.org>
References: <E74C02CC-8A35-4057-95E4-14925B332456@cooperw.in> <544B44BD.7030805@cisco.com> <734aafb2601d4c7f9fa3184daa6dddb1@EX13-MBX-13.ad.syr.edu> <544D3DC3.5000409@cisco.com>
In-Reply-To: <544D3DC3.5000409@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/JtZBS52-M3xFNUAk-b_GW1x2iGc
Subject: Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-response-01
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: Sun, 26 Oct 2014 18:58:08 -0000
Eliot Lear wrote: > > On 10/26/14, 5:38 PM, Milton L Mueller wrote: >> >> "To address concerns regarding appropriate contingencies to >> transition to another operator, IAOC is asked to conclude a >> supplemental agreement that- 1. captures provisions C.7.3 and >> I.61 of the current IANA functions contract between ICANN and the >> NTIA [NTIA-Contract >> <http://tools.ietf.org/html/draft-ietf-ianaplan-icg-response-01#ref-NTIA-Contract>]; >> and" >> >> Similar to my comment above, I think this should align with the >> other bits about the IAOC, i.e., >> >> "To address concerns regarding appropriate contingencies to >> transition to another operator, the IAOC is asked to engage with >> the IANA functions operator regarding: 1. maintaining the IANA >> functions operator's obligations established under provisions >> C.7.3 and I.61 of the current IANA functions contract between >> ICANN and the NTIA [NTIA-Contract >> <http://tools.ietf.org/html/draft-ietf-ianaplan-icg-response-01#ref-NTIA-Contract>]; >> and >> >> >> I have no problem with the wording change above. >> >> I do. Replacing conclude a supplemental agreement with engage >> with the IANA functions operator regarding replaces very specific >> wording and requirements with very vague and noncommital stuff. I >> dont know what it means to engage with. I dont know what the >> outcome of such an engagement would be. >> >> A compromise version of this wording might read: >> >> To address concerns regarding appropriate contingencies to >> transition to another operator, IAOC is asked to conclude a >> supplemental agreement that 1. Maintains the IANA functions >> operator's obligations established under provisions C.7.3 and I.61 of >> the current IANA functions contract between ICANN and the NTIA >> [NTIA-Contract >> <http://tools.ietf.org/html/draft-ietf-ianaplan-icg-response-01#ref-NTIA-Contract>]; >> and >> >> > > This is what will be in the next version (I had not made the edit). I > missed the Alissa's proposed edit, as it happens (not sure how I > missed it), and apologize for confusion. The issue for me here is > precisely what you describe. However, I would be open to changes to > this text if they can be made in such a way that maintains our > interests with additional flexibility. I believe that would also > address a comment from Jon Peterson. I just don't have the right > wording to do that. > I would also urge more specific and binding language, rather than vague language. Let's make sure this is done before the NTIA contract goes away. Also, note that, as far as the process is concerned - IAOC and IETF are the same entity (IAOC is the entity that reflects IETF when it comes to contracts). Language like "the IAOC is asked" is cumbersome, since for legal and contractual purposes, that's the IETF asking the IETF to do something. It's more accurate to say that "the IETF proposes that, before a transition occurs, that supplemental agreements be put in place.... with the IOAC acting as the legal and contracting representative of the IETF." Something I've said before, that bears repetition: The final IETF proposal should include IAB, IAOC, considerations, as well those of any other entities that are part of IETF from view of the outside world. How to coordinate that is an open question - clearly that goes beyond the scope of the WG charter. Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra
- [Ianaplan] Review of draft-ietf-ianaplan-icg-resp… Alissa Cooper
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Richard Hill
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Eliot Lear
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Richard Hill
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Eliot Lear
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Eliot Lear
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Milton L Mueller
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Eliot Lear
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Miles Fidelman
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Richard Hill
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Eliot Lear
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Andrei Robachevsky
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Brian E Carpenter
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Miles Fidelman
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… JFC Morfin
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… John Curran
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… Jefsey
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… John Curran
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… JFC Morfin
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… John Curran
- Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-… JFC Morfin