Deprecating ASM for Interdomain Multicast
draft-ietf-mboned-deprecate-interdomain-asm-02

Document Type Active Internet-Draft (mboned WG)
Last updated 2018-10-22
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Mboned                                                    M. Abrahamsson
Internet-Draft                                                 T-Systems
Intended status: Best Current Practice                          T. Chown
Expires: April 25, 2019                                             Jisc
                                                             L. Giuliano
                                                  Juniper Networks, Inc.
                                                               T. Eckert
                                                                  Huawei
                                                        October 22, 2018

               Deprecating ASM for Interdomain Multicast
             draft-ietf-mboned-deprecate-interdomain-asm-02

Abstract

   This document recommends deprecation of the use of Any-Source
   Multicast (ASM) for interdomain multicast.  It recommends the use of
   Source-Specific Multicast (SSM) for interdomain multicast
   applications and that hosts and routers in these deployments fully
   support SSM.  The recommendations in this document do not preclude
   the continued use of ASM within a single organisation or domain and
   are especially easy to adopt in existing intradomain ASM/PIM-SM
   deployments.

Requirements Language and Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in "Key words for use in
   RFCs to Indicate Requirement Levels" [RFC2119].

   The term IP and IP multicast are used to refer to both IPv4 and IPv6.

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."

Abrahamsson, et al.      Expires April 25, 2019                 [Page 1]
Internet-Draft         Deprecating Interdomain ASM          October 2018

   This Internet-Draft will expire on April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (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.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Multicast service models  . . . . . . . . . . . . . . . .   3
     2.2.  ASM routing protocols . . . . . . . . . . . . . . . . . .   4
       2.2.1.  PIM Sparse Mode (PIM-SM)  . . . . . . . . . . . . . .   4
       2.2.2.  Embedded-RP . . . . . . . . . . . . . . . . . . . . .   5
       2.2.3.  Bidir-RP  . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  SSM Routing protocols . . . . . . . . . . . . . . . . . .   5
   3.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Observations on ASM and SSM deployments . . . . . . . . .   5
     3.2.  Advantages of SSM for interdomain multicast . . . . . . .   6
       3.2.1.  Reduced network operations complexity . . . . . . . .   7
       3.2.2.  No network wide IP multicast group-address management   7
       3.2.3.  Intrinsic source-control security . . . . . . . . . .   8
   4.  Recommendations . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Deprecating use of ASM for interdomain multicast  . . . .   8
     4.2.  Including network support for IGMPv3 / MLDv2  . . . . . .   9
     4.3.  Building application support for SSM  . . . . . . . . . .   9
     4.4.  Developing application guidance: SSM, ASM, service
           discovery . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.5.  Preferring SSM applications intradomain . . . . . . . . .  10
     4.6.  Documenting an ASM/SSM protocol mapping mechanism . . . .  10
     4.7.  Not filtering ASM addressing between domains  . . . . . .  11
     4.8.  Not precluding Intradomain ASM  . . . . . . . . . . . . .  11
     4.9.  Evolving PIM deployments for SSM  . . . . . . . . . . . .  11
Show full document text