RE: [dhcwg] Router option, in DHCPv6
Ralph Droms <rdroms@cisco.com> Wed, 15 September 2004 08:11 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10852; Wed, 15 Sep 2004 04:11:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7UkL-0004vm-JE; Wed, 15 Sep 2004 04:02:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7UiM-0004AS-PB for dhcwg@megatron.ietf.org; Wed, 15 Sep 2004 04:00:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10209 for <dhcwg@ietf.org>; Wed, 15 Sep 2004 04:00:28 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7UnR-0005bG-DF for dhcwg@ietf.org; Wed, 15 Sep 2004 04:05:45 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 15 Sep 2004 04:14:53 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i8F7xuO9029386; Wed, 15 Sep 2004 03:59:57 -0400 (EDT)
Received: from rdroms-w2k01.cisco.com (sjc-vpn4-561.cisco.com [10.21.82.49]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ALO04973; Wed, 15 Sep 2004 03:59:54 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040915035651.02e5d3b0@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 15 Sep 2004 03:59:51 -0400
To: Anil Kumar Reddy <sakreddy@india.hp.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: RE: [dhcwg] Router option, in DHCPv6
In-Reply-To: <200409150641.MAA24453@iconsrv6.india.hp.com>
References: <000901c49808$78269010$6401a8c0@amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: dhcwg@ietf.org, 'Bernie Volz' <volz@cisco.com>, 'Robert Elz' <kre@munnari.OZ.AU>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Anil - the scenario you describe falls, I think, in the class of scenarios kre described: >But, it might be perhaps useful to be able to configure a particular >router on a net with several - and perhaps different routers for >different hosts, which is something that RAs cannot achieve, so the >option shouldn't necessarily simply be discarded as completely useless. Do we have any reason to believe, at this point, that load balancing through explicit default router assignment will be used in practice? - Ralph At 12:10 PM 9/15/2004 +0530, Anil Kumar Reddy wrote: >Thanks for your responses. Sorry for the delay in my response. > >I have a question : >Take a case of load balancing, where two routers present and > we want to manage/configure few set of hosts (address range) > to use one router and others to use a different one (two > paths), how do we achieve this using RAs ? > >-- >Thanks, >Anil > >: -----Original Message----- >: From: Bernie Volz [mailto:volz@cisco.com] >: Sent: Saturday, September 11, 2004 7:36 PM >: To: 'Robert Elz'; 'Anil Kumar Reddy' >: Cc: dhcwg@ietf.org >: Subject: RE: [dhcwg] Router option, in DHCPv6 >: >: I agree. We do not need this option. >: >: If someone can demonstrate a solid need for this (either a >: list of default routers or list of static routes), we will >: consider this. But if you have no solid use case, this should >: be outside the scope of DHCPv6. >: >: In IPv4, there was no basic mechanism for a host to find >: router(s) and to discover whether addresses are on or off >: link (ICMP messages were added later, but I think they've >: been little used). This is a basic feature of IPv6. >: >: - Bernie >: >: > -----Original Message----- >: > From: dhcwg-bounces@ietf.org >: [mailto:dhcwg-bounces@ietf.org] On Behalf >: > Of Robert Elz >: > Sent: Friday, September 10, 2004 3:00 PM >: > To: Anil Kumar Reddy >: > Cc: dhcwg@ietf.org >: > Subject: Re: [dhcwg] Router option, in DHCPv6 >: > >: > >: > Date: Fri, 10 Sep 2004 19:32:22 +0530 >: > From: "Anil Kumar Reddy" <sakreddy@india.hp.com> >: > Message-ID: <200409101402.TAA29984@iconsrv6.india.hp.com> >: > >: > | I feel, having a router configuration option >: (similar to >: > | DNS, SIP, NIS) would help the client's network >: connectivity >: > | in the absence of RA. >: > >: > As a rationale, that's useless. If there are no RAs, there are no >: > routers, RAs in v6 aren't optional. >: > >: > But, it might be perhaps useful to be able to configure a >: particular >: > router on a net with several - and perhaps different routers for >: > different hosts, which is something that RAs cannot achieve, so the >: > option shouldn't necessarily simply be discarded as completely >: > useless. >: > >: > Whether the benefit in allowing this is worth the extra >: complexity I'm >: > not sure I'd like to take a position on at the minute. >: > >: > kre >: > >: > >: > _______________________________________________ >: > dhcwg mailing list >: > dhcwg@ietf.org >: > https://www1.ietf.org/mailman/listinfo/dhcwg >: > >: >: > > > >_______________________________________________ >dhcwg mailing list >dhcwg@ietf.org >https://www1.ietf.org/mailman/listinfo/dhcwg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Server Unicast Option in DCHPv6 Suman
- RE: [dhcwg] Server Unicast Option in DCHPv6 Bernie Volz
- [dhcwg] Router option, in DHCPv6 Anil Kumar Reddy
- Re: [dhcwg] Router option, in DHCPv6 Robert Elz
- RE: [dhcwg] Router option, in DHCPv6 Bernie Volz
- RE: [dhcwg] Router option, in DHCPv6 Anil Kumar Reddy
- RE: [dhcwg] Router option, in DHCPv6 Ralph Droms