IETF-93 Proceedings
Introduction | Area, Working Goup & BoF Reports | Plenaries | Training | Internet Research Task Force
Inter-Domain Routing (idr) (WG)
Additional information is available at tools.ietf.org/wg/idr
Chair(s):
Routing Area Area Director(s):
Assigned Area Director
Technical Advisor(s)
|
Recordings:
Meeting Slides:
Blue Sheets:
Internet-Drafts:
Request for Comments:
- Subcodes for BGP Finite State Machine Error (RFC 6608) (8612 bytes)
updates RFC4271
- BGP Support for Four-Octet Autonomous System (AS) Number Space (RFC 6793) (26366 bytes)
obsoletes rfc4893 updates RFC4271
- Application of the Border Gateway Protocol in the Internet (RFC 1164) (54988 bytes)
obsoleted by RFC 1268
- Border Gateway Protocol (BGP) (RFC 1163) (67778 bytes)
obsoleted by RFC 1267
obsoletes rfc1105
- Definitions of Managed Objects for the Border Gateway Protocol: Version 3 (RFC 1269) (25717 bytes)
obsoleted by RFC 4273
- Border Gateway Protocol 3 (BGP-3) (RFC 1267) (80724 bytes)
obsoletes rfc1163
- Experience with the BGP Protocol (RFC 1266) (21938 bytes)
- BGP Protocol Analysis (RFC 1265) (20728 bytes)
- Application of the Border Gateway Protocol in the Internet (RFC 1268) (31102 bytes)
obsoleted by RFC 1655
obsoletes rfc1164
- BGP OSPF Interaction (RFC 1364) (32121 bytes)
obsoleted by RFC 1403
- Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol (RFC 1397) (4124 bytes)
- A Border Gateway Protocol 4 (BGP-4) (RFC 1654) (130118 bytes)
obsoleted by RFC 1771
- Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 (RFC 1657) (45504 bytes)
obsoleted by RFC 4273
- Application of the Border Gateway Protocol in the Internet (RFC 1655) (43664 bytes)
obsoleted by RFC 1772
obsoletes rfc1268
- BGP-4 Protocol Document Roadmap and Implementation Experience (RFC 1656) (7705 bytes)
obsoleted by RFC 1773
- BGP4/IDRP for IP---OSPF Interaction (RFC 1745) (43675 bytes)
- Experience with the BGP-4 protocol (RFC 1773) (19936 bytes)
obsoletes rfc1656
- A BGP/IDRP Route Server alternative to a full mesh routing (RFC 1863) (37426 bytes)
obsoleted by RFC 4223
- Guidelines for creation, selection, and registration of an Autonomous System (AS) (RFC 1930) (22073 bytes)
updated by RFC 6996,RFC 7300
- BGP Route Reflection An alternative to full mesh IBGP (RFC 1966) (14320 bytes)
obsoleted by RFC 4456
updated by RFC 2796
- Autonomous System Confederations for BGP (RFC 1965) (13575 bytes)
obsoleted by RFC 3065
- An Application of the BGP Community Attribute in Multi-home Routing (RFC 1998) (16953 bytes)
- Using a Dedicated AS for Sites Homed to a Single Provider (RFC 2270) (12063 bytes)
- Multiprotocol Extensions for BGP-4 (RFC 2283) (18946 bytes)
obsoleted by RFC 2858
- A Framework for Inter-Domain Route Aggregation (RFC 2519) (25394 bytes)
- Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing (RFC 2545) (10209 bytes)
- BGP Route Reflection - An Alternative to Full Mesh IBGP (RFC 2796) (20174 bytes)
obsoleted by RFC 4456
updates RFC1966
- Capabilities Advertisement with BGP-4 (RFC 2842) (8366 bytes)
obsoleted by RFC 3392
- Multiprotocol Extensions for BGP-4 (RFC 2858) (23305 bytes)
obsoleted by RFC 4760
obsoletes rfc2283
- Route Refresh Capability for BGP-4 (RFC 2918) (7354 bytes)
updated by RFC 7313
- Autonomous System Confederations for BGP (RFC 3065) (20529 bytes)
obsoleted by RFC 5065
obsoletes rfc1965
- Capabilities Advertisement with BGP-4 (RFC 3392) (9885 bytes)
obsoleted by RFC 5492
obsoletes rfc2842
- Key Management Considerations for the TCP MD5 Signature Option (RFC 3562) (14965 bytes)
- Reclassification of RFC 1863 to Historic (RFC 4223) (5123 bytes)
obsoletes rfc1863
- A Border Gateway Protocol 4 (BGP-4) (RFC 4271) (222702 bytes)
obsoletes rfc1771 updated by RFC 6286,RFC 6608,RFC 6793,RFC 7607,RFC 7606
- BGP-4 Protocol Analysis (RFC 4274) (38200 bytes)
- BGP Security Vulnerabilities Analysis (RFC 4272) (53119 bytes)
- Experience with the BGP-4 Protocol (RFC 4277) (45117 bytes)
- BGP-4 MIB Implementation Survey (RFC 4275) (77598 bytes)
- BGP-4 Implementation Report (RFC 4276) (132864 bytes)
- BGP Extended Communities Attribute (RFC 4360) (24145 bytes)
updated by RFC 7153,RFC 7606
- Subcodes for BGP Cease Notification Message (RFC 4486) (10254 bytes)
- Multiprotocol Extensions for BGP-4 (RFC 4760) (24542 bytes)
obsoletes rfc2858 updated by RFC 7606
- Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE) (RFC 4798) (31381 bytes)
- BGP Support for Four-octet AS Number Space (RFC 4893) (21520 bytes)
obsoleted by RFC 6793
- Avoid BGP Best Path Transitions from One External to Another (RFC 5004) (11437 bytes)
- Autonomous System Confederations for BGP (RFC 5065) (28732 bytes)
obsoletes rfc3065
- Outbound Route Filtering Capability for BGP-4 (RFC 5291) (23949 bytes)
- Address-Prefix-Based Outbound Route Filter for BGP-4 (RFC 5292) (10429 bytes)
- Textual Representation of Autonomous System (AS) Numbers (RFC 5396) (5373 bytes)
- Autonomous System (AS) Number Reservation for Documentation Use (RFC 5398) (5433 bytes)
- Autonomous-System-Wide Unique BGP Identifier for BGP-4 (RFC 6286) (7497 bytes)
updates RFC4271
- Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP (RFC 6472) (10673 bytes)
- Dissemination of Flow Specification Rules (RFC 5575) (46473 bytes)
- Deprecation of BGP Path Attributes: DPA, ADVERTISER, and RCID_PATH / CLUSTER_ID (RFC 6938) (3875 bytes)
- BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) (RFC 4456) (23209 bytes)
obsoletes rfc1966 obsoletes rfc2796 updated by RFC 7606
- Definitions of Managed Objects for BGP-4 (RFC 4273) (65629 bytes)
obsoletes rfc1269 obsoletes rfc1657
- Autonomous System (AS) Reservation for Private Use (RFC 6996) (8198 bytes)
updates RFC1930
- BGP-4 Protocol Analysis (RFC 1774) (23823 bytes)
- Capabilities Advertisement with BGP-4 (RFC 5492) (13581 bytes)
obsoletes rfc3392
- BGP Communities Attribute (RFC 1997) (8275 bytes)
updated by RFC 7606
- IANA Registries for BGP Extended Communities (RFC 7153) (30557 bytes)
updates RFC5701,RFC4360
- BGP Route Flap Damping (RFC 2439) (86402 bytes)
- Making Route Flap Damping Usable (RFC 7196) (15202 bytes)
- Reservation of Last Autonomous System (AS) Numbers (RFC 7300) (7952 bytes)
updates RFC1930
- Enhanced Route Refresh Capability for BGP-4 (RFC 7313) (15111 bytes)
updates RFC2918
- The Accumulated IGP Metric Attribute for BGP (RFC 7311) (32615 bytes)
- Graceful Restart Mechanism for BGP (RFC 4724) (32343 bytes)
- Protection of BGP Sessions via the TCP MD5 Signature Option (RFC 2385) (12315 bytes)
obsoleted by RFC 5925
updated by RFC 6691
- Border Gateway Protocol (BGP) Persistent Route Oscillation Condition (RFC 3345) (38137 bytes)
- Revised Error Handling for BGP UPDATE Messages (RFC 7606) (42141 bytes)
updates RFC1997,RFC4271,RFC4360,RFC4456,RFC4760,RFC5543,RFC5701,RFC6368
- Codification of AS 0 Processing (RFC 7607) (9113 bytes)
updates RFC4271
Charter (as of 1994-08-15):
The Inter-Domain Routing Working Group is chartered to standardize,
develop, and support the Border Gateway Protocol Version 4 (BGP-4)
[RFC 4271] capable of supporting policy based routing for TCP/IP
internets.
The main objective of the working group is to support the use of
BGP-4 by IP version 4 and IP version 6 networks. The working group
will also continue to work on improving the robustness and
scalability of BGP.
IDR will review extensions made to BGP in other working groups at least
at WG document adoption and during working group last calls. The IDR
working group will also provide advice and guidance on BGP to other
working groups as requested.
Work Items:
The IDR working group will work on correctness, robustness and
scalability of the BGP protocol, as well as clarity and accuracy of the
BGP document set. The group will also work on extensions beyond these
areas when specifically added to the charter. The current additional
work items are:
- Relax the definition of BGP identifiers to only require AS-wide
uniqueness. This change must be made in a backward compatible way.
- Specify a means to non-disruptively introduce new BGP Capabilities
to an existing BGP session.
- Upgrade of the base BGP specification to Full Standard
- Define AS_PATH based Outbound Route Filtering.
- MIB v2 for BGP-4
- Augment the BGP multiprotocol extensions to support the use of
multiple concurrent sessions between a given pair of BGP speakers.
Each session is used to transport routes related by some session-
based attribute such as AFI/SAFI. This will provide an alternative
to the MP-BGP approach of multiplexing all routes onto a single
connection.
- Support for four-octet AS Numbers in BGP.
- Revisions to the BGP 'Minimum Route Advertisement Interval'
deprecating the previously recommended values and allowing for
withdrawals to be exempted from the MRAI.
- Advertisement of multiple paths for the same address prefix without
the new paths implicitly replacing any previous ones. Each path is
identified by a path identifier in addition to the address prefix.
- Revised error handling rules for optional transitive BGP attributes
so that a BGP speaker is no longer required to reset the session
over which a malformed attribute is received. Provide guidelines
for authors of documents that define new optional transitive
attributes, and re-assess procedures for existing optional
transitive attributes
- Specify Link Bandwidth Extended Community for use in unequal cost
load balancing.
- The definition of an "Accumulated IGP Metric" attribute for BGP
to report the sum of the metric of each link along the path.
This attribute is for use in a restricted environment where:
- all ASes are subject to the administrative control
- some form of tunneling is used to deliver a packet to its next
BGP hop
- where the path for a route leads outside the AS to which the
BGP speaker adding the attribute belongs.
- Advertisement of the best external route in BGP to assist with
resolution of the next hop in the chosen data plane.