draft-ietf-idr-mrai-dep-02.txt		draft-ietf-idr-mrai-dep-03.txt
	Inter-Domain Routing P. Jakma		Inter-Domain Routing P. Jakma
	Internet-Draft February 19, 2010		Internet-Draft DCS, Uni. of Glasgow
	Expires: August 23, 2010		Updates: rfc4271 October 12, 2010
			(if approved)
			Intended status: Standards Track
			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-02		draft-ietf-idr-mrai-dep-03
	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.
	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 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), its areas, and its working groups. Note that		Task Force (IETF). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		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."
	The list of current Internet-Drafts can be accessed at		This Internet-Draft will expire on April 15, 2011.
	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 August 23, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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
	described in the BSD License.		described in the Simplified BSD License.
	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
	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
	RFC4271 [BGP]. This timer acts to rate-limit updates, on a per-		[RFC4271]. This timer acts to rate-limit updates, on a per-
	destination basis. [BGP] 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
	MinRouteAdvertisementIntervalTimer given in RFC4271 [BGP] are		MinRouteAdvertisementIntervalTimer given in [RFC4271] are deprecated.
	deprecated. The appropriate choice of default values is left to the		The appropriate choice of default values is left to the discretion of
	discretion of implementors. Implementations SHOULD provide a means		implementors. Implementations SHOULD provide a means to allow
	to allow operators to choose values appropriate to their		operators to choose values appropriate to their requirements, on a
	requirements, on a per-peer and per-AFI/SAFI basis. Implementations		per-peer and per-AFI/SAFI basis. Implementations MAY exempt
	MAY exempt withdrawals from the MRAI timer.		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		[RFC1771] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4
	Protocol 4 (BGP-4)", RFC 4271, January 2006.		(BGP-4)", RFC 1771, March 1995.
	[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", 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
	2/1, 5 Moir St.		School of Computing Science, Uni. of Glasgow
	Glasgow G1 5AE		Sir Alwyn Williams Building
	Scotland		University of Glasgow
			Glasgow G12 8QQ
			UK
	Email: paul@jakma.org		Email: paulj@dcs.gla.ac.uk
End of changes. 13 change blocks.
	30 lines changed or deleted		32 lines changed or added
This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/