Use of Multicast Across Inter-Domain Peering Points
draft-ietf-mboned-interdomain-peering-bcp-14

Document Type Active Internet-Draft (mboned WG)
Last updated 2017-11-11 (latest revision 2017-10-30)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tim Chown
Shepherd write-up Show (last changed 2017-07-19)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state EDIT
MBONED Working Group                                    P. Tarapore, Ed.
Internet-Draft                                                  R. Sayko
Intended status: Best Current Practice                              AT&T
Expires: May 3, 2018                                         G. Shepherd
                                                                   Cisco
                                                          T. Eckert, Ed.
                                                                  Huawei
                                                             R. Krishnan
                                                          SupportVectors
                                                        October 30, 2017

          Use of Multicast Across Inter-Domain Peering Points
              draft-ietf-mboned-interdomain-peering-bcp-14

Abstract

   This document examines the use of Source Specific Multicast (SSM)
   across inter-domain peering points for a specified set of deployment
   scenarios.  The objective is to describe the setup process for
   multicast-based delivery across administrative domains for these
   scenarios and document supporting functionality to enable this
   process.

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 https://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 May 3, 2018.

Copyright Notice

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

Tarapore, et al.           Expires May 3, 2018                  [Page 1]
Internet-DraftMulticast Across Inter-Domain Peering Points  October 2017

   (https://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Overview of Inter-domain Multicast Application Transport  . .   5
   3.  Inter-domain Peering Point Requirements for Multicast . . . .   6
     3.1.  Native Multicast  . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Peering Point Enabled with GRE Tunnel . . . . . . . . . .   8
     3.3.  Peering Point Enabled with an AMT - Both Domains
           Multicast Enabled . . . . . . . . . . . . . . . . . . . .  10
     3.4.  Peering Point Enabled with an AMT - AD-2 Not Multicast
           Enabled . . . . . . . . . . . . . . . . . . . . . . . . .  12
     3.5.  AD-2 Not Multicast Enabled - Multiple AMT Tunnels Through
           AD-2  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.  Functional Guidelines . . . . . . . . . . . . . . . . . . . .  16
     4.1.  Network Interconnection Transport Guidelines  . . . . . .  16
       4.1.1.  Bandwidth Management  . . . . . . . . . . . . . . . .  16
     4.2.  Routing Aspects and Related Guidelines  . . . . . . . . .  18
       4.2.1.  Native Multicast Routing Aspects  . . . . . . . . . .  19
       4.2.2.  GRE Tunnel over Interconnecting Peering Point . . . .  19
       4.2.3.  Routing Aspects with AMT Tunnels  . . . . . . . . . .  20
       4.2.4.  Public Peering Routing Aspects  . . . . . . . . . . .  22
     4.3.  Back Office Functions - Provisioning and Logging
           Guidelines  . . . . . . . . . . . . . . . . . . . . . . .  23
       4.3.1.  Provisioning Guidelines . . . . . . . . . . . . . . .  24
       4.3.2.  Interdomain Authentication Guidelines . . . . . . . .  25
       4.3.3.  Log Management Guidelines . . . . . . . . . . . . . .  26
     4.4.  Operations - Service Performance and Monitoring
           Guidelines  . . . . . . . . . . . . . . . . . . . . . . .  27
     4.5.  Client Reliability Models/Service Assurance Guidelines  .  29
     4.6.  Application Accounting Guidelines . . . . . . . . . . . .  29
   5.  Troubleshooting and Diagnostics . . . . . . . . . . . . . . .  29
Show full document text