[169638] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: BGP attributes through IGP

daemon@ATHENA.MIT.EDU (Saku Ytti)
Fri Mar 7 02:12:45 2014

Date: Fri, 7 Mar 2014 09:11:50 +0200
From: Saku Ytti <saku@ytti.fi>
To: nanog@nanog.org
In-Reply-To: <B2C1BAE1-021D-435A-9B22-5B56F4FA1BA4@gdt.id.au>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On (2014-03-07 10:49 +1030), Glen Turner wrote:

> That's pretty much what the OSPF tag and the BGP's synchronisation with OSPF were originally intended for.

1403 (1364) is historic and never referenced by OSPF standard. Original
intention for external tag is unspecified information carried between AS
borders.

> However it's pretty much a design misfeature and you'd be happier with iBGP over a tunnel

Agreed. If this is common requirement, nothing stopping figuring out new
LSA/LSP to properly carry BGP information. Of course won't be solution for
near-term, unless OP controls the edge and uses open source implementation, in
which case he might send this information in opaque LSA.



-- 
  ++ytti


home help back first fref pref prev next nref lref last post