Re: [dhcwg] dhcpv6-24: movement detection and Confirm message

Ted Lemon <Ted.Lemon@nominum.com> Sun, 12 May 2002 14:50 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 KAA18797 for <dhcwg-archive@odin.ietf.org>; Sun, 12 May 2002 10:50:03 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA23124 for dhcwg-archive@odin.ietf.org; Sun, 12 May 2002 10:50:14 -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 KAA22962; Sun, 12 May 2002 10:45:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA22936 for <dhcwg@optimus.ietf.org>; Sun, 12 May 2002 10:45:51 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18610 for <dhcwg@ietf.org>; Sun, 12 May 2002 10:45:39 -0400 (EDT)
Received: from green.bisbee.fugue.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id g4CEiWS24919; Sun, 12 May 2002 07:44:32 -0700 (PDT)
Received: from tongpanyi (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id g4CEjdA00337; Sun, 12 May 2002 09:45:39 -0500 (CDT)
Date: Sun, 12 May 2002 09:45:39 -0500
Subject: Re: [dhcwg] dhcpv6-24: movement detection and Confirm message
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v481)
Cc: dhcwg@ietf.org, Ralph Droms <rdroms@cisco.com>, Thomas Narten <narten@us.ibm.com>, "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "Bound, Jim" <Jim.Bound@hp.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <9C422444DE99BC46B3AD3C6EAFC9711B022D2A5E@tayexc13.americas.cpqcorp.net>
Message-Id: <ED753344-65B6-11D6-BABF-00039367340A@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.481)
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

The server administrator will likely configure the DHCP server to know what 
the prefix lengths are for the subnets it serves, so in fact it will know 
prefix lengths, and we can use them.   We shouldn't require the use of them 
in all cases, because the server administrator might _not_ configure the 
DHCP server with a complete list, but we can specify what to do if the DHCP 
server has them, and this will be of genuine use in real-world 
installations.


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg