idnits 2.17.1 draft-ietf-idr-mrai-dep-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 12, 2010) is 4944 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1771 (Obsoleted by RFC 4271) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing P. Jakma 3 Internet-Draft DCS, Uni. of Glasgow 4 Updates: rfc4271 October 12, 2010 5 (if approved) 6 Intended status: Standards Track 7 Expires: April 15, 2011 9 Revisions to the BGP 'Minimum Route Advertisement Interval' 10 draft-ietf-idr-mrai-dep-03 12 Abstract 14 This document revises the specification of the BGP MRAI timer, by 15 deprecating the previously recommended values and by allowing for 16 withdrawals to be exempted from the MRAI. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on April 15, 2011. 35 Copyright Notice 37 Copyright (c) 2010 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 53 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 56 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 57 6. Normative References . . . . . . . . . . . . . . . . . . . . . 3 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 1. Requirements Language 62 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 63 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 64 document are to be interpreted as described in [RFC2119]. 66 2. Background 68 The Minimum Route Advertisement Interval (MRAI) timer is specified in 69 [RFC4271]. This timer acts to rate-limit updates, on a per- 70 destination basis. [RFC4271] suggests values of 30s and 5s for this 71 interval for eBGP and iBGP respectively. The MRAI must also be 72 applied to withdrawals according to RFC4271, a change from the 73 earlier [RFC1771]. 75 The MRAI timer has a significant effect on the convergence of BGP, in 76 terms of convergence time, the number of messages, amongst other 77 metrics. The optimum value for this timer is hard to estimate, never 78 mind calculate and will differ between networks, and probably even 79 different subsets of the same network. 81 3. Revision 83 The suggested default values for the 84 MinRouteAdvertisementIntervalTimer given in [RFC4271] are deprecated. 85 The appropriate choice of default values is left to the discretion of 86 implementors. Implementations SHOULD provide a means to allow 87 operators to choose values appropriate to their requirements, on a 88 per-peer and per-AFI/SAFI basis. Implementations MAY exempt 89 withdrawals from the MRAI timer. 91 4. IANA Considerations 93 There are no requests made to IANA in this document. 95 5. Security Considerations 97 This document raises no new security considerations. 99 6. Normative References 101 [RFC1771] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 102 (BGP-4)", RFC 1771, March 1995. 104 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 105 Requirement Levels", BCP 14, RFC 2119, March 1997. 107 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 108 Protocol 4 (BGP-4)", RFC 4271, January 2006. 110 Author's Address 112 Paul Jakma 113 School of Computing Science, Uni. of Glasgow 114 Sir Alwyn Williams Building 115 University of Glasgow 116 Glasgow G12 8QQ 117 UK 119 Email: paulj@dcs.gla.ac.uk