idnits 2.17.1 draft-ietf-manet-olsrv2-rmpr-optimization-00.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 : ---------------------------------------------------------------------------- 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 (September 19, 2013) is 3871 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: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Mobile Ad hoc Networking (MANET) C. Dearlove 3 Internet-Draft BAE Systems ATC 4 Updates: OLSRv2 (if approved) T. Clausen 5 Intended status: Standards Track LIX, Ecole Polytechnique 6 Expires: March 23, 2014 September 19, 2013 8 Routing MPR Optimization for the Optimized Link State Routing Protocol 9 version 2 (OLSRv2) 10 draft-ietf-manet-olsrv2-rmpr-optimization-00 12 Abstract 14 This specification updates the Optimized Link State Routing Protocol 15 version 2 (OLSRv2) with an optimization to improve the selection of 16 routing MPRs. The optimization retains full interoperability between 17 implementations of OLSRv2 with and without this optimization. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on March 23, 2014. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Applicability Statement . . . . . . . . . . . . . . . . . . . . 3 56 4. Routing MPR Selection . . . . . . . . . . . . . . . . . . . . . 4 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 58 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 59 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 60 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 62 8.2. Informative References . . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 65 1. Introduction 67 The Optimized Link State Routing Protocol, version 2 [OLSRv2] is a 68 proactive link state routing protocol designed for use in mobile ad 69 hoc networks (MANETs) [RFC2501]. This document improves one area of 70 that specification. 72 One improvement included in OLSRv2, compared to its predecessor 73 described in [RFC3626], is the use of link metrics, rather than 74 minimum hop routing. A rationale for how link metrics were included 75 in OLSRv2 is documented in [RFC6966-to-be]. However, one aspect of 76 the use of link metrics described in [RFC6966-to-be], the removal of 77 some unnecessarily selected routing MPRs, was not included in 78 [OLSRv2]. This specification updates OLSRv2 to include this 79 optimization. 81 Note that an implementation using this optimization is not strictly 82 compliant with the current specification [OLSRv2], but is fully 83 interoperable with implementations not using this optimization. This 84 specification updates [OLSRv2] to specify that an implementation 85 using this optimization is compliant with the protocol OLSRv2. 87 2. Terminology 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 91 "OPTIONAL" in this document are to be interpreted as described in 92 [RFC2119]. 94 Additionally, this document uses the terminology of [OLSRv2]. 96 3. Applicability Statement 98 This specification updates [OLSRv2]. As such it is applicable to all 99 implementations of this protocol. The optimization presented in this 100 specification is simply permissive, it allows an additional 101 optimization, and there is no requirement for any implementation to 102 include it. However inclusion of this optimization is advised, it 103 can, in some cases, create smaller and fewer messages, without ever 104 having the opposite effect. 106 [OLSRv2] defines the properties for the selection of routing MPRs 107 (multipoint relays) from among a router's symmetric 1-hop neighbors 108 as properties that correspond first to that the selected MPRs consist 109 of a set of symmetric 1-hop neighbors that cover all the symmetric 110 2-hop neighbors, and second that they do so retaining a minimum 111 distance route (1-hop, if present, or 2-hop) to each symmetric 2-hop 112 neighbor. The discussion in the latter part of Section 6.2 of 113 [RFC6966-to-be] indicates that this requirement is over-prescriptive 114 for routing MPR selection. The update to [OLSRv2] described in this 115 specification permits a router to use the described optimization, 116 while still being considered compliant. 118 Note that, whether considered compliant or not, a router that 119 implements the optimization, described in this specification, will 120 interoperate successfully with routers not implementing this 121 optimization. 123 4. Routing MPR Selection 125 A set of routing MPRs created as specified in [OLSRv2] MAY be 126 optimized in the following manner. Note that this uses the notation 127 of Section 18.3 of [OLSRv2]: 129 1. If there is a sequence x_0, ..., x_n of elements of N1 such that: 131 * x_0 is a routing MPR, 133 * x_1, ... , x_n have corresponding elements y_1, ..., y_n of 134 N2, and 136 * d1(x_0) + d2(x_0,y_1) + ... + d2(x_m-1,y_m) < d1(x_m) for m = 137 1, ... , n, 139 then x_1 to x_n may be removed from the set of routing MPRs, if 140 selected. 142 Note that "corresponding elements" in N1 and N2 means that these 143 elements represent the same router. All of this information is 144 available from information gathered by NHDP [RFC6130]. 146 It is RECOMMENDED that all OLSRv2 routers use this optimization. 148 5. IANA Considerations 150 This document has no actions for IANA. 152 [This section may be removed by the RFC Editor.] 154 6. Security Considerations 156 The update to [OLSRv2] does not introduce any new protocol signals, 157 compared to the already published specifications of the protocol, nor 158 does it change the processing of any received protocol signals. 160 This update to [OLSRv2] permits a compliant implementation of OLSRv2 161 to (potentially) eliminate some redundant information from the 162 routing MPR sets otherwise generated by the algorithms described in 163 [OLSRv2], and therefore also eliminate the need for including that 164 information in generated TC messages. Because this information is 165 not used when included, this update to [OLSRv2] does not present any 166 additional security considerations, beyond those described in 167 [OLSRv2]. 169 7. Acknowledgments 171 The authors would like to gratefully acknowledge Philippe Jacquet 172 (Alcatel-Lucent) for intense technical discussions and comments. 174 8. References 176 8.1. Normative References 178 [OLSRv2] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg, 179 "The Optimized Link State Routing Protocol version 2", 180 work in progress draft-ietf-manet-olsrv2-19, March 2013. 182 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 183 Requirement Levels", BCP 14, RFC 2119, March 1997. 185 [RFC6130] Clausen, T., Dean, J., and C. Dearlove, "Mobile Ad Hoc 186 Network (MANET) Neighborhood Discovery Protocol (NHDP)", 187 RFC 6130, April 2011. 189 8.2. Informative References 191 [RFC2501] Macker, J. and S. Corson, "Mobile Ad hoc Networking 192 (MANET): Routing Protocol Performance Issues and 193 Evaluation Considerations", RFC 2501, January 1999. 195 [RFC3626] Clausen, T. and P. Jacquet, "The Optimized Link State 196 Routing Protocol", RFC 3626, October 2003. 198 [RFC6966-to-be] 199 Clausen, T., Dearlove, C., and P. Jacquet, "Rationale for 200 the Use of Link Metrics in the Optimized Link State 201 Routing Protocol Version 2 (OLSRv2)", RFC 6966, TBD 2013. 203 Authors' Addresses 205 Christopher Dearlove 206 BAE Systems Advanced Technology Centre 207 West Hanningfield Road 208 Great Baddow, Chelmsford 209 United Kingdom 211 Phone: +44 1245 242194 212 Email: chris.dearlove@baesystems.com 213 URI: http://www.baesystems.com/ 215 Thomas Heide Clausen 216 LIX, Ecole Polytechnique 218 Phone: +33 6 6058 9349 219 Email: T.Clausen@computer.org 220 URI: http://www.ThomasClausen.org/