Re: [Ianaplan] A draft for your review

John Curran <> Sun, 02 November 2014 01:34 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9F9641A3B9C for <>; Sat, 1 Nov 2014 18:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R_1c9-STbUuR for <>; Sat, 1 Nov 2014 18:34:13 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2366F1A2130 for <>; Sat, 1 Nov 2014 18:34:12 -0700 (PDT)
Received: from [] (helo=[]) by with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <>) id 1Xkk3Y-0003jI-5X; Sun, 02 Nov 2014 01:34:12 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: (see for abuse reporting information)
X-MHO-User: U2FsdGVkX19IvSUIRBnQOZ1dIe0Ce8sM
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: John Curran <>
In-Reply-To: <>
Date: Sun, 02 Nov 2014 01:34:08 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
To: Brian E Carpenter <>
X-Mailer: Apple Mail (2.1990.1)
Subject: Re: [Ianaplan] A draft for your review
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 02 Nov 2014 01:34:14 -0000

On Nov 1, 2014, at 7:42 PM, Brian E Carpenter <> wrote:
> ...
> Trying to go up a level, what I see here is a very senior member of
> our wider community (that would be Mr Conrad) telling us of at least
> two cases (the recent RFC 6761, and the ancient blunder of IPv6
> Top Level Aggregation, RFC 2374) where he feels that the IETF side of
> the house did not in practice consult adequately with the registry or
> operators sides of the house. And if he feels that, then it's true
> by definition: we didn't consult enough, period.

I actually think we have been doing a pretty good job of policy 
coordination when it comes IETF and the Internet numbers registries.
There have been lots of small issues that have arisen over the years 
(special purpose addresses, documentation prefixes, transition blocks) 
all of which have been worked out, and often with specific coordination
efforts, i.e. folks from both communities attending others meetings.
While the initial IPv6 address format could have benefited by having
more operator input incorporated, that lack can probably be claimed
for most aspects of IP next generation design process (as opposed to 
being the result of any lack of coordination among policy bodies.)

I do think it is worth documenting the need for good coordination 
between the IETF and delegated registries, predominantly because 
the RFP does specifically ask about independencies and good policy 
coordination keeps the IANA operator(s) an administrative function
rather than becoming an arbitration role.


Disclaimer: my views alone.