IETF Logo Mail Archive

RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt]

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 01 February 2018 17:39 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 C9B6212EC0D for <ipv6@ietfa.amsl.com>; Thu, 1 Feb 2018 09:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 Go-24jBQ7SzU for <ipv6@ietfa.amsl.com>; Thu, 1 Feb 2018 09:39:52 -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 2910A12EBBA for <ipv6@ietf.org>; Thu, 1 Feb 2018 09:39:52 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 67384B1; Thu, 1 Feb 2018 18:39:50 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1517506790; bh=kasM2jDL4goGQtG+WzKBPV0UVfe9EU4czlWtbupoDFg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=SEMo9TGwRWIg8ilx6+wOEkp7tnuXqAC+pQDr61bTvmnx5EJOqCO9nRtQS/PXFXqvI YhUvfOtF+mhKJg5RGWQ1TQogcNAOTX73cKxa9GhSrdCylcaJ86BXTDuNp0KC2sgEs2 lv93l8CcrSFAt4PLfusNQ/uIO6jWEampx9MXifrM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 639CEB0; Thu, 1 Feb 2018 18:39:50 +0100 (CET)
Date: Thu, 01 Feb 2018 18:39:50 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
cc: Lorenzo Colitti <lorenzo@google.com>, 6man WG <ipv6@ietf.org>
Subject: RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt]
In-Reply-To: <c3357bf41dab4c268039fa8fe463bc8f@XCH15-06-08.nw.nos.boeing.com>
Message-ID: <alpine.DEB.2.20.1802011832480.8884@uplift.swm.pp.se>
References: <91953634-9B4A-405B-AB36-FBB2079A0A40@gmail.com> <CAKD1Yr23G+rz7woT1K504UEb2=sQGJd2p_CcQogLA5BbmTomZA@mail.gmail.com> <32FB86D8-235A-434F-A20C-6624FB7C3CE2@employees.org> <CAKD1Yr1oTmBOQR7YJnJV3S9_NG54sA-+phzRMwPT5qQcF1nKPA@mail.gmail.com> <alpine.DEB.2.20.1801311327410.8884@uplift.swm.pp.se> <CAKD1Yr04NV0+r1V1XnOo9XUu2GF_RiVPN6pqM0pJ0a68=mC9Zw@mail.gmail.com> <alpine.DEB.2.20.1801311402350.8884@uplift.swm.pp.se> <CAKD1Yr2cTdK+kkojHa5qPOO4VyT=jW1pmJmf=uXSrdif404iQQ@mail.gmail.com> <alpine.DEB.2.20.1802010954270.8884@uplift.swm.pp.se> <CAKD1Yr28iU=jCBv7dy4D8gyeL=uB5hFu-YhGOKPiih9sykZ1GQ@mail.gmail.com> <alpine.DEB.2.20.1802011138010.8884@uplift.swm.pp.se> <658076313dd5488080a596717d00c19b@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1802011733380.8884@uplift.swm.pp.se> <d9091a6779aa47cc905a1fdb76480b84@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1802011805250.8884@uplift.swm.pp.se> <c3357bf41dab4c268039fa8fe463bc8f@XCH15-06-08.nw.nos.boeing.com>
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/Na57rRKzp60eB__9ZVQP-yt4EWs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 01 Feb 2018 17:39:55 -0000

On Thu, 1 Feb 2018, Templin, Fred L wrote:

> I am trying to understand this and failing. Is it the way the acronym 
> sounds as it rolls of your tongue? Is it a loathing of the many public 
> domain and proprietary implementations? Do you think there is something 
> flawed with the protocol messaging?

Yes. All of it.

Btw, around 2008-2012 when I started dibbling with IPv6 I ran into the 
same problem with DHCPv6 public domain server(s) implementation that was 
available didn't have RIB interaction. So yes, I could do PD, I just 
couldn't make it actually useful.

> I have also shown how IPv6ND and DHCPv6PD can be combined into a unified 
> service for all autoconfiguration needs. Even if it were to be pure 
> IPv6ND, though, there would still need to be a control messaging 
> protocol for route lifetime management that does pretty much the same 
> thing that DHCPv6 control messaging already does. So, why not just use 
> DHCPv6PD?

Because it was designed as ships in the night with routers. Because it 
generally doesn't support telling the device that "oops, your lease is up 
before its time".

If we just gave up the idea that the DHCPv6 server lives anywhere else 
than on a router (with all consequences that has), that would solve some 
parts of my issues with it. Specifying what some events on ND would 
reflect on DHCPv6 resources (operational document) would also help.

So your proposal of tunneling DHCPv6 inside RS/RA and if that means we get 
operational guidance such as "zero lifetime in the RA means deprecate all 
DHCPv6 resources you have" and similar, would help a long way.

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

v2.23.0 | Report a Bug | By Email