Skip to main content

Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone Bridging
draft-ietf-l2vpn-pbb-vpls-pe-model-07

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    l2vpn mailing list <l2vpn@ietf.org>,
    l2vpn chair <l2vpn-chairs@tools.ietf.org>
Subject: Document Action: 'Extensions to VPLS PE model for Provider Backbone Bridging' to Informational RFC (draft-ietf-l2vpn-pbb-vpls-pe-model-07.txt)

The IESG has approved the following document:
- 'Extensions to VPLS PE model for Provider Backbone Bridging'
  (draft-ietf-l2vpn-pbb-vpls-pe-model-07.txt) as Informational RFC

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

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-l2vpn-pbb-vpls-pe-model/


Ballot Text

Technical Summary

The draft documents extensions to the VPLS PE model 
required to incorporate desirable IEEE PBB (Provider 
Backbone Bridges) components, such as enhanced 
scalability in terms of number of customer MAC 
addresses and number of service instances, whilst 
maintaining the Service Provider alignment of VPLS - 
which has been deployed on a large scale in many 
Service Provider networks. 

Working Group Summary

This document is an L2VPN Working Group document, 
and has been well reviewed in the working group through 
multiple iterations of the draft. It has been essentially stable 
since WG adoption in May 2009. 

Document Quality

The document is concise (13 pages of which about 6 are 
substantive - the rest being introduction, terminology, 
references and acknowledgements) and is stable. 
There are multiple interoperable implementations by 
multiple vendors. 

Personnel

Document Shepherd: Giles Heron (giheron@cisco.com)
Area Director: Stewart Bryant (stbryant@cisco.com) 


RFC Editor Note