https://lore.kernel.org/netdev/20190617.104121.1475407136257...
66 karma · joined February 8, 2013
Verifying my Blockstack ID is secured with the address 1DiaxZCRXyZoWBmTN1Fh7gxXs1Ne53htKy https://explorer.blockstack.org/address/1DiaxZCRXyZoWBmTN1Fh7gxXs1Ne53htKy
https://lore.kernel.org/netdev/20190617.104121.1475407136257...
Cloud to me is also shared risk. I read - "Google cloud outage" as "multiple companies that rely on a shared infrastructure is not available ATM".
The mindset should be to run your services on a distributed infrastructure with no SPOF. Leverage cloud, fog, racks, PCs, whatever resources you can, but diversify your content/service and be risk averse from failure of one kind.
However, IMO - what should have been the focus for Google Fiber is to come up with applications that consume more upstream traffic. That is where DOCSIS lacks in terms of throughput and a fundamental problem docsis nodes face called "noise funneling". To avoid that - cable companies push fiber nodes closer to last mile.
If Google would have been successful in creating a FTTH marketplace, it wouldn't be that difficult for cable companies to start investing on ONU/ONT and GPON solutions to compete. With competition, Google wouldn't really get the ROI they were expecting unless they really bring about change in applications that utilize the upstream bandwidth heavy.
2. Live Interaction with Events, Games, Television, Radio etc. e.g. Polls, QnA, Sentiment etc.
3. Open Access to Developers to build Apps on real-time content.
4. Enable fact-check score methodologies on every tweets. Don't completely wipe out the trolls. As weird as it may sound - trolls make twitter interesting.
5. The Ultimate messaging platform that replaces SMS/Texts with an identity that is not numbers.
Wouldn't this be taxed as capital gains though - when exercised?
Therefore, I don't think Academics should stop doing what they do (i.e. wander around) and have a laser focus on Industry's product-based researches.
BGP itself, is a path vector protocol (came from standard and vetted Graph Theory algorithms) and therefore for the scalability of the Internet Prefixes - works perfectly with many network devices talking the standard protocol.
Work has always been done within the IETF wg on BGP attributes that the protocol carries for many use-cases and so far BGP has been the preferable choice for many networks, both within an AS and outside an AS(Autonomous System).
You wouldn't want the Internet be controlled by a central authority, that is an absolute NO - at the same time - you have to work together to make sure the "global routing table" or the "default free zone" is not polluted with unnecessary updates and churn and overseeing misbehavior from other ASes.
I believe with so many disparate organizations and networks around the world - we could not have built a common talking "language"/"protocol" without having accountability into it and constantly monitoring it.
Type: A > pathchange Involving: 74.125.226.0/24
Short description: The route 39202 174 9498 17488 15169 is changed to 39202 174 15169
Path: 39202, 174, 15169,
Date and time: 2015-03-12 09:16:23 Collected by: 01-195.66.225.2 # whois -h whois.cymru.com 41.138.222.196
AS | IP | AS Name
327692 | 41.138.222.196 | SMILECOMMS,UG
# whois -h whois.cymru.com 41.73.194.97
AS | IP | AS Name
36930 | 41.73.194.97 | Zantel-AS,TZWonder what your latency would be with a SEACOM(AS37100) traversal, http://en.wikipedia.org/wiki/Telecommunications_in_Tanzania
Here are your downstream carrier options : http://www.cidr-report.org/cgi-bin/as-report?as=AS37100&v=4&...
http://www.cidr-report.org/cgi-bin/as-report?as=AS15169&view...
Complexities aside - this is how your Internet works.