datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

Multicasting Applications Across Inter-Domain Peering Points
draft-tarapore-mboned-multicast-cdni-07

Document type: Active Internet-Draft (candidate for mboned WG)
Document stream: IETF
Last updated: 2014-10-27
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: Call For Adoption By WG Issued
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

MBONED Working Group                                  Percy S. Tarapore
Internet Draft                                             Robert Sayko
Intended status: BCP                                               AT&T
Expires: April 27, 2015                                   Greg Shepherd
                                                        Toerless Eckert
                                                                  Cisco
                                                           Ram Krishnan
                                                                 Brocade
                                                        October 27, 2014

       Multicasting Applications Across Inter-Domain Peering Points
                draft-tarapore-mboned-multicast-cdni-07.txt

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 April 27, 2015.

Copyright Notice

   Copyright (c) 2014 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 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.

Tarapore, et al         Expires April 27, 2015                 [Page 1]
IETF I-D  Multicasting Applications Across Peering Points    April 2014

   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.

Abstract

   This document examines the process of transporting applications via
   multicast across inter-domain peering points. The objective is to
   describe the setup process for multicast-based delivery across
   administrative domains and document supporting functionality to
   enable this process.

Table of Contents

   1. Introduction...................................................3
   2. Overview of Inter-domain Multicast Application Transport.......4
   3. Inter-domain Peering Point Requirements for Multicast..........5
      3.1. Native Multicast..........................................5
      3.2. Peering Point Enabled with GRE Tunnel.....................7
      3.3. Peering Point Enabled with an AMT - Both Domains Multicast
      Enabled........................................................8
      3.4. Peering Point Enabled with an AMT - AD-2 Not Multicast
      Enabled........................................................9
      3.5. AD-2 Not Multicast Enabled - Multiple AMT Tunnels Through
      AD-2..........................................................11
   4. Supporting Functionality......................................13
      4.1. Network Interconnection Transport and Security Guidelines14
      4.2. Routing Aspects and Related Guidelines...................15
         4.2.1    Native Multicast Routing Aspects..................15
         4.2.2    GRE Tunnel over Interconnecting Peering Point.....16
         4.2.3 Routing Aspects with AMT Tunnels.....................16
      4.3. Back Office Functions - Billing and Logging Guidelines...19
         4.3.1    Provisioning Guidelines...........................19
         4.3.2    Application Accounting Billing Guidelines.........20
         4.3.3    Log Management Guidelines.........................21

[include full document text]