draft-ietf-manet-olsrv2-multitopology-01.txt   draft-ietf-manet-olsrv2-multitopology-02.txt 
Mobile Ad hoc Networking (MANET) C. Dearlove Mobile Ad hoc Networking (MANET) C. Dearlove
Internet-Draft BAE Systems ATC Internet-Draft BAE Systems ATC
Intended status: Experimental T. Clausen Intended status: Experimental T. Clausen
Expires: December 25, 2014 LIX, Ecole Polytechnique Expires: December 27, 2014 LIX, Ecole Polytechnique
June 23, 2014 June 25, 2014
Multi-Topology Extension for the Optimized Link State Routing Protocol Multi-Topology Extension for the Optimized Link State Routing Protocol
version 2 (OLSRv2) version 2 (OLSRv2)
draft-ietf-manet-olsrv2-multitopology-01 draft-ietf-manet-olsrv2-multitopology-02
Abstract Abstract
This specification describes an extension to the Optimized Link State This specification describes an extension to the Optimized Link State
Routing Protocol version 2 (OLSRv2) to support multiple routing Routing Protocol version 2 (OLSRv2) to support multiple routing
topologies, while retaining interoperability with OLSRv2 routers that topologies, while retaining interoperability with OLSRv2 routers that
do not implement this extension. do not implement this extension.
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 December 25, 2014. This Internet-Draft will expire on December 27, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Notation . . . . . . . . . . . . . . . . . . . 3 1.1. Motivation and Experimentation . . . . . . . . . . . . . . 3
3. Applicability Statement . . . . . . . . . . . . . . . . . . . 4 2. Terminology and Notation . . . . . . . . . . . . . . . . . . . 4
4. Protocol Overview and Functioning . . . . . . . . . . . . . . 4 3. Applicability Statement . . . . . . . . . . . . . . . . . . . 5
5. Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Protocol Overview and Functioning . . . . . . . . . . . . . . 5
5. Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Information Bases . . . . . . . . . . . . . . . . . . . . . . 6 6. Information Bases . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Local Attached Network Set . . . . . . . . . . . . . . . . 6 6.1. Local Attached Network Set . . . . . . . . . . . . . . . . 7
6.2. Link Sets . . . . . . . . . . . . . . . . . . . . . . . . 6 6.2. Link Sets . . . . . . . . . . . . . . . . . . . . . . . . 7
6.3. 2-Hop Sets . . . . . . . . . . . . . . . . . . . . . . . . 6 6.3. 2-Hop Sets . . . . . . . . . . . . . . . . . . . . . . . . 7
6.4. Neighbor Set . . . . . . . . . . . . . . . . . . . . . . . 6 6.4. Neighbor Set . . . . . . . . . . . . . . . . . . . . . . . 7
6.5. Router Topology Set . . . . . . . . . . . . . . . . . . . 7 6.5. Router Topology Set . . . . . . . . . . . . . . . . . . . 8
6.6. Routable Address Topology Set . . . . . . . . . . . . . . 7 6.6. Routable Address Topology Set . . . . . . . . . . . . . . 8
6.7. Attached Network Set . . . . . . . . . . . . . . . . . . . 7 6.7. Attached Network Set . . . . . . . . . . . . . . . . . . . 8
6.8. Routing Sets . . . . . . . . . . . . . . . . . . . . . . . 8 6.8. Routing Sets . . . . . . . . . . . . . . . . . . . . . . . 8
7. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Message TLVs . . . . . . . . . . . . . . . . . . . . . . . 8 7.1. Message TLVs . . . . . . . . . . . . . . . . . . . . . . . 9
7.1.1. MPR_TYPES TLV . . . . . . . . . . . . . . . . . . . . 8 7.1.1. MPR_TYPES TLV . . . . . . . . . . . . . . . . . . . . 9
7.1.2. MPR_WILLING TLV . . . . . . . . . . . . . . . . . . . 8 7.1.2. MPR_WILLING TLV . . . . . . . . . . . . . . . . . . . 9
7.2. Address Block TLVs . . . . . . . . . . . . . . . . . . . . 9 7.2. Address Block TLVs . . . . . . . . . . . . . . . . . . . . 10
7.2.1. LINK_METRIC TLV . . . . . . . . . . . . . . . . . . . 9 7.2.1. LINK_METRIC TLV . . . . . . . . . . . . . . . . . . . 10
7.2.2. MPR TLV . . . . . . . . . . . . . . . . . . . . . . . 10 7.2.2. MPR TLV . . . . . . . . . . . . . . . . . . . . . . . 10
7.2.3. GATEWAY TLV . . . . . . . . . . . . . . . . . . . . . 10 7.2.3. GATEWAY TLV . . . . . . . . . . . . . . . . . . . . . 11
8. HELLO Messages . . . . . . . . . . . . . . . . . . . . . . . . 11 8. HELLO Messages . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. HELLO Message Generation . . . . . . . . . . . . . . . . . 11 8.1. HELLO Message Generation . . . . . . . . . . . . . . . . . 12
8.2. HELLO Message Processing . . . . . . . . . . . . . . . . . 11 8.2. HELLO Message Processing . . . . . . . . . . . . . . . . . 12
9. TC Messages . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. TC Messages . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. TC Message Generation . . . . . . . . . . . . . . . . . . 12 9.1. TC Message Generation . . . . . . . . . . . . . . . . . . 13
9.2. TC Message Processing . . . . . . . . . . . . . . . . . . 12 9.2. TC Message Processing . . . . . . . . . . . . . . . . . . 13
10. MPR Calculation . . . . . . . . . . . . . . . . . . . . . . . 13 10. MPR Calculation . . . . . . . . . . . . . . . . . . . . . . . 13
11. Routing Set Calculation . . . . . . . . . . . . . . . . . . . 13 11. Routing Set Calculation . . . . . . . . . . . . . . . . . . . 14
12. Management Considerations . . . . . . . . . . . . . . . . . . 13 12. Management Considerations . . . . . . . . . . . . . . . . . . 14
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
13.1. Expert Review: Evaluation Guidelines . . . . . . . . . . . 14 13.1. Expert Review: Evaluation Guidelines . . . . . . . . . . . 15
13.2. Message TLV Types . . . . . . . . . . . . . . . . . . . . 15 13.2. Message TLV Types . . . . . . . . . . . . . . . . . . . . 15
13.3. Address Block TLV Types . . . . . . . . . . . . . . . . . 16 13.3. Address Block TLV Types . . . . . . . . . . . . . . . . . 16
14. Security Considerations . . . . . . . . . . . . . . . . . . . 18 14. Security Considerations . . . . . . . . . . . . . . . . . . . 18
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
16.1. Normative References . . . . . . . . . . . . . . . . . . . 18 16.1. Normative References . . . . . . . . . . . . . . . . . . . 18
16.2. Informative References . . . . . . . . . . . . . . . . . . 19 16.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
skipping to change at page 3, line 28 skipping to change at page 3, line 28
is designed to permit this, while maintaining maximal is designed to permit this, while maintaining maximal
interoperability with OLSRv2 routers not implementing this extension. interoperability with OLSRv2 routers not implementing this extension.
The purpose of OLSRv2 can be described as to create and maintain a The purpose of OLSRv2 can be described as to create and maintain a
Routing Set, which contains all the necessary information to populate Routing Set, which contains all the necessary information to populate
an IP routing table. In a similar way, the role of this extension an IP routing table. In a similar way, the role of this extension
can be described as to create and maintain multiple Routing Sets, one can be described as to create and maintain multiple Routing Sets, one
for each link metric type supported by the router maintaining the for each link metric type supported by the router maintaining the
sets. sets.
1.1. Motivation and Experimentation
Multi-topology routing is a natural extension to a link state routing
protocol, as for example to OSPF (see [RFC4915]). However multi-
topology routing for OLSRv2 does not yet benefit from extensive
operational, or even experimental, experience. This specification is
published to facilitate collecting such experience, with the intent
that in a reasonable period of time after the acceptance of this
specification as an Experimental RFC (as soon as possible after
experimental evidence is collected), an OLSRv2 Multi-Topology Routing
Extension will be proposed for advancement onto Standards Track.
While general experiences with this protocol extension, including
interoperability of implementations, are encouraged, specific
information would be particularly appreciated on the following areas:
o Operation in a network that contains both routers implementing
this extension, and routers implementing only [RFC7181], in
particular are there any unexpected interactions that can break
the network?
o Operation in realistic deployments, and details thereof, including
in particular indicating how many concurrent topologies were
required.
A broader issue that applies to unextended [RFC7181] as well as this
extension (and potentially to other MANET routing protocols) is which
link metric types are useful in a MANET, and how to establish the
metrics to associate with a given link. While this issue is not only
related to this extension, the ability for an OLSRv2 network to
maintain different concurrent link metrics may facilitate both
experiments with different link metric types, ways to measure them,
etc. and may also allow experimentation with link metric types that
are not compromises to handle multiple traffic types.
2. Terminology and Notation 2. Terminology and Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
This specification uses the terminology of [RFC5444], [RFC6130] and This specification uses the terminology of [RFC5444], [RFC6130] and
[RFC7181], which is to be interpreted as described in those [RFC7181], which is to be interpreted as described in those
specifications. specifications.
skipping to change at page 19, line 26 skipping to change at page 19, line 26
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
December 1998. December 1998.
[RFC2501] Macker, J. and S. Corson, "Mobile Ad hoc Networking [RFC2501] Macker, J. and S. Corson, "Mobile Ad hoc Networking
(MANET): Routing Protocol Performance Issues and (MANET): Routing Protocol Performance Issues and
Evaluation Considerations", RFC 2501, January 1999. Evaluation Considerations", RFC 2501, January 1999.
[RFC3626] Clausen, T. and P. Jacquet, "The Optimized Link State [RFC3626] Clausen, T. and P. Jacquet, "The Optimized Link State
Routing Protocol", RFC 3626, October 2003. Routing Protocol", RFC 3626, October 2003.
[RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P.
Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF",
RFC 4915, June 2007.
Authors' Addresses Authors' Addresses
Christopher Dearlove Christopher Dearlove
BAE Systems Advanced Technology Centre BAE Systems Advanced Technology Centre
West Hanningfield Road West Hanningfield Road
Great Baddow, Chelmsford Great Baddow, Chelmsford
United Kingdom United Kingdom
Phone: +44 1245 242194 Phone: +44 1245 242194
Email: chris.dearlove@baesystems.com Email: chris.dearlove@baesystems.com
 End of changes. 11 change blocks. 
30 lines changed or deleted 70 lines changed or added

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