Re: [fun] Routing ?

Mikael Abrahamsson <swmike@swm.pp.se> Sat, 02 July 2011 09:20 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: fun@ietfa.amsl.com
Delivered-To: fun@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175BF21F86DE for <fun@ietfa.amsl.com>; Sat, 2 Jul 2011 02:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iMaMbE9gQqhr for <fun@ietfa.amsl.com>; Sat, 2 Jul 2011 02:20:03 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 268C921F86DD for <fun@ietf.org>; Sat, 2 Jul 2011 02:20:02 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 00BCB9E; Sat, 2 Jul 2011 11:19:58 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id F388C9A for <fun@ietf.org>; Sat, 2 Jul 2011 11:19:58 +0200 (CEST)
Date: Sat, 02 Jul 2011 11:19:58 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: fun@ietf.org
In-Reply-To: <4E0ED065.6060706@piuha.net>
Message-ID: <alpine.DEB.2.00.1107021025410.31677@uplift.swm.pp.se>
References: <4E0AE3CF.2070504@piuha.net> <ECEBBF3B-B240-48DF-8A6B-F0566322F18D@cisco.com> <4E0ED065.6060706@piuha.net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Subject: Re: [fun] Routing ?
X-BeenThere: fun@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "FUture home Networking \(FUN\)" <fun.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fun>, <mailto:fun-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fun>
List-Post: <mailto:fun@ietf.org>
List-Help: <mailto:fun-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fun>, <mailto:fun-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2011 09:20:04 -0000

On Sat, 2 Jul 2011, Jari Arkko wrote:

> But back to your question. Do we need a routing protocol, or can a 
> single router be at the center and deal with all? I think the single 
> router model is a good one even when there are multiple subnets. That 
> being said, when you plug in. say, the first sensor-network-to-WLAN 
> router that can't do bridging you're in trouble. I personally think we 
> should build for the case where there are multiple routers, while hoping 
> that there is just one and that the number of subnets is either 1 or at 
> least a very small number.

It's my opinion that while it may not happen the first 5-10 years, any 
home will consist of multiple routers.

Any architecture we develop should in the long run handle multiple 
upstream providers (implying multiple provider CPEs) and multiple 
hierarchies of routers in the home. I also believe we need a routing 
protocol, plus a mechanism to do source based routing out to the correct 
ISP. Some of the needed mechanism might need to be developed in other WGs, 
but this WG can determine the need.

This was discussed in quite a lot of detail on v6ops a few months back for 
the CPE router requirement draft, I'm sure there are discussions in other 
WGs touching on these topics as well.

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