idnits 2.17.1 draft-ietf-idr-mrai-dep-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. 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 (July 28, 2009) is 5380 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 July 28, 2009 4 Expires: January 29, 2010 6 Revisions to the BGP 'Minimum Route Advertisement Interval' 7 draft-ietf-idr-mrai-dep-01 9 Status of this Memo 11 This Internet-Draft is submitted to IETF in full conformance with the 12 provisions of BCP 78 and BCP 79. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on January 29, 2010. 32 Copyright Notice 34 Copyright (c) 2009 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents in effect on the date of 39 publication of this document (http://trustee.ietf.org/license-info). 40 Please review these documents carefully, as they describe your rights 41 and restrictions with respect to this document. 43 Abstract 45 This document revises the specification of the BGP MRAI timer, by 46 deprecating the previously recommended values and by allowing for 47 withdrawals to be exempted from the MRAI. 49 Table of Contents 51 1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 52 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 3. Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 56 6. Normative References . . . . . . . . . . . . . . . . . . . . . 3 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 1. Requirements Language 61 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 62 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 63 document are to be interpreted as described in [RFC2119]. 65 2. Background 67 The Minimum Route Advertisement Interval (MRAI) timer is specified in 68 RFC4271 [BGP]. This timer acts to rate-limit updates, on a per- 69 destination basis. [BGP] suggests values of 30s and 5s for this 70 interval for eBGP and iBGP respectively. The MRAI must also be 71 applied to withdrawals according to RFC4271, a change from the 72 earlier RFC1771. 74 The MRAI timer has a significant effect on the convergence of BGP, in 75 terms of convergence time, the number of messages, amongst other 76 metrics. The optimum value for this timer is hard to estimate, never 77 mind calculate and will differ between networks, and probably even 78 different subsets of the same network. 80 3. Revision 82 The suggested default values for the 83 MinRouteAdvertisementIntervalTimer given in RFC4271 [BGP] are 84 deprecated. The appropriate choice of default values is left to the 85 discretion of implementors. Implementations SHOULD provide a means 86 to allow operators to choose values appropriate to their 87 requirements, on a per-peer and per-AFI/SAFI basis. Implementations 88 MAY exempt withdrawals from the MRAI timer. 90 4. IANA Considerations 92 There are no requests made to IANA in this document. 94 5. Security Considerations 96 This document raises no new security considerations. 98 6. Normative References 100 [BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 101 Protocol 4 (BGP-4)", RFC 4271, January 2006. 103 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 104 Requirement Levels", RFC 2119, BCP 14, February 2001. 106 Author's Address 108 Paul Jakma 109 2/1, 5 Moir St. 110 Glasgow G1 5AE 111 Scotland 113 Email: paul@jakma.org