Re: [v6ops] A good example of why we need to careful about ULAs

Jeroen Massar <jeroen@massar.ch> Sat, 01 June 2013 17:05 UTC

Return-Path: <jeroen@massar.ch>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A165E21F9DDA for <v6ops@ietfa.amsl.com>; Sat, 1 Jun 2013 10:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level:
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 g9TiySoui9Em for <v6ops@ietfa.amsl.com>; Sat, 1 Jun 2013 10:05:34 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id 4862421F9DD5 for <v6ops@ietf.org>; Sat, 1 Jun 2013 10:05:34 -0700 (PDT)
Received: from kami.ch.unfix.org (unknown [IPv6:2001:559:8000:c9:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 2F097801C2BA; Sat, 1 Jun 2013 19:05:29 +0200 (CEST)
Message-ID: <51AA29D7.8010901@massar.ch>
Date: Sat, 01 Jun 2013 10:05:27 -0700
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr29kf1Me=6JR66Gq0dFYgQx2wq=pjW8WZyHByPA0POsMQ@mail.gmail.com> <1369901467.70362.YahooMailNeo@web142506.mail.bf1.yahoo.com> <51A7C86B.3020808@gmail.com> <BCEC2341-CF91-4184-B14A-FE0BE683F89F@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BFE04@mbx-01.win.nominum.com> <4CB10EDC-1E2B-4423-AD77-7B6062F80579@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751C01BD@mbx-01.win.nominum.com> <D41922F4-CD88-4530-AD90-E985F1905CE3@employees.org> <2EFF47FB-D3E5-4020-9AB6-57201CA40888@steffann.nl> <8D23D4052ABE7A4490E77B1A012B6307751C0650@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751C0650@mbx-01.win.nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "<draft-ietf-v6ops-ula-usage-recommendations@tools.ietf.org>" <draft-ietf-v6ops-ula-usage-recommendations@tools.ietf.org>
Subject: Re: [v6ops] A good example of why we need to careful about ULAs
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 01 Jun 2013 17:05:39 -0000

On 2013-06-01 09:16, Ted Lemon wrote:
> On Jun 1, 2013, at 8:26 AM, Sander Steffann <sander@steffann.nl>
> wrote:
>>>> So you're arguing that every router on the internet needs a
>>>> global IP address?
>>> 
>>> Every node on the IPv6 internet needs a global IPv6 address.
>> 
>> +1
> 
> So I also +1 this, but if people are seeing traceroutes with ULAs in
> them, apparently _someone_ doesn't agree.

Nothing to do with disagreement, everything to do with not understanding
(nicely put) where ULA should be used and how.

Next to not understanding the concepts of BCP38/84.

Note that it seems that in this specific case the vendor actually
informed them that they could/should use a ULA there as it would never
leak to the Internet anyway..... thus can't even completely blame the
person who configured it, though I don't understand why one still then
would try and select ULA there when you have enough global space.

Greets,
 Jeroen