datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Issues in Revising BGP-4 (RFC1771 to RFC4271)
draft-ietf-idr-bgp-issues-06

Document type: Expired Internet-Draft (idr WG)
Document stream: IETF
Last updated: 2012-10-04 (latest revision 2012-03-27)
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: Submitted to IESG for Publication
Consensus: Unknown
Document shepherd: Susan Hares
Shepherd Write-Up: Last changed 2012-07-29

IESG State: Expired (IESG: Dead)
Responsible AD: Stewart Bryant
Send notices to: idr-chairs@tools.ietf.org, draft-ietf-idr-bgp-issues@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-idr-bgp-issues

Abstract

This document records the issues discussed and the consensus reached in the Interdomain Routing (IDR) Working Group during its efforts to revise and bring up to date the base specification for the BGP-4 protocol as documented in RFC1771. The document focuses on the changes tracked from August 2002 when the last major push for revision began. The results of these efforts are encoded in RFC4271, which should be taken as normative for any of the issues that were discussed. The discussion here is intended to record how and why some of the changes to BGP were made.

Authors

Andrew Lange <andrew.lange@alcatel-lucent.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)