Re: Comments on IPv6 Prefix Subdelegation

John Jason Brzozowski <john_brzozowski@cable.comcast.com> Wed, 29 July 2009 14:45 UTC

Return-Path: <john_brzozowski@cable.comcast.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 8ED273A6DFA for <ipv6@core3.amsl.com>; Wed, 29 Jul 2009 07:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.796
X-Spam-Level:
X-Spam-Status: No, score=-5.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 AGR+rqilJhp7 for <ipv6@core3.amsl.com>; Wed, 29 Jul 2009 07:45:24 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 63FE53A67E7 for <ipv6@ietf.org>; Wed, 29 Jul 2009 07:45:24 -0700 (PDT)
Received: from ([10.52.116.31]) by pacdcimo01.cable.comcast.com with ESMTP id 5503620.47585491; Wed, 29 Jul 2009 10:45:09 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Jul 2009 10:45:09 -0400
Received: from 130.129.17.173 ([130.129.17.173]) by NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.153]) with Microsoft Exchange Server HTTP-DAV ; Wed, 29 Jul 2009 14:45:08 +0000
User-Agent: Microsoft-Entourage/12.17.0.090302
Date: Wed, 29 Jul 2009 16:45:04 +0200
Subject: Re: Comments on IPv6 Prefix Subdelegation
From: John Jason Brzozowski <john_brzozowski@cable.comcast.com>
To: Fred Baker <fred@cisco.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Message-ID: <C6962D10.B1D75%john_brzozowski@cable.comcast.com>
Thread-Topic: Comments on IPv6 Prefix Subdelegation
Thread-Index: AcoOs1Qq6XvClAPNTfCK+p6/dM704QBp9RGv
In-Reply-To: <6C2F751B-119F-41D6-878C-C4CFBD57DF14@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Jul 2009 14:45:09.0803 (UTC) FILETIME=[2BE5CFB0:01CA105B]
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: Wed, 29 Jul 2009 14:45:25 -0000

Only opinion I have is, it seems to makes sense to have the algorithm text
worked in 6man.

The network models standard delegation (non-hierarchical) versus advanced
delegation (hierarchical) would still reside in a CPE requirements draft
right in v6ops?

John
=========================================
John Jason Brzozowski
Comcast Corporation
e) mailto:john_brzozowski@cable.comcast.com
m) 609-377-6594
=========================================


> From: Fred Baker <fred@cisco.com>
> Date: Mon, 27 Jul 2009 08:09:20 -0400
> To: IETF IPv6 Mailing List <ipv6@ietf.org>
> Cc: <draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org>,
> <draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@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...
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------