IETF Logo Mail Archive

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

Brian Haberman <brian@innovationslab.net> Mon, 03 June 2013 12:33 UTC

Return-Path: <brian@innovationslab.net>
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 B357821F96EC for <v6ops@ietfa.amsl.com>; Mon, 3 Jun 2013 05:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 TbzE7XMIDaqL for <v6ops@ietfa.amsl.com>; Mon, 3 Jun 2013 05:33:37 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7662121F969F for <v6ops@ietf.org>; Mon, 3 Jun 2013 05:33:37 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 22D3888112 for <v6ops@ietf.org>; Mon, 3 Jun 2013 05:33:37 -0700 (PDT)
Received: from clemson.local (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id E25B414000C for <v6ops@ietf.org>; Mon, 3 Jun 2013 05:33:36 -0700 (PDT)
Message-ID: <51AC8D23.3070702@innovationslab.net>
Date: Mon, 03 Jun 2013 08:33:39 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: v6ops@ietf.org
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> <51A97375.1090402@gmail.com> <51A97918.9070404@massar.ch> <90D50EC6-D510-4A3B-B33A-32135462A233@delong.com>
In-Reply-To: <90D50EC6-D510-4A3B-B33A-32135462A233@delong.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Mon, 03 Jun 2013 12:33:42 -0000

On 6/1/13 12:33 AM, Owen DeLong wrote:
>
> On May 31, 2013, at 9:31 PM, Jeroen Massar <jeroen@massar.ch> wrote:
>
>> On 2013-05-31 21:07, Brian E Carpenter wrote:
>> [..]
>>> Agreed. But when it does get through, it does no particular
>>> harm (you just see a bizarre hop in the traceroute). If it got
>>> through in a SYN/ACK exchange, it would probably distress a user.
>>
>> If such a packet gets through it means BCP38 is not applied as things
>> are not properly filtered.
>>
>
> This has nothing to do with BCP38.
>
> Any router which forwards a packet containing a link local address in the header is broken regardless of any BCP38 configuration.
>

The IPv6 Scoped Addressing Architecture covers this for less-than-global 
scoped addresses...

https://tools.ietf.org/html/rfc4007#section-9

Regards,
Brian

v2.23.0 | Report a Bug | By Email