The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-Apr> msg00055



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

draft-ietf-ipatm-encaps-00.txt

  • From: Grenville Armitage <gja@thumper.bellcore.com>
  • Date: Wed, 26 Apr 1995 11:20:36 -0400
  • CC: asmith@Baynetworks.COM, ip-atm@matmos.hpl.hp.com, gja@thumper.bellcore.com


Greg,
	[..]
>>    4.) market uncertainty (LAN emulation is starting to look a lot better!)

I'm intrigued by this comment, given your dislike of different encaspulations.
LANE is nothing if not different, and is not really a solution for
people who have complex IPmc requirements. Lets be a little realistic
here and compare apples with apples, ok? Or to put it another way,
if you can build hardware to do LANE and rfc1483, then you've already
mastered the art of multiple encaps., so what's the problem?

>>Last year, I thought we agreed that our "long-term intention" was
>>(as an option) null encapsulation.

This also puzzles me. It has _always_ been an option for people
to use VC muxing - just not the default.

gja