Re: [homenet] Configuration must not be carried by the routing protocol

Ted Lemon <mellon@fugue.com> Wed, 26 June 2013 18:05 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F63111E81CF for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 11:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[AWL=1.600, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IiEKMyzYdJ-Q for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 11:05:43 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 4954F11E8115 for <homenet@ietf.org>; Wed, 26 Jun 2013 11:05:43 -0700 (PDT)
Received: from [IPv6:2001:470:88a3::e9b5:193b:216d:267d] (unknown [IPv6:2001:470:88a3:0:e9b5:193b:216d:267d]) by toccata.fugue.com (Postfix) with ESMTPSA id A33B72381D5F; Wed, 26 Jun 2013 14:05:41 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <93311FD2-507C-4415-9CBC-9D5671F91405@townsley.net>
Date: Wed, 26 Jun 2013 14:05:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E480FDE2-76CF-4FFE-9820-7024BB0B564A@fugue.com>
References: <878v1yqhje.wl%jch@pps.univ-paris-diderot.fr> <020301ce71e1$da38d120$8eaa7360$@comcast.net> <87wqphonkv.wl%jch@pps.univ-paris-diderot.fr> <1A4D24AC-445C-422A-B2C8-D9C307347BA0@townsley.net> <31A37EFD-C5E5-4D6E-81C2-301EC64CD58B@fugue.com> <93311FD2-507C-4415-9CBC-9D5671F91405@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1508)
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Configuration must not be carried by the routing protocol
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 18:05:48 -0000

On Jun 26, 2013, at 1:42 PM, Mark Townsley <mark@townsley.net> wrote:
> DHCPv6 PD has been referred to by one of its co-authors as "a Fax replacement", so that the user doesn't have to type in his prefix sent to him in printed form from his ISP. I think that analogy was given to sway anyone away from trying to rely on it for more than a very long-lived, essentially static, value from an ISP. 

I find this sort of report remarkably unhelpful in making design decisions.   Like all IETF consensus documents, the DHCPv6-PD document is a product of the working group and, ultimately, the IETF.   An opinion expressed by one author at one time during the development of the document provides us with little guidance as to how to interpret the document in the present.   What's in the document should stand on its own.   Certainly current use cases treat DHCPv6-PD as dynamic, not static, for varying values of dynamic right up to "forced renumbering every day."

I also find statements like "the IETF has a configuration protocol, it is DHCP" to be unhelpful, because it's even less grounded in any consensus process.   But let's not fight fire with fire—I think most people reading this statement would have the same reaction to it that we do.   Certainly, a working group chair who used a statement like this as part of a consensus determination would be making a grievous error!