draft-ietf-idr-mrai-dep-00.txt   draft-ietf-idr-mrai-dep-01.txt 
Inter-Domain Routing P. Jakma Inter-Domain Routing P. Jakma
Internet-Draft Sun Microsystems
Expires: June 18, 2009 December 15, 2008 Expires: January 29, 2010
Revisions to the BGP 'Minimum Route Advertisement Interval' Revisions to the BGP 'Minimum Route Advertisement Interval'
draft-ietf-idr-mrai-dep-00 draft-ietf-idr-mrai-dep-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of 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.
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 June 18, 2009. This Internet-Draft will expire on January 29, 2010.
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.
Abstract Abstract
This document revises the specification of the BGP MRAI timer, by This document revises the specification of the BGP MRAI timer, by
deprecating the previously recommended values and by allowing for deprecating the previously recommended values and by allowing for
withdrawals to be exempted from the MRAI. withdrawals to be exempted from the MRAI.
Table of Contents Table of Contents
1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
6. Normative References . . . . . . . . . . . . . . . . . . . . . 3 6. Normative References . . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4
Intellectual Property and Copyright Statements . . . . . . . . . . 5
1. Requirements Language 1. Requirements Language
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Background 2. Background
The Minimum Route Advertisement Interval (MRAI) timer is specified in The Minimum Route Advertisement Interval (MRAI) timer is specified in
skipping to change at page 3, line 30 skipping to change at page 3, line 30
The MRAI timer has a significant effect on the convergence of BGP, in The MRAI timer has a significant effect on the convergence of BGP, in
terms of convergence time, the number of messages, amongst other terms of convergence time, the number of messages, amongst other
metrics. The optimum value for this timer is hard to estimate, never metrics. The optimum value for this timer is hard to estimate, never
mind calculate and will differ between networks, and probably even mind calculate and will differ between networks, and probably even
different subsets of the same network. different subsets of the same network.
3. Revision 3. Revision
The suggested default values for the The suggested default values for the
MinRouteAdvertisementIntervalTimer given in RFC4271 [BGP] are MinRouteAdvertisementIntervalTimer given in RFC4271 [BGP] are
deprecated. Implementations SHOULD provide a means to allow deprecated. The appropriate choice of default values is left to the
operators to choose values appropriate to their requirements, on a discretion of implementors. Implementations SHOULD provide a means
per-peer and per-AFI/SAFI basis. Implementations MAY exempt to allow operators to choose values appropriate to their
withdrawals from the MRAI timer. requirements, on a per-peer and per-AFI/SAFI basis. Implementations
MAY exempt withdrawals from the MRAI timer.
4. IANA Considerations 4. IANA Considerations
There are no requests made to IANA in this document. There are no requests made to IANA in this document.
5. Security Considerations 5. Security Considerations
This document raises no new security considerations. This document raises no new security considerations.
6. Normative References 6. Normative References
[BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, February 2001. Requirement Levels", RFC 2119, BCP 14, February 2001.
Author's Address Author's Address
Paul Jakma Paul Jakma
Sun Microsystems 2/1, 5 Moir St.
Springfield Glasgow G1 5AE
Linlithgow, West Lothian EH49 7LR
Scotland Scotland
Phone: +44 1506 673150 Email: paul@jakma.org
Email: paul.jakma@sun.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 8 change blocks. 
16 lines changed or deleted 24 lines changed or added

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