[dhcwg] Prefix delegation issues from Minneapolis
Ralph Droms <rdroms@cisco.com> Sat, 23 March 2002 13:13 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 IAA21359 for <dhcwg-archive@odin.ietf.org>; Sat, 23 Mar 2002 08:13:24 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA21071 for dhcwg-archive@odin.ietf.org; Sat, 23 Mar 2002 08:13:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20680; Sat, 23 Mar 2002 08:10:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20646 for <dhcwg@optimus.ietf.org>; Sat, 23 Mar 2002 08:10:43 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21307 for <dhcwg@ietf.org>; Sat, 23 Mar 2002 08:10:39 -0500 (EST)
Received: from rdroms-w2k.cisco.com (sjc-vpn2-243.cisco.com [10.21.112.243]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA01976; Sat, 23 Mar 2002 08:10:10 -0500 (EST)
Message-Id: <4.3.2.7.2.20020323075001.0357f170@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 23 Mar 2002 07:59:11 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Cc: ipng@sunroof.eng.sun.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Prefix delegation issues from Minneapolis
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
A couple of issues came out of the discussion of the prefix delegation option in Minneapolis: * Disallow reassigning delegated prefix on upstream link (and should this restriction be configurable?) * Allow use of DHCP on NBMA links by reserving a well-known anycast address for client->server messages * Devise a mechanism for prefix delegation through a two-message exchange * Write a specification for a simplified version of DHCP that meets the requirements for prefix delegation; this simplified protocol needs a name that doesn't include the word "Host" I'll kick off discussion on these issues in separate messages on the dhcwg@ietf.org mailing list. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg