draft-ietf-manet-packetbb-05.txt   draft-ietf-manet-packetbb-06.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: December 17, 2007 BAE Systems Advanced Technology Expires: December 22, 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
June 15, 2007 June 20, 2007
Generalized MANET Packet/Message Format Generalized MANET Packet/Message Format
draft-ietf-manet-packetbb-05 draft-ietf-manet-packetbb-06
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 December 17, 2007. This Internet-Draft will expire on December 22, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (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.
skipping to change at page 2, line 31 skipping to change at page 2, line 31
5.3.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.3.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3.2. Constraints . . . . . . . . . . . . . . . . . . . . . 16 5.3.2. Constraints . . . . . . . . . . . . . . . . . . . . . 16
5.4. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.4. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 16
6. TLV specification . . . . . . . . . . . . . . . . . . . . . . 17 6. TLV specification . . . . . . . . . . . . . . . . . . . . . . 17
6.1. Address Block TLV Specification . . . . . . . . . . . . . 17 6.1. Address Block TLV Specification . . . . . . . . . . . . . 17
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1. Normative References . . . . . . . . . . . . . . . . . . . 20 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20
9.2. Informative References . . . . . . . . . . . . . . . . . . 20 9.2. Informative References . . . . . . . . . . . . . . . . . . 20
Appendix A. Illustrations . . . . . . . . . . . . . . . . . . . 21 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 21
Appendix A.1. Packet . . . . . . . . . . . . . . . . . . . . . . . 21 A.1. Address Block Examples . . . . . . . . . . . . . . . . . . 21
Appendix A.2. Message and Padding . . . . . . . . . . . . . . . . 23 A.2. TLV Examples . . . . . . . . . . . . . . . . . . . . . . . 22
Appendix A.3. Message Body . . . . . . . . . . . . . . . . . . . . 29 Appendix B. Illustrations . . . . . . . . . . . . . . . . . . . 25
Appendix A.4. Address Block . . . . . . . . . . . . . . . . . . . 30 Appendix B.1. Packet . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix A.5. TLV Block . . . . . . . . . . . . . . . . . . . . . 32 Appendix B.2. Message and Padding . . . . . . . . . . . . . . . . 27
Appendix A.6. TLV . . . . . . . . . . . . . . . . . . . . . . . . 32 Appendix B.3. Message Body . . . . . . . . . . . . . . . . . . . . 33
Appendix B. Complete Example . . . . . . . . . . . . . . . . . . 35 Appendix B.4. Address Block . . . . . . . . . . . . . . . . . . . 34
Appendix C. Contributors . . . . . . . . . . . . . . . . . . . . 37 Appendix B.5. TLV Block . . . . . . . . . . . . . . . . . . . . . 36
Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 38 Appendix B.6. TLV . . . . . . . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 Appendix C. Complete Example . . . . . . . . . . . . . . . . . . 39
Intellectual Property and Copyright Statements . . . . . . . . . . 40 Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 41
Appendix E. Acknowledgements . . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43
Intellectual Property and Copyright Statements . . . . . . . . . . 44
1. Introduction 1. Introduction
This document specifies the syntax of a general purpose multi-message This document specifies the syntax of a general purpose multi-message
packet format for information exchange between MANET routers. packet format for information exchange between MANET routers.
Messages consist of a message header, which is designed for control Messages consist of a message header, which is designed for control
of message dissemination, and a message body, which contains protocol of message dissemination, and a message body, which contains protocol
information. Only the syntax of the message body is specified. All information. Only the syntax of the message body is specified. All
syntactical entities, including messages and packets, are specified syntactical entities, including messages and packets, are specified
using regular expressions. using regular expressions.
skipping to change at page 6, line 25 skipping to change at page 6, line 25
addresses, IPv4 addresses are represented as IPv4-mapped IPv6 addresses, IPv4 addresses are represented as IPv4-mapped IPv6
addresses as specified in [2]. addresses 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 in a single transmission. The packets may number of messages between in a single transmission. The packets may
use any transport mechanism (unicast, multicast) and transport be unicast or multicast and may use any transport protocol (TCP, UDP,
protocol (TCP, UDP, ...) appropriate to the protocol using this ...) appropriate to the protocol using this specification and may
specification and may travel over a single logical hop which might travel over a single logical hop which might consist of one or more
consist of one or more IP hops. When the diffusion mechanism enabled IP hops. When the diffusion mechanism enabled by this specification
by this specification is employed, UDP may be most appropriate. 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 the protocol will employ. diffusion mechanism) that the protocol will employ.
skipping to change at page 8, line 11 skipping to change at page 8, line 11
This specification does not describe a protocol. It describes a This specification does not describe a protocol. It describes a
packet format, which may be used by any mobile ad hoc network routing packet format, which may be used by any mobile ad hoc network routing
or other protocol. or other protocol.
5. Signaling Framework 5. Signaling Framework
This section provides syntactical specification of a packet, This section provides syntactical specification of a packet,
represented by the element <packet> and the elements from which it is represented by the element <packet> and the elements from which it is
composed. The specification is given in the form of regular composed. The specification is given in the form of regular
expressions. Illustrations of specified elements are given in expressions. Illustrations of specified elements are given in
Appendix A. Appendix B.
The length of a <packet> is obtained as the size of the payload of The length of a <packet> is obtained as the size of the payload of
the transport protocol employed. the transport protocol employed.
5.1. Packets 5.1. Packets
<packet> is defined by: <packet> is defined by:
<packet> = {<packet-header><pad-octet>*}? <packet> = {<packet-header><pad-octet>*}?
{<message><pad-octet>*}* {<message><pad-octet>*}*
skipping to change at page 17, line 20 skipping to change at page 17, line 20
6.1. Address Block TLV Specification 6.1. Address Block TLV Specification
+----------------------+------+--------+----------------------------+ +----------------------+------+--------+----------------------------+
| Name | Type | Length | Value | | Name | Type | Length | Value |
+----------------------+------+--------+----------------------------+ +----------------------+------+--------+----------------------------+
| PREFIX_LENGTH | 0 | 8 bits | Indicates that the address | | PREFIX_LENGTH | 0 | 8 bits | Indicates that the address |
| | | | is a network address, | | | | | is a network address, |
| | | | rather than a host | | | | | rather than a host |
| | | | address. The value is the | | | | | address. The value is the |
| | | | length of the | | | | | length of the |
| | | | prefix/netmask. | | | | | prefix/netmask, in bits. |
+----------------------+------+--------+----------------------------+ +----------------------+------+--------+----------------------------+
Table 5 Table 5
An address in an address block without an associated PREFIX_LENGTH An address in an address block without an associated PREFIX_LENGTH
TLV may be considered to have a prefix length equal to the address TLV may be considered to have a prefix length equal to the address
length in bits (i.e. address-length times 8). length in bits (i.e. address-length times 8).
7. IANA Considerations 7. IANA Considerations
skipping to change at page 18, line 48 skipping to change at page 18, line 48
initial assignments as specified in Table 7. Future values in the initial assignments as specified in Table 7. Future values in the
range 1-127 can be allocated using standards action [3]. range 1-127 can be allocated using standards action [3].
Additionally, values in the range 128-255 are reserved for private/ Additionally, values in the range 128-255 are reserved for private/
local use. local use.
+--------------------+-------+--------------------------------------+ +--------------------+-------+--------------------------------------+
| Mnemonic | Value | Description | | Mnemonic | Value | Description |
+--------------------+-------+--------------------------------------+ +--------------------+-------+--------------------------------------+
| PREFIX_LENGTH | 0 | Indicates that associated addresses | | PREFIX_LENGTH | 0 | Indicates that associated addresses |
| | | are network addresses, with given | | | | are network addresses, with given |
| | | prefix length. | | | | prefix length, in bits. |
+--------------------+-------+--------------------------------------+ +--------------------+-------+--------------------------------------+
Table 7 Table 7
8. Security Considerations 8. Security Considerations
Messages are designed to be carriers of protocol information and MAY, Messages are designed to be carriers of protocol information and MAY,
at each hop, be forwarded and/or processed according to the at each hop, be forwarded and/or processed according to the
information in the message header by the protocol using this information in the message header by the protocol using this
specification. specification.
skipping to change at page 21, line 5 skipping to change at page 21, line 5
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", October 1998. Considerations Section in RFCs", October 1998.
9.2. Informative References 9.2. Informative References
[4] Clausen, T. and P. Jacquet, "The Optimized Link State Routing [4] Clausen, T. and P. Jacquet, "The Optimized Link State Routing
Protocol", RFC 3626, October 2003. Protocol", RFC 3626, October 2003.
Appendix A. Illustrations Appendix A. Examples
This appendix contains some examples of parts of this specification.
A.1. Address Block Examples
The following examples illustrate how some combinations of addresses
may be efficiently included in address blocks. These examples are
for IPv4, with address-length equal to 4. a, b, c etc. represent
distinct, non-zero, octet values.
Note that it is permissible to use a less efficient representation,
in particular one in which the nohead and notail bits of the
semantics octet are set, and hence head-length = 0, tail-length = 0,
mid-length = address-length, and the address block consists of the
number of addresses, the semantics octet with value 3, and a list of
the uncompressed addresses. This is also the most efficient way to
represent a single address, and the only way to represent, for
example, a.b.c.d and e.f.g.h in one address block.
Examples:
o To include a.b.c.d, a.b.e.f and a.b.g.h:
* head-length = 2;
* tail-length = 0;
* mid-length = 2;
* <semantics> has notail set (value 2);
* <tail-length> and <tail> are omitted.
The address block is then 3 2 2 a b c d e f g h (11 octets).
o To include a.b.c.g and d.e.f.g:
* head-length = 0;
* tail-length = 1;
* mid-length = 3;
* <semantics> has nohead set (value 1);
* <head-length> and <head> are omitted.
The address block is then 2 1 1 g a b c d e f (10 octets).
o To include a.b.d.e and a.c.d.e:
* head-length = 1;
* tail-length = 2;
* mid-length = 1;
* <semantics> = 0.
The address block is then 2 0 1 a 2 d e b c (9 octets).
o To include a.b.0.0, a.c.0.0, and a.d.0.0:
* head-length = 1;
* tail-length = 2;
* mid-length = 1;
* <semantics> has zerotail set (value 4);
* <tail> is omitted.
The address block is then 3 4 1 a 2 b c d (8 octets).
o To include a.b.0.0 and c.d.0.0:
* head-length = 0;
* tail-length = 2;
* mid-length = 2;
* <semantics> has nohead and zerotail set (value 5);
* <head> and <tail> are omitted.
The address block is then 2 5 2 a b c d (7 octets).
A.2. TLV Examples
If network addresses a.b.0.0/16, c.d.0.0/16, c.d.e.0/24 and
c.d.e.f/32 are to be represented using a single address block
containing a.b.0.0, c.d.0.0, c.d.e.0 and c.d.e.f, with the prefix
lengths added using one or more address block TLVs of type
PREFIX_LENGTH (0), then this can be done in a number of ways.
Possible examples are:
o Using one multivalue TLV covering all of the addresses:
* <semantics> has noindex and multivalue set (value 20);
* <index-start> and <index-stop> are omitted;
* <length> = 4 (single-length = 1).
* The TLV is then 0 20 4 16 16 24 32 (7 octets).
o Using one multivalue TLV omitting the last address (a prefix
length of 32 is the default):
* <semantics> has multivalue set (value 16);
* <index-start> = 0;
* <index-stop> = 2
* <length> = 3 (single-length = 1).
* The TLV is then 0 16 0 2 3 16 16 24 (8 octets).
o Using two single value TLVs, omitting the last address. First:
* <semantics> = 0;
* <index-start> = 0;
* <index-stop> = 1;
* <length> = 1;
* <value> = 16.
* The TLV is then 0 0 0 1 1 16 (6 octets).
Second:
* <semantics> has singlevalue set (value 8);
* <index-start> = 2;
* <index-stop> is omitted;
* <length> = 1;
* <value> = 24.
* The TLV is then 0 8 2 1 24 (5 octets).
Total length of TLVs is 11 octets.
In this case the first of these is the most efficient. In other
cases patterns such as the others may be preferred. Regardless of
efficiency, any of these may be used.
Assuming the definition of an address block TLV with type EXAMPLE
which has no value (it is sufficient to simply indicate which
addresses are examples), for the same address block, with the second
and third addresses being examples, this can be indicated with a
single TLV:
o <semantics> has novalue set (value 2);
o <index-start> = 1;
o <index-stop> = 2;
o <length> and <value> are omitted.
o The TLV is then EXAMPLE 2 1 2 (4 octets).
Assuming the definition of a message TLV with type DATA which can
take a value field of any length, for such a message TLV with 8
octets of data (a to h):
o <semantics> has noindex set (value 4);
o <index-start> and <index-stop> are omitted;
o <length> = 8.
o The TLV is then DATA 4 8 a b c d e f g h (11 octets).
If, in this example, the number of data octets were 256 or greater
then <semantics> would also have extended set and have value 5. The
length would require two octets (most significant first). The TLV
length would be 4 + N octets, where N is the number of data octets
(it can be 3 + N octets if N is 255 or less).
Appendix B. Illustrations
This informative appendix illustrates the elements, which are This informative appendix illustrates the elements, which are
normatively specified in Section 5 using regular expressions. normatively specified in Section 5 using regular expressions.
Bits labeled Reserved, Resv, or Rsv are cleared ('0'). Bits labeled Bits labeled Reserved, Resv, or Rsv are cleared ('0'). Bits labeled
N and M may be cleared ('0') or set ('1'). Octets labeled Padding N and M may be cleared ('0') or set ('1'). Octets labeled Padding
are cleared ('0'), and are optional. are cleared ('0'), and are optional.
Appendix A.1. Packet Appendix B.1. Packet
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0| Reserved |0|0| Packet Sequence Number | |0 0 0 0 0 0 0 0| Reserved |0|0| Packet Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 23, line 20 skipping to change at page 27, line 20
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix A.2. Message and Padding Appendix B.2. Message and Padding
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type | Rsv |N|0|0|0|0| Message Size | | Message Type | Rsv |N|0|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number | | Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 29, line 5 skipping to change at page 33, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type | Rsv |N|1|1|1|0| Message Size | | Message Type | Rsv |N|1|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix A.3. Message Body Appendix B.3. Message Body
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message TLV Block | | Message TLV Block |
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
skipping to change at page 30, line 5 skipping to change at page 34, line 5
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Address TLV Block | | Address TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix A.4. Address Block Appendix B.4. Address Block
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Resv |0|0|0| Head Length | Head | | Number Addrs | Resv |0|0|0| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Tail | | Head (cont) | Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | | | Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
skipping to change at page 32, line 5 skipping to change at page 36, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | | | Mid (cont) | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix A.5. TLV Block Appendix B.5. TLV Block
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | | | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| TLV | | TLV |
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | | | | |
skipping to change at page 32, line 29 skipping to change at page 36, line 29
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| TLV | | TLV |
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix A.6. TLV Appendix B.6. TLV
0 1 2 3 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 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 |M|0|0|0|0| Index Start | Index Stop | | Type |Resv |M|0|0|0|0| Index Start | Index Stop |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | | | Length | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Value | | Value |
| | | |
skipping to change at page 35, line 5 skipping to change at page 39, line 5
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
0 1 2 3 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 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|1|0|1|0| Index Start | | Type |Resv |0|1|0|1|0| Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B. Complete Example Appendix C. Complete Example
An example packet, using IPv4 addresses (length four octets) is An example packet, using IPv4 addresses (length four octets) is
shown. This packet has a header, indicated by the initial octet 0. shown. This packet has a header, indicated by the initial octet 0.
The packet header has semantics octet 0, and hence has a packet The packet header has semantics octet 0, and hence has a packet
sequence number, but no packet TLV block. sequence number, but no packet TLV block.
The packet contains a single message. This message has semantics The packet contains a single message. This message has semantics
octet 0, and hence has a complete message header, including octet 0, and hence has a complete message header, including
originator address, hop limit, hop count and message sequence number originator address, hop limit, hop count and message sequence number
(which is type independent). The message has a message TLV block (which is type independent). The message has a message TLV block
skipping to change at page 37, line 5 skipping to change at page 41, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop |0 0 0 0 0 0 1 0|0 0 0 0 0 1 0 1|0 0 0 0 0 0 1 0| | Index Stop |0 0 0 0 0 0 1 0|0 0 0 0 0 1 0 1|0 0 0 0 0 0 1 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | Mid | | Mid | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1| PREFIX_LENGTH |0 0 0 1 0 1 0 0| |0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1| PREFIX_LENGTH |0 0 0 1 0 1 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 1 0| Value0 | Value1 |0 0 0 0 0 0 0 0| |0 0 0 0 0 0 1 0| Value0 | Value1 |0 0 0 0 0 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix C. Contributors Appendix D. Contributors
This specification is the result of the joint efforts of the This specification is the result of the joint efforts of the
following contributors from the OLSRv2 Design Team -- listed following contributors from the OLSRv2 Design Team -- listed
alphabetically. alphabetically.
o Cedric Adjih, INRIA, France, <Cedric.Adjih@inria.fr> o Cedric Adjih, INRIA, France, <Cedric.Adjih@inria.fr>
o Emmanuel Baccelli, Hitachi Labs Europe, France, o Emmanuel Baccelli, Hitachi Labs Europe, France,
<Emmanuel.Baccelli@inria.fr> <Emmanuel.Baccelli@inria.fr>
skipping to change at page 38, line 5 skipping to change at page 42, line 5
o Christopher Dearlove, BAE Systems, UK, o Christopher Dearlove, BAE Systems, UK,
<chris.dearlove@baesystems.com> <chris.dearlove@baesystems.com>
o Satoh Hiroki, Hitachi SDL, Japan, <h-satoh@sdl.hitachi.co.jp> o Satoh Hiroki, Hitachi SDL, Japan, <h-satoh@sdl.hitachi.co.jp>
o Philippe Jacquet, INRIA, France, <Philippe.Jacquet@inria.fr> o Philippe Jacquet, INRIA, France, <Philippe.Jacquet@inria.fr>
o Monden Kazuya, Hitachi SDL, Japan, <monden@sdl.hitachi.co.jp> o Monden Kazuya, Hitachi SDL, Japan, <monden@sdl.hitachi.co.jp>
Appendix D. Acknowledgements Appendix E. Acknowledgements
The authors would like to acknowledge the team behind OLSRv1, as The authors would like to acknowledge the team behind OLSRv1, as
specified in RFC 3626, including Anis Laouiti, Pascale Minet, Laurent specified in RFC 3626, including Anis Laouiti, Pascale Minet, Laurent
Viennot (all at INRIA, France), and Amir Qayyum (Center for Advanced Viennot (all at INRIA, France), and Amir Qayyum (Center for Advanced
Research in Engineering, Pakistan) for their contributions. Research in Engineering, Pakistan) for their contributions.
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
specification and its components: Joe Macker (NRL), Alan Cullen (BAE specification and its components: Joe Macker (NRL), Alan Cullen (BAE
Systems), Ian Chakeres (Boeing), Charlie E. Perkins (Nokia), Andreas Systems), Ian Chakeres (Boeing), Charlie E. Perkins (Nokia), Andreas
Schjonhaug (LIX), Florent Brunneau (LIX), Yasunori Owada (Niigata Schjonhaug (LIX), Florent Brunneau (LIX), Yasunori Owada (Niigata
University) and the entire IETF MANET working group. University) and the entire IETF MANET working group.
Authors' Addresses Authors' Addresses
Thomas Heide Clausen Thomas Heide Clausen
LIX, Ecole Polytechnique, France LIX, Ecole Polytechnique, France
Phone: +33 6 6058 9349 Phone: +33 6 6058 9349
Email: T.Clausen@computer.org Email: T.Clausen@computer.org
URI: http://www.lix.polytechnique.fr/Labo/Thomas.Clausen/ URI: http://www.thomasclausen.org/
Christopher M. Dearlove Christopher M. Dearlove
BAE Systems Advanced Technology Centre BAE Systems Advanced Technology Centre
Phone: +44 1245 242194 Phone: +44 1245 242194
Email: chris.dearlove@baesystems.com Email: chris.dearlove@baesystems.com
URI: http://www.baesystems.com/ocs/sharedservices/atc/ URI: http://www.baesystems.com/
Justin W. Dean Justin W. Dean
Naval Research Laboratory Naval Research Laboratory
Phone: +1 202 767 3397 Phone: +1 202 767 3397
Email: jdean@itd.nrl.navy.mil Email: jdean@itd.nrl.navy.mil
URI: http://pf.itd.nrl.navy.mil/ URI: http://pf.itd.nrl.navy.mil/
Cedric Adjih Cedric Adjih
INRIA Rocquencourt INRIA Rocquencourt
 End of changes. 21 change blocks. 
36 lines changed or deleted 228 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/