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

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Mon, 07 May 2012 17:18 UTC

Return-Path: <Tina.Tsou.Zouting@huawei.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 5E54921F8659 for <ipv6@ietfa.amsl.com>; Mon, 7 May 2012 10:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level:
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141, 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 mF8TEdn+aF+K for <ipv6@ietfa.amsl.com>; Mon, 7 May 2012 10:18:26 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 82B5621F8658 for <ipv6@ietf.org>; Mon, 7 May 2012 10:18:26 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFX15255; Mon, 07 May 2012 13:18:26 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 7 May 2012 10:16:57 -0700
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 7 May 2012 10:16:57 -0700
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.48]) by szxeml408-hub.china.huawei.com ([10.82.67.95]) with mapi id 14.01.0323.003; Tue, 8 May 2012 01:16:52 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Christian Huitema <huitema@microsoft.com>
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/QigIOOt9HVpEOEhan7onieOJa9XycAgAAO+4CAAILegIAAFTQAgACMR04=
Date: Mon, 07 May 2012 17:16:52 +0000
Message-ID: <D622DF39-4E02-4BBF-B924-6C80886387B2@huawei.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>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0BC26723@tk5ex14mbxc272.redmond.corp.microsoft.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Dave Thaler <dthaler@microsoft.com>
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:18:27 -0000

Sent from my iPhone

On May 7, 2012, at 9:57 AM, "Christian Huitema" <huitema@microsoft.com> wrote:

>>> Link-Local Unicast Addresses          1111 1110 10   1/1024
>>> Site-Local Unicast Addresses          1111 1110 11   1/1024
>> ...
>> So they define the /10 as the link local *prefix*, within which any *addresses* have to fall into the /64.
>> The rest of the /10 is unused but is still defined as link-local scope.
> 
> The specs may be reasonable, but they did cause confusion for addresses in FE80::/10 but out of FE80::/64. Some implementations appear to treat these addresses as global, others as local, and yet others as "unexpected." There may be a way to use these addresses as an attack vectors against poor implementations. Given that, I would suggest to be very specific:
> 
> * 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
These statements are much clearer.
> 
> -- Christian Huitema
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------