Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-response-01

Eliot Lear <lear@cisco.com> Sun, 26 October 2014 18:30 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 6B7CC1A037F for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 11:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 DcmKkhWwpoox for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 11:30:20 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD8D71A037C for <ianaplan@ietf.org>; Sun, 26 Oct 2014 11:30:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11450; q=dns/txt; s=iport; t=1414348220; x=1415557820; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=2CJ2lHfo5xld//RkjsgaQzjY6K4tCC7u/PmvQFihtW0=; b=K2zYR1BpuGDz2TH+pVDy4pBG8Vant6kXJeGy5CrQzfmFaefSVfEKI9Tw /wOuoodfTantMnRGFzalzfGagTiPs1HQ9gLH3NqBrz1Wn8bh5uFH07n70 HrprV6U0ozNoJtOsZ3RqUL8lCkiLNchQaSi/iGaEgszsDD4vx8oOik9p7 I=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqgEAIM8TVStJssW/2dsb2JhbABcDoI6gRpZgwXJcYdLAoEcAX2EAwEBBCMKSxEJAhgJFgsCAgkDAgECAUUGAQwIAQGIPQ2WcJxfk30BAQEBAQEBAQEBAQEBAQEBAQEBAQEXkQ+Cd4FUAQSGYY02gVBohxKBMTyFfzuOB4M4QTyCegEBAQ
X-IronPort-AV: E=Sophos;i="5.04,791,1406592000"; d="asc'?scan'208,217";a="221379486"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 26 Oct 2014 18:30:17 +0000
Received: from [10.61.108.74] (dhcp-10-61-108-74.cisco.com [10.61.108.74]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9QIUGKP017425; Sun, 26 Oct 2014 18:30:16 GMT
Message-ID: <544D3DC3.5000409@cisco.com>
Date: Sun, 26 Oct 2014 19:30:27 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Milton L Mueller <mueller@syr.edu>, Alissa Cooper <alissa@cooperw.in>, "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>
In-Reply-To: <734aafb2601d4c7f9fa3184daa6dddb1@EX13-MBX-13.ad.syr.edu>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="Nm7XaK70UjJnSwuNaEpFIbKlabbwVaH0d"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/yNddXLSmImMU_aQsK0IOuJh19P0
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:30:22 -0000

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
> don’t know what it means to “engage with.” I don’t 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.

Eliot