In Aug of this year, I posted about three-phase power. Subsequently, I had a discussion with a friend from Delhi about bonding neutral with earth/ground at the distribution panel. He has a commercial load of 20KW delivered via three phases and his electrician advised him to bond neutral with the ground. We both were curious whether it was technically correct or not. Taking a break from network engineering, here goes a post about it.
Yesterday there was an article in the Indian paper Financial Express with the title “OTTs may have to pay access charge to telcos”.
Quoting a few points from the article:
- Social media intermediaries like WhatsApp, Facebook and Twitter, and over-the-top (OTT) players like Netflix, Prime Video and Disney+Hotstar may have to pay a carriage charge to telecom service providers
- Data, particularly video, comprises 70% of the overall traffic flow on telecom networks, and this would grow further with the rollout of 5G services
- Upon reference from the DoT, Trai is currently studying various possible models under which OTTs can be brought within the purview of some form of regulation
- According to sources, an interconnect regime is a must between OTTs and telcos because as 5G services grow, there would be immense data/ video load on networks, which may lead to them getting clogged or even crashing at times.
This concept of “OTTs must pay” is not new. This has been argued a few times in past. Exactly ten years ago in 2012 I wrote a blog post about Bharti Airtel expecting Google/YouTube to pay. At that time they could not convince OTTs to pay. Why is this renewed interest now? Well, that has to do with the first SK Telecom (South Kore telecom) Vs Netflix court case in South Korea where SK Telecom claimed that a large part of bandwidth utilization was because of Netflix and hence they should pay a “fair share” of their traffic which they lost. Soon around this multiple of large telecom monopolies in Europe started this discussion in their respective geography. Four of the top EU players - Deutsche Telekom, Orange, Vodafone and Telefonica are of opinion that OTTs should share the burden (news here). And hence Indian telcos possibly looking to renew this debate.
In Hyderabad for the weekend to participate in GFCE workshop at IIIT Hyderabad. I like GFCE workshops as they are short & to the point. This will be my third one after Delhi and Kolkata. These are round table discussions covering concepts like IPv6, routing security, DNS, email security protocols etc. I will be sharing updates on RPKI in the region and participating in the discussion about this wide varieties of topics.
Next week will be APNIC 54 conference followed by SGNOG 9 (Singapore Network Operators Group) event. I will be attending both events. At APNIC 54 I will be doing a short tutorial on “Running Containers in Production” with CI/CD pipelines with a focus on its utility in network engineering and also a panel discussion on “World IPv6 2022 - the story behind the events”. This should be fun!
I have migrated this 14-year-old blog from a dynamic WordPress (based on WordPress) to a static website (based on Hugo). It was a pretty lengthy process even when I had scripts converting the WordPress XML export into markdown files.
Why a static site?
This gives a few advantages like:
I haven’t finalised the hosting location for this newer site. For now, it’s on Google Cloud firebase but I am still just playing with the options. If I get some free time, I might just tweak my PowerDNS setup to start using GeoIP data for the request and serve the local server in a given country. That way I can host the website in India, Europe and US and let authoritative DNS steer the traffic. More on this later!
I was having this discussion with someone recently on possible software to manage an IXP. Lately, IXP Manager has become the de-facto choice for managing IX. It’s a good tool. Nick and INEX team has built a fantastic open-source tool. But I still feel it’s a bit overloaded for a small 1-2 DC IX operation.
If I have to set up a small to mid-size IX, I would rather do that with arouteserver instead of IXP Manager as I did in case of BharatIX in Mumbai (until it shutdown!). One of the problems with arouteserver is that it can be script intensive and one may need something around it to manage it for things like build config on clients.yml update, regularly update filters etc.
Next week SANOG (South Asia Network Operator Group) event will start in Kathmandu, Nepal. I will be instructing on a 4-day workshop on Network Automation with two fellow instructors. The idea of this workshop is to make fellow Ops / Network engineers familiar with concepts of Docker, Ansible, and Gitlab CI/CD pipeline and ultimately to make use of REST APIs to bind these all together.
This is the first time I am doing such a workshop and the content here is built from scratch. On the positive side, it gives good flexibility on content but the challenge is to stick on time. Since content is not tested before, there will always be a risk of going “too slow” or “too fast”. The goal by the end of the workshop is to ensure that attendees can build up event-driven automation. They should be able to set up a system where “if x happens” then “action y is triggered”. This can fit a wide variety of use cases.
As returning readers of this blog would be aware - I found a trick to find Facebook caching servers around the world during the APRICOT 2018 hackathon. Since then I am running my code again every year to see the changes and publish this report.
Previous reports
Back in 2019, I was in San Francisco, California for NANOG 75. While roaming around in the lobby, someone read the NANOG card hanging around my neck and greeted me. His 2nd line after greeting was “Oh I know that name, you are the guy who mapped our caching nodes” and we both laughed. I must say this specific category of the post has brought some attention around.
In a recent Network AF podcast Avi Freedman (Kentik) joked with the guest about how he finds who is transit free / tier 1 network. He said, “I ask everyone who they think is a tier 1 network. Everyone includes their own name + other names”. Next, he ignores the self-nomination & looks at the common list to find who actually is a tier 1 network. This is funny, intuitive and gives some clue.
CERT-IN i.e Computer Emergency Response Team, India issued new guidelines on 28th April. Guidelines essentially ask those VPN providers to keep a log of customer details, their IP addresses, emails, phone numbers etc and maintain that log for at least 5 years. The detailed notification is here.
This not only extends to VPN players but also to datacenters, VPS, cloud service providers etc. I can understand the problem they are trying to solve as most criminal activities are hidden behind VPN players and investigating agencies just hit a dead end as they see the WAN IP of a VPN player.