RFC 7080 on Virtual Private LAN Service (VPLS) Interoperability with Provider Backbone Bridges

rfc-editor@rfc-editor.org Fri, 20 December 2013 21:22 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F377A1ADF9B; Fri, 20 Dec 2013 13:22:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level:
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUI7P2vL_7K6; Fri, 20 Dec 2013 13:22:39 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 0E72E1A1F33; Fri, 20 Dec 2013 13:22:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AEAC27FC15A; Fri, 20 Dec 2013 13:22:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7080 on Virtual Private LAN Service (VPLS) Interoperability with Provider Backbone Bridges
From: rfc-editor@rfc-editor.org
Message-Id: <20131220212236.AEAC27FC15A@rfc-editor.org>
Date: Fri, 20 Dec 2013 13:22:36 -0800
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: Fri, 20 Dec 2013 21:22:44 -0000

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

        
        RFC 7080

        Title:      Virtual Private LAN Service (VPLS) 
                    Interoperability with Provider Backbone Bridges 
        Author:     A. Sajassi, S. Salam,
                    N. Bitar, F. Balus
        Status:     Informational
        Stream:     IETF
        Date:       December 2013
        Mailbox:    sajassi@cisco.com, 
                    ssalam@cisco.com, 
                    nabil.n.bitar@verizon.com,  
                    florin.balus@nuagenetworks.net
        Pages:      26
        Characters: 61560
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2vpn-pbb-vpls-interop-06.txt

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

The scalability of Hierarchical Virtual Private LAN Service (H-VPLS)
with Ethernet access networks (RFC 4762) can be improved by
incorporating Provider Backbone Bridge functionality in the VPLS
access.  Provider Backbone Bridging has been standardized as IEEE
802.1ah-2008.  It aims to improve the scalability of Media Access
Control (MAC) addresses and service instances in Provider Ethernet
networks.  This document describes different interoperability
scenarios where Provider Backbone Bridge functionality is used in
H-VPLS with Ethernet or MPLS access network to attain better
scalability in terms of number of customer MAC addresses and number of
service instances.  The document also describes the scenarios and the
mechanisms for incorporating Provider Backbone Bridge functionality
within H-VPLS with existing Ethernet access and interoperability among
them.  Furthermore, the document discusses the migration mechanisms
and scenarios by which Provider Backbone Bridge functionality can be
incorporated into H-VPLS with existing MPLS access.

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/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