- Test - lists.nanog.org

Sprint contact - Mobile network block DNS
by Andrew Imeson 19 Nov '20

19 Nov '20

I'm looking for a contact at Sprint (or T-Mobile?) mobile networking, if someone could please contact me off-list. I help run a service that relies on being able to make DNS queries via standard UDP directly to particular servers, and recently we've been seeing all the packets silently dropped on Sprint with both iOS and Android devices. -- Thanks, Andrew Imeson

1 0

Mozilla solicits comments on rolling DoH wide
by Jay R. Ashworth 19 Nov '20

19 Nov '20

If, like me, you think it's a solution in search of a problem -- excuse me, a *problem* in search of a problem -- here's your chance: https://www.zdnet.com/article/fearing-drama-mozilla-opens-public-consultati… -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

1 0

Spectrum (AS33363) Clue?
by Bryan Fields 19 Nov '20

19 Nov '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Is there anyone at Spectrum business with clue who can contact me off list regarding some peering issues in your network? I have several customers seeing 150ms of latency due to traffic bouncing between east and west coasts to go across the room. This is between routers both in TAMSFLDE. Support has said this is "normal" and refused to escalate it. Some quick testing with RIPE Atlas probes shows it's the same across 33363. Thanks, - -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEaESdNosUjpjcN/JhYTmgYVLGkUAFAl+0N20ACgkQYTmgYVLG kUAsBQ/8Cu5i3rH98K/pEwawV391d++V8dQWrFosYEz6Yp99OTJg3K2NcgI5wYGj +cfTYbw2sGTQUB57bIxZbpAYIV1KIeEwHckQ2P/2coud9y8yeuFjSY2kEYl5HpoV T9Q8bIw8XTvZgPZYvQ9VPry4zWscV+2OoHEZQpQSN4MOyjN1Oj+w36/nM3La+Dp3 RaQkbKKW44LcAgqn4wUqdZgmZcYpsgz+RyA9hbbvT3tl7693LdD4XcenULo0t4kS cu0YcoDA7+2yoTdF7yzabl0qPwhqfhTPEYczWxHEqfEXN0NebV5Nqj4pMAQfQFZ2 mEyckAx84+hL2op0XVXYPnbU6Kd3i5JZxcHOwXIp5Kk0LvZVSfMypseAAPRzS/M+ PXbnlqFYf350VOjV7rQn23UWo5kduxzvOyc+bYGAvsqJWYumpIGYqe05EHQqYiBO RTuJoOLmEYfg52OML/ih0M9UPGtluIZvvMPv+jLmbyVt2COjaJnVGiWWfrIjkQqr 2kjIRrja3RTvHZHVUHHyZZMdfjufjb2fIhboHDhhEueEMSPBdzCb+j241IrG4IHb sDWkhkcdXyN82htvEocZDJqGGMQqzCP86TWoefjN3YOjKMLl8kL9HgRV7eZGZJc9 6cbQrh50mWHQtYgki9a0+3Sk9Eu7cJIWSAA4p6l3WaOa80VGbEw= =BfB0 -----END PGP SIGNATURE-----

3 3

Telia Not Withdrawing v6 Routes
by Matt Corallo 19 Nov '20

19 Nov '20

Has anyone else experienced issues where Telia won't withdraw (though will happily accept an overriding) prefixes for the past week, at least? eg 2620:6e:a003::/48 was a test prefix and should not now appear in any DFZ, has not been announced for a few days at least, but shows up in Telia's LG and RIPE RIS as transiting Telia. Telia's LG traceroute doesn't of course, go anywhere, traces die immediately after a hop or with a !N. Wouldn't be a problem except that I needed to withdraw another route due to a separate issue which wouldn't budge out of Telia's tables until it was replaced with something else of higher pref. Matt

11 18

Phoenix-IX Contact
by Kate Gerry 18 Nov '20

18 Nov '20

Does anybody have a contact who works at Phoenix-IX? I have been attempting to reach somebody there for a while now without any luck. Attempts to each out to peering(a)phoenix-ix.net <mailto:peering@phoenix-ix.net> as well as Ninja-IX have been without any luck. We also tried reaching out to Paul Emmons via LinkedIn mail and never received a response. Any assistance either on or off the list is appreciated. Thanks! -- Kate

12 19

GTT contact
by Joseph Breu 18 Nov '20

18 Nov '20

Hi All, Looking for a GTT NOC contact that can assist with packet loss on a transit link between SEA and SFO. I tried emailing their NOC but they keep asking for an account number of service details. We are not their customer - we’re just being impacted by the packet loss. Thanks in advance -breu

2 1

AFRINIC IP Block Thefts -- The Saga Continues
by Ronald F. Guilmette 18 Nov '20

18 Nov '20

South African tech journalist Jan Vermeulen has written a new chapter in this ongoing saga of greed, theft, and skulduggery. EXECUTIVE SUMMARY: Maikel Uerlings and Elad Cohen registered a bunch of new domain names as part of their overall scheme to steal AFRINIC legacy blocks by fiddling the AFRINIC WHOIS records for the contact persons for each legacy block that they wanted to steal. The domain names themselves were deliberately chosen and tailored to try to minimize suspicion relating to their numerous legacy block thefts. https://mybroadband.co.za/news/security/367188-the-great-african-ip-address… How exactly these two gentlemen managed to gain the kind of read/write access to the AFRINIC WHOIS data base which allowed them to fiddle so many WHOIS records for so many AFRINIC legacy IPv4 blocks is something that AFRINIC has yet to offer any explanation for, even a full year after these thefts came to light. NOTE: As of the present moment AFRINIC is *still* delegating authority for reverse DNS for many of the stolen legacy blocks detailed in Jan's most recent article to name servers that are owned and controled by Maikel Uerlings and/or Elad Cohen. In particular, Uerlings and/or Cohen are still in control of the reverse DNS for all of the stolen legacy blocks listed in the table below, as well as the reverse DNS for the very valuable 196.16.0.0/14 block, worth well over $5 million USD. There is no reasonable excuse for this ongoing inaction by AFRINIC. As things stand, it appears that AFRINIC is still refusing to do even the minimum amount necessary to stop the profiteering of Uerlings and Cohen, EVEN THOUGH every additional dollar, every additional sheckel, and every additional ruble that they earn from these ongoing thefts is being used to fund Cohen's ongoing lawsuit against AFRINIC. AFRINIC has known about these legacy block thefts for well over a year now, and yet in all this time AFRINIC has done absolutely nothing to remediate the fradulent entries in their WHOIS data base, or to remove the reverse DNS relegations for the 196.16.0.0/14 block and the several stolen blocks listed below. Reasonable people can and should ask why. One theory, currently circulating among people I know is that Mr. Uerlings and/or Mr. Cohen are in possession of some confidential information that AFRINIC really hopes will never see the light of day, and that AFRINIC is being blackmailed into inaction. Whatever the reason, AFRINIC's continuing inaction is effectively providing funding for Mr. Cohen's ongoing lawsuit against AFRINIC. How this makes any sense at all is something that remains for AFRINIC to explain. #------------------------------------------------------------------------ # ORG: (SC) ORG-AISL1-AFRINIC "AECI Information Services (Pty) Ltd" #------------------------------------------------------------------------ 168.80.0.0/15 #------------------------------------------------------------------------ # ORG: (ZA) ORG-AA79-AFRINIC "Agrihold" #------------------------------------------------------------------------ 163.198.0.0/16 #------------------------------------------------------------------------ # ORG: (ZA) ORG-ACSL2-AFRINIC "Affiliated Computing Services (Pty) Ltd" #------------------------------------------------------------------------ 160.116.0.0/16 #------------------------------------------------------------------------ # ORG: (ZA) ORG-FSED1-AFRINIC "Free State Education Department" #------------------------------------------------------------------------ 168.76.0.0/19 168.76.36.0/24 168.76.128.0/20 168.76.144.0/22 168.76.148.0/24 168.76.228.0/22 168.76.232.0/21 168.76.240.0/20 #------------------------------------------------------------------------ # ORG: (ZA) ORG-SCS1-AFRINIC "Safren Computer Services" #------------------------------------------------------------------------ 155.159.0.0/16

12 17

Fwd: Phoenix-IX Contact
by Paul Emmons 17 Nov '20

17 Nov '20

still trying to post . . . -------- Forwarded Message -------- Subject: Re: Phoenix-IX Contact Date: Mon, 16 Nov 2020 13:15:34 -0700 From: Paul Emmons <paul(a)iosaz.net> To: nanog(a)nanog.org Hello All! I've been out of the loop here and but have some updates. There was a change last spring and I moved on to other projects. But that hasn't worked out for the IX. I have regained access to all of the elements, including the email and voip. Let me reach out to each of you offline in the coming days. I have been able to reach out to a few locals that are willing to help get the project back up to where it needs to be. If I haven;t reached out to you in the next 48 hours or you have something urgent, please reach out to me here (my personal email) or via the Phoenix-IX Contacts peering(a)phoenix-ix.net +1 602 688-6414 ~Paul Emmons On 11/16/2020 12:23 PM, Neil Hanlon wrote: > While I agree it is objectively irresponsible to abandon a project > without passing it to another, I think that possibly in this situation > we don't know all the details? > > 2020 has been a difficult year for everyone. Perhaps Paul (and > whomever else may be responsible for Phoenix-IX) were subject to > things this year beyond their control which led them to be unable to > work on the project and unable to transfer it, either.. unfortunate, > yes.. but not malicious surely. > > If Paul _is_ reading these messages.. I think support is the best path > forward.. If there are things that can be done to assist/take over the > IX... maybe that would help (as you, Kate, had offered towards the > beginning of this all). Though of course, the first step is _reaching_ > them... Maybe this can be turned into a "win" for everyone. So: > Paul/Phoenix-IX -- let the NANOG community know how they/we can help. > > -- > Neil > > On Mon, Nov 16, 2020 at 2:05 PM Kate Gerry <kgerry(a)outlook.com > <mailto:kgerry@outlook.com>> wrote: > > An update on my side, we reached out to PhoenixNAP, one of the > Phoenix-IX's vendors. > > PhoenixNAP reached out all of their contacts at Phoenix-IX and > have received no response. They are in as much of the dark as the > rest of us. I feel like I'm on the Ghost ship Phoenix-IX. > > What I don't understand, is how somebody could abandon a project > without passing it to another person or entity. This is extremely > irresponsible. > > — > Kate > >> On Nov 12, 2020, at 05:11, Marcus Josephson <mjosephson(a)inap.com >> <mailto:mjosephson@inap.com>> wrote: >> >> I tried to get a link to PHX-IX for months. Never heard back from >> them, went with Digital Realty Phoenix >> *From:*NANOG <nanog-bounces+mjosephson=inap.com(a)nanog.org >> <mailto:nanog-bounces+mjosephson=inap.com@nanog.org>>*On Behalf >> Of*Kate Gerry >> *Sent:*Tuesday, November 10, 2020 11:06 AM >> *To:*Matt Hoppes <mattlists(a)rivervalleyinternet.net >> <mailto:mattlists@rivervalleyinternet.net>> >> *Cc:*nanog@nanog.org <mailto:nanog@nanog.org> list >> <nanog(a)nanog.org <mailto:nanog@nanog.org>> >> *Subject:*Re: Phoenix-IX Contact >> Matt, >> I am running on a huge assumption here, but I think Phoenix-IX >> runs on donated infrastructure. From what I recall, there was >> only an NRC to join Phoenix-IX. >> And in regards to Walt's suggestion, it looks like HE already >> started one with Stellar Technologies. https://48ix.net >> <https://48ix.net/> but it is only in a single facility. So until >> that IX grows, both in peers and footprint, I'm stuck on Phoenix-IX. >> I have wondered what happens if a participant storms the IX. Will >> somebody appear? Because attempts to reach their NOC/peering >> handles has resulted in a lack of response. >> I also wonder how the other Ninja-IX exchanges are running, I >> haven't heard anything about them, is there the same lack of >> communication? Or do those have a local staff? >> — >> Kate >> >> >> On Nov 10, 2020, at 06:15, Matt Hoppes >> <mattlists(a)rivervalleyinternet.net >> <mailto:mattlists@rivervalleyinternet.net>> wrote: >> How is the IX still running? Surely someone must be paying >> colo rent? >> >> On 11/10/20 9:03 AM, Eric Kuhnke wrote: >> >> Always a good time for network operators to consider the >> risks of having any one person as a single point of >> failure for something kind of important: >> https://en.wikipedia.org/wiki/Bus_factor >> <https://en.wikipedia.org/wiki/Bus_factor> >> Disaster recovery and continuity of business plans should >> always include the concept of what if some percentage of >> the key team members were to be suddenly unavailable >> permanently (the Malaysian airline incident, for example). >> On Mon, Nov 9, 2020 at 8:08 PM Kate Gerry >> <kgerry(a)outlook.com <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%20%3cmailto:kgerry@outlook.com>>> >> wrote: >> Is there anybody else even there? I thought that it >> was all Paul's show! >> If I was able to (as in, had access to), I would offer >> to help/run >> with the IX. I may live in California, but it's a >> realistic car trip >> back and forth to Phoenix. >> -- >> Kate >> >> On Nov 9, 2020, at 17:58, Mike Hammett >> <nanog(a)ics-il.net >> <mailto:nanog@ics-il.net >> <mailto:nanog@ics-il.net%0b%C2%A0%C2%A0%C2%A0%3cmailto:nanog@ics-il.net>>> >> wrote: >> >> Paul's LinkedIn seems to show that he checked out >> in April. Let me >> know if you have any success reaching anyone there. >> >> >> >> ----- >> Mike Hammett >> Intelligent Computing Solutions >> <http://www.ics-il.com/ <http://www.ics-il.com/>> >> <https://www.facebook.com/ICSIL >> <https://www.facebook.com/ICSIL>><https://plus.google.com/+IntelligentComputingSolutionsDeKalb >> <https://plus.google.com/+IntelligentComputingSolutionsDeKalb>><https://www.linkedin.com/company/intelligent-computing-solutions >> <https://www.linkedin.com/company/intelligent-computing-solutions>><https://twitter.com/ICSIL >> <https://twitter.com/ICSIL>> >> Midwest Internet Exchange >> <http://www.midwest-ix.com/ <http://www.midwest-ix.com/>> >> <https://www.facebook.com/mdwestix >> <https://www.facebook.com/mdwestix>><https://www.linkedin.com/company/midwest-internet-exchange >> <https://www.linkedin.com/company/midwest-internet-exchange>><https://twitter.com/mdwestix >> <https://twitter.com/mdwestix>> >> The Brothers WISP <http://www.thebrotherswisp.com/ >> <http://www.thebrotherswisp.com/>> >> <https://www.facebook.com/thebrotherswisp >> <https://www.facebook.com/thebrotherswisp>><https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg >> <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg>> >> ------------------------------------------------------------------------ >> *From:*"Kate Gerry" <kgerry(a)outlook.com >> <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%20%3cmailto:kgerry@outlook.com>>> >> *To:*"Bill Woodcock" <woody(a)pch.net >> <mailto:woody@pch.net >> <mailto:woody@pch.net%20%3cmailto:woody@pch.net>>> >> *Cc:*nanog@nanog.org <mailto:nanog@nanog.org> >> <mailto:nanog@nanog.org <mailto:nanog@nanog.org>> >> *Sent:*Monday, November 9, 2020 5:44:42 PM >> *Subject:*Re: Phoenix-IX Contact >> >> Just a heads-up, I never heard a word from anybody >> at Phoenix-IX. >> >> Is there anybody still running the IX? Or is it >> just on autopilot? >> It'd be nice if anybody had some information on >> whatever happened >> to Paul. Hopefully he is okay! >> >> -- >> Kate >> >> On Sep 14, 2020, at 13:33, Kate Gerry >> <kgerry(a)outlook.com >> <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%0b%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%3cmailto:kgerry@outlook.com>>> >> wrote: >> >> Thank Bill! I've been trying to reach Paul for >> ages now, >> hopefully he pops back up again. We want to >> upgrade. >> >> On an unrelated note, it looks like somebody >> has their ticket >> system subscribed to the list... Awesome. >> >> *From: *Dating Support >> <dating.support(a)csvwebsupport.com >> <mailto:dating.support@csvwebsupport.com >> <mailto:dating.support@csvwebsupport.com%0b%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%3cmailto:dating.support@csvwebsupport.com>>> >> *Subject: **[#WQV-291-95071]: Phoenix-IX >> Contact* >> *Date: *September 14, 2020 at 12:43:20 PDT >> *To:*kgerry@outlook.com >> <mailto:*kgerry@outlook.com><mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com>> >> *Reply-To:*dating.support@csvwebsupport.com >> <mailto:*dating.support@csvwebsupport.com> >> <mailto:dating.support@csvwebsupport.com >> <mailto:dating.support@csvwebsupport.com>> >> >> Kate Gerry, >> >> Thank you for contacting us. This is an >> automated response >> confirming the receipt of your ticket. Our >> team will get >> back to you within 24 hours. >> >> >> -- >> Kate >> >> >> On Sep 14, 2020, at 12:48, Bill Woodcock >> <woody(a)pch.net >> <mailto:woody@pch.net >> <mailto:woody@pch.net%0b%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%3cmailto:woody@pch.net>>> >> wrote: >> >> >> >> On Sep 14, 2020, at 9:31 PM, Kate Gerry >> <kgerry(a)outlook.com >> <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%20%3cmailto:kgerry@outlook.com>>> >> wrote: >> >> Does anybody have a contact who works >> at Phoenix-IX? I >> have been attempting to reach somebody >> there for a >> while now without any luck. >> >> Attempts to each >> outtopeering(a)phoenix-ix.net >> <mailto:topeering@phoenix-ix.net> >> <mailto:peering@phoenix-ix.net >> <mailto:peering@phoenix-ix.net>>as well as Ninja-IX >> have been without any luck. We also >> tried reaching out >> to Paul Emmons via LinkedIn mail and >> never received a >> response. >> >> >> Paul is the correct person. >> >> -Bill >> >

1 0

ATT Contact for DDoS?
by Sajan Parikh 17 Nov '20

17 Nov '20

Trying to figure out whom to escalate to with ATT to help with a DDoS attack for a network, we are trying to help out. RTBH is not sufficient because they are hitting a large swath of IPs out of the prefixes advertised, and the targets are moving. The network AS itself is the attack target. I'd heard of other operators working with their transit provider's Cybersecurity NOC to filter traffic outside of the US. Does anyone have a good ATT contact for this? Sajan Parikh sajan(a)parikh.io 262.343.5973

1 0

PeeringDB Satisfaction Survey open now til November 20th
by Steve McManus 16 Nov '20

16 Nov '20

PeeringDB is a non-profit, freely available, user-maintained, database of networks, and the go-to location for interconnection data. The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centers, and other interconnection facilities, and is the first stop in making interconnection decisions. We want input from network operators, exchange operators, facility providers, content distributors and anyone who uses our interconnection database. This year we are running an anonymous satisfaction survey in addition to the usual feedback gathering we employ. The survey will be available here: https://surveyhero.com/c/f7be5236 until 23:59 UTC on 20 November 2020. We would like your feedback to help us make PeeringDB more useful to everyone involved in connecting networks.This survey will help us understand what is important to you and how satisfied you are with what we are doing. We will use your responses to focus our product roadmap on the improvements that will make things better for you. If you have specific comments or suggestions, we’d love you to leave them along with your ratings. This is the first survey we are making available in multiple languages. In this survey we are using the six UN languages for the questions. That said, we’re happy with people providing free text comments in another whichever language they are happiest expressing themselves. We’ll share the results and the new product roadmap early in 2021. Steve McManus on behalf of PeeringDB Product Committee

1 1