Announcing Peering-LAN prefixes to customers

Wed Jan 16 09:54:42 UTC 2019

(Perhaps off-topic)

KINX are using 192.145.251.0/24 as their Peering IPv4 space.

However, I couldn't find any valid SWIP or IRR record created by IP
owner Hiawatha Broadband Communications, Inc.

Some ISP like Hurricane Electric will route this prefix to KINX but I'm not
sure if it's authorized by IP owner.

Regards,
Siyuan

On Wed, Jan 16, 2019 at 5:44 PM Job Snijders <job at ntt.net> wrote:

> On Wed, Jan 16, 2019 at 12:39 Christoffer Hansen <christoffer at netravnen.de>
> wrote:
>
>>
>> On 16/01/2019 08:56, Mark Tinka wrote:
>> > Running a few exchange points in Africa since 2002, the news was that
>> > the exchange point LAN should not be visible anywhere on the Internet.
>>
>> Do you use AS0 as origin on the RPKI objects for said exchange point
>> LAN(s) to prevent route propagation?
>
>
>
> Either AS 0, or the ASN of the IXP’s service network are valid options.
> Whatever ASN is listed in the RPKI ROA, should simply never announce the
> prefix.
>
> IXPs should make sure to not set MaxLength to allow anything more-l
> specific, it should be equal to the prefix length.
>
> Kind regards,
>
> Job
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190116/6a156a2f/attachment.html>