Skip to main content

Carrying Protocol Independent Multicast - Sparse Mode (PIM-SM) in Any-Source Multicast (ASM) Mode Trees over Multipoint LDP (mLDP)

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: RFC Editor <>,
    mpls mailing list <>,
    mpls chair <>
Subject: Protocol Action: 'Carrying PIM-SM in ASM mode Trees over P2MP mLDP LSPs' to Proposed Standard (draft-ietf-mpls-pim-sm-over-mldp-03.txt)

The IESG has approved the following document:
- 'Carrying PIM-SM in ASM mode Trees over P2MP mLDP LSPs'
  (draft-ietf-mpls-pim-sm-over-mldp-03.txt) as Proposed Standard

This document is the product of the Multiprotocol Label Switching Working

The IESG contact persons are Adrian Farrel and Alia Atlas.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

   When IP multicast trees created by PIM-SM in Any Source Multicast
   (ASM) mode need to pass through an MPLS domain, it may be desirable
   to map such trees to Point-to-Multipoint Label Switched Paths. This
   document describes how to accomplish this in the case where such
   Point-to-Multipoint Label Switched Paths are established using Label
   Distribution Protocol Extensions for Point-to-Multipoint and
   Multipoint-to-Multipoint Label Switched Paths Multipoint LDP (mLDP).

Working Group Summary

  Originally there was an overlap between this document and 
  draft-ietf-mpls-mldp-in-band-wildcard-encoding. This was resolved to the 
  satisfaction of the working group, document shepherd, wg chairs and the 
  authors of both document, before the documents were adopted as working 
  group document.

Document Quality

  We are currently not aware of any implementations of this specification.


   Adrian Farrel is the Responsible AD.
   Loa Andersson is the Document Shepherd.

RFC Editor Note

  There are six authors named on the front of this document. This
  reflects the combined author teams of two merged documents.
  The RFC editor is requested to make an exception to the five-
  author rule for this document.

RFC Editor Note