IETF Logo Mail Archive

Routing over Demand Circuits

Tony Li <tli@cisco.com> Wed, 18 August 1993 17:12 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07975; 18 Aug 93 13:12 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07971; 18 Aug 93 13:12 EDT
Received: from atlas.xylogics.com by CNRI.Reston.VA.US id aa16596; 18 Aug 93 13:12 EDT
Received: by atlas.xylogics.com id AA29120 (5.65c/UK-2.1-930726); Wed, 18 Aug 1993 13:11:16 -0400
Received: from lager.cisco.com by atlas.xylogics.com with SMTP id AA08396 (5.65c/UK-2.1-930726); Wed, 18 Aug 1993 13:11:09 -0400
Received: by lager.cisco.com id AA22060 (5.67a/IDA-1.5 for ietf-rip@xylogics.com); Wed, 18 Aug 1993 10:10:32 -0700
Date: Wed, 18 Aug 1993 10:10:32 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Li <tli@cisco.com>
Message-Id: <199308181710.AA22060@lager.cisco.com>
To: gerry@spider.co.uk
Cc: gerry@spider.co.uk, ietf-rip@xylogics.com, tli@cisco.com
In-Reply-To: Gerry Meyer's message of Wed, 18 Aug 93 17:06:05 +0100 <20592.9308181606@orbweb.spider.co.uk>
Subject: Routing over Demand Circuits

   Msecs?  Wish I could use your X.25 net.

You just did.  It has no X.25 in it.  ;-)

   >Let's not fix RIP as it's clearly not a better solution.

   It is the *only* applicable solution today to routing many protocols
   over demand circuits.

Good.  Then let's use TCP as it's the *ONLY* tractable solution today
to implementing your proposal.  By "tractable", it's the only one that
cisco is willing to implement.  It's your choice.

Tony

v2.23.0 | Report a Bug | By Email