All things related to multicast

[David Farmer <>]

I think this is relevant to our recent discussions.

In particular this draft says the following, emphasis added by me; 

       o As described in Section 2, the source IP address of the
         multicast stream in the originating AD (AD-1) is known. Under
         this condition, PIM-SSM use is beneficial as it allows the
         receiver's upstream router to directly send a JOIN message to
         the source without the need of invoking an intermediate
         Rendezvous Point (RP). Use of SSM also presents an improved
         threat mitigation profile against attack, as described in
         [RFC4609]. Hence, in the case of inter-domain peering, it is
         recommended to use only SSM protocols; the setup of inter-
         domain peering for ASM (Any-Source Multicast) is not in scope
         for this document.

While this is does not formally deprecate ASM, it is clear that ASM is no longer the recommended approach for inter-domain multicast and SSM is the recommended approach for inter-domain multicast.

Also there was mention of this draft about a month ago;

https://tools.ietf.org/html/draft-acg-mboned-multicast-models-00

I'd like to encourage our community to review these drafts and comment as appropriate.  Further, I think we should seriously evaluate if inter-domain ASM is still needed by and appropriate for our community. 

Thanks.

 

---------- Forwarded message ----------
From: The IESG <>
Date: Wed, Aug 9, 2017 at 2:17 PM
Subject: Last Call: <draft-ietf-mboned-interdomain-peering-bcp-10.txt> (Use of Multicast Across Inter-Domain Peering Points) to Best Current Practice
To: IETF-Announce <>
Cc: , , ,



The IESG has received a request from the MBONE Deployment WG (mboned) to
consider the following document: - 'Use of Multicast Across Inter-Domain
Peering Points'
  <draft-ietf-mboned-interdomain-peering-bcp-10.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
mailing lists by 2017-08-23. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information:
    rfc2784: Generic Routing Encapsulation (GRE) (Proposed Standard - Legacy stream)
    rfc3810: Multicast Listener Discovery Version 2 (MLDv2) for IPv6 (Proposed Standard - IETF stream)
    rfc7450: Automatic Multicast Tunneling (Proposed Standard - IETF stream)
    rfc4609: Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and Enhancements (Informational - IETF stream)
    rfc4271: A Border Gateway Protocol 4 (BGP-4) (Draft Standard - IETF stream)
    rfc4604: Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast (Proposed Standard - IETF stream)
    rfc3376: Internet Group Management Protocol, Version 3 (Proposed Standard - IETF stream)

--

===============================================
David Farmer              
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota  
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================