[dns-wg] Stale restricted IPv6 information at Verisign/IANA

[Bernhard Schmidt <]

Good evening,

perhaps slightly off-topic, but nethertheless... I've been trying to 
readd an AAAA glue record to one of my nameservers in .net after the 
server moved from M"net space (2001:a60::/32) to TNIB (2001:1b18::/32). 
It worked before, after the move the registrar (dd24.net if anyone is 
curious) could not add the appropriate record:

| [COMMAND]
| command=ModifyNameserver
| delipaddress0=212.90.120.82
| addipaddress0=81.92.162.8
| delipaddress1=2001:a60:9000:1000::1:11
| addipaddress1=2001:1B18:202:FFFF::53:1:1
| nameserver=auth01.dns.mucip.net
| EOF
| [RESPONSE]
| code = 535
| description = Restricted IP address

a quick query of the registrar at Verisign GRS resulted in Verisign 
claiming

| The IPv6 you were trying to add is currently in a restricted range by
| IANA.
|
| The IP 2001:1B18:202:FFFF::53:1:1 falls into the below restricted
| range.
|
| 2001:1A00:: 2001:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF

Well, 1b18 is slightly older than a60, so I decided to give Verisign a 
small hint that their list is out of date.

Verisign although claims

| WE are currently following the restricted v6 IP list which is mandated
| by IANA and is current.
|
| We recommend that you contact IANA directly in regards to your matter.

I tried to contact/blame IANA but I haven't received any reply so far. 
Anyone having an idea who the culprit is in this game?

Bernhard