Application Statement
yakov@watson.ibm.com Fri, 03 March 1995 20:29 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10147;
3 Mar 95 15:29 EST
Received: from maelstrom.acton.timeplex.com by IETF.CNRI.Reston.VA.US
id aa10137; 3 Mar 95 15:29 EST
Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by
maelstrom.acton.timeplex.com (8.6.9/ACTON-MAIN-1.2) with SMTP id PAA17349 for
<rolc@acton.timeplex.com>; Fri, 3 Mar 1995 15:07:10 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
Message-Id: <199503032007.PAA17349@maelstrom.acton.timeplex.com>
Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 9193;
Fri, 03 Mar 95 15:08:02 EST
Date: Fri, 3 Mar 95 15:08:02 EST
To: jbuffum@pobox.wellfleet.com, curtis@ans.net
cc: rolc@acton.timeplex.com
Subject: Application Statement
Ref: Your note of Fri, 03 Mar 1995 14:20:35 -0500
Jeffrey,
>While NHRP is certainly not a panacea for all the worlds routing
>problems, to lobby for language whose only purpose is to denegrate
>this solution as unworthy of deployment is, in my opinion, excessive.
On the other hand stating that
"It is recommended that during Router-to-Router operation, options that
help to detect loops be invoked and NHRP requests be reissued
periodically."
strikes me as wishful thinking. For instance, would you please explain
how any of the options that NHRP has, or how reissuing NHRP requests
periodically would help to solve the looping problem that Joel Halpern
posted to the list about a month ago.
Curtis's observation about the need to avoid non-NBMA paths is also correct.
Saying that "it is advisable to avoid the non-NBMA paths between the routers
where NHRP is being run" falls into the category of wishful thinking as well,
and certainly doesn't match the reality.
>There are a great many cases where NHRP would be very effective and where
>the routing loop problem would not arise.
It would certainly help if you'll enumerate these cases that involve
router-to-router, and explain how NHRP mechanisms would help to prevent
routing loop problem.
Yakov.
- Application Statement dhc2
- Re: Application Statement Curtis Villamizar
- Re: Application Statement dhc2
- Re: Application Statement Jeffrey A. Buffum - Bay Networks
- Application Statement yakov
- Re: Application Statement Curtis Villamizar
- Re: Application Statement j.garrett
- Re: Application Statement Juha Heinanen
- Re: Application Statement Jeffrey A. Buffum - Bay Networks
- Re: Application Statement j.garrett
- Application Statement yakov
- Application Statement yakov
- Re: Application Statement Bruce Cole
- Application Statement yakov
- Re: Application Statement yakov
- Re: Application Statement Bruce Cole
- Re: Application Statement Bruce Cole
- Re: Application Statement j.garrett
- Re: Application Statement Curtis Villamizar
- Re: Application Statement j.garrett
- Re: Application Statement Curtis Villamizar
- Application Statement yakov
- Application Statement yakov
- Re: Application Statement Ross Callon
- Re: Application Statement Ted Matsumura
- Application Statement dhc2