RE: [dhcwg] RFC 3633 Question

"Bernie Volz \(volz\)" <volz@cisco.com> Fri, 05 January 2007 14:31 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2q6d-0004yF-BX; Fri, 05 Jan 2007 09:31:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2q6c-0004x8-RH for dhcwg@ietf.org; Fri, 05 Jan 2007 09:31:38 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2q6b-00035A-8p for dhcwg@ietf.org; Fri, 05 Jan 2007 09:31:38 -0500
Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-4.cisco.com with ESMTP; 05 Jan 2007 06:31:36 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l05EVaIj010883; Fri, 5 Jan 2007 06:31:36 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l05EVUIp016286; Fri, 5 Jan 2007 06:31:32 -0800 (PST)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 5 Jan 2007 09:31:31 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [dhcwg] RFC 3633 Question
Date: Fri, 05 Jan 2007 09:27:37 -0500
Message-ID: <8E296595B6471A4689555D5D725EBB2102EC1D8E@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] RFC 3633 Question
thread-index: AccwjbuKg5nL4vjLTIm1QOh42b0lVgAR166w
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Archimedes S. Gaviola" <agaviola@infoweapons.com>, dhcwg@ietf.org
X-OriginalArrivalTime: 05 Jan 2007 14:31:31.0436 (UTC) FILETIME=[3176EAC0:01C730D6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5134; t=1168007496; x=1168871496; c=relaxed/relaxed; s=sjdkim8002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20RFC=203633=20Question |Sender:=20; bh=eBkJakcVbyebonATiwoTJoQznL1uZqE50loceD7/fFM=; b=qDpSUm4v/UQ0doWLdFnFN1zKn85RzeSdBKRPQ5VqZZ5jm+gIlh1GRton64B4CPadvdVi5Nbz riz8vLJ7grJzH6chTPpBodMeUY2DHoZXUrhfXMGghfOlaTh0cuFWkWNf;
Authentication-Results: sj-dkim-8; header.From=volz@cisco.com; dkim=pass (si g from cisco.com/sjdkim8002 verified; );
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc:
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>
Content-Type: multipart/mixed; boundary="===============2127075419=="
Errors-To: dhcwg-bounces@ietf.org

In IPv6, routers communicate the routing information via Routing
Advertisements (see RFCs 2461 and 2462). There is no need for DHCPv6 to
do this. (And if you don't have a router, why do you need any routing
information.) This type of functionality (Routing Advertisements)
doesn't really exist in IPv4, hence DHCPv4 needed to communicate this
information.
 
Prefix delegation is primarily design for use by routers, not hosts
(unless a host is also serving as a router).
 
- Bernie

________________________________

From: Archimedes S. Gaviola [mailto:agaviola@infoweapons.com] 
Sent: Friday, January 05, 2007 12:53 AM
To: dhcwg@ietf.org
Subject: [dhcwg] RFC 3633 Question


Hi! Based on RFC 3633 - IPv6 Prefix Options for DHCPv6, the specified
nodes involved in the operation are routers such as the requesting
router - the router that acts as a DHCP client that is requesting for
prefix(es) and a delegating router that acts as the DHCP server. My
question are, thus the option (IA_PD) mentioned here is only intended
when DHCP is running on a router ( a packet forwarding node) and not on
a host ( non-forwarding packet node)?  Is there a DHCPv6 option for
specifying gateway or router just like in IPv4 when a DHCPv6 is running
on a non-forwarding packet node, in which it will provide options for
routers?
 
Thank you very much.
 
Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg