| draft-ietf-idr-mrai-dep-03.txt | draft-ietf-idr-mrai-dep-04.txt | |||
|---|---|---|---|---|
| Inter-Domain Routing P. Jakma | Inter-Domain Routing P. Jakma | |||
| Internet-Draft DCS, Uni. of Glasgow | Internet-Draft School of Computing Science, | |||
| Updates: rfc4271 October 12, 2010 | Updates: 4271 (if approved) Uni. of Glasgow | |||
| (if approved) | Intended status: Standards Track September 20, 2011 | |||
| Intended status: Standards Track | Expires: March 23, 2012 | |||
| Expires: April 15, 2011 | ||||
| Revisions to the BGP 'Minimum Route Advertisement Interval' | Revisions to the BGP 'Minimum Route Advertisement Interval' | |||
| draft-ietf-idr-mrai-dep-03 | draft-ietf-idr-mrai-dep-04 | |||
| Abstract | Abstract | |||
| This document revises the specification of the BGP MRAI timer, by | This document updates the specification of the BGP MRAI timer in | |||
| deprecating the previously recommended values and by allowing for | [RFC4271], by deprecating the previously recommended values and by | |||
| withdrawals to be exempted from the MRAI. | allowing for withdrawals to be exempted from the MRAI. | |||
| 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 April 15, 2011. | This Internet-Draft will expire on March 23, 2012. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2010 IETF Trust and the persons identified as the | Copyright (c) 2011 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 | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 3, line 18 | skipping to change at page 3, line 18 | |||
| "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 | |||
| [RFC4271]. This timer acts to rate-limit updates, on a per- | [RFC4271]. This timer acts to rate-limit updates, on a per- | |||
| destination basis. [RFC4271] suggests values of 30s and 5s for this | destination basis. [RFC4271] suggests values of 30s and 5s for this | |||
| interval for eBGP and iBGP respectively. The MRAI must also be | interval for eBGP and iBGP respectively. The MRAI must also be | |||
| applied to withdrawals according to RFC4271, a change from the | applied to withdrawals according to RFC4271, a change from the | |||
| earlier [RFC1771]. | earlier RFC1771. | |||
| 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 | |||
| skipping to change at page 3, line 46 | skipping to change at page 3, line 46 | |||
| 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 | |||
| [RFC1771] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 | [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway | |||
| (BGP-4)", RFC 1771, March 1995. | 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", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway | ||||
| Protocol 4 (BGP-4)", RFC 4271, January 2006. | ||||
| Author's Address | Author's Address | |||
| Paul Jakma | Paul Jakma | |||
| School of Computing Science, Uni. of Glasgow | School of Computing Science, Uni. of Glasgow | |||
| Sir Alwyn Williams Building | Sir Alwyn Williams Building | |||
| University of Glasgow | ||||
| Glasgow G12 8QQ | Glasgow G12 8QQ | |||
| UK | Scotland | |||
| Email: paulj@dcs.gla.ac.uk | Email: paulj@dcs.gla.ac.uk | |||
| End of changes. 10 change blocks. | ||||
| 19 lines changed or deleted | 14 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||