Re: [dhcwg] DHCP over ATM
Van Aken Dirk <Dirk.Van_Aken@Alcatel.be> Wed, 06 March 2002 07:49 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 CAA26704 for <dhcwg-archive@odin.ietf.org>; Wed, 6 Mar 2002 02:49:05 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA20076 for dhcwg-archive@odin.ietf.org; Wed, 6 Mar 2002 02:49:07 -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 CAA20013; Wed, 6 Mar 2002 02:47:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19981 for <dhcwg@optimus.ietf.org>; Wed, 6 Mar 2002 02:47:18 -0500 (EST)
Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26666 for <dhcwg@ietf.org>; Wed, 6 Mar 2002 02:47:15 -0500 (EST)
Received: from bt08sp.cpe.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id g267kbA04722; Wed, 6 Mar 2002 08:46:37 +0100 (MET)
Received: from Alcatel.be (cpws62 [138.203.68.62]) by bt08sp.cpe.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id IAA21863; Wed, 6 Mar 2002 08:46:36 +0100 (MET)
Message-ID: <3C85C95C.7C4BB13A@Alcatel.be>
Date: Wed, 06 Mar 2002 08:46:36 +0100
From: Van Aken Dirk <Dirk.Van_Aken@Alcatel.be>
Organization: Alcatel Bell
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: Jim Rainville <jim@fatboy.rainville.net>
CC: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCP over ATM
References: <000501c1c44e$5e125f00$2900a8c0@mushroom>
Content-Type: multipart/mixed; boundary="------------8F2BC6A5EB2BC660356CC799"
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
Isn't this the same problem as DHCP over point to point links ? i.e. Appart from the AAL5/ATM encapsulation I see no real differences (assuming the DHCP application does not has to run over an NBMA style of ATM network).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
Dirk.
- [dhcwg] DHCP over ATM Jim Rainville
- Re: [dhcwg] DHCP over ATM Van Aken Dirk