IETF Logo Mail Archive

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

Michael Thomas <mike@mtcc.com> Wed, 26 June 2013 18:24 UTC

Return-Path: <mike@mtcc.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 E131C11E8117 for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 11:24:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 om3gX9BlceFF for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 11:24:38 -0700 (PDT)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by ietfa.amsl.com (Postfix) with ESMTP id 7142121F9EF5 for <homenet@ietf.org>; Wed, 26 Jun 2013 11:24:38 -0700 (PDT)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id r5QIOaet015734 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 26 Jun 2013 11:24:37 -0700
Message-ID: <51CB31E4.8080504@mtcc.com>
Date: Wed, 26 Jun 2013 11:24:36 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: David R Oran <daveoran@orandom.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> <93311FD2-507C-4415-9CBC-9D5671F91405@townsley.net> <51CB290D.6000100@mtcc.com> <9F300BF6-6F42-415E-B422-08A0F71E7B96@orandom.net>
In-Reply-To: <9F300BF6-6F42-415E-B422-08A0F71E7B96@orandom.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1438; t=1372271077; x=1373135077; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[homenet]=20Configuration=20must=20not= 20be=20carried=20by=20the=20routing=20protocol |Sender:=20 |To:=20David=20R=20Oran=20<daveoran@orandom.net> |Content-Type:=20text/plain=3B=20charset=3Dwindows-1252=3B= 20format=3Dflowed |Content-Transfer-Encoding:=208bit |MIME-Version:=201.0; bh=cF1PzXj9NgS3nC7cvCJRY9zs2SNhKlPOiQYUWHgttqg=; b=cAQlgTG/Y46ia0b6PyAXTGGPhULVYYTF79/NxAr15rv+mkDKIEReayMhqy uNuHyuw6SDrkxNXLX4QCvEgwB1YIIRnX2fvWZqUYnsG3wnpo9Bkx8eA/6Nd5 uJTe3RKij50jGY+p+/JcU2MCIXaQ8o+JLqwKT72tpZag4DP9g21eQ=;
Authentication-Results: mtcc.com; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; ); dkim-asp=pass header.From=mike@mtcc.com
Cc: Ted Lemon <mellon@fugue.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mark Townsley <mark@townsley.net>, 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:24:43 -0000

On 06/26/2013 11:22 AM, David R Oran wrote:
> On Jun 26, 2013, at 1:46 PM, Michael Thomas <mike@mtcc.com> wrote:
>
>> On 06/26/2013 10:42 AM, Mark Townsley wrote:
>>> 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.
>>>
>> Isn't a Somebody's-Law that states that "every successful protocol will become a
>> transport protocol for something else”?Yup. I claim
>>
> Yup - I claim to have coined that one.
>

Heh -- I definitely heard it from you first :)

Mike

v2.23.0 | Report a Bug | By Email