Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks
draft-ietf-l3vpn-gre-ip-2547-05

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: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    l3vpn mailing list <l3vpn@ietf.org>, 
    l3vpn chair <l3vpn-chairs@tools.ietf.org>
Subject: Document Action: 'Use of PE-PE GRE or IP in BGP/MPLS IP 
         Virtual Private Networks' to Informational RFC 

The IESG has approved the following document:

- 'Use of PE-PE GRE or IP in BGP/MPLS IP Virtual Private Networks '
   <draft-ietf-l3vpn-gre-ip-2547-06.txt> as an Informational RFC

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

The IESG contact persons are Mark Townsley and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-gre-ip-2547-06.txt

Ballot Text

Technical Summary
 
   This document describes a variation of BGP/MPLS IP Virtual Private
   Networks (VPNs) in which the outermost MPLS label of a VPN packet
   (the tunnel label) is replaced with either IP or a Generic Routing
   Encapsulation (GRE).  This enables the VPN packets to be carried over
   non-MPLS networks.

Working Group Summary
 
 There was concensus in the WG for this document.
 
Protocol Quality
 
 This document has been reviewed for the IESG by Thomas Narten and Mark
Townsley


IESG Note:

This document proposes an automated mechanism for establishing tunnels
between provider-edge routers in a VPN but does not provide an
automated mechanism for establishing security associations for these
tunnels. Without such a mechanism, this document is not appropriate for
publication on the Internet standards track.

RFC Editor Note