Somewhat related to this, I wrote this patchset last year:

The idea was to let you configure two AS numbers that a remote peer
can connect to us with, so that the remote peer can be reconfigured
to use a different AS number without the local machine needing to
reconfigured at the same time.

(The converse case, where the local machine will reconnect with a
secondary AS number if connecting with the primary AS number fails is
more involved, and in my use case, I control both endpoints anyway,
so this was sufficient.)

If there's interest in this patchset I can dust it off and try
resubmitting it.

On Sun, Feb 18, 2018 at 01:25:37PM +0000, Adam Król wrote:

> Does BIRD have any support for AS migration mechanism as mentioned in RFC7705 
> Something like 
> I know it can be achieved by functions, but maybe there is already simplier 
> way to get this done.
> Best regards,
> Adam Król

Reply via email to