1969
ARPANET connects its first four hosts
The initial ARPANET connected four host computers. It demonstrated packet-switched networking between independently located systems.
Infrastructure and operations
How the field of a Network Engineer got here: the sourced milestones from every published course of this career, on one axis.
1969 to 2025
266 milestones across 28 courses
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
35 milestones
1969
The initial ARPANET connected four host computers. It demonstrated packet-switched networking between independently located systems.
1969 Oct
ARPANET connected its first nodes and demonstrated packet-switched communication between hosts.
1973
Ethernet introduced a local-network technology that became a dominant link-layer technology for computers and workstations. It separated local frame delivery from wider-area internetworking.
1973
Vint Cerf and Bob Kahn described a protocol for interconnecting packet networks, establishing the architecture later divided into TCP and IP.
1974
Vint Cerf and Bob Kahn describe TCP, the protocol that would become the foundation of internet communication. The design separated network interconnection from the applications running above it.
1974
Cerf and Kahn described a protocol for interconnecting packet networks, establishing the design problem that became TCP/IP.
1974 Dec
RFC 675 documented an early Internet Transmission Control Program with connection state, acknowledgments, windows, and retransmission concepts.
1974 Dec
RFC 675 described an early Internet TCP design with connections, sockets, sequencing, and flow-control concepts. It established a transport-layer model above packet switching.
1980
RFC 760 redefines the Host-Level Protocol as Internet Protocol, splitting networking functions into a distinct layer. This separation gave IP its own specification separate from TCP.
1980 Jan
RFC 761 described a DoD standard TCP for reliable host-to-host communication across interconnected packet-switched networks.
1980 Aug
RFC 768 specified the User Datagram Protocol, defining its minimal datagram header and service.
1981 Jan
RFC 791 defines 32-bit addresses, the header format, connectionless datagram delivery, and the fragmentation model. This is the protocol specification that still governs IPv4 today.
1981 Sep
RFCs 791, 793, and 768 defined Internet Protocol, Transmission Control Protocol, and User Datagram Protocol as separate layers.
1981 Sep
RFC 791 published the Internet Protocol specification for IPv4. It provided the packet format and forwarding model that made inter-network delivery a distinct layer.
1981 Sep
RFC 793 specified TCP's reliable, in-order byte-stream service and its connection, sequencing, acknowledgment, and control behavior.
1983 Jan
The ARPANET transition to TCP/IP established the protocol suite as the common basis for internetworking.
1983 Jan
ARPANET changed its host protocol from NCP to TCP/IP in a coordinated transition. The change made the TCP/IP suite the common basis for host communication on that network.
1983 Jan 1
ARPANET hosts transitioned from NCP to TCP/IP, making the protocol suite the network's required communication basis.
1983 Jan 1
ARPANET completes its migration from NCP to TCP/IP on flag day. Every host on the network switches in a single coordinated event, establishing TCP/IP as the universal network protocol.
1983 Nov
RFC 882 described a distributed domain system with a hierarchical tree, referrals, caching, and timeouts. It established the architectural model that replaced a single host table.
1983 Nov
RFC 882 described a tree-structured domain name space and name servers. It moved name-to-resource lookup beyond a single shared host table.
1984
The Domain Name System replaced a single host table approach with a distributed, hierarchical naming system.
1985 Sep
BOOTP defines an IP and UDP bootstrap exchange for clients that need an address and boot information. DHCP later extends this client-server configuration model.
1985 Sep
The first NTP RFC defines a distributed client-server protocol over UDP for synchronizing network clocks.
1986
NSFNET became a major backbone for research and education networks and accelerated Internet growth.
1986
Cisco records that its early engineering work included software that became Cisco IOS. IOS became the common software foundation for Cisco routers as the company grew.
1987 Nov
RFC 1034 defines the domain name system concepts used by authoritative servers and resolvers. DNS became a control point that could influence which application address a client later uses.
1987 Nov
DNS standardized a distributed hierarchical namespace with authority, delegation, caching, and resolvers. Operations gained a model where updates propagate through independently cached copies rather than becoming instantly universal.
1987 Nov
RFC 1034 documented DNS as a distributed database with hierarchical names and resource records. It addressed the scaling limits of distributing a single HOSTS.TXT file.
1987 Nov
RFC 1034 replaced the earlier concepts document and described the namespace, delegation, zones, resolvers, and caching model. These remain the foundation for tracing authority today.
1987 Nov
RFC 1035 replaced the earlier implementation document with the protocol format and record definitions. It made the query, response sections, flags, and core resource records interoperable.
1988 Jul
Version 1 documents the protocol structure, hierarchy, selection algorithms, and local-clock control model.
1989 Jun
RFC 1105 documents the Border Gateway Protocol for exchanging reachability information between autonomous systems. This created the interdomain routing basis used by Internet-scale anycast.
1989 Oct
RFC 1122 documented host requirements for Internet protocols, including TCP and UDP implementation requirements and application responsibilities.
1989 Oct
Version 2 updates the specification and implementation guidance for the evolving Internet protocol.
56 milestones
1990
RFC 2068 records HTTP in use on the World-Wide Web since 1990 and identifies HTTP/0.9 as the first version. The early protocol established the request-and-response role that later versions expanded.
1991
The Web added a hypertext application on the Internet, reinforcing the distinction between the underlying network and a service that uses it.
1992 Mar
Version 3 consolidates the protocol, filtering, selection, and local-clock algorithms into a widely deployed specification.
1992 May
RFC 1323 specified window scaling, timestamps, and protection against wrapped sequence numbers for long-delay or high-bandwidth paths.
1992 Dec
Cisco lists IOS 9.1 as first customer shipped in December 1992. It provides a dated anchor for the commercial IOS release line.
1993
RFC 1518 and RFC 1519 introduce CIDR, replacing the classful A/B/C allocation system. Prefix-length notation lets blocks be any size and enables route aggregation across the internet.
1993
IANA is restructured to coordinate IPv4 address allocation through regional registries. The change establishes the administrative framework that distributes address blocks to RIRs worldwide.
1993 Sep
RFC 1519 specified classless prefixes and route aggregation, allowing address allocation and forwarding to use variable-length prefixes.
1993 Sep
RFC 1519 proposed classless inter-domain routing to slow routing-table growth and improve address allocation. Prefix length became central to route aggregation and longest-match forwarding.
1993 Oct
RFC 1531 defines DHCP as a protocol for delivering host configuration and allocating network addresses. It establishes DHCP as an extension of BOOTP.
1993 Oct
RFC 1541 replaces RFC 1531 after editorial corrections. The protocol's client-server allocation and configuration purpose remains the central model.
1993 Nov
RFC 1546 describes an IP anycasting service in which a datagram is delivered to one accepting server. It established the service-selection idea later used for distributed front doors.
1994 May
RFC 1631 described network address translation at a boundary between private and public addressing realms.
1995 Feb
RFC 1918 reserved three IPv4 blocks for private internets, making private addressing a defined part of many local network designs.
1995 Feb
Netscape released SSL 2.0 as the first public transport encryption protocol for the web. Its design limitations—MD5-only MAC, shared encryption and authentication key, unprotected handshake—drove a complete redesign within a year.
1995 Mar
RFC 1771 specifies BGP-4 and its route advertisement model. BGP-4 became the routing protocol context for global route announcements.
1995 Apr
Apache begins as patches to NCSA HTTPd. The project establishes a modular, community-maintained server line that becomes a standard deployment choice.
1995 Apr
Cisco notified IOS 9.1 users to move to IOS 10.0 or 10.2 after the last IOS 9.1 maintenance release. Release maintenance and upgrade choice became part of operating the platform.
1995 Apr
Internet backbone traffic shifted toward commercial providers and interconnected networks rather than a single federally funded backbone.
1995 Dec
Apache 1.0 formalizes a modular architecture. Server capability increasingly comes from configured modules rather than a fixed file-serving core.
1995 Dec
RFC 1883 defined IPv6 as an IPv4 successor with 128-bit addresses and a revised header design. It put address-space growth and protocol evolution into the Internet-layer roadmap.
1996
RFC 1918 reserves three blocks for private use: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. Organizations can reuse these blocks internally without consuming globally routable address space.
1996 May
HTTP/1.0 documented a message-oriented protocol with headers, methods, and status codes. It provided the first RFC specification for the version used by early web clients and servers.
1996 Aug
DNS NOTIFY let a primary server signal that zone data changed so secondary servers could check for updates. It reduced reliance on waiting for the next refresh interval after a change.
1996 Aug
DNS NOTIFY gave primaries a way to prompt secondaries to check for new zone data. It reduced avoidable refresh delay without replacing serial comparison and zone transfer.
1996 Oct
Simple NTP defines a reduced synchronization protocol for applications that do not implement the full NTP algorithms.
1996 Nov
A complete protocol redesign by Kocher, Karlton, and Freier separated data transport from the message layer and added Diffie-Hellman key exchange. SSL 3.0 became the foundation for all subsequent TLS versions.
1997
RFC 2131 standardizes DHCP, automating IPv4 address assignment and configuration for hosts on a network. Dynamic leases replaced manual address management for most end-user devices.
1997
Gerald Combs began the project to troubleshoot network problems and learn more about networking. The project established packet dissection as its practical focus.
1997 Jan
The first HTTP/1.1 specification addressed persistent connections, hierarchical proxies, caching, and virtual hosts. Those concerns made intermediaries and connection reuse part of normal HTTP practice.
1997 Mar
RFC 2131 updates RFC 1541 and defines the DHCPv4 message exchanges, client states, lease handling, and relay behavior used in practice.
1997 May
Researchers at MIT published "Consistent Hashing and Random Trees", the algorithm that let a cache selection survive server additions and removals. It became the core request-routing idea behind the first large commercial CDN.
1997 Jun
The first IEEE 802.11 standard defined CSMA/CA, the MAC and PHY that every subsequent amendment builds on, with 1 and 2 Mbps rates using spread spectrum in the 2.4 GHz band.
1997 Dec
Juniper's 1999 annual report records that the JUNOS operating system shipped to customers in December 1997. It established the software base before the first router hardware shipment.
1998
IEEE 802.1D-1998 became the referenced MAC bridge standard. It provided the baseline that later spanning-tree revisions extended.
1998
Cisco describes IOS 11.3 and later as port-ready through finer modularity. That architecture made feature sets more manageable across hardware platforms.
1998
RFC 2460 publishes the IPv6 specification with 128-bit addresses, designed to replace the finite IPv4 address space. The larger address eliminates the need for NAT and private addressing in the long term.
1998 Mar
The specification clarified how resolvers cache negative answers. Operators had to account for NXDOMAIN and no-data cache lifetimes when adding or correcting records.
1998 Jul
The first public release made the analyzer available for community patches and dissector contributions. Protocol support could expand when contributors needed a new decoder.
1998 Jul
Juniper's company backgrounder dates the release of Junos OS to July 1998. The software became the common operating model associated with the company's network platforms.
1998 Aug
The MIT research team incorporated Akamai to commercialize distributed content delivery. The company grew out of the 1998 MIT $50K business-plan competition, where the consistent-hashing delivery proposal was a finalist.
1998 Sep
ICANN began coordinating Internet unique identifiers, including the DNS and IP address allocation functions.
1998 Sep
The annual report records the first wire-speed M40 shipment in September 1998. Junos moved from a shipped operating system to the control software for a deployed router platform.
1998 Nov
RFC 2401 defined a security architecture for IP traffic using authentication, encapsulation, and security associations. It gave site-to-site and host-to-host protection a common standards-track foundation.
1998 Dec
RFC 2460 specified the IPv6 protocol and its 128-bit addressing model as the successor to IPv4.
1998 Dec
IPv6 defined a 128-bit addressing protocol to extend Internet addressing beyond IPv4.
1998 Dec
The revised specification becomes the reference for the base header, extension headers, forwarding, and fragmentation behavior.
1998 Dec
Stateless Address Autoconfiguration documents address formation and Duplicate Address Detection, making router advertisements central to host configuration.
1999 Jan
The IETF standardized SSL as Transport Layer Security. TLS 1.0 replaced the custom MAC with HMAC and expanded alert codes, but remained close enough to SSL 3.0 that downgrade attacks were a known concern from the start.
1999 Mar
802.11b brought 11 Mbps to the 2.4 GHz band for broad consumer adoption, while 802.11a moved to 5 GHz with OFDM at 54 Mbps, establishing the dual-band model that defines wireless design.
1999 Mar
RFC 2308 clarified caching of name errors and missing data. It made the operational distinction between NXDOMAIN and a NOERROR response without the requested type explicit.
1999 Apr
Akamai launched its commercial content delivery service and was listed on NASDAQ the same year. Delivery of web objects through distributed surrogates became a purchasable service rather than a research prototype.
1999 Jun
The Apache HTTP Server project moves into the new foundation. The server becomes part of a durable open-source governance and release structure.
1999 Jun
RFC 2616 replaced RFC 2068 as the HTTP/1.1 specification. It consolidated the protocol that became the common reference for HTTP/1.1 implementations before the later HTTPbis split.
1999 Jul
CERT reporting described widespread deployment of networks using tools such as trinoo and Tribe Flood Network. Defenders had to treat coordinated traffic sources and compromised intermediaries as an operational problem.
1999 Aug
EDNS(0) added an extension mechanism and an OPT pseudo-record to DNS messages. It made capability negotiation and larger UDP DNS messages possible without changing the base header.
45 milestones
2000 Jan
RFC 3046 defines relay-supplied information that can identify the client access circuit or remote identity. It makes relay context usable for more specific server policy.
2000 Feb
Public attacks against major e-commerce sites demonstrated that distributed flooding could disrupt prominent Internet services. The event accelerated attention to coordinated detection and response.
2000 Mar
Apache 2.0 introduces a new generation of the server. Its multi-processing modules make process, thread, and event-style handling explicit deployment choices.
2001
HAProxy 1.0 is developed to offload traffic from hardware load balancers. This established a software-based proxy path for distributing client traffic to backend servers.
2001
RFC 3022 defines traditional NAT and Network Address Port Translation. The specification formalizes address and port mapping between private and public realms, extending the life of IPv4 address space.
2001 Jan
RFC 3040 standardized the vocabulary for replication and caching infrastructure, defining the surrogate as a gateway delegated authority to act for an origin server. CDN engineering gained shared terminology for the roles that make up a delivery network.
2002
HAProxy 1.1 adds round-robin scheduling, health checks, and improved logging. Backend eligibility and traffic selection become explicit operational concerns.
2002 Oct
DDoS attacks against root name servers reinforced that service availability depends on name resolution as well as an application's own hosts. DNS capacity and distribution became explicit resilience concerns.
2002 Nov
NIST SP 800-48 set out security recommendations for wireless networks as WLAN use expanded. It established that radio networks needed dedicated configuration, access-control, and monitoring treatment.
2003
HAProxy 1.2 adds client-side IPv6 support and the forwardfor keyword. Proxy deployments must account for both network addressing and client-context propagation.
2003 Apr
The addressing architecture records IPv6 address types and representations used in routing and interface configuration.
2003 Jun
802.11g combined 802.11a's OFDM modulation with 802.11b's 2.4 GHz band, delivering 54 Mbps with backward compatibility and putting Wi-Fi in every home and office.
2003 Jul
RFC 3568 documented the known techniques for directing clients to surrogates — DNS-based, transport-layer, and application-layer routing. The selection criteria described there, including network proximity, load, and content availability, still govern edge selection.
2003 Jul
RFC 3315 introduces DHCP for IPv6 with a distinct message format, identifiers, state machine, and configuration model.
2003 Sep
RFC 3513 documented the IPv6 addressing architecture, including address types and the notation used to write IPv6 addresses.
2003 Oct
RFC 3596 defined the AAAA record and the ip6.arpa reverse-mapping domain for IPv6. DNS operators gained a standard way to publish and reverse-map IPv6 addresses.
2003 Dec
RFC 3633 defines DHCPv6 prefix delegation. A requesting router can receive a prefix for use on downstream links rather than only a host address.
2004
The 802.1w rapid-reconfiguration work was incorporated into 802.1D-2004. Faster recovery became part of the bridge-standard path.
2004 May
Cisco announced IOS XR as a new IOS family member for terabit-scale, distributed carrier routing. It introduced a purpose-built path beyond the classic monolithic IOS model.
2004 Oct 4
NGINX is released publicly after being designed around the C10K problem. Its event-driven model makes large numbers of slow connections a central web-server design concern.
2005 Mar
RFC 4033 introduced the DNSSEC security framework and its new record types and protocol changes. Validating resolvers could authenticate DNS data and denial of existence through a chain of trust.
2005 Mar
DNSSEC defined authenticated DNS data and the delegation chain of trust. Zone correctness now included signatures, DNSKEY data, and parent DS coordination.
2005 Apr
IEEE 802.1AB defined discovery of adjacent devices and connection endpoints. Physical-neighbor information became standardized for Ethernet operations.
2005 Dec
IEEE approved the 802.1Q revision in December 2005; it was published in 2006. The revision specified interoperable MAC-bridge operation for VLANs.
2006
HAProxy 1.3 introduces TCP scripting, explicit source-port ranges, and interface binding. Proxy policy extends below HTTP routing to connection behavior.
2006 Feb
The updated architecture defines unicast, anycast, and multicast addressing and confirms that IPv6 has no broadcast addresses.
2006 Apr
Added explicit per-record initialization vectors for CBC cipher suites, addressing the chosen-plaintext weakness that the BEAST attack later demonstrated against TLS 1.0 in practice.
2006 May
The project changed its name after its original author could not retain the Ethereal trademark. Development continued under the Wireshark name.
2006 Aug
RFC 4632 documented the CIDR address strategy and its routing-table scaling purpose. It preserved prefix-based aggregation as a practical Internet routing technique.
2006 Dec
RFC 4786 publishes best current practice for operating anycast services. It calls out location-dependent monitoring, changing client populations, and data synchronization constraints.
2006 Dec
NETCONF standardized XML-encoded RPC operations for retrieving and changing device configuration. It established a programmatic management interface distinct from interactive command entry.
2007 Aug
RFC 4987 collected mitigations for exhaustion of TCP half-open connection state, including filtering, SYN cookies, proxies, and hybrid approaches. It made delayed state allocation a documented defense principle.
2007 Sep
Neighbor Discovery consolidates router discovery, on-link information, address resolution, reachability detection, and redirects in ICMPv6.
2007 Sep
RFC 5007 defines a way to query DHCPv6 lease binding data. It supports devices that need to learn client information held by a DHCPv6 server.
2007 Dec
RFC 4732 described denial-of-service threats across protocols, hosts, and networks and the tradeoffs of mitigations. It established a cross-layer view rather than a single-appliance model.
2008
Wireshark reached version 1.0 after ten years of development. Its release coincided with the first Wireshark Developer and User Conference, Sharkfest.
2008 Feb
Juniper's release archive lists Junos 9.0 with a February 2008 publication date. Operators could track a regular documented release train rather than treat Junos as one static CLI.
2008 May
Cisco's IOS XE configuration guide records IOS XE 2.1 as the first release of that book. IOS XE became the IOS-family path for platforms with a modern Linux operating system beneath the networking software.
2008 Jun
IEEE 802.1ah was approved to support interoperable provider-bridge networks and larger service-VLAN scale. Bridging concepts expanded beyond a single enterprise LAN.
2008 Aug
Replaced hardcoded hash functions with cipher-suite-specified pseudo-random functions and added AEAD modes such as AES-GCM. TLS 1.2 remains the compatibility floor for current deployment guidance.
2008 Sep
Cisco renamed its SAN operating system NX-OS as it pursued a unified data-center fabric. IOS-style command familiarity continued in a product with a distinct data-center focus.
2009
HAProxy 1.4 adds server stickiness and ACL-based persistence. Backend selection can now preserve a relationship across requests rather than treating every request independently.
2009 Sep
802.11n added multiple-input multiple-output spatial streams, channel bonding, and frame aggregation, raising theoretical rates to 600 Mbps and making MIMO the foundation of modern wireless capacity.
2009 Sep
NIST SP 800-41 Rev. 1 updated its firewall guidance with policy, selection, configuration, testing, deployment, and management considerations. Firewall operation became a lifecycle concern rather than only a perimeter-device purchase.
2009 Sep
RFC 5681 consolidated TCP congestion-control behavior, including slow start, congestion avoidance, fast retransmit, and fast recovery.
91 milestones
2010
HAProxy 1.5 adds SSL, compression, and server-side keep-alive. The client-facing and backend-facing connection policies become more independently configurable.
2010 Feb
Juniper's archive dates JunosE 10.0 documentation to February 2010. Release and platform context became a practical part of interpreting feature and command availability.
2010 Jun
NTPv4 updates the protocol and algorithm specification that anchors current packet, association, and clock-discipline terminology.
2010 Jun
The standard described full-zone transfer behavior over TCP. Transfer authorization and failure handling became explicit interoperability requirements.
2010 Jul
The root-zone deployment made cryptographic trust anchors available from the top of the DNS hierarchy. It made authenticated DNS responses a practical part of the internet's security architecture.
2010 Aug
The recommendation makes IPv6 addresses easier to compare in logs and documentation by defining a canonical text representation.
2010 Oct
YANG provided a language for describing configuration and state data, operations, and notifications. Automation could then reason about modeled structure instead of only command text.
2010 Dec
AWS announces Route 53 as a managed authoritative DNS service for routing end users to Internet applications. It made programmable DNS steering available as a cloud service.
2011
The IEEE 802.1Q history records a 2011 edition among the successive VLAN and bridge standards. The bridging specification continued to gather related functions into the 802.1Q line.
2011 Feb 3
IANA allocates its last free /8 blocks to regional registries, exhausting the central IPv4 pool. Five /8 blocks are distributed to RIRs, marking the end of unallocated address space at the IANA level.
2011 Apr 12
NGINX reaches a stable 1.0 release. Its static serving and proxying pattern becomes a common way to put an event-driven edge in front of application processes.
2011 Jun
The revised NETCONF standard defined the protocol's current base behavior, including capability exchange and configuration datastore operations. Capability discovery became a required step before using optional behavior.
2011 Jun
Participating operators enabled IPv6 for a coordinated one-day production test before wider permanent deployment.
2011 Sep
Rizzo and Duong showed a practical chosen-plaintext attack against TLS 1.0 CBC mode that could recover HTTPS session cookies. The attack validated the per-record IV fix in TLS 1.1 and accelerated the case for TLS 1.2 adoption.
2012
The working group began HTTP/2 work from SPDY, then changed its format, compression, and HTTP mapping through the standards process.
2012
Telecom operators published the original NFV concept white paper and ETSI formed the NFV Industry Specification Group. The work shifted discussion from dedicated appliances toward a common virtualization architecture.
2012 Feb
NIST SP 800-153 consolidated recommendations for securing wireless clients, access points, switches, and monitoring throughout the WLAN lifecycle. Wireless security became an operational design and monitoring concern, not only a passphrase choice.
2012 Mar
IEEE 802.1aq was approved in 2012. It specified shortest-path bridging with multiple active topologies, an alternative to one blocked-tree forwarding arrangement.
2012 Apr
APNIC, serving the Asia-Pacific region, reaches its last /8 block and enters tiered allocation. New requests receive smaller blocks as the remaining pool diminishes.
2012 Jun
Participating websites, access providers, and equipment makers committed to enable IPv6 permanently alongside IPv4.
2012 Jun
Participating networks, websites, and access providers enabled IPv6 permanently, moving deployment from testing toward routine operation.
2012 Sep
RFC 6707 framed the problem of one CDN delegating delivery to another, defining the upstream and downstream CDN roles, the surrogate terminology this course uses, and the four interconnection interfaces for control, request routing, metadata, and logging.
2012 Nov
Juniper's archive dates JunosE 12.3 documentation to November 2012. The archived record reinforces the need to verify behavior against the target release.
2012 Dec
The guidance organized signing, key storage, and rollover procedures around timing and cache behavior. DNSSEC deployment became an operational lifecycle rather than a one-time record change.
2013 Dec
802.11ac operated exclusively in 5 GHz with wider channels, more spatial streams, and 256-QAM, pushing theoretical rates past 1 Gbps and making wireless a credible alternative to wired access.
2014
ETSI published the early NFV documentation that became the basis for the following interoperability work. The architecture moved from a concept toward specified functional relationships.
2014 Feb
CISA's alert documented UDP-based amplification vectors and mitigation considerations. Reflection and spoofed-source traffic became a routine part of defensive planning.
2014 Feb
The first Cybersecurity Framework provided voluntary, risk-based guidance for managing critical-infrastructure cybersecurity. It gave network controls a shared way to connect technical work to organizational risk outcomes.
2014 Jun
RFC 7230 defined HTTP/1.1 message syntax and routing as part of the HTTPbis revision. Splitting the former monolithic specification let message framing and routing evolve alongside separate semantics and caching documents.
2014 Jun
A standard YANG model for IP management demonstrated how network-management data could be represented in reusable schema. Practitioners could connect protocol automation to defined domain data.
2014 Oct
Google researchers demonstrated a padding oracle attack against SSL 3.0 CBC mode. All major browsers disabled SSL 3.0 within weeks, effectively ending support for any protocol version below TLS 1.0.
2014 Nov
IEEE 802.1Q-2014 incorporated earlier 802.1Q amendments and much functionality previously specified in 802.1D. VLAN and bridged-network practice moved toward one combined standard.
2014 Dec
RFC 7413 specified a mechanism for exchanging data during the TCP handshake when a client has a valid cookie.
2015
Jeremy Stretch starts NetBox at DigitalOcean to support automated network provisioning with a dedicated IPAM and DCIM model.
2015
ETSI started Release 2 to specify deployable NFV capabilities and interoperability among MANO functions. The work covered requirements, architecture, interfaces, information models, protocols, and tests.
2015
Wireshark 2.0 shipped with a new user interface. The change updated how practitioners navigate packet lists, details, and analysis views.
2015 Feb
Approval completed the standards-track process for HTTP/2 and its header-compression format before their RFC publication.
2015 Apr
Defined a signaling cipher suite value that prevents protocol downgrade attacks by letting a server detect when a client has fallen back to a lower TLS version than the server supports.
2015 May
HTTP/2 standardizes binary framing, stream multiplexing, and header compression. Servers must map many concurrent streams on a connection without changing HTTP's request-response role.
2015 May
HTTP/2 mapped HTTP semantics onto binary frames and multiplexed streams. Practitioners could change connection behavior without changing the meanings of methods, status codes, and fields.
2015 May
HPACK standardized header compression with static and dynamic tables for HTTP/2 field sections.
2015 Jun
Juniper's archive lists Junos OS 15.1 as published in June 2015. The long-running release record is why a production change needs a platform-and-release check.
2015 Jul
Kubernetes reached its v1.0 release, establishing the platform that later networking APIs and implementations build upon.
2015 Sep
ARIN, serving North America, exhausts its IPv4 free pool. Requests for new address space are placed on a waiting list, and the transfer market becomes the primary source of IPv4 addresses.
2016
HAProxy 1.7 introduces a Runtime API and server hot reconfiguration. Operators can change parts of traffic handling without a full process restart.
2016 Mar
The second wave of 802.11ac introduced downlink multi-user MIMO, allowing access points to serve multiple clients simultaneously and shifting capacity planning from per-link to per-airtime.
2016 Mar
RFC 7766 clarified that full DNS implementations support TCP and described operational requirements for persistent TCP connections. It reinforced that UDP-only reachability is not enough for complete DNS behavior.
2016 Jun
DigitalOcean agrees to release NetBox publicly. The project positions itself as a network source of truth with a REST API from early on.
2016 Jul
Early public versions ship after the announcement, giving operators a Django and PostgreSQL application they can self-host.
2016 Jul 6
Traefik's first stable release supports configuration from container and orchestration systems. Proxy routing can now follow service discovery in dynamic deployments.
2016 Aug
YANG 1.1 revised the data-modeling language used by NETCONF and RESTCONF systems. Model validation and capability support remained central to interoperable automation.
2016 Sep
Release 2 added specifications for virtualized-resource management and network-service and VNF lifecycle management. It gave multi-vendor implementations more concrete interface and information-model material.
2016 Oct
CISA alerted organizations to Mirai activity using compromised Internet-connected devices. Defensive planning had to account for large, distributed sources outside conventional server botnets.
2016 Oct
ETSI announced OSM Release ONE as an open-source MANO stack aligned with NFV. Its VNF, VIM, and SDN-controller interoperability work made the architecture inspectable in a running implementation.
2016 Dec
RFC 8006 defined the metadata exchanged between interconnected CDNs, including the acquisition source and cache-control policy a downstream CDN applies. The cache object in that model carries the TTL and serving-stale policy decisions that govern a surrogate's stored responses.
2017
HAProxy 1.8 introduces multithreading and a new multiplexer layer. Proxy capacity and protocol handling evolve with concurrent workloads.
2017
Cisco documents IOS XR Release 6.x moving from 32-bit QNX to 64-bit Linux. The change supported programmatic provisioning, telemetry, and access to the underlying Linux environment.
2017
ETSI started Release 3 to extend the framework for global deployment and operations. Its work included operational concerns, edge computing, network slicing, cloud-native VNFs, and acceleration.
2017
RFC 8200 replaces RFC 2460 as the IPv6 specification. The update clarifies extension header processing, flow label behavior, and neighbor discovery, consolidating the successor protocol's standard.
2017 Jan
RESTCONF standardized HTTP access to YANG-modeled data using NETCONF datastore concepts. HTTP tooling became an additional interface without removing model or datastore concerns.
2017 Mar
RFC 8085 documented requirements and guidance for applications and protocols that use UDP on the Internet.
2017 May
Cloudflare announces Load Balancing availability to all customers after an enterprise rollout. The service combines health monitoring, failover, and geographic origin selection.
2017 Jun
Kubernetes 1.7 promoted NetworkPolicy to stable, making label-based Pod communication rules a stable API while leaving enforcement to network plugins.
2017 Jul
RFC 8200 updated the IPv6 base specification and advanced it to Internet Standard status.
2017 Jul
Validating resolvers could synthesize negative answers from authenticated denial records. Negative-response behavior became more dependent on DNSSEC state and resolver cache policy.
2017 Jul
RFC 8198 allowed validating resolvers to use NSEC and NSEC3 records to synthesize certain negative answers and wildcard-positive answers. It changed cache behavior for signed zones while reducing repeated queries.
2017 Jul
RFC 8200 advances the IPv6 specification to Internet Standard status and replaces RFC 2460.
2017 Jul
RFC 8200 published the IPv6 specification as an IETF Standards Track document and obsoleted RFC 2460. It is the current base specification for IPv6 packet format and processing.
2017 Jul
The revised Path MTU Discovery specification preserves Packet Too Big feedback as the way a source learns a smaller path MTU.
2017 Jul
Wireshark 2.4 disabled the legacy GTK-plus interface by default in Windows installers and the development environment. The Qt interface became the normal path for new installations.
2017 Sep
Google Cloud announces general availability of IPv6 global load balancing with a single anycast virtual IP. The release extends global, capacity-aware backend selection to IPv6 clients.
2017 Sep
RFC 8246 defined the `immutable` Cache-Control extension, letting servers declare that a fresh response will not change during its freshness lifetime. Versioned URLs could suppress the conditional revalidation a browser reload would otherwise send.
2017 Oct
Kubernetes 1.8 added egress policy capabilities, allowing workloads to restrict connections they initiate as well as inbound connections.
2018
Chrome required signed certificate timestamps for all publicly trusted certificates. Apple enforced CT for certificates issued after October 2018. Certificate issuance became auditable by design rather than by policy.
2018
HAProxy 1.9 adds end-to-end HTTP/2 and gRPC support. A proxy can preserve newer application protocols across both legs of the request path.
2018 Feb
GitHub reported a 1.35 Tbps, 126.9 million-packet-per-second attack using publicly reachable memcached instances with UDP enabled. The incident showed why upstream diversion and filtering remain necessary even after adding transit capacity.
2018 Mar
The datastore architecture separated intended, applied, and operational information into named conceptual datastores. Automation could make its desired-versus-observed comparison more explicit.
2018 Jul
Cloudflare announces Dynamic Steering for selecting the fastest origin pool from a Cloudflare region. The feature illustrates a managed latency signal feeding a pool-selection policy.
2018 Aug
Removed RSA key exchange, eliminated CBC ciphers, and reduced the handshake to one round trip. Mandatory forward secrecy and authenticated encryption became baseline properties rather than optional enhancements.
2018 Sep
An early large-scale edge deployment made the UDP and QUIC operational path available before the final RFCs.
2018 Oct
Juniper's archive lists a combined Junos OS and Junos OS Evolved 18.3 documentation release in October 2018. Operators began to encounter release material that identifies both product lines.
2018 Oct
The HTTP mapping over IETF QUIC adopted the HTTP/3 name, separating it from the earlier HTTP/2 over gQUIC terminology.
2018 Nov
RFC 8415 updates and replaces RFC 3315. It consolidates DHCPv6 protocol behavior and related updates into a newer specification.
2019
HAProxy 2.0 adds a Kubernetes Ingress Controller and a Prometheus exporter. Proxy routing and observability become part of cloud-native platform operation.
2019 Feb
Wireshark 3.0 added updated capabilities including a modernized IP map and initial PKCS number 11 token support for RSA decryption. It continued the major-version evolution of the analysis tool.
2019 Mar
The Automatic Certificate Management Environment protocol behind Let's Encrypt reached IETF standard status. Fully automated issuance and renewal drove mass HTTPS adoption from roughly 45% to over 95% of web traffic.
2019 Mar
YANG Library described how a server reports the modules and schema information it implements. Clients gained a standardized way to discover model support before relying on it.
2019 Jul
The best-current-practices document collects operational guidance for source diversity, monitoring, pools, leap handling, and security.
2019 Sep
The deployment paired HTTP/3 with an existing reverse-proxy delivery path, illustrating an additive rollout rather than a replacement of HTTP/2.
2019 Sep
Standardized subscriptions made modeled event notifications part of the management interface. Automation could incorporate event-driven observation alongside scheduled collection.
2019 Oct
ETSI began Release 4 work on cloud and virtualization techniques, automation, and container-based VNF deployment. The scope expanded NFV beyond virtual-machine-only deployment patterns.
39 milestones
2020
NetBox gains a first-class plugin system so operators can add models and integrations without maintaining a soft fork of core.
2020 Feb
802.11ax introduced OFDMA, BSS coloring, and target wake time, optimizing for dense environments where channel utilization and airtime contention matter more than peak link speed.
2020 Mar
Juniper's lifecycle table records a March 2020 first-release date for Junos OS Evolved 20.1. Release selection now needs to account for the OS line as well as the version.
2020 Aug
Kubernetes 1.19 graduated Ingress to v1, stabilizing the core API for HTTP and HTTPS access to Services.
2020 Aug
NIST SP 800-207 described zero trust as moving defenses from static network perimeters toward users, assets, and resources. It formalized the shift from location-based trust to explicit access decisions.
2020 Sep
In Kubernetes 1.19, kube-proxy began reading EndpointSlices by default, replacing large single Endpoints objects with smaller backend sets.
2020 Oct
NTS adds TLS-based key establishment and authenticated NTP extension fields for client-server mode.
2020 Nov
The updated TSIG specification documented message authentication and integrity for DNS exchanges. It reinforced the distinction between authenticated transfers and confidential transfer channels.
2021
Network to Code publishes Nautobot as a hard fork aimed at tighter coupling between source of truth and automation platforms.
2021 Apr
Kubernetes 1.21 made EndpointSlice stable, cementing it as the scalable representation of Service backends.
2021 Apr
SIG Network published conformance work to compare CNI behavior across NetworkPolicy constructs, highlighting implementation differences beneath one API.
2021 Apr
Wi-Fi 6E extended 802.11ax into the 6 GHz band, providing clean, uncongested spectrum free of legacy devices and DFS requirements where regulations permit, expanding the channel reuse planning covered in this course.
2021 May
RFC 9001 specifies how TLS 1.3 secures QUIC, the UDP-based transport protocol behind HTTP/3. TLS provides the handshake and key schedule while QUIC replaces the record layer with its own packet protection.
2021 May
RFC 9000 standardized QUIC transport, enabling HTTP/3 to carry HTTP semantics over QUIC streams.
2021 May
QUIC standardized a secure, multiplexed transport over UDP. It supplied the transport foundation that HTTP/3 uses instead of TCP.
2021 May
QUIC version 1 standardized a UDP-based secure transport with multiplexed streams, integrated TLS, and connection migration support.
2021 Aug
Major release introduces a GraphQL API, IP ranges, SVG cable traces, and a redesigned interface for day-to-day operators.
2021 Aug
DNS zone transfer over TLS standardized a protected channel for AXFR and IXFR. Operators gained a standards-based option when transfer contents require confidentiality in transit.
2021 Nov
Wireshark 3.6 included display-filter syntax updates, including comma-separated set elements and clarified inequality behavior. Filter expressions remained a central analysis interface.
2022 Jun
RFC 9111 revised the core HTTP caching specification, consolidating the freshness, validation, and cache-key rules that every shared cache implements. Together with RFC 9110 it replaced the older HTTP/1.1 document set with the current semantics the course teaches.
2022 Jun
HTTP/3 standardizes HTTP over QUIC. Web servers can use QUIC streams to avoid transport-level head-of-line blocking across independent requests.
2022 Jun
RFC 9110 defined HTTP semantics as a shared specification for versions that use different message syntax and transports. It is the current reference for methods, status codes, fields, representations, and content.
2022 Jun
The HTTP/2 revision incorporated later protocol changes while preserving its TCP-based framing and stream model.
2022 Jun
HTTP/3 standardized HTTP semantics over QUIC, while QPACK standardized header compression designed for QUIC's per-stream ordering.
2022 Jun
HTTP/3 mapped HTTP semantics onto QUIC streams and control mechanisms. The change moved HTTP's transport binding while retaining the application-level request and response model.
2022 Jun
RFC 9213 defined the `CDN-Cache-Control` response header, letting an origin send different cache policies to CDN caches than to other shared caches or browsers. Publishers could grant a CDN they can invalidate a longer freshness lifetime than caches they cannot reach.
2022 Aug
RFC 9293 replaced RFC 793 as the current TCP specification while retaining the protocol's core byte-stream service.
2022 Oct
Wireshark 4.0 redesigned Conversation and Endpoint dialogs and changed the default main-window layout. It also expanded display-filter syntax.
2022 Nov
Best Current Practice replacing RFC 7525, mandating TLS 1.2 as the minimum and providing cipher suite guidance that reflects the post-TLS 1.3 landscape. Deprecated TLS 1.0 and 1.1 for all new deployments.
2022 Dec
Juniper's lifecycle table records December 2022 as the first-release date for Junos OS Evolved 22.4. Lifecycle dates became an additional operational input for selecting a supported release.
2023
ETSI started Release 6 as the Telco Cloud Architecture direction. It frames applications, infrastructure, platform services, and orchestration as one evolving architecture.
2023 Feb
As IBM acquires NS1, NetBox Labs becomes an independent company and commercial steward for NetBox Cloud and the open source project.
2023 Mar
The Wireshark Foundation became the nonprofit organization operating project infrastructure, hosting Sharkfest, and promoting low-level network education. Project stewardship moved into the foundation structure.
2023 Apr
Remote data sources and configuration template rendering land, tightening the path from NetBox data to rendered device config fragments without turning NetBox into a full config manager.
2023 Oct
Gateway, GatewayClass and HTTPRoute graduated to v1, establishing a stable role-oriented routing API.
2024 Feb
CSF 2.0 expanded the framework's intended audience and added the Govern function. Network security planning gained a clearer link between technical controls, enterprise risk decisions, and supply-chain context.
2024 May
Gateway API v1.1 added stable GRPCRoute and service-mesh support, extending the portable route model beyond the initial v1 resources.
2024 May
Version 4.0 replaces the legacy admin-centric experience, updates the GraphQL engine, and raises the bar for plugin compatibility.
2025 Aug
RFC 9915 replaces RFC 8415 and publishes DHCPv6 as an Internet Standard. It is the current base specification for DHCPv6 behavior.