Automatic Multicast Tunneling
draft-ietf-mboned-auto-multicast-14

Network Working Group                                      G. Bumgardner
Internet-Draft                                                     Cisco
Intended status: Standards Track                           June 12, 2012
Expires: December 14, 2012

                     Automatic Multicast Tunneling
                  draft-ietf-mboned-auto-multicast-14

Abstract

   This document describes Automatic Multicast Tunneling (AMT), a
   protocol for delivering multicast traffic from sources in a
   multicast-enabled network to receivers that lack multicast
   connectivity to the source network.  The protocol uses UDP
   encapsulation and unicast replication to provide this functionality.

   The AMT protocol is specifically designed to support rapid deployment
   by requiring minimal changes to existing network infrastructure.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 14, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Bumgardner              Expires December 14, 2012               [Page 1]
Internet-Draft                     AMT                         June 2012

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Requirements Notation  . . . . . . . . . . . . . . . . . .  5
     3.2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5
     3.3.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  8
     4.1.  General Architecture . . . . . . . . . . . . . . . . . . .  8
     4.2.  General Operation  . . . . . . . . . . . . . . . . . . . . 17
   5.  Protocol Description . . . . . . . . . . . . . . . . . . . . . 32
     5.1.  Protocol Messages  . . . . . . . . . . . . . . . . . . . . 32
     5.2.  Gateway Operation  . . . . . . . . . . . . . . . . . . . . 47
     5.3.  Relay Operation  . . . . . . . . . . . . . . . . . . . . . 62
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 73
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 76
     7.2.  IPv4 Address Prefix Allocation for IGMP Source
           Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 76
   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 77
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 78
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 79
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 79
     10.2. Informative References . . . . . . . . . . . . . . . . . . 79
   Appendix A.  Implementation Notes  . . . . . . . . . . . . . . . . 82
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 85