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

Eliot Lear <lear@cisco.com> Sat, 25 October 2014 10:47 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 959121A8779 for <ianaplan@ietfa.amsl.com>; Sat, 25 Oct 2014 03:47:33 -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 I5Hy5z-58Nmg for <ianaplan@ietfa.amsl.com>; Sat, 25 Oct 2014 03:47:32 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2AC71A8778 for <ianaplan@ietf.org>; Sat, 25 Oct 2014 03:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5441; q=dns/txt; s=iport; t=1414234052; x=1415443652; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=7LTRgQKzvUnZ5yGJCyyIsxxEAQWh/qxlJ+1p8Qjhf2g=; b=O1gLK9CEHBkDhYEmaYjaDSzUE8zq+ZH74fqbRy8792ioLp8Lai9qG+Cg LIqeXtq/NHuh0cn16BAUP1v/OYgu/qilZsfC+3PZkFv1X8fr5wFSPWOU+ 9MMkjt5/Mn+4Z5WsLdKexXgcexJXvfZvLvYcPPu3ldGVwR49vZ7W/+qBM M=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQEAL1+S1StJssW/2dsb2JhbABch0DOaIMgAoEeAX2EAwEBBCNVEQkCBBQJFgsCAgkDAgECAUUGAQwIAQEQiC2XbZxflGEBAQEBAQEBAQIBAQEBAQEBARqQX4J3gVQBBJQTgVCHeodsjkCDejuCegEBAQ
X-IronPort-AV: E=Sophos;i="5.04,786,1406592000"; d="asc'?scan'208,217";a="223758582"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 25 Oct 2014 10:47:29 +0000
Received: from [10.61.108.74] (dhcp-10-61-108-74.cisco.com [10.61.108.74]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s9PAlTJG022668; Sat, 25 Oct 2014 10:47:29 GMT
Message-ID: <544B7FC9.4030808@cisco.com>
Date: Sat, 25 Oct 2014 12:47:37 +0200
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: rhill@hill-a.ch, Alissa Cooper <alissa@cooperw.in>, ianaplan@ietf.org
References: <GLEAIDJPBJDOLEICCGMNIEBCCNAA.rhill@hill-a.ch>
In-Reply-To: <GLEAIDJPBJDOLEICCGMNIEBCCNAA.rhill@hill-a.ch>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="7dR1OCb9bJDsSB6pD8h9kaDHbQpnU2blH"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/1mmpzLTUpJQ4Hmcl9lYk9UBTQPI
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: Sat, 25 Oct 2014 10:47:33 -0000

Hi Richard,

On 10/25/14, 12:27 PM, Richard Hill wrote:
> Many thanks to both Alissa and Eliot for this.
>  
> I largely (not not entirely) agree with Alissa's comments, and I
> almost entirely  agree with Eliot's proposed dispostions.
>  
> Here is where I differ from what Eliot has proposed.
>
> Re "We will contintue to coordinate with ICANN regarding those
> changes", I would propose  "We will continue to coordinate with the
> IANA functions operator (at present ICANN) regarding those changes",
> or something along those lines.
>

Perhaps we need a different approach, if people feel strongly about that
particular phrase in this response, because in this context we are
talking about the DNS protocol, and that requires a lot of coordination
when we make changes, and perhaps it's not just with ICANN or the IANA
functions operator.  So...

I suggest then:

          The IETF specifies the DNS protocol.  From time to time
          there have been and will be updates to that protocol.    As we
          make changes we will broadly consult the operational
          community about the impact of those changes, as we have
          done in the past.

Eliot