IETF Logo Mail Archive

RE: There are claims of ambiguity over what is a link-local address

Dave Thaler <dthaler@microsoft.com> Mon, 07 May 2012 17:32 UTC

Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1E3121F8694 for <ipv6@ietfa.amsl.com>; Mon, 7 May 2012 10:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.846
X-Spam-Level:
X-Spam-Status: No, score=-103.846 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 CSLpWX92IIS1 for <ipv6@ietfa.amsl.com>; Mon, 7 May 2012 10:32:44 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id DFE7E21F8690 for <ipv6@ietf.org>; Mon, 7 May 2012 10:32:43 -0700 (PDT)
Received: from mail29-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.23; Mon, 7 May 2012 17:32:30 +0000
Received: from mail29-va3 (localhost [127.0.0.1]) by mail29-va3-R.bigfish.com (Postfix) with ESMTP id 2412440021B; Mon, 7 May 2012 17:32:30 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC106.redmond.corp.microsoft.com; RD:none; EFVD:NLI
X-SpamScore: -35
X-BigFish: VS-35(zz9371I542M1432N98dKzz1202hzz1033IL8275dhz2fh2a8h668h839h944hd25h)
Received-SPF: pass (mail29-va3: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=dthaler@microsoft.com; helo=TK5EX14HUBC106.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail29-va3 (localhost.localdomain [127.0.0.1]) by mail29-va3 (MessageSwitch) id 1336411948157562_27459; Mon, 7 May 2012 17:32:28 +0000 (UTC)
Received: from VA3EHSMHS015.bigfish.com (unknown [10.7.14.245]) by mail29-va3.bigfish.com (Postfix) with ESMTP id 21E443C0046; Mon, 7 May 2012 17:32:28 +0000 (UTC)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.8) by VA3EHSMHS015.bigfish.com (10.7.99.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 7 May 2012 17:32:27 +0000
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) with Microsoft SMTP Server (TLS) id 14.2.298.5; Mon, 7 May 2012 17:32:25 +0000
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) with Microsoft SMTP Server (TLS) id 14.2.298.5; Mon, 7 May 2012 10:32:24 -0700
Received: from TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com ([169.254.5.160]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.02.0298.005; Mon, 7 May 2012 10:32:24 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Dan Luedtke <maildanrl@googlemail.com>, David Conrad <drc@virtualized.org>
Subject: RE: There are claims of ambiguity over what is a link-local address
Thread-Topic: There are claims of ambiguity over what is a link-local address
Thread-Index: AQHNK/QgGyZZTfkT90utwS/iqTPEg5a+WpwAgAAO+4CAAAunUIAAjGsAgAADo4CAAAOrgP//jVbg
Date: Mon, 07 May 2012 17:32:23 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B5B70D9@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <20120506235919.66E7B206E4F1@drugs.dv.isc.org> <4FA77236.30109@gmail.com> <4FA77EC7.6000406@gmail.com> <9B57C850BB53634CACEC56EF4853FF653B5B6560@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com> <C91E67751B1EFF41B857DE2FE1F68ABA0BC26723@tk5ex14mbxc272.redmond.corp.microsoft.com> <113B5F7B-646A-4012-9F10-A994BFE39E8B@virtualized.org> <CAAfuxnKZCUMX+8qP_9p_rbs4g193gwwf1TvR5S5yLieb408eQw@mail.gmail.com>
In-Reply-To: <CAAfuxnKZCUMX+8qP_9p_rbs4g193gwwf1TvR5S5yLieb408eQw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.43]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: Christian Huitema <huitema@microsoft.com>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 17:32:44 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Dan Luedtke
> Sent: Monday, May 07, 2012 10:21 AM
> To: David Conrad
> Cc: Christian Huitema; 6man
> Subject: Re: There are claims of ambiguity over what is a link-local address
> 
> Hi,
> 
> On Mon, May 7, 2012 at 7:07 PM, David Conrad <drc@virtualized.org> wrote:
> >> * FE80::/64 is used for configuring link local addresses;
> >> * FE80::/10 is reserved by the IETF.
> >> * By default, implementations SHOULD discard packets received from
> >> addresses in FE80::/10 outside of FE80::/64
> > I personally believe the lesson we've learned from the Class E space is that
> this sort of reservation/direction is less useful than we might like.
> 
> It might be common sense, but could you give me a hint why a
> implementation SHOULD not discard those packets? I really tried to craft a
> scenario, but none come to my mind so far.

MUST NOT would seem to match the intent of the original
RFCs which say:
"   Routers must not forward any packets with link-local source or
   destination addresses to other links."

-Dave

v2.23.0 | Report a Bug | By Email