Re: NHS Record extensions seem to be unnecessary

Andrew Smith <asmith@baynetworks.com> Wed, 23 August 1995 22:39 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24518; 23 Aug 95 18:39 EDT
Received: from nexen.nexen.com by IETF.CNRI.Reston.VA.US id aa24514; 23 Aug 95 18:39 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id SAA21111; Wed, 23 Aug 1995 18:23:27 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id SAA20524 for rolc-out; Wed, 23 Aug 1995 18:22:02 -0400
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id SAA20515; Wed, 23 Aug 1995 18:22:00 -0400
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id SAA21105; Wed, 23 Aug 1995 18:21:58 -0400
Received: from BayNetworks.COM ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA29876; Wed, 23 Aug 95 15:20:01 PDT
Received: from milliways-le0 (milliways-le0.synoptics.com) by BayNetworks.COM (4.1/SMI-4.1) id AA19103; Wed, 23 Aug 95 15:20:30 PDT
Received: by milliways-le0 (4.1/2.0N) id AA26642; Wed, 23 Aug 95 15:22:19 PDT
Message-Id: <9508232222.AA26642@milliways-le0>
Date: Wed, 23 Aug 95 15:22:19 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
To: malis@nexen.com, yakov@cisco.com
Subject: Re: NHS Record extensions seem to be unnecessary
Cc: rolc@nexen.com
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

> From owner-rolc@nexen.com Wed Aug 23 15:07:34 1995
> To: "Andrew G. Malis" <malis@nexen.com>
> Cc: rolc@nexen.com
> Subject: Re: NHS Record extensions seem to be unnecessary  
> Date: Wed, 23 Aug 95 14:49:44 PDT
> From: Yakov Rekhter <yakov@cisco.com>
> 
> > >   - NHRP Forward NHS Record Extension
> > >   - NHRP Reverse NHS Record Extension
> > > 
> > > do not serve any useful purposes in NHRP. Therefore I would suggest
> > > to delete them.
> > 
> > I strongly disagree.  I expect these to be invaluable for debugging an
> > implementation, and when tracking down the inevitable operational
> > problems once NHRP has been deployed.
> 
> Fine. Just say that these two options are for debugging.

Isn't this another case of complicating the client-server protocol in 
order to support the server-server interactions? If the NHS is giving
a client the wrong answer then it is that NHS that needs the debugging
help, not the poor client. I can't imagine anyone writing a NHRP-debugging 
application to be run by clients which would include these options.

I suggest mandating that these options not be used by clients but may
be used by NHSs.

I also disagree with including protocol elements to aid debugging an
implementation. Add stuff for diagnosing operational problems, yes but not
to detect software bugs, please.

> Yakov.
> 

Andrew 


********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy Unit				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************