IETF Logo Mail Archive

Re: [Ianaplan] I-D Action: draft-lear-iana-icg-response-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 08 September 2014 19:47 UTC

Return-Path: <brian.e.carpenter@gmail.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 DC8C41A036C for <ianaplan@ietfa.amsl.com>; Mon, 8 Sep 2014 12:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 m5pX66wwAk_e for <ianaplan@ietfa.amsl.com>; Mon, 8 Sep 2014 12:47:44 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6505F1A0368 for <ianaplan@ietf.org>; Mon, 8 Sep 2014 12:47:44 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id p10so4495916pdj.30 for <ianaplan@ietf.org>; Mon, 08 Sep 2014 12:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0UFE9GOicVls2coOdqjtsy6KR3iwbjQjvygpo/I5jnc=; b=J8XOoHTS6d9X/cWtuCm9RHyfMXZTfYm4KXHXcv++M2PywnlTKwW284mVgy36k7ZVf7 /YlMIWkoxrc+IqBBc2QukEYUjtvaZYfYfn25KnpdBKGS0f+IZmS6nRQiyzE3iJbugaeC Hs4AlQVfkmyHNYzPulXyRHbPTRSY7ndYOrUJkHbKUy/lblfdYF9vOCqO8RfHGdEGzGWu GJOhRw72CysNTVo+kvpUfjU2XWg7s7jUmQhtoHqwjCm7HdBbaxL7bGMkrdbBzc1TAwyA vHvQQ2u+xFYpK1ePFhdVp7rfNxTi7133z2vonSzbh0d4GWF0d1dkMj74rFwbXxLPn4g4 Btbg==
X-Received: by 10.68.98.194 with SMTP id ek2mr23604637pbb.103.1410205663946; Mon, 08 Sep 2014 12:47:43 -0700 (PDT)
Received: from [192.168.178.23] (21.196.69.111.dynamic.snap.net.nz. [111.69.196.21]) by mx.google.com with ESMTPSA id o2sm9760217pde.30.2014.09.08.12.47.42 for <ianaplan@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 12:47:43 -0700 (PDT)
Message-ID: <540E07E1.6090805@gmail.com>
Date: Tue, 09 Sep 2014 07:47:45 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ianaplan@ietf.org
References: <20140830063916.1613.19503.idtracker@ietfa.amsl.com> <540CC133.8070105@gmail.com>
In-Reply-To: <540CC133.8070105@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/30CUyPQsBZ0gBsrG8N9TUMAJMkU
Subject: Re: [Ianaplan] I-D Action: draft-lear-iana-icg-response-00.txt
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: Mon, 08 Sep 2014 19:47:47 -0000

One glitch in my comments has been brought to my attention:

On 08/09/2014 08:33, Brian E Carpenter wrote:
...
>>    o  The IETF has specified a number of special use registries.  These
>>       registries require coordination with the GNSO.  We already perform
>>       this coordination.

> Add: These include certain IP addresses reserved by the IETF for technical
> reasons.

They of course need to be coordinated with the ASO, not the GNSO.

...
> Now commenting on Russ's comment:
> 
>>        [[RH2]I think there are two areas of overlap:
>>
>>          Addresses: special-purpose addresses, such as anycast.  We need
>>          to set up procedures to coordinate assignments.
> 
> Why? These are discussed in IETF open process when they occur, where
> NRO and IANA people are welcome, so the coordination already happens.
> This should be documented as an ongoing procedure.

Again, that should be ASO.

   Brian

v2.23.0 | Report a Bug | By Email