Re: [v6ops] Thoughts on draft-byrne-v6ops-clatip-01

joel jaeggli <joelja@bogus.com> Thu, 01 May 2014 22:52 UTC

Return-Path: <joelja@bogus.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 11E931A8026 for <v6ops@ietfa.amsl.com>; Thu, 1 May 2014 15:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level:
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NORMAL_HTTP_TO_IP=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 7t5Lhmoh7p-7 for <v6ops@ietfa.amsl.com>; Thu, 1 May 2014 15:51:59 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3531A09B8 for <v6ops@ietf.org>; Thu, 1 May 2014 15:51:59 -0700 (PDT)
Received: from mb-aye.local (c-67-188-0-113.hsd1.ca.comcast.net [67.188.0.113]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s41MpkZp020172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 1 May 2014 22:51:46 GMT (envelope-from joelja@bogus.com)
Message-ID: <5362CFFC.2040609@bogus.com>
Date: Thu, 01 May 2014 15:51:40 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Thunderbird/29.0
MIME-Version: 1.0
To: Owen DeLong <owen@delong.com>
References: <DA7557DA-C003-4FAC-A1C5-2FAD5BD028EC@cisco.com> <CAKD1Yr3JA8jKjfk1BMA4dfMQ8CQ5L5V5txnEmXPLjE=CnOR9VQ@mail.gmail.com> <40C41DA9-3513-4BC3-B6C9-7A1EEF98BBC7@cisco.com> <CAKD1Yr2AZN7+czefosQG9uaJ0dDLmtrAp7+QHKOP+Kpk+rBvcA@mail.gmail.com> <5361DBFA.3010403@bogus.com> <B6D62ADF-63DF-41CE-92F2-361E3120CFB5@delong.com>
In-Reply-To: <B6D62ADF-63DF-41CE-92F2-361E3120CFB5@delong.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="GkGombuktf3bBVaR4QLPNgFN5RdveU3Da"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Thu, 01 May 2014 22:51:48 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/oF7y6y1VPjGilULN5PT9m_lst7U
Cc: V6 Ops List <v6ops@ietf.org>, "Byrne, Cameron" <Cameron.Byrne@t-mobile.com>
Subject: Re: [v6ops] Thoughts on draft-byrne-v6ops-clatip-01
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, 01 May 2014 22:52:01 -0000

On 5/1/14, 3:31 PM, Owen DeLong wrote:
> 
> On Apr 30, 2014, at 10:30 PM, joel jaeggli <joelja@bogus.com> wrote:
> 
>> On 4/30/14, 7:55 PM, Lorenzo Colitti wrote:
>>> On Thu, May 1, 2014 at 8:24 AM, Fred Baker (fred) <fred@cisco.com
>>> <mailto:fred@cisco.com>> wrote:
>>>
>>>   Ask me someday what thoughts go through my mind about applications
>>>   making inferences from network layer addresses.
>>>
>>>
>>> The wording in RFC 3927 is much stronger. For example, it states
>>> multiple times that packets sourced from 169.254/16 MUST NOT be
>>> forwarded, and that they MUST NOT ever be sent to any router for
>>> forwarding. I think it's perfectly reasonable for an app (or even an
>>> OS!) to assume that such addresses have no connectivity.
>>>
>>>
>>>   Hey, 192.168.0.0/16 <http://192.168.0.0/16>is for networks that
>>>   don’t connect to the Internet. You want proof? From RFC 1918, the
>>>   motivation is
>>>
>>>      With the proliferation of TCP/IP technology worldwide, including
>>>      outside the Internet itself, an increasing number of non-connected
>>>      enterprises use this technology and its addressing capabilities for
>>>      sole intra-enterprise communications, without any intention to ever
>>>      directly connect to other enterprises or the Internet itself.
>>>
>>>
>>> Funny, that's what the proponents of ULA-only networks say too - "no,
>>> this network will NEVER connect to the Internet, ever!!11" I suspect
>>> they do so because they know that saying "we want to use NAT to connect
>>> this network to the Internet like we do in IPv4" is going to result in
>>> strong opinions and removal of support for the use case. But that's
>>> off-topic here.
>>
>> site-local unicast in ipv6  and rfc 1918 are relatively contemporaneous
>> ideas...
>>
>> I don't thing the pressures that produce such solutions are particularly
>> new in fact it's pretty easy to assert that they co-evolved.
> 
> Yes, but unlike RFC-1918, we came to our senses and deprecated site-local.
>
> ULA came later as a result of pressure from people who loved their NAT. Sad, really, that the problem was not addressed through education instead of better RIR policies for global unicast.

fec0::/10 was reserved way back in rfc 1884

3879 and 4193 are contemporaneous activities. meany people on this list
were present for them.

The fact that we did a bad job at something 20 years ago doesn't mean
the problem that we were attempting to address went away.

> Owen
> 
>