Re: [v6ops] New Version Notification for draft-naveen-slaac-prefix-management-00.txt

Mark Smith <markzzzsmith@gmail.com> Sun, 25 November 2018 07:45 UTC

Return-Path: <markzzzsmith@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 79D53129C6B; Sat, 24 Nov 2018 23:45:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 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_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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FbT_hbpLrMo7; Sat, 24 Nov 2018 23:45:44 -0800 (PST)
Received: from mail-ot1-x341.google.com (mail-ot1-x341.google.com [IPv6:2607:f8b0:4864:20::341]) (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 8C383126BED; Sat, 24 Nov 2018 23:45:44 -0800 (PST)
Received: by mail-ot1-x341.google.com with SMTP id k98so13903421otk.3; Sat, 24 Nov 2018 23:45:44 -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 :cc; bh=sALyC4YfGYVSJU1uHABw508khMdYmAeqYxH7QUGglUA=; b=cNCIHRAa75+CLGT2XKI9zPFl0qVrY1KaEzKIoza1rRunbL3eCIzCinXaewL/6AhptB Mt4xds68+tObJW0B06iG0pepusY8zLV/ODWU3oTxC4c3mkwhCVeeKf+SdcvVZTqASzTy +DeuWCuAtztiiEOk1jBT2wh+KMermhHbvL3tfN/hjG1XM4FKzCRHvQKujGARksN58ynM bT2r6UJHamhZLz2EW/8EDQlMBYyGb47vlLO0raAR8YWuCfpdiVbkL8AJXcZ7hglwEc8+ r7wsTckSGGq5rytFzvvy8NZW82Gx1cZPiDHmfba5QUfEWJerRiKSBQtTm0BxQeqDXYVS qQlg==
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=sALyC4YfGYVSJU1uHABw508khMdYmAeqYxH7QUGglUA=; b=UzzKV+VmZ1dsak24Ixxh1T/CuZjMGVfuqCB/FR3zHpxV/C4JGhvZOB3AvNlPrvKbZ/ Xiyt5oB996hrAXO7nv2656ywd+EKroZkiOgSxp+Grd2JYDM3iqlavxvGx2PbTzz+c5+u JUBNTapSM1ahaqTUQK4mZ+8NpYHwzaWWFGXuqaHn1noQ7u4n6b6TdLEoFOSmGi3kEIm2 daeZtrD5eRG9Zw1Ce8PlpUOO0UvFss8aAXYvgVnMFQFofMVl4Mo5BNc+UgJmvkUfRzVa oRG9Xe9LczSVU8bwtwcU8CjxP/VoPEL9lS6GCAubBR6+KpEBBnjCFesi74JPMOZcyqnU njMw==
X-Gm-Message-State: AA+aEWaU7TzeA7r01MQ/9vHXVquJA4kkke366c0K3XzGMJ63ff8AzZOy HC/rvuzNjmFR6SxXYW7X/eNXuDhZbPmi9sXvcqo=
X-Google-Smtp-Source: AFSGD/UL7ck+Ge1FOv0fVwVs9OKcpgwLwDl6G/HIITFwHtenhD2Anqzfej26pkKPUf4BWPzYhGnpYGNOHzCMAkSCUcA=
X-Received: by 2002:a9d:630f:: with SMTP id q15mr704492otk.187.1543131943759; Sat, 24 Nov 2018 23:45:43 -0800 (PST)
MIME-Version: 1.0
References: <154155148848.30897.17784898234776136208.idtracker@ietfa.amsl.com> <430c94b29f3a49bd9fed24d8d78c6624@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811211109340.14216@uplift.swm.pp.se> <7ba4a7429e374385856002e361e0324e@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811211708220.14216@uplift.swm.pp.se> <51084397aa90410684c599a2cb1953d0@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811211724550.14216@uplift.swm.pp.se> <275c824aec1c46c9a4fd4775e97fa127@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811211903140.14216@uplift.swm.pp.se> <ccb7ae3b97c8430eb2422b2ed3c4505c@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811211920230.14216@uplift.swm.pp.se> <0f1eab2127ce49d2a7f3da56b053c741@XCH15-06-08.nw.nos.boeing.com> <0c56d7eb-e7a3-0640-9612-176c595897d0@gmail.com> <b8b6689d2cfe4985bfb8634661890674@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811220617270.14216@uplift.swm.pp.se> <7bbb7a430084407f801d0becaaa2906d@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811250713500.14216@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1811250713500.14216@uplift.swm.pp.se>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sun, 25 Nov 2018 18:45:17 +1100
Message-ID: <CAO42Z2yrom7eL3EHsvuhixSce0xigNJWm=XzfumfwtqQscn8+w@mail.gmail.com>
Subject: Re: [v6ops] New Version Notification for draft-naveen-slaac-prefix-management-00.txt
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vBFf7FNPYftWZwnhipYoOCKgqyo>
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, 25 Nov 2018 07:45:47 -0000

On Sun, 25 Nov 2018 at 17:16, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Sat, 24 Nov 2018, Templin (US), Fred L wrote:
>
> > Do you think we should bring back RAAN?
>
> Yes, but also note that the relay behavior is my least concern with the
> DHCP+RA combination. The ships in the night problem between leasetimers
> (DHCP) and lifetimes (RA) is a much bigger concern for me.
>

(I haven't followed this thread, apologies if it has been covered.)

In this scenario, I assume the DHCPv6 server is selecting the prefix
to delegate, and the BRAS is acting as a DHCPv6 relay, which is why
the BRAS has to glean the delegated prefix to then be able to announce
it into the routing domain? Are the delegated prefixes dynamic or
static, and if they're static (or at least stable across
disconnect/connect), is it correct that the CPE's DUID is being used
to re-issue the same delegated prefix?

The reason I ask is that the IPv6 residential broadband deployment I
worked on achieved this without gleaning via two methods:

- for static delegated prefixes, the prefix is supplied as part of the
RADIUS authentication response, which the BRAS DHCPv6 server then uses
for DHCPv6-PD, and the BRAS can then announce into the routing domain

- for dynamic delegated prefixes, the RADIUS server provided a pool
name to allocate from, with each BRAS having a local pool with that
name. At the time the pool name was a proprietary RADIUS attribute,
however there is now an IETF attribute for the pool name specified in
RFCRFC6911.


An alternative idea, although probably more medium term, would be to
have the CPE's receive the prefix via DHCPv6-PD, and then the CPE
advertises the prefix itself, using automatically established eBGP
sessions via a well known Link-Local anycast address.

"IPv6 Formal Anycast Addresses and Functional Anycast Addresses"
https://tools.ietf.org/html/draft-smith-6man-form-func-anycast-addresses-00

"5.7.3.  Automatic eBGP Session Establishment"
https://tools.ietf.org/html/draft-smith-6man-form-func-anycast-addresses-00#section-5.7.3


Regards,
Mark.


> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------