Re: IPv6 Link Local Addresses

Kerry Lynn <kerlyn@ieee.org> Tue, 11 June 2019 17:42 UTC

Return-Path: <kerlyn2001@gmail.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 A677E120133 for <ipv6@ietfa.amsl.com>; Tue, 11 Jun 2019 10:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S653kPcfAxKS for <ipv6@ietfa.amsl.com>; Tue, 11 Jun 2019 10:42:37 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D38CD12012A for <ipv6@ietf.org>; Tue, 11 Jun 2019 10:42:36 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id p13so3895603wru.10 for <ipv6@ietf.org>; Tue, 11 Jun 2019 10:42:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZCfWxsShDLGjgyDgrZLSq7daIomHYUuVgK9Vtnh3rDY=; b=WxYkeCMurr6bPyXM86p0WCGOtj1bb5UPrubE4TbOUM8uaiIEKJx11vtxmwwCQttRMi l1WyTbbWAx4xlZrTlXl3AGiVfwygU5dm6d4E51wfNjw//ZAYmBGhRspLSoR6OJw1TBI7 S0GrJ3waMYVu4VV+aYDPFEQ6bbwCA795samUg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZCfWxsShDLGjgyDgrZLSq7daIomHYUuVgK9Vtnh3rDY=; b=rv0OSRjJrpoq19gDKUlrHCHtYSxp8vtR5uv1O3+vzp3kxIRnfroQrfnNZScgxUQ6OY UslhVxn3Dk9ArugpXpqI3FQQ13TGuLQYps0xNfv1LLLuuGpH8dklNxee9gO2uQmevUFY uMMK3JCJ/mfBo2sbTgMxdKCbo3iS11H2uH0aymaEzoACqZVlrE8CuNdWi8EtmWqcmVEu +UlzY1BMzNIdUoSx8+Pz2lP+fFSQGugEHQ/eAwcbqgylMaWpkNdM+7E81+ZG/uPOBr4M 053a2mzIVS2lkGFGciDKDcrOGF13qmPsMILq6tVVQgr7gNUtDbBaphNWpOYFxAiVEG0z urfg==
X-Gm-Message-State: APjAAAWnAWIKIkdHz5FmjU06ih/nvuDTBxcWMEll+/dn9nR7tjy+jrtM jqCZ+TyNy5ftgk+ny9vX1GWJbZjSZ2bP9nns3hg=
X-Google-Smtp-Source: APXvYqw44QwgfC+aBFXYoBIqRf0gUGm7DUrhCA+pyGKqniTna+lR9g/DWlAQaFQiWwEmZeafWkSEFjOcpeHgwm1RFvg=
X-Received: by 2002:a5d:5152:: with SMTP id u18mr17788650wrt.319.1560274955273; Tue, 11 Jun 2019 10:42:35 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR15MB2506E62560613C85F74A1FF8BB100@DM6PR15MB2506.namprd15.prod.outlook.com> <CALx6S36vVpD9bAPSBQmhV+daR0Yr4heQ-LaiB4hABAs8ofVfNQ@mail.gmail.com> <DM6PR15MB25063BAF058C1825E2B63E30BB130@DM6PR15MB2506.namprd15.prod.outlook.com> <CAKQ4NaW-QRZDO52zDZTSqz_MsfrS1uQHdz6zFjo+gXvtYVnFxA@mail.gmail.com> <DM6PR15MB2506E06165EA22E66BBB9524BB130@DM6PR15MB2506.namprd15.prod.outlook.com> <7E03089C-8429-4B56-96D6-441490C850B2@gmail.com> <32ad99f9-7e22-d214-7311-266d4f12caba@gmail.com>
In-Reply-To: <32ad99f9-7e22-d214-7311-266d4f12caba@gmail.com>
From: Kerry Lynn <kerlyn@ieee.org>
Date: Tue, 11 Jun 2019 13:42:23 -0400
Message-ID: <CABOxzu1Lr0n7VfaW3_CECYbe2UphGoQ8ByWMkvKfx1HpohfeBA@mail.gmail.com>
Subject: Re: IPv6 Link Local Addresses
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: 6man 6man <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000076094c058b0fd2d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4fWdPQ03wXrRre4cTGP7MM0a4zY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 11 Jun 2019 17:42:39 -0000

On Tue, Jun 11, 2019 at 9:05 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 10/06/2019 à 18:44, Bob Hinden a écrit :
> > Hi,
> >
> > RFC4291 defines Link Local Address as:
> >
> >   2.5.6.  Link-Local IPv6 Unicast Addresses
> >
> >     Link-Local addresses are for use on a single link.  Link-Local
> >     addresses have the following format:
> >
> >     |   10     |
> >     |  bits    |         54 bits         |          64 bits           |
> >     +----------+-------------------------+----------------------------+
> >     |1111111010|           0             |       interface ID         |
> >     +----------+-------------------------+----------------------------+
> >
> >     Link-Local addresses are designed to be used for addressing on a
> >     single link for purposes such as automatic address configuration,
> >     neighbor discovery, or when no routers are present.
> >
> >     Routers must not forward any packets with Link-Local source or
> >     destination addresses to other links.
> >
> > This means that link local addresses have a 10 bit prefix (1111111010)
> followed by 54 bits of zeros.  That is it, nothing more.   Address with
> different prefixes or with a 1111111010 prefix followed by non-zero 54 bits
> are not link local addresses.
> >
> > This is not ambiguous.
>
> Bob,
>
> The RFC4291 link local addresses have a 10 bit prefix and 54bits of
> zero.  That is fe80::/64.
>
> The IANA allocation of IPv6 link-local addresses is fe80::/10.
>
>  > fe80::/10    Link-Scoped Unicast     [RFC3513][RFC4291]
>
> In that sense, the IANA definition and the RFC4291 differ with respect
> to the definition of link-local addresses.
>
> fe80::/10 and fe80::/64 are not the same thing.
>
> Alex
>
>
Bob et al.

Would a correct router implementation base its "must not forward" decision
on the most-significant 10 bits or most significant 64 bits?

Kerry