RE: Comments on IPv6 Prefix Subdelegation

"Stark, Barbara" <bs7652@att.com> Wed, 29 July 2009 21:04 UTC

Return-Path: <bs7652@att.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 3BC0F3A6BDB for <ipv6@core3.amsl.com>; Wed, 29 Jul 2009 14:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.603
X-Spam-Level:
X-Spam-Status: No, score=-105.603 tagged_above=-999 required=5 tests=[AWL=0.996, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 UM8zvuUScUBs for <ipv6@core3.amsl.com>; Wed, 29 Jul 2009 14:04:07 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id DAFD63A6F90 for <ipv6@ietf.org>; Wed, 29 Jul 2009 14:03:43 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-15.tower-121.messagelabs.com!1248901423!27764532!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [144.160.20.53]
Received: (qmail 30623 invoked from network); 29 Jul 2009 21:03:44 -0000
Received: from sbcsmtp6.sbc.com (HELO mlph073.enaf.sfdc.sbc.com) (144.160.20.53) by server-15.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Jul 2009 21:03:44 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlph073.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n6TL3hn2002488; Wed, 29 Jul 2009 17:03:43 -0400
Received: from 01GAF5142010624.AD.BLS.COM (01GAF5142010624.ad.bls.com [139.76.131.91]) by mlph073.enaf.sfdc.sbc.com (8.14.3/8.14.3) with SMTP id n6TL3cGc002411; Wed, 29 Jul 2009 17:03:38 -0400
Received: from 01NC27689010627.AD.BLS.COM ([90.144.44.202]) by 01GAF5142010624.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Jul 2009 17:03:37 -0400
Received: from 01NC27689010641.AD.BLS.COM ([90.144.44.103]) by 01NC27689010627.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Jul 2009 17:03:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Comments on IPv6 Prefix Subdelegation
Date: Wed, 29 Jul 2009 17:03:34 -0400
Message-ID: <7582BC68E4994F4ABF0BD4723975C3FA0F5E5A92@crexc41p>
In-Reply-To: <FBEE7CCE-BE43-40FD-B252-D74CBD6A16CC@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Comments on IPv6 Prefix Subdelegation
Thread-Index: AcoQNBRyiIvwfOsnS06T1UWPuZ3ANwAV/qcw
References: <6C2F751B-119F-41D6-878C-C4CFBD57DF14@cisco.com><2E2FECEBAE57CC4BAACDE67638305F10485093E811@ROCH-EXCH1.corp.pvt><A17AA367-2FC2-4EC8-A3B4-A7EAB1F0C1CC@cisco.com><2E2FECEBAE57CC4BAACDE67638305F10485093E983@ROCH-EXCH1.corp.pvt><74BEE319-C600-4DF5-B784-445B8CDEA770@cisco.com><2E2FECEBAE57CC4BAACDE67638305F1048509A903E@ROCH-EXCH1.corp.pvt> <FBEE7CCE-BE43-40FD-B252-D74CBD6A16CC@cisco.com>
From: "Stark, Barbara" <bs7652@att.com>
To: Fred Baker <fred@cisco.com>, "Azinger, Marla" <marla.azinger@frontiercorp.com>
X-OriginalArrivalTime: 29 Jul 2009 21:03:37.0994 (UTC) FILETIME=[0B08C6A0:01CA1090]
Cc: draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org, draft-donley-ipv6-cpe-rtr-use-cases-and-reqs@tools.ietf.org, IETF IPv6 Mailing List <ipv6@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 21:04:08 -0000

I'm sorry if the following questions show my ignorance, but, here
goes...

Why does it need to be a dynamic routing protocol? Why not a simple
configuration protocol, like with RFC 4191 or a DHCPv6 option as
suggested in
http://tools.ietf.org/html/draft-dec-dhcpv6-route-option-01? 

Why do the peered routers (such as CPE RTR 1 and 2, in Fig 3) need to
know which routes other routers claim to serve? There shouldn't be
misdirected traffic, if the  routes are known to downstream devices. Or
is it the home/office RTRs (Fig 3) who need to know which prefixes have
been assigned to each other, advertising on their WAN interfaces? It
seems like if the home/office RTRs don't know about each other, it
doesn't really hurt efficiency that much; it'll still work. They'll send
the messages up to the next hop (CPE RTR) serving that prefix, and then
it'll get routed down to the right home/office RTR.

If peered CPE RTRs do need to know each others' routes, why can't they
get it through an RFC 4191 or DHCPv6 method (this would be on the LAN
interface). I realize that there are those who say it's wrong for them
to solicit (RS or DHCPv6) on their LAN interfaces -- but why is it
wrong?

And don't these routes need to get propagated down to the hosts, because
hosts may individually have multiple interfaces (e.g., smartphone with
Wi-Fi and 3G)?
Barbara

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
Of
> Fred Baker
> Sent: Wednesday, July 29, 2009 6:05 AM
> To: Azinger, Marla
> Cc: draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org;
draft-donley-ipv6-
> cpe-rtr-use-cases-and-reqs@tools.ietf.org; IETF IPv6 Mailing List
> Subject: Re: Comments on IPv6 Prefix Subdelegation
> 
> 
> On Jul 29, 2009, at 10:35 AM, Azinger, Marla wrote:
> 
> > Routing in such an environment calls for a routing protocol. Each
> > CPE must run either RIPv6 [RFC2080], IS-IS [RFC5308], or OSPF
> > [RFC5340] on a default route and to the homes interal upstream a
> > static default route. The issues raised in [RFC3704] also apply,
> > meaning that the two CPE routers may each need to observe the source
> > addresses in datagrams  they handle to divert them to the other CPE
> > to handle upstream
> 
> I'll figure something out there. This makes it sound like only the CPE
> routers have to run a routing protocol; in fact, all of the routers in
> the home have to run a routing protocol. But yes, something like that.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------