Re: 64share v2
Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Wed, 11 November 2020 11:43 UTC
Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 7DA8C3A10AD for <ipv6@ietfa.amsl.com>; Wed, 11 Nov 2020 03:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level:
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.276, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 c4x3Ft7dDIX5 for <ipv6@ietfa.amsl.com>; Wed, 11 Nov 2020 03:43:54 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DFF23A0317 for <ipv6@ietf.org>; Wed, 11 Nov 2020 03:43:52 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kcoXQ-0000G1C; Wed, 11 Nov 2020 12:43:44 +0100
Message-Id: <m1kcoXQ-0000G1C@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: 64share v2
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <CAD6AjGR-NE_sJ_jp7nAT6OvNkcdE9qoWuGEiiVW7r9YtsQvbbw@mail.gmail.com> <CAKD1Yr0G8PjzE+pULte_AaOi=RHMLyto-YUQerGjQ=iOYnz+iA@mail.gmail.com> <0986B112-2159-4045-87F9-876B58F1D896@employees.org> <CAKD1Yr0h9=7p+n=qnH1o1EHqtPrsaYebgvHciOJpP3=iXgNgKQ@mail.gmail.com> <0C739112-D8EA-42C3-BEFD-88C014D5BCD0@employees.org> <62bc0e56-85b8-42ea-c46b-4f2205dc435f@joelhalpern.com> <28C2E56B-1443-480A-B3D1-82E0F8CC0EC7@employees.org> <aabd41ad-1770-f2ac-77d6-62bfff1992c0@joelhalpern.com> <CC7C2B94-5A05-4682-8367-9072CC201C49@employees.org> <80ed3a3b-6e2c-188f-4c1e-c2ededfbbe0d@joelhalpern.com> <0188AC41-60B0-4BC6-810D-DC59CF9E4FB3@employees.org> <1931a638-64ed-f40e-07a3-67cf1eafb941@joelhalpern.com> <376D6BB0-87E2-42E5-9BC4-F3A2F04FA005@employees.org> <CAD6AjGSr-TPcGo7f9EGgoAahYLQTL68CUSq58LGMgD0=6GmRRg@mail.gmail.com> <8DC674FB-9F90-4C41-A323-62BD62934A12@employees.org> <CAD6AjGTYBs8YbHgCJJG84vgwXK4ZSCm65z6KXvZP9F+LdT_atg@mail.gmail.com> <038A830C-E024-42C6-917E-E6FF57829A1C@employees.or g> <CAD6AjGTQVtJBJ3=aZBsF1WcdSK2k9b1hzeZXM6008w_2vpo6_w@mail.gmail.com> <948ACA2B-E45C-4289-A837-9F2536F20F8F@employees.org> <CAKD1Yr0tDTSH2F4=ZsdMJREy1k6equ9mZV0Au1bJPmKuzxeYVA@mail.gmail.com> <43C449AD-D116-4452-A4F2-79AE5A76539F@employees.org>
In-reply-to: Your message of "Wed, 11 Nov 2020 09:53:11 +0100 ." <43C449AD-D116-4452-A4F2-79AE5A76539F@employees.org>
Date: Wed, 11 Nov 2020 12:43:43 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/L1Ko5cbYhMPcNFbQJlDsJfArgHE>
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, 11 Nov 2020 11:43:57 -0000
> Right, you do get a very clear L2 event on mobile networks. If we > want to make this general it might be needed in other networks. > I thought it might be something to consider, given how many problems > we've seen in broadband deployments, where the PE does DHCPv6 PD > snooping as a relay, and seems to forget state. And unless the CE > actively probes there's no way to recover. It seems to me that we need to rethink how we distribute prefixes and other address information. At the moment the primary mechanism to control the lifetime of a prefix or an address is a timer. But we know that doesn't really work. If my laptop connects to a wifi, gets a SLAAC prefix and configures an address and then later connects to a different wifi, then the valid time of the SLAAC prefix is irrelevant, the laptop needs to stop using the prefix. At the same time the router can invalidate the prefix at any moment. So the lifetime is nice for garbage collection, but doesn't have much real world value. In many DHCPv6 PD installations we have the issue that the lifetime of the prefix is completely detached from the forwarding state. If we define a new option to do prefix delegation using RA, then maybe we can try to get rid of lifetimes are the primary mechnism and switch to something more explicit. For example, a downstream device receives a prefix using RA. At some point the downstream device either sees an RA from a new router or see an RA from the same router without the prefix. That should trigger a link attachment procedure where the downstream device verifies that it still connected to the same link and that the upstream router still offers the same prefix. If verification fails then the device removes derived prefixes from any downstream interfaces and tries to inform downstream devices. Ideally we can set all prefix lifetimes to infinity and they will still get cleaned up in time through other mechanisms. I'm not in favor of duplicating DHCP features in RA. However, in the case of prefix delegating, we may be able to fix the semantic gap between what DHCP PD offers and what we really need.
- 64share v2 Ca By
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 Mikael Abrahamsson
- Re: 64share v2 otroan
- Re: 64share v2 Mark Smith
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 otroan
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 otroan
- Re: 64share v2 Mikael Abrahamsson
- Re: 64share v2 otroan
- Re: 64share v2 Mikael Abrahamsson
- Re: 64share v2 Ca By
- Re: 64share v2 Joel M. Halpern
- Re: 64share v2 Ca By
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 otroan
- Re: 64share v2 Joel M. Halpern
- Re: 64share v2 Ca By
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 otroan
- Re: 64share v2 Joel M. Halpern
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 Bob Hinden
- Re: 64share v2 otroan
- Re: 64share v2 Joel M. Halpern
- Re: 64share v2 otroan
- Re: 64share v2 Ca By
- Re: 64share v2 Joel M. Halpern
- Re: 64share v2 Joel Halpern
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 otroan
- Re: 64share v2 Ca By
- Re: [SUSPECTED SPAM] 64share v2 otroan
- Re: [SUSPECTED SPAM] 64share v2 Ca By
- Re: 64share v2 Brian E Carpenter
- Re: 64share v2 Joel M. Halpern
- Re: 64share v2 Ca By
- Re: 64share v2 Philip Homburg
- Re: 64share v2 Brian E Carpenter
- Re: 64share v2 Ca By
- Re: 64share v2 Brian E Carpenter
- Re: 64share v2 Erik Kline
- Re: 64share v2 otroan
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 otroan
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 Philip Homburg
- Re: 64share v2 Mikael Abrahamsson
- Ephemeral addressing [was Re: 64share v2] otroan
- Re: 64share v2 otroan
- Re: 64share v2 Philip Homburg
- Re: 64share v2 Mikael Abrahamsson
- Re: 64share v2 Mikael Abrahamsson
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 otroan
- RE: Ephemeral addressing [was Re: 64share v2] Vasilenko Eduard
- Re: 64share v2 Mikael Abrahamsson
- Re: Ephemeral addressing [was Re: 64share v2] Philip Homburg
- Re: 64share v2 Philip Homburg
- Re: 64share v2 Philip Homburg
- Re: 64share v2 Mikael Abrahamsson
- Re: 64share v2 Philip Homburg
- Re: Ephemeral addressing [was Re: 64share v2] otroan
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 otroan
- Re: Ephemeral addressing [was Re: 64share v2] Lorenzo Colitti
- RE: 64share v2 Vasilenko Eduard
- Re: Ephemeral addressing [was Re: 64share v2] Philip Homburg
- Re: 64share v2 Philip Homburg
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 Alexandre Petrescu
- Re: Ephemeral addressing [was Re: 64share v2] otroan
- Re: 64share v2 Brian E Carpenter
- Re: Ephemeral addressing [was Re: 64share v2] Brian E Carpenter
- Re: 64share v2 神明達哉
- Re: 64share v2 Brian E Carpenter
- Re: 64share v2 Lorenzo Colitti
- Re: 64share v2 Brian E Carpenter
- Re: 64share v2 Gyan Mishra
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 Alexandre Petrescu
- Re: Ephemeral addressing [was Re: 64share v2] Philip Homburg
- Re: Ephemeral addressing [was Re: 64share v2] otroan
- Re: Ephemeral addressing [was Re: 64share v2] Philip Homburg
- Re: Ephemeral addressing [was Re: 64share v2] otroan
- Re: Ephemeral addressing [was Re: 64share v2] Philip Homburg
- Re: Ephemeral addressing [was Re: 64share v2] Fernando Gont
- Re: Ephemeral addressing [was Re: 64share v2] Fernando Gont
- Re: Ephemeral addressing [was Re: 64share v2] Fernando Gont
- Re: Ephemeral addressing [was Re: 64share v2] Fernando Gont
- Re: 64share v2 Brian E Carpenter
- Re: 64share v2 Alexandre Petrescu
- Re: 64share v2 Alexandre Petrescu