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

Fred Baker <fred@cisco.com> Wed, 02 March 2011 16:13 UTC

Return-Path: <fred@cisco.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 A5B773A67AE for <v6ops@core3.amsl.com>; Wed, 2 Mar 2011 08:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.511
X-Spam-Level:
X-Spam-Status: No, score=-110.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 8C9mqfALiJQO for <v6ops@core3.amsl.com>; Wed, 2 Mar 2011 08:13:28 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 5E3083A67A5 for <v6ops@ietf.org>; Wed, 2 Mar 2011 08:13:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1629; q=dns/txt; s=iport; t=1299082474; x=1300292074; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=da1D7rdzzdy+/6Ic4fXCYOU8sw10s6wlxMFMKdTedds=; b=Gkyop34sC5H7ASZNE1lKwIjHfiwmHIMxenGt/NHezS0e50oq281xodYX wHfzEVTwFkJ7NY0M5xM8t2WA7Sh1F+NcPaiHHeoscsKdaA2uWWt/TLcJr hSrgmAtRu2trGKq7uWtBoEcd3MUCnJin/SOvB2GHZ9g1jbATJzkWNoeRf Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEr8bU2rRN+J/2dsb2JhbACmWHShd5tyhWEEhReHDw
X-IronPort-AV: E=Sophos;i="4.62,253,1297036800"; d="scan'208";a="337847853"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 02 Mar 2011 16:14:27 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p22GDVDd019566; Wed, 2 Mar 2011 16:14:27 GMT
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Fred Baker <fred@cisco.com>
In-Reply-To: <0B0B1D69-37A1-4BDC-A473-D574C087F3A0@apple.com>
Date: Wed, 02 Mar 2011 08:14:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <06B3A5FE-6BA7-46C1-86D1-19AA80321628@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>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1082)
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:13:29 -0000

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 :-)