Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

Mikael Abrahamsson <swmike@swm.pp.se> Mon, 09 November 2020 11:36 UTC

Return-Path: <swmike@swm.pp.se>
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 4153A3A0F35 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 03:36:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 pdf6PdWpt6mX for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 03:36:02 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36F223A0EF2 for <ipv6@ietf.org>; Mon, 9 Nov 2020 03:36:02 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9A351B4; Mon, 9 Nov 2020 12:36:00 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1604921760; bh=k7KZGNof+5R7nCWu5gBEsLLBsGc3QK2paezKrBNRO54=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=OzyB2UD+RTas1fH2mk/jwjEbjJXAItdFU4SVbHAEqQswe5SdJU+X/N8HR8VZ/4uhM tcqxWFQ4PG02V9wx3SZXbi+3yTema49DLRuNjC1kf1uhLXMfDfYmi0OfmqGRNJM+yC bhNaA9ZtNnN8ZwogwPq5R638JO8dXWLvimxvPP38=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 96751B3; Mon, 9 Nov 2020 12:36:00 +0100 (CET)
Date: Mon, 09 Nov 2020 12:36:00 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ca By <cb.list6@gmail.com>
cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, 6man WG <ipv6@ietf.org>
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
In-Reply-To: <alpine.DEB.2.20.2011091220500.15604@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.20.2011091232440.15604@uplift.swm.pp.se>
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com> <CAD6AjGQPatbg5=OaMzxJXy5mGZai1bqLfg8f+9SUnfg=s1kADg@mail.gmail.com> <FE260932-A064-493E-8CD5-D92B2725F9E6@employees.org> <CAD6AjGRXYqJhXL6ipbS_cWkE2mg3sU4tM5XCCvgiGvSALGfeeg@mail.gmail.com> <alpine.DEB.2.20.2011091220500.15604@uplift.swm.pp.se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UGJmoJmKV9TVH1__6z1agi6wQGI>
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: Mon, 09 Nov 2020 11:36:04 -0000

On Mon, 9 Nov 2020, Mikael Abrahamsson wrote:

> If you already know what /56 the customer has (because you assign it the 
> same way as the default bearer /64 is assigned today), you don't need a 
> full-on stateful dhcpv6 server in the PDN gateway. You can do it 
> statelessly and just respond with the same /56 regardless. You don't 
> need a full DHCPv6-PD server, you just need a bare-bones DHCPv6 
> responder that takes information from the local pool database that it 
> already uses to keep track of what prefix goes to what bearer.

https://www.etsi.org/deliver/etsi_ts/123400_123499/123401/11.03.00_60/ts_123401v110300p.pdf 
talks about /56 instead of /64, and then it uses PD-exclude for the 
RA-announced "classic" /64 on the bearer.

This seems to me like it was designed *exactly* to avoid more state in the 
PDN gateway. You just assign a /56 to each bearer, send the /64 RA as you 
always do, then if someone happens to ask for DHCPv6-PD you respond with 
that /56. There is no additional "DHCP-servers" etc, you just need a bare 
minimum DHCPv6-PD "announcer/responder".

I can't believe this standard was done in 2011 and now 9 years later we're 
still not any further into deployment. Why?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se