Comments on alternatives
yakov@watson.ibm.com Thu, 09 March 1995 15:25 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04061;
9 Mar 95 10:25 EST
Received: from maelstrom.acton.timeplex.com by IETF.CNRI.Reston.VA.US
id aa04041; 9 Mar 95 10:25 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 KAA17055 for
<rolc@maelstrom.timeplex.com>; Thu, 9 Mar 1995 10:20:17 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
Message-Id: <199503091520.KAA17055@maelstrom.acton.timeplex.com>
Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 2335;
Thu, 09 Mar 95 10:19:59 EST
Date: Thu, 9 Mar 95 10:19:59 EST
To: jhalpern@newbridge.com
cc: rolc@maelstrom.timeplex.com
Subject: Comments on alternatives
Joel, >2) NHRP with state exchange could be used in certain situations. If both > ends are BGP routers... a degenerate exchange between the two ... Let's make this clear -- if both ends are BGP routers *NO* NHRP is needed. Yakov.
- Comments on alternatives Joel Halpern
- Comments on alternatives yakov
- Re: Comments on alternatives j.garrett
- Re: Comments on alternatives Curtis Villamizar
- Comments on alternatives yakov