Re: Question on anycast IID range(s)

Erik Kline <ek@loon.co> Wed, 02 January 2019 17:57 UTC

Return-Path: <ek@google.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 90AA0130ECF for <ipv6@ietfa.amsl.com>; Wed, 2 Jan 2019 09:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.499
X-Spam-Level:
X-Spam-Status: No, score=-9.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=loon.co
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 u0YvziFTFeo4 for <ipv6@ietfa.amsl.com>; Wed, 2 Jan 2019 09:57:38 -0800 (PST)
Received: from mail-it1-x12c.google.com (mail-it1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 92739130ECD for <ipv6@ietf.org>; Wed, 2 Jan 2019 09:57:38 -0800 (PST)
Received: by mail-it1-x12c.google.com with SMTP id h193so39657109ita.5 for <ipv6@ietf.org>; Wed, 02 Jan 2019 09:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loon.co; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=rWQH/UiSqVjmIikXN6jBqzvCucU6y5N7BX3VFOFQj/Y=; b=JhjM7lUXshhpL5YJTgxgn4IzATc/MGBit4NIgRf2/Z0smza6OsYm6TimwkuzgRRZNw 5iDdOi2L5DLppJFcynAU/dzMn8nc4b5dFvYydYbCtgba+EtD7XHZvpqL581hfNTftJDX QywoSLRZ5uUamxiR2noP7H+vsAxi3clpqVarM=
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:reply-to :from:date:message-id:subject:to:cc; bh=rWQH/UiSqVjmIikXN6jBqzvCucU6y5N7BX3VFOFQj/Y=; b=WQ0hoIFgyQrWn6WunG2OZW4j6x+wAhEEKtL9G9Wwbz1oYIhVaXLzbR58l7IXv6xFjC OEPgyKvkXO3zfX4ZbPF+YGXpU/mnVgcSFvXgSFb5GDBYu4f/LOp074ACZxlZgwgGch5K BcJy1gEFarerJCTMCO9V0cZwvY0INiJcUmp+3WI9hPKceykXozAph9NLt1nXUsY/VyK9 Ty1T6BuC6+SZLVgn65/jkBjxfD/d53lmDCnfWSG5OxB5J7lg2uVR0LbrGEdD5IOHrnjk DMXNVyAAOMzNxC0s6tDMy2/Vmg/twJrf40kxvKditdo6mrNY6NZXnwNgp6cVsLONUZXi GMyQ==
X-Gm-Message-State: AA+aEWZd/gesfjFGpsgamCkKs4JGcjBsFXLGFJs5vCkDuJpUVBXM3nyi 5La69bESZOOpGsuuxeIkBWHYhXXw/mrwJ+7RnEycbpYtIk1ENg==
X-Google-Smtp-Source: AFSGD/X1oSHx+QEAUKNChQWE6nA6PSQVNBS6D1pdA2RHPU9dFz8CCxD4rapzVxnKhOcLO9OpaScoWtTytx46XKvdeMA=
X-Received: by 2002:a02:8943:: with SMTP id u3mr28774411jaj.92.1546451857504; Wed, 02 Jan 2019 09:57:37 -0800 (PST)
MIME-Version: 1.0
References: <CABOxzu1O6qd_23xLgpAsx6BiZ09SCNUAgFurOL2UX4HQTvYFCA@mail.gmail.com>
In-Reply-To: <CABOxzu1O6qd_23xLgpAsx6BiZ09SCNUAgFurOL2UX4HQTvYFCA@mail.gmail.com>
Reply-To: ek@loon.co
From: Erik Kline <ek@loon.co>
Date: Wed, 02 Jan 2019 09:57:26 -0800
Message-ID: <CAAedzxq=AHCD6MSksz4P4ZGVxamStF3x2+xTasJH+oOxFY5H9Q@mail.gmail.com>
Subject: Re: Question on anycast IID range(s)
To: Kerry Lynn <kerlyn@ieee.org>
Cc: 6man 6man <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a164ed057e7d61a9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0EgZo17Qt5fvQ1muDm2B6hQFuCI>
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: Wed, 02 Jan 2019 17:57:41 -0000

I think practically speaking the only to tell if an address on another node
is anycast or not is by the observable difference in the NA:

    https://tools.ietf.org/html/rfc4861#section-7.2.7

"""
   From the perspective of Neighbor Discovery, anycast addresses are
   treated just like unicast addresses in most cases.  Because an
   anycast address is syntactically the same as a unicast address, nodes
   performing address resolution or Neighbor Unreachability Detection on
   an anycast address treat it as if it were a unicast address.  No
   special processing takes place.

   Nodes that have an anycast address assigned to an interface treat
   them exactly the same as if they were unicast addresses with two
   exceptions.  First, Neighbor Advertisements sent in response to a
   Neighbor Solicitation SHOULD be delayed by a random time between 0
   and MAX_ANYCAST_DELAY_TIME to reduce the probability of network
   congestion.  Second, the Override flag in Neighbor Advertisements
   SHOULD be set to 0, so that when multiple advertisements are
   received, the first received advertisement is used rather than the
   most recently received advertisement.
"""


On Wed, 2 Jan 2019 at 08:51, Kerry Lynn <kerlyn@ieee.org> wrote:

> For practical purposes, particularly in light of RFC 7136, should one
> consider an anycast address to be any that ends in dfff:ffff:ffff:ff80-
> dfff:ffff:ffff:ffff OR ffff:ffff:ffff:ff80-ffff:ffff:ffff:ffff?
>
> The phrase in RFC 2526 that's causing confusion for me is
> "Specifically, for IPv6 address types required to have to have
> [sic] 64-bit interface identifiers in EUI-64 format ..."  To my
> knowledge, there are address types that require a 64-bit IID,
> but it seems we've been systematically trying to deprecate
> *EUI-64 format* IIDs.  In any case, there's nothing to prevent a
> mix of EUI-64 or *other* format IIDs in the same subnet as far
> as I'm aware.
>
> Thanks, Kerry
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>