Subject: Fwd: New Version Notification for draft-pmohapat-l3vpn-acceptown-community-00

From: "John G. Scudder" <[email-masked]>
Date: Wed, 11 Jun 2008 15:34:16 -0400

FYI.  We'd be interested in any comments.  We've requested a slot to  
discuss this at the IETF-72 meeting.

--John

Begin forwarded message:

> From: IETF I-D Submission Tool <[email-masked]>
> Date: June 8, 2008 3:47:16 AM GMT-04:00
> To: [email-masked]
> Cc: [email-masked], [email-masked], [email-masked], [email-masked] 
> , [email-masked]
> Subject: New Version Notification for  draft-pmohapat-l3vpn- 
> acceptown-community-00
>
>
> A new version of I-D, draft-pmohapat-l3vpn-acceptown- 
> community-00.txt has been successfuly submitted by Pradosh Mohapatra  
> and posted to the IETF repository.
>
> Filename:	 draft-pmohapat-l3vpn-acceptown-community
> Revision:	 00
> Title:		 BGP ACCEPT_OWN Well-known Community Attribute
> Creation_date:	 2008-06-08
> WG ID:		 Independent Submission
> Number_of_pages: 9
>
> Abstract:
> Under certain conditions it is desirable for a BGP route reflector to
> be able to modify the Route Target list of a VPN route that is
> distributed by the route reflector, enabling the route reflector to
> control how a route originated within one VRF is imported into other
> VRFs.  This technique works effectively as long as the VRF that
> exports the route is not on the same PE as the VRF(s) that import the
> route. However, due to the constraints of the BGP protocol, it does
> not work if the two are on the same PE.
>
> This document describes a modification to the BGP protocol allowing
> this technique to work when the VRFs are on the same PE, allowing the
> technique to be used in a standard manner throughout an autonomous
> system.
>
>
>
> The IETF Secretariat.
>
>