RFC 6517 on Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN Solution
rfc-editor@rfc-editor.org Mon, 20 February 2012 22:59 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D39821E8063; Mon, 20 Feb 2012 14:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.012
X-Spam-Level:
X-Spam-Status: No, score=-104.012 tagged_above=-999 required=5 tests=[AWL=1.065, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zg-aznXvgXG5; Mon, 20 Feb 2012 14:59:46 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id EFEF721E8069; Mon, 20 Feb 2012 14:59:42 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8F7A5B1E017; Mon, 20 Feb 2012 14:54:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6517 on Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN Solution
From: rfc-editor@rfc-editor.org
Message-Id: <20120220225438.8F7A5B1E017@rfc-editor.org>
Date: Mon, 20 Feb 2012 14:54:38 -0800
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Mon, 20 Feb 2012 22:59:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6517
Title: Mandatory Features in a Layer 3
Multicast BGP/MPLS VPN Solution
Author: T. Morin, Ed.,
B. Niven-Jenkins, Ed.,
Y. Kamite, R. Zhang,
N. Leymann, N. Bitar
Status: Informational
Stream: IETF
Date: February 2012
Mailbox: thomas.morin@orange.com,
ben@niven-jenkins.co.uk,
y.kamite@ntt.com,
raymond.zhang@alcatel-lucent.com,
n.leymann@telekom.de,
nabil.n.bitar@verizon.com
Pages: 41
Characters: 102395
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l3vpn-mvpn-considerations-06.txt
URL: http://www.rfc-editor.org/rfc/rfc6517.txt
More that one set of mechanisms to support multicast in a layer 3
BGP/MPLS VPN has been defined. These are presented in the documents
that define them as optional building blocks.
To enable interoperability between implementations, this document
defines a subset of features that is considered mandatory for a
multicast BGP/MPLS VPN implementation. This will help implementers
and deployers understand which L3VPN multicast requirements are best
satisfied by each option. This document is not an Internet Standards Track
specification; it is published for informational purposes.
This document is a product of the Layer 3 Virtual Private Networks 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
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