Support of the PREF64 option in RAdv protocol (RFC 8781)

[Martin Huněk]

Hi,

It would be great if it were supported. However, it seems that there is no working server-side implementation so far.

I've spoken with Jen Linkova at IETF 113, and she said that there is some WIP in Juniper to add support for that, but I do not know what is current state of things.

There is one workaround from Lorenzo Colitti (I think) that was sent to the v6ops WG mailing list. It was done on OpenWRT by sending otherwise empty RA with only PREF64 information. This way, it was possible to convince Android to detect PREF64 without interfering with IPv6 routing provided by the usual RA daemon.

The proposed standard is the official standard as it is in the Standards track ...

Best Regards,
Martin Hunek

Dne pondělí 21. listopadu 2022 19:18:02 CET, Tom Herbers via Bird-users napsal(a):
> Hi,
> 
> has anyone already looked into adding support for the PREF64 Option
> into the RAdv protocol? So far i haven't found any mention of that
> option in any context with BIRD.
> 
> The purpose of the option is to inform clients which NAT64 Prefix they
> should use.
> 
> It's proposed in RFC 8781 [1], but apparently not yet an official
> standard.
> 
> Hoewer, there seems to be already some Client Support [2][3].
> 
> 
> Best Regards,
> 
> Tom Herbers
> 
> 
> [1] https://datatracker.ietf.org/doc/html/rfc8781
> [2]
> https://blog.apnic.net/2022/11/21/deploying-ipv6-mostly-access-networks/
> [3] https://nlnog.net/static/nlnogday2022/NLNOG_Ondrej.pdf
> 
> 
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20221122/643f7688/attachment.sig>