[PATCH] adding custom options in radv protocol, strict ipv6 regex

[Ondrej Zajicek]

On Mon, Jun 12, 2023 at 01:08:15PM +0200, Alexander Zubkov via Bird-users wrote:
> Hi,
> 
> Currently one can use only a predefined set of advertised options in radv
> protocol, that are supported by bird's configuration. It would be
> convenient to be able to specify other possible options at least manually
> as a blob so one should not wait until it is supported in the code,
> released, etc.

Hi

Merged:

https://gitlab.nic.cz/labs/bird/-/commit/9c81250c04798fd274ae9d77380e93b941ac2d7f

Hopefully there is no requirement for RA options to be sorted by type, at
least i did not find it in RFC 4861.

The only objection from me is that 'other type' option name is kind of
non-descriptive, does not indicate it is related to RA options (nor it is
implicated by context). I do not really have a good idea for alternative,
perhaps just 'custom option'? What do you think?

Could you prepare a patch for documentation?

BTW, why not to use WALK_LIST() in radv_prepare_custom()?
(just noticed in now)

-- 
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."