draft-ietf-idr-bgp-issues-02.txt   draft-ietf-idr-bgp-issues-03.txt 
IDR A. Lange IDR A. Lange
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Informational July 29, 2010 Intended status: Informational August 17, 2010
Expires: January 30, 2011 Expires: February 18, 2011
Issues in Revising BGP-4 Issues in Revising BGP-4 (RFC1771 to RFC4271)
draft-ietf-idr-bgp-issues-02 draft-ietf-idr-bgp-issues-03
Abstract Abstract
This document records the issues discussed and the consensus reached This document records the issues discussed and the consensus reached
in the Interdomain Routing (IDR) Working Group during its efforts to in the Interdomain Routing (IDR) Working Group during its efforts to
revise and bring up to date the base specification for the BGP-4 revise and bring up to date the base specification for the BGP-4
protocol. protocol as documented in RFC1771. The results of these efforts are
encoded in RFC4271.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 30, 2011. This Internet-Draft will expire on February 18, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 10 skipping to change at page 6, line 10
3.56. Clarify what is covered in the base document . . . . . . 169 3.56. Clarify what is covered in the base document . . . . . . 169
4. Security Considerations . . . . . . . . . . . . . . . . . . . 170 4. Security Considerations . . . . . . . . . . . . . . . . . . . 170
5. Normative References . . . . . . . . . . . . . . . . . . . . 170 5. Normative References . . . . . . . . . . . . . . . . . . . . 170
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 170 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 170
1. Introduction 1. Introduction
This document records the issues discussed and the consensus reached This document records the issues discussed and the consensus reached
in the Interdomain Routing (IDR) Working Group during its efforts to in the Interdomain Routing (IDR) Working Group during its efforts to
revise and bring up to date the base specification for the BGP-4 revise and bring up to date the base specification for the BGP-4
protocol. The rational for doing this is simple: Experience has protocol as documented in RFC1771. The results of these efforts are
demonstrated that the same issues and questions tend to come up again encoded in RFC4271. The rational for doing this is simple:
and again. This memo will document not only the decisions on these Experience has demonstrated that the same issues and questions tend
issues but also how and why the working group reached those to come up again and again. This memo will document not only the
conclusions. We hope that this will help make future discussions decisions on these issues but also how and why the working group
more fruitful by providing them with a historical context. reached those conclusions. We hope that this will help make future
discussions more fruitful by providing them with a historical
context.
This document traces the evolution of the BGP-4 base specification This document traces the evolution of the BGP-4 base specification
from its incarnation as draft-ietf-idr-bgp4-17.txt through the big from its incarnation as draft-ietf-idr-bgp4-17.txt through the big
revision and update push culminating in draft-ietf-idr-bgp4-19.txt. revision and update push culminating in draft-ietf-idr-bgp4-19.txt.
It is divided into two main sections. The first deals with the It is divided into two main sections. The first deals with the
issues discussed between -17 and -18, and the second deals with the issues discussed between -17 and -18, and the second deals with the
issues discussed between -18 and -19. issues discussed between -18 and -19.
N.B. There is no rhyme or reason to the numbering scheme other than N.B. There is no rhyme or reason to the numbering scheme other than
unique tags to address the issues. unique tags to address the issues.
skipping to change at page 170, line 32 skipping to change at page 170, line 32
5. Normative References 5. Normative References
[RFC1771] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 [RFC1771] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4
(BGP-4)", RFC 1771, March 1995. (BGP-4)", RFC 1771, March 1995.
Author's Address Author's Address
Andrew S. Lange Andrew S. Lange
Alcatel-Lucent Alcatel-Lucent
Email: andrew.lange at alcatel-lucent.com Email: andrew.lange@alcatel-lucent.com
 End of changes. 6 change blocks. 
12 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/