Route reflector not setting originator_id

[Ondrej Zajicek]

On Thu, Jul 16, 2015 at 04:29:12PM -0700, Evelio VILA wrote:
> Hello,
> 
> I have a very simple setup with one rr and one rr client.
> 
> Im not seeing  ORIGINATOR_ID nor  CLUSTER_LIST attributes appended to the
> updates sent to the rr client. Aren't those supposed to be mandatory per
> RFC 4456 ?

Hello

I am not sure what is your exact setting, but ORIGINATOR_ID and CLUSTER_LIST
are set when the route is reflected on route reflector. They are not set when
the route is locally originated on a route reflector. AFAIK RFC 4456 does
not specify such case, but it probably makes sense to add these attributes
even in this case.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20150717/4d4a611b/attachment.asc>