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

Ole Troan <otroan@employees.org> Mon, 31 January 2011 23:32 UTC

Return-Path: <ichiroumakino@gmail.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 471883A6B88 for <v6ops@core3.amsl.com>; Mon, 31 Jan 2011 15:32:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level:
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, 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 S8VEHwFxpMxT for <v6ops@core3.amsl.com>; Mon, 31 Jan 2011 15:32:22 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 0C7E13A6848 for <v6ops@ietf.org>; Mon, 31 Jan 2011 15:32:21 -0800 (PST)
Received: by ewy8 with SMTP id 8so3139129ewy.31 for <v6ops@ietf.org>; Mon, 31 Jan 2011 15:35:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=61mdg5e0vc2LGvoowEJPCl2p8A9NJX+Ktxqhp+JeUEo=; b=jFGOAHUIroPBVpYcUVbIPtse+/d/Ec+oxfv5yTGIMDZZH8rfzmzz6oAlYtCI3Fr6W2 Xhsvuq/v/WAMHMB/mUuzeGvpFM78tA67bNWY0C+aoUs4W+trDGlnY+g0/u584bidGkhe +/X5HT9/cWrpGe+lVg3WYcZKJ+joA7k+9nEH8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=yCWLdGyBRem4nW+ANWanfle5/K03+IlVeU1aZjmzwIlJ7O4U2KbjBbZmNjs25XCPs2 UdYu34EB8asKVY7upxU4liIADJX/Qk0t+QjFceKe4ttv6UWPzNKcqASoaen3GEUNUVdH dxPlM/bkSb4naJ0CizAewYC3psVp45XNsauME=
Received: by 10.14.52.13 with SMTP id d13mr7655734eec.11.1296516936451; Mon, 31 Jan 2011 15:35:36 -0800 (PST)
Received: from gomlefisk.cisco.com (146.84-48-213.nextgentel.com [84.48.213.146]) by mx.google.com with ESMTPS id t5sm16782775eeh.8.2011.01.31.15.35.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 31 Jan 2011 15:35:35 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Ole Troan <otroan@employees.org>
In-Reply-To: <4D473EB9.6010802@brightok.net>
Date: Tue, 01 Feb 2011 00:35:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F0BB162-030F-45EC-B430-9BA9C53A7439@employees.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> <28C56464-559F-431C-8F68-4F0F633992EE@employees.org> <4D4723F5.9000201@brightok.net> <A296A17E-36CC-4E4A-B611-7990FBBD4044@employees.org> <4D472B53.7080400@brightok.net> <86B22269-D7B6-4B1E-978F-51D719B2FB47@employees.org> <4D473262.8060109@brightok.net> <E6019F66-7DC4-4F93-8F8A-19F086B37E02@employees.org> <4D473EB9.6010802@brightok.net>
To: Jack Bates <jbates@brightok.net>
X-Mailer: Apple Mail (2.1082)
Cc: 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: Mon, 31 Jan 2011 23:32:23 -0000

Jack,

>> please see the discussion a month or two ago. the CPE has not
>> information available to request a certain prefix size.
>> 
> 
> CPE has the information available to
> 
> 1) request it's immediate needs if it's virgin

unless the CPE is configured with this information it has no available information to know the size required to number the site behind it.

> 2) request an aggregate of it's needs and all subtending needs if it has active prefix information.
> 
> As I have mentioned, the ability for a CPE to expand it's prefix with the ISP is also of great benefit in this case.

"expanding" the site can only be done either by renumbering or doing flat as in /64s prefix delegation.

>> how the provider deals with delegating prefixes and the size of the
>> prefix is up to provider policy. there is nothing stopping a provider
>> from assigning whatever sized prefix to whatever number of connected
>> CPEs in a single site.
>> 
> 
> A mechanism isn't documented for a variable prefix layout. As you said, the CPE (especially virgin) has no idea what it's future needs might be. If the ISP hands it a large prefix, it has what it has to work with. However, an ISP should be able to support more, handing out portions of a /48 to a customer site regardless of how they connect routers to the ISP.

then hand out /56s to up to 256 CPEs.

>> you cannot expect to rely on a hint in the PD message to determine
>> the size to delegate, nor can the provider depend on multiple IAIDs
>> in the request.
> 
> Depend, no. Which is why I wrote up a rough idea of ISP logic which could compensate for a variety of dumb and smart CPEs. The HINT is useful in making determinations. Lack of a HINT can be answered in a number of ways. As for multiple IAIDs, if CPEs aren't FORCED to support this, we will have problems when delegations are too small for what is required (unless we just want to sit back and proxy-nd everything when we are out of prefix space).

with a /56 a end user site has 2^8 number of prefixes, do we think that will ever run out? if so, he can justify a request for whatever he needs.

you can either do flat delegation and expose the internal topology of the end user site to the SP or you can do aggregated delegation.  you _could_ imagine a CE using multiple IAIDs to request additional bits of address space. but that would complicate sub-delegation a lot. all the proposals I'm aware of are based on a single site prefix being subdelegated...

in any case I don't think there is anything for the Basic IPv6 CE document here. but lots of opportunities for a home networking architecture one, so I look forward to drafts! ;-)

cheers,
Ole