A Common API for Transparent Hybrid Multicast
RFC 7046, “A Common API for Transparent Hybrid Multicast”, is an Experimental document published in December 2013 by M. Waehlisch, T. Schmidt, S. Venaas. The canonical text is published by the RFC Editor.
Abstract
Group communication services exist in a large variety of flavors and technical implementations at different protocol layers. Multicast data distribution is most efficiently performed on the lowest available layer, but a heterogeneous deployment status of multicast technologies throughout the Internet requires an adaptive service binding at runtime. Today, it is difficult to write an application that runs everywhere and at the same time makes use of the most efficient multicast service available in the network. Facing robustness requirements, developers are frequently forced to use a stable upper-layer protocol provided by the application itself. This document describes a common multicast API that is suitable for transparent communication in underlay and overlay and that grants access to the different flavors of multicast. It proposes an abstract naming scheme that uses multicast URIs, and it discusses mapping mechanisms between different namespaces and distribution technologies. Additionally, this document describes the application of this API for building gateways that interconnect current Multicast Domains throughout the Internet. It reports on an implementation of the programming Interface, including service middleware. This document is a product of the Scalable Adaptive Multicast (SAM) Research Group.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 7046 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7045 Transmission and Processing of IPv6 Extension Headers
- RFC 7047 The Open vSwitch Database Management Protocol
- RFC 7043 Resource Records for EUI-48 and EUI-64 Addresses in the DNS
- RFC 7049 Concise Binary Object Representation
- RFC 7042 IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters
- RFC 7050 Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis
- RFC 7041 Extensions to the Virtual Private LAN Service Provider Edge Model for Provider Backbone Bridging
- RFC 7051 Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix