Looks like they are encountering the issue of head-of-line blocking. Since HTTP/2 multiplexes streams on a single tcp connection, all streams suffer when packet loss occurs. This is a well-known flaw in HTTP/2. HTTP/1 creates multiple tcp connections; if one connection needs to wait for retransmissions, the others are not impeded.
Not really, considering any single subscriber could be assigned a whole /56, and that machines with privacy addressing would be periodically changing the last 64 bits of their address.
ASAs are often used at the perimeter of small satellite networks using a local ISP's internet access, and then connecting back to HQ with IPSEC tunnels. I would guess that it is not uncommon, though bad practice, to centrally monitor SNMP on the external interface instead of over the IPSEC tunnel (which can be a little tricky to do).
You can learn the community string by monitoring traffic. The community string is included in each and every SNMPv2 PDU. SNMPv2 performs no handshake, so is vulnerable to trivial spoofing. Enterprises and ISPs reusing community strings on every device and never rotating them is not unheard of.
When was this? For a long time IPv6 suffered from people running services over tunnels via tunnel brokers, which resulted in horrible performance, MTU issues, timeouts and so on.
I have noticed recently that the situation has improved a lot, with more and more "real", native deployments coming online.
I am quite worried about this development as someone who has to deal with DDoS traffic on a regular basis.
I am starting to feel like UDP and UDP-like protocols should be abolished outright.
Some people would prefer scaled down quality instead of stuttering when watching eg. live streams or on-demand movies (and not have to wait for download to finish).