RFC 6246 on Virtual Private LAN Service (VPLS) Interoperability with Customer Edge (CE) Bridges
rfc-editor@rfc-editor.org Fri, 10 June 2011 17:27 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D1F11E8152; Fri, 10 Jun 2011 10:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.408
X-Spam-Level:
X-Spam-Status: No, score=-102.408 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y-sIys3-v-Dh; Fri, 10 Jun 2011 10:27:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5EED411E8151; Fri, 10 Jun 2011 10:27:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4BB7D98C51B; Fri, 10 Jun 2011 10:27:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6246 on Virtual Private LAN Service (VPLS) Interoperability with Customer Edge (CE) Bridges
From: rfc-editor@rfc-editor.org
Message-Id: <20110610172735.4BB7D98C51B@rfc-editor.org>
Date: Fri, 10 Jun 2011 10:27:35 -0700
Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 17:27:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6246
Title: Virtual Private LAN Service (VPLS)
Interoperability with Customer Edge (CE) Bridges
Author: A. Sajassi, Ed.,
F. Brockners,
D. Mohan, Ed.,
Y. Serbest
Status: Informational
Stream: IETF
Date: June 2011
Mailbox: sajassi@cisco.com,
fbrockne@cisco.com,
dinmohan@hotmail.com,
yetik_serbest@labs.att.com
Pages: 20
Characters: 51024
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l2vpn-vpls-bridge-interop-06.txt
URL: http://www.rfc-editor.org/rfc/rfc6246.txt
One of the main motivations behind Virtual Private LAN Service (VPLS) is
its ability to provide connectivity not only among customer routers and
servers/hosts but also among customer IEEE bridges. VPLS is expected to
deliver the same level of service that current enterprise users are
accustomed to from their own enterprise bridged networks or their
Ethernet Service Providers.
When customer edge (CE) devices are IEEE bridges, then there are certain
issues and challenges that need to be accounted for in a VPLS network. The
majority of these issues have been addressed in the IEEE 802.1ad
standard for provider bridges and they can be leveraged for VPLS
networks. This document extends the provider edge (PE) model described in
RFC 4664 based on IEEE 802.1ad bridge module, and it illustrates a clear
demarcation between the IEEE bridge module and IETF LAN emulation
module. By doing so, it shows that the majority of interoperability
issues with CE bridges can be delegated to the 802.1ad bridge
module, thus removing the burden on the IETF LAN emulation module
within a VPLS PE. This document is not an Internet Standards Track
specification; it is published for informational purposes.
This document is a product of the Layer 2 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