IPv6 Formal Anycast Addresses and Functional Anycast Addresses (Fwd: New Version Notification for draft-smith-6man-form-func-anycast-addresses-01.txt)

Mark Smith <markzzzsmith@gmail.com> Sun, 03 November 2019 11:46 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 76365120113 for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 03:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, 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 (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Ra6RrS1DMdBK for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 03:46:32 -0800 (PST)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (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 03A361200F4 for <6man@ietf.org>; Sun, 3 Nov 2019 03:46:32 -0800 (PST)
Received: by mail-ot1-x329.google.com with SMTP id z6so12115438otb.2 for <6man@ietf.org>; Sun, 03 Nov 2019 03:46:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=0CL0OEaqgv3b1wnuGV2jBNX4breh2rKHDm+hiCtFhF8=; b=Au53e025rjlzZ15Eyp8vaD2on4CyLR5TYqN7rKTNzFBomCMW+JFeUGXW6q6XSsFLTK h6Ep/sekNRp2sYhIMC6848t2GMkmCRMCW2LFY3cf6TsAoSSUOC+KOJkCI2ewGznE5/kD 6CRZfTOBCV7ZLlKdBV/aNkyM6bYS0vrD5ggzODE6ee8kIjLbwVoW3NZ7I44B4059IXiJ G2leqfwv3F7ACqP33V5IJ0FW9jxlJqDV6yDfIrm8tIXOS0fR4+SBEACWoZng2KHmMHWs au8Q4LERoHx2DUyaCw1Ywj/hjcknHmQYUaMMHTGlNj/UOrMVqQ5MOLVRYh+CzNi/z57C YJFg==
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; bh=0CL0OEaqgv3b1wnuGV2jBNX4breh2rKHDm+hiCtFhF8=; b=BNomcRO7cO5CKbuVSDsUmpRIdlcLUR5YspL1RmGSRaqxrV1i4f09H0kf40uOUtrW1o JFA9hWrVdthFZ7jYJky8lcJzoRrgpH6TL/5QIE8Qky3aINf1ze9DsSoIwxuCqfr4QMvC tJaIaNf6jdFHVKCkDE20X04UpFVXfVvVf/pQnkMu0t+vuYn5PWOpd1evf7C/H40sPB/p VlNeXsy5wNHKRujhgHkQhXyi03fGbou5rYnKeXGFLpCE0Z5gAr7jgtFm4DDtSdWFAlM2 qNPUKZ9o5Ifk2yojTFL+e0lDSzYPiG2X3p67yfYqEl2XhriY1KnSG4UtMgcaG89J0+14 J2kA==
X-Gm-Message-State: APjAAAU+OcVVXrqnHNk8ensSqGX4LB9BgBqS3TgEjK3SgMxQ/YANJcJ+ zYEzU32NKE7hciKeJIdyNol50iz7F0hI7qbzo/jwXg60
X-Google-Smtp-Source: APXvYqwh7x1RNpvFerBvBUKK1HQjBb1nmmUGXuCsK1ezo3y92XLpUIjM0cB4n1BLGQ2dXtJJFP0w0MVuOICFLEq42rY=
X-Received: by 2002:a05:6830:2322:: with SMTP id q2mr16083095otg.74.1572781591103; Sun, 03 Nov 2019 03:46:31 -0800 (PST)
MIME-Version: 1.0
References: <157277906705.13535.345852921709779212.idtracker@ietfa.amsl.com>
In-Reply-To: <157277906705.13535.345852921709779212.idtracker@ietfa.amsl.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sun, 3 Nov 2019 22:46:04 +1100
Message-ID: <CAO42Z2wSU-puDaQq-PzTCTE=S3qyqUNrPhH0pgOEO_d3=StnHA@mail.gmail.com>
Subject: IPv6 Formal Anycast Addresses and Functional Anycast Addresses (Fwd: New Version Notification for draft-smith-6man-form-func-anycast-addresses-01.txt)
To: 6MAN <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/-hw8DZlWzMiDVBxejcIjf6EG6p0>
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: Sun, 03 Nov 2019 11:46:34 -0000

Hi All,

This is the second version of a draft I submitted in October last year.

RFC 1546, "Host Anycasting Service", which looks to be the first RFC
specifically on anycast, suggested possible two ways of supporting

-  using addresses within the existing IPv4 unicast address space

- having a distinct class of addresses used for anycast addresses

In both cases of IPv4 and IPv6, it has been the first case.

I think there are advantages to having a formal IPv6 anycast address
class and space. For example, similar to multicast addresses, it could
be very useful to be able to look at an address and immediately know
it is an anycast address.

This draft proposes a formal class of IPv6 anycast addresses,
identified by a well known /8 prefix. It also supports forwarding
scopes, the same ones as multicast. Finally, it supports up to 16
sub-formats for the following 112 bits (mainly as a safety parachute
if the first sub-format ends up being entirely wrong).

The first sub-format, "Functional Anycast Addresses" defines a format
that has many of the properties that IPv6 multicast addresses can have
- ability to encode a unicast IPv6 prefix up to /64 to identify an
anycast domain, IANA assigned well known anycast identifiers, or local
network assigned anycast identifiers.

This draft is quite long and has taken a few years of work because I
wanted to see if the idea of having a specific class of anycast
addresses would work out. I'm also proposing a /8 for this class,
similar multicast having a /8, so I think that requires a lot of

I've put in some possible example use cases, although for most of the
address construction text for them isn't complete. To get up to speed,
I'd suggest looking at the first example, "Devices Factory Configured
with NTP Functional Anycast Addresses", which does go through exactly
how a formal and  functional anycast address is constructed. Then
perhaps have a look at some of the other use cases, possibly starting
with "Multipath Transport Layer Protocols" or "Automatic eBGP Session

I've requested a presentation slot at IETF-106 to present on this ID.

Thanks very much,

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sun, 3 Nov 2019 at 22:04
Subject: New Version Notification for
To: Mark Smith <markzzzsmith@gmail.com>

A new version of I-D, draft-smith-6man-form-func-anycast-addresses-01.txt
has been successfully submitted by Mark Smith and posted to the
IETF repository.

Name:           draft-smith-6man-form-func-anycast-addresses
Revision:       01
Title:          IPv6 Formal Anycast Addresses and Functional Anycast Addresses
Document date:  2019-11-03
Group:          Individual Submission
Pages:          35

   Currently, IPv6 anycast addresses are chosen from within the existing
   IPv6 unicast address space, with the addresses nominated as anycast
   addresses through configuration.  An alternative scheme would be to
   have a special class of addresses for use as anycast addresses.  This
   memo proposes a distinct general anycast addressing class for IPv6,
   and a more specific scheme for functional anycast addresses.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat