Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP

John C Klensin <john-ietf@jck.com> Fri, 10 February 2012 19:30 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F73521F8796 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 11:30:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.704
X-Spam-Level:
X-Spam-Status: No, score=-102.704 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XaQVWhdjyDu for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 11:30:02 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EF23221F881A for <ietf@ietf.org>; Fri, 10 Feb 2012 11:29:58 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Rvw6D-0003Jf-Ji; Fri, 10 Feb 2012 14:25:37 -0500
Date: Fri, 10 Feb 2012 14:29:24 -0500
From: John C Klensin <john-ietf@jck.com>
To: Chris Grundemann <cgrundemann@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <CA9CD08984777E1019A5A1BF@PST.JCK.COM>
In-Reply-To: <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 19:30:03 -0000

--On Friday, February 10, 2012 11:22 -0700 Chris Grundemann
<cgrundemann@gmail.com> wrote:

> On Fri, Feb 10, 2012 at 11:15, John C Klensin
> <john-ietf@jck.com> wrote:
> 
>> To follow up on an earlier comment, the rate at which ARIN (or
>> other RIRs) are running out of /10s (or /8s) is probably
>> irrelevant, as are hypotheses about what ARIN staff might do
>> about requests for allocation for CGN use with or without this
>> policy/ block.
>...

> This is not about IPv4 life-support. This is about providing
> the best answer to a difficult problem. Run-out date is not
> nearly as important as efficient use at this point. It is not
> efficient for multiple ISPs to use different space when a
> shared space will function optimally.

Indeed, although I note that it isn't a huge step from the above
to get to "we could really make _much_ more efficient use of
IPv4 space by partitioning the Internet into regions and using
explicit routing or X.75-like gateways to route traffic between
regions, thereby permitting each region to use almost all of the
IPv4 space".  One could even use CGNs to establish that model
with each ISP using almost the entire IPv4 space inside its
castle walls.    Now, I think either of those would be terrible
ideas but, as you and others are probably aware, people who
believe themselves to be serious and competent have proposed
them, almost exactly  

Anything that moves us closer to those models gives me visions
of slippery steep cliffs and the creeps, so I feel a need to be
careful about efficiency arguments too.   YMMD, either because
you see the efficiency arguments differently, because you have
reason to be less afraid of an ultimate "islands connected by
gateways" outcome, or for other reasons.

>> If that difference is less than years, I, personally, don't
>> think that particular argument is useful.   Other arguments
>> may be, but not that one.
> 
> Please see
> https://tools.ietf.org/html/draft-bdgks-arin-shared-transition
> -space for a more thorough analysis of the motivations, pros,
> cons, and alternatives for this shared CGN space. I think
> you'll find that those other arguments are laid out there.

I have and I agree those arguments are there (their interaction
with my fear of the scenarios above is another matter).  Again,
my main suggestion was that we just stop the discussions based
on allocation strategies or IPv4 exhaustion alone... because
they are distractions rather than helpful.

     john