Re: proxy relay agent
Rajesh Saluja <rsaluja@wipinfo.soft.net> Wed, 06 March 1996 04:25 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00693;
5 Mar 96 23:25 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00689;
5 Mar 96 23:25 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa00402;
5 Mar 96 23:25 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu;
(5.65v3.0/1.1.8.2/29Aug94-0956AM)
id AA18191; Tue, 5 Mar 1996 23:06:45 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4)
id AA00641; Tue, 5 Mar 1996 22:56:44 -0500
Received: from s.wipinfo.soft.net by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA15475; Tue, 5 Mar 1996 22:56:38 -0500
Received: by s.wipinfo.soft.net (4.1/SMI-4.1)
id AA27619; Wed, 6 Mar 96 09:31:44 IST
Received: from comm10 by rolex.rnd.blr (4.1/SMI-4.1)
id AA18780; Wed, 6 Mar 96 09:31:13+050
Received: (from rsaluja@localhost) by comm10 (8.6.12/8.6.9) id JAA02341;
Wed, 6 Mar 1996 09:26:46 +0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rajesh Saluja <rsaluja@wipinfo.soft.net>
Message-Id: <199603060426.JAA02341@comm10>
Subject: Re: proxy relay agent
To: Jonathan Wenocur <jhw@shiva.com>
Date: Wed, 6 Mar 1996 09:26:45 +0500 (GMT+0500)
Cc: DHCP MAILING LIST <dhcp-v4@bucknell.edu>
In-Reply-To: <199603051557.KAA27287@shiva-dev.shiva.com> from "Jonathan
Wenocur" at Mar 5, 96 10:57:00 am
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
> FYI, Shiva has been shipping a proxy DHCP client in our remote access
> servers for about a year now (this is a proxy client, not a proxy
> relay agent). Finding a consistent way to make DHCP and PPP work
> together is tricky because it depends a lot on the IP stack and PPP
> client at the dial-in client end. Our experience was that there were
> a lot of limitations imposed by the stacks in terms of whether you
> could give them an address after a certain point in their start-up,
> whether the DHCP code could be made to wait for the PPP session to be
> established before it tried to get an address, etc.
>
> -- Jonathan
>
How does it depend on the PPP client at the dial-in client end? Can't the whole
process be handled by the proxy DHCP client as a part of IPCP negotiation?
But the questions arise whether the dial-in client will wait for say 2 minutes
(in the worst case) for IPCP negotiation? Also what action should be taken when
lease for the dial-in client expires (since it could not be renewed for any
reason)? It is not proper to break the connection abruptly. Then what should be
done?
Any thoughts on these issues will be highly appreciated.
Best regards
Rajesh Saluja
- proxy relay agent Hiroto Shibuya
- Re: proxy relay agent Mike Carney - Sun BOS Software
- Re: proxy relay agent Hiroto Shibuya
- Re: proxy relay agent Jonathan Wenocur
- Re: proxy relay agent Jonathan Wenocur
- Re: proxy relay agent Rajesh Saluja
- Re: proxy relay agent Jonathan Wenocur
- Re: proxy relay agent Rajesh Saluja
- Re: proxy relay agent Rajesh Saluja
- Re: proxy relay agent Rajesh Saluja