Don't bother: It was removed 24+ h ago after we got alerted
George
On Tue, Mar 7, 2017 at 2:10 PM, Mark Andrews wrote:
>
> In message <6bcda810-52cd-4efe-9a69-4b1aabc90...@burn.net>, Brandon Applegate
> writes:
>> Just did a whois on the documentation prefix and was surprised to see
>> what loo
In message <6bcda810-52cd-4efe-9a69-4b1aabc90...@burn.net>, Brandon Applegate
writes:
> Just did a whois on the documentation prefix and was surprised to see
> what looks like a user object registered for it:
>
> % Information related to '2001:0DB8::/32AS132111'
>
> route6: 2001:0DB8::/32
Hi.
On Mon, Mar 6, 2017 at 5:03 PM, Alarig Le Lay 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 what
>> looks like a user object registered for it:
>>
>> % Information related to '2001:0DB8::/32AS132111'
Hi,
On Mon, Mar 6, 2017 at 4:55 PM, Brandon Applegate wrote:
> Just did a whois on the documentation prefix and was surprised to see what
> looks like a user object registered for it:
>
> % Information related to '2001:0DB8::/32AS132111'
>
> route6: 2001:0DB8::/32
> descr: FUTUR
On lun. 6 mars 10:55:18 2017, Brandon Applegate wrote:
> Just did a whois on the documentation prefix and was surprised to see what
> looks like a user object registered for it:
>
> % Information related to '2001:0DB8::/32AS132111'
>
> route6: 2001:0DB8::/32
> descr: FUTURE D S
Just did a whois on the documentation prefix and was surprised to see what
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: MAI
6 matches
Mail list logo