RE: NT 3.51 dhcp client and server ip address
Pratik Gupta <pratikg@raleigh.ibm.com> Wed, 04 December 1996 22:15 UTC
Received: from cnri by ietf.org id aa02894; 4 Dec 96 17:15 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa22940;
4 Dec 96 17:15 EST
Received: from reef.bucknell.edu by mail.bucknell.edu;
(5.65v3.2/1.1.8.2/17Jul96-0109PM)
id AA10707; Wed, 4 Dec 1996 17:06:19 -0500
Date: Wed, 4 Dec 1996 17:06:19 -0500
Message-Id: <01BBE1FF.0DC8E3C0@starfish.raleigh.ibm.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Pratik Gupta <pratikg@raleigh.ibm.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: NT 3.51 dhcp client and server ip address
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
I believe we should leave it as it is. Most current implementations supporting multiple interfaces correctly, already put in the address of the correct interface. This is just a clarification. Not any change in protocol. A clarification can be issued at a later date which can deal with all the issues relating to multihomed server, multiple logical subnets on a wire etc. As far as fixing some servers is concerned, they will have to do it on their own schedule irrespective of when this clarification is made in this draft or another document. Pratik On Wednesday, December 04, 1996 1:02 PM, Ralph Droms[SMTP:droms@bucknell.edu] wrote: > At 6:54 PM 12/3/96, Ted Lemon wrote: > >In general, it just seems like a bad idea to > >have multiple identifiers referring to the same object. > > Yeah - looks like we blew it by overloading the "identifier" field to also > act as the "return address" field. > > We can either fix it or leave it: > > * Fixing will delay the advancement to Draft Standard, as it would > represent a fairly basic change to the behavior of clients and > servers. > > * Leaving it leaves the problem with multiple identifiers for a single > server - as pointed out by Ted - unfixed. > > Discussion? > > - Ralph > > >
- NT 3.51 dhcp client and server ip address Tim Rowe
- Re: NT 3.51 dhcp client and server ip address Tim Rowe
- Re: NT 3.51 dhcp client and server ip address Ted Lemon
- Re: NT 3.51 dhcp client and server ip address Ken Key
- Re: NT 3.51 dhcp client and server ip address Ted Lemon
- Re: NT 3.51 dhcp client and server ip address Shawn Mamros
- Re: NT 3.51 dhcp client and server ip address Matt Crawford
- Re: NT 3.51 dhcp client and server ip address Shawn Mamros
- Re: NT 3.51 dhcp client and server ip address Ken Key
- Re: NT 3.51 dhcp client and server ip address Ted Lemon
- Re: NT 3.51 dhcp client and server ip address Ralph Droms
- Re: NT 3.51 dhcp client and server ip address Don Coolidge
- Re: NT 3.51 dhcp client and server ip address Mike Carney - SunSoft Internet Engineering
- Re: NT 3.51 dhcp client and server ip address Ted Lemon
- Re: NT 3.51 dhcp client and server ip address Kim Kinnear
- RE: NT 3.51 dhcp client and server ip address Pratik Gupta
- RE: NT 3.51 dhcp client and server ip address Pratik Gupta
- Re: NT 3.51 dhcp client and server ip address Shawn Mamros
- Re: NT 3.51 dhcp client and server ip address Shawn Mamros
- Re: NT 3.51 dhcp client and server ip address Ken Key
- Re: NT 3.51 dhcp client and server ip address Ted Lemon
- Re: NT 3.51 dhcp client and server ip address Ted Lemon
- Re: NT 3.51 dhcp client and server ip address David Lapp
- Re: NT 3.51 dhcp client and server ip address Ken Key
- Re: NT 3.51 dhcp client and server ip address John M. Wobus
- Re: NT 3.51 dhcp client and server ip address Shawn Mamros
- Re: NT 3.51 dhcp client and server ip address Ted Lemon
- Re: NT 3.51 dhcp client and server ip address Ralph Droms
- Re: NT 3.51 dhcp client and server ip address David Lapp
- Re: NT 3.51 dhcp client and server ip address Ted Lemon