Re: ISP data collection from home routers

[PJ Capelli via NANOG]

Not sure why they are different; most ISPs are not a pure play and can use that 
data for other aspects of their business that you may not have agreed to (e.g. 
Verizon FiOS feeding to Verizon Wireless).  Comcast/NBC, etc.

pj capelli
pjcape...@pm.me

No one can build you the bridge on which you, and only you, must cross the 
river of life - Nietzsche

Sent with ProtonMail secure email.

--- Original Message ---

On Thursday, March 24th, 2022 at 10:24 AM, Kord Martin 
 wrote:

> On 2022-03-24 10:04 a.m., Giovane C. M. Moura via NANOG wrote:
> 

> > They can easily profile you and know when you're at home, and when
> > 

> > you're gone. Some people may find this interesting...
> > 

> > To have a really meaningful discuss on the privacy implications, we
> > 

> > would need to see the data model, and the frequency that they pool the
> > 

> > data.
> 

> Is your concern that ISPs have access to this information, or that it's
> 

> something they could possibly be selling to a third party? Those are two
> 

> completely different discussions.
> 

> K

signature.asc
Description: OpenPGP digital signature

Re: ISP data collection from home routers

[PJ Capelli via NANOG]

Most end users (at least in the US) don't have a choice as many jurisdictions 
have sold a franchise (monopoly) to one provider.  Either they sign or they 
don't get internet.

Perhaps 5G will broaden the number of providers end users can choose from, and 
not be forced into this kind of contract.  But why do you think any ISP would 
agree to not collect this information?

pj capelli
pjcape...@pm.me

No one can build you the bridge on which you, and only you, must cross the 
river of life - Nietzsche

Sent with ProtonMail secure email.

--- Original Message ---

On Thursday, March 24th, 2022 at 1:11 PM, Christian David 
 wrote:

> I think that if the end user at signed contract agreed with this data
> 

> collecting and also if there's a mechanism that the same user could deny
> 

> the data collection, its look fine to me, there's compliant here in
> 

> Brazil with LGPD (our variant from GDPR) and i think that users could
> 

> see it as a "plus" cause the majority of ISPs don't have a service that
> 

> inspect CPE WIFI's quality.
> 

> Em 24/03/2022 14:00, Jay Hennigan escreveu:
> 

> > On 3/24/22 06:26, Josh Luthman wrote:
> > 

> > > I'm surprised we're having this discussion about an internet device
> > > 

> > > that the customer is using to publicize all of their information on
> > > 

> > > Facebook and Twitter.
> > 

> > That's called informed consent. And Facebook and Twitter use TLS to
> > 

> > protect the data in transit.
> > 

> > > Consumers do not care enough about their privacy to the point where
> > > 

> > > they are providing the information willingly.
> > 

> > That's the point. The customer is providing information willingly when
> > 

> > they post to social media. The ISP is collecting data without consent.

signature.asc
Description: OpenPGP digital signature

Re: "Permanent" DST

[PJ Capelli via NANOG]

   But how will we remember to change the batteries in our smoke and CO2 detectors then? Sent from ProtonMail for iOS On Tue, Mar 15, 2022 at 3:19 PM, Dave  wrote:  Ending DST is a really good idea.Moving 15 degrees East not so much but let’s face it, the environmental impact statement will take forever to writeDave> On Mar 15, 2022, at 3:11 PM, Jay R. Ashworth  wrote:>> In a unanimous vote today, the US Senate approved a bill which would>> 1) Cancel DST permanently, and> 2) Move every square inch of US territory 15 degrees to the east.>> My opinion of this ought to be obvious from my rhetoric.  Hopefully, it will> fail, because it's likely to be the end of rational time worldwide, and even> if you do log in UTC, it will still make your life difficult.>> I'm poleaxed; I can't even decide which grounds to scream about this on...>> Hopefully, the House or the White House will be more coherent in their> decision on this engineering construct.>> Cheers,> -- jra>> --> Jay R. Ashworth  Baylink   j...@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




signature.asc
Description: OpenPGP digital signature

Re: Better description of what happened

[PJ Capelli via NANOG]

I probably still have my US Robotics 14.4 in the basement, but it's been awhile 
since I've had access to a POTS line it would work on ... :)

pj capelli
pjcape...@pm.me

"Never to get lost, is not living" - Rebecca Solnit

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Wednesday, October 6th, 2021 at 10:41 AM, Curtis Maurand 
 wrote:

> On 10/5/21 5:51 AM, scott wrote:
> 

> > On 10/5/21 8:39 PM, Michael Thomas wrote:
> > 

> > > This bit posted by Randy might get lost in the other thread, but it 
> > > appears that their DNS withdraws BGP routes for prefixes that they can't 
> > > reach or are flaky it seems. Apparently that goes for the prefixes that 
> > > the name servers are on too. This caused internal outages too as it seems 
> > > they use their front facing DNS just like everybody else.
> > > 

> > > Sounds like they might consider having at least one split horizon server 
> > > internally. Lots of fodder here.
> 

> even a POTS line connected to a modem connected to a serial port on a 
> workstation in the data enter so that you can talk to whatever you need to 
> talk to.  I would go so far as to have other outgoing serial connections to 
> routers from that workstation. It's ugly, but it provides remote out of band 
> disaster management.  Just sayin'
> 

> > 
> > 

> > Move fast; break things? :)
> > 

> > scott
> > 

> > > >

signature.asc
Description: OpenPGP digital signature

Re: massive facebook outage presently

[PJ Capelli via NANOG]

Seems unlikely that FB internal controls would allow such a backdoor ...

"Never to get lost, is not living" - Rebecca Solnit

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Monday, October 4th, 2021 at 4:12 PM, Baldur Norddahl 
 wrote:

> On Mon, 4 Oct 2021 at 21:58, Michael Thomas  wrote:
> 

> > On 10/4/21 11:48 AM, Luke Guillory wrote:
> > 

> > > I believe the original change was 'automatic' (as in configuration done 
> > > via a web interface). However, now that connection to the outside world 
> > > is down, remote access to those tools don't exist anymore, so the 
> > > emergency procedure is to gain physical access to the peering routers and 
> > > do all the configuration locally.
> > 

> > Assuming that this is what actually happened, what should fb have done 
> > different (beyond the obvious of not screwing up the immediate issue)? This 
> > seems like it's a single point of failure. Should all of the BGP speakers 
> > have been dual homed or something like that? Or should they not have been 
> > mixing ops and production networks? Sorry if this sounds dumb.
> 

> Facebook is a huge network. It is doubtful that what is going on is this 
> simple. So I will make no guesses to what Facebook is or should be doing.
> 

> However the traditional way for us small timers is to have a backdoor using 
> someone else's network. Nowadays this could be a simple 4/5G router with a 
> VPN, to a terminal server that allows the operator to configure the equipment 
> through the monitor port even when the config is completely destroyed.
> 

> Regards,
> 

> Baldur

signature.asc
Description: OpenPGP digital signature