RFC 7117 on Multicast in Virtual Private LAN Service (VPLS)

rfc-editor@rfc-editor.org Tue, 11 February 2014 21:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 97C4C1A0785; Tue, 11 Feb 2014 13:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id XTk-Nzluu3og; Tue, 11 Feb 2014 13:56:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 681B91A0789; Tue, 11 Feb 2014 13:56:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D36DF7FC3AC; Tue, 11 Feb 2014 13:56:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7117 on Multicast in Virtual Private LAN Service (VPLS)
From: rfc-editor@rfc-editor.org
Message-Id: <20140211215606.D36DF7FC3AC@rfc-editor.org>
Date: Tue, 11 Feb 2014 13:56:06 -0800 (PST)
Cc: l2vpn@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2014 21:56:16 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7117

        Title:      Multicast in Virtual Private LAN 
                    Service (VPLS) 
        Author:     R. Aggarwal, Ed.,
                    Y. Kamite, L. Fang,
                    Y. Rekhter, C. Kodeboniya
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2014
        Mailbox:    raggarwa_1@yahoo.com, 
        Pages:      50
        Characters: 126280
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2vpn-vpls-mcast-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7117.txt

RFCs 4761 and 4762 describe a solution for Virtual Private LAN
Service (VPLS) multicast that relies on the use of point-to-point or
multipoint-to-point unicast Label Switched Paths (LSPs) for carrying
multicast traffic.  This solution has certain limitations for certain
VPLS multicast traffic profiles.  For example, it may result in highly
non-optimal bandwidth utilization when a large amount of multicast
traffic is to be transported.

This document describes solutions for overcoming a subset of the
limitations of the existing VPLS multicast solution.  It describes
procedures for VPLS multicast that utilize multicast trees in the
service provider (SP) network.  The solution described in this
document allows sharing of one such multicast tree among multiple
VPLS instances.  Furthermore, the solution described in this document
allows a single multicast tree in the SP network to carry traffic
belonging only to a specified set of one or more IP multicast streams
from one or more VPLS instances.

This document is a product of the Layer 2 Virtual Private Networks Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC