IETF Logo Mail Archive

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

Owen DeLong <owen@delong.com> Sat, 01 June 2013 04:38 UTC

Return-Path: <owen@delong.com>
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 2094821F8E37 for <v6ops@ietfa.amsl.com>; Fri, 31 May 2013 21:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level:
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599]
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 Eb5FyC1Jp98A for <v6ops@ietfa.amsl.com>; Fri, 31 May 2013 21:38:20 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id D5BB921F8DE4 for <v6ops@ietf.org>; Fri, 31 May 2013 21:38:19 -0700 (PDT)
Received: from [192.168.6.83] (ip-64-134-24-48.public.wayport.net [64.134.24.48]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r514X4N1010836 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 31 May 2013 21:33:49 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r514X4N1010836
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1370061231; bh=lqwY4li2TZ39Htb0Y4mJnZyWh1o=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=OjAtSDrsLGkZpDEfQ1/ZM1eedOsf9GNCs1g4+QGbbzPbb/DLabGFVU9pDrBFcNyTY +q6H6OKzpJfsILBNC9USSwG/7qwfGTj8D059N6IX9wSatDziJfWJMl15AERoS4y9/j OlpL2hjErBJGu6kEXOq/jU64ncsJv6Ktfx10LsbA=
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <51A97918.9070404@massar.ch>
Date: Fri, 31 May 2013 21:33:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <90D50EC6-D510-4A3B-B33A-32135462A233@delong.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> <51A97375.1090402@gmail.com> <51A97918.9070404@massar.ch>
To: Jeroen Massar <jeroen@massar.ch>
X-Mailer: Apple Mail (2.1503)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Fri, 31 May 2013 21:33:51 -0700 (PDT)
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 04:38:22 -0000

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.

Owen

v2.23.0 | Report a Bug | By Email