Re: server-to-server protocols

"Hibbs, R Barr (rbhibbs)" <rbhibbs@pbsrv02.isp.pacbell.com> Sat, 12 April 1997 01:45 UTC

Received: from cnri by ietf.org id aa24339; 11 Apr 97 21:45 EDT
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa24300; 11 Apr 97 21:45 EDT
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA09288; Fri, 11 Apr 1997 21:07:27 -0400
Date: Fri, 11 Apr 1997 21:07:27 -0400
Message-Id: <9704120024.AA01311@ns.PacBell.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: "Hibbs, R Barr (rbhibbs)" <rbhibbs@pbsrv02.isp.pacbell.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: server-to-server protocols
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Worldtalk (NetConnex V4.00a)/MIME


Ted--

I agree wholeheartedly about the length of time developing a 
server-to-server protocol could take if we get bogged down trying to solve 
essentially unsolvable problems, but I think if we don't address the 
question, it will simply arise later to confound us.

 --Barr

 ----------
From: dhcp-v4
To: Multiple recipients of list
Subject: Re: server-to-server protocols
Date: Friday, 11 April, 1997 3:55PM


> The fundamental question that I am asking is 'Just what is the nature of
> what the server-to-server protocol is trying to accomplish?'  In
particular,
> are we attempting to synchronize binding information (alone) among 
servers,
> or are we attempting to enable one server to take-over from another by
> synchronizing configuration information?

Gosh, I *really* hope that we aren't going to try to go beyond
synchronizing binding information.   I'd really like to have the DHCP
Interserver Protocol (DIP :') working before the new millenium.

                      _MelloN_