The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-May> msg00008



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

draft-ietf-ipatm-encaps-00.txt (fwd)

  • From: Grenville Armitage <gja@thumper.bellcore.com>
  • Date: Fri, 28 Apr 1995 15:44:42 -0400
  • CC: ip-atm@matmos.hpl.hp.com, gja@thumper.bellcore.com


	[..]
>>My understanding is that it the use of the multicast server, and the
>>consequent packet echos, that are driving the encaps change.

Right.

>>I also
>>understand that there are other approaches to multicast over ATM that don't
>>use a multicast server.

Yes, and until it was demanded at the San Jose IETF that I include
support for multicast servers my I-D was focussed on VC meshes only.

>>I believe another undesirable property is that they
>>apparently force us to consider 1483 & 1577 as experimental, rather than
>>mature.

They have nothing to say about 1577, that is a unicast-only solution.
1483 has been at 'Proposed' standard status for awhile, which is
designed exactly to flesh out problems.

Yes, multicast servers are a problem. However, I got burned at Danvers
for suggesting people throw them away if the reflected packets were
to become a problem. So, the demand is there. Feel free to battle
on, I say.

cheers,
gja