Re: A Splendid Example Of A Renumbering Disaster

David Conrad <drc@virtualized.org> Sat, 24 November 2012 02:54 UTC

Return-Path: <drc@virtualized.org>
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 98C3421F8605 for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 18:54:37 -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 XgPHm6UIP5P9 for <ietf@ietfa.amsl.com>; Fri, 23 Nov 2012 18:54:37 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id F07FD21F8604 for <ietf@ietf.org>; Fri, 23 Nov 2012 18:54:36 -0800 (PST)
Received: from [10.0.1.2] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 3B64417066; Sat, 24 Nov 2012 02:54:35 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: A Splendid Example Of A Renumbering Disaster
From: David Conrad <drc@virtualized.org>
In-Reply-To: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
Date: Fri, 23 Nov 2012 18:54:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2ABE8946-A59E-4E15-987C-EC0A45949934@virtualized.org>
References: <54E43A43-A9F3-4803-BAB9-B06F4EB0CB19@me.com>
To: Sabahattin Gucukoglu <listsebby@me.com>
X-Mailer: Apple Mail (2.1499)
Cc: 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: Sat, 24 Nov 2012 02:54:37 -0000

On Nov 23, 2012, at 5:46 PM, Sabahattin Gucukoglu <listsebby@me.com> wrote:
> It's Friday.  Time to plug IPv6 some more. :-)
> 
> http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/
> 
> LogMeIn Hamachi is basically a NAT-traversing layer 2 VPN solution.  They avoided conflicts with RFC 1918 space by hijacking IPv4 space in 5/8,

Back when I was running IANA and we noticed this (back in 2006 or so -- don't remember the exact dates), we suggested to the folks at Hamachi that using squat space was perhaps not the best idea.  They floated the idea of a /8 dedicated to VPNs, but it didn't go anywhere (we at IANA told them to bring it up with the IETF -- not sure if they ever did).  

> now actively being allocated by LIRs in Europe.  When that didn't work (see link above), they moved to 25/8, allocated to the UK MoD.  

Sigh.  You would think that after a number of years they could've come up with a better solution than to use different squat space. Given 25/8 is 'legacy' space, unencumbered by registration service agreements, I suspect folks using Hamachi for v4 VPNs will get another unpleasant surprise in the future.

Regards,
-drc