Re: Do ISP's collect and analyze traffic of users?

2023-05-17 Thread Livingood, Jason via NANOG 
> Why would there be a difference between wireless and wired?

Service provisioning in a mobile network is at the device level and tied to an 
individual vs. at a home shared across many devices & people. So just starting 
off there is more visibility to say X traffic is related to Y person. Then 
there’s location data to know roughly where that person/device is traveling. 
Also most carriers have software installed on the device as part of the 
provisioning/authentication function and I think there are historical cases 
where that provided some visibility into other apps on the device. In any case, 
it seems the most value (to advertisers & data brokers) is in the location data 
and I think that’s where all the scrutiny on MNOs has been recently.



JL

Re: Do ISP's collect and analyze traffic of users?

2023-05-17 Thread Robert Mathews (OSIA) 


On 5/17/23 12:06 AM, Mark Tinka wrote:

On 5/16/23 16:55, Saku Ytti wrote:

I can't tell what large is. But I've worked for enterprise ISP and
consumer ISPs, and none of the shops I worked for had capability to
monetise information they had. And the information they had was
increasingly low resolution. Infraprovider are notoriously bad even
monetising their infra.

[  ]

I tend to agree.

ISP's are, generally, terrible at evolving beyond selling bandwidth.

While there might be some ISP's that are able to monetize the data 
they collect - to whatever degree that monetization is useful - I'd 
hazard that the majority don't do this because it requires a different 
mindset that most ISP's simply don't have.


Mark.



For those who may have a broader interest in the topic of 
user/subscriber information collection by ISPs


Eight Years Holding ISPs to Account in Latin America: A Comparative 
Outlook of Victories and Challenges for User Privacy

By Veridiana Alimonti
May 12, 2023
https://www.eff.org/deeplinks/2023/05/eight-years-holding-isps-account-latin-america-comparative-outlook-victories-and

All the best
--
/Dr. Robert Mathews, D.Phil.
Principal Technologist &
Distinguished Research Scholar - National Security Affairs & Industrial 
Preparedness

Office of Scientific Inquiry & Applications
University of Hawai'i/

NANOG 88 Agenda is Now Available! + More

2023-05-17 Thread Nanog News 
*NANOG 88 Agenda is Now Available! *
*Join Us for our 88th Community-Wide Gathering 12-14, June*

Sync your calendars today and plan out your NANOG 88 experience!


*VIEW AGENDA  *
*What's Trending on the Mailing List? *
*Find or Give a Solution on Our Online Conversation Threads *

*Current Trending Conversations *

   - Do ISP’s collect and analyze traffic of users?
   - Looking for Contact: MTN South Africa (AS16637)
   - Routed Optical Networks
   - Major changes to ARIN RPKI functionality (Fwd: [arin-announce] New
   Features Added to ARIN Online)
   - Weekly Global IPv4 Routing Table Report
   - DNS Dinner at NANOG 88 for the DNS Affinity Group
   - Cisco Nexus 3k Route Selection\Packet Forwarding Debugging

*MORE INFO * 

*Did You Know There is a Parents Affinity Group at NANOG?*
*Find Community in our Online Discussion Threads*

The NANOG Affinity Groups are part of the Community Forum and allow our
members to connect over shared interests.

We need your voice! Connect with others in the tech industry and find
mentorship and support while sharing your experiences.


*MORE INFO  *

Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread holow29 
Is anyone able to reach treasurydirect.gov over IPv6? Unable to do so over
Verizon Fios, and I'm not sure if it is a routing issue or an issue on
Treasury's end.

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread Daniel Marks via NANOG 
You can utilize online (i.e. https://dnstools.ws/) or ISP looking glass 
tools to check for routing issues.


It's up for us via AS12129

On 5/17/2023 2:30 PM, holow29 wrote:
Is anyone able to reach treasurydirect.gov  
over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it 
is a routing issue or an issue on Treasury's end.

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread John Levine 
It appears that holow29  said:
>-=-=-=-=-=-
>
>Is anyone able to reach treasurydirect.gov over IPv6? Unable to do so over
>Verizon Fios, and I'm not sure if it is a routing issue or an issue on
>Treasury's end.

Works fine via a HE tunnel.

R's,
John

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread Jay Hennigan 

On 5/17/23 11:30, holow29 wrote:
Is anyone able to reach treasurydirect.gov  
over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is 
a routing issue or an issue on Treasury's end.


Reachable from AS4927 in California.

--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread John Lightfoot 
Verizon has IPv6?

From: NANOG  on behalf of Jay 
Hennigan 
Date: Wednesday, May 17, 2023 at 3:21 PM
To: nanog@nanog.org 
Subject: Re: Treasurydirect.gov unreachable over IPv6?
On 5/17/23 11:30, holow29 wrote:
> Is anyone able to reach treasurydirect.gov 
> over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is
> a routing issue or an issue on Treasury's end.

Reachable from AS4927 in California.

--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread holow29 
Thanks all.
Given that traceroute can reach Zayo and Zayo appears to have route to
Treasury's AS13506, is it reasonable to assume this is on Treasury's end,
potentially blocking traffic from VZ's AS701?

@John Lightfoot: Yes, they rolled out largely throughout last year.

On Wed, May 17, 2023 at 3:24 PM John Lightfoot  wrote:

> Verizon has IPv6?
>
>
>
> *From: *NANOG  on behalf of
> Jay Hennigan 
> *Date: *Wednesday, May 17, 2023 at 3:21 PM
> *To: *nanog@nanog.org 
> *Subject: *Re: Treasurydirect.gov unreachable over IPv6?
>
> On 5/17/23 11:30, holow29 wrote:
> > Is anyone able to reach treasurydirect.gov 
> > over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is
> > a routing issue or an issue on Treasury's end.
>
> Reachable from AS4927 in California.
>
> --
> Jay Hennigan - j...@west.net
> Network Engineering - CCIE #7880
> 503 897-8550 - WB6RDV
>

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread Jesse Rehmer 

From Spectrum, I'm able to hit port 80, but the redirect to 443 fails.


% curl -6IL treasurydirect.gov
HTTP/1.0 302 Moved Temporarily
Location: https://treasurydirect.gov/
Server: BigIP
Connection: Keep-Alive
Content-Length: 0

curl: (35) Recv failure: Connection reset by peer

Cheers,

Jesse

On 5/17/23 1:30 PM, holow29 wrote:
Is anyone able to reach treasurydirect.gov  
over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is 
a routing issue or an issue on Treasury's end.

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread Jay Hennigan 

On 5/17/23 12:19, Jesse Rehmer wrote:

 From Spectrum, I'm able to hit port 80, but the redirect to 443 fails.


Smells like broken PMTUD to me.

--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

Re: Treasurydirect.gov unreachable over IPv6?

2023-05-17 Thread Chris Adams 
Once upon a time, Jay Hennigan  said:
> On 5/17/23 12:19, Jesse Rehmer wrote:
> > From Spectrum, I'm able to hit port 80, but the redirect to 443 fails.
> 
> Smells like broken PMTUD to me.

Yeah.  From Google Fiber, IPv4 works.  IPv6 connects on port 80, gets
redirected to HTTPS, which connects on port 443 but fails in SSL
negotiation.

I wonder if some over-zealous network admin blocked all ICMPv6.
-- 
Chris Adams