RE: [dhcwg] Enabling ipv6 forwarding with dhcpv6

"Bound, Jim" <jim.bound@hp.com> Tue, 25 May 2004 17:16 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 NAA00998; Tue, 25 May 2004 13:16:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BSfJ0-0000Ed-PA; Tue, 25 May 2004 13:01:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BSec9-0003NG-BN for dhcwg@megatron.ietf.org; Tue, 25 May 2004 12:17:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24037 for <dhcwg@ietf.org>; Tue, 25 May 2004 12:17:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BSec8-0000TF-4i for dhcwg@ietf.org; Tue, 25 May 2004 12:17:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BSeZR-00003S-00 for dhcwg@ietf.org; Tue, 25 May 2004 12:14:30 -0400
Received: from zmamail05.zma.compaq.com ([161.114.64.105]) by ietf-mx with esmtp (Exim 4.12) id 1BSeX8-0007Sl-00 for dhcwg@ietf.org; Tue, 25 May 2004 12:12:06 -0400
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net [16.103.130.103]) by zmamail05.zma.compaq.com (Postfix) with ESMTP id 8073D6707; Tue, 25 May 2004 12:12:05 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.0); Tue, 25 May 2004 12:11:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Enabling ipv6 forwarding with dhcpv6
Date: Tue, 25 May 2004 12:11:39 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B0644C239@tayexc13.americas.cpqcorp.net>
Thread-Topic: [dhcwg] Enabling ipv6 forwarding with dhcpv6
Thread-Index: AcRBdSxLGRZZ1x4HS3KV1DR37tmuegA/WoGw
From: "Bound, Jim" <jim.bound@hp.com>
To: "Cristian Cadar" <Cristian.Cadar@netlab.nec.de>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 25 May 2004 16:11:43.0115 (UTC) FILETIME=[F83515B0:01C44272]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
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
Content-Transfer-Encoding: quoted-printable

Hi Christian,

IPv6 is very clear about Host vs Router.  An interface cannot be both.
So a router interface would not be using a DHCPv6 client is my guess. I
think giving hints to the Host interface of a client that has a router
interface state too is not a good idea.  A UNIX router interface will
get all it needs from being a router.  We had to do this to support
MIPv6 HA on UNIX where I work and the trick is to get all the OSPF,
IS-IS, RIPng, BGP et al updates via routing daemon for that interface.

Does this answer help?

Good question.

/jim 

> -----Original Message-----
> From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On 
> Behalf Of Cristian Cadar
> Sent: Monday, May 24, 2004 5:30 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Enabling ipv6 forwarding with dhcpv6
> 
> Hi ,
> 
> Since there might be clients configured by dhcpv6 with 
> routing capabilities in the network I'm missing the feature 
> of enabling the ipv6 forwarding in dhcpv6. As far as I know 
> the RA does not provide this feature. On a dual-stack UNIX 
> machine there are two different flags to be set for enabling 
> ip forwarding, one for ipv4 and the other for ipv6.
> Is there any way for doing it with dhcp or RA ? I could not find any.
> 
> TNX
> Cristian
> 
> 
> _______________________________________________
> 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