[rfc-dist] RFC 4609 on Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and Enhancements
rfc-editor at rfc-editor.org
Fri Oct 13 19:19:23 PDT 2006
A new Request for Comments is now available in online RFC libraries.
Title: Protocol Independent Multicast - Sparse
Mode (PIM-SM) Multicast Routing Security Issues
Author: P. Savola, R. Lehtonen,
Date: October 2006
Mailbox: psavola at funet.fi,
rami.lehtonen at teliasonera.com,
dmm at 1-4-5.net
I-D Tag: draft-ietf-mboned-mroutesec-04.txt
This memo describes security threats for the larger (intra-domain or
inter-domain) multicast routing infrastructures. Only Protocol
Independent Multicast - Sparse Mode (PIM-SM) is analyzed, in its
three main operational modes: the traditional Any-Source Multicast
(ASM) model, the source-specific multicast (SSM) model, and the ASM
model enhanced by the Embedded Rendezvous Point (Embedded-RP)
group-to-RP mapping mechanism. This memo also describes enhancements
to the protocol operations that mitigate the identified threats. This
memo provides information for the Internet community.
This document is a product of the MBONE Deployment
Working Group of the IETF.
INFORMATIONAL: 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist