draft-ietf-manet-packetbb-09.txt   draft-ietf-manet-packetbb-10.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: March 13, 2008 BAE Systems Advanced Technology Expires: March 4, 2008 BAE Systems Advanced Technology
Centre Centre
J. Dean J. Dean
Naval Research Laboratory Naval Research Laboratory
C. Adjih C. Adjih
INRIA Rocquencourt INRIA Rocquencourt
September 10, 2007 September 2007
Generalized MANET Packet/Message Format Generalized MANET Packet/Message Format
draft-ietf-manet-packetbb-09 draft-ietf-manet-packetbb-10
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 March 13, 2008. This Internet-Draft will expire on March 4, 2008.
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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Applicability Statement . . . . . . . . . . . . . . . . . . . 6 3. Applicability Statement . . . . . . . . . . . . . . . . . . . 7
4. Protocol Overview and Functioning . . . . . . . . . . . . . . 7 4. Protocol Overview and Functioning . . . . . . . . . . . . . . 8
5. Signaling Framework . . . . . . . . . . . . . . . . . . . . . 8 5. Signaling Framework . . . . . . . . . . . . . . . . . . . . . 9
5.1. Packets . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Packets . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2.1. Address Blocks . . . . . . . . . . . . . . . . . . . . 11 5.3. Packet and Message Versioning . . . . . . . . . . . . . . 13
5.3. TLVs and TLV Blocks . . . . . . . . . . . . . . . . . . . 13 5.4. Address Blocks . . . . . . . . . . . . . . . . . . . . . . 13
5.3.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.5. TLVs and TLV Blocks . . . . . . . . . . . . . . . . . . . 15
5.3.2. Constraints . . . . . . . . . . . . . . . . . . . . . 16 5.5.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3.3. Malformed Elements . . . . . . . . . . . . . . . . . . 16 5.5.2. TLV Inclusion and Constraints . . . . . . . . . . . . 18
5.4. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.6. Malformed Elements . . . . . . . . . . . . . . . . . . . . 19
6. TLV specification . . . . . . . . . . . . . . . . . . . . . . 18 5.7. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1. Address Block TLV Specification . . . . . . . . . . . . . 18 6. TLV specification . . . . . . . . . . . . . . . . . . . . . . 21
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 6.1. Address Block TLV Specification . . . . . . . . . . . . . 21
8. Security Considerations . . . . . . . . . . . . . . . . . . . 21 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7.1. Message Types . . . . . . . . . . . . . . . . . . . . . . 22
9.1. Normative References . . . . . . . . . . . . . . . . . . . 22 7.2. Packet TLV Types . . . . . . . . . . . . . . . . . . . . . 22
9.2. Informative References . . . . . . . . . . . . . . . . . . 22 7.3. Message TLV Types . . . . . . . . . . . . . . . . . . . . 23
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 23 7.4. Address Block TLV Types . . . . . . . . . . . . . . . . . 23
A.1. Address Block Examples . . . . . . . . . . . . . . . . . . 23 8. Security Considerations . . . . . . . . . . . . . . . . . . . 25
A.2. TLV Examples . . . . . . . . . . . . . . . . . . . . . . . 24 8.1. Security Suggestions . . . . . . . . . . . . . . . . . . . 25
Appendix B. Illustrations . . . . . . . . . . . . . . . . . . . 27 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Appendix B.1. Packet . . . . . . . . . . . . . . . . . . . . . . . 27 9.1. Normative References . . . . . . . . . . . . . . . . . . . 26
Appendix B.2. Message and Padding . . . . . . . . . . . . . . . . 29 9.2. Informative References . . . . . . . . . . . . . . . . . . 26
Appendix B.3. Message Body . . . . . . . . . . . . . . . . . . . . 35 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 27
Appendix B.4. Address Block . . . . . . . . . . . . . . . . . . . 36 A.1. Address Block Examples . . . . . . . . . . . . . . . . . . 27
Appendix B.5. TLV Block . . . . . . . . . . . . . . . . . . . . . 38 A.2. TLV Examples . . . . . . . . . . . . . . . . . . . . . . . 28
Appendix B.6. TLV . . . . . . . . . . . . . . . . . . . . . . . . 38 Appendix B. Illustrations . . . . . . . . . . . . . . . . . . . 31
Appendix C. Complete Example . . . . . . . . . . . . . . . . . . 44 Appendix B.1. Packet . . . . . . . . . . . . . . . . . . . . . . . 31
Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 46 Appendix B.2. Message and Padding . . . . . . . . . . . . . . . . 36
Appendix E. Acknowledgements . . . . . . . . . . . . . . . . . . 47 Appendix B.3. Message Body . . . . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 48 Appendix B.4. Address Block . . . . . . . . . . . . . . . . . . . 43
Intellectual Property and Copyright Statements . . . . . . . . . . 49 Appendix B.5. TLV Block . . . . . . . . . . . . . . . . . . . . . 45
Appendix B.6. TLV . . . . . . . . . . . . . . . . . . . . . . . . 45
Appendix C. Complete Example . . . . . . . . . . . . . . . . . . 51
Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 53
Appendix E. Acknowledgements . . . . . . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 55
Intellectual Property and Copyright Statements . . . . . . . . . . 56
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 packet and messages is
syntactical entities, including messages and packets, are specified specified. All syntactical entities, including packets and messages,
using regular expressions. are specified using regular expressions.
This document specifies: This document specifies:
o A packet format, allowing zero or more messages to be contained o A packet format, allowing zero or more messages to be contained
within a single transmission, and optionally including a packet within a single transmission, and optionally including a packet
header. A packet with zero messages may be sent in case the only header. A packet with zero messages may be sent in case the only
information to exchange is contained in the packet header (such as information to exchange is contained in the packet header (such as
a "keep alive" sequence number). a "keep alive" sequence number).
o A message format, where a message is composed of a message header o A message format, where a message is composed of a message header
and a message body. and a message body.
o A message header format which allows a node to make forwarding o A message header format, which may allow a node to make
decisions based on the node's present state and the message praocessing and forwarding decisions based on the node's present
header, without inspecting and processing the message body, and state and the message header, without inspecting and parsing the
independently of the TTL or hop limit information in the IP message body. Message header information permits single- and
header. Message header information permits single- and multi-hop multi-hop message diffusion.
message diffusion.
o A message body format, containing attributes associated with the o A message body format, containing attributes associated with the
message or the originator of the message, as well as blocks of message or the originator of the message, as well as blocks of
addresses with associated attributes. addresses with associated attributes.
o An address block format, where an address block represents sets of o An address block format, where an address block represents sets of
addresses in a compact (compressed) form. addresses in a compact (compressed) form.
o A generalized type-length-value (TLV) format representing o A generalized type-length-value (TLV) format representing
attributes. Multiple TLVs can be included and associated with a attributes. Multiple TLVs can be included and each associated
packet, a message, an address, or a set of addresses. with a packet, a message, an address, or a set of addresses.
The specification has been explicitly designed with the following The specification has been explicitly designed with the following
properties, listed in no particular order, in mind: properties, listed in no particular order, in mind:
Parsing logic - the regular expression specification facilitates Parsing logic - the regular expression specification facilitates
generic, protocol independent, parsing logic. generic, protocol independent, parsing logic.
Extensibility - packets and messages defined by a protocol using Extensibility - packets and messages defined by a protocol using
this specification are extensible through defining new message this specification are extensible through defining new message
types and new TLVs. Existing protocol specifications using this types and new TLVs. Existing protocol specifications using this
specification will be able to correctly identify and skip such new specification will be able to correctly identify and skip such new
message types and TLVs, while correctly parsing the remainder of message types and TLVs, while correctly parsing the remainder of
the packet and message. the packet and message.
Efficiency - when reported addresses share common bit sequences Efficiency - when reported addresses share common bit sequences
(e.g. prefixes or IPv6 interface identifiers) the address block (e.g. prefixes or IPv6 interface identifiers) the address block
representation allows for a compact representation. Compact representation allows for a compact representation. Compact
message headers are ensured through permitting inclusion of only message headers are ensured through permitting inclusion of only
required message header elements. required message header elements, unless indicated otherwise. The
structure of packet and message encoding allows parsing,
verifying, and identifying individual elements in a single linear
pass.
Separation of forwarding and processing - duplicate detection and Separation of forwarding and processing - duplicate detection and
controlled scope message forwarding decisions can be made using controlled scope message forwarding decisions can be made using
information contained in the message header, without processing information contained in the message header, without processing
the message body. the message body.
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
skipping to change at page 6, line 12 skipping to change at page 7, line 12
address-length - a variable whose value is the length of an address address-length - a variable whose value is the length of an address
in octets, it is 4 if using IPv4, 16 if using IPv6. in octets, it is 4 if using IPv4, 16 if using IPv6.
3. Applicability Statement 3. Applicability Statement
This specification describes a generic multi-message packet format, This specification describes a generic multi-message packet format,
for carrying MANET routing protocol signals. The specification has for carrying MANET routing protocol signals. The specification has
been developed from that used by OLSR (The Optimized Link State been developed from that used by OLSR (The Optimized Link State
Routing Protocol) [4]. Routing Protocol) [4].
The specification is designed specifically with IP (IPv4/IPv6) in The specification is designed with IP (IPv4/IPv6) in mind. All
mind. All addresses within a control message are assumed to be of addresses within a control message are assumed to be of the same
the same size, deduced from IP. In the case of mixed IPv6 and IPv4 size, deduced from IP. In the case of mixed IPv6 and IPv4 addresses,
addresses, IPv4 addresses are represented as IPv4-mapped IPv6 IPv4 addresses are represented as IPv4-mapped IPv6 addresses as
addresses as specified in [2]. 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 in a single transmission. The packets may be number of messages in a single transmission. The packets may be
unicast or multicast and may use any transport protocol (TCP, UDP, unicast or multicast, may be transmitted as appropriate to the
...) appropriate to the protocol using this specification and may protocol using this specification and may travel over a single
travel over a single logical hop which might consist of one or more logical hop which might consist of one or more IP hops.
IP hops.
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
message header) and features (for example specifying the suggested specific set of message header fields) and features (for example
diffusion mechanism) that the protocol will employ. specifying the suggested diffusion mechanism) that the protocol will
employ.
4. Protocol Overview and Functioning 4. Protocol Overview and Functioning
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 B. Appendix B.
The length of a <packet> is obtained as the size of the payload of
the transport protocol employed.
5.1. Packets 5.1. Packets
<packet> is defined by: <packet> is defined by:
<packet> = {<packet-header><pad-octet>*}? <packet> = {<pkt-header><pad-octet>*}?
{<message><pad-octet>*}* {<message><pad-octet>*}*
where <message> is defined in Section 5.2, and <pad-octet> is defined where <message> is defined in Section 5.2, and <pad-octet> is defined
in Section 5.4. Successful parsing is terminated when all octets are in Section 5.7. Successful parsing is terminated when all octets
used. (defined using the variable pkt-size below) are used. A packet MUST
contain either a <pkt-header> or at least one <message>.
<packet-header> is defined by: <pkt-header> is defined by:
<packet-header> = <zero> <pkt-header> = <zero>
<packet-semantics> <pkt-semantics>
<packet-seq-number>? <pkt-version>?
<pkt-size>?
<pkt-seq-num>?
<tlv-block>? <tlv-block>?
where: where:
<zero> is an 8 bit field with all bits cleared ('0'). This field <zero> is an 8 bit field with all bits cleared ('0'). This field
serves to identify that the packet starts with a packet header. serves to identify that the packet starts with a <pkt-header>.
<packet-semantics> is an 8 bit field, specifying the composition of <pkt-semantics> is an 8 bit field, specifying the composition of the
the packet header: <pkt-header>:
bit 0 (pnoseqnum): if cleared ('0'), then the packet header bit 0 (phasversion): If cleared ('0'), then <pkt-version> is not
contains a <packet-seq-number>. If set ('1'), then the packet included in the <pkt-header>. If set ('1'), then <pkt-version>
header does not include a <packet-seq-number>. is included in the <pkt-header>.
bit 1 (ptlv): if cleared ('0'), then the packet header does not bit 1 (phassize): if cleared ('0'), then <pkt-size> is not
include a TLV block. If set ('1'), then the packet header included in the <pkt-header>. if set ('1'), then <pkt-size> is
includes a TLV block. included in the <pkt-header>.
bits 2-7: are RESERVED, and MUST each be cleared ('0') to be in bit 2 (pnoseqnum): if cleared ('0'), then <pkt-seq-num> is
included in the <pkt-header>. If set ('1'), then <pkt-seq-num>
is not included in the <pkt-header>.
bit 3 (phastlv): if cleared ('0'), then <tlv-block> is not
included in the <pkt-header>. If set ('1'), then <tlv-block>
is included in the <pkt-header>.
bits 4-7: are RESERVED, and MUST each be cleared ('0') to be in
conformance with this version of the specification. conformance with this version of the specification.
<packet-seq-number> is omitted if the pnoseqnum bit is set ('1'), <pkt-version> is omitted if the phasversion bit is cleared ('0'),
otherwise is an 8 bit field, specifying the version of this
specification.
<pkt-size> is omitted if the phassize bit is cleared ('0'),
otherwise is a 16 bit field, specifying the size of the <packet>
counted in octets.
<pkt-seq-num> is omitted if the pnoseqnum bit is set ('1'),
otherwise is a 16 bit field, specifying a packet sequence number. otherwise is a 16 bit field, specifying a packet sequence number.
<tlv-block> is omitted if the ptlv bit is cleared ('0'), and is <tlv-block> is omitted if the phastlv bit is cleared ('0'), and is
otherwise defined in Section 5.3. otherwise as defined in Section 5.5.
Note that since the message type zero is reserved (see Section 7), Note that since the message type zero is not used (see Section 7),
the presence or absence of a packet header can be determined by the presence or absence of a packet header can be determined by
inspecting the first octet of the packet. inspecting the first octet of the packet.
pkt-version is a variable, defined to equal <pkt-version> if
present, or 0 otherwise. See Section 5.3.
pkt-size is a variable, defined to equal <pkt-size> if present, or
the size of the payload of the transport protocol employed
otherwise.
5.2. Messages 5.2. Messages
Information is carried through messages. Messages contain: Information is carried through messages. Messages contain:
o A message header. o A message header.
o A message TLV block that contains zero or more TLVs, associated o A message TLV block that contains zero or more TLVs, associated
with the whole message. with the whole message.
o Zero or more address blocks, each containing one or more o Zero or more address blocks, each containing one or more
skipping to change at page 9, line 41 skipping to change at page 11, line 16
block. block.
<message> is defined by: <message> is defined by:
<message> = <msg-header> <message> = <msg-header>
<tlv-block> <tlv-block>
{<addr-block><tlv-block>}* {<addr-block><tlv-block>}*
<msg-header> = <msg-type> <msg-header> = <msg-type>
<msg-semantics> <msg-semantics>
<msg-size> <msg-version>?
<msg-header-info> <msg-size>?
<msg-orig-addr>?
<msg-header-info> = <originator-address>? <msg-hop-limit>?
<hop-limit>? <msg-hop-count>?
<hop-count>? <msg-seq-num>?
<msg-seq-number>?
where: where:
<tlv-block> is defined in Section 5.3. <tlv-block> is as defined in Section 5.5.
<addr-block> is defined in Section 5.2.1. <addr-block> is as defined in Section 5.4.
<msg-type> is an 8 bit field, specifying the type of message. A <msg-type> is an 8 bit field, specifying the type of message. A
type with all bits cleared ('0') MUST NOT be used. type with all bits cleared ('0') MUST NOT be used.
<msg-semantics> is an 8 bit field, specifying the interpretation of <msg-semantics> is an 8 bit field, specifying the interpretation of
the remainder of the message header: the remainder of the message header:
bit 0 (noorig): If cleared ('0'), then <originator-address> is bit 0 (mhasversion): If cleared ('0'), then <msg-version> is not
included in the <msg-header-info>. If set ('1'), then included in the <msg-header>. If set ('1'), then <msg-version>
<originator-address> is not included in the <msg-header-info>. is included in the <msg-header>.
bit 1 (nohoplimit): If cleared ('0'), then <hop-limit> is bit 1 (mnoorig): If cleared ('0'), then <msg-orig-addr> is
included in the <msg-header-info>. If set ('1'), then <hop- included in the <msg-header>. If set ('1'), then <msg-orig-
limit> is not included in the <msg-header-info>. addr> is not included in the <msg-header>.
bit 2 (nohopcount): If cleared ('0'), then <hop-count> is bit 2 (mnohoplimit): If cleared ('0'), then <msg-hop-limit> is
included in the <msg-header-info>. If set ('1'), then <hop- included in the <msg-header>. If set ('1'), then <msg-hop-
count> is not included in the <msg-header-info> limit> is not included in the <msg-header>.
bit 3 (noseqnum): If cleared ('0'), then <msg-seq-number> is bit 3 (mnohopcount): If cleared ('0'), then <msg-hop-count> is
included in the <msg-header-info>. If set ('1'), then <msg- included in the <msg-header>. If set ('1'), then <msg-hop-
seq-number> is not included in the <msg-header-info>. count> is not included in the <msg-header>
bit 4 (mnoseqnum): If cleared ('0'), then <msg-seq-num> is
included in the <msg-header>. If set ('1'), then <msg-seq-num>
is not included in the <msg-header>.
bit 4 (typedep): If cleared ('0'), then the message sequence bit 5 (mistypedep): If cleared ('0'), then the message sequence
number in the message is type-independent. If set ('1'), then number in the message is type-independent. If set ('1'), then
the message sequence number contained in the message is type the message sequence number contained in the message is type
dependent (the message originator maintains a sequence number dependent (the message originator maintains a sequence number
specific to <msg-type>). This bit MUST be cleared ('0') if the specific to <msg-type>). This bit MUST be cleared ('0') if the
noorig bit is set ('1'). mnoorig bit is set ('1').
bits 5-7: are RESERVED and MUST each be cleared ('0') to be in bits 6-7: are RESERVED and MUST each be cleared ('0') to be in
conformance with this version of the specification. conformance with this version of the specification.
If bit 0 (noorig) and bit 3 (noseqnum) are both cleared, then the If bit 1 (mnoorig) and bit 4 (mnoseqnum) are both cleared, then
message header provides for duplicate suppression. the message header provides for duplicate suppression.
If bit 1 (nohoplimit) is cleared, then the message header provides If bit 2 (mnohoplimit) is cleared, then the message header
for scope-delimited forwarding. provides for scope-delimited forwarding.
<msg-version> is omitted if the mhasversion bit is cleared ('0'),
otherwise is an 8 bit field, specifying the version of this
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- <msg-orig-addr> is omitted if the mnoorig bit is set ('1'),
length, which serves to uniquely identify the node that originated otherwise is an identifier of length equal to address-length,
the message. which serves to uniquely identify the node that originated the
message.
<hop-limit> is an 8 bit field, which contains the maximum number of <msg-hop-limit> is omitted if the mnohoplimit bit is set ('1'),
logical hops a message should be further transmitted. otherwise is an 8 bit field, which contains the maximum number of
logical hops that the message should be further transmitted.
<hop-count> is an 8 bit field, which contains the number of logical <msg-hop-count> is omitted if the mnohopcount bit is set ('1'),
hops a message has traveled. otherwise is an 8 bit field, which contains the number of logical
hops that the message has traveled.
<msg-seq-number> is a 16 bit field, which contains a unique number, <msg-seq-num> is omitted if the mnoseqnum bit is set ('1'),
generated by the originator node. The <originator-address>, <msg- otherwise is a 16 bit field, which contains a unique number,
seq-number>, and, if the typedep bit in the <msg-semantics> field generated by the message's originator node. The <msg-orig-addr>,
is set, the <msg-type> of a message serves to uniquely identify <msg-seq-num>, and, if the mistypedep bit in the <msg-semantics>
the message in the network (within the time period until <msg-seq- field is set, the <msg-type> of a message serves to uniquely
number> wraps around to a matching value). identify the message in the network (within the time period until
<msg-seq-num> wraps around to a matching value).
5.2.1. Address Blocks msg-version is a variable, defined to equal <msg-version> if
present, or to pkt-version otherwise. See Section 5.3.
5.3. Packet and Message Versioning
This specification defines packets and messages of version 0 (zero),
so that pkt-version and each msg-version MUST equal zero. This
SHOULD be indicated by clearing the phasversion and mhasversion bits
in <pkt-semantics> and <msg-semantics>, respectively.
A protocol using this specification, or any future version (i.e.
where pkt-version or msg-version are different from zero) of this
specification MUST specify appropriate behavior in the case where an
incoming packet or message indicates a pkt-version or msg-version
different from the one used by that protocol, e.g. by discarding the
packet or message.
5.4. 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
form head:mid:tail. An address block is an ordered set of addresses form head:mid:tail. An address block is an ordered set of addresses
sharing the same head and tail, and having individual mids. Network sharing the same head and tail, and having individual mids. Network
addresses may be represented using the PREFIX_LENGTH TLV defined in addresses may be represented using the PREFIX_LENGTH TLV defined in
Section 6. Section 6.
<address block> is defined by: <address-block> is defined by:
<address-block> = <num-addr> <address-block> = <num-addr>
<addr-semantics> <addr-semantics>
<head-length>? <head-length>?
<head>? <head>?
<tail-length>? <tail-length>?
<tail>? <tail>?
<mid>* <mid>*
where: where:
<num-addr> is an 8 bit field containing the number of addresses <num-addr> is an 8 bit field containing the number of addresses
represented in the address block, which MUST NOT be zero. represented in the address block, which MUST NOT be zero.
<addr-semantics> is an 8 bit field specifying the interpretation of <addr-semantics> is an 8 bit field specifying the interpretation of
the remainder of the address block: the remainder of the address block:
bit 0 (nohead): if cleared ('0'), then <head-length> is included bit 0 (anohead): if cleared ('0'), then <head-length> is included
in <address-block>, and <head> may be included in <address- in the <address-block>, and <head> may be included in the
block>. If set ('1'), then <head-length> and <head> are not <address-block>. If set ('1'), then <head-length> and <head>
included in <address-block>. are not included in the <address-block>.
bit 1 (notail) and bit 2 (zerotail): MUST NOT both be set ('1'). bit 1 (anotail) and bit 2 (ahaszerotail): MUST NOT both be set
Otherwise, they are interpreted according to Table 1. ('1'). Otherwise, they are interpreted according to Table 1.
+--------+----------+---------------+-----------------+ +---------+--------------+---------------+-----------------+
| notail | zerotail | <tail-length> | <tail> | | anotail | ahaszerotail | <tail-length> | <tail> |
+--------+----------+---------------+-----------------+ +---------+--------------+---------------+-----------------+
| 0 | 0 | included | may be included | | 0 | 0 | included | may be included |
| | | | | | | | | |
| 0 | 1 | included | not included | | 0 | 1 | included | not included |
| | | | | | | | | |
| 1 | 0 | not included | not included | | 1 | 0 | not included | not included |
+--------+----------+---------------+-----------------+ +---------+--------------+---------------+-----------------+
Table 1 Table 1
bits 3-7: are RESERVED and MUST each be cleared ('0') to be in bits 3-7: are RESERVED and MUST each be cleared ('0') to be in
accordance with this version of the specification. accordance with this version of the specification.
<head-length> if present is an 8 bit field, which contains the total <head-length> if present is an 8 bit field, which contains the total
length (in octets) of the head of all of the addresses. length (in octets) of the head of all of the addresses.
head-length is a variable, defined to equal <head-length> if head-length is a variable, defined to equal <head-length> if
skipping to change at page 12, line 38 skipping to change at page 14, line 38
<head> is omitted if head-length == 0, otherwise it is a field of <head> is omitted if head-length == 0, otherwise it is a field of
the head-length leftmost octets of all the addresses. the head-length leftmost octets of all the addresses.
<tail-length> if present is an 8 bit field, which contains the total <tail-length> if present is an 8 bit field, which contains the total
length (in octets) of the tail of all of the addresses. length (in octets) of the tail of all of the addresses.
tail-length is a variable, defined to equal <tail-length> if tail-length is a variable, defined to equal <tail-length> if
present, or 0 otherwise. present, or 0 otherwise.
<tail> is omitted if tail-length == 0 or if the zerotail bit is set <tail> is omitted if tail-length == 0 or if the ahaszerotail bit is
('1'), otherwise it is a field of the tail-length rightmost octets set ('1'), otherwise it is a field of the tail-length rightmost
of all the addresses. If the zerotail bit is set ('1') then the octets of all the addresses. If the ahaszerotail bit is set ('1')
tail-length rightmost octets of all the addresses are all 0. then the tail-length rightmost octets of all the addresses are all
0.
mid-length is a variable, which MUST be non-negative, defined by: mid-length is a variable, which MUST be non-negative, defined by:
* mid-length = address-length - head-length - tail-length * mid-length = address-length - head-length - tail-length
<mid> is omitted if mid-length == 0, otherwise each <mid> is a field <mid> is omitted if mid-length == 0, otherwise each <mid> is a field
of length mid-length octets, representing the mid of the of length mid-length octets, representing the mid of the
corresponding address in the address block. corresponding address in the address block.
5.3. TLVs and TLV Blocks 5.5. TLVs and TLV Blocks
A TLV block is defined by: A TLV block is defined by:
<tlv-block> = <tlvs-length> <tlv-block> = <tlvs-length>
<tlv>* <tlv>*
where: where:
<tlvs-length> is a 16 bit field, which contains the total length (in <tlvs-length> is a 16 bit field, which contains the total length (in
octets) of all of the immediately following <tlv> elements. octets) of all of the immediately following <tlv> elements.
<tlv> is defined in Section 5.3.1. <tlv> is as defined in Section 5.5.1.
5.3.1. TLVs 5.5.1. TLVs
There are three kinds of TLV, each represented by an element <tlv>: There are three kinds of TLV, each represented by an element <tlv>:
o A packet TLV, included in a packet header. o A packet TLV, included in a packet header.
o A message TLV, included in a message before all address blocks. o A message TLV, included in a message before all address blocks.
o An address block TLV, included in a TLV block following an address o An address block TLV, included in a TLV block following an address
block. An address block TLV applies to: block. An address block TLV applies to:
* all addresses in the address block; OR * all addresses in the address block; OR
* any continuous sequence of addresses in the address block; OR * any continuous sequence of addresses in the address block; OR
* a single address in the address block. * a single address in the address block.
<tlv> is defined by: <tlv> is defined by:
<tlv> = <tlv-type> <tlv> = <tlv-type>
<tlv-semantics> <tlv-semantics>
<tlv-subtype>? <tlv-type-ext>?
<index-start>? <index-start>?
<index-stop>? <index-stop>?
<length>? <length>?
<value>? <value>?
where: where:
<tlv-type> is an 8 bit field, specifying the type of the TLV, <tlv-type> is an 8 bit field, specifying the type of the TLV,
specific to the TLV kind (i.e. packet, message, or address block specific to the TLV kind (i.e. packet, message, or address block
TLV). TLV).
<tlv-semantics> is an 8 bit field specifying the interpretation of <tlv-semantics> is an 8 bit field specifying the interpretation of
the remainder of the TLV: the remainder of the TLV:
bit 0 (hassubtype): if cleared ('0'), then <tlv-subtype> is not bit 0 (thastypeext): if cleared ('0'), then <tlv-type-ext> is not
included in the <tlv>. If set ('1'), then <tlv-subtype> is included in the <tlv>. If set ('1'), then <tlv-type-ext> is
included in the <tlv>. included in the <tlv>.
bit 1 (extended) and bit 2 (novalue): MUST NOT both be set ('1'). bit 1 (tisextended) and bit 2 (tnovalue): MUST NOT both be set
Otherwise, they are interpreted according to Table 2. ('1'). Otherwise, they are interpreted according to Table 2.
+----------+---------+--------------+--------------+ +-------------+----------+--------------+--------------+
| extended | novalue | <length> | <value> | | tisextended | tnovalue | <length> | <value> |
+----------+---------+--------------+--------------+ +-------------+----------+--------------+--------------+
| 0 | 0 | 8 bits | included | | 0 | 0 | 8 bits | included |
| | | | | | | | | |
| 0 | 1 | not included | not included | | 0 | 1 | not included | not included |
| | | | | | | | | |
| 1 | 0 | 16 bits | included | | 1 | 0 | 16 bits | included |
+----------+---------+--------------+--------------+ +-------------+----------+--------------+--------------+
Table 2 Table 2
bit 3 (noindex) and bit 4 (singleindex): MUST NOT both be set bit 3 (tnoindex) and bit 4 (thassingleindex): MUST NOT both be
('1'). The former MUST be set ('1') and the latter MUST be set ('1'). The former MUST be set ('1') and the latter MUST be
cleared ('0') for packet or message TLVs. They are interpreted cleared ('0') for packet or message TLVs. They are interpreted
according to Table 3. according to Table 3.
+---------+-------------+---------------+--------------+ +----------+-----------------+---------------+--------------+
| noindex | singleindex | <index-start> | <index-stop> | | tnoindex | thassingleindex | <index-start> | <index-stop> |
+---------+-------------+---------------+--------------+ +----------+-----------------+---------------+--------------+
| 0 | 0 | included | included | | 0 | 0 | included | included |
| | | | | | | | | |
| 0 | 1 | included | not included | | 0 | 1 | included | not included |
| | | | | | | | | |
| 1 | 0 | not included | not included | | 1 | 0 | not included | not included |
+---------+-------------+---------------+--------------+ +----------+-----------------+---------------+--------------+
Table 3 Table 3
bit 5 (multivalue): this bit serves to specify how the <value> bit 5 (tismultivalue): this bit serves to specify how the <value>
field is interpreted, as specified below. This bit MUST be field is interpreted, as specified below. This bit MUST be
cleared ('0') for packet or message TLVs, if the singleindex cleared ('0') for packet or message TLVs, if the
bit is set ('1'), or if the novalue bit is set ('1'). thassingleindex bit is set ('1'), or if the tnovalue bit is set
('1').
bits 6-7: are RESERVED and MUST each be cleared ('0') to be in bits 6-7: are RESERVED and MUST each be cleared ('0') to be in
accordance with this version of the specification. accordance with this version of the specification.
<tlv-subtype> is an 8 bit field, specifying the subtype of the TLV, <tlv-type-ext> is an 8 bit field, specifying an extension of the TLV
specific to the TLV type and kind (i.e. packet, message, or type, specific to the TLV type and kind (i.e. packet, message, or
address block TLV). address block TLV).
tlv-subtype is a variable, defined to equal <tlv-subtype> if tlv-type-ext is a variable, defined to equal <tlv-type-ext> if
present, or 0 otherwise. present, or 0 otherwise.
tlv-fulltype is a variable, defined by: tlv-fulltype is a variable, defined by:
* tlv-fulltype = 256 * <tlv-type> + tlv-subtype; * tlv-fulltype = 256 * <tlv-type> + tlv-type-ext;
<index-start> and <index-stop> when present are each an 8 bit field, <index-start> and <index-stop> when present are each an 8 bit field,
interpreted as follows. interpreted as follows.
index-start and index-stop are variables, defined according to index-start and index-stop are variables, defined according to
Table 4. The variable end-index is defined as follows: Table 4. The variable end-index is defined as follows:
* For message and packet TLVs: * For message and packet TLVs:
+ end-index = 0 + end-index = 0
* For address block TLVs: * For address block TLVs:
+ end-index = <num-addr> - 1 + end-index = <num-addr> - 1
+---------+-------------+---------------+---------------+ +----------+-----------------+---------------+---------------+
| noindex | singleindex | index-start = | index-stop = | | tnoindex | thassingleindex | index-start = | index-stop = |
+---------+-------------+---------------+---------------+ +----------+-----------------+---------------+---------------+
| 0 | 0 | <index-start> | <index-stop> | | 0 | 0 | <index-start> | <index-stop> |
| | | | | | | | | |
| 0 | 1 | <index-start> | <index-start> | | 0 | 1 | <index-start> | <index-start> |
| | | | | | | | | |
| 1 | 0 | 0 | end-index | | 1 | 0 | 0 | end-index |
+---------+-------------+---------------+---------------+ +----------+-----------------+---------------+---------------+
Table 4 Table 4
For an address block TLV, the TLV applies to the addresses from For an address block TLV, the TLV applies to the addresses from
position index-start to position index-stop (inclusive) in the position index-start to position index-stop (inclusive) in the
address block, where the first address has position zero. address block, where the first address has position zero.
number-values is a variable, defined by: number-values is a variable, defined by:
* number-values = index-stop - index-start + 1 * number-values = index-stop - index-start + 1
<length> is omitted or is a 8 or 16 bit field according to Table 2. <length> is omitted or is an 8 or 16 bit field according to Table 2.
If the multivalue bit is set ('1') then <length> MUST be an If the tismultivalue bit is set ('1') then <length> MUST be an
integral multiple of number-values, and the variable single-length integral multiple of number-values, and the variable single-length
is defined by: is defined by:
* single-length = <length> / number-values * single-length = <length> / number-values
If the multivalue bit is cleared ('0'), then the variable single- If the tismultivalue bit is cleared ('0'), then the variable
length is defined by: single-length is defined by:
* single-length = <length> * single-length = <length>
<value> if present (see Table 2) is a field of length <length> <value> if present (see Table 2) is a field of length <length>
octets. In an address block TLV, <value> is associated with the octets. In an address block TLV, <value> is associated with the
addresses from index-start to index-stop, inclusive. If the addresses from index-start to index-stop, inclusive. If the
multivalue bit is cleared ('0') then the whole of this field is tismultivalue bit is cleared ('0') then the whole of this field is
associated with each of the indicated addresses. If the associated with each of the indicated addresses. If the
multivalue bit is set ('1') then this field is divided equally tismultivalue bit is set ('1') then this field is divided equally
into number-values fields, each of length single-length octets and into number-values fields, each of length single-length octets and
these are associated, in order, with the indicated addresses. these are associated, in order, with the indicated addresses.
5.3.2. Constraints 5.5.2. TLV Inclusion and Constraints
TLVs in the same TLV block MUST be sorted in non-descending tlv- TLVs associates attributes to entities, where entities are individual
addresses in an address block, ranges of addresses in an address
block, messages or packets. Inclusion of a TLV serves to associate
an attribute to a given entity; the processing of this attribute and
the relationship (e.g. interpretation, order of processing) between
multiple different attributes associated to the same entity is to be
defined by the protocol which uses this specification.
The following constraints on TLV ordering MUST be respected:
o TLVs in the same TLV block MUST be sorted in non-descending tlv-
fulltype order. fulltype order.
Packet and message TLVs MUST be defined so as to indicate whether two o Packet and message TLVs MUST be defined so as to indicate whether
TLVs with the same tlv-fulltype are, or are not, allowed in the same two TLVs with the same tlv-fulltype are, or are not, allowed in
packet or message TLV block, respectively. the same packet or message TLV block, respectively.
Two or more TLVs with the same tlv-fulltype in the same address block o Two or more TLVs with the same tlv-fulltype in the same address
TLV block MUST NOT be associated with the same copy of an address block TLV block MUST NOT be associated with the same copy of an
(i.e. they must not have overlapping index ranges). address (i.e. they must not have overlapping index ranges).
TLVs with the same tlv-fulltype associated with the same address o TLVs with the same tlv-fulltype associated with the same address
block MUST be sorted in ascending index-start order. block MUST be sorted in ascending index-start order.
5.3.3. Malformed Elements Note that the above constrains only the encoding of TLVs in a TLV
block for transmission, and do specifically NOT mandate any given
order of processing or interpretation by a protocol of the TLVs and
the entities to which these are associated.
Respecting the constraints above allows parsing and verification of a
TLV block in a single linear pass and allows terminating the search
for a TLV with a specific type without traversing the entire TLV
block.
The constraints on address block TLVs, which may apply to ranges of
addresses, ensure that encoded information (entity-attributes) can be
unambiguously decoded, and that verification of such is a linear
operation.
5.6. Malformed Elements
An element is malformed if it cannot be parsed according to its An element is malformed if it cannot be parsed according to its
syntatical specification (including if there are insufficient octets syntactical specification (including if there are insufficient octets
available when a length is specified) or if a constraint (including, available when a length is specified, in particular if there are
but not only, those specified in Section 5.3.2) specified as one fewer than pkt-size octets overall) or if a constraint (including,
but not only, those specified in Section 5.5.2) specified as one
which MUST be satisfied, is not. A protocol using this specification which MUST be satisfied, is not. A protocol using this specification
MUST specify the action, or choice of actions, to be taken when a MUST specify the action, or choice of actions, to be taken when a
packet containing such elements is received. Typical examples will packet containing such elements is received. Typical examples will
include discarding any affected message(s), or discarding the include discarding any affected message(s), or discarding the
complete packet. complete packet.
5.4. Padding 5.7. Padding
Packet headers and messages MAY be padded to ensure 32 bit alignment Packet headers and messages MAY be padded to ensure 32 bit alignment
of each message contained within the packet and of the overall packet of each message contained within the packet and of the overall packet
length. Padding MAY also be used to ensure that all packets/messages length. Padding MAY also be used to ensure that all packets and/or
have the same size. messages have the same size.
All elements are an integer multiple of octets, hence padding can be All elements are an integer multiple of octets, hence padding can be
accomplished by inserting an integer number of <pad-octet> elements accomplished by inserting an integer number of <pad-octet> elements
after the element that is to be 32 bit aligned. after the element that is to be 32 bit aligned.
The number of <pad-octet> elements required to achieve this 32 bit The number of <pad-octet> elements required to achieve this 32 bit
alignment is the smallest number (0 to 3) that, when added to the alignment is the smallest number (0 to 3) that, when added to the
size of the preceding elements, produces an integer multiple of 4. size of the preceding elements, produces an integer multiple of 4.
<pad-octet> is an 8 bit field with all bits cleared ('0'). <pad-octet> is an 8 bit field with all bits cleared ('0').
skipping to change at page 18, line 12 skipping to change at page 21, line 12
The padding after a message may be freely changed when a message is The padding after a message may be freely changed when a message is
forwarded without affecting the message. forwarded without affecting the message.
6. TLV specification 6. TLV specification
This document specifies one address block TLV, which is included to This document specifies one address block TLV, which is included to
allow a standardized way of representing network addresses. allow a standardized way of representing network addresses.
6.1. Address Block TLV Specification 6.1. Address Block TLV Specification
+---------------+------+---------+--------+-------------------------+ +---------------+------+-----------+--------+-----------------------+
| Name | Type | Subtype | Length | Value | | Name | Type | Type | Length | Value |
+---------------+------+---------+--------+-------------------------+ | | | extension | | |
+---------------+------+-----------+--------+-----------------------+
| PREFIX_LENGTH | 0 | 0 | 8 bits | Indicates that the | | PREFIX_LENGTH | 0 | 0 | 8 bits | Indicates that the |
| | | | | address is a network | | | | | | address is a network |
| | | | | address, rather than a | | | | | | address, rather than |
| | | | | host address. The | | | | | | a host address. The |
| | | | | value is the length of | | | | | | value is the length |
| | | | | the prefix/netmask, in | | | | | | of the |
| | | | | prefix/netmask, in |
| | | | | bits. | | | | | | 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. 8 * address-length). length in bits (i.e. 8 * address-length).
7. IANA Considerations 7. IANA Considerations
7.1. Message Types
A new registry for message types must be created with initial A new registry for message types must be created with initial
assignments as specified in Table 6. Future values in the range assignments as specified in Table 6. Future values in the range
5-127 can be allocated using standards action [3]. Additionally, 5-127 can be allocated using standards action [3]. Additionally,
values in the range 128-255 are reserved for private/local use. values in the range 128-255 are reserved for private/local use.
+------+------------------------+ +------+------------------------+
| Type | Description | | Type | Description |
+------+------------------------+ +------+------------------------+
| 0 | MUST NOT be allocated. | | 0 | MUST NOT be allocated. |
| | | | | |
| 1-4 | RESERVED | | 1-4 | RESERVED |
+------+------------------------+ +------+------------------------+
Table 6 Table 6
Message type 0 MUST NOT be allocated because a zero-octet signifies a Message type 0 MUST NOT be allocated because a zero-octet signifies a
packet header and zero-octets are used for padding. Message types 1 packet header and zero-octets are used for padding. Message types 1
to 4 are reserved because they are used by OLSR [4], which uses a to 4 are reserved because they are used by OLSR [4], which uses a
compatible packet/message header format. compatible packet/message header format.
7.2. Packet TLV Types
A new registry for packet TLV types must be created, with no initial A new registry for packet TLV types must be created, with no initial
assignments. Future values in the range 0-127 can be allocated using assignments.
standards action [3]. Additionally, values in the range 128-255 are
reserved for private/local use. If a packet TLV type is allocated Future values in the range 0-127 can be allocated using standards
then a new registry for subtypes of that type must be created. A action [3], respecting the following guidelines:
document which defines a packet TLV type MUST also specify the
mechanism by which its subtypes are allocated, from among those in values 0-7 - MUST NOT be assigned except when a documented need
[3]. exists that TLVs of a given type are required to appear before all
other TLVs in the TLV block as encoded for transmission. Note
that the need for a TLV to be processed before other TLVs does not
however automatically translate into a need for the TLV to appear
before all other TLVs in the TLV block - the order in which TLVs
are to be processed MUST be defined, if applicable, in the
protocols using this specification.
values 8-127 - no constraints.
Additionally, values in the range 128-255 are reserved for private/
local use. If a packet TLV type is allocated then a new registry for
type extensions of that type must be created. A document which
defines a packet TLV type MUST also specify the mechanism by which
its type extensions are allocated, from among those in [3].
7.3. Message TLV Types
A new registry for message TLV types must be created with no initial A new registry for message TLV types must be created with no initial
assignments. Future values in the range 0-127 can be allocated using assignments.
standards action [3]. Additionally, values in the range 128-255 are
reserved for private/local use. If a message TLV type is allocated Future values in the range 0-127 can be allocated using standards
then a new registry for subtypes of that type must be created. A action [3], respecting the following guidelines:
document which defines a message TLV type MUST also specify the
mechanism by which its subtypes are allocated, from among those in values 0-7 - MUST NOT be assigned except when a documented need
[3]. exists that TLVs of a given type are required to appear before all
other TLVs in the TLV block as encoded for transmission. Note
that the need for a TLV to be processed before other TLVs does not
however automatically translate into a need for the TLV to appear
before all other TLVs in the TLV block - the order in which TLVs
are to be processed MUST be defined, if applicable, in the
protocols using this specification.
values 8-127 - no constraints.
A new registry for address block TLV types must be created with
initial assignments as specified in Table 7. Future values in the
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. If an address block TLV type is allocated then a new local use. If a message TLV type is allocated then a new registry
registry for subtypes of that type must be created. A document which for type extensions of that type must be created. A document which
defines an address block TLV type MUST also specify the mechanism by defines a message TLV type MUST also specify the mechanism by which
which its subtypes are allocated, from among those in [3]. its type extensions are allocated, from among those in [3].
+---------------+------+---------+----------------------------------+ 7.4. Address Block TLV Types
| Mnemonic | Type | Subtype | Description |
+---------------+------+---------+----------------------------------+ A new registry for address block TLV types must be created with
initial assignments as specified in Table 7.
+---------------+------+-----------+--------------------------------+
| Mnemonic | Type | Type | Description |
| | | extension | |
+---------------+------+-----------+--------------------------------+
| PREFIX_LENGTH | 0 | 0 | Indicates that associated | | PREFIX_LENGTH | 0 | 0 | Indicates that associated |
| | | | addresses are network addresses, | | | | | addresses are network |
| | | | with given prefix length, in | | | | | addresses, with given prefix |
| | | | bits. | | | | | length, in bits. |
| | | | | | | | | |
| | 0 | 1-255 | RESERVED | | | 0 | 1-255 | RESERVED |
+---------------+------+---------+----------------------------------+ +---------------+------+-----------+--------------------------------+
Table 7 Table 7
Subtypes indicated as RESERVED may be allocated by standards action, Future values in the range 1-127 can be allocated using standards
as specified in [3]. action [3], respecting the following guidelines:
values 1-7 - MUST NOT be assigned except when a documented need
exists that TLVs of a given type are required to appear before all
other TLVs in the TLV block as encoded for transmission. Note
that the need for a TLV to be processed before other TLVs does not
however automatically translate into a need for the TLV appearing
before all other TLVs in the TLV block - the order in which TLVs
are to be processed MUST be defined, if applicable, in the
protocols using this specification.
values 8-127 - no constraints.
Additionally, values in the range 128-255 are reserved for private/
local use. If an address block TLV type is allocated then a new
registry for type extensions of that type must be created. A
document which defines an address block TLV type MUST also specify
the mechanism by which its type extensions are allocated, from among
those in [3].
8. Security Considerations 8. Security Considerations
Messages are designed to be carriers of protocol information and MAY, This specification does not describe a protocol; it describes a
at each hop, be forwarded and/or processed according to the packet format. As such it does not specify any security
considerations, these are matters for a protocol using this
specification. However two mechanisms which are enabled by this
specification, and may form part of a security approach in a protocol
using this specification, are described in Section 8.1. There is
however no requirement that a protocol using this specification
should use either.
8.1. Security Suggestions
The security suggestions made here, are based on that:
o Messages are designed to be carriers of protocol information and
MAY, 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.
For forwarded messages where the message is unchanged by forwarding o Packets are designed to carry a number of messages between
nodes, then end-to-end security MAY be implemented, between nodes neighboring nodes in a single transmission and over a single
with an existing security association, by including a suitable logical hop.
message TLV containing a cryptographic signature in the message.
Since <hop-count> and <hop-limit> are the only fields that may be
modified when such a message is forwarded in this manner, this
signature can be calculated based on the entire message, including
the message header, with the <hop-count> and <hop-limit> fields set
to zero ('0') if present.
Packets are designed to carry a number of messages between Consequently:
neighboring nodes in a single transmission and over a single logical
hop. Hop-by-hop packet level security MAY be implemented, between o For forwarded messages where the message is unchanged by
nodes with an existing security association, by including a suitable forwarding nodes, then end-to-end security MAY be implemented,
packet TLV containing a cryptographic signature to the packet. Since between nodes with an existing security association, by including
packets are received as transmitted, this signature can be calculated a suitable message TLV containing a cryptographic signature in the
based on the entire packet, or on parts thereof as appropriate. message. Since <hop-count> and <hop-limit> are the only fields
that may be modified when such a message is forwarded in this
manner, this signature can be calculated based on the entire
message, including the message header, with the <hop-count> and
<hop-limit> fields set to zero ('0') if present.
o Hop-by-hop packet level security MAY be implemented, between nodes
with an existing security association, by including a suitable
packet TLV containing a cryptographic signature to the packet.
Since packets are received as transmitted, this signature can be
calculated based on the entire packet, or on parts thereof as
appropriate.
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, BCP 14, March 1997. Levels", RFC 2119, BCP 14, March 1997.
[2] Hinden, R. and S. Deering, "IP Version 6 Addressing [2] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
skipping to change at page 23, line 17 skipping to change at page 27, line 17
This appendix contains some examples of parts of this specification. This appendix contains some examples of parts of this specification.
A.1. Address Block Examples A.1. Address Block Examples
The following examples illustrate how some combinations of addresses The following examples illustrate how some combinations of addresses
may be efficiently included in address blocks. These examples are may be efficiently included in address blocks. These examples are
for IPv4, with address-length equal to 4. a, b, c etc. represent for IPv4, with address-length equal to 4. a, b, c etc. represent
distinct, non-zero, octet values. distinct, non-zero, octet values.
Note that it is permissible to use a less efficient representation, Note that it is permissible to use a less efficient representation,
in particular one in which the nohead and notail bits of the in particular one in which the anohead and anotail bits of the
semantics octet are set, and hence head-length = 0, tail-length = 0, semantics octet are set, and hence head-length = 0, tail-length = 0,
mid-length = address-length, and the address block consists of the mid-length = address-length, and the address block consists of the
number of addresses, the semantics octet with value 3, and a list of number of addresses, the semantics octet with value 3, and a list of
the uncompressed addresses. This is also the most efficient way to the uncompressed addresses. This is also the most efficient way to
represent a single address, and the only way to represent, for 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. example, a.b.c.d and e.f.g.h in one address block.
Examples: Examples:
o To include a.b.c.d, a.b.e.f and a.b.g.h: o To include a.b.c.d, a.b.e.f and a.b.g.h:
* head-length = 2; * head-length = 2;
* tail-length = 0; * tail-length = 0;
* mid-length = 2; * mid-length = 2;
* <semantics> has notail set (value 2); * <addr-semantics> has anotail set (value 2);
* <tail-length> and <tail> are omitted. * <tail-length> and <tail> are omitted.
The address block is then 3 2 2 a b c d e f g h (11 octets). 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: o To include a.b.c.g and d.e.f.g:
* head-length = 0; * head-length = 0;
* tail-length = 1; * tail-length = 1;
* mid-length = 3; * mid-length = 3;
* <semantics> has nohead set (value 1); * <addr-semantics> has anohead set (value 1);
* <head-length> and <head> are omitted. * <head-length> and <head> are omitted.
The address block is then 2 1 1 g a b c d e f (10 octets). 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: o To include a.b.d.e and a.c.d.e:
* head-length = 1; * head-length = 1;
* tail-length = 2; * tail-length = 2;
* mid-length = 1; * mid-length = 1;
* <semantics> = 0. * <addr-semantics> = 0.
The address block is then 2 0 1 a 2 d e b c (9 octets). 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: o To include a.b.0.0, a.c.0.0, and a.d.0.0:
* head-length = 1; * head-length = 1;
* tail-length = 2; * tail-length = 2;
* mid-length = 1; * mid-length = 1;
* <semantics> has zerotail set (value 4); * <addr-semantics> has ahaszerotail set (value 4);
* <tail> is omitted. * <tail> is omitted.
The address block is then 3 4 1 a 2 b c d (8 octets). 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: o To include a.b.0.0 and c.d.0.0:
* head-length = 0; * head-length = 0;
* tail-length = 2; * tail-length = 2;
* mid-length = 2; * mid-length = 2;
* <semantics> has nohead and zerotail set (value 5); * <addr-semantics> has anohead and ahaszerotail set (value 5);
* <head> and <tail> are omitted. * <head> and <tail> are omitted.
The address block is then 2 5 2 a b c d (7 octets). The address block is then 2 5 2 a b c d (7 octets).
A.2. TLV Examples A.2. TLV Examples
If network addresses a.b.0.0/16, c.d.0.0/16, c.d.e.0/24 and 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 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 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 lengths added using one or more address block TLVs of type
PREFIX_LENGTH (0), then this can be done in a number of ways. PREFIX_LENGTH (0, with no type extension), then this can be done in a
Possible examples are: number of ways. Possible examples are:
o Using one multivalue TLV covering all of the addresses: o Using one multivalue TLV covering all of the addresses:
* <semantics> has noindex and multivalue set (value 40); * <tlv-semantics> has tnoindex and tismultivalue set (value 40);
* <index-start> and <index-stop> are omitted; * <index-start> and <index-stop> are omitted;
* <length> = 4 (single-length = 1). * <length> = 4 (single-length = 1).
* The TLV is then 0 40 4 16 16 24 32 (7 octets). * The TLV is then 0 40 4 16 16 24 32 (7 octets).
o Using one multivalue TLV omitting the last address (a prefix o Using one multivalue TLV omitting the last address (a prefix
length of 32 is the default): length of 32 is the default):
* <semantics> has multivalue set (value 32); * <tlv-semantics> has tismultivalue set (value 32);
* <index-start> = 0; * <index-start> = 0;
* <index-stop> = 2 * <index-stop> = 2
* <length> = 3 (single-length = 1). * <length> = 3 (single-length = 1).
* The TLV is then 0 32 0 2 3 16 16 24 (8 octets). * The TLV is then 0 32 0 2 3 16 16 24 (8 octets).
o Using two single value TLVs, omitting the last address. First: o Using two single value TLVs, omitting the last address. First:
* <semantics> = 0; * <tlv-semantics> = 0;
* <index-start> = 0; * <index-start> = 0;
* <index-stop> = 1; * <index-stop> = 1;
* <length> = 1; * <length> = 1;
* <value> = 16. * <value> = 16.
* The TLV is then 0 0 0 1 1 16 (6 octets). * The TLV is then 0 0 0 1 1 16 (6 octets).
Second: Second:
* <semantics> has singlevalue set (value 16); * <tlv-semantics> has thassingleindex set (value 16);
* <index-start> = 2; * <index-start> = 2;
* <index-stop> is omitted; * <index-stop> is omitted;
* <length> = 1; * <length> = 1;
* <value> = 24. * <value> = 24.
* The TLV is then 0 16 2 1 24 (5 octets). * The TLV is then 0 16 2 1 24 (5 octets).
Total length of TLVs is 11 octets. Total length of TLVs is 11 octets.
In this case the first of these is the most efficient. In other In this case the first of these is the most efficient. In other
cases patterns such as the others may be preferred. Regardless of cases patterns such as the others may be preferred. Regardless of
efficiency, any of these may be used. efficiency, any of these may be used.
Assuming the definition of an address block TLV with type EXAMPLE Assuming the definition of an address block TLV with type EXAMPLE
which has no value (it is sufficient to simply indicate which (and no type extension) which has no value (it is sufficient to
addresses are examples), for the same address block, with the second simply indicate which addresses are examples), for the same address
and third addresses being examples, this can be indicated with a block, with the second and third addresses being examples, this can
single TLV: be indicated with a single TLV:
o <semantics> has novalue set (value 4); o <tlv-semantics> has tnovalue set (value 4);
o <index-start> = 1; o <index-start> = 1;
o <index-stop> = 2; o <index-stop> = 2;
o <length> and <value> are omitted. o <length> and <value> are omitted.
o The TLV is then EXAMPLE 4 1 2 (4 octets). o The TLV is then EXAMPLE 4 1 2 (4 octets).
Assuming the definition of a message TLV with type DATA which can Assuming the definition of a message TLV with type DATA (and no type
take a value field of any length, for such a message TLV with 8 extension) which can take a value field of any length, for such a
octets of data (a to h): message TLV with 8 octets of data (a to h):
o <semantics> has noindex set (value 8); o <tlv-semantics> has tnoindex set (value 8);
o <index-start> and <index-stop> are omitted; o <index-start> and <index-stop> are omitted;
o <length> = 8. o <length> = 8.
o The TLV is then DATA 8 8 a b c d e f g h (11 octets). o The TLV is then DATA 8 8 a b c d e f g h (11 octets).
If, in this example, the number of data octets were 256 or greater If, in this example, the number of data octets were 256 or greater
then <semantics> would also have extended set and have value 10. The then <tlv-semantics> would also have tisextended set and have value
length would require two octets (most significant first). The TLV 10. The length would require two octets (most significant first).
length would be 4 + N octets, where N is the number of data octets The TLV length would be 4 + N octets, where N is the number of data
(it can be 3 + N octets if N is 255 or less). octets (it can be 3 + N octets if N is 255 or less).
Appendix B. Illustrations 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.
Examples with version fields are omitted, as not needed when using
this version of this specification (although permitted).
Bits labeled Reserved, Resv, or Rsv are cleared ('0'). Bits labeled Bits labeled Resv, or Rsv are cleared ('0'). Bits labeled N or M may
N and M may be cleared ('0') or set ('1'). Octets labeled Padding be cleared ('0') or set ('1'). Octets labeled Padding must be zero
are cleared ('0'), and are optional. ('0'), and are optional. (They have been omitted where not needed
for alignment.)
Appendix B.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| Resv |0|0|0|0| Packet Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
: ... :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 0 0 0 0 0 0 0| Resv |0|0|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packet Sequence Number | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0| Reserved |0|1| Padding | |0 0 0 0 0 0 0 0| Resv |0|1|0|0| Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0| Reserved |1|0| Packet Sequence Number | |0 0 0 0 0 0 0 0| Resv |0|1|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
: ... :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 0 0 0 0 0 0 0| Resv |1|0|0|0| Packet Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Packet TLV Block | | Packet TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
skipping to change at page 28, line 27 skipping to change at page 34, line 4
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0| Reserved |1|1| | |0 0 0 0 0 0 0 0| Resv |1|0|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packet Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Packet TLV Block | | Packet TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
skipping to change at page 29, line 7 skipping to change at page 35, line 7
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0| Resv |1|1|0|0| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Packet TLV Block |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
: ... :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 0 0 0 0 0 0 0| Resv |1|1|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Packet TLV Block |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
: ... :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message + Padding |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B.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|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number | | Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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 |0|0|0|0|1| Message Size | | Message Type |Rsv|0|0|0|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number | | Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|0| Message Size | | Message Type |Rsv|N|0|0|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | Message Sequence Number | | | Hop Count | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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 |0|0|0|1|1| Message Size | | Message Type |Rsv|0|0|0|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | Message Sequence Number | | | Hop Count | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|0|0| Message Size | | Message Type |Rsv|N|0|1|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Message Sequence Number | | | Hop Limit | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|0|1| Message Size | | Message Type |Rsv|N|0|1|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Message Sequence Number | | | Hop Limit | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|1|0| Message Size | | Message Type |Rsv|N|0|1|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Sequence Number | | | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|1|1| Message Size | | Message Type |Rsv|N|0|1|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Sequence Number | | | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|0|0|0| Message Size | | Message Type |Rsv|N|1|0|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | | | Hop Limit | Hop Count | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|0|0|1| Message Size | | Message Type |Rsv|N|1|0|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | | | Hop Limit | Hop Count | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|0|1|0| Message Size | | Message Type |Rsv|N|1|0|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | | | Hop Count | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|0|1|1| Message Size | | Message Type |Rsv|N|1|0|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | | | Hop Count | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|1|0|0| Message Size | | Message Type |Rsv|N|1|1|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | | | Hop Limit | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|1|0|1| Message Size | | Message Type |Rsv|N|1|1|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | | | Hop Limit | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|1|1|0| Message Size | | Message Type |Rsv|N|1|1|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | 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|1|1|1|1| Message Size | | Message Type |Rsv|N|1|1|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B.3. Message Body Appendix B.3. Message Body
skipping to change at page 39, line 7 skipping to change at page 46, line 7
| Length | | | Length | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|M|0|0|0|0|1| Subtype | Index Start | | Type |Rsv|M|0|0|0|0|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop | Length | | | Index Stop | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 39, line 35 skipping to change at page 46, line 35
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|M|0|0|0|1|1| Subtype | Index Start | | Type |Rsv|M|0|0|0|1|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop | Length | | | Index Stop | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|0|0|0|1|0|0| Index Start | Index Stop | | Type |Rsv|0|0|0|1|0|0| Index Start | Index Stop |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |Rsv|0|0|0|1|0|1| Subtype | Index Start | | Type |Rsv|0|0|0|1|0|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop | | Index Stop |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|M|0|1|0|0|0| Length | | | Type |Rsv|M|0|1|0|0|0| Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|M|0|1|0|0|1| Subtype | Length | | Type |Rsv|M|0|1|0|0|1| Type Ext | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 41, line 19 skipping to change at page 48, line 19
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|M|0|1|0|1|1| Subtype | Length | | Type |Rsv|M|0|1|0|1|1| Type Ext | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length (cont) | | | Length (cont) | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|0|0|1|1|0|0| | Type |Rsv|0|0|1|1|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |Rsv|0|0|1|1|0|1| Subtype | | Type |Rsv|0|0|1|1|0|1| Type Ext |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |Rsv|0|1|0|0|0|0| Index Start | Length | | Type |Rsv|0|1|0|0|0|0| Index Start | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|0|1|0|0|0|1| Subtype | Index Start | | Type |Rsv|0|1|0|0|0|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | | | Length | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
skipping to change at page 43, line 7 skipping to change at page 50, line 7
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|0|1|0|0|1|1| Subtype | Index Start | | Type |Rsv|0|1|0|0|1|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | | | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Value | | Value |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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 |Rsv|0|1|0|1|0|0| Index Start | | Type |Rsv|0|1|0|1|0|0| Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |Rsv|0|1|0|1|0|1| Subtype | Index Start | | Type |Rsv|0|1|0|1|0|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix C. 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 version zero,
sequence number, but no packet TLV block. a packet 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, other than version
originator address, hop limit, hop count and message sequence number (which is zero), including originator address, hop limit, hop count
(which is type independent). The message has a message TLV block and message sequence number (which is type independent). The message
with content length 9 octets, containing a single TLV. This TLV has has a message TLV block with content length 9 octets, containing a
the noindex bit of its semantics octet 8 set, and has value length 6 single TLV. This TLV has the tnoindex bit of its semantics octet 8
octets. The message then has two address blocks each with a set, and has value length 6 octets. The message then has two address
following TLV block. blocks each with a following TLV block.
The first address block contains 3 addresses. It has the notail bit The first address block contains 3 addresses. It has the anotail bit
of its semantics octet 2 set, and has head length 2 octets, hence mid of its semantics octet 2 set, and has head length 2 octets, hence mid
length two octets. It is followed by a TLV block, with content length two octets. It is followed by a TLV block, with content
length 9 octets, containing two TLVs. The first of these TLVs has length 9 octets, containing two TLVs. The first of these TLVs has
the noindex bit of its semantics octet 8 set, and has a single value the tnoindex bit of its semantics octet 8 set, and has a single value
of length 2 octets, which applies to all of the addresses in the of length 2 octets, which applies to all of the addresses in the
address block. The second of these TLVs has the novalue bit of its address block. The second of these TLVs has the tnovalue bit of its
semantics octet 4 set, and hence has no length or value fields. It semantics octet 4 set, and hence has no length or value fields. It
does have index fields, which indicate those addresses this TLV does have index fields, which indicate those addresses this TLV
applies to. applies to.
The second address block contains 2 addresses. It has the nohead and The second address block contains 2 addresses. It has the anohead
zerotail bits of its semantics octet 5 set, and has tail length 2 and ahaszerotail bits of its semantics octet 5 set, and has tail
octets, hence mid length two octets. The two tail octets of each length 2 octets, hence mid length two octets. The two tail octets of
address are zero. It is followed by a TLV block with content length each address are zero. It is followed by a TLV block with content
5 octets. This TLV block contains a single TLV of type PREFIX_LENGTH length 5 octets. This TLV block contains a single TLV of type
that has the multivalue and noindex bits of its semantics octet 40 PREFIX_LENGTH that has the tismultivalue and tnoindex bits of its
set, and a value field length of 2 octets, indicating two values each semantics octet 40 set, and a value field length of 2 octets,
of one octet length. There is one final padding octet 0 that is not indicating two values each of one octet length. There is one final
included in the message length of 59 octets. padding octet 0 that is not included in the message length of 59
octets.
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|0 0 0 0 0 0 0 0| Packet Sequence Number | |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0| Packet Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 1 1 1 0 1 1| | Message Type |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 1 1 1 0 1 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 46, line 13 skipping to change at page 53, line 13
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix D. 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, INRIA, France, <Emmanuel.Baccelli@inria.fr>
<Emmanuel.Baccelli@inria.fr>
o Thomas Heide Clausen, LIX, Ecole Polytechnique, France, o Thomas Heide Clausen, LIX, Ecole Polytechnique, France,
<T.Clausen@computer.org> <T.Clausen@computer.org>
o Justin W. Dean, NRL, USA<jdean@itd.nrl.navy.mil> o Justin W. Dean, NRL, USA<jdean@itd.nrl.navy.mil>
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, <hiroki.satoh.yj@hitachi.com> o Satoh Hiroki, Hitachi SDL, Japan, <h-satoh.yj@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, <kazuya.monden.vw@hitachi.com> o Monden Kazuya, Hitachi SDL, Japan, <monden.vw@sdl.hitachi.co.jp>
Appendix E. 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
skipping to change at page 48, line 14 skipping to change at page 55, line 14
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.thomasclausen.org/ URI: http://www.thomasclausen.org/
Christopher 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/ 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
 End of changes. 155 change blocks. 
335 lines changed or deleted 578 lines changed or added

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