IETF Logo Mail Archive

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

"Leddy, John" <John_Leddy@cable.comcast.com> Tue, 25 June 2013 20:42 UTC

Return-Path: <john_leddy@cable.comcast.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 BE1F511E8155 for <homenet@ietfa.amsl.com>; Tue, 25 Jun 2013 13:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.897
X-Spam-Level:
X-Spam-Status: No, score=-0.897 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334]
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 caltVkNHpkc5 for <homenet@ietfa.amsl.com>; Tue, 25 Jun 2013 13:42:30 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id F1D7211E8151 for <homenet@ietf.org>; Tue, 25 Jun 2013 13:42:25 -0700 (PDT)
Received: from ([24.40.56.114]) by pacdcavout01.cable.comcast.com with ESMTP id 97wm3m1.56646719; Tue, 25 Jun 2013 16:41:01 -0400
Received: from PACDCEXMB13.cable.comcast.com ([169.254.5.141]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Tue, 25 Jun 2013 16:42:21 -0400
From: "Leddy, John" <John_Leddy@cable.comcast.com>
To: Dave Taht <dave.taht@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: [homenet] Configuration must not be carried by the routing protocol
Thread-Index: AQHOceR9NMCq1bvg3kuCUnnDg9dRmw==
Date: Tue, 25 Jun 2013 20:42:20 +0000
Message-ID: <9FB60CE5849B194190DC0CDAD4825AEC3F4272EC@PACDCEXMB13.cable.comcast.com>
In-Reply-To: <CAA93jw4mAUDBb2Q2AFqs6nyUXKnNFi9X9faWtj_cHJC5PqB2Mg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [68.87.16.248]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6B43BACBA870C042A7182ED5D03CE8FB@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 25 Jun 2013 20:42:36 -0000

On 6/25/13 3:58 PM, "Dave Taht" <dave.taht@gmail.com> wrote:
>
>I have been on the fence on this issue for a very long time,
>preferring to wait for running code, and the opportunity to run it.
>Various problems, like the need for a small dhcpv6-pd capable server
>have been met, but the prefix distribution issue and choice of a
>routing protocol remains a sketchy one.
>
>Do we have consensus that the majority of connections in the homenet
>will be wireless?


If you really mean wireless not wifi, I would agree.

But don't forget about Zigbee on the wireless side (and futures).

Also technologies using existing wiring; MoCA, HPNA and HomePlug (and
futures).  
They may be for direct attachment (ex. IP STBs) or dongles for ethernet,
wireless, HomeNet router extension.

John

v2.23.0 | Report a Bug | By Email