RE: Comments on IPv6 Prefix Subdelegation

"Erichsen, Kirk" <kirk.erichsen@twcable.com> Mon, 27 July 2009 13:40 UTC

Return-Path: <kirk.erichsen@twcable.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FE5E3A6C96 for <ipv6@core3.amsl.com>; Mon, 27 Jul 2009 06:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level:
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 a7Zrk8mGwUfy for <ipv6@core3.amsl.com>; Mon, 27 Jul 2009 06:40:53 -0700 (PDT)
Received: from pblpas02.twcable.com (pblpas02.twcable.com [204.235.121.150]) by core3.amsl.com (Postfix) with ESMTP id 144BA3A6C82 for <ipv6@ietf.org>; Mon, 27 Jul 2009 06:40:53 -0700 (PDT)
X-SENDER-IP: 10.157.247.213
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.43,276,1246852800"; d="scan'208";a="436532569"
Received: from unknown (HELO prvpmailconn3.corp.twcable.com) ([10.157.247.213]) by pblpas02.twcable.com with ESMTP; 27 Jul 2009 09:40:54 -0400
Received: from PRVPVSMAIL10.corp.twcable.com ([10.157.194.199]) by prvpmailconn3.corp.twcable.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Jul 2009 09:40:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Comments on IPv6 Prefix Subdelegation
Date: Mon, 27 Jul 2009 09:38:34 -0400
Message-ID: <A8C48A0A46A1F443988897887EBB9BD5027099C2@PRVPVSMAIL10.corp.twcable.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Comments on IPv6 Prefix Subdelegation
Thread-Index: AcoOsxtCsct0a+uWTDy1a8yCM3t15wADG61f
References: <6C2F751B-119F-41D6-878C-C4CFBD57DF14@cisco.com>
From: "Erichsen, Kirk" <kirk.erichsen@twcable.com>
To: Fred Baker <fred@cisco.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-OriginalArrivalTime: 27 Jul 2009 13:40:53.0673 (UTC) FILETIME=[DCA39190:01CA0EBF]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 27 Jul 2009 08:50:43 -0700
Cc: draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org, draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 13:40:54 -0000

Fred,
 
Organizationally, I agree with your asersion that referencing another document to describe the sub-delegation behavior gives some wiggle room.
 
-KE

________________________________

From: Fred Baker [mailto:fred@cisco.com]
Sent: Mon 7/27/2009 6:09 AM
To: IETF IPv6 Mailing List
Cc: draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@tools.ietf.org; draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org
Subject: Comments on IPv6 Prefix Subdelegation



Let me make an introductory comment on:
http://tools.ietf.org/html/draft-baker-ipv6-prefix-subdelegation
  "Prefix Sub-delegation in a SOHO/SMB Environment", Fred Baker, 27-
Jul-09,
  <draft-baker-ipv6-prefix-subdelegation-00.txt>

In IPv6 Operations, we have two posted documents right now that 
comment on prefix subdelegation. These are:

http://tools.ietf.org/html/draft-donley-ipv6-cpe-rtr-use-cases-and-reqs
  "Use Cases and Requirements for an IPv6 CPE Router", Chris Donley, 
Deepak
  Kharbanda, John Jason Brzozowski, Yiu Lee, Jason Weil, Kirk 
Erichsen, Lee
  Howard, Jean-Francois Tremblay, 2-Jul-09,
  <draft-donley-ipv6-cpe-rtr-use-cases-and-reqs-00.txt>

http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-cpe-router
  "IPv6 CPE Router Recommendations", Hemant Singh, Wes Beebee, 25-
Mar-09,
  <draft-ietf-v6ops-ipv6-cpe-router-00.txt>

The premise is that an ISP might delegate a PA prefix to a SOHO/SMB 
network, perhaps using DHCP or etc. It would be nice if the prefix 
could be in turn sliced into /64 prefixes and sub-delegated to the 
various LANs in the subsidiary network.

draft-ietf-v6ops-ipv6-cpe-router is trying to recommend to vendors 
that they should build CPE routers in a certain way, and specifies in 
part how sub-delegation would work. In my opinion as WG chair, I would 
rather that it said "do RFC X" than "do the following algorithm", as 
one might want to change the algorithm and the proposed algorithm has 
not been proven operationally. In general, I would like 6man to take 
on the work of describing that algorithm.

I threw draft-baker-ipv6-prefix-subdelegation together very quickly 
for the purpose of saying "I would want you to reference something 
like <this>". That said, it is at least a first step, and may be the 
right answer for the moment. I would appreciate it if 6man could take 
a look at the discussion on sub-delegation in the two CPE drafts and 
at this draft, and decide first whether the draft is a reasonable 
first step toward solving the problem that the CPE drafts target, and 
then further decide whether and with what authors they would like to 
finish that discussion. I'm throwing no personal ego in here - if 
someone else would like to respond to the question, less work on my 
part sounds good to me.

Your opinions, please...


This E-mail and any of its attachments may contain Time Warner
Cable proprietary information, which is privileged, confidential,
or subject to copyright belonging to Time Warner Cable. This E-mail
is intended solely for the use of the individual or entity to which
it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents
of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any
copy of this E-mail and any printout.