draft-ietf-idr-add-paths-02.txt   draft-ietf-idr-add-paths-03.txt 
Network Working Group D. Walton Network Working Group D. Walton
Internet Draft A. Retana Internet Draft A. Retana
Intended Status: Standards Track E. Chen Intended Status: Standards Track E. Chen
Expiration Date: February 2010 Cisco Systems Expiration Date: August 2010 Cisco Systems
J. Scudder J. Scudder
Juniper Networks Juniper Networks
August 3, 2009 February 6, 2010
Advertisement of Multiple Paths in BGP Advertisement of Multiple Paths in BGP
draft-ietf-idr-add-paths-02.txt draft-ietf-idr-add-paths-03.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on February 4, 2010. This Internet-Draft will expire on August 6, 2010.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Abstract Abstract
In this document we propose a BGP extension that allows the In this document we propose a BGP extension that allows the
advertisement of multiple paths for the same address prefix without advertisement of multiple paths for the same address prefix without
the new paths implicitly replacing any previous ones. The essence of the new paths implicitly replacing any previous ones. The essence of
the extension is that each path is identified by a path identifier in the extension is that each path is identified by a path identifier in
addition to the address prefix. addition to the address prefix.
1. Introduction 1. Introduction
skipping to change at page 6, line 7 skipping to change at page 6, line 24
7. Deployment Considerations 7. Deployment Considerations
The extension proposed in this document provides a mechanism for a The extension proposed in this document provides a mechanism for a
BGP speaker to advertise multiple paths over a BGP session. Care BGP speaker to advertise multiple paths over a BGP session. Care
needs to be taken in its deployment to ensure consistent routing and needs to be taken in its deployment to ensure consistent routing and
forwarding in a network, the details of which will be described in forwarding in a network, the details of which will be described in
separate application documents. separate application documents.
8. IANA Considerations 8. IANA Considerations
IANA has assigned capability number <TBD> for the ADD-PATH Capability IANA has assigned capability number 69 for the ADD-PATH Capability
described in this document. This registration is in the BGP described in this document. This registration is in the BGP
Capability Codes registry. Capability Codes registry.
9. Security Considerations 9. Security Considerations
This document introduces no new security concerns to BGP or other This document introduces no new security concerns to BGP or other
specifications referenced in this document. specifications referenced in this document.
10. Acknowledgments 10. Acknowledgments
skipping to change at page 8, line 4 skipping to change at line 301
Cisco Systems, Inc. Cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Email: enkechen@cisco.com Email: enkechen@cisco.com
John Scudder John Scudder
Juniper Networks Juniper Networks
Email: jgs@juniper.net Email: jgs@juniper.net
13. Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
 End of changes. 6 change blocks. 
5 lines changed or deleted 20 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/