Re: NHRP for the router-to-router case (somewhat shorter message)

Yakov Rekhter <yakov@cisco.com> Tue, 18 July 1995 18:48 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13325; 18 Jul 95 14:48 EDT
Received: from [204.249.96.18] by IETF.CNRI.Reston.VA.US id aa13321; 18 Jul 95 14:48 EDT
Received: from maelstrom.acton.timeplex.com (maelstrom.nexen.com [204.249.97.5]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id OAA03645; Tue, 18 Jul 1995 14:34:00 -0400
Received: (from root@localhost) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) id OAA28657 for rolc-out; Tue, 18 Jul 1995 14:27:33 -0400
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) with ESMTP id OAA28642 for <rolc@nexen.com>; Tue, 18 Jul 1995 14:27:22 -0400
Received: from hubbub.cisco.com (hubbub.cisco.com [198.92.30.32]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id OAA03455 for <rolc@nexen.com>; Tue, 18 Jul 1995 14:27:20 -0400
Received: from puli.cisco.com (puli.cisco.com [171.69.1.174]) by hubbub.cisco.com (8.6.10/CISCO.GATE.1.1) with SMTP id LAA04725; Tue, 18 Jul 1995 11:24:45 -0700
Message-Id: <199507181824.LAA04725@hubbub.cisco.com>
To: Juha Heinanen <jh@lohi.dat.tele.fi>
cc: asmith@baynetworks.com, bcole@cisco.com, nfinn@cisco.com, rolc@nexen.com
Subject: Re: NHRP for the router-to-router case (somewhat shorter message)
In-reply-to: Your message of "Sat, 15 Jul 95 10:14:50 +0200." <199507150714.KAA08968@lohi.dat.tele.fi>
Date: Tue, 18 Jul 95 11:24:44 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yakov Rekhter <yakov@cisco.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/

Juha,

> i fully agree with andrew.  my position has always been that the
> router-to-router case should not complicate the host-to-host and
> host-to-router cases.  so lets leave the the router-to-router case for
> another document and clean the current draft of all complications that
> it creates.

That is a fine idea. 

Yakov.