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

Mark Townsley <mark@townsley.net> Wed, 26 June 2013 17:42 UTC

Return-Path: <mark@townsley.net>
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 150D821F9DBB for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 10:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 EeZUklXoIkYu for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 10:42:13 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 5903721F9D07 for <homenet@ietf.org>; Wed, 26 Jun 2013 10:42:13 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id f11so10657630wgh.27 for <homenet@ietf.org>; Wed, 26 Jun 2013 10:42:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=XiKnKIXk5S/JUaO1iGJHWM6f4vpxKH+3J7Pgbpq0lSw=; b=b9iWddhi359FxfRwlvOpEB9lJTDTL93i8r4BBeAR60096+u3d5jNWNGFAJlhM/JYDS F3yKVDqRjtjICGqR8/FvKfsE7Bd5upteGeUnTyS4CXMSYhsTy7GaDg6CDFGel7oqaB9/ kcGgJ9L1dIckWurfqil9VbE//0VCpwIxAMHmWi4uxXJ/aW7TOAJcVGi4yb4Id3f+aYBN 3SIcUJAq2DkOlZ+bUcvVYb6sj0sa0on9MchiNE7QbbweoFKplQnxEZjTfpHlUrxzZ0sh 1+DCxZPlAtqZOD4nvTz9OZm+JTYPuBKA18+fnjgrcepeODbf4XJBtH4MT7YT36rMlqsw 6zPg==
X-Received: by 10.194.243.226 with SMTP id xb2mr3643833wjc.67.1372268532428; Wed, 26 Jun 2013 10:42:12 -0700 (PDT)
Received: from ?IPv6:2001:420:44f0:1004:90c:ea8e:a056:5036? ([2001:420:44f0:1004:90c:ea8e:a056:5036]) by mx.google.com with ESMTPSA id w4sm12254124wia.9.2013.06.26.10.42.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Jun 2013 10:42:11 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <31A37EFD-C5E5-4D6E-81C2-301EC64CD58B@fugue.com>
Date: Wed, 26 Jun 2013 19:42:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <93311FD2-507C-4415-9CBC-9D5671F91405@townsley.net>
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>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1283)
X-Gm-Message-State: ALoCoQmeX8UpcGxdtSbbjrjvPs84yoyWnH/Q8KVnjCFe6PA6tzcaDKW4MHbV66SORnj/CxZdkVgZ
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 17:42:14 -0000

On Jun 26, 2013, at 3:52 PM, Ted Lemon wrote:

> On Jun 26, 2013, at 4:08 AM, Mark Townsley <mark@townsley.net> wrote:
>> That explicit statement went away in RFC 3315, though the terminology section makes it very clear that a Host is not a Router.
> 
> DHCPv6 PD is explicitly for configuring routers, so I think this assertion is wrong.   

This was linked back to the assertion that "the IETF has a configuration protocol, it is DHCP" or some such. I was simply trying to point out what "the IETF" has on record in this regard.

Certainly, we often use protocols beyond their original intent. RFC 5218 calls this "Wild Success", with plenty of examples. 

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 think Lorenzo's argument is a better one.

Agreed.

- Mark