AODV Extensions for MANET Clustering
draft-ahn-manet-clustering-aodv-00
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Author | Sanghyun Ahn | ||
| Last updated | 2012-12-03 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-ahn-manet-clustering-aodv-00
MANET Working Group Sanghyun Ahn
Internet Draft University of Seoul
Expires: May 27, 2013 December 3, 2012
AODV Extensions for MANET Clustering
draft-ahn-manet-clustering-aodv-00.txt
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, except to format it
for publication as an RFC or to translate it into languages other
than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 27, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (http://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Ahn Expires May 27, 2013 [Page 1]
Internet-Draft AODV Extensions for MANET Clustering December 2012
Abstract
This document describes an extention on AODV [1] so that clustering
of MANET nodes can be allowed for the improvement of MANET
scalability. MANET clustering requires some MANET nodes to become
Cluster Heads (CHs) and each non-CH MANET nodes to belong to any one
appropriate cluster which is represented by a CH node.In this draft,
AODV control messages are extended for MANET clustering.
Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Extensions on AODV Control Messages. . . . . . . . . . . . . . 4
4.1 Cluster Anouncement (CLAN) Message Format . . . . . . . . 4
4.2 Cluster Join (CLJN) Message Format . . . . . . . . . . . . 5
5. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Other Considerations . . . . . . . . . . . . . . . . . . . . . 6
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
Ahn Expires May 27, 2013 [Page 2]
Internet-Draft AODV Extensions for MANET Clustering December 2012
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Introduction
In a MANET where a subset of nodes grouping together such as in an
office environment with a set of departments, MANET clustering is a
good choice for the efficient communication among MANET nodes.
For MANET clustering, some nodes are required to act as clulster
heads (CHs) and the others as cluster members (non-CH nodes).
A CH announces its existence by sending out CH announcement messages
and each non-CH node joins to any one cluster after receiving one or
more CH announcement messages from its nearby CHs. The detailed
MANET clustering architecture is defined in a companion draft [2].
For this MANET clustering architecture to work in the MANET using
AODV [1] as its routing protocol, AODV is required to be extended.
Therefore, in this draft, we define how to extend AODV for the MANET
clustering architecture of [2].
3. Terminology
Cluster Head The representative node of a cluster; the
cluster head receives data from its cluster
members and forwards the data to the cluster
head of the cluster to which the destination
belongs, and vice versa.
Cluster Member The node belonging to a cluster
Cluster Size The maximum number of hops from a cluster head
to any one of its cluster members; assumed to
be k
Cluster Announcement Message
The message sent by the cluster head to its
k-hop neighbors to indicate its willingness of
forwarding data from its cluster members
Cluster Join Message The message sent by a node wishing to act as a
cluster member to the cluster head upon
receiving a Cluster Announcement message
Ahn Expires May 27, 2013 [Page 3]
Internet-Draft AODV Extensions for MANET Clustering December 2012
4. Extensions on AODV Control Messages
For the cluster announcement and the cluster join, we extend the RREQ
and the RREP messages of AODV, respectively.
4.1 Cluster Anouncement (CLAN) Message Format
If a node wishes to act as a CH, it should sends out a Cluster
Announcement message to its k-hop neighbors, where k is the cluster
size.
The CLAN message is extended from the RREQ message of AODV.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type |J|R|G|D|U|C| Reserved | Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RREQ ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 1
C Cluster flag; indicates whether this message is
a Cluster Announcement message
Hop Count The cluster size; the maximum number of hops from
the Originator IP Address to a cluster member
Destination IP Address
The broadcast address (i.e., 255.255.255.255)
Originator IP Address
The IP Address of the node which originated this
Cluster Announcement message
Ahn Expires May 27, 2013 [Page 4]
Internet-Draft AODV Extensions for MANET Clustering December 2012
4.2 Cluster Join (CLJN) Message Format
Once a node receives a CLAN message, it replies back to the
corresponding CH (i.e., the originator of the CLAN message) with a
Cluster Join message, if it wishes to join the cluster announced
by the CLAN message.
The CLJN message is extended from the RREP message of AODV.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type |R|A|C| Reserved |Prefix Sz| Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 2
C Cluster flag; indicates whether this message is
a Cluter Join message
Hop Count The number of hops from the Destination IP Address
to the Originator IP Address; This is set to the
Hop Count value of the received CLAN message minus
one
Destination IP Address
The IP Address of the node which originated this
Cluster Join message
Originator IP Address
The IP Address of the node which originated the
corresponding Cluster Announcement message
If a node receives a CLAN message, it decreases the Hop Count value
of the CLAN message by one and, if the modified Hop Count value is
greater than 1, it forwards it to its 1-hop neighbors. Otherwise, it
does not forward any more. And if it wants to join the cluster, it
sends out a CLJN message back to the originator node of the CLAN
message.
Ahn Expires May 27, 2013 [Page 5]
Internet-Draft AODV Extensions for MANET Clustering December 2012
When the originator node of the CLAN message receives the CLJN
message, it can determine the number of hops from the originator to
the cluster member by subtracting the Hop Count value in the CLJN
message from k (i.e., the cluster size).
5. Operation
TBD.
6. Other Considerations
TBD.
References
[1] C. Perkins, E. Belding-Royer and S. Das, "Ad hoc On-Demand
Distance Vector (AODV) Routing," RFC 3561, July 2003.
[2] S. Ahn, "Architecture for MANET Clustering," draft-ahn-manet-
clustering-architecture-00.txt, Dec. 2012.
Author's Address
Sanghyun Ahn
University of Seoul
90, Cheonnong-dong, Tongdaemun-gu
Seoul 130-743
Korea
Email: ahn@uos.ac.kr
Ahn Expires May 27, 2013 [Page 6]