Skip to main content

An Overview of Source-Specific Multicast (SSM)

The information below is for an old version of the document that is already published as an RFC.
Document Type This is an older version of an Internet-Draft that was ultimately published as an RFC.
Author Supratik Bhattacharya
Last updated 2015-10-14 (Latest revision 2003-05-01)
Stream Internet Engineering Task Force (IETF)
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3569 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Alex D. Zinin
IESG note In Authors' 48 Hours
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3569

        Title:      An Overview of Source-Specific Multicast (SSM)
        Author(s):  S. Bhattacharyya, Ed.
        Status:     Informational
        Date:       July 2003
        Pages:      14
        Characters: 29387
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ssm-overview-05.txt


The purpose of this document is to provide an overview of 
Source-Specific Multicast (SSM) and issues related to its deployment.
It discusses how the SSM service model addresses the challenges faced
in inter-domain multicast deployment, changes needed to routing
protocols and applications to deploy SSM and interoperability issues
with current multicast service models.

This document is the product of the Source-Specific Multicast Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.