The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1996-Mar> msg00187



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

MARS ipmc-12 suggestions

  • From: asmith@Baynetworks.COM (Andrew Smith)
  • Date: Tue, 26 Mar 96 15:34:57 PST
  • Cc: ip-atm@nexen.com

> From gja@thumper.bellcore.com Tue Mar 26 15:20:14 1996
> To: asmith@BayNetworks.COM (Andrew Smith)
> Cc: gja@bellcore.com, ip-atm@nexen.com, gja@thumper.bellcore.com
> Subject: Re: MARS ipmc-12 suggestions 
> In-Reply-To: Your message of Tue, 26 Mar 1996 14:31:10 -0800.
>              <9603262231.AA09006@milliways-le0.engwest> 
> Date: Tue, 26 Mar 1996 18:14:46 -0500
> From: Grenville Armitage <gja@bellcore.com>

Grenville,

> This is ipmc-12 here. In ipmc-12 we actually _assume_ that there
> are no current solutions to the load-sharing-multiple-MCS-per-group
> problem. ipmc-12 hardly says all that much about MCSs anyway, punting
> that to a separate document on "What an MCS should or should not expect"
> (which is what I'd encouraged Rajesh to be developing).
>
> That's where you tighten up (or explicitly allow) certain MCSs behaviours
> (to fill in the gaps I _deliberately_ tried to leave in ipmc-12).

The ipmc-12 version that I've got has a bunch of rules and regulations
about the MARS<->MCS interface: what I hear you saying is that ipmc-13 
will remove these, correct?

...
> I'm sorry if I've not been clear on the strategy of follow-on
> documents I'd envisaged when I left gaps in ipmc-12.
...
> cheers,
> gja
> 

Andrew

********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************