<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.crowcroft-apex-multicast" target="https://datatracker.ietf.org/doc/html/draft-crowcroft-apex-multicast-01">
   <front>
      <title>MAPEX Application level multicast architectural requirements for APEX</title>
      <author initials="J." surname="Crowcroft" fullname="Jon Crowcroft">
         </author>
      <author initials="K." surname="Carlberg" fullname="Ken Carlberg">
         </author>
      <date month="October" day="2" year="2001" />
      <abstract>
	 <t>This is a memo that presents an approach to do application layer
multicast.  Our intention is to present a design that produces a tree
distribution structure within the existing design structure of APEX
and BEEP. It is not our intention to present a design that replaces
multicast at the network layer. Where the need exists (and in
scenarios where it would seem symbiotic), we would find it
constructive to integrate the two technologies and perspective (i.e.,
application later and network layer multicast).
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-crowcroft-apex-multicast-01" />
   
</reference>
