[dhcwg] Question on DHCPV6 RFC draft-ietf-dhc-dhcpv6-26.txt
"Imran Hafeez" <ihafeez@nortelnetworks.com> Wed, 24 July 2002 00:16 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08231 for <dhcwg-archive@odin.ietf.org>; Tue, 23 Jul 2002 20:16:07 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA27023 for dhcwg-archive@odin.ietf.org; Tue, 23 Jul 2002 20:17:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA25597; Tue, 23 Jul 2002 19:39:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04789 for <dhcwg@optimus.ietf.org>; Fri, 19 Jul 2002 10:58:35 -0400 (EDT)
Received: from zrc2s0jx.nortelnetworks.com (zrc2s0jx.nortelnetworks.com [47.103.122.112]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10641 for <dhcwg@ietf.org>; Fri, 19 Jul 2002 10:57:36 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g6JEwDi00055 for <dhcwg@ietf.org>; Fri, 19 Jul 2002 09:58:13 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id <KKXY2Q25>; Fri, 19 Jul 2002 09:57:59 -0500
Message-ID: <EF1056F8EB4ED511B8FB0002A56079D40384B5B5@zrc2c014.us.nortel.com>
From: Imran Hafeez <ihafeez@nortelnetworks.com>
To: "'dhcwg@ietf.org'" <dhcwg@ietf.org>
Date: Fri, 19 Jul 2002 09:57:58 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C22F34.ABA9C4F0"
Subject: [dhcwg] Question on DHCPV6 RFC draft-ietf-dhc-dhcpv6-26.txt
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Hi, In the DHCPV6 RFC the IAADDR option specifies an IPV6 address but without any indication to where the prefix & interface id starts and ends. However if you read Radius RFC's for IPV6, they explicitly specify this information, in otherwords they break the IPV6 address into its components. Does anyone know why it was done this way ? Wouldn't this have any potential implications to the way DHCPV6 could be configured ? thanx in advance, Imran Hafeez
- [dhcwg] Question on DHCPV6 RFC draft-ietf-dhc-dhc… Imran Hafeez