draft-ietf-mpls-bgp-mpls-restart-01.txt   draft-ietf-mpls-bgp-mpls-restart-02.txt 
Network Working Group Yakov Rekhter (Juniper Networks) Network Working Group Yakov Rekhter (Juniper Networks)
Internet Draft Rahul Aggarwal (Redback Networks) Internet Draft Rahul Aggarwal (Redback Networks)
Expiration Date: March 2003 Expiration Date: April 2003
Graceful Restart Mechanism for BGP with MPLS Graceful Restart Mechanism for BGP with MPLS
draft-ietf-mpls-bgp-mpls-restart-01.txt draft-ietf-mpls-bgp-mpls-restart-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line 30 skipping to change at page 2, line 30
restart. restart.
Specification of Requirements Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Summary for Sub-IP Area Summary for Sub-IP Area
Summary (This section to be removed before publication.)
0.1 Summary
This document describes a mechanism that helps to minimize the This document describes a mechanism that helps to minimize the
negative effects on MPLS forwarding caused by LSR's control plane negative effects on MPLS forwarding caused by LSR's control plane
restart, and specifically by the restart of its BGP component in the restart, and specifically by the restart of its BGP component in the
case where BGP is used to carry MPLS labels and LSR is capable of case where BGP is used to carry MPLS labels and LSR is capable of
preserving its MPLS forwarding state across the restart. preserving its MPLS forwarding state across the restart.
Related documents 0.2 Related documents
See the Reference Section See the Reference Section
Where does it fit in the Picture of the Sub-IP Work 0.3 Where does it fit in the Picture of the Sub-IP Work
This work fits squarely in MPLS box. This work fits squarely in MPLS box.
Why is it Targeted at this WG 0.4 Why is it Targeted at this WG
The specifications on carrying MPLS Labels in BGP is a product of the The specifications on carrying MPLS Labels in BGP is a product of the
MPLS WG. This document specifies procedures to minimize the negative MPLS WG. This document specifies procedures to minimize the negative
effects on MPLS forwarding caused by the restart of the control plane effects on MPLS forwarding caused by the restart of the control plane
BGP module in the case where BGP is used to carry MPLS labels. Since BGP module in the case where BGP is used to carry MPLS labels. Since
the procedures described in this document are directly related to the procedures described in this document are directly related to
MPLS forwarding and carrying MPLS labels in BGP, it would be logical MPLS forwarding and carrying MPLS labels in BGP, it would be logical
to target this document at the MPLS WG. to target this document at the MPLS WG.
Justification 0.5 Justification
The WG should consider this document, as it allows to minimize the The WG should consider this document, as it allows to minimize the
negative effects on MPLS forwarding caused by the restart of the negative effects on MPLS forwarding caused by the restart of the
control plane BGP module in the case where BGP is used to carry MPLS control plane BGP module in the case where BGP is used to carry MPLS
labels. labels.
1. Motivation 1. Motivation
For the sake of brevity in the context of this document by "MPLS For the sake of brevity in the context of this document by "MPLS
forwarding state" we mean either <incoming label -> (outgoing label, forwarding state" we mean either <incoming label -> (outgoing label,
skipping to change at page 9, line 9 skipping to change at page 9, line 9
However, the downstream LSR may declare the session as failed before However, the downstream LSR may declare the session as failed before
the expiration of its Restart Time. This increases the period during the expiration of its Restart Time. This increases the period during
which the downstream LSR might reallocate the label while the which the downstream LSR might reallocate the label while the
upstream LSR continues to transmit data using the old usage of the upstream LSR continues to transmit data using the old usage of the
label. To reduce this issue, this document requires that labels are label. To reduce this issue, this document requires that labels are
not re-used until for at least the Restart Time. not re-used until for at least the Restart Time.
8. Intellectual Property Considerations 8. Intellectual Property Considerations
Juniper Networks, Inc. is seeking patent protection on some or all of This section is taken from Section 10.4 of [RFC2026].
the technology described in this Internet-Draft. If technology in
this document is adopted as a standard, Juniper Networks agrees to
license, on reasonable and non-discriminatory terms, any patent
rights it obtains covering such technology to the extent necessary to
comply with the standard.
Redback Networks, Inc. is seeking patent protection on some of the The IETF takes no position regarding the validity or scope of any
technology described in this Internet-Draft. If technology in this intellectual property or other rights that might be claimed to
document is adopted as a standard, Redback Networks agrees to pertain to the implementation or use of the technology described in
license, on reasonable and non-discriminatory terms, any patent this document or the extent to which any license under such rights
rights it obtains covering such technology to the extent necessary to might or might not be available; neither does it represent that it
comply with the standard. has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
9. Acknowledgments The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
9. Copyright Notice
Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
10. Acknowledgments
We would like to thank Chaitanya Kodeboyina and Loa Andersson for We would like to thank Chaitanya Kodeboyina and Loa Andersson for
their review and comments. The approach described in Section their review and comments. The approach described in Section
"Alternative procedures for the restarting LSR" is based on the idea "Alternative procedures for the restarting LSR" is based on the idea
suggested by Manoj Leelanivas. suggested by Manoj Leelanivas.
10. Normative References 11. Normative References
[1] "Graceful Restart Mechanism for BGP", draft-ietf-idr- [1] "Graceful Restart Mechanism for BGP", draft-ietf-idr-
restart-01.txt restart-01.txt
[2] Rekhter, Y., Rosen, E., "Carrying Label Information in BGP-4", [2] Rekhter, Y., Rosen, E., "Carrying Label Information in BGP-4",
RFC3107 RFC3107
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119 Requirement Levels", BCP 14, RFC 2119
[RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5 [RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5
Signature Option", RFC2385 Signature Option", RFC2385
11. Author Information [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", RFC2026
12. Author Information
Yakov Rekhter Yakov Rekhter
Juniper Networks Juniper Networks
1194 N.Mathilda Ave 1194 N.Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
e-mail: yakov@juniper.net e-mail: yakov@juniper.net
Rahul Aggarwal Rahul Aggarwal
Redback Networks Redback Networks
350 Holger Way 350 Holger Way
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/