Subject: RFC 7152 on Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN)

From: [email-masked]
Date: Mon, 31 Mar 2014 12:46:39 -0700 (PDT)

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

        RFC 7152

        Title:      Requirements for Metro Ethernet Forum 
                    (MEF) Ethernet-Tree (E-Tree) Support in Layer 
                    2 Virtual Private Network (L2VPN) 
        Author:     R. Key, Ed., S. DeLord, F. Jounay,
                    L. Huang, Z. Liu, M. Paul
        Status:     Informational
        Stream:     IETF
        Date:       March 2014
        Mailbox:    [email-masked], 
                    [email-masked], 
                    [email-masked],
                    [email-masked], 
                    [email-masked],
                    [email-masked]
        Pages:      12
        Characters: 22795
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2vpn-etree-reqt-05.txt

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

This document provides functional requirements for the support 
of Metro Ethernet Forum (MEF) Ethernet Tree (E-Tree) in 
multipoint Layer 2 Virtual Private Network solutions (referred 
to as simply "L2VPN").  It is intended that potential solutions 
will use these requirements as guidelines.

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
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 [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC