Re: MCNS Telco Return DHCP Messaging

Mike Carney <> Tue, 15 April 1997 17:24 UTC

Received: from cnri by id aa03049; 15 Apr 97 13:24 EDT
Received: from by CNRI.Reston.VA.US id aa15479; 15 Apr 97 13:24 EDT
Received: from by; (5.65v3.2/ id AA10745; Tue, 15 Apr 1997 13:17:03 -0400
Date: Tue, 15 Apr 1997 13:17:03 -0400
Message-Id: <Roam.SIMC.2.0.Beta.861121436.7767.mwc@atlantic.east>
Precedence: bulk
From: Mike Carney <>
To: Multiple recipients of list <>
Subject: Re: MCNS Telco Return DHCP Messaging
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text

>      When the DHCP_discover message is send it passes through the TRAC and 
>      reaches the DHCP server. But the return path is different. The trick 
>      to make DHCP_offer reach CM via CMTS is:
>           When CM generates DHCPDISCOVER it fills the 'giaddr' with the 
>           address of CMTS. The DHCP proxies (if any) relay the message to 
>           DHCP server without changing the 'giaddr'. DHCP server sends the 
>           offer to 'giaddr' (CMTS). And CMTS sends the DHCPOFFER to CM.
> Is there any DHCP server/proxy implementation that the above method will 
> not work?
> Do you see any problems?
> All ideas/comments/problem scenarios are welcome.

Hi Burcak,
	This should work just fine. 

Mike Carney
SNT Internet Engineering
Sun Microsystems, Inc.
2 Elizabeth Drive
Chelmsford, MA 01824