IETF Logo Mail Archive

Re: [Ianaplan] What are the RIRs doing?

Eric Burger <eburger@standardstrack.com> Tue, 09 September 2014 10:03 UTC

Return-Path: <eburger@standardstrack.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 0535A1A0421 for <ianaplan@ietfa.amsl.com>; Tue, 9 Sep 2014 03:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level:
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
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 QZrftVHxarvK for <ianaplan@ietfa.amsl.com>; Tue, 9 Sep 2014 03:03:00 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.246.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 966351A030A for <ianaplan@ietf.org>; Tue, 9 Sep 2014 03:03:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=vRrFf/hbvgZW/jbw6fFZkoEGB9UCG08Kmra0FWConXc=; b=TDBD6yMGxspaHs9MQsjLXY4/1QRjWaY1PgLucXsfNkQwtEIwXvSE08oYvutEI9dGFvQtCrLU9WT/YCrQ8IMNSn9qDzT4J7oyxcBuheXFqq9SZxcPViSd3A6/HDLOJAcehF3hQ8RBLN3cuRYhlG884lajumVZix7mjHpg6sgUFJI=;
Received: from ip68-100-74-115.dc.dc.cox.net ([68.100.74.115]:51225 helo=[192.168.15.119]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <eburger@standardstrack.com>) id 1XR4cA-0000iV-SK; Mon, 08 Sep 2014 12:28:39 -0700
Content-Type: multipart/signed; boundary="Apple-Mail=_D51458B5-DBE7-434C-BC5C-447C6F506CF7"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <46cb2aaf81b4437aa3f570c794e603b7@EX13-MBX-13.ad.syr.edu>
Date: Mon, 08 Sep 2014 15:28:38 -0400
Message-Id: <E46D372E-CBE7-42B5-84BF-F1FE198394C0@standardstrack.com>
References: <540DB003.1060900@cisco.com> <a9927883f15b4da7aa03735b5efeae10@EX13-MBX-13.ad.syr.edu> <20140908190223.GM74274@mx1.yitter.info> <46cb2aaf81b4437aa3f570c794e603b7@EX13-MBX-13.ad.syr.edu>
To: Milton L Mueller <mueller@syr.edu>
X-Mailer: Apple Mail (2.1878.6)
X-OutGoing-Spam-Status: No, score=
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/MCQwCrw5wYKVoev8zG2U7WuviGo
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, "NCSG-DISCUSS@LISTSERV.SYR.EDU" <NCSG-DISCUSS@LISTSERV.SYR.EDU>
Subject: Re: [Ianaplan] What are the RIRs doing?
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, 09 Sep 2014 10:03:02 -0000

You have captured it in one:

On Sep 8, 2014, at 3:19 PM, Milton L Mueller <mueller@syr.edu> wrote:
> ICANN tried that at first with the preparations for the ICG, proposing a skewed process and a prejudiced scoping document. It was laughed out of town, and quickly corrected itself. Let's hope the RIRs and IETF have the same good sense. 

I am not worried.

v2.23.0 | Report a Bug | By Email