<div><div dir="auto">Ack for NTT</div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 1, 2019 at 21:36 Christopher Morrow <<a href="mailto:morrowc.lists@gmail.com">morrowc.lists@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">(from offline chat and pokery)<br>
<br>
It looks like 701/1239/3356 are permitting 4837 to announce this prefix because:<br>
$ whois -h <a href="http://whois.radb.net" rel="noreferrer" target="_blank">whois.radb.net</a> 192.139.135.0<br>
route: <a href="http://192.139.135.0/24" rel="noreferrer" target="_blank">192.139.135.0/24</a><br>
descr: managedway company<br>
origin: AS53292<br>
mnt-by: MAINT-AS53292<br>
changed: <a href="mailto:rsanders@managedway.com" target="_blank">rsanders@managedway.com</a> 20181128 #23:11:53Z<br>
source: RADB<br>
<br>
route: <a href="http://192.139.135.0/24" rel="noreferrer" target="_blank">192.139.135.0/24</a><br>
descr: GLENQCY1<br>
origin: AS271<br>
mnt-by: BELL-RC<br>
changed: <a href="mailto:config@in.bell.ca" target="_blank">config@in.bell.ca</a> 19930820<br>
source: BELL<br>
<br>
route: <a href="http://192.139.135.0/24" rel="noreferrer" target="_blank">192.139.135.0/24</a><br>
descr: CMI IP Transit<br>
origin: AS4808<br>
admin-c: MAINT-CMI-INT-HK<br>
tech-c: MAINT-CMI-INT-HK<br>
mnt-by: MAINT-CMI-INT-HK<br>
changed: <a href="mailto:qas_support@cmi.chinamobile.com" target="_blank">qas_support@cmi.chinamobile.com</a> 20160525<br>
source: NTTCOM<br>
<br>
mntner: MAINT-CMI-INT-HK<br>
descr: China Mobile International Limited<br>
country: HK<br>
admin-c: CMIL1-AP<br>
upd-to: <a href="mailto:qas_support@cmi.chinamobile.com" target="_blank">qas_support@cmi.chinamobile.com</a><br>
auth: # Filtered<br>
mnt-by: MAINT-CMI-INT-HK<br>
referral-by: APNIC-HM<br>
last-modified: 2017-11-22T09:00:43Z<br>
source: APNIC<br>
<br>
<br>
There is some less-than-great management of the associated IRR data.<br>
It'd be in the best interest of <someone> (Metro Wireless) to start<br>
asking the various IRR's:<br>
bell - <a href="mailto:config@in.bell.ca" target="_blank">config@in.bell.ca</a> ?<br>
radb -<br>
nttcom - job?<br>
apnic -<br>
<br>
to remove the objects in question.<br>
I'm curious why NTT's still holding this record since there's a competing ROA?<br>
<br>
On Mon, Apr 1, 2019 at 1:27 PM Jay Borkenhagen <<a href="mailto:jayb@braeburn.org" target="_blank">jayb@braeburn.org</a>> wrote:<br>
><br>
> [No attempts at 01-April humor will be attempted in this message.]<br>
><br>
><br>
> Seeking help from routing engineers around the 'net:<br>
><br>
><br>
> ARIN documents that <a href="http://192.139.135.0/24" rel="noreferrer" target="_blank">192.139.135.0/24</a> has been allocated to Metro<br>
> Wireless International:<br>
><br>
> <a href="https://whois.arin.net/rest/net/NET-192-139-135-0-1" rel="noreferrer" target="_blank">https://whois.arin.net/rest/net/NET-192-139-135-0-1</a><br>
><br>
> Further, the party to whom <a href="http://192.139.135.0/24" rel="noreferrer" target="_blank">192.139.135.0/24</a> has been allocated has<br>
> published a ROA in ARIN's hosted RPKI asserting that bgp announcements<br>
> for that prefix are valid only when originating in AS63251. To view<br>
> this, go to your favorite RPKI vantage point that uses ARIN's TAL. If<br>
> you don't yet have a favorite, feel free to telnet to<br>
> <a href="http://route-server.ip.att.net" rel="noreferrer" target="_blank">route-server.ip.att.net</a> and run:<br>
><br>
> show validation database record <a href="http://192.139.135.0/24" rel="noreferrer" target="_blank">192.139.135.0/24</a><br>
><br>
><br>
> Unfortunately, as may be seen at route-views, etc, most of the<br>
> Internet now prefers an invalid path that's mis-originated in as4808:<br>
><br>
><br>
> Network Next Hop Path<br>
> * 192.139.135.0 208.51.134.254 3549 3356 4837 4808 i<br>
> * 194.85.40.15 3267 3356 4837 4808 i<br>
> * 193.0.0.56 3333 1273 4837 4808 i<br>
> * 37.139.139.0 57866 6762 4837 4808 i<br>
> * 12.0.1.63 7018 1299 53292 63251 ?<br>
> * 140.192.8.16 54728 20130 6939 4837 4808 i<br>
> * 91.218.184.60 49788 1299 53292 63251 ?<br>
> * 203.181.248.168 7660 2516 4837 4808 i<br>
> * 154.11.12.212 852 4837 4808 i<br>
> * 134.222.87.1 286 1299 53292 63251 ?<br>
> * 209.124.176.223 101 101 3356 4837 4808 i<br>
> * 137.39.3.55 701 4837 4808 i<br>
> * 94.142.247.3 8283 1239 4837 4808 i<br>
> * 162.251.163.2 53767 3257 1299 53292 63251 ?<br>
> * 212.66.96.126 20912 1267 3356 4837 4808 i<br>
> * 198.58.198.255 1403 6461 4837 4808 i<br>
> * 198.58.198.254 1403 6461 4837 4808 i<br>
> *> 202.232.0.2 2497 4837 4808 i<br>
> * 203.62.252.83 1221 4637 4837 4808 i<br>
> * 132.198.255.253 1351 6939 4837 4808 i<br>
> * 206.24.210.80 3561 209 4837 4808 i<br>
> * 195.208.112.161 3277 39710 9002 3356 4837 4808 i<br>
> * 217.192.89.50 3303 4837 4808 i<br>
> * 173.205.57.234 53364 3257 1299 53292 63251 ?<br>
> * 207.172.6.20 6079 3356 4837 4808 i<br>
> * 207.172.6.1 6079 3356 4837 4808 i<br>
> * 208.74.64.40 19214 174 4837 4837 4808 i<br>
> * 144.228.241.130 1239 4837 4808 i<br>
> * 162.250.137.254 4901 6079 3356 4837 4808 i<br>
> * 114.31.199.1 4826 1299 53292 63251 i<br>
> * 64.71.137.241 6939 4837 4808 i<br>
><br>
><br>
> Please help the Metro Wireless International folks get this cleared up<br>
> so their <a href="http://192.139.135.0/24" rel="noreferrer" target="_blank">192.139.135.0/24</a> can once again be usable. In particular,<br>
> help is sought from 4837 and their transit providers:<br>
><br>
> 1239<br>
> 701<br>
> 3356<br>
><br>
> (Yes, I am trying to reach folks at those networks in other ways, too.)<br>
><br>
><br>
> Thanks.<br>
><br>
> Jay B.<br>
><br>
><br>
><br>
</blockquote></div></div>