TOC 
Inter-Domain RoutingP. Jakma
Internet-DraftSun Microsystems
Expires: June 18, 2009December 15, 2008


Revisions to the BGP 'Minimum Route Advertisement Interval'
draft-ietf-idr-mrai-dep-00

Status of this Memo

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware 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 Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on June 18, 2009.

Abstract

This document revises the specification of the BGP MRAI timer, by deprecating the previously recommended values and by allowing for withdrawals to be exempted from the MRAI.



Table of Contents

1.  Requirements Language
2.  Background
3.  Revision
4.  IANA Considerations
5.  Security Considerations
6.  Normative References
§  Author's Address
§  Intellectual Property and Copyright Statements




 TOC 

1.  Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” February 2001.).



 TOC 

2.  Background

The Minimum Route Advertisement Interval (MRAI) timer is specified in RFC4271 (Rekhter, Y., Li, T., and S. Hares, “A Border Gateway Protocol 4 (BGP-4),” January 2006.) [BGP]. This timer acts to rate-limit updates, on a per-destination basis. [BGP] (Rekhter, Y., Li, T., and S. Hares, “A Border Gateway Protocol 4 (BGP-4),” January 2006.) suggests values of 30s and 5s for this interval for eBGP and iBGP respectively. The MRAI must also be applied to withdrawals according to RFC4271, a change from the earlier RFC1771.

The MRAI timer has a significant effect on the convergence of BGP, in terms of convergence time, the number of messages, amongst other metrics. The optimum value for this timer is hard to estimate, never mind calculate and will differ between networks, and probably even different subsets of the same network.



 TOC 

3.  Revision

The suggested default values for the MinRouteAdvertisementIntervalTimer given in RFC4271 (Rekhter, Y., Li, T., and S. Hares, “A Border Gateway Protocol 4 (BGP-4),” January 2006.) [BGP] are deprecated. Implementations SHOULD provide a means to allow operators to choose values appropriate to their requirements, on a per-peer and per-AFI/SAFI basis. Implementations MAY exempt withdrawals from the MRAI timer.



 TOC 

4.  IANA Considerations

There are no requests made to IANA in this document.



 TOC 

5.  Security Considerations

This document raises no new security considerations.



 TOC 

6. Normative References

[BGP] Rekhter, Y., Li, T., and S. Hares, “A Border Gateway Protocol 4 (BGP-4),” RFC 4271, January 2006.
[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” RFC 2119, BCP 14, February 2001.


 TOC 

Author's Address

  Paul Jakma
  Sun Microsystems
  Springfield
  Linlithgow, West Lothian EH49 7LR
  Scotland
Phone:  +44 1506 673150
Email:  paul.jakma@sun.com


 TOC 

Full Copyright Statement

Intellectual Property