IP Broadcast over ATM Networks (RFC2226)
Original Publication Date: 1997-Oct-01
Included in the Prior Art Database: 2019-Feb-15
Internet Society Requests For Comment (RFCs)
T. Smith: AUTHOR [+1]
This memo describes how the IP multicast service being developed by the IP over ATM working group may be used to support IP broadcast transmission. [STANDARDS-TRACK]
Network Working Group T. Smith Request for Comments: 2226 IBM Corporation Category: Standards Track G. Armitage Lucent Technologies October 1997
IP Broadcast over ATM Networks
Status of this Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (1997). All Rights Reserved.
This memo describes how the IP multicast service being developed by the IP over ATM working group may be used to support IP broadcast transmission. The solution revolves around treating the broadcast problem as a special case of multicast, where every host in the subnet or cluster is a member of the group.
An understanding of the services provided by RFC 2022 is assumed.
The IETF’s first step in solving the problems of running IP over Asynchronous Transfer Mode (ATM) technology is described in RFC 1577 . It provides for unicast communication between hosts and routers within Logical IP Subnets (LISs), and proposes a centralized ATM ARP Server which provides IP to ATM address resolution services to LIS members.
Two classes of IP service were omitted - multicast and broadcast transmissions. Multicasting allows a single transmit operation to cause a packet to be received by multiple remote destinations.
Smith & Armitage Standards Track [Page 1]
RFC 2226 IP Broadcast over ATM Networks October 1997
Broadcasting typically allows a single transmit operation to cause a packet to be received by all IP hosts that are members of a particular ’subnet’.
To address the need for multicast support (represented by transmission to IP addresses in the Class D space), RFC 2022 ("Support for Multicast over UNI 3.0/3.1 based ATM Networks")  was created. This memo creates an analog of the RFC 1577 ARP Server - a new entity known as the MARS (Multicast Address Resolution Server). The MARS operates as a centralized registry and distribution mechanism for mappings between IP multicast addresses and groups of ATM unicast addresses. Host behavior is also defined for establishing and managing point to multipoint VCs, based on the information returned by the MARS, when hosts wish to transmit packets to a multicast group.
This memo aims to show how RFC 2022 may be used to emulate IP broadcast within Logical IP Subnets. While the broadcast technique does not align itself well with the underlying point-to-point nature of ATM, clearly, some applications will still wish to use IP broadcasts. Client-server applications where the client searches for a server by sending out a broadcast is one scenario. Routing protocols, most notably RIP, are other examples.
2. Review of Unicast and Multicast.
Both the unicast and multicast cases take advantage of...