[191833] in North American Network Operators' Group
Re: Providing transit to unallocated networks
daemon@ATHENA.MIT.EDU (joel jaeggli)
Tue Sep 27 22:57:17 2016
X-Original-To: nanog@nanog.org
To: Alistair Mackenzie <magicsata@gmail.com>,
George Michaelson <ggm@algebras.org>, NANOG <nanog@nanog.org>
From: joel jaeggli <joelja@bogus.com>
Date: Tue, 27 Sep 2016 19:57:09 -0700
In-Reply-To: <CA+bbMkvEd--AGas0EPwFwSdd3fDqLBhXRWRXah4gspof9yftqw@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ET97jqmRdaKLKh31064tjqVHv0ahxFoII
From: joel jaeggli <joelja@bogus.com>
To: Alistair Mackenzie <magicsata@gmail.com>,
George Michaelson <ggm@algebras.org>, NANOG <nanog@nanog.org>
Message-ID: <386dcc99-7964-b195-4689-7d50305c8ec3@bogus.com>
Subject: Re: Providing transit to unallocated networks
References: <CA+bbMkusT1hygisQqBFxXLiuN8mfcNNn_W7vDLvesgYzW4V=UQ@mail.gmail.com>
<CAKr6gn3GpaM-edysguthi-PpREQcDsm-japHXd4ZQyCqu6Hdpg@mail.gmail.com>
<CA+bbMkvEd--AGas0EPwFwSdd3fDqLBhXRWRXah4gspof9yftqw@mail.gmail.com>
In-Reply-To: <CA+bbMkvEd--AGas0EPwFwSdd3fDqLBhXRWRXah4gspof9yftqw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
On 9/27/16 5:46 PM, Alistair Mackenzie wrote:
> Thanks for this, it shows as
>
> apnic|ZZ|ipv4|103.***.***.0|1024|20160927|reserved||e-stats
>
> I expect this still stands with it being reserved?
I'm not sure why you would bother obscuring it. What purpose does that
serve in furthering the discussion?
If it's not
route-views>show ip bgp 103.6.232.0/22
BGP routing table entry for 103.6.232.0/22, version 87113221
Paths: (1 available, best #1, table default)
Not advertised to any peer
Refresh Epoch 1
3277 39710 20632 31133 58073
195.208.112.161 from 195.208.112.161 (194.85.4.4)
Origin IGP, localpref 100, valid, external, best
Community: 3277:39710 20632:65441 65535:65000
rx pathid: 0, tx pathid: 0x0
What is it?
>
>
> William, it's 100% an apnic range and shows no org and is registered
> to the APNIC Hostmaster. This applies for both the ASN and the address
> space.
>
>
> On 28 September 2016 at 01:28, William Herrin <bill@herrin.us> wrote:
>
>> On Tue, Sep 27, 2016 at 8:18 PM, Alistair Mackenzie <magicsata@gmail.c=
om> wrote:
>>> I've come across a network which seem to be getting transit yet both =
the
>>> ASN and IP space is not allocated by the RIR.
>> Hi Alistair,
>>
>> There is still unicast address space that isn't allocated by any RIR?
>>
>> Seriously though, check all your bases. Is not the space unallocated
>> by all RIRs or just the one you expect to hold it? If you have a
>> transit provider that's not playing by the rules, contact their
>> transit providers to complain and if you still don't get satisfaction,=
>> I'd name and shame the lot of them. Failure to filter bad actors is
>> how prefix hijacking happens.
>>
>> Regards,
>> Bill Herrin
>>
>>
>>
>> --
>> William Herrin ................ herrin@dirtside.com bill@herrin.us
>> Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/>
>>
>>
> On 28 September 2016 at 01:36, George Michaelson <ggm@algebras.org> wro=
te:
>
>> check if the block is in this file.
>>
>> http://labs.apnic.net/delegated-nro-extended
>>
>> If not, then the block is hijacked or being abused.
>>
>> the file format is a bit obscure: the ipv4 record is base-ip|hostcount=
>> but converting that to prefix length is pretty simple.
>>
>> -G
>>
>> On Wed, Sep 28, 2016 at 10:18 AM, Alistair Mackenzie
>> <magicsata@gmail.com> wrote:
>>> Hi,
>>>
>>> I've come across a network which seem to be getting transit yet both =
the
>>> ASN and IP space is not allocated by the RIR. It does appear at some
>> point
>>> that it was valid however this is no longer the case.
>>>
>>> The network is single homed and I tried asking the transit provider w=
hat
>>> their policy was on this but got no answer.
>>>
>>> Has anyone seen anything like this? What has happened in the past wit=
h
>>> things like this?
>>>
>>> Thanks,
>>> Alistair
--ET97jqmRdaKLKh31064tjqVHv0ahxFoII
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAlfrMYYACgkQ8AA1q7Z/VrL6NQCffDFzH/xx5zjPeGBsO4FZWmJY
edkAn3QO1kLGCVt+igRx2RTIGvf3IrEl
=mVUg
-----END PGP SIGNATURE-----
--ET97jqmRdaKLKh31064tjqVHv0ahxFoII--
