IETF Logo Mail Archive

Re: A Splendid Example Of A Renumbering Disaster

Paul Wouters <paul@nohats.ca> Mon, 26 November 2012 17:34 UTC

Return-Path: <paul@nohats.ca>
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 970D621F85EE for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:34:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KiCQ1f0UuPhc for <ietf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:34:39 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3818421F86C6 for <ietf@ietf.org>; Mon, 26 Nov 2012 09:34:38 -0800 (PST)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 7EDA682B73; Mon, 26 Nov 2012 12:33:51 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 733F1803FD; Mon, 26 Nov 2012 12:33:51 -0500 (EST)
Date: Mon, 26 Nov 2012 12:33:51 -0500
From: Paul Wouters <paul@nohats.ca>
To: Benson Schliesser <bensons@queuefull.net>
Subject: Re: A Splendid Example Of A Renumbering Disaster
In-Reply-To: <50B3A30A.3000201@queuefull.net>
Message-ID: <alpine.LFD.2.02.1211261231160.7313@bofh.nohats.ca>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com> <alpine.LFD.2.02.1211241129320.2810@bofh.nohats.ca> <CAA=duU3cuFPhii9d4Gab74N_cxzPALZP0K1ENVsyfrj7P+2AdA@mail.gmail.com> <50B3A30A.3000201@queuefull.net>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-Mailman-Approved-At: Tue, 27 Nov 2012 08:48:05 -0800
Cc: IETF Discussion <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: Mon, 26 Nov 2012 17:34:39 -0000

On Mon, 26 Nov 2012, Benson Schliesser wrote:

> I expect to be flamed for suggesting it, but why not use the Shared Address Space for this purpose?
> (http://tools.ietf.org/html/rfc6598)

You can't, if carriers are assigning you that IP range. You'd still get
a conflict if you use it for your own VPN range, as the inner address
cannot be in the same subnet as the outer address (whether in tunnel
mode, or when using transport mode with L2TP)

Paul

v2.23.0 | Report a Bug | By Email