MP_UNREACH_NLRI RFC8277 compatibility

[Ondrej Zajicek]

On Fri, Jun 29, 2018 at 04:26:46PM +0300, Vadim Fedorenko wrote:
> Hi!
> According to RFC 8277, NLRI for withdrawal contains 3 fields: Length,
> Compatibility and Prefix.
> "Upon transmission, the Compatibility field SHOULD be set to 0x800000.Upon
> reception, the value of the Compatibility field MUST be ignored."
> Right now, BIRD 2.0.2 checks Compatibility field for value 0x800000, and
> this is not compatible with RFC, and at least Juniper MX do not set this
> field to 0x800000, and BGP session between BIRD and Juniper resets with
> Malformed Attribute List.
> Attached patch fixes this behavior.

Hi

Thanks, will merge that. The current code is based on RFC 3107, which
was vague in many ways, and we did not yet reviewed it w.r.t RFC 8277.

-- 
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: 195 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180629/2bba039e/attachment.sig>