<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: L3VPN VPNv4 NLRI - Route Reflector Scaling</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>This is made easier by the cisco allowing regular expressions in the extcommunity list,<BR>
an RT scoping policy can be implemented as a result.<BR>
<BR>
------------------------------------------------<BR>
David Freedman<BR>
Group Network Engineering<BR>
Claranet Limited<BR>
<A HREF="http://www.clara.net">http://www.clara.net</A><BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Mark Tinka [<A HREF="mailto:mtinka@globaltransit.net">mailto:mtinka@globaltransit.net</A>]<BR>
Sent: Fri 4/4/2008 11:07<BR>
To: David Freedman<BR>
Cc: nanog@merit.edu<BR>
Subject: Re: L3VPN VPNv4 NLRI - Route Reflector Scaling<BR>
<BR>
On Friday 04 April 2008, David Freedman wrote:<BR>
<BR>
> The downside to this of course is that the RRs spend time<BR>
> discarding prefixes when update time comes around for the<BR>
> PEs.<BR>
<BR>
And also, of course, the fact that you have to maintain the<BR>
Extended communities on the route reflector(s).<BR>
<BR>
Cheers,<BR>
<BR>
Mark.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>