- NANOG - lists.nanog.org

IPv6 Thought Experiment
by Antonios Chariton 10 Oct '19

10 Oct '19

Dear list, First of all, let me apologize if this post is not allowed by the list. To my best interpretation of the guidelines [1] it is allowed, but may be in a gray area due to rule #7. I would like to propose the following thought experiment about IPv6, and I would like your opinion on what you believe would happen in such a case. Feel free to reply on or off list. What if, globally, and starting at January 1st, 2020, someone (imagine a government or similar, but with global reach) imposed an IPv4 tax. For every IPv4 address on the Global Internet Routing Table, you had to pay a tax. Let’s assume that this can be imposed, must be paid, and cannot be avoided using some loophole. Let’s say that this tax would be $2, and it would double, every 3 or 6 months. What do you think would happen? Would it be the only way to reach 100% IPv6 deployment, or even that wouldn’t be sufficient? And for bonus points, consider the following: what if all certification bodies of equipment, for certifications like FCC’s or CE in Europe, for applications after Jan 1st 2023 would include a “MUST NOT support IPv4”.. What I am trying to understand is whether deploying IPv6 is a pure financial problem. If it is, in this scenario, it would very very soon become much more pricey to not deploy it. I know there are a lot of gaps in this, for example who imposes this, what is the "Global Internet Routing Table", etc. but let’s try to see around them, to the core idea behind them. Thanks, Antonis ------- Links ------- 1: https://nanog.org/resources/usage-guidelines/ <https://nanog.org/resources/usage-guidelines/>

39 142

Chicago Equinix IX LAN oddity
by JASON BOTHE 09 Oct '19

09 Oct '19

Hi all I realize this might not be the right list but I have a request to peer on the Chicago Equinix IX to a 206.223.119 IP but we and many others are on the 208.115.137 network. While I await a response from the peering partner, I’d curious to know if this is an error, perhaps there was a renumber at one time or I’m flat out just missing something. Cheers! J~

2 1

Contact at DALnet?
by Christopher Smalling 09 Oct '19

09 Oct '19

Hello, We're having an issue with peering to DALnet (AS31800) and have received no further correspondence since the initial contact, and they do not appear to have anything further than email contact. If someone from DALnet or someone with a contact at DALnet, please contact me off-list. Thank you, -- Christopher Smalling NOC Support Technician

2 1

Quantum Internet Article - Netherlands
by Rod Beck 09 Oct '19

09 Oct '19

https://www.quantamagazine.org/stephanie-wehner-is-designing-a-quantum-inte… [https://d2r55xnwy6nx47.cloudfront.net/uploads/2019/09/WehnerQA_1200x630.jpg]<https://www.quantamagazine.org/stephanie-wehner-is-designing-a-quantum-inte…> To Invent a Quantum Internet - Quanta Magazine<https://www.quantamagazine.org/stephanie-wehner-is-designing-a-quantum-inte…> Fifty years after the current internet was born, the physicist and computer scientist Stephanie Wehner is planning and designing the next internet — a quantum one. The first data ever transmitted over Arpanet, the precursor of the internet, blipped from a computer at the University of California ... www.quantamagazine.org Roderick Beck VP of Business Development United Cable Company www.unitedcablecompany.com<http://www.unitedcablecompany.com> New York City & Budapest rod.beck(a)unitedcablecompany.com 36-70-605-5144 [1467221477350_image005.png]

1 0

Telemetry System Ideas
by Chris Misa 08 Oct '19

08 Oct '19

I am a researcher working on developing a new on-the-fly telemetry system that potentially takes a flow chart as input to describe a particular detection task (rather than just features or information elements as in IPFIX). For an example of what I mean by "flow chart" see the figure here: https://ieeexplore.ieee.org/mediastore_new/IEEE/content/media/8048782/80488…. Might anyone have pointers to a source of more such flow charts? The other issue I'm worried about is that it might take a couple rounds before an event is detected (since the system has to step through the flow chart and possibly look at different traffic features in the process). What is a typical duration of the types of events people might want to catch with a telemetry system like this? Do these kind of events generate the same type of traffic throughout their durations, or do traffic features change as the event progresses? Thanks! Chris

1 0

Contacts at Three.co.uk
by John Von Essen 08 Oct '19

08 Oct '19

I know this is a North America list, but anyone here connected with Three or have a contact there? I am investigating an issue related to the default adult filter settings that are becoming more common (maybe required now?) in the UK on mobile data networks. I work at a large search engine, not Google or Bing, but like #4 or 5 in the world, and a portion of our site is being blocked by Three - and we’ve determined its related to their adult filter settings on mobile or mifi devices. We’d like to get in contact with them to understand how/why it was blocked and what we can do to resolve it. Thanks John Von Essen

2 1

Re: Chicago Equinix IX LAN oddity
by JASON BOTHE 08 Oct '19

08 Oct '19

Got it, thanks for that. I’ll have to give the big E a call and see how to sort this one out. J~ > On Oct 8, 2019, at 13:55, James Cornman <james(a)atlanticmetro.net> wrote: > > > There was a subnet expansion/migration there earlier this year (maybe late last year?) > > We have an old and new address on our interface.. The 208.x is the new range (aka bigger) > > ip address 206.223.119.124/24 > ip address 208.115.136.124/23 > > -James > >> On Tue, Oct 8, 2019 at 2:47 PM JASON BOTHE via NANOG <nanog(a)nanog.org> wrote: >> Hi all >> >> I realize this might not be the right list but I have a request to peer on the Chicago Equinix IX to a 206.223.119 IP but we and many others are on the 208.115.137 network. While I await a response from the peering partner, I’d curious to know if this is an error, perhaps there was a renumber at one time or I’m flat out just missing something. >> >> Cheers! >> >> J~ > > > -- > James Cornman > jcornman(a)atlanticmetro.net > 212.792.9950 > > Atlantic Metro Communications > 4 Century Drive, Parsippany NJ 07054 > > Cloud Hosting • Colocation • Network Connectivity • Managed Services > Follow us on Twitter: @atlanticmetro • Like us on Facebook > www.atlanticmetro.net

2 1

Update to BCP-38?
by Stephen Satchell 08 Oct '19

08 Oct '19

Is anyone working on an update to include IPv6?

12 35

Spoofer Report for NANOG for Sep 2019
by CAIDA Spoofer Project 08 Oct '19

08 Oct '19

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within usa, can. Inferred improvements during Sep 2019: ASN Name Fixed-By 13427 SOFTCOM-INTERNET-COMMUNICATION 2019-09-12 3807 UMTNET-ASN 2019-09-16 8047 GCI 2019-09-16 225 VIRGINIA 2019-09-18 16787 CHARTER-16787-DC 2019-09-23 22402 NEXTCO 2019-09-23 2828 XO-AS15 2019-09-26 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Sep 2019: ASN Name First-Spoofed Last-Spoofed 40065 CNSERVERS 2016-05-01 2019-09-04 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2019-09-25 6128 CABLE-NET-1 2016-09-03 2019-09-25 27364 ACS-INTERNET 2016-09-27 2019-09-19 20412 CLARITY-TELECOM 2016-09-30 2019-09-27 6181 FUSE-NET 2016-10-10 2019-09-29 15305 SYRINGANETWORKS 2016-10-21 2019-09-19 14971 PINETEL 2016-10-21 2019-09-19 25787 ROWE-NETWORKS 2016-10-21 2019-09-29 174 COGENT-174 2016-10-21 2019-09-26 32440 LONI 2016-11-03 2019-09-26 12083 WOW-INTERNET 2016-11-09 2019-09-30 39939 RISE-CO-AS39939 2016-11-11 2019-09-12 1403 EBOX 2016-11-12 2019-09-27 2828 XO-AS15 2016-11-21 2019-09-11 9009 M247 2017-01-10 2019-09-04 701 UUNET 2017-06-14 2019-09-30 63296 AMARILLO-WIRELESS 2017-09-01 2019-09-27 546 PARSONS-PGS-1 2017-11-20 2019-09-12 54540 INCERO-HVVC 2018-01-15 2019-09-16 12222 AKAMAI 2018-02-14 2019-09-30 4201 ORST 2018-04-19 2019-09-25 11827 WSU 2018-05-07 2019-09-26 19016 WCG 2018-05-19 2019-09-01 225 VIRGINIA 2018-06-18 2019-09-27 33452 RW 2018-09-19 2019-09-28 20448 VPNTRANET-LLC 2018-09-20 2019-09-10 63275 RADIOWIRE 2019-02-07 2019-09-23 15290 ALLST-15290 2019-04-09 2019-09-19 8047 GCI 2019-04-11 2019-09-24 10745 ARIN-ASH-CHA 2019-04-29 2019-09-30 38235 MEKONGNET-ADC 2019-05-09 2019-09-22 32 STANFORD 2019-08-21 2019-09-24 21709 IMPLEX-NET 2019-09-24 2019-09-24 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block… Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

dns cache beyond ttl - viasat / exede
by Mike 08 Oct '19

08 Oct '19

Hello, I am moving a number of web sites from one colo to another, re-numbering them in the process, and I have run into an interesting issue I'd like to solicit feedback on. My dns TTL's are all 300 seconds, and I have noticed that once I update the A records with the new addresses, most (but not all) web clients begin using the new address within 5 minutes or so. However, there is a persistent set of stragglers who continue accessing the site(s) on their old addresses for far in excess of this - up to a week in fact. And, what I have noted, all of these clients have something in common - they all appear to be satellite users of viasat/exede. This is based on whois lookups of the ip addresses of the clients. Note, I am NOT expecting 'turn on a time' - just looking for clients to refresh within a reasonable time. I am wondering if perhaps this is due to some kind of (known?) bug in the embedded dns cache/client in the client satellite modem, or if there is another plausible explanation I am not seeing. It compounds my problem slightly since I have to continue running the web sites at both the old and new addresses while these things time out I guess and it's just inconvenient. Thanks. MIke-

7 11