November 2024 - NANOG - lists.nanog.org

FCC NPRM: Updating Security for Vital Submarine Cables
by Sean Donelan 20 Nov '24

20 Nov '24

On Thursday, the Federal Communications Commission will vote on a Notice of Proposed Rulemaking on submarine cable security. Approximately 84 of the 600 global inter-country submarine cables are licensed by the FCC, and a few intra-territorial cables. https://www.fcc.gov/document/updating-security-vital-submarine-cables

1 0

Re: Shaping the Future of ICP-2: Community Input Extended to December 2024
by Dilip Kounmany 20 Nov '24

20 Nov '24

Hello NANOG community, I’d like to share my thoughts on the ongoing discussion regarding the ICP-2 revision, particularly the importance of the “Portability of Rights to Number Resources.” ICP-2 is essential for guiding Regional Internet Registries (RIRs) in managing IP addresses globally. As we consider revisions, I believe that ensuring the portability of IP resources should be a hard requirement. This means networks should have the right to move their IP resources between RIRs without undue restrictions. Portability is crucial for maintaining network autonomy, allowing operators to control their resources independently of any single RIR. It also promotes competition among RIRs, incentivizing them to improve service quality and accountability. Additionally, if an RIR’s performance negatively impacts a network's operation, there should be a clear mechanism for portability, similar to DNS registries. This would serve as a necessary safety net for networks facing operational issues. As we move forward, let’s advocate for these changes in the ICP-2 policy to foster a more resilient and accountable Internet governance framework. I look forward to hearing your thoughts!

2 2

IPTV and Different markets
by Justin Wilson (Lists) 20 Nov '24

20 Nov '24

Here is the Scenario. Several different IP blocks 2 different geodiverse exit points on the network (more but two for this scenario). This network has Google, Hulu and other Live tv providers complain about being in one market when it should be in another. The way this is being solved at the moment is a /24 for TV market A and a /24 for TV market B. This is a waste for the one market. Customers have IPV6 as well. IPV6 does not seem to be a factor in this scenario. Are there any other solutions to this? If I change GeoLocation on the blocks it ties it to that TV market so not geolocation issue per se. It’s a location issue. Justin Wilson j2sw(a)j2sw.com — https://j2sw.com (AS399332) https://blog.j2sw.com - Podcast and Blog

1 0

Internal Server Error @ mailman.nanog.org
by nanog＠fleish.org 20 Nov '24

20 Nov '24

I am unable to login to the mailman web interface & manage my subscription options @ https://mailman.nanog.org/mailman/listinfo/nanog. I get the below Internal Server Error 500 response: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. Apache/2.4.18 (Ubuntu) Server at mailman.nanog.org Port 443 If an admin could look into this I’d appreciate it. -T

2 1

Technical contact for Verizon (not Fios) before we unplug a service router
by Bruce Wainer 20 Nov '24

20 Nov '24

Hi, My dayjob is preparing to decom our original datacenter, built in the 90's, and the building is being torn down. We have a Verizon Fujitsu Flashwave 4500 with working (green lights) OC12 connections to two local CO's. We don't currently have any Verizon data services, and thus no way to officially inform them of the imminent disconnection. Although this is an older platform and these are (for today) slower links, we want to provide time in case this is part of a ring with other customers on it (like we have with other providers). This is in southeastern Virginia. If anyone from Verizon is here or anyone has contact information to pass along, I'm happy to be contacted off-list. Otherwise, we plan to unplug it and see what happens (not during the holidays). Thank you, Bruce Wainer

6 5

Anyone know Hispasec Sistemas ?
by John Levine 19 Nov '24

19 Nov '24

They are a security company in Spain who I gather have some relation to Virus Total. Unfortunately, someone there believes that abuse.net is the Network Police, and is sending it urgent messages to take down naughty domains. In reality, abuse.net is just me, and their spam is getting rather tedious. I have tried writing to addresses on their web site with no response. Any chance someone knows someone there who might be able to relay a clue? TIA. R's, John

3 2

AS35361 Contact
by Richard Desjardine 19 Nov '24

19 Nov '24

Good day, If there is anyone out there from AS35361 that could help me with a routing issue between 45.59.96.0/22 and AS36351 via Torix please contact me off list. Thank you, Richard [cid:2b592541-7b68-4ffd-a2d6-75608244a346]

1 0

Netflix peering contact
by Tim Burke 18 Nov '24

18 Nov '24

Any peering folks from 2906 on the list? Have a several month old case open about getting some PNI’s stood up… sent over an LOA but haven’t heard anything since. Thanks, Tim

1 1

Soooo..... Netflix
by Mike Hammett 18 Nov '24

18 Nov '24

Armchair quarterbacking... Discussions I've seen from operators on Facebook shows some that had PNIs that worked just fine, while others with PNIs and cache boxes didn't fare so well. Some with just cache boxes were fine, while others were not. What were your educated observations, preferably with supporting data? Did we have a problem with congestion where the cache boxes phones home to, and this they just fell over? AWS used to be the data source of last resort. Did anyone notice congestion going from AWS to cache boxes? -----Mike HammettIntelligent Computing SolutionsMidwest Internet ExchangeThe Brothers WISP

11 13

Incorrect Reverse DNS in Verizon Fios NYC core router traceroute
by Neel Chauhan 18 Nov '24

18 Nov '24

Hi, I got Fios installed today in my NYC apartment, as I just moved back from Seattle after a 4-month stay in Connecticut. When doing a traceroute, I am noticing an incorrect Reverse DNS entry: [root@twin ~]# traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets 1 _gateway (172.20.0.1) 0.145 ms 0.115 ms 0.106 ms 2 lo0-100.NYCMNY-VFTTP-372.verizon-gni.net (173.56.84.1) 2.079 ms 2.070 ms 2.061 ms 3 G0-3-4-4.PITBPA-LCR-21.verizon-gni.net (100.41.196.252) 3.751 ms T0-8-0-9.BSTNMA-LCR-21.verizon-gni.net (100.41.196.248) 4.454 ms 4.447 ms 4 * * * 5 * * * 6 162.158.61.113 (162.158.61.113) 7.246 ms 6.603 ms 162.158.61.117 (162.158.61.117) 4.944 ms 7 one.one.one.one (1.1.1.1) 6.077 ms 6.355 ms 6.346 ms [root@twin ~]# In short, hop 3 is "G0-3-4-4.PITBPA-LCR-21.verizon-gni.net (100.41.196.252)" which seems to be a Pittsburgh, PA reverse DNS entry even when I'm in NYC. While it doesn't affect the normal operation of the service, it might give the impression packets are being routed via Pittsburgh to someone less savvy. If someone works at the Verizon Fios/ILEC network engineering or sysadmin team could the 100.41.196.252 reverse DNS entry to say "G0-3-4-4.NYCMNY-LCR-21.verizon-gni.net" please get updated? Thanks! Neel Chauhan

5 4