Re: [Ianaplan] comments on draft-ietf-ianaplan-icg-response-01

Milton L Mueller <mueller@syr.edu> Fri, 24 October 2014 14:16 UTC

Return-Path: <mueller@syr.edu>
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 4E96C1A0161 for <ianaplan@ietfa.amsl.com>; Fri, 24 Oct 2014 07:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 FDBkclkzDcwV for <ianaplan@ietfa.amsl.com>; Fri, 24 Oct 2014 07:16:47 -0700 (PDT)
Received: from smtp1.syr.edu (smtp1.syr.edu [128.230.18.82]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF2481A016C for <ianaplan@ietf.org>; Fri, 24 Oct 2014 07:16:46 -0700 (PDT)
Received: from EX13-MBX-11.ad.syr.edu (ex13-mbx-11.ad.syr.edu [128.230.108.142]) by smtp1.syr.edu (8.14.7/8.14.7) with ESMTP id s9OEGi13028014 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 24 Oct 2014 10:16:45 -0400
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-11.ad.syr.edu (128.230.108.142) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 24 Oct 2014 10:16:38 -0400
Received: from EX13-MBX-13.ad.syr.edu ([128.230.108.144]) by EX13-MBX-13.ad.syr.edu ([128.230.108.144]) with mapi id 15.00.0847.030; Fri, 24 Oct 2014 10:16:38 -0400
From: Milton L Mueller <mueller@syr.edu>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "ianaplan@ietf.org" <ianaplan@ietf.org>
Thread-Topic: [Ianaplan] comments on draft-ietf-ianaplan-icg-response-01
Thread-Index: AQHP7wwQhg9hTf3Tz0SIrT3AqtZkQpw/ChMAgAALBoCAAGsqAP//yYIQ
Date: Fri, 24 Oct 2014 14:16:26 +0000
Message-ID: <b77c00e3d6fb4b4dbc874ecec28477b8@EX13-MBX-13.ad.syr.edu>
References: <5449EF98.70701@cisco.com> <GLEAIDJPBJDOLEICCGMNAEACCNAA.rhill@hill-a.ch> <20141024132307.GA2240@mx1.yitter.info>
In-Reply-To: <20141024132307.GA2240@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [184.153.243.196]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-10-24_04:2014-10-24,2014-10-24,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1410240120
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/69ou8NFyRvHM0GRMXuT16ACAXBE
Subject: Re: [Ianaplan] comments on 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: Fri, 24 Oct 2014 14:16:49 -0000


> -----Original Message-----
> 
> I think that's completely off-topic for this, and it's also clearly outside our
> charter since it would be a major change to the existing arrangements and
> our charter tells us not to do that: "This working group is chartered solely
> with respect to the planning needed for the transition, and is not meant to
> cover other topics related to IANA. Possible improvements outside that scope
> will be set aside for future consideration."  The recommendation of
> jurisdiction in the first proposal also seems to me to be in violation of that
> term.

While I don't necessarily agree with Richard's recommendation of Swiss jurisdiction, I think the jurisdiction in which IANA resides or might be incorporated is very much in scope as part of the transition. The RFP specifically asks for that, and generally it's a bad idea for people to try to rule out ideas they don't like by claiming that they are out of scope. Let's debate the merits, not foreclose.