draft-ietf-manet-olsrv2-management-snapshot-01.txt   draft-ietf-manet-olsrv2-management-snapshot-02.txt 
Network Working Group T. Clausen Network Working Group T. Clausen
Internet-Draft LIX, Ecole Polytechnique Internet-Draft LIX, Ecole Polytechnique
Intended status: Informational U. Herberg Intended status: Informational U. Herberg
Expires: January 5, 2015 Fujitsu Laboratories of America Expires: February 8, 2015 Fujitsu Laboratories of America
July 4, 2014 August 7, 2014
Snapshot of OLSRv2-Routed MANET Management Snapshot of OLSRv2-Routed MANET Management
draft-ietf-manet-olsrv2-management-snapshot-01 draft-ietf-manet-olsrv2-management-snapshot-02
Abstract Abstract
This document describes how Mobile Ad Hoc Networks (MANETs) are This document describes how Mobile Ad Hoc Networks (MANETs) are
typically managed, in terms of pre-deployment management, as well as typically managed, in terms of pre-deployment management, as well as
rationale and means of monitoring and management of MANET routers rationale and means of monitoring and management of MANET routers
running the Optimized Link State Routing protocol version 2 (OLSRv2) running the Optimized Link State Routing protocol version 2 (OLSRv2)
and its constituent MANET NehgiborHood Discovery Protocol (NHDP). and its constituent MANET NehgiborHood Discovery Protocol (NHDP).
Apart from pre-deployment management for setting up IP addresses and Apart from pre-deployment management for setting up IP addresses and
security related credentials, OLSRv2 only needs routers to agree one security related credentials, OLSRv2 only needs routers to agree one
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 5, 2015. This Internet-Draft will expire on February 8, 2015.
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
skipping to change at page 2, line 33 skipping to change at page 2, line 33
3.2. Interface Addresses . . . . . . . . . . . . . . . . . . . 4 3.2. Interface Addresses . . . . . . . . . . . . . . . . . . . 4
3.3. Security Material . . . . . . . . . . . . . . . . . . . . 5 3.3. Security Material . . . . . . . . . . . . . . . . . . . . 5
3.4. The Value of C . . . . . . . . . . . . . . . . . . . . . . 5 3.4. The Value of C . . . . . . . . . . . . . . . . . . . . . . 5
4. How do we Manage OLSRv2-based MANETs? . . . . . . . . . . . . 5 4. How do we Manage OLSRv2-based MANETs? . . . . . . . . . . . . 5
4.1. Internal Management . . . . . . . . . . . . . . . . . . . 6 4.1. Internal Management . . . . . . . . . . . . . . . . . . . 6
4.2. External Management . . . . . . . . . . . . . . . . . . . 6 4.2. External Management . . . . . . . . . . . . . . . . . . . 6
5. What and Why do we Manage and Monitor? . . . . . . . . . . . . 7 5. What and Why do we Manage and Monitor? . . . . . . . . . . . . 7
6. Typical Communication Patterns . . . . . . . . . . . . . . . . 8 6. Typical Communication Patterns . . . . . . . . . . . . . . . . 8
7. This Document does not Constrain how to Manage and Monitor 7. This Document does not Constrain how to Manage and Monitor
MANETs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 MANETs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
9. Informative References . . . . . . . . . . . . . . . . . . . . 11 9. Security Considerations . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
11. Informative References . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
The MANET routing protocol OLSRv2 [RFC7181], as well as its The MANET routing protocol OLSRv2 [RFC7181], as well as its
constituent parts NHDP [RFC6130], [RFC5497], [RFC5148], [RFC5444], constituent parts NHDP [RFC6130], [RFC5497], [RFC5148], [RFC5444],
[RFC7182], [RFC7183], is designed to autonomously maintain routes [RFC7182], [RFC7183], is designed to autonomously maintain routes
across a dynamic network topology. OLSRv2 is designed so as to across a dynamic network topology. OLSRv2 is designed so as to
minimize operator intervention throughout the duration of a network minimize operator intervention throughout the duration of a network
deployment, and to allow for heterogeneous configuration of routers deployment, and to allow for heterogeneous configuration of routers
within the same network deployment: most configuration values are within the same network deployment: most configuration values are
skipping to change at page 11, line 19 skipping to change at page 11, line 19
between routers, so as to obtain locally optimized performance. between routers, so as to obtain locally optimized performance.
While such a management model is highly interesting, it is also at While such a management model is highly interesting, it is also at
present entirely fictional - at least outside the realm of research. present entirely fictional - at least outside the realm of research.
It is included to, both, indicate directions being explored (but not It is included to, both, indicate directions being explored (but not
exploited), and to insist that the intent of this document is not to exploited), and to insist that the intent of this document is not to
prescribe how MANETs are to be managed, in the presence or in the prescribe how MANETs are to be managed, in the presence or in the
future, but to describe the (known) state of how MANETs are managed, future, but to describe the (known) state of how MANETs are managed,
presently. presently.
8. Acknowledgments 8. IANA Considerations
This document has no actions for IANA.
[This section may be removed by the RFC Editor.]
9. Security Considerations
This document does not specify a protocol, nor does it provide
recommendations for how to manage an OLSRv2 deployment - rather, it
reflects how some known deployments of OLSRv2 (and its predecessor,
OLSR) have been known to be managed.
With that being said, managing an OLSRv2 network requires the ability
to inspect and affect the internal state of the routers therein, by
way of mechanisms other than the protocol signals specified for
OLSRv2 [RFC7181] and NHDP [RFC6130].
When affecting the state of the OLSRv2 routing process, a management
process can be considered as an "outside process" to OLSRv2 and is
then expected to respect (at least) the constraints given in Section
5.5, Section 5.6, and in Appendix A of [RFC7181], as well as in
Section 5.5 and in Appendix B of [RFC6130].
For both inspecting and affecting the state of an OLSRv2 routing
process by way of a management interface, great care is necessary to
avoid divulging information that should not be exposed, and in
opening additional vulnerabilities by way of the management
interface. In part, to be able to benefit from securing existing
management interfaces, protocols, and implementations, migration to a
standardized management framework is desired, and was one of the
motivators for standardizing MIB modules for OLSRv2 and NHDP in the
first place.
10. Acknowledgments
The authors would like to gratefully acknowledge the following people The authors would like to gratefully acknowledge the following people
for intense technical discussions, early reviews, and comments on the for intense technical discussions, early reviews, and comments on the
documents: Alan Cullen (BAE Systems), Christopher Dearlove (BAE documents: Alan Cullen (BAE Systems), Christopher Dearlove (BAE
Systems), Adrian Farrel (Juniper), David Harrington (Comcast), and Systems), Adrian Farrel (Juniper), David Harrington (Comcast), and
Jurgen Schoenwalder (Jacobs University). Jurgen Schoenwaelder (Jacobs University).
9. Informative References 11. Informative References
[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.
[RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter [RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter
Considerations in Mobile Ad Hoc Networks (MANETs)", Considerations in Mobile Ad Hoc Networks (MANETs)",
RFC 5148, February 2008. RFC 5148, February 2008.
[RFC5444] Clausen, T., Dearlove, C., Dean, J., and C. Adjih, [RFC5444] Clausen, T., Dearlove, C., Dean, J., and C. Adjih,
"Generalized MANET Packet/Message Format", RFC 5444, "Generalized MANET Packet/Message Format", RFC 5444,
 End of changes. 7 change blocks. 
10 lines changed or deleted 46 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/