1. Internet Governance (IG) Primer 2. I-* Organizations 3. IANA function -Names, Numbers and Protocol Parameters 4. IANA Transition 5. WHOIS for names and numbers 6. Need for Standardization and Standardization Bodies 7. How IETF Works 8. TLS Protocol 9. Increasing Indian participation in global Internet Governance activities and structures

1. Mohit Batra
20th Jan 2018
OWASP/NULL Delhi Chapter Meetup

2.  Organization - National Internet Exchange of India (NIXI)
http://www.nixi.in
 Email - mohit4677@gmail.com
 LinkedIn - https://www.linkedin.com/in/mohitbatra80/
 Twitter - @mohitbatra80

3. Internet Governance (IG) Primer
I-* Organizations
IANA function - Names, Numbers and Protocol Parameters
IANA Transition
WHOIS for names and numbers

4.  Need for Standardization and Standardization Bodies
 How IETF Works
 TLS Protocol
 Increasing Indian participation in global Internet Governance activities
and structures

6. Today’s Basic necessities: Roti, Kapda, Makaan, Internet and
Smartphone with Internet
We take Internet for granted and use it in daily life.
A large no. of businesses run completely over Internet/Cloud, and
Internet outages are costly.
Ever wondered what is going on behind the scenes that
makes Internet work seamlessly 24*7*365 on our laptops,
desktops, mobiles…?

7. Do you know that there was a significant overhaul in how
Internet is governed in 2016, but most Internet users didn’t
notice? (IANA Transition)
Threats/attacks are constantly evolving:
 On Internet’s core infrastructure
 That use Internet as a medium
It is our duty as Security Pro’s to protect the Internet.
Knowledge of Internet Governance is critical for a global IT (and
Security) professional.

8.  No billionaire person, company or government (not even US) owns or runs the
Internet.
 It is a globally distributed internetwork, comprising of many voluntarily
interconnected autonomous networks.
 It operates without a central governing body, with each participating network
setting and enforcing its own policies.
 However, to ensure interoperability, several key technical and policy
aspects of the underlying core infrastructure and the principal
namespaces need to be administered centrally.

10.  The I* (I-star) group of organizations is a loose term to describe core Internet
organizations that share responsibilities for:
 Coordinating Internet’s unique identifiers at the topmost level
 Designing robust, scalable and interoperable Internet protocols.
 Conducting research into future Internet technologies
 Supervising architecture, evolution and growth of Internet
 Developing policies for smooth allocation/maintenance/de-allocation of critical Internet
resources like domain names, IPv4/v6 addresses, ASN’s
 Sharing best practices and discuss most pressing issues related to Internet
 IETF, ISOC, IAB, IRTF, ICANN, IGF, IEEE, RIR’s, W3C

11. Formed in 1986
When you think of Layer 1-7 (actually 2-7), TCP/IP,
internetworking protocols, VoIP, YouTube streaming, Web
browsing, SSH, NetBanking, TLS, Routing protocols, picture
IETF.
A unique organization that falls simultaneously amongst 2
select groups of:
 Core Internet (I-star) organizations
 Global Standards Developing Organizations (SDO’s)

13. Physical
Link
Internet
Transport
Application

14. IETF develops standards above the wire and below the
application, but boundaries are blurring.
The mission of the IETF is to make the Internet work better
by producing high quality, relevant technical documents that
influence the way people design, use, and manage the
Internet.
RFC3935 defines IETF's mission.
IETF is led by its chair, currently Alissa Cooper from Cisco.

15.  IETF develops and promotes voluntary open Internet standards.
 Internet protocol standards produced by IETF are not binding in nature
for Networking and Application software, Networking Hardware,
Operating System vendors.
However, IETF protocols’ standards adoption is a natural
choice for everyone using Internet:
 due to their high quality
 wide coverage of use cases
 for the sake of maintaining interoperability on Internet
 absence of any other competing Internet standardization forum

16. All aspects related to IETF are documented as RFC/BCP
documents.
 Internet Draft (I-D)
Request for Comments (RFC) series contains technical and
organizational documents about the Internet, including
specifications and policy documents produced by four
streams: IETF, IRTF, IAB and independent submissions.
RFCs are never changed – A new RFC can supersede older
ones

17. Not all RFCs are standards: informational, experimental, best
current practice.
RFC2026 documents:
 the process used by the Internet community for standardization of
protocols
 stages in the standardization process
 requirements for moving a document between stages
 types of documents used during this process

18. Who utilizes and conforms to Internet protocol standards
produced by IETF:
 Routers and Switches
 Firewalls, IDS/IPS and Proxies
 IPSEC, SSL and MPLS VPNs
 TCP/IP internetworking stacks inside modern Desktop Operating
Systems (Windows, Unix) and Smartphones (Android, iOS)
 IoT sensors
 All modern internetworking software e.g. Web Browsers (Chrome,
Firefox), Emailing softwares (MS Outlook, GMail), DNS Servers
(BIND)
 Handy utilities like PuTTy, ping, traceroute, ftp, dig, wireshark

19.  I-* and SDO’s do not work in isolation, and have liaising mechanisms in place.
 IETF has liaison relationships with other organizations.
 The primary contact for IETF liaison negotiation and representation with outside organizations is IAB.
 Establishing a liaison relationship can:
 prevent duplication of effort, without obstructing either organization from pursuing its own mandate; and
 provide authoritative information of one organization's dependence on other’s work.
 IETF and 3GPP collaboration for 5G
 ICANN TLG – IETF (via IAB), ETSI, ITU-T and W3C

20.  Non-profit organization founded in 1992 to provide leadership in Internet-related
standards, education, and policy
 Dedicated to ensuring the open development, evolution and use of the Internet and its
architecture for the benefit of people throughout the world.
 IETF (1986) was formed before ISOC (1992)
 ISOC was formed by a number of people with long-term involvement in the IETF.
 Provide an institutional home, organization structure, legal umbrella and
financial support (e.g. for meetings) for the IETF, and to promote Internet
Standardization process in general.

21.  ISOC Chapters are communities of like-minded people who work together to run a
variety of programmes and activities related to Internet, such as educational events,
community and public policy programmes and networking events.
 Chapters are formed by individual members of the Internet Society who share an
interest and belief in ISOC’s principles and mission, and who are committed to
furthering ISOC’s goals and objectives within a particular geographic area.
 ISOC chapters have their presence throughout world.
 India currently has following ISOC chapters:
 Delhi Bangalore Kolkata
 Chennai Trivendrum Mumbai*

22.  The IAB provides long-range technical direction for Internet
development, ensuring the Internet continues to grow and evolve as a
platform for global communication and innovation.
 Ensure that the Internet is a trusted medium of communication that
provides a solid technical foundation for privacy and security, especially
in light of pervasive surveillance
 Establish the technical direction for Internet that will enable billions
more people to connect, support the vision for an Internet of Things,
and allow mobile networks to flourish, while keeping the core
capabilities that have been a foundation of the Internet’s success
 RFC4440 documents the relationship between IRTF, IAB and IETF.

23.  The primary contact for IETF liaison negotiation and representation with
outside organizations is IAB
 The ICANN’s Technical Liaison Group (TLG) consists of 4 SDO’s – ETSI, ITU-
T, W3C and IAB.
 The purpose of the TLG is to connect the ICANN Board with appropriate
sources of technical advice on specific matters pertinent to ICANN's activities.
 ICANN bylaws ask these organisations to each provide 2 technical experts.
 On behalf of the IETF, the IAB names two technical experts to the ICANN
TLG.

24. While IETF focuses on short-term issues of engineering /
standardization, its research counterpart IRTF focuses on
long-term research issues related to the Internet.
IRTF investigates Internet related topics considered to be too
uncertain/advanced or insufficiently understood.
But once IRTF research generates a specification that is
considered stable for Internet standardization, the
specification is processed through IETF.

25. For example, research on decentralized Internet
infrastructure / distributed ledger technologies (DLTs),
which forms the basis of evolving disruptive
technologies like Blockchain is underway at IRTF.
After research is completed, corresponding standardization
activities for DLTs and Blockchain will take place through
IETF.
IRTF is led by its chair, currently Allison Mankin from
SalesForce.

26.  Decentralized Internet Infrastructure Proposed Research Group
 Human Rights Protocol Considerations Research Group
 Thing-to-Thing Research Group
 Crypto Forum Research Group
 Global Access to the Internet for All Research Group
 Internet Congestion Control Research Group

27.  Information-Centric Networking Research Group
 Measurement and Analysis for Protocols Research Group
 Network Function Virtualization Research Group
 Network Management Research Group
 Network Coding for Efficient Network Communications Research Group
 Path Aware Networking Proposed Research Group

28. There is now an emphasis to design Internet protocols
keeping in mind human aspects and rights.
The The Human Rights Protocol Considerations (HRPC)
Research Group is chartered to research whether standards
and protocols can enable, strengthen or threaten human
rights.
 HRPC RG has recently come out with RFC8280: Research
into Human Rights Protocol Considerations

29. [1]Research on Delay-Tolerant Networking Research Group
(DTNRG) concluded in 2016.
Expectedly, corresponding Engineering / Standardization
work is currently been done in Delay/Disruption Tolerant
Networking (dtn) Working Group under Transport Area of
IETF.
[2] Research on Interplanetary Internet Research Group
(IPNRG) is also concluded.

30.  Internet Corporation for Assigned Names and Numbers (ICANN) was
founded in 1998, and is headquartered at Los Angeles, California.
 Core Internet (I-*) organization responsible for coordinating the
assignment of globally unique identifiers at the top level on the
Internet, including Names (domain names), Numbers (IPv4/v6
Addresses, ASN numbers), and Protocol Parameters
 ICANN performs above overseer/coordination responsibility via its
IANA function (department).
 Without unique assignment of these critical Internet identifiers at the
top level, Internet can’t work properly.

33.  Internet DNS Root Zone Management is one of core ICANN functions
 There are 13 root DNS server clusters (A-M), but actual DNS root
server instances is large (650+) due to Anycast Routing technique.
 IANA (a department of ICANN) maintains DNS Root Zone file
 Top level domains (TLDs) come in 2 flavours:
 Generic (gTLDs) - .com, .tech
 Country-code (ccTLDs) - .in, .de, .au
 Root Zone file consists of pointers (NS records) to DNS servers for Top
Level Domains (TLDs) – gTLDs as well as ccTLDs

34.  Management, policy development and technical operation of gTLD
Domain Names is the most basic function of ICANN.
 ICANN uses multistakeholder approach of Policy Development for gTLDs
 Management, policy development and technical operation of ccTLD
Domain Names is left to respective countries.
---
 Assignment/Allocation of unique Numbers and Protocol parameters
are done in close coordination with RIRs and IETF respectively via
SLAs, MoUs and agreements.

35.  ICANN has 7 SO/ACs representing all Internet communities
 Supporting Organizations (SO’s) (can do Policy Development)
 Address Supporting Organization (ASO)
 Country Codes Name Supporting Organization (ccNSO)
 Generic Name Supporting Organization (GNSO)
 Advisory Committees (AC’s) (can only advise ICANN Board)
 Governmental Advisory Committee (GAC)
 Root Server System Advisory Committee (RSSAC)
 Security and Stability Advisory Committee (SSAC)
 [ICANN ASO] == [NRO] via MoU

36.  ICANN’s new gTLD program (.amazon, .tech, .bank, .pharmacy) after
2012
ICANN meetings: 3 times an year across globe
 India: 2 ICANN meetings - in 2008 (New Delhi) and 2016
(Hyderabad)
Domain names are registered by Registrants via
intermediaries like Registrars (e.g. GoDaddy)
WHOIS is used to check availability of domain name before
purchasing.

37. IGF is a multi-stakeholder forum for policy dialogue on
issues of Internet governance.
It brings together all stakeholders (governments, private
sector, civil society, technical, academic community, LEAs)
in the Internet governance debate, on an equal basis and
through an open and inclusive process.
The establishment of the IGF was formally announced by
the United Nations Secretary-General in July 2006.

38. Internet related Best Practices are also shared at
IGF meetings
IGF meeting is being held on an yearly basis from
2006 onwards (2008: Hyderabad)
Outcomes of IGF are not binding.

39.  RIRs distribute and manage Internet number resources (IPv4 and IPv6 addresses and
Autonomous System Numbers) within their respective regions.
 There are five RIRs: AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC
 The Number Resource Organization (NRO) is a coordinating body for the 5 RIRs

40.  Internet unique identifiers are coordinated globally (by ICANN, via its IANA
function), so that each identifier is uniquely assigned to only one party – thus
enabling successful and reliable communication among parties on the
Internet.
 For Internet numbers (which include, IPv4/v6 addresses and ASN numbers), a
global registration system is facilitated by the coordinated activities of five
Regional Internet Registries (RIRs).
 Hierarchy of distribution of numbering resources– RIRs -> NIRs -> LIRs / ISPs
 India’s NIR is IRINN, operated by NIXI
 One of just 7 NIRs within APAC region
 Works directly beneath APNIC

41.  W3C is a SDO for the web, which forms a major portion on Internet.
 It was founded by Tim Berners-Lee after he left the European
Organization for Nuclear Research (CERN)
 W3C develops interoperable standards and technologies (specifications,
guidelines, software, tools) to lead the Web to its full potential.
 Members include businesses, nonprofit organizations, universities,
governmental entities.
 Currently 460+ members

42. Some notable web standards produced by W3C are:
HTML CSS XHTML
DOM CGI XML Schema
XML SOAP XForms
WSDL Xpath MathML
Xquery XSLT VoiceXML

44.  Someone (I-* org.) needed to coordinate the assignment of globally
unique identifiers at the top level on the Internet, including:
 Names (domain names)
 Numbers (IPv4/v6 Addresses, ASN numbers)
 Protocol Parameters (port numbers, IP protocol numbers etc.)
 Without unique assignment of these critical Internet identifiers, Internet
can’t work properly.
 ICANN since 1998 is performing this overseer/coordination
responsibility, via its IANA function as per a contract with US Govt.
Department of Commerce’s NTIA.

45. Domain Names at the top level (TLDs) come in 2 flavours:
1) gTLDS like .com, .org, .net, .amazon, .tech, .bank etc.
Can be further classified into Legacy and new gTLDs
2) ccTLDs like .in, .de, .au
Countries treat ccTLDs as their sovereign function
Countries formulate own policies for respective ccTLDs
IANA maintains DNS Root Zone file

46. 13 root DNS server clusters (A-M) host Root Zone
File for queries by DNS Resolvers (ISPs)
Additions, Deletions and modifications to DNS Root
zone file are propagated from IANA to Root Servers
across the world.
Root Zone file consists of pointers (NS records) to
DNS servers for Top Level Domains (TLDs) – gTLDs
as well as ccTLDs

47.  IANA is responsible for distribution/allocation of pools of numbering
resources at the top level i.e.
 IPv4/v6 addresses
 Autonomous System Numbers used for routing Internet traffic.
 When an RIR requires more IP addresses/ASNs for allocation or
assignment within its region, IANA makes an additional allocation (pool)
to the RIR.
 IANA also coordinates policies for inter-RIR transfer, as well as de-
allocation/recovery of numbering resources at top level.
 IANA performs these functions as per its global policy

48.  IANA does not make allocations directly to ISPs or end users except in
specific circumstances, such as allocations of multicast addresses or
other protocol specific needs.
 Both IPv4 and IPv6 addresses are generally assigned in a hierarchical
manner.
 Users are assigned IP addresses by Internet service providers (ISPs).
 ISPs obtain allocations of IP addresses from a local Internet registry
(LIR) or National Internet Registry (NIR), or from their appropriate
Regional Internet Registry (RIR).
 It can be observed in IPv4 IANA Registry that /8 blocks have been
allocated to entities other than RIRs also.

49. TCP/IP protocol suite specifications include numbers,
keywords and other parameters that must be uniquely
assigned for correct, stable and interoperable operation of
Internet devices.
Examples include assignment of port numbers and protocol
numbers.
IANA is responsible for assigning values of these protocol
parameters.
Wireshark Example

55.  ICANN since 1998 was performing the overseer/coordination responsibility of
Internet’s unique identifiers, via its IANA function as per a renewable
contract with US Govt. Department of Commerce’s NTIA.
 NTIA announced in March 2014 that it was planning to end its contract with
ICANN, paving the way for relinquishing US Govt.’s control (stewardship) of
Internet’s core functions.
 ICANN launched a multi-stakeholder process to gather community inputs on
principles and mechanisms for transitioning NTIA's stewardship of IANA
functions.
 Subsequently, ICANN constituted the IANA Stewardship Transition
Coordination Group (ICG), with representation from three communities.

56.  ICG released a request for proposal to communities
interested in and/or affected by the IANA transition.
IETF created an IANAPLAN Working Group to formulate
its proposal on behalf of the protocol parameters
community.
 IETF (RFC 7979) and two other communities developed
proposals/replies after consultations with their respective
stakeholder communities, and submitted them to ICG.

57.  ICG then transmitted the consolidated proposal to ICANN Board.
 ICANN Board approved and sent the consolidated proposal, along with
the CCWG Accountability WS1 proposal to US Government’s NTIA for
approval.
 NTIA approved the consolidated proposal, and IANA transition came
into effect in October 2016.
 IANA transition transferred the control of IANA function from US Govt.
oversight (stewardship) to a global multistakeholder community (a non
governmental / non inter governmental setup).

60. ICANN
gTLD Registrar (Godaddy,
BigRock)
gTLD Registry
Operator
(.com – Verisign
.info – Afilias)
gTLD Registrant

61. • ICANN is global domain name overseer
• Develops policies for gTLDs
• Coordinates policy development for
ccTLDs via ccNSO
• Enters into an agreement with Registrars
and Registry Operators

62. • The final client (end-user / organization)
who wishes to register the domain
name
• For example Google Inc. is the
Registrant if it wishes to register the
domain name google.com

63. • A (domain name) Registry is the
authoritative database of all domain names
registered under a certain top level domain
(TLD) eg .com and .in
• .in Registry has 2.2 million domain
names at Second Level

64. • It is an organization that manages the domain name
Registry w.r.t. policies of domain name allocation,
technical operation etc.
• There is a dedicated Registry Operator to manage each
domain name Registry.
• Registry Agreement is the contract that governs the
relationship between ICANN and a Registry Operator.
• Some well known examples of Registry Operators are
Verisign, Afilias etc.
• NIXI is Registry Operator for .in ccTLD Registry

65. • It is an organization that acts as an
intermediary between a Registry Operator
and the Registrants.
• A Registrar is the entity that directly
interacts with (and allots domains to)
Registrants.
• Some well known examples of Registrars
are GoDaddy, MarkMonitor, BigRock etc.

66. Types of WHOIS:
For domain names, Domain name Registration Data (DNRD)
popularly called WHOIS is collected by Registrars at the time
Registrants register for a new domain name
Domain name WHOIS data has 4 sections – Registrant /
Administrative / Technical / Billing Contact
For numbering resources also, WHOIS database is
maintained.

67. • Just like DNS, WHOIS is not a single, centrally
managed (i.e. it is a distributed) database
• Rather, registration data is held in disparate
locations and administered by multiple registries
and registrars.

68. • Determine whether a domain is available for registration
• Contact domain/web administrators regarding technical
issues related to a domain or website
• Obtain the real world identity, business location and
contact information of an online merchant or business
• Security professionals and LEA’s use WHOIS to
identify points of contact for a domain name

70.  Problems in legacy WHOIS protocol needed to be fixed
 IETF Web Extensible Internet Registration Data Service (weirds) Working Group
designed Registration Directory Access Protocol (RDAP) that will be WHOIS
successor.
 RDAP caters to WHOIS for both names and numbers
 Utilizes RESTFUL Web Services for WHOIS request/response
 Utilizes JSON as the format for data

71. • Policy work – ICANN Generic Names Supporting Organization (GNSO)
• Technical / Protocol work – IETF Web Extensible Internet Registration
Data Service (WEIRDS) Working Group
RFC 7480 - HTTP Usage in the Registration Data Access Protocol (RDAP)
RFC 7481 - Security Services for the Registration Data Access Protocol
(RDAP)
RFC 7482 – Registration Data Access Protocol (RDAP) Query Format
RFC 7483 – JSON Responses for the Registration Data Access Protocol
(RDAP)
RFC 7484 – Finding the Authoritative Registration Data (RDAP) Service
RFC 7485 - Inventory and Analysis of WHOIS Registration Objects

72. WHOIS for domain names
WHOIS for numbers

74.  A standard is a set of rules that a group agrees to follow for compatibility and
interoperability
 Is English language a standard? YES.
 Examples of standards for the Internet:
 Protocols: HTTP, TCP, IP, TLS
 Data representation: ASCII, UTF-8
 Languages: HTML5, JavaScript, CSS
 Standards adoption can be Mandatory to implement or Voluntary
 ANSI standards are mandatory, IETF standards are voluntary.

75. My pen drive works across Desktops, Laptops, TV, Smartphones coz it
follows USB standards
You send files from Samsung smartphone to iPhone coz they both follow
Bluetooth standards
Emoji’s sent from one smartphone to other render correctly coz they
follow Unicode standards

77. Physical
Link
Network
Transport
Application

80.  “We reject kings, presidents and voting. We believe in rough consensus and running code.” – David Clark
 “Rough Consensus” - Rough consensus is achieved when all issues are addressed, but not necessarily
accommodated
 You are identified as individual and not your org. affiliation
 Selection of Area directors, Chair and other roles done by NOMCOM (nominating committee)
 Nomcom formed from selected volunteers
 Anyone who has attended 3 IETFs (out of last 5) can volunteer

83.  https://www.youtube.com/watch?v=ADQmECtl0L4

85.  Held 3 times an year across the world
 6 days per meeting
 One can participate physically or remotely
 BoF sessions
 Hackathons and code sprints

86.  One can participate in IETF’s standardization work by joining Working
Group mailing lists.
 There are 130+ WG’s for 7 IETF Areas

87.  IETF chair
 Areas - Area directors (AD)
 IETF Areas
General
Applications/
Real Time
Transport
Internet Routing
Operations
and
Management
Security

89.  There is an emphasis to design Internet protocols keeping in mind human aspects
and rights.
 The HRPC Research Group is chartered to research whether standards and protocols
can enable, strengthen or threaten human rights.
 HRPC RG has recently come out with RFC8280: Research into Human Rights Protocol
Considerations

90.  Encryption and authentication measures are the focus of attention across all IETF working
groups.
 The IAB statement and documentation in RFC1984 promotes strong, ubiquitous and
opportunistic encryption and authentication mechanisms, which are turned on by default
 These concerns are particularly relevant after Snowden revelations
 RFC7258 declares pervasive monitoring as an attack.
 DNS Privacy project and DPRIVE WG aim to cryptographically secure DNS, one of oldest and
critical Internet protocols.
 Dedicated IRTF Crypto Forum Research Group.

91.  Additionally, work is underway at various stages of protocols’ design and
development for emerging technologies and modern Internet protocols like
 TLS 1.3 Internet of Things
 QUIC Multipath TCP
 Captive Portals YANG model
 DANE Home Networking
 IPWAVE SIDR

93.  TLS provides cryptographic security in the communication between two
hosts over Internet.
 It provides Confidentiality, Integrity, Authentication.
 TLS Supports both Server and Client Authentication, but mostly Server
authentication is used (e.g. using Secure NetBanking).
 TLS is used most commonly in web browsers (e.g. for NetBanking).
 HTTP+TLS=HTTPS
 However, it can be used with any application layer protocol that uses
TCP as the transport layer. e.g. POP3S.

94.  SSL was originally a Netscape project realized in association with
MasterCard, Bank of America, MDI & Silicon Graphics.
 The first version, SSLv1, wasn't released.
 SSLv2 was replaced by SSLv3 in 1999 because of security problems.
 At this time, SSL became a standard so IETF bought a patent and
created TLS in 2001 (standard actually used a derivation of SSLv3).

95.  TLS 1.0 -> RFC2246 (1999)
 TLS 1.1 -> RFC4346 (2006)
 TLS 1.2 -> RFC5246 (2008)
 TLS 1.3 -> 2018?
 TLS Extensions: Extension Definitions -> RFC 6066
 Prohibiting Secure Sockets Layer (SSL) Version 2.0 –> RFC 6176
 TLS 1.2 is mostly in the wild (most used) out of SSL / TLS protocols

96.  Datagram Transport Layer Security (DTLS) is a communications protocol that provides security for
datagram-based applications.
 TLS was designed for TCP-based applications only
 DTLS 1.0 -> RFC4347
 There is no DTLS 1.1; that version number was skipped in order to harmonize version numbers with
TLS.
 DTLS 1.2 -> RFC6347
 DTLS 1.3 under development

97.  Biggest TLS overhaul in 10+ years
 Reduces handshake protocol time from 2 RTT (TLS 1.2) to 1 RTT (TLS 1.3)
 Support for following insecure protocols/algorithms is being removed in TLS 1.3:
 RC4 Steam Cipher
 RSA Key Transport
 SHA-1 Hash Function
 CBC Mode Ciphers
 MD5 Algorithm
 Various Diffie-Hellman groups
 EXPORT-strength ciphers
 DES
 3DES

98.  TLS – Transport Layer Security
 UTA – Using TLS in Applications

99.  OpenSSL
 WolfSSL
 BoringSSL
 GNUTLS
 LibreSSL

101.  Organizations dominant in Internet standardization process:
 Ericsson, Cisco, Juniper, Huawei, SalesForce
 Negligible presence of homegrown Indian organizations
 Indians are followers of standards and technologies, long after
inventions are done by Western world
 TCS Indigenous RFC on IoT:
 RFC 7967 (Constrained Application Protocol (CoAP) Option for No Server
Response)
 Reliance Jio boosts India past 25% IPv6 capability

102.  Attend IETF meetings physically and remotely (Remote hubs,
meetecho)
 Join ISOC chapters (6) in India and participate
 Attend MeitY / NIXI roundtables
 Submit new Internet drafts
 Join WGs and participate in mailing lists