Re: [mpls-linux-devel] Moving forward

[Scott A. Y. <sy...@im...>]

After some more research I think we'll need the VRF infrastructure first since both the BGP transmit and
receive depend on the route distinguisher and import/export route targets defined by the VRF.

Scott Yoder
Support Engineer
ImageStream Internet Solutions, Inc.
E-mail: sy...@im...

James R. Leu wrote:
> Scott,
> 
> This sounds like a great first step.  Please don't hesitate to
> ask questions or bounce ideas off the list.
> 
> On Tue, Jan 06, 2009 at 02:09:08PM -0500, Scott A. Yoder wrote:
>> James R. Leu wrote:
>>> Here are a couple of areas to start, note these are just beginings, not
>>> finished products.  I'm also open to other ideas.  For example if there is a
>>> particular area that you find interesting, challenging, or benifits you
>>> in some way, let me know and I'm sure we can make it work.
>>>
>>> BGP transmit side
>>>     - a VTY interface to creating VPN4 NLRI with tagging info
>>>     - peer with an existing implementation to make sure they
>>>       get added to the peers correct VRF
>>> BGP receive side
>>>     - implement RFC2547 policy interface
>>>     - apply policy to incoming VPN4 NLRI and put the results into
>>>       different quagga tables (not neccessariy VRFs at this point)
>> As much as I'd like to get the label manager foundation done first I'd also like to
>> see some quick results. I think I'm going to start with the VPNV4 exchange to see
>> it working and then go back and finish up the label manager.
>>
>> I haven't done a lot of coding with Quagga so I'm spending some time familiarizing myself
>> with the code. I'll also bounce ideas off of the list as much as possible.
>>
>> Thanks,
>> Scott Yoder
>> ImageStream Internet Solutions, Inc.
>> E-mail: sy...@im...
>