The IP over ATM Mailing List Archive by date

[Andrew Smith <asmith@Baynetworks.COM>]

> From mohta@necom830.cc.titech.ac.jp Tue May 30 23:21:55 1995
> From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
> Subject: Re:  Resilient ATM
> To: asmith@BayNetworks.COM (Andrew Smith)
> Date: Wed, 31 May 95 15:16:16 JST
> Cc: MLG2@trpo6.Tredydev.Unisys.com, ip-atm@matmos.hpl.hp.com

Masataka,

> > 1. Aim for good layer 2 redundancy/failover (e.g. use PNNI signalling)
> >      and use a simple upper layer protocol (e.g. RFC 1577)
> 
> It can't be redundant against the ARP server failure, the
> single-and-only link failure to the ARP server or the single switch
> failure to which the ARP server is directly attached.

With PNNI and Anycast signaling to provide failover to alternative servers
and with a server-server coordination protocol, a very simple upper-layer 
protocol e.g. RFC 1577 between client and server is sufficient. It is
all a question of where you want to put the complexity. 

> As LANE will be there, why do you think we need work to have RFC826-?

As I've stated here before, that could be the $10000000 question ....

> 							Masataka Ohta
> 

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
********************************************************************************