IETF Logo Mail Archive

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

james woodyatt <jhw@apple.com> Wed, 02 March 2011 00:43 UTC

Return-Path: <jhw@apple.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 D2E733A6A21 for <v6ops@core3.amsl.com>; Tue, 1 Mar 2011 16:43:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level:
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 x8nkqnhldb2i for <v6ops@core3.amsl.com>; Tue, 1 Mar 2011 16:43:57 -0800 (PST)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 28D343A6965 for <v6ops@ietf.org>; Tue, 1 Mar 2011 16:43:57 -0800 (PST)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id A8AABD5B0075 for <v6ops@ietf.org>; Tue, 1 Mar 2011 16:45:01 -0800 (PST)
X-AuditID: 11807130-b7b5eae000005ccb-76-4d6d930d4544
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay11.apple.com (Apple SCV relay) with SMTP id 80.C3.23755.D039D6D4; Tue, 1 Mar 2011 16:45:01 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="us-ascii"
Received: from [17.193.13.64] by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHE00BNTNF17I50@et.apple.com> for v6ops@ietf.org; Tue, 01 Mar 2011 16:45:01 -0800 (PST)
From: james woodyatt <jhw@apple.com>
In-reply-to: <027501cbd86b$ed15f2d0$c741d870$%sturek@att.net>
Date: Tue, 01 Mar 2011 16:45:01 -0800
Message-id: <EE6C68F4-5A67-4511-8904-BF0B31ACD683@apple.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>
To: IPv6 Ops WG <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1203)
X-Brightmail-Tracker: AAAAAA==
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 00:43:57 -0000

On Mar 1, 2011, at 3:53 PM, Don Sturek wrote:
> 
> I think these topics need to be addressed someplace before internetworked CPEs are deployed and the topic becomes a major oversight.  For our application (Smart Energy) we already have groups like WiFi, HomePlug and HomeGrid planning exactly such deployments next year.

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.

Is there are reason that application proxies and neighbor discovery proxies are unsatisfactory solutions?


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking

v2.23.0 | Report a Bug | By Email