draft-ietf-manet-packetbb-03.txt   draft-ietf-manet-packetbb-04.txt 
Mobile Ad hoc Networking (MANET) T. Clausen Mobile Ad hoc Networking (MANET) T. Clausen
Internet-Draft LIX, Ecole Polytechnique, France Internet-Draft LIX, Ecole Polytechnique, France
Intended status: Standards Track C. Dearlove Intended status: Standards Track C. Dearlove
Expires: August 2, 2007 BAE Systems Advanced Technology Expires: July 5, 2007 BAE Systems Advanced Technology
Centre Centre
J. Dean J. Dean
Naval Research Laboratory Naval Research Laboratory
C. Adjih C. Adjih
INRIA Rocquencourt INRIA Rocquencourt
January 29, 2007 January 2007
Generalized MANET Packet/Message Format Generalized MANET Packet/Message Format
draft-ietf-manet-packetbb-03 draft-ietf-manet-packetbb-04
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 2, 2007. This Internet-Draft will expire on July 5, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies a multi-message packet format that may be This document specifies a multi-message packet format that may be
used by mobile ad hoc network routing and other protocols. used by mobile ad hoc network routing and other protocols.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
skipping to change at page 5, line 14 skipping to change at page 5, line 14
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. [1]. document are to be interpreted as described in RFC 2119. [1].
Additionally, this document uses the following terminology: Additionally, this document uses the following terminology:
Packet - the top level entity in this specification. Packets are Packet - the top level entity in this specification. Packets are
transmitted hop-by-hop and are not forwarded. A packet contains transmitted over a single logical hop and are not forwarded. A
zero or more messages, and may contain a packet header. packet contains zero or more messages, and may contain a packet
header.
Message - the fundamental entity carrying protocol information, in Message - the fundamental entity carrying protocol information, in
the form of addresses and TLVs. Messages are transmitted in the form of addresses and TLVs. Messages are transmitted in
packets, and may be forwarded based on their header information. packets, and may be forwarded based on their header information.
Address - an address of the same length as the source IP address in Address - an address of the same length as the source IP address in
the IP datagram carrying the packet. the IP datagram carrying the packet.
TLV - a Type-Length-Value structure. This is a generic way in which TLV - a Type-Length-Value structure. This is a generic way in which
an attribute can be represented and correctly parsed, without the an attribute can be represented and correctly parsed, without the
skipping to change at page 6, line 23 skipping to change at page 6, line 23
mind. All addresses within a control message are assumed to be of mind. All addresses within a control message are assumed to be of
the same size, deduced from IP. In the case of mixed IPv6 and IPv4 the same size, deduced from IP. In the case of mixed IPv6 and IPv4
addresses, IPv4 addresses are carried in IPv6 as specified in [2]. addresses, IPv4 addresses are carried in IPv6 as specified in [2].
The messages defined by this specification are designed to carry The messages defined by this specification are designed to carry
routing protocol signals between MANET routers, and to support scope routing protocol signals between MANET routers, and to support scope
limited diffusion, as well as point to point signaling in a multi-hop limited diffusion, as well as point to point signaling in a multi-hop
network. network.
The packets defined by this specification are designed to carry a The packets defined by this specification are designed to carry a
number of messages between neighboring nodes in a single transmission number of messages between in a single transmission. The packets may
and over a single logical hop. The packets may use any transport use any transport mechanism (unicast, multicast) and transport
mechanism (unicast, multicast) and transport protocol (TCP, UDP, ...) protocol (TCP, UDP, ...) appropriate to the protocol using this
appropriate to the protocol using this specification. When the specification and may travel over a single logical hop which might
diffusion mechanism enabled by this specification is employed, UDP consist of one or more IP hops. When the diffusion mechanism enabled
may be most appropriate. by this specification is employed, UDP may be most appropriate.
This specification is particularly appropriate for extensible This specification is particularly appropriate for extensible
protocols. It offers external extensibility in the form of new protocols. It offers external extensibility in the form of new
message types. It offers internal extensibility in the form of TLVs, message types. It offers internal extensibility in the form of TLVs,
which may be added to existing message types. which may be added to existing message types.
A protocol using the multi-message packet format defined by this A protocol using the multi-message packet format defined by this
specification may constrain the syntax (for example requiring a full specification may constrain the syntax (for example requiring a full
message header) and features (for example specifying the suggested message header) and features (for example specifying the suggested
diffusion mechanism) that it will employ. diffusion mechanism) that it will employ.
skipping to change at page 10, line 43 skipping to change at page 10, line 43
conformance with this version of the specification. conformance with this version of the specification.
<msg-size> is a 16 bit field, specifying the size of the <message>, <msg-size> is a 16 bit field, specifying the size of the <message>,
counted in octets. counted in octets.
<originator-address> is an identifier of length equal to address- <originator-address> is an identifier of length equal to address-
length, which serves to uniquely identify the node that originated length, which serves to uniquely identify the node that originated
the message. the message.
<hop-limit> is an 8 bit field, which contains the maximum number of <hop-limit> is an 8 bit field, which contains the maximum number of
hops a message should be further transmitted. logical hops a message should be further transmitted.
<hop-count> is an 8 bit field, which contains the number of hops a <hop-count> is an 8 bit field, which contains the number of logical
message has traveled. hops a message has traveled.
<msg-seq-number> is a 16 bit field, which contains a unique number, <msg-seq-number> is a 16 bit field, which contains a unique number,
generated by the originator node. The <originator-address>, <msg- generated by the originator node. The <originator-address>, <msg-
seq-number>, and, if the typedep bit in the <msg-semantics> field seq-number>, and, if the typedep bit in the <msg-semantics> field
is set, the <msg-type> of a message serves to uniquely identify is set, the <msg-type> of a message serves to uniquely identify
the message in the network. the message in the network.
5.2.1. Address Blocks 5.2.1. Address Blocks
An address is specified as a sequence of address-length octets of the An address is specified as a sequence of address-length octets of the
skipping to change at page 36, line 7 skipping to change at page 36, line 7
Cedric Adjih Cedric Adjih
INRIA Rocquencourt INRIA Rocquencourt
Phone: +33 1 3963 5215 Phone: +33 1 3963 5215
Email: Cedric.Adjih@inria.fr Email: Cedric.Adjih@inria.fr
URI: http://menetou.inria.fr/~adjih/ URI: http://menetou.inria.fr/~adjih/
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 11 change blocks. 
21 lines changed or deleted 22 lines changed or added

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