[193962] in North American Network Operators' Group
Re: IPv6 doc. prefix (2001:db8::/32) - APNIC object ?
daemon@ATHENA.MIT.EDU (Job Snijders)
Mon Mar 6 11:10:41 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <20170306160313.pywykwmaqwq4kfko@mew.swordarmor.fr>
From: Job Snijders <job@instituut.net>
Date: Mon, 6 Mar 2017 17:06:07 +0100
To: Alarig Le Lay <alarig@swordarmor.fr>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Hi.
On Mon, Mar 6, 2017 at 5:03 PM, Alarig Le Lay <alarig@swordarmor.fr> wrote:
> On lun. 6 mars 10:55:18 2017, Brandon Applegate wrote:
>> Just did a whois on the documentation prefix and was surprised to see wh=
at looks like a user object registered for it:
>>
>> % Information related to '2001:0DB8::/32AS132111'
>>
>> route6: 2001:0DB8::/32
>> descr: FUTURE D SDN BHD
>> origin: AS132111
>> country: MY
>> mnt-by: MAINT-FUTUREDSDNBHD-MY
>> changed: hm-changed@apnic.net 20160523
>> source: APNIC
>>
>> Any idea what this is ? I would have thought there might be some sanity=
check that would have stopped this from getting registered ?
>
> Hi,
>
> If you look for TEST-NET-3, it is also registered to APNIC:
> [snip]
>
> As long as APNIC is a RIR, I don=E2=80=99t see a big issue with that.
Don't confuse an 'inetnum' and a 'route' object. Inetnum's are fine,
as long as their documented purpose is correct. The route object the
OP mentioned makes no sense. AS132111 is not authorised to announce
the IPv6 Documentation prefix.
Kind regards,
Job
