Generated by GPT-5-mini| IETF Routing Area | |
|---|---|
| Name | IETF Routing Area |
| Formation | 1990s |
| Parent organization | Internet Engineering Task Force |
| Focus | Internet routing protocols and architecture |
| Location | Global |
IETF Routing Area The IETF Routing Area coordinates development of Internet routing protocols, architectures, and operational practices across multiple RFCs, IETF Working Groups, and standards bodies. It interacts with organizations such as the Internet Engineering Task Force, Internet Research Task Force, Internet Architecture Board, IAB and collaborates with regional registries and operators including ARIN, RIPE NCC, APNIC, LACNIC, and AFRINIC. Through working groups and meetings, the Routing Area influences protocols deployed by vendors like Cisco Systems, Juniper Networks, Huawei, Nokia, and Arista Networks and is cited in research from institutions such as MIT, Stanford University, University of California, Berkeley, Carnegie Mellon University, and ETH Zurich.
The Routing Area addresses protocol design, routing architectures, and protocol interactions with layers defined by RFC 1122 and RFC 791 foundations, while liaising with standards bodies such as the IETF Transport Area, IETF Security Area, IETF Operations and Management Area, and the IETF Applications Area. Major protocols under its remit include Border Gateway Protocol, Open Shortest Path First, Intermediate System to Intermediate System, IS-IS, and link-state and distance-vector families informed by theoretical work from Leonard Kleinrock and Paul Baran. The Area draws on operational data from measurement projects like CAIDA, RIPE Atlas, and research labs including Bell Labs and AT&T Labs Research.
The Area is organized into multiple working groups overseen historically by Area Directors who coordinate with the Internet Engineering Steering Group, IESG, and other ADs such as those for the Internet Area and Transport Area. Notable working groups include those for BGP extensions, L3VPN technologies, Segment Routing, MPLS, SRv6, RPKI integration, BFD, and LDP. Working groups often collaborate with external bodies including IEEE 802.1, MEF, 3GPP, ETSI, IANA, IETF Program Area Directors, and network operator groups like NOGs and Nanog. Chairs and contributors have included engineers from Google, Facebook, Amazon Web Services, Microsoft, Verizon, AT&T, Comcast, Telefonica, and research contributors from University of Cambridge and Princeton University.
The Routing Area processes standards through RFC publication tracks including Proposed Standards, Draft Standards, and Best Current Practice. Key specifications include extensions to BGP-4, BGPsec, BGP-LS, Multiprotocol BGP, and IGP enhancements for OSPF and IS-IS. Protocol suites such as MPLS, MP-BGP, VPN technologies like L2VPN and EVPN, and newer paradigms like Segment Routing and SR-MPLS are standardized here. Security and routing provenance efforts reference artifacts like RPKI, ROAs, Resource Public Key Infrastructure practices, and converge with work by IETF SDOs and certification authorities such as Let's Encrypt and regional registries including ARIN.
The Area coordinates agendas for plenary sessions at IETF meetings held in cities such as Prague, Berlin, Vancouver, Singapore, Istanbul, and San Francisco. Decisions follow IETF processes involving rough consensus and running code, with shepherding from document editors and review by the IESG and the RFC Editor. Mailing lists, Git repositories, and tools like Datatracker and GitHub host drafts, while collaboration uses platforms established by IETF Secretariat and event support from organizations like ISOC. Interactions include BOFs, working group sessions, and interoperability events such as IETF Hackathons and operator-led testbeds.
Routing Area work emphasizes resilience against route leaks, prefix hijacking, and stability under route churn; mitigations include BGP Route Reflection best practices, RPKI deployment, BGPsec proposals, router configuration guides from vendors such as Cisco Systems and Juniper Networks, and operator frameworks from RFC 7454. Operational research draws on datasets from RouteViews, RIPE NCC, and measurement initiatives like CAIDA and RIPE Atlas. Coordination with bodies such as FIRST, CERT/CC, ENISA, and national Computer Emergency Response Teams helps translate protocol standards into operational guidelines used by carriers like Deutsche Telekom, BT Group, NTT Communications, and cloud providers including Google Cloud Platform and Amazon Web Services.
Routing Area evolution traces to early work on the ARPANET and early internetworking research at RAND Corporation and DARPA, through seminal protocols like Interior Gateway Protocols and the emergence of BGP in the 1980s. Milestones include the split of BGP-3 to BGP-4, adoption of CIDR following work by Vint Cerf and Jon Postel, the development of MPLS at IETF MPLS Working Group and Bell Labs, the creation of RPKI and route origin validation after high-profile incidents involving operators such as Vodafone and AT&T, and more recent advances in Segment Routing championed by vendors and operators across Internet2 and research networks like GEANT and CANARIE. The Area’s ongoing agenda reflects inputs from industry events such as Interop, RIPE Meetings, and academic conferences like SIGCOMM and USENIX.
Category:Internet Standards