draft-ietf-idr-bgp-multisession-04.txt   draft-ietf-idr-bgp-multisession-05.txt 
Internet Engineering Task Force J. Scudder Internet Engineering Task Force J. Scudder
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track C. Appanna Intended status: Standards Track C. Appanna
Expires: January 13, 2010 Cisco Systems Expires: September 24, 2010 Cisco Systems
July 12, 2009 March 23, 2010
Multisession BGP Multisession BGP
draft-ietf-idr-bgp-multisession-04 draft-ietf-idr-bgp-multisession-05
Abstract
This specification augments "Multiprotocol Extensions for BGP-4" (MP-
BGP) by proposing a mechanism to facilitate the use of multiple
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 provides an alternative to the MP-BGP approach of
multiplexing all routes onto a single connection.
Use of this approach is expected to provide finer-grained fault
management and isolation as the BGP protocol is used to support more
and more diverse services.
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. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
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.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
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 January 13, 2010. This Internet-Draft will expire on September 24, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This specification augments "Multiprotocol Extensions for BGP-4" (MP- described in the BSD License.
BGP) by proposing a mechanism to facilitate the use of multiple
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 provides an alternative to the MP-BGP approach of
multiplexing all routes onto a single connection.
Use of this approach is expected to provide finer-grained fault This document may contain material from IETF Documents or IETF
management and isolation as the BGP protocol is used to support more Contributions published or made publicly available before November
and more diverse services. 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 5 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Use of BGP Capability Advertisement . . . . . . . . . . . . . 6 3. Use of BGP Capability Advertisement . . . . . . . . . . . . . 5
4. New NOTIFICATION Subcodes . . . . . . . . . . . . . . . . . . 7 4. New NOTIFICATION Subcodes . . . . . . . . . . . . . . . . . . 6
5. Overview of Operation . . . . . . . . . . . . . . . . . . . . 8 5. Overview of Operation . . . . . . . . . . . . . . . . . . . . 7
5.1. Using Multisession . . . . . . . . . . . . . . . . . . . . 9 5.1. Using Multisession . . . . . . . . . . . . . . . . . . . . 8
5.1.1. Initiating Connections . . . . . . . . . . . . . . . . 9 5.1.1. Initiating Connections . . . . . . . . . . . . . . . . 8
5.1.1.1. Continuing a Redirected Connection . . . . . . . . 11 5.1.1.1. Continuing a Redirected Connection . . . . . . . . 10
5.1.2. Accepting Connections . . . . . . . . . . . . . . . . 11 5.1.2. Accepting Connections . . . . . . . . . . . . . . . . 10
5.1.3. Collision Detection, Graceful Restart . . . . . . . . 12 5.1.3. Collision Detection, Graceful Restart . . . . . . . . 11
6. Backward Compatibility . . . . . . . . . . . . . . . . . . . . 12 6. Backward Compatibility . . . . . . . . . . . . . . . . . . . . 11
7. State Machine . . . . . . . . . . . . . . . . . . . . . . . . 13 7. State Machine . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Modifications to Connect State and Active State . . . . . 13 7.1. Modifications to Connect State and Active State . . . . . 12
7.2. Addition of WaitForOpen State, Deletion of OpenSent 7.2. Addition of WaitForOpen State, Deletion of OpenSent
State . . . . . . . . . . . . . . . . . . . . . . . . . . 14 State . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. Security Considerations . . . . . . . . . . . . . . . . . . . 13
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
12.1. Normative References . . . . . . . . . . . . . . . . . . . 15 12.1. Normative References . . . . . . . . . . . . . . . . . . . 14
12.2. Informative References . . . . . . . . . . . . . . . . . . 16 12.2. Informative References . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Most BGP [RFC4271] implementations only permit a single ESTABLISHED Most BGP [RFC4271] implementations only permit a single ESTABLISHED
connection to exist with each peer. More precisely, they only permit connection to exist with each peer. More precisely, they only permit
a single ESTABLISHED connection for any given pair of IP endpoints. a single ESTABLISHED connection for any given pair of IP endpoints.
BGP Capabilities [RFC5492] extend BGP to allow diverse information BGP Capabilities [RFC5492] extend BGP to allow diverse information
(encoded as "capabilities") to be associated with a session. In some (encoded as "capabilities") to be associated with a session. In some
cases, a capability may relate to the operation of the protocol cases, a capability may relate to the operation of the protocol
skipping to change at page 16, line 9 skipping to change at page 16, line 9
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
January 2007. January 2007.
[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
with BGP-4", RFC 5492, February 2009. with BGP-4", RFC 5492, February 2009.
12.2. Informative References 12.2. Informative References
[I-D.ietf-idr-dynamic-cap] [I-D.ietf-idr-dynamic-cap]
Chen, E. and S. Sangli, "Dynamic Capability for BGP-4", Chen, E. and S. Ramachandra, "Dynamic Capability for
draft-ietf-idr-dynamic-cap-09 (work in progress), BGP-4", draft-ietf-idr-dynamic-cap-10 (work in progress),
November 2006. January 2010.
[RFC2918] Chen, E., "Route Refresh Capability for BGP-4", RFC 2918, [RFC2918] Chen, E., "Route Refresh Capability for BGP-4", RFC 2918,
September 2000. September 2000.
Authors' Addresses Authors' Addresses
John G. Scudder John G. Scudder
Juniper Networks Juniper Networks
Email: jgs@juniper.net Email: jgs@juniper.net
 End of changes. 10 change blocks. 
59 lines changed or deleted 64 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/