[dhcwg] DHCP over ATM
"Jim Rainville" <jim@fatboy.rainville.net> Tue, 05 March 2002 14:19 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 JAA00996 for <dhcwg-archive@odin.ietf.org>; Tue, 5 Mar 2002 09:19:46 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA06353 for dhcwg-archive@odin.ietf.org; Tue, 5 Mar 2002 09:19:47 -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 JAA06190; Tue, 5 Mar 2002 09:16:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06171 for <dhcwg@optimus.ietf.org>; Tue, 5 Mar 2002 09:16:30 -0500 (EST)
Received: from fatboy.rainville.net (IDENT:root@fatboy.rainville.net [216.174.196.34]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00799 for <dhcwg@ietf.org>; Tue, 5 Mar 2002 09:16:28 -0500 (EST)
Received: from mushroom ([192.168.0.41]) by fatboy.rainville.net (8.11.0/8.8.7) with ESMTP id g25FMTh07319 for <dhcwg@ietf.org>; Tue, 5 Mar 2002 07:22:29 -0800
From: Jim Rainville <jim@fatboy.rainville.net>
To: dhcwg@ietf.org
Date: Tue, 05 Mar 2002 06:01:51 -0800
Message-ID: <000501c1c44e$5e125f00$2900a8c0@mushroom>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C1C40B.4FEF1F00"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Subject: [dhcwg] DHCP over ATM
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 - I know DHCP was designed to work over a broadcast media but I need to do dynamic IP allocation over an ATM network. I have bought an off the shelf DHCP implementation that does not support this but the modifications should be fairly straight forward. My plan is to use a predefined vpi/vci for an end device to send its DHCP request. The DHCP server will know this is a DHCP request because of the vpi/vci it came in on. The server will also know how to route it back to the end device because it will know which physical interface it came in on. My question is this: Is there a standards defined vpi/vci to do this? Right now my company is making the end device as well as the server but we may have to work with third party vendors in the future so a standard vpi/vci would be nice. Thanks. Jim
- [dhcwg] DHCP over ATM Jim Rainville
- Re: [dhcwg] DHCP over ATM Van Aken Dirk