draft-ietf-manet-olsrv2-multipath-04.txt   draft-ietf-manet-olsrv2-multipath-05.txt 
Network Working Group J. Yi Network Working Group J. Yi
Internet-Draft LIX, Ecole Polytechnique Internet-Draft LIX, Ecole Polytechnique
Intended status: Experimental B. Parrein Intended status: Experimental B. Parrein
Expires: January 1, 2016 University of Nantes Expires: January 3, 2016 University of Nantes
June 30, 2015 July 2, 2015
Multi-path Extension for the Optimized Link State Routing Protocol Multi-path Extension for the Optimized Link State Routing Protocol
version 2 (OLSRv2) version 2 (OLSRv2)
draft-ietf-manet-olsrv2-multipath-04 draft-ietf-manet-olsrv2-multipath-05
Abstract Abstract
This document specifies a multi-path extension for the Optimized Link This document specifies a multi-path extension for the Optimized Link
State Routing Protocol version 2 (OLSRv2) to discover multiple State Routing Protocol version 2 (OLSRv2) to discover multiple
disjoint paths, so as to improve reliability of the OLSRv2 protocol. disjoint paths, so as to improve reliability of the OLSRv2 protocol.
The interoperability with OLSRv2 is retained. The interoperability with OLSRv2 is retained.
Status of this Memo Status of this Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. 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."
This Internet-Draft will expire on January 1, 2016. This Internet-Draft will expire on January 3, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Motivation and Experiments to Be Conducted . . . . . . . . 3 1.1. Motivation and Experiments to Be Conducted . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Applicability Statement . . . . . . . . . . . . . . . . . . . 5 3. Applicability Statement . . . . . . . . . . . . . . . . . . . 5
4. Protocol Overview and Functioning . . . . . . . . . . . . . . 6 4. Protocol Overview and Functioning . . . . . . . . . . . . . . 6
5. Parameters and Constants . . . . . . . . . . . . . . . . . . . 7 5. Parameters and Constants . . . . . . . . . . . . . . . . . . . 7
5.1. Router Parameters . . . . . . . . . . . . . . . . . . . . 7 5.1. Router Parameters . . . . . . . . . . . . . . . . . . . . 7
6. Packets and Messages . . . . . . . . . . . . . . . . . . . . . 7 6. Packets and Messages . . . . . . . . . . . . . . . . . . . . . 7
6.1. HELLO and TC messages . . . . . . . . . . . . . . . . . . 8 6.1. HELLO and TC messages . . . . . . . . . . . . . . . . . . 8
6.1.1. SR_OLSRv2 TLV . . . . . . . . . . . . . . . . . . . . 8 6.1.1. SOURCE_ROUTE TLV . . . . . . . . . . . . . . . . . . . 8
6.2. Datagram . . . . . . . . . . . . . . . . . . . . . . . . . 8 6.2. Datagram . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2.1. Source Routing Header in IPv4 . . . . . . . . . . . . 8 6.2.1. Source Routing Header in IPv4 . . . . . . . . . . . . 8
6.2.2. Source Routing Header in IPv6 . . . . . . . . . . . . 8 6.2.2. Source Routing Header in IPv6 . . . . . . . . . . . . 8
7. Information Bases . . . . . . . . . . . . . . . . . . . . . . 9 7. Information Bases . . . . . . . . . . . . . . . . . . . . . . 9
7.1. SR-OLSRv2 Router Set . . . . . . . . . . . . . . . . . . . 9 7.1. SR-OLSRv2 Router Set . . . . . . . . . . . . . . . . . . . 9
7.2. Multi-path Routing Set . . . . . . . . . . . . . . . . . . 9 7.2. Multi-path Routing Set . . . . . . . . . . . . . . . . . . 9
8. Protocol Details . . . . . . . . . . . . . . . . . . . . . . . 10 8. Protocol Details . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. HELLO and TC Message Generation . . . . . . . . . . . . . 10 8.1. HELLO and TC Message Generation . . . . . . . . . . . . . 10
8.2. HELLO and TC Message Processing . . . . . . . . . . . . . 10 8.2. HELLO and TC Message Processing . . . . . . . . . . . . . 10
8.3. Datagram Processing at the MP-OLSRv2 Originator . . . . . 10 8.3. Datagram Processing at the MP-OLSRv2 Originator . . . . . 10
8.4. Multi-path Dijkstra Algorithm . . . . . . . . . . . . . . 11 8.4. Multi-path Dijkstra Algorithm . . . . . . . . . . . . . . 11
8.5. Datagram Forwarding . . . . . . . . . . . . . . . . . . . 12 8.5. Datagram Forwarding . . . . . . . . . . . . . . . . . . . 12
9. Configuration Parameters . . . . . . . . . . . . . . . . . . . 13 9. Configuration Parameters . . . . . . . . . . . . . . . . . . . 13
10. Implementation Status . . . . . . . . . . . . . . . . . . . . 14 10. Implementation Status . . . . . . . . . . . . . . . . . . . . 14
10.1. Multi-path extension based on nOLSRv2 . . . . . . . . . . 14 10.1. Multi-path extension based on nOLSRv2 . . . . . . . . . . 14
10.2. Multi-path extension based on olsrd . . . . . . . . . . . 14 10.2. Multi-path extension based on olsrd . . . . . . . . . . . 14
10.3. Multi-path extension based on umOLSR . . . . . . . . . . . 15 10.3. Multi-path extension based on umOLSR . . . . . . . . . . . 15
11. Security Considerations . . . . . . . . . . . . . . . . . . . 15 11. Security Considerations . . . . . . . . . . . . . . . . . . . 15
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
12.1. Expert Review: Evaluation Guidlines . . . . . . . . . . . 16
12.2. Message TLV Types . . . . . . . . . . . . . . . . . . . . 16
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
14.1. Normative References . . . . . . . . . . . . . . . . . . . 16 14.1. Normative References . . . . . . . . . . . . . . . . . . . 17
14.2. Informative References . . . . . . . . . . . . . . . . . . 17 14.2. Informative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Examples of Multi-path Dijkstra Algorithm . . . . . . 18 Appendix A. Examples of Multi-path Dijkstra Algorithm . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
The Optimized Link State Routing Protocol version 2 (OLSRv2) The Optimized Link State Routing Protocol version 2 (OLSRv2)
[RFC7181] is a proactive link state protocol designed for use in [RFC7181] is a proactive link state protocol designed for use in
mobile ad hoc networks (MANETs). It generates routing messages mobile ad hoc networks (MANETs). It generates routing messages
periodically to create and maintain a Routing Set, which contains periodically to create and maintain a Routing Set, which contains
routing information to all the possible destinations in the routing routing information to all the possible destinations in the routing
domain. For each destination, there exists a unique Routing Tuple, domain. For each destination, there exists a unique Routing Tuple,
which indicates the next hop to reach the destination. which indicates the next hop to reach the destination.
skipping to change at page 8, line 17 skipping to change at page 8, line 17
HELLO and TC messages used by MP-OLSRv2 Routing Process share the HELLO and TC messages used by MP-OLSRv2 Routing Process share the
same format as defined in [RFC7181]. In addition, a new Message TLV same format as defined in [RFC7181]. In addition, a new Message TLV
type is defined, to identify the originator of the HELLO or TC type is defined, to identify the originator of the HELLO or TC
message that supports source route forwarding. The new Message TLV message that supports source route forwarding. The new Message TLV
type is introduced for the interoperability between OLSRv2 and MP- type is introduced for the interoperability between OLSRv2 and MP-
OLSRv2: only the routers supporting source-route forwarding can be OLSRv2: only the routers supporting source-route forwarding can be
used in the source routing header of a datagram, because adding an used in the source routing header of a datagram, because adding an
router that does not understand the source routing header will cause router that does not understand the source routing header will cause
routing failure. routing failure.
6.1.1. SR_OLSRv2 TLV 6.1.1. SOURCE_ROUTE TLV
SR_OLSRv2 TLV is a Message TLV that signals the message is generated SOURCE_ROUTE TLV is a Message TLV that signals the message is
by a router that supports source-route forwarding. It can be an MP- generated by a router that supports source-route forwarding. It can
OLSRv2 Routing Process, or an OLSRv2 Routing Process that support be an MP-OLSRv2 Routing Process, or an OLSRv2 Routing Process that
source-route forwarding. The SR_OLSRv2 TLV does not include any support source-route forwarding. The SOURCE_ROUTE TLV does not
value. include any value.
Every HELLO or TC message generated by a MP-OLSRv2 Routing Process Every HELLO or TC message generated by a MP-OLSRv2 Routing Process
MUST have one SR_OLSRv2 TLV. MUST have one SOURCE_ROUTE TLV.
Every HELLO or TC message generate by a OLSRv2 Routing Process MAY Every HELLO or TC message generate by a OLSRv2 Routing Process MAY
have one SR_OLSRv2 TLV, if the OLSRv2 Routing Process supports have one SOURCE_ROUTE TLV, if the OLSRv2 Routing Process supports
source-route forwarding, and is willing to join the source route source-route forwarding, and is willing to join the source route
generated by other MP-OLSRv2 Routing Processes. The existence of generated by other MP-OLSRv2 Routing Processes. The existence of
SR_OLSRv2 TLV MUST be consistent for a specific OLSRv2 Routing SOURCE_ROUTE TLV MUST be consistent for a specific OLSRv2 Routing
Process, i.e., either it adds SR_OLSRv2 TLV to all its HELLO/TC Process, i.e., either it adds SOURCE_ROUTE TLV to all its HELLO/TC
messages, or it does not add SR_OLSRv2 TLV to any HELLO/TC message. messages, or it does not add SOURCE_ROUTE TLV to any HELLO/TC
message.
6.2. Datagram 6.2. Datagram
6.2.1. Source Routing Header in IPv4 6.2.1. Source Routing Header in IPv4
In IPv4 [RFC0791] networks, the MP-OLSRv2 routing process employs In IPv4 [RFC0791] networks, the MP-OLSRv2 routing process employs
loose source routing header, as defined in [RFC0791]. It exists as loose source routing header, as defined in [RFC0791]. It exists as
an option header, with option class 0, and option number 3. an option header, with option class 0, and option number 3.
The source route information is kept in the "route data" field of the The source route information is kept in the "route data" field of the
skipping to change at page 10, line 28 skipping to change at page 10, line 28
retains the basic routing control packets formats and processing of retains the basic routing control packets formats and processing of
OLSRv2 to obtain topology information of the network. The main OLSRv2 to obtain topology information of the network. The main
differences between OLSRv2 routing process are the datagram differences between OLSRv2 routing process are the datagram
processing at the source router and datagram forwarding. processing at the source router and datagram forwarding.
8.1. HELLO and TC Message Generation 8.1. HELLO and TC Message Generation
HELLO and TC messages are generated according to the section 15.1 or HELLO and TC messages are generated according to the section 15.1 or
section 16.1 of [RFC7181]. section 16.1 of [RFC7181].
A single Message TLV with Type := SR_OLSRv2 MUST be added to the A single Message TLV with Type := SOURCE_ROUTE MUST be added to the
message. message.
8.2. HELLO and TC Message Processing 8.2. HELLO and TC Message Processing
HELLO and TC messages are processed according to the section 15.3 and HELLO and TC messages are processed according to the section 15.3 and
16.3 of [RFC7181]. 16.3 of [RFC7181].
For every HELLO or TC message received, if there exists a Message TLV For every HELLO or TC message received, if there exists a Message TLV
with Type := SR_OLSRv2, create or update (if the tuple exists with Type := SOURCE_ROUTE, create or update (if the tuple exists
already) the SR-OLSR Router Tuple with already) the SR-OLSR Router Tuple with
o SR_OLSR_addr = originator of the HELLO or TC message o SR_OLSR_addr = originator of the HELLO or TC message
and set the SR_OLSR_valid_time := current_time + SR_OLSR_HOLD_TIME. and set the SR_OLSR_valid_time := current_time + SR_OLSR_HOLD_TIME.
8.3. Datagram Processing at the MP-OLSRv2 Originator 8.3. Datagram Processing at the MP-OLSRv2 Originator
When the MP-OLSRv2 routing process receives a datagram from upper When the MP-OLSRv2 routing process receives a datagram from upper
layers or interfaces connecting other routing domains, find the layers or interfaces connecting other routing domains, find the
skipping to change at page 15, line 32 skipping to change at page 15, line 32
Implementation experience and test data can be found at [WCNC08]. Implementation experience and test data can be found at [WCNC08].
11. Security Considerations 11. Security Considerations
As an extension of [RFC7181], the security considerations and As an extension of [RFC7181], the security considerations and
security architecture illustrated in [RFC7181] are applicable to this security architecture illustrated in [RFC7181] are applicable to this
MP-OLSRv2 specification. MP-OLSRv2 specification.
The implementations without security mechanisms are vulnerable to The implementations without security mechanisms are vulnerable to
threats discussed in [I-D.clausen-manet-olsrv2-sec-threats]. As threats discussed in [I-D.ietf-manet-olsrv2-sec-threats]. As
[RFC7181], a conformant implementation of MP-OLSRv2 MUST, at minimum, [RFC7181], a conformant implementation of MP-OLSRv2 MUST, at minimum,
implement the security mechanisms specified in [RFC7183] to provide implement the security mechanisms specified in [RFC7183] to provide
integrity and replay protection of routing control messages. integrity and replay protection of routing control messages.
Compared to OLSRv2, the use of source routing header in this Compared to OLSRv2, the use of source routing header in this
specification introduces vulnerabilities related to source routing specification introduces vulnerabilities related to source routing
attacks, which include bypassing filtering devices, bandwidth attacks, which include bypassing filtering devices, bandwidth
exhaustion of certain routers, etc. Those attacks are discussed in exhaustion of certain routers, etc. Those attacks are discussed in
Section 5.1 of [RFC6554] and [RFC5095]. To make sure that the Section 5.1 of [RFC6554] and [RFC5095]. To make sure that the
influence is limited to the OLSRv2/MP-OLSRv2 routing domain, the influence is limited to the OLSRv2/MP-OLSRv2 routing domain, the
source routing header MUST be used only in the current routing source routing header MUST be used only in the current routing
domain. domain.
12. IANA Considerations 12. IANA Considerations
This specification defines one Message TLV Type, which must be This section adds one new Message TLV, allocated as a new Type
allocated from the Message TLV Types repository of [RFC5444]. Extension to an existing Message TLV.
IANA is requested to create a registry for Message TLV, in accordance This specification assumes that the TLV renaming specified in
with Section 6.2 of [RFC5444], and with initial assignments and [I-D.ietf-manet-tlv-naming] has been carried out.
allocation policies as specified in Table 1.
+--------+-----------+---------------------------------+------------+ 12.1. Expert Review: Evaluation Guidlines
| Type | Name | Description | Allocation |
| | | | Policy |
+--------+-----------+---------------------------------+------------+
| 9 | SR_OLSRv2 | The originator of the message | |
| | | supports source routing | |
| 10-223 | | Unassigned | Expert |
| | | | Review |
+--------+-----------+---------------------------------+------------+
Table 1: Message TLV Types For the registry where an Expert Review is required, the designated
expert SHOULD take the same general recommendations into
consideration as are specified by [RFC5444] and
[I-D.ietf-manet-tlv-naming].
12.2. Message TLV Types
This specification updates the Message Type 7 by adding the new Type
Extension SOURCE_ROUTE, as illustrated in Table 1.
+-----------+--------------+------------------------+---------------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+--------------+------------------------+---------------+
| TBD | SOURCE_ROUTE | Indicates the | This |
| | | originator of the | specification |
| | | message supports | |
| | | source route | |
| | | forwarding. No value. | |
| TBD-223 | | Unassigned | |
| 224-255 | | Reserved for | |
| | | Experimental Use | |
+-----------+--------------+------------------------+---------------+
Table 1: SOURCE_ROUTE type for RFC 5444 Type 7 Message TLV Type
Extensions
13. Acknowledgments 13. Acknowledgments
The authors would like to thank Sylvain David, Asmaa Adnane, Eddy The authors would like to thank Sylvain David, Asmaa Adnane, Eddy
Cizeron, Salima Hamma, Pascal Lesage and Xavier Lecourtier for their Cizeron, Salima Hamma, Pascal Lesage and Xavier Lecourtier for their
efforts in developing, implementing and testing the specifications. efforts in developing, implementing and testing the specification.
The authors also appreciate valuable comments and discussions from The authors also appreciate valuable comments and discussions from
Thomas Clausen, Ulrich Herberg, Justin Dean, Geoff Ladwig and Henning Thomas Clausen, Ulrich Herberg, Justin Dean, Geoff Ladwig, Henning
Rogge. Rogge and Christopher Dearlove.
14. References 14. References
14.1. Normative References 14.1. Normative References
[I-D.ietf-manet-tlv-naming]
Dearlove, C. and T. Clausen, "TLV Naming in the MANET
Generalized Packet/Message Format",
draft-ietf-manet-tlv-naming-05 (work in progress),
June 2015.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5444] Clausen, T., Dearlove, C., Dean, J., and C. Adjih, [RFC5444] Clausen, T., Dearlove, C., Dean, J., and C. Adjih,
"Generalized Mobile Ad Hoc Network (MANET) Packet/Message "Generalized Mobile Ad Hoc Network (MANET) Packet/Message
Format", RFC 5444, February 2009. Format", RFC 5444, February 2009.
skipping to change at page 17, line 22 skipping to change at page 17, line 47
and Optimized Link State Routing Protocol Version 2 and Optimized Link State Routing Protocol Version 2
(OLSRv2)", RFC 7183, April 2014. (OLSRv2)", RFC 7183, April 2014.
14.2. Informative References 14.2. Informative References
[ADHOC11] Yi, J., Adnane, A-H., David, S., and B. Parrein, [ADHOC11] Yi, J., Adnane, A-H., David, S., and B. Parrein,
"Multipath optimized link state routing for mobile ad hoc "Multipath optimized link state routing for mobile ad hoc
networks", In Elsevier Ad Hoc Journal, vol.9, n. 1, 28-47, networks", In Elsevier Ad Hoc Journal, vol.9, n. 1, 28-47,
January, 2011. January, 2011.
[I-D.clausen-manet-olsrv2-sec-threats]
Clausen, T., Herberg, U., and J. Yi, "Security Threats for
the Optimized Link State Routing Protocol version 2
(OLSRv2)", draft-clausen-manet-olsrv2-sec-threats-01 (work
in progress), August 2014.
[I-D.ietf-manet-olsrv2-dat-metric] [I-D.ietf-manet-olsrv2-dat-metric]
Rogge, H. and E. Baccelli, "Packet Sequence Number based Rogge, H. and E. Baccelli, "Packet Sequence Number based
directional airtime metric for OLSRv2", directional airtime metric for OLSRv2",
draft-ietf-manet-olsrv2-dat-metric-05 (work in progress), draft-ietf-manet-olsrv2-dat-metric-05 (work in progress),
April 2015. April 2015.
[I-D.ietf-manet-olsrv2-multitopology] [I-D.ietf-manet-olsrv2-multitopology]
Dearlove, C. and T. Clausen, "Multi-Topology Extension for Dearlove, C. and T. Clausen, "Multi-Topology Extension for
the Optimized Link State Routing Protocol version 2 the Optimized Link State Routing Protocol version 2
(OLSRv2)", draft-ietf-manet-olsrv2-multitopology-05 (work (OLSRv2)", draft-ietf-manet-olsrv2-multitopology-05 (work
in progress), February 2015. in progress), February 2015.
[I-D.ietf-manet-olsrv2-sec-threats]
Clausen, T., Herberg, U., and J. Yi, "Security Threats for
the Optimized Link State Routing Protocol version 2
(OLSRv2)", draft-ietf-manet-olsrv2-sec-threats-00 (work in
progress), February 2015.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
December 1998. December 1998.
[RFC2501] Corson, M. and J. Macker, "Mobile Ad hoc Networking [RFC2501] Corson, M. and J. Macker, "Mobile Ad hoc Networking
(MANET): Routing Protocol Performance Issues and (MANET): Routing Protocol Performance Issues and
 End of changes. 25 change blocks. 
47 lines changed or deleted 71 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/