idnits 2.17.1 draft-ietf-idr-mrai-dep-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 19, 2010) is 5179 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) No issues found here. 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 February 19, 2010 4 Expires: August 23, 2010 6 Revisions to the BGP 'Minimum Route Advertisement Interval' 7 draft-ietf-idr-mrai-dep-02 9 Abstract 11 This document revises the specification of the BGP MRAI timer, by 12 deprecating the previously recommended values and by allowing for 13 withdrawals to be exempted from the MRAI. 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on August 23, 2010. 38 Copyright Notice 40 Copyright (c) 2010 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the BSD License. 53 Table of Contents 55 1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 56 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 60 6. Normative References . . . . . . . . . . . . . . . . . . . . . 3 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Requirements Language 65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 67 document are to be interpreted as described in [RFC2119]. 69 2. Background 71 The Minimum Route Advertisement Interval (MRAI) timer is specified in 72 RFC4271 [BGP]. This timer acts to rate-limit updates, on a per- 73 destination basis. [BGP] suggests values of 30s and 5s for this 74 interval for eBGP and iBGP respectively. The MRAI must also be 75 applied to withdrawals according to RFC4271, a change from the 76 earlier RFC1771. 78 The MRAI timer has a significant effect on the convergence of BGP, in 79 terms of convergence time, the number of messages, amongst other 80 metrics. The optimum value for this timer is hard to estimate, never 81 mind calculate and will differ between networks, and probably even 82 different subsets of the same network. 84 3. Revision 86 The suggested default values for the 87 MinRouteAdvertisementIntervalTimer given in RFC4271 [BGP] are 88 deprecated. The appropriate choice of default values is left to the 89 discretion of implementors. Implementations SHOULD provide a means 90 to allow operators to choose values appropriate to their 91 requirements, on a per-peer and per-AFI/SAFI basis. Implementations 92 MAY exempt withdrawals from the MRAI timer. 94 4. IANA Considerations 96 There are no requests made to IANA in this document. 98 5. Security Considerations 100 This document raises no new security considerations. 102 6. Normative References 104 [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 105 Protocol 4 (BGP-4)", RFC 4271, January 2006. 107 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 108 Requirement Levels", RFC 2119, BCP 14, February 2001. 110 Author's Address 112 Paul Jakma 113 2/1, 5 Moir St. 114 Glasgow G1 5AE 115 Scotland 117 Email: paul@jakma.org