IETF Logo Mail Archive

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

Jack Bates <jbates@brightok.net> Tue, 01 February 2011 03:42 UTC

Return-Path: <jbates@brightok.net>
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 8052F3A6833 for <v6ops@core3.amsl.com>; Mon, 31 Jan 2011 19:42:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
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 C1-aCM4o5caE for <v6ops@core3.amsl.com>; Mon, 31 Jan 2011 19:42:34 -0800 (PST)
Received: from phobos.brightok.net (mail1.brightok.net [69.8.2.26]) by core3.amsl.com (Postfix) with ESMTP id 62E673A67D3 for <v6ops@ietf.org>; Mon, 31 Jan 2011 19:42:33 -0800 (PST)
Received: from [192.168.1.122] ([69.8.25.3]) by phobos.brightok.net (8.13.6/8.13.6) with ESMTP id p113jm5Z010348 for <v6ops@ietf.org>; Mon, 31 Jan 2011 21:45:48 -0600 (CST)
Message-ID: <4D4781DF.9010009@brightok.net>
Date: Mon, 31 Jan 2011 21:45:35 -0600
From: Jack Bates <jbates@brightok.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: v6ops@ietf.org
References: <8C80472E-DEF2-45DE-BECB-D09E58328D14@cisco.com> <4D46D04C.9080600@brightok.net> <79156CD2-EF2D-4A67-BF40-C67A3FD2B49D@cisco.com> <4D46DDA2.1090204@brightok.net> <B711D39C-5888-4619-B8BF-29A317145E51@cisco.com> <4D46F5BD.2050704@brightok.net> <20110201073623.5628b0b9@opy.nosense.org> <4D472732.5070104@brightok.net> <AANLkTi=Lu64kPViWnphYf_j0o+n+y8dUdXV20wEZ4Uu8@mail.gmail.com>
In-Reply-To: <AANLkTi=Lu64kPViWnphYf_j0o+n+y8dUdXV20wEZ4Uu8@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Tue, 01 Feb 2011 03:42:35 -0000

On 1/31/2011 9:07 PM, Sam Silvester wrote:
> I don't know that I'd be comfortable trusting the CPE with this
> responsibility unless I as the service provider managed it; in fact,
> in many cases for residential ISPs, the customer owns / manages their
> own CPE (and are even welcome to bring their own as opposed to buying
> the one their ISP provides).

Oh, I agree. I meant that as "in addition to" the ISP controls. There's 
no reason every step of the process couldn't have DHCPv6 controls to 
limit excessive requests, especially for DHCPv6-PD. It's precisely the 
"customer buys own CPE" that raises my issues with the lack of a good 
diverse model, both for the ISP as well as support in the CPE market.


Jack

v2.23.0 | Report a Bug | By Email