RE: Comments on IPv6 Prefix Subdelegation
"Erichsen, Kirk" <kirk.erichsen@twcable.com> Thu, 30 July 2009 15:23 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 A4BAE28C2C0 for <ipv6@core3.amsl.com>; Thu, 30 Jul 2009 08:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level:
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_31=0.6]
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 owtmjb5qocsx for <ipv6@core3.amsl.com>; Thu, 30 Jul 2009 08:23:28 -0700 (PDT)
Received: from pblpas02.twcable.com (pblpas02.twcable.com [204.235.121.150]) by core3.amsl.com (Postfix) with ESMTP id A371928C2BE for <ipv6@ietf.org>; Thu, 30 Jul 2009 08:23:28 -0700 (PDT)
X-SENDER-IP: 10.157.247.213
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.43,295,1246852800"; d="scan'208";a="437876492"
Received: from unknown (HELO prvpmailconn3.corp.twcable.com) ([10.157.247.213]) by pblpas02.twcable.com with ESMTP; 30 Jul 2009 11:23:29 -0400
Received: from PRVPVSMAIL10.corp.twcable.com ([10.157.194.199]) by prvpmailconn3.corp.twcable.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 30 Jul 2009 11:23:29 -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: Thu, 30 Jul 2009 11:21:41 -0400
Message-ID: <A8C48A0A46A1F443988897887EBB9BD5027099EE@PRVPVSMAIL10.corp.twcable.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Comments on IPv6 Prefix Subdelegation
Thread-Index: AcoQ5n1TIYjMKG0LQOSWEX1hob9RvgAQr/JaAAAM8Gs=
References: <C69786CF.B2083%john_brzozowski@cable.comcast.com>
From: "Erichsen, Kirk" <kirk.erichsen@twcable.com>
To: John Jason Brzozowski <john_brzozowski@cable.comcast.com>, Mikael Abrahamsson <swmike@swm.pp.se>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-OriginalArrivalTime: 30 Jul 2009 15:23:29.0621 (UTC) FILETIME=[B11BF050:01CA1129]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 30 Jul 2009 08:30:15 -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: Thu, 30 Jul 2009 15:23:29 -0000
JJB, I'm reading that draft link you just sent out in response to IGP avoidance in multi-router HNs. I for one would like to avoid icky/sticky RIP'y or a heavier IGP if we can at all avoid it. -KE ________________________________ From: John Jason Brzozowski [mailto:john_brzozowski@cable.comcast.com] Sent: Thu 7/30/2009 9:20 AM To: Mikael Abrahamsson; IETF IPv6 Mailing List Cc: draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org; draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@tools.ietf.org Subject: Re: Comments on IPv6 Prefix Subdelegation > From: Mikael Abrahamsson <swmike@swm.pp.se> > Organization: People's Front Against WWW > Date: Thu, 30 Jul 2009 03:21:50 -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: Re: Comments on IPv6 Prefix Subdelegation > > On Thu, 30 Jul 2009, Fred Baker wrote: > >> Um, what does a router do? Look at the example in the text and ask >> yourself if you want an average user (my canonical "average user" being >> my daughter, who wanted me to come to her house to install a camera on >> her computer so she could use it on Skype - "did you try plugging it >> in?") manually installing routes in each of the four routers when they >> could in fact learn them from each other directly? > > So, looking at this from another angle, namely deployment. I'm a router > engineer, I support the use of routing protocols as much as the next > router engineer, but I think a good question to ask is whether most home > CPE vendors think RIP for IPv6 is hard to implement, or if this is > something they consider easy? [jjmb] implementation difficulty is important as is making sure the underlying hardware can support it. Also we may be ok with a routing protocol but what about someone who is not a router engineer? Will it be straightforward enough for everyone else to setup? > > If it's easy to implement RIP for IPv6 then I'm a proponent for that > model. > > Fred, (just checking) the model you're advocating then is that DHCPv6-PD > from the main home CPE (with WAN connection) hands out subnets which are > then announced to all home gateways via RIP(v6) ? > > -- > Mikael Abrahamsson email: swmike@swm.pp.se > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- 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.
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Comments on IPv6 Prefix Subdelegation Fred Baker
- RE: Comments on IPv6 Prefix Subdelegation Erichsen, Kirk
- RE: Comments on IPv6 Prefix Subdelegation Azinger, Marla
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- RE: Comments on IPv6 Prefix Subdelegation Azinger, Marla
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- RE: Comments on IPv6 Prefix Subdelegation Azinger, Marla
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- RE: Comments on IPv6 Prefix Subdelegation Azinger, Marla
- Re: Comments on IPv6 Prefix Subdelegation John Jason Brzozowski
- Re: Comments on IPv6 Prefix Subdelegation John Jason Brzozowski
- RE: Comments on IPv6 Prefix Subdelegation Stark, Barbara
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Re: Comments on IPv6 Prefix Subdelegation Mikael Abrahamsson
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Re: Comments on IPv6 Prefix Subdelegation Ole Troan
- Re: Comments on IPv6 Prefix Subdelegation Ole Troan
- Re: Comments on IPv6 Prefix Subdelegation Ole Troan
- Re: Comments on IPv6 Prefix Subdelegation Yiu L. Lee
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- RE: Comments on IPv6 Prefix Subdelegation Jason.Weil
- Re: Comments on IPv6 Prefix Subdelegation John Jason Brzozowski
- Re: Comments on IPv6 Prefix Subdelegation Yiu L. Lee
- Re: Comments on IPv6 Prefix Subdelegation John Jason Brzozowski
- Re: Comments on IPv6 Prefix Subdelegation John Jason Brzozowski
- RE: Comments on IPv6 Prefix Subdelegation Erichsen, Kirk
- Re: Comments on IPv6 Prefix Subdelegation John Jason Brzozowski
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Re: Comments on IPv6 Prefix Subdelegation Fred Baker
- Re: Comments on IPv6 Prefix Subdelegation John Jason Brzozowski
- Re: Comments on IPv6 Prefix Subdelegation Aleksi Suhonen