Mobile Ad hoc Networking (MANET) J. Haerri
Internet-Draft C. Bonnet
Intended status: Experimental F. Filali
Expires: August 29, 2007 Institut Eurecom, France
February 25, 2007
MANET Position and Mobility Signaling Format
draft-haerri-manet-position-signaling-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
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 August 29, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Haerri, et al. Expires August 29, 2007 [Page 1]
Internet-Draft MANET Position Signaling February 2007
Abstract
This document describes a flexible TLV (type-length-value structure)
for exchanging geolocalization and mobility information using the
generalized MANET packet/message format.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Applicability Statement . . . . . . . . . . . . . . . . . . . 6
4. Protocol Overview and Functioning . . . . . . . . . . . . . . 7
5. General Mobility TLV Structure . . . . . . . . . . . . . . . . 8
5.1. Constraints . . . . . . . . . . . . . . . . . . . . . . . 9
6. Representing Time . . . . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9. Normative References . . . . . . . . . . . . . . . . . . . . . 13
Appendix A. Message Layout . . . . . . . . . . . . . . . . . . . 14
A.1. Mobility TLVs . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . . . 17
Haerri, et al. Expires August 29, 2007 [Page 2]
Internet-Draft MANET Position Signaling February 2007
1. Introduction
The generalized packet/message format [PacketBB] specifies a
signaling format which MANET routing protocols can employ for
exchanging protocol information. This format presents the ability to
express and associate attributes to packets, messages or addresses,
by way of a general TLV (type-length-value) mechanism.
This document specifies a Mobility TLV structure, which MAY be used
by any MANET routing protocol that needs to exchange geolocalization
information using the generalized MANET packet/message format.
Depending on the configuration, this allows a receiving node to
obtain the position, the azimuth or the velocity of a sending node if
it is used as a message or packet TLV. If it is used as an address
block TLV, it allows a receiving node to obtain the position, the
azimuth or the velocity of nodes different from the sending node.
Haerri, et al. Expires August 29, 2007 [Page 3]
Internet-Draft MANET Position Signaling February 2007
2. Terminology
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].
Additionally, this document uses the terminology from [PacketBB],
and introduces the following terminology
GPS - Global Positioning System. A geolocalization system
developped and operated by the US Department of Defense that is
able to provide accurate worldwide coordinates of devices equiped
with GPS receivers. A similar European system is currently under
developpement under the name of Galileo. The GPS system does not
work without a clear access to at least 3 satellites, thus is
inoperable for indoor positioning.
GPS-free Positioning - A set of techniques that has been developped
in order to provide a mean of localization in situation when a
clear access to satellites is not possible. Most of the methods
uses multilateration techniques and requires either a formal
training, or an anchor node that knows its accurate position.
Time - The universal GPS time expressed in seconds.
Longitude - The longitude describes the location of a place on Earth
east or west of a north-south line called the Prime Meridian
located in Greenwich, UK. Longitude is given as an angular
measurement ranging from 0 degree at the Prime Meridian to +180
degree eastward and -180 degree westward.
Latitude - The latitude gives the location of a place on Earth north
or south of the equator. Latitude is an angular measurement
ranging from 0 degree at the Equator to 90 degree at the poles.
Elevation - The elevation is the altitude of an object from a known
level or datum. Common datums are mean sea level and the surface
of the WGS-84 geoid, used by GPS.
Azimuth - Azimuth is the horizontal component of a direction,
measured around the horizon, from the north toward the east in the
northern hemisphere, and from the south toward the west in the
southern hemisphere.
Mobility - mobility information related to a specific address, which
MAY consist of a longitude, latitude or elevation, a velocity, an
azimuth, or the time this mobility information has been sampled.
Haerri, et al. Expires August 29, 2007 [Page 4]
Internet-Draft MANET Position Signaling February 2007
Stability - a measure of the similarity between a node's sampled
(past) mobility parameters and the actual ones.
Haerri, et al. Expires August 29, 2007 [Page 5]
Internet-Draft MANET Position Signaling February 2007
3. Applicability Statement
The TLV structure described in this document is applicable whenever
the position, the velocity or the azimuth of a node or of a set of
nodes is required in a MANET protocol using the generalized MANET
packet/message format [PacketBB].
Haerri, et al. Expires August 29, 2007 [Page 6]
Internet-Draft MANET Position Signaling February 2007
4. Protocol Overview and Functioning
This specification does not describe a protocol, nor does it mandate
specific node or protocol behavior. Rather, it describes mechanisms
for encoding geolocalization parameters using the TLV mechanism of
[PacketBB].
Protocols using the TLVs specified in this documents MUST transmit
geolocalization information of the sending node using a message or
packet TLV, while general geolocalization information of other nodes
MUST be encoded using a TLV block.
Haerri, et al. Expires August 29, 2007 [Page 7]
Internet-Draft MANET Position Signaling February 2007
5. General Mobility TLV Structure
This specification defines the content and the structure of a
Mobility TLV, which may be a packet, a message, or an address block
TLV. In all cases, a Mobility TLV is always a single value TLV as
specified in [PacketBB].
All TLVs are conformed to the following specification:
<tlv> = <tlv-type>
<tlv-semantic>
<index-start>?
<index-stop>?
<length>?
<value>?
using the regular syntax of [PacketBB].
The <value> field of a Mobility TLV is encoded according to the
following layout
<value> = {<value-semantic><mobility>}*
where:
<value-semantic> is an 8 bit field which describes the stucture of
the <mobility> tag.
bit 0 (position bit): TLV with this bit cleared ('0') does not
contain the position of the address in the respective address
block. TLVs with this bit set ('1') contains position
information.
bit 1 (velocity bit): TLV with this bit cleared ('0') does not
contain the velocity of the address in the respective address
block. TLVs with this bit set ('1') contains the velocity.
bit 2 (azimuth bit): TLV with this bit cleared ('0') does not
contain the azimuth of the address in the respective address
block. TLVs with this bit set ('1') contains the azimuth.
Haerri, et al. Expires August 29, 2007 [Page 8]
Internet-Draft MANET Position Signaling February 2007
bit 3 (stability bit): TLV with this bit cleared ('0') does not
contain the stability of the address in the respective address
block. TLVs with this bit set ('1') contains the stability.
bits 4-7 are RESERVED They MUST be cleared ('0')to be in
conformance with this version of the specification.
<mobility> is a field containing the mobility parameters. The
length of this field may be obtained from the <value-semantic>
field. The <mobility> field is specified by:
<mobility> = {<pos>?<azi>?<velo>?<stab><time>}
<pos> is an 96 bit field containing the coordinates of a node
following the general layout
<pos> = <Longitude><Latitude><Elevation>
<velo> is an 8 bit field containing the node's velocity in m/s
<azi> is an 8 bit field containing the node's azimuth in degree
<stab> is an 8 bit field containing the node's stability ,
which represents the node eagerness to keep the current
mobility parameters, and which MAY be used as a measure of the
relative confidence of the mobility parameters.
<time> is an 64 bit field containing the GPS time in seconds
when these mobility parameters have been sampled. In
conjunction with <stab>, it MAY be able to provide a confidence
predictor of the mobility parameters.
5.1. Constraints
o If the bit <azi> is set ('1'), the bit <velo> MUST also be set
('1').
o Each mobility parameter applies to a single and unique address.
Haerri, et al. Expires August 29, 2007 [Page 9]
Internet-Draft MANET Position Signaling February 2007
6. Representing Time
This document specifies a TLV structure in which time values are used
to represent the sampling time of the geolocalization data. As no
synchronization assumption is defined in this document, the time
shared by all nodes implementing this document MUST be the GPS time.
GPS (Global Positioning System) time is the atomic time scale
implemented by the atomic clocks in the GPS ground control stations
and the GPS satellites themselves. GPS time is expressed as a number
of seconds since the beginning of the GPS epoch on Sunday January 6th
1980 at 0:00 UTC.
Haerri, et al. Expires August 29, 2007 [Page 10]
Internet-Draft MANET Position Signaling February 2007
7. IANA Considerations
This document does not specify any message TLV type.
Haerri, et al. Expires August 29, 2007 [Page 11]
Internet-Draft MANET Position Signaling February 2007
8. Security Considerations
This document is subject to similar security issues as [PacketBB].
Accordingly, similar security considerations may be undertaken.
Haerri, et al. Expires August 29, 2007 [Page 12]
Internet-Draft MANET Position Signaling February 2007
9. Normative References
[PacketBB]
Clausen, T., "Generalized MANET Packet/Message Format", <
www.ietf.org/internet-drafts/
draft-ietf-manet-packetbb-03.txt>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Haerri, et al. Expires August 29, 2007 [Page 13]
Internet-Draft MANET Position Signaling February 2007
Appendix A. Message Layout
This section specifies the translation from the abstract descriptions
of the Mobility TLVs in this document, and the bit-layout Mobility
TLVs actually exchanged between nodes.
A.1. Mobility TLVs
The basic layout of the <value-semantic> field in the <value> field
of a TLV is as follows:
+----+----+----+----+----+----+----+----+-----------------------+
| Semantic | Value |
+----+----+----+----+----+----+----+----+ |
| 7 6 5 4 3 2 1 0 | |
|Resv|Resv|Resv|Resv|Stab|Azim|Velo|Pos | |
+----+----+----+----+----+----+----+----+-----------------------+
| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | Mobility TLV with |
| | velocity only |
+----+----+----+----+----+----+----+----+-----------------------+
| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | Mobility TLV with |
| | velocity and stability|
+----+----+----+----+----+----+----+----+-----------------------+
| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | Mobility TLV with |
| | azimuth |
+----+----+----+----+----+----+----+----+-----------------------+
| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | Mobility TLV with |
| | velocity and position |
+----+----+----+----+----+----+----+----+-----------------------+
| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | Mobility TLV with all|
| | mobility parameters |
+----+----+----+----+----+----+----+----+-----------------------+
Figure 5
where, according to the bits cleared or set in the <value-semantic>
field and the related constraints, any combinations are possible.
Haerri, et al. Expires August 29, 2007 [Page 14]
Internet-Draft MANET Position Signaling February 2007
The basic layout of a Mobility TVL is as follows:
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 | Resv|0|0|1|0|0| Length | Resv |1|1|1|1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Longitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Latitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Elevation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Velocity | Azimuth | Stability | Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6
where all mobility parameters have been displayed. According to the
bits cleared or set in the <value-semantic> field and the related
constraints, any combinations are possible.
Haerri, et al. Expires August 29, 2007 [Page 15]
Internet-Draft MANET Position Signaling February 2007
Authors' Addresses
Jerome Haerri
Institut Eurecom, France
Phone: +33 4 93 00 8176
Email: haerri@eurecom.fr
Christian Bonnet
Institut Eurecom, France
Phone: +33 4 93 00 8108
Email: bonnet@eurecom.fr
Fethi Filali
Institut Eurecom, France
Phone: +33 4 93 00 8134
Email: filali@eurecom.fr
Haerri, et al. Expires August 29, 2007 [Page 16]
Internet-Draft MANET Position Signaling February 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Haerri, et al. Expires August 29, 2007 [Page 17]