Re: [v6ops] draft-wbeebee-v6ops-ipv6-cpe-router-bis - where to go from here

Joel Jaeggli <joelja@bogus.com> Wed, 02 March 2011 16:26 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79F4D3A6816 for <v6ops@core3.amsl.com>; Wed, 2 Mar 2011 08:26:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.924
X-Spam-Level:
X-Spam-Status: No, score=-101.924 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aeZXpnVmpQiV for <v6ops@core3.amsl.com>; Wed, 2 Mar 2011 08:26:44 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 1FA203A67A5 for <v6ops@ietf.org>; Wed, 2 Mar 2011 08:26:43 -0800 (PST)
Received: from 23173jjaeggli.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p22GRfhs059267 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 2 Mar 2011 16:27:42 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D6E6FF8.8000008@bogus.com>
Date: Wed, 02 Mar 2011 08:27:36 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.14) Gecko/20110221 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <8C80472E-DEF2-45DE-BECB-D09E58328D14@cisco.com> <20110301221558.GA22199@srv03.cluenet.de> <B2B0EB4F-BF8B-4148-A0BE-E64937AFD54B@apple.com> <027501cbd86b$ed15f2d0$c741d870$%sturek@att.net> <EE6C68F4-5A67-4511-8904-BF0B31ACD683@apple.com> <16BC7386-769C-46E3-A6E4-6EA957268E06@cisco.com> <0B0B1D69-37A1-4BDC-A473-D574C087F3A0@apple.com> <06B3A5FE-6BA7-46C1-86D1-19AA80321628@cisco.com>
In-Reply-To: <06B3A5FE-6BA7-46C1-86D1-19AA80321628@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Wed, 02 Mar 2011 16:27:42 +0000 (UTC)
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] draft-wbeebee-v6ops-ipv6-cpe-router-bis - where to go from here
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 16:26:45 -0000

buffalo aps that I was using a couple of years ago came with rip enabled
by default. That was to support the extension of the network using their
bridges or mesh APs. similarly I've seen OLSR deployed in a similar
fashion in both cases it was meant to be done without user intervention.

When two devices are plugged together today they form an l2 adjacency,
why not an l3 one?

joel

On 3/2/11 8:14 AM, Fred Baker wrote:
> 
> On Mar 2, 2011, at 7:57 AM, james woodyatt wrote:
> 
>> On Mar 1, 2011, at 7:42 PM, Fred Baker wrote:
>>> On Mar 1, 2011, at 4:45 PM, james woodyatt wrote:
>>>
>>>> Understood.  Do any of those organizations have a recommendation for a suitable interior routing protocol for residential IPv6 networks?  I'm pretty sure IETF doesn't have one to recommend right now, and I'm pessimistic that it will have one by next year to satisfy the plans of the Smart Energy community.
>>>
>>> Well, one could discuss ZOSPF, or OSPFv3 with a default configuration, or RIPng, or IS-IS with a default configuration. Why would, picking one at random, RIPng be inappropriate?
>>
>> Unacceptable human interface burden, for starters.  Beyond that, I have no technical contributions I can make here.
> 
> I dunno. On my Linksys router (which I don't use anymore, but there is one here at the house), there is a radio button that says "on" or "off" for RIP. If OSPF comes with a default configuration such as described in the MIB document, it can do the same; at the job I had before coming to Cisco (ACC), our configuration design required that when you turned a feature on it had to be operational, and from there configuration commands would change it, and so "SET OSPF ON" (ACC's equivalent of that radio button) had to result in a usable configuration. It worked quite well, actually. I don't see a radio button as "unacceptable UI burden"; a lot of people seem to be able to handle it.
> 
> I would agree if we were asking people to navigate IOS CLI. That's a punishment, not a UI :-)
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>