Re: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working group last call

Eliot Lear <lear@cisco.com> Tue, 04 November 2014 18:21 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 AB0C41A1B26 for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 10:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level:
X-Spam-Status: No, score=-15.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, 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 TSBNALzD_kRd for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 10:20:52 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E7521A1A17 for <ianaplan@ietf.org>; Tue, 4 Nov 2014 10:20:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2095; q=dns/txt; s=iport; t=1415125254; x=1416334854; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=QqT0bm7bQKr0pJkuEBOawkgWDMIc/74GcMb04bNpMks=; b=C/DAcBMxb6oLxorHEf3/zYpukVLntvwx78kFkWMSL4AxPPPWFbwrbKEm tRZf6kgjNVI+hWrfENsybhQsmKFVE/hcyKpreJUlKlbxnVPagIrA+bI15 xcEW095vHXf8ihih3bqLzmv1qU5d5QvnB6YkiDvQAb0dlT14OoFHYw4yj s=;
X-Files: signature.asc : 486
X-IronPort-AV: E=Sophos;i="5.07,314,1413244800"; d="asc'?scan'208";a="230840652"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 04 Nov 2014 18:20:50 +0000
Received: from [171.68.20.226] (dhcp-171-68-20-226.cisco.com [171.68.20.226]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id sA4IKktd022922; Tue, 4 Nov 2014 18:20:47 GMT
Message-ID: <545918F8.40200@cisco.com>
Date: Tue, 04 Nov 2014 10:20:40 -0800
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: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "ianaplan@ietf.org" <ianaplan@ietf.org>
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca> <FC8732DC-BB60-45A2-BF30-0B085CA5FEB9@cooperw.in> <5454B8DE.8040308@cs.tcd.ie> <E5F99046-6C9D-4170-B408-9CA9B7CD6476@gmail.com> <D07CEABF.1357FC%jon.peterson@neustar.biz> <40696145-F2EA-428B-911D-60AD5988BE43@cisco.com>
In-Reply-To: <40696145-F2EA-428B-911D-60AD5988BE43@cisco.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="bXENOaGjUFi4wi5dkmSSQPMpC7b9kvnAw"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/UgEP1QeWcqczbBzYB5TsuUDnPmY
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, Bernard Aboba <bernard.aboba@gmail.com>, Alissa Cooper <alissa@cooperw.in>, Jon Peterson <jon.peterson@neustar.biz>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Ianaplan] 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: Tue, 04 Nov 2014 18:21:00 -0000

Just on this point.

On 11/4/14, 7:39 AM, Cullen Jennings (fluffy) wrote:
>
> Related to this, I find the phrase "IAOC is asked to conclude a supplemental agreement that ..." weird. Does this mean IAOC has to do this? or that IETF wishes that they try to get that? or what? I have no idea, but one thing I am sure about is that this draft is the wrong place and wrong time to change the relationship between IETF and IAOC. This should be phrased such that it is clear it is within in the normal existing relationship of the IETF and IAOC. 
>
>

We are not changing the relationship in the document.  The point is that
the IAOC is the arm of our organization that makes these sorts of
arrangements.  In this case matters are complicated by the fact that the
responsibility is shared, as per RFC 6220, with the IAB (amongst
others), and we are producing a response document that identifies needs
that should be addressed.  We could simply say that "A supplemental
agreement should be concluded that says," and leave as an inference that
it is in fact the IAOC, but a normal human being might not quite follow
that.

Eliot