Re: [v6ops] (re)numbering [ULA draft revision #2 Regarding isolated networks]

Matthew Petach <mpetach@netflight.com> Thu, 29 May 2014 11:18 UTC

Return-Path: <mpetach@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 080161A088D for <v6ops@ietfa.amsl.com>; Thu, 29 May 2014 04:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 MOskMBKaeeO3 for <v6ops@ietfa.amsl.com>; Thu, 29 May 2014 04:18:11 -0700 (PDT)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09F251A009E for <v6ops@ietf.org>; Thu, 29 May 2014 04:18:10 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id db12so189550veb.11 for <v6ops@ietf.org>; Thu, 29 May 2014 04:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HyIyhQlIoRmlMW+6afaOqPtuOZWnvpaBA9UoVkKtTTc=; b=P1Pgn49AHRSVfa8nhzxNropLUA2FzklOecJ2Vs5FSJtY8AZTu7FXS/0daDwKYYesAj MiF22QEMD5s/7d/ACmWpY2rVWj83qRFKffuzb4jhANVFA6lcpboev9dvs6Exrpxy6mac hYy3hLpT5Tta1G8ONu4KswgVyVXiLpg9ejf+3GhUIiygBE0n4LxqzwO4g+WDRKK8tFYC CJk2l0y7WeCVs19wzf4ZsQ9CQUFuY8HMAI0wgVbGNMQgEpGgyZsgEYmt/QMmb98BV7Hv bOpHdkr2Ml0ALJE9Dqs7tRPOQW8nYKO0y79nS/rCYpP+UDXUX4p6RoMud+Ev2e8/fjnt eZSg==
MIME-Version: 1.0
X-Received: by 10.58.243.198 with SMTP id xa6mr70359vec.65.1401362286611; Thu, 29 May 2014 04:18:06 -0700 (PDT)
Sender: mpetach@gmail.com
Received: by 10.220.173.193 with HTTP; Thu, 29 May 2014 04:18:06 -0700 (PDT)
In-Reply-To: <1401312298.99614.YahooMailNeo@web162205.mail.bf1.yahoo.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6B9A@nkgeml506-mbx.china.huawei.com> <1401141423.52956.YahooMailNeo@web162206.mail.bf1.yahoo.com> <5383C2CF.6040205@gmail.com> <1401230263.69077.YahooMailNeo@web162206.mail.bf1.yahoo.com> <53854B03.8040702@gmail.com> <1401312298.99614.YahooMailNeo@web162205.mail.bf1.yahoo.com>
Date: Thu, 29 May 2014 04:18:06 -0700
X-Google-Sender-Auth: t4jZx0tYb49sVocOzN73Dnsipf0
Message-ID: <CAEmG1=rz=o3adK5a7M5DOFGVa1GnjKxj3bNRq6896nBQGLOTVQ@mail.gmail.com>
From: Matthew Petach <mpetach@netflight.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Content-Type: multipart/alternative; boundary="047d7b6dc3e44b95fb04fa8815cb"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/edgOT7ql4yoYgLm_p5vJXDQNPcQ
Cc: v6ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] (re)numbering [ULA draft revision #2 Regarding isolated networks]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 May 2014 11:18:12 -0000

On Wed, May 28, 2014 at 2:24 PM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
wrote:
[...]

> RFC1918s have provided that internal connectivity robustness to both home
> networks and enterprise networks. Of course the drawback is that in IPv4 it
> is binary - hosts either have RFC1918s or public addresses, so if you have
> RFC1918s you have to use NAT to access external destinations on the
> Internet.
>

Wow...that's news to me.

For a decade now, I've been using
RFC1918 addresses+global addresses
in IPv4 on my home network; each
host has an address from each subnet,
and uses the 1918 addresses to reach
internal-only devices (printers, terminal
servers, etc.) which only have RFC1918
addresses, and use the globally routed
IPs for reaching non-local destinations.

I'm not sure I'd agree with your characterization
that IPv4 is different from IPv6 in that regards;
there's nothing in the IPv4 world that prevents
hosts from having multiple addresses, and
making use of them.

It's definitely a plus to have internal connectivity
stay working regardless of external connectivity,
I completely agree with you on that.

Matt