draft-ietf-manet-packetbb-11.txt   draft-ietf-manet-packetbb-12.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: May 17, 2008 BAE Systems Advanced Technology Expires: September 8, 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
November 14, 2007 March 7, 2008
Generalized MANET Packet/Message Format Generalized MANET Packet/Message Format
draft-ietf-manet-packetbb-11 draft-ietf-manet-packetbb-12
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 May 17, 2008. This Internet-Draft will expire on September 8, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies a multi-message packet format that may be This document specifies a packet format capable of carrying multiple
used by mobile ad hoc network routing and other protocols. messages that may be used by mobile ad hoc network routing and
signaling protocols.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology and Notation . . . . . . . . . . . . . . . . . . . 5
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. Syntactical Specification . . . . . . . . . . . . . . . . . . 9
5.1. Packets . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Packets . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.3. Packet and Message Versioning . . . . . . . . . . . . . . 12 5.3. Address Blocks . . . . . . . . . . . . . . . . . . . . . . 13
5.4. Address Blocks . . . . . . . . . . . . . . . . . . . . . . 12 5.4. TLVs and TLV Blocks . . . . . . . . . . . . . . . . . . . 16
5.5. TLVs and TLV Blocks . . . . . . . . . . . . . . . . . . . 15 5.4.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.5.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.4.2. TLV Inclusion and Constraints . . . . . . . . . . . . 19
5.5.2. TLV Inclusion and Constraints . . . . . . . . . . . . 18 5.5. Malformed Elements . . . . . . . . . . . . . . . . . . . . 20
5.6. Malformed Elements . . . . . . . . . . . . . . . . . . . . 19
5.7. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 20
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
6.1. Message Types . . . . . . . . . . . . . . . . . . . . . . 21 6.1. Message Types . . . . . . . . . . . . . . . . . . . . . . 21
6.2. Packet TLV Types . . . . . . . . . . . . . . . . . . . . . 21 6.2. Packet TLV Types . . . . . . . . . . . . . . . . . . . . . 21
6.3. Message TLV Types . . . . . . . . . . . . . . . . . . . . 22 6.3. Message TLV Types . . . . . . . . . . . . . . . . . . . . 22
6.4. Address Block TLV Types . . . . . . . . . . . . . . . . . 22 6.4. Address Block TLV Types . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24
7.1. Security Suggestions . . . . . . . . . . . . . . . . . . . 24 7.1. Authentication Suggestions . . . . . . . . . . . . . . . . 24
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.1. Normative References . . . . . . . . . . . . . . . . . . . 25 8.1. Normative References . . . . . . . . . . . . . . . . . . . 25
8.2. Informative References . . . . . . . . . . . . . . . . . . 25 8.2. Informative References . . . . . . . . . . . . . . . . . . 25
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 26 Appendix A. Intended Usage . . . . . . . . . . . . . . . . . . . 26
A.1. Address Block Examples . . . . . . . . . . . . . . . . . . 26 Appendix B. Compatibility Requirements for Future Versions . . . 27
A.2. TLV Examples . . . . . . . . . . . . . . . . . . . . . . . 28 Appendix C. Examples . . . . . . . . . . . . . . . . . . . . . . 28
Appendix B. Illustrations . . . . . . . . . . . . . . . . . . . 31 C.1. Address Block Examples . . . . . . . . . . . . . . . . . . 28
Appendix B.1. Packet . . . . . . . . . . . . . . . . . . . . . . . 31 C.2. TLV Examples . . . . . . . . . . . . . . . . . . . . . . . 30
Appendix B.2. Message and Padding . . . . . . . . . . . . . . . . 36 Appendix D. Illustrations . . . . . . . . . . . . . . . . . . . . 33
Appendix B.3. Message Body . . . . . . . . . . . . . . . . . . . . 42 D.1. Packet . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Appendix B.4. Address Block . . . . . . . . . . . . . . . . . . . 43 D.2. Message . . . . . . . . . . . . . . . . . . . . . . . . . 40
Appendix B.5. TLV Block . . . . . . . . . . . . . . . . . . . . . 50 D.3. Message Body . . . . . . . . . . . . . . . . . . . . . . . 46
Appendix B.6. TLV . . . . . . . . . . . . . . . . . . . . . . . . 50 D.4. Address Block . . . . . . . . . . . . . . . . . . . . . . 47
Appendix C. Complete Example . . . . . . . . . . . . . . . . . . 56 D.5. TLV Block . . . . . . . . . . . . . . . . . . . . . . . . 54
Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 58 D.6. TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Appendix E. Acknowledgements . . . . . . . . . . . . . . . . . . 59 Appendix E. Complete Example . . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 60 Appendix F. Contributors . . . . . . . . . . . . . . . . . . . . 62
Intellectual Property and Copyright Statements . . . . . . . . . . 61 Appendix G. Acknowledgements . . . . . . . . . . . . . . . . . . 63
1. Introduction 1. Introduction
This document specifies the syntax of a general purpose multi-message This document specifies the syntax of a general purpose packet format
packet format for information exchange between MANET routers. capable of carrying multiple messages for information exchange
Messages consist of a message header, which is designed for control between MANET (Mobile Ad hoc NETwork) routers. Messages consist of a
of message dissemination, and a message body, which contains protocol message header, which is designed for control of message
dissemination, and a message body, which contains protocol
information. Only the syntax of the packet and messages is information. Only the syntax of the packet and messages is
specified. All syntactical entities, including packets and messages, specified. All syntactical entities, including packets and messages,
are specified 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. information to exchange is contained in the packet header.
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 contains information which may be o A message header format, which contains information which may be
sufficient to allow a protocol using this specification to make sufficient to allow a protocol using this specification to make
processing and forwarding decisions. processing and forwarding decisions.
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, or address prefixes, 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
network addresses in a compact (compressed) form. addresses, or address prefixes, 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 each associated attributes. Multiple TLVs can be included and each associated
with a packet, a message, an address, or a set of addresses. with a packet, a message, or one or more addresses or address
prefixes.
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. address prefixes or IPv6 interface identifiers) the address
representation allows for a compact representation. Compact block 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, unless indicated otherwise. The required message header elements, unless indicated otherwise. The
structure of packet and message encoding allows parsing, structure of packet and message encoding allows parsing,
verifying, and identifying individual elements in a single pass. verifying, and identifying individual elements in a single pass.
Separation of forwarding and processing - a protocol using this Separation of forwarding and processing - a protocol using this
specification can be designed such that duplicate detection and specification can be designed such that 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 and Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. [1]. document are to be interpreted as described in RFC 2119. [RFC2119].
Additionally, this document uses the following terminology: Additionally, this document uses the following terminology:
Packet - the top level entity in this specification. Packets are Packet - The top level entity in this specification. A packet
transmitted over a single logical hop and are not forwarded. A contains zero or more messages, and may contain a packet header.
packet contains zero or more messages, and may contain a packet
header.
Message - the fundamental entity carrying protocol information, in Message - The fundamental entity carrying protocol information, in
the form of addresses and TLVs. Messages are designed to be able the form of address objects and TLVs.
to be forwarded over one or more logical hops.
Address - a number of octets of the same length as the source IP Address - A number of octets of the same length as the source IP
address in the IP datagram carrying the packet. The meaning of an address in the IP datagram carrying the packet. The meaning of an
address is defined by the protocol using this specification. address is defined by the protocol using this specification.
Network Address - An address plus a prefix length between zero and Address Prefix - An address plus a prefix length, with the prefix
the length of an address in bits, inclusive. length being a number of address bits measured from the left/most
significant end of the address.
TLV - a Type-Length-Value structure. This is a generic way in which Address Object - Either an address, or an address prefix, as
specified in an address block in this specification.
TLV - A Type-Length-Value structure. This is a generic way in which
an attribute can be represented and correctly parsed, without the an attribute can be represented and correctly parsed, without the
parser having to understand the attribute. parser having to understand the attribute.
Element - a syntactic entity defined in the regular expression Element - A syntactic entity defined in the regular expression
specification, represented using the notation <foo>. specification, represented using the notation <foo>.
<foo> - if <foo> is an 8 or 16 bit field then <foo> is also used to <foo> - If <foo> is an 8 or 16 bit unsigned integer field then <foo>
represent the value of that field. is also used to represent the value of that field.
? - zero or one occurrences of the preceding element. bar - A variable, usually obtained through calculations based on the
value(s) of element(s). Variables are introduced into the
specification solely as a means to clarify the description.
* - zero or more occurrences of the preceding element. := - Indicates that the element or variable on the left hand side is
defined as the expression on the right hand side.
bar - a variable, usually obtained through calculations based on the {<element1><element2>} - Indicates a grouping of the elements
value(s) of field(s). Variables are introduced into the enclosed by the braces.
specification solely as a means to clarify the description.
address-length - a variable whose value is the length of an address ? - Zero or one occurrences of the preceding element or group.
* - Zero or more occurrences of the preceding element or group.
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 packet format capable of
for carrying MANET routing protocol signals. The specification has carrying multiple messages, for carrying MANET routing protocol
been developed from that used by OLSR (The Optimized Link State signals. The specification has been inspired by and extended from
Routing Protocol) [4]. that used by OLSR (The Optimized Link State Routing protocol)
[RFC3626].
The specification is designed with IP (IPv4/IPv6) in mind. All The specification is designed with IP (IPv4/IPv6) in mind. All
addresses within a control message are assumed to be of the same addresses within a control message are assumed to be of the same
size, deduced from IP. In the case of mixed IPv6 and IPv4 addresses, size, deduced from IP. In the case of mixed IPv6 and IPv4 addresses,
IPv4 addresses are represented as IPv4-mapped IPv6 addresses as IPv4 addresses can be represented as IPv4-mapped IPv6 addresses as
specified in [2]. specified in [RFC4291].
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 MANET routing protocol signals between MANET routers. This
limited diffusion, as well as point to point signaling in a multi-hop specification includes elements which can support limited diffusion
network. (flooding), as well as being usable for point to point delivery of
MANET routing protocol signals in a multi-hop 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 MANET routing protocol messages in a single transmission.
unicast or multicast, may be transmitted as appropriate to the The packets may be unicast or multicast, and may be transmitted as
protocol using this specification and may travel over a single appropriate to the MANET routing protocol using this specification.
logical hop which might consist of one or more IP hops.
This specification is particularly appropriate for extensible This specification is particularly appropriate for extensible MANET
protocols. It offers external extensibility in the form of new routing protocols. It offers external extensibility in the form of
message types. It offers internal extensibility in the form of TLVs, new message types. It offers internal extensibility in the form of
which may be added to existing message types. TLVs, which may be added to existing message types.
A protocol using the multi-message packet format defined by this A MANET routing protocol using the multi-message packet format
specification may constrain the syntax (for example requiring a defined by this specification MAY constrain the syntax (for example
specific set of message header fields) and features (for example requiring a specific set of message header fields) that the protocol
specifying the suggested diffusion mechanism) that the protocol will will employ.
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. Syntactical Specification
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 D.
This format uses network byte order (most significant octet first)
for all fields.
5.1. Packets 5.1. Packets
<packet> is defined by: <packet> is defined by:
<packet> = {<pkt-header><pad-octet>*}? <packet> := <pkt-header>?
{<message><pad-octet>*}* <message>*
where <message> is defined in Section 5.2, and <pad-octet> is defined where <message> is as defined in Section 5.2. Successful parsing is
in Section 5.7. Successful parsing is terminated when all octets terminated when all octets (defined using the variable pkt-size
(defined using the variable pkt-size below) are used. A packet MUST below) are used. A packet MUST NOT be empty, that is a packet MUST
contain either a <pkt-header> or at least one <message>. contain either a <pkt-header> or at least one <message>.
<pkt-header> is defined by: <pkt-header> is defined by:
<pkt-header> = <zero> <pkt-header> := <zero>
<pkt-semantics> <pkt-semantics>
<pkt-version>? <pkt-version>?
<pkt-size>? <pkt-size>?
<pkt-seq-num>? <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 <pkt-header>. serves to identify that the packet starts with a <pkt-header>.
<pkt-semantics> is an 8 bit field, specifying the composition of the <pkt-semantics> is an 8 bit field, specifying the composition of the
<pkt-header>: <pkt-header>:
bit 0 (phasversion): If cleared ('0'), then <pkt-version> is not bit 0 (phasversion): If cleared ('0'), then <pkt-version> is not
included in the <pkt-header>. If set ('1'), then <pkt-version> included in the <pkt-header>. If set ('1'), then <pkt-version>
is included in the <pkt-header>. is included in the <pkt-header>.
bit 1 (phassize): if cleared ('0'), then <pkt-size> is not bit 1 (phassize): If cleared ('0'), then <pkt-size> is not
included in the <pkt-header>. if set ('1'), then <pkt-size> is included in the <pkt-header>. If set ('1'), then <pkt-size> is
included in the <pkt-header>. included in the <pkt-header>.
bit 2 (pnoseqnum): if cleared ('0'), then <pkt-seq-num> is bit 2 (phasseqnum): If cleared ('0'), then <pkt-seq-num> is not
included in the <pkt-header>. If set ('1'), then <pkt-seq-num> included in the <pkt-header>. If set ('1'), then <pkt-seq-num>
is not included in the <pkt-header>. is included in the <pkt-header>.
bit 3 (phastlv): if cleared ('0'), then <tlv-block> is not bit 3 (phastlv): If cleared ('0'), then <tlv-block> is not
included in the <pkt-header>. If set ('1'), then <tlv-block> included in the <pkt-header>. If set ('1'), then <tlv-block>
is included in the <pkt-header>. is included in the <pkt-header>.
bit 4 (pnouniord): if cleared ('0'), then the packet TLV block bit 4 (pnouniord): If cleared ('0'), then the packet TLV block
MUST conform to the constraints in Section 5.5.2. If set MUST conform to the constraints in Section 5.4.2. If set
('1'), then the packet TLV block is not subject to the ('1'), then the packet TLV block is not subject to the
constraints in Section 5.5.2. Additional constraints MAY be constraints in Section 5.4.2. Additional constraints MAY be
imposed by a protocol using this specification. imposed by a protocol using this specification.
bits 5-7: are RESERVED, and MUST each be cleared ('0') to be in bits 5-7: Are RESERVED, and SHOULD each be cleared ('0') on
conformance with this version of the specification. transmission, and SHOULD be ignored on reception.
<pkt-version> is omitted if the phasversion bit is cleared ('0'), <pkt-version> is omitted if the phasversion bit is cleared ('0'),
otherwise is an 8 bit field, specifying the version of this otherwise is an 8 bit unsigned integer field, specifying the
specification. version of this specification.
<pkt-size> is omitted if the phassize bit is cleared ('0'), <pkt-size> is omitted if the phassize bit is cleared ('0'),
otherwise is a 16 bit field, specifying the size of the <packet> otherwise is a 16 bit unsigned integer field, specifying the
counted in octets. number of octets that make up the <packet>.
<pkt-seq-num> is omitted if the pnoseqnum bit is set ('1'), <pkt-seq-num> is omitted if the phasseqnum bit is cleared ('0'),
otherwise is a 16 bit field, specifying a packet sequence number. otherwise is a 16 bit unsigned field, specifying a packet sequence
number.
<tlv-block> is omitted if the phastlv bit is cleared ('0'), and is <tlv-block> is omitted if the phastlv bit is cleared ('0'), and is
otherwise as defined in Section 5.5. otherwise as defined in Section 5.4.
Note that since the message type zero is not used (see Section 6), Note that since message type zero is not used (see Section 6), the
the presence or absence of a packet header can be determined by 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 pkt-version is a variable, defined to equal <pkt-version> if
present, or 0 otherwise. See Section 5.3. present, or zero (0) otherwise. pkt-version MUST be zero to be in
accordance with this version of this specification. See
Appendix B.
pkt-size is a variable, defined to equal <pkt-size> if present, or pkt-size is a variable, defined to equal <pkt-size> if present, or
the size of the payload of the network or transport protocol the size of the payload of the network or transport protocol
employed otherwise. (If not present, and the payload size is employed otherwise. (If not present, and the payload size is
unknown, then the packet cannot be parsed, and is considered unknown, then the packet cannot be parsed, and is considered
malformed.) malformed.)
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 address
addresses. objects.
o An address TLV block, containing zero or more TLVs, following each o An address TLV block, containing zero or more TLVs, following each
address block. address 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-version>? <msg-version>?
<msg-size> <msg-size>
<msg-orig-addr>? <msg-orig-addr>?
<msg-hop-limit>? <msg-hop-limit>?
<msg-hop-count>? <msg-hop-count>?
<msg-seq-num>? <msg-seq-num>?
where: where:
<tlv-block> is as defined in Section 5.5. <tlv-block> is as defined in Section 5.4.
<addr-block> is as defined in Section 5.4. <addr-block> is as defined in Section 5.3.
<msg-type> is an 8 bit field, specifying the type of message. A <msg-type> is an 8 bit unsigned integer field, specifying the type
type with all bits cleared ('0') MUST NOT be used. of the message. A 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 (mhasversion): If cleared ('0'), then <msg-version> is not bit 0 (mhasversion): If cleared ('0'), then <msg-version> is not
included in the <msg-header>. If set ('1'), then <msg-version> included in the <msg-header>. If set ('1'), then <msg-version>
is included in the <msg-header>. is included in the <msg-header>.
bit 1 (mnoorig): If cleared ('0'), then <msg-orig-addr> is bit 1 (mhasorig): If cleared ('0'), then <msg-orig-addr> is not
included in the <msg-header>. If set ('1'), then <msg-orig- included in the <msg-header>. If set ('1'), then <msg-orig-
addr> is not included in the <msg-header>. addr> is included in the <msg-header>.
bit 2 (mnohoplimit): If cleared ('0'), then <msg-hop-limit> is bit 2 (mhashoplimit): If cleared ('0'), then <msg-hop-limit> is
included in the <msg-header>. If set ('1'), then <msg-hop- not included in the <msg-header>. If set ('1'), then <msg-hop-
limit> is not included in the <msg-header>. limit> is included in the <msg-header>.
bit 3 (mnohopcount): If cleared ('0'), then <msg-hop-count> is bit 3 (mhashopcount): If cleared ('0'), then <msg-hop-count> is
included in the <msg-header>. If set ('1'), then <msg-hop- not included in the <msg-header>. If set ('1'), then <msg-hop-
count> is not included in the <msg-header> count> is included in the <msg-header>
bit 4 (mnoseqnum): If cleared ('0'), then <msg-seq-num> is bit 4 (mhasseqnum): If cleared ('0'), then <msg-seq-num> is not
included in the <msg-header>. If set ('1'), then <msg-seq-num> included in the <msg-header>. If set ('1'), then <msg-seq-num>
is not included in the <msg-header>. is included in the <msg-header>.
bit 5 (mistypedep): 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
mnoorig bit is set ('1'). mhasorig bit is cleared ('0').
bit 6 (mnouniord): if cleared ('0'), then the message TLV block bit 6 (mnouniord): If cleared ('0'), then the message TLV block
and all address TLV blocks in the message MUST conform to the and all address TLV blocks in the message MUST conform to the
constraints in Section 5.5.2. If set ('1'), then the message constraints in Section 5.4.2. If set ('1'), then the message
TLV block and all address TLV blocks in the message are not TLV block and all address TLV blocks in the message are not
subject to the constraints in Section 5.5.2. Additional subject to the constraints in Section 5.4.2. Additional
constraints MAY be imposed by a protocol using this constraints MAY be imposed by a protocol using this
specification. specification.
bit 7: is RESERVED and MUST be cleared ('0') to be in conformance bit 7: Is RESERVED, and SHOULD be cleared ('0') on transmission,
with this version of the specification. and SHOULD be ignored on reception.
If bit 1 (mnoorig) and bit 4 (mnoseqnum) are both cleared, then
the message header provides for duplicate suppression.
If bit 2 (mnohoplimit) is cleared, then the message header
provides for scope-delimited forwarding.
<msg-version> is omitted if the mhasversion bit is cleared ('0'), <msg-version> is omitted if the mhasversion bit is cleared ('0'),
otherwise is an 8 bit field, specifying the version of this otherwise is an 8 bit unsigned integer field, specifying the
specification. version of this specification.
<msg-size> is a 16 bit field, specifying the size of the <message>, <msg-size> is a 16 bit unsigned integer field, specifying the number
counted in octets. of octets that make up the <message>
<msg-orig-addr> is omitted if the mnoorig bit is set ('1'), <msg-orig-addr> is omitted if the mhasorig bit is cleared ('0'),
otherwise is an identifier of length equal to address-length, otherwise is an identifier with length equal to address-length,
which serves to uniquely identify the node that originated the which can serve to uniquely identify the node that originated the
message. message.
<msg-hop-limit> is omitted if the mnohoplimit bit is set ('1'), <msg-hop-limit> is omitted if the mhashoplimit bit is cleared ('0'),
otherwise is an 8 bit field, which contains the maximum number of otherwise is an 8 bit unsigned integer field, which can contain
logical hops that the message should be further transmitted. the maximum number of hops that the message should be further
(<msg-hop-limit> SHOULD be decremented if the message is transmitted.
forwarded.)
<msg-hop-count> is omitted if the mnohopcount bit is set ('1'), <msg-hop-count> is omitted if the mhashopcount bit is cleared ('0'),
otherwise is an 8 bit field, which contains the number of logical otherwise is an 8 bit unsigned integer field, which can contain
hops that the message has traveled. (<msg-hop-count> SHOULD be the number of hops that the message has traveled.
incremented if the message is forwarded.)
<msg-seq-num> is omitted if the mnoseqnum bit is set ('1'), <msg-seq-num> is omitted if the mhasseqnum bit is cleared ('0'),
otherwise is a 16 bit field, which contains a unique number, otherwise is a 16 bit unsigned integer field, which can contain a
generated by the message's originator node. The <msg-orig-addr>, sequence number, generated by the message's originator node.
<msg-seq-num>, and, if the mistypedep bit in the <msg-semantics>
field is set, the <msg-type> of a message serves to uniquely
identify the message in the network (within the time period until
<msg-seq-num> wraps around to a matching value).
msg-version is a variable, defined to equal <msg-version> if msg-version is a variable, defined to equal <msg-version> if
present, or to pkt-version otherwise. See Section 5.3. present, or to pkt-version otherwise. msg-version MUST be 0 (zero)
to be in accordance with this version of this specification. See
Appendix B.
5.3. Packet and Message Versioning 5.3. Address Blocks
This specification defines packets and messages of version 0 (zero), An address block can specify one or more addresses. It can also
so that pkt-version and each msg-version MUST equal zero. This specify prefix lengths that can be applied to all addresses in the
SHOULD be indicated by clearing the phasversion and mhasversion bits address block. This allows an address block to specify either
in <pkt-semantics> and <msg-semantics>, respectively. addresses or address prefixes. A protocol may specify that an
address with a maximum prefix length (equal to the address length, in
bits) is considered to be an address, rather than a address prefix,
thus allowing an address block to contain a mixture of addresses and
address prefixes. The common term "address object" is used in this
specification to cover both of these; note that an address object in
an address block always includes the prefix length, if present.
A protocol using this specification, or any future version (i.e. An address is specified as a sequence of address-length octets of the
where pkt-version or msg-version are different from zero) of this form head:mid:tail. An address block contains an ordered set of
specification MUST specify appropriate behavior in the case where an addresses sharing the same head and tail, and having individual mids.
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 block can specify address prefixes:
An address block may specify one or more addresses, or one or more o with a single prefix length for all address prefixes, OR
network addresses (address plus prefix length). An address is
specified as a sequence of address-length octets of the form head: o with a prefix length for each address prefix.
mid:tail. An address block is an ordered set of addresses sharing
the same head and tail, and having individual mids. An address block
may specify network addresses either with a single prefix length for
all network addresses, or with a prefix length for each network
address.
<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>?}?
<tail-length>?
<tail>?
<mid>* <mid>*
<prefix-length>* <prefix-length>*
where: where:
<num-addr> is an 8 bit field containing the number of addresses <num-addr> is an 8 bit unsigned integer field containing the number
represented in the address block, which MUST NOT be zero. of addresses 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 (anohead): if cleared ('0'), then <head-length> is included bit 0 (ahashead): If cleared ('0'), then <head-length> and <head>
in the <address-block>, and <head> may be included in the are not included in the <address-block>. If set ('1'), then
<address-block>. If set ('1'), then <head-length> and <head> <head-length> is included in the <address-block>, and <head> is
are not included in the <address-block>. included in the <address-block> unless <head-length> is zero.
bit 1 (anotail) and bit 2 (ahaszerotail): MUST NOT both be set bit 1 (ahasfulltail) and bit 2 (ahaszerotail): Are interpreted
('1'). Otherwise, they are interpreted according to Table 1. according to Table 1. A combination not shown in that table
MUST NOT be used.
+---------+--------------+---------------+-----------------+ bit 3 (ahassingleprelen) and bit 4 (ahasmultiprelen): Are
| anotail | ahaszerotail | <tail-length> | <tail> | interpreted according to Table 2. A combination not shown in
+---------+--------------+---------------+-----------------+ that table MUST NOT be used.
| 0 | 0 | included | may be included |
bits 5-7: Are RESERVED, and SHOULD each be cleared ('0') on
transmission, and SHOULD be ignored on reception.
+--------------+--------------+---------------+---------------------+
| ahasfulltail | ahaszerotail | <tail-length> | <tail> |
+--------------+--------------+---------------+---------------------+
| 0 | 0 | not included | not included |
| | | | | | | | | |
| 1 | 0 | not included | not included | | 1 | 0 | included | included unless |
| | | | <tail-length> is |
| | | | zero |
| | | | | | | | | |
| 0 | 1 | included | not included | | 0 | 1 | included | not included |
+---------+--------------+---------------+-----------------+ +--------------+--------------+---------------+---------------------+
Table 1
bit 3 (ahassingleprelen) and bit 4 (ahasmultiprelen): MUST NOT
both be set ('1'). Otherwise, they are interpreted according
to Table 2.
+------------+------------+--------------------+--------------------+ Table 1: Interpretation of the ahasfulltail and ahaszerotail bits
| ahassingle | ahasmulti | number of | nth network | +------------+-----------+------------------+-----------------------+
| prelen | prelen | <prefix-length> | address prefix | | ahassingle | ahasmulti | number of | prefix length of the |
| | | fields | length | | prelen | prelen | <prefix-length> | nth address prefix, |
+------------+------------+--------------------+--------------------+ | | | fields | in bits |
| 0 | 0 | zero | 8 * address-length | +------------+-----------+------------------+-----------------------+
| 0 | 0 | 0 | 8 * address-length |
| | | | | | | | | |
| 1 | 0 | one | <prefix-length> | | 1 | 0 | 1 | <prefix-length> |
| | | | | | | | | |
| 0 | 1 | <num-addr> | nth | | 0 | 1 | <num-addr> | nth <prefix-length> |
| | | | <prefix-length> | +------------+-----------+------------------+-----------------------+
+------------+------------+--------------------+--------------------+
Table 2
bits 5-7: are RESERVED and MUST each be cleared ('0') to be in Table 2: Interpretation of the ahassingleprelen and ahasmultiprelen
accordance with this version of the specification. bits
<head-length> if present is an 8 bit field, which contains the total <head-length> if present is an 8 bit unsigned integer field, which
length (in octets) of the head of all of the addresses. contains the number of octets in 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
present, or 0 otherwise. present, or 0 otherwise.
<head> is omitted if head-length == 0, otherwise it is a field of <head> is omitted if head-length is equal to 0, otherwise it is a
the head-length leftmost octets of all the addresses. field of 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 unsigned integer field, which
length (in octets) of the tail of all of the addresses. contains the number of octets in 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 ahaszerotail bit is <tail> is omitted if tail-length is equal to 0 or if the
set ('1'), otherwise it is a field of the tail-length rightmost ahaszerotail bit is set ('1'), otherwise it is a field of the
octets of all the addresses. If the ahaszerotail bit is set ('1') tail-length rightmost octets of all the addresses. If the
then the tail-length rightmost octets of all the addresses are all ahaszerotail bit is set ('1') then the tail-length rightmost
0. 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 is equal to 0, otherwise each <mid>
of length mid-length octets, representing the mid of the is a field of length mid-length octets, representing the mid of
corresponding address in the address block. the corresponding address in the address block.
<prefix-length> is an 8 bit field containing the length, in bits, of <prefix-length> is an 8 bit unsigned integer field containing the
the prefix length of a network address. If the ahassingleprelen length, in bits, of the prefix length of an address prefix. If
bit is set ('1') then a single <prefix-length> field contains the the ahassingleprelen bit is set ('1') then a single <prefix-
prefix length of all addresses in the address block. If the length> field contains the prefix length of all addresses in the
ahasmultiprelen bit is set ('1') then each of the <num-addr> address block. If the ahasmultiprelen bit is set ('1') then each
<prefix-length> fields contains the prefix length of the of the <num-addr> <prefix-length> fields contains the prefix
corresponding address in the address block (in the same order). length of the corresponding address prefix in the address block
Otherwise no <prefix-length> fields are present; each address may (in the same order). Otherwise no <prefix-length> fields are
be considered to have a prefix length equal to 8 * address-length present; each address object can be considered to have a prefix
bits. The address block is malformed if any <prefix-length> field length equal to 8 * address-length bits. The address block is
has a value greater than 8 * address-length. malformed if any <prefix-length> element has a value greater than
8 * address-length.
5.5. TLVs and TLV Blocks 5.4. 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 unsigned integer field, which contains the
octets) of all of the immediately following <tlv> elements. total number of octets in all of the immediately following <tlv>
elements.
<tlv> is as defined in Section 5.5.1. <tlv> is as defined in Section 5.4.1.
5.5.1. TLVs 5.4.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 the packet TLV block in a packet header. o A packet TLV, included in the packet TLV block in a packet header.
o A message TLV, included in the message TLV block in a message, o A message TLV, included in the message TLV block in a message,
before the first address block. before the first address block.
o An address block TLV, included in an address TLV block following o An address block TLV, included in an address TLV block following
an address block. An address block TLV applies to: an address block. An address block TLV applies to:
* all addresses in the address block; OR * all address objects in the address block; OR
* any continuous sequence of addresses in the address block; OR * any continuous sequence of address objects in the address
block; OR
* a single address in the address block. * a single address object in the address block.
<tlv> is defined by: <tlv> is defined by:
<tlv> = <tlv-type> <tlv> := <tlv-type>
<tlv-semantics> <tlv-semantics>
<tlv-type-ext>? <tlv-type-ext>?
<index-start>? {<index-start><index-stop>?}?
<index-stop>? {<length><value>?}?
<length>?
<value>?
where: where:
<tlv-type> is an 8 bit field, specifying the type of the TLV, <tlv-type> is an 8 bit unsigned integer field, specifying the type
specific to the TLV kind (i.e. packet, message, or address block of the TLV, specific to the TLV kind (i.e. packet, message, or
TLV). address block 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 (thastypeext): if cleared ('0'), then <tlv-type-ext> is not bit 0 (thastypeext): If cleared ('0'), then <tlv-type-ext> is not
included in the <tlv>. If set ('1'), then <tlv-type-ext> is included in the <tlv>. If set ('1'), then <tlv-type-ext> is
included in the <tlv>. included in the <tlv>.
bit 1 (thasextlen) and bit 2 (tnovalue): MUST NOT both be set bit 1 (thassingleindex) and bit 2 (thasmultiindex): Are
('1'). Otherwise, they are interpreted according to Table 3. interpreted according to Table 3. A combination not shown in
that table MUST NOT be used. Both bits MUST be cleared ('0')
in packet and message TLVs.
+------------+----------+--------------+--------------+ bit 3 (thasvalue) and bit 4 (thasextlen): Are interpreted
| thasextlen | tnovalue | <length> | <value> | according to Table 4. A combination not shown in that table
+------------+----------+--------------+--------------+ MUST NOT be used.
| 0 | 0 | 8 bits | included |
| | | | |
| 1 | 0 | 16 bits | included |
| | | | |
| 0 | 1 | not included | not included |
+------------+----------+--------------+--------------+
Table 3 bit 5 (tismultivalue): This bit serves to specify how the <value>
field is interpreted, as specified below. This bit MUST be
cleared ('0') in packet and message TLVs, if the thasmultiindex
bit is cleared ('0'), or if the thasvalue bit is cleared ('0').
bit 3 (tnoindex) and bit 4 (thassingleindex): MUST NOT both be bits 6-7: Are RESERVED, and SHOULD each be cleared ('0') on
set ('1'). The former MUST be set ('1') and the latter MUST be transmission, and SHOULD be ignored on reception.
cleared ('0') for packet or message TLVs. They are interpreted
according to Table 4.
+----------+-----------------+---------------+--------------+ +-----------------+----------------+---------------+--------------+
| tnoindex | thassingleindex | <index-start> | <index-stop> | | thassingleindex | thasmultiindex | <index-start> | <index-stop> |
+----------+-----------------+---------------+--------------+ +-----------------+----------------+---------------+--------------+
| 0 | 0 | included | included | | 0 | 0 | not included | not included |
| | | | | | | | | |
| 1 | 0 | not included | not included | | 1 | 0 | included | not included |
| | | | | | | | | |
| 0 | 1 | included | not included | | 0 | 1 | included | included |
+----------+-----------------+---------------+--------------+ +-----------------+----------------+---------------+--------------+
Table 4
bit 5 (tismultivalue): this bit serves to specify how the <value> Table 3: Interpretation of the thassingleindex and thasmultiindex
field is interpreted, as specified below. This bit MUST be bits
cleared ('0') for packet or message TLVs, if the +-----------+------------+-------------+----------------------------+
thassingleindex bit is set ('1'), or if the tnovalue bit is set | thasvalue | thasextlen | <length> | <value> |
('1'). +-----------+------------+-------------+----------------------------+
| 0 | 0 | not | not included |
| | | included | |
| | | | |
| 1 | 0 | 8 bits | included unless <length> |
| | | | is zero |
| | | | |
| 1 | 1 | 16 bits | included unless <length> |
| | | | is zero |
+-----------+------------+-------------+----------------------------+
bits 6-7: are RESERVED and MUST each be cleared ('0') to be in Table 4: Interpretation of the thasvalue and thasextlen bits
accordance with this version of the specification.
<tlv-type-ext> is an 8 bit field, specifying an extension of the TLV <tlv-type-ext> is an 8 bit unsigned integer field, specifying an
type, specific to the TLV type and kind (i.e. packet, message, or extension of the TLV type, specific to the TLV type and kind (i.e.
address block TLV). packet, message, or address block TLV).
tlv-type-ext is a variable, defined to equal <tlv-type-ext> 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-type-ext; * 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, in an address block TLV
interpreted as follows. only, are each an 8 bit unsigned integer field.
index-start and index-stop are variables, defined according to index-start and index-stop are variables, defined according to
Table 5. The variable end-index is defined as follows: Table 5. 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
+----------+-----------------+---------------+---------------+
| tnoindex | thassingleindex | index-start = | index-stop = | An address block TLV applies to the address objects from position
+----------+-----------------+---------------+---------------+ index-start to position index-stop (inclusive) in the address
| 0 | 0 | <index-start> | <index-stop> | block, where the first address object has position zero.
+-----------------+----------------+----------------+---------------+
| thassingleindex | thasmultiindex | index-start := | index-stop := |
+-----------------+----------------+----------------+---------------+
| 0 | 0 | 0 | end-index |
| | | | | | | | | |
| 1 | 0 | 0 | end-index | | 1 | 0 | <index-start> | <index-start> |
| | | | | | | | | |
| 0 | 1 | <index-start> | <index-start> | | 0 | 1 | <index-start> | <index-stop> |
+----------+-----------------+---------------+---------------+ +-----------------+----------------+----------------+---------------+
Table 5
For an address block TLV, the TLV applies to the addresses from Table 5: Interpretation of the thassingleindex and thasmultiindex
position index-start to position index-stop (inclusive) in the bits
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 an 8 or 16 bit field according to Table 3. <length> is omitted or is an 8 or 16 bit unsigned integer field
If the tismultivalue bit is set ('1') then <length> MUST be an according to Table 4. If the tismultivalue bit is set ('1') then
integral multiple of number-values, and the variable single-length <length> MUST be an integral multiple of number-values, and the
is defined by: variable single-length is defined by:
* single-length = <length> / number-values * single-length := <length> / number-values
If the tismultivalue bit is cleared ('0'), then the variable If the tismultivalue bit is cleared ('0'), then the variable
single-length is defined by: single-length is defined by:
* single-length = <length> * single-length := <length>
<value> if present (see Table 3) is a field of length <length> <value> if present (see Table 4) 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 address objects from positions index-start to index-stop,
tismultivalue bit is cleared ('0') then the whole of this field is inclusive. If the tismultivalue bit is cleared ('0') then the
associated with each of the indicated addresses. If the whole of this field is associated with each of the indicated
tismultivalue bit is set ('1') then this field is divided equally address objects. If the tismultivalue bit is set ('1') then this
into number-values fields, each of length single-length octets and field is divided equally into number-values fields, each of length
these are associated, in order, with the indicated addresses. single-length octets and these are associated, in order, with the
indicated address objects.
5.5.2. TLV Inclusion and Constraints 5.4.2. TLV Inclusion and Constraints
A TLV associates an attribute with a packet, a message or one or more A TLV associates an attribute with a packet, a message or one or more
consecutive network addresses in an address block. The consecutive address objects in an address block. The interpretation
interpretation and processing of this attribute, and the relationship and processing of this attribute, and the relationship (including
(including order of processing) between different attributes order of processing) between different attributes associated with the
associated with the same entity MUST be defined by a protocol which same entity MUST be defined by a protocol which uses this
uses this specification. specification.
If the appropriate semantics bit (pnouniord for a packet TLV block, If the appropriate semantics bit (pnouniord for a packet TLV block,
mnouniord for a message TLV block or an address TLV block) is clear mnouniord for a message TLV block or an address TLV block) is clear
('0'), then the following constraints MUST be respected. These bits ('0'), then the following constraints MUST be respected. These bits
MUST always be clear ('0') unless a protocol using this specification MUST always be clear ('0') unless a protocol using this specification
defines otherwise. Protocols SHOULD only define use of these bits defines otherwise. Protocols SHOULD only define use of these bits
when necessary, and then MUST indicate what constraints do apply if when necessary, and then MUST indicate what constraints do apply if
each of the indicated bits is set ('1'); each of these constraints each of the indicated bits is set ('1'); each of these constraints
SHOULD be retained unless otherwise necessary. SHOULD be retained unless otherwise necessary.
o TLVs in the same TLV block are sorted in non-descending tlv- o TLVs in the same TLV block are sorted in non-descending tlv-
fulltype order. fulltype order.
o Two or more address TLVs with the same tlv-fulltype in the same o Two or more address TLVs with the same tlv-fulltype in the same
message are not associated with the same network address. message are not associated with the same value of address object.
o TLVs with the same tlv-fulltype associated with the same address o TLVs with the same tlv-fulltype associated with the same address
block are sorted in ascending index-start order. block are sorted in ascending index-start order.
In addition, packet and message TLVs MUST be defined so as to In addition, packet and message TLVs MUST be defined so as to
indicate whether two such TLVs with the same tlv-fulltype are, or are indicate whether two such TLVs with the same tlv-fulltype are, or are
not, allowed in the same packet or message TLV block, respectively. not, allowed in the same packet or message TLV block, respectively.
Note that the above constrains only the encoding of TLVs in a TLV Note that the above constrains only the encoding of TLVs in a TLV
block for transmission, and do specifically NOT mandate any given block for transmission, and do specifically NOT mandate any given
order of processing or interpretation by a protocol of the TLVs and order of processing or interpretation by a protocol of the TLVs and
the entities to which these are associated. the entities to which these are associated.
Respecting the constraints above allows parsing and verification of a Respecting the constraints above allows parsing and verification of a
TLV block in a single pass and allows terminating the search for a TLV block in a single pass and allows terminating the search for a
TLV with a specific type without traversing the entire TLV block. TLV with a specific type without traversing the entire TLV block.
The constraints on address block TLVs ensure that encoded information The constraints on address block TLVs ensure that encoded information
(entity-attributes) can be unambiguously decoded. (entity-attributes) can be unambiguously decoded.
5.6. Malformed Elements 5.5. 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
syntactical specification (including if there are insufficient octets syntactical specification (including if there are insufficient octets
available when a length is specified, in particular if there are available when a length is specified, in particular if there are
fewer than pkt-size octets overall) or if a constraint (including, fewer than pkt-size octets overall) or if a constraint (including,
but not only, those specified in Section 5.5.2) specified as one but not only, those specified in Section 5.4.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.7. Padding
Packet headers and messages MAY be padded to ensure 32 bit alignment
of each message contained within the packet and of the overall packet
length. Padding MAY also be used to ensure that all packets and/or
messages have the same size.
All elements are an integer multiple of octets, hence padding can be
accomplished by inserting an integer number of <pad-octet> elements
after the element that is to be 32 bit aligned.
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
size of the preceding elements, produces an integer multiple of 4.
<pad-octet> is an 8 bit field with all bits cleared ('0').
There is no need to indicate if padding is included, since a <pad-
octet> will always precede either a message or the end of the packet.
In the former case, the start of a message is indicated by the next
non-zero octet parsed.
The padding after a message may be freely changed when a message is
forwarded without affecting the message.
6. IANA Considerations 6. IANA Considerations
6.1. Message Types 6.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.
5-127 can be allocated using standards action [3]. Additionally,
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 | | 128-255 | Reserved for private/local use. |
+------+------------------------+ +---------+---------------------------------+
Table 6 Table 6: Message Types
Message type 0 MUST NOT be allocated because a zero-octet signifies a Future values in the range 1-127 can be allocated using standards
packet header and zero-octets are used for padding. Message types 1 action [RFC2434]. Message type 0 MUST NOT be allocated because a
to 4 are reserved because they are used by OLSR [4], which uses a zero octet signifies a packet header.
compatible packet/message header format.
6.2. Packet TLV Types 6.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 initial
assignments. assignments as specified in Table 7.
+---------+---------------------------------+
| Type | Description |
+---------+---------------------------------+
| 128-255 | Reserved for private/local use. |
+---------+---------------------------------+
Table 7: Packet TLV Types
Future values in the range 0-127 can be allocated using standards Future values in the range 0-127 can be allocated using standards
action [3], respecting the following guidelines: action [RFC2434], respecting the following guidelines:
values 0-7 - MUST NOT be assigned except when a documented need values 0-7 - MUST NOT be assigned except when a documented need
exists that TLVs of a given type are required to appear before all exists that TLVs of a given type are required to appear before all
other TLVs in the TLV block as encoded for transmission. Note 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 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 however automatically translate into a need for the TLV to appear
before all other TLVs in the TLV block - the order in which TLVs before all other TLVs in the TLV block - the order in which TLVs
are to be processed MUST be defined, if applicable, in the are to be processed MUST be defined, if applicable, in the
protocols using this specification. protocols using this specification.
values 8-127 - no constraints. values 8-127 - no constraints.
Additionally, values in the range 128-255 are reserved for private/ If a packet TLV type is allocated then a new registry for type
local use. If a packet TLV type is allocated then a new registry for extensions of that type must be created. A document which defines a
type extensions of that type must be created. A document which packet TLV type MUST also specify the mechanism by which its type
defines a packet TLV type MUST also specify the mechanism by which extensions are allocated, from among those in [RFC2434].
its type extensions are allocated, from among those in [3].
6.3. Message TLV Types 6.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 initial
assignments. assignments as specified in Table 8.
+---------+---------------------------------+
| Type | Description |
+---------+---------------------------------+
| 128-255 | Reserved for private/local use. |
+---------+---------------------------------+
Table 8: Message TLV Types
Future values in the range 0-127 can be allocated using standards Future values in the range 0-127 can be allocated using standards
action [3], respecting the following guidelines: action [RFC2434], respecting the following guidelines:
values 0-7 - MUST NOT be assigned except when a documented need values 0-7 - MUST NOT be assigned except when a documented need
exists that TLVs of a given type are required to appear before all exists that TLVs of a given type are required to appear before all
other TLVs in the TLV block as encoded for transmission. Note 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 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 however automatically translate into a need for the TLV to appear
before all other TLVs in the TLV block - the order in which TLVs before all other TLVs in the TLV block - the order in which TLVs
are to be processed MUST be defined, if applicable, in the are to be processed MUST be defined, if applicable, in the
protocols using this specification. protocols using this specification.
values 8-127 - no constraints. values 8-127 - no constraints.
Additionally, values in the range 128-255 are reserved for private/ If a message TLV type is allocated then a new registry for type
local use. If a message TLV type is allocated then a new registry extensions of that type must be created. A document which defines a
for type extensions of that type must be created. A document which message TLV type MUST also specify the mechanism by which its type
defines a message TLV type MUST also specify the mechanism by which extensions are allocated, from among those in [RFC2434].
its type extensions are allocated, from among those in [3].
6.4. Address Block TLV Types 6.4. Address Block TLV Types
A new registry for address block TLV types must be created, with no A new registry for address block TLV types must be created, with
initial assignments. initial assignments as specified in Table 9.
+---------+---------------------------------+
| Type | Description |
+---------+---------------------------------+
| 128-255 | Reserved for private/local use. |
+---------+---------------------------------+
Table 9: Address Block TLV Types
Future values in the range 0-127 can be allocated using standards Future values in the range 0-127 can be allocated using standards
action [3], respecting the following guidelines: action [RFC2434], respecting the following guidelines:
values 0-7 - MUST NOT be assigned except when a documented need values 0-7 - MUST NOT be assigned except when a documented need
exists that TLVs of a given type are required to appear before all exists that TLVs of a given type are required to appear before all
other TLVs in the TLV block as encoded for transmission. Note 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 that the need for a TLV to be processed before other TLVs does not
however automatically translate into a need for the TLV appearing however automatically translate into a need for the TLV appearing
before all other TLVs in the TLV block - the order in which TLVs before all other TLVs in the TLV block - the order in which TLVs
are to be processed MUST be defined, if applicable, in the are to be processed MUST be defined, if applicable, in the
protocols using this specification. protocols using this specification.
values 8-127 - no constraints. values 8-127 - no constraints.
Additionally, values in the range 128-255 are reserved for private/ If an address block TLV type is allocated then a new registry for
local use. If an address block TLV type is allocated then a new type extensions of that type must be created. A document which
registry for type extensions of that type must be created. A defines an address block TLV type MUST also specify the mechanism by
document which defines an address block TLV type MUST also specify which its type extensions are allocated, from among those in
the mechanism by which its type extensions are allocated, from among [RFC2434].
those in [3].
7. Security Considerations 7. Security Considerations
This specification does not describe a protocol; it describes a This specification does not describe a protocol; it describes a
packet format. As such it does not specify any security packet format. As such it does not specify any security
considerations, these are matters for a protocol using this considerations, these are matters for a protocol using this
specification. However two mechanisms which are enabled by this specification. However two mechanisms which are enabled by this
specification, and may form part of a security approach in a protocol specification, and may form part of a security approach in a protocol
using this specification, are described in Section 8.1. There is using this specification, are described in Section 8.1. There is
however no requirement that a protocol using this specification however no requirement that a protocol using this specification
should use either. should use either.
7.1. Security Suggestions 7.1. Authentication Suggestions
The security suggestions made here, are based on that: The authentication suggestions made here, are based on the intended
usage in Appendix A, specifically that:
o Messages are designed to be carriers of protocol information and o Messages are designed to be carriers of protocol information and
MAY, at each hop, be forwarded and/or processed by the protocol MAY, at each hop, be forwarded and/or processed by the protocol
using this specification. using this specification.
o Packets are designed to carry a number of messages between o Packets are designed to carry a number of messages between
neighboring nodes in a single transmission and over a single neighboring nodes in a single transmission and over a single
logical hop. logical hop.
Consequently: Consequently:
o For forwarded messages where the message is unchanged by o For forwarded messages where the message is unchanged by
forwarding nodes, then end-to-end security MAY be implemented, forwarding nodes, then end-to-end security MAY be implemented,
between nodes with an existing security association, by including between nodes with an existing security association, by including
a suitable message TLV containing a cryptographic signature in the a suitable message TLV containing a cryptographic signature in the
message. Since <hop-count> and <hop-limit> are the only fields message. Since <hop-count> and <hop-limit> are the only fields
that may be modified when such a message is forwarded in this that should be modified when such a message is forwarded in this
manner, this signature can be calculated based on the entire manner, this signature can be calculated based on the entire
message, including the message header, with the <hop-count> and message, including the message header, with the <hop-count> and
<hop-limit> fields set to zero ('0') if present. <hop-limit> fields set to 0 if present.
o Hop-by-hop packet level security MAY be implemented, between nodes o Hop-by-hop packet level security MAY be implemented, between nodes
with an existing security association, by including a suitable with an existing security association, by including a suitable
packet TLV containing a cryptographic signature to the packet. packet TLV containing a cryptographic signature to the packet.
Since packets are received as transmitted, this signature can be Since packets are received as transmitted, this signature can be
calculated based on the entire packet, or on parts thereof as calculated based on the entire packet, or on parts thereof as
appropriate. appropriate.
8. References 8. References
8.1. Normative References 8.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[2] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Considerations Section in RFCs", RFC 2434, BCP 26, October 1998. IANA Considerations Section in RFCs", RFC 2434, BCP 26,
October 1998.
8.2. Informative References 8.2. Informative References
[4] Clausen, T. and P. Jacquet, "The Optimized Link State Routing [RFC3626] Clausen, T. and P. Jacquet, "The Optimized Link State
Protocol", RFC 3626, October 2003. Routing Protocol", RFC 3626, October 2003.
Appendix A. Examples Appendix A. Intended Usage
The packet and message format specified in this document is designed
to carry MANET routing protocol messages and signals between MANET
routers, and to support scope limited diffusion (flooding) as well as
point-to-point delivery.
Specifically:
o Packets are transmitted over a single logical hop and are not
forwarded. Messages are designed to be able to be forwarded over
one or more logical hops, in a new packet for each logical hop.
Each logical hop may consist of one or more IP hops. Packets may
contain a different combination of messages for each logical hop.
Packets may be formed from messages from more than one MANET
routing protocol; the use of a single message type space for all
such protocols allows these messages to be separated by protocol.
o Scope limited flooding is supported for messages thus:
* If the mhasorig and mhasseqnum and bits in the <msg-semantics>
field are both set ('1') then the message header provides for
duplicate suppression, using the identifier consisting of the
message's <msg-orig-addr>, <msg-seq-num>, and, if the
mistypedep bit in the <msg-semantics> field is set ('1), <msg-
type>. These serve to uniquely identify the message in the
network within the time period until <msg-seq-num> is repeated,
i.e. wraps around to a matching value if used sequentially.
* If the mhashoplimit bit in the <msg-semantics> field is set
('1'), then the message header provides the information to make
forwarding decisions for scope limited diffusion (flooding).
This may be by any appropriate flooding mechanism specified by
a protocol using this specification.
* <msg-hop-limit> SHOULD, if present, be decremented, usually by
one, if the message is forwarded.
* <msg-hop-count> SHOULD, if present, be incremented, usually by
one, if the message is forwarded.
Appendix B. Compatibility Requirements for Future Versions
This specification defines packets and messages with version zero
(0).
Although this specification does not define packet and message
versions greater than zero, any future version of this specification
MUST, for backwards compatibility, satisfy the following:
o If the packet version is greater than zero, then a <pkt-header>
element MUST be included in the packet, which MUST include a <pkt-
version> element indicating the packet version.
o If the message version is greater than zero, then a <msg-version>
element MUST be included in the <msg-header>, indicating the
message version.
o The initial octets of a <pkt-header>, up to and including <pkt-
version>, MUST be preserved as in this specification, in order
that packets of versions greater than zero can be correctly
recognized (and discarded) by implementations of this version of
this specification.
o The initial octets of a <msg-header>, up until and including <msg-
length>, MUST be preserved as in this specification, in order that
messages of versions greater than zero can be correctly recognized
(and discarded) by implementations of this version of this
specification.
Appendix C. Examples
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 C.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 anohead and anotail bits of the in particular one in which the ahashead and ahasfulltail bits of the
semantics octet are set, and hence head-length = 0, tail-length = 0, semantics octet are cleared ('0'), and hence head-length = 0, tail-
mid-length = address-length, and the address block consists of the length = 0, mid-length = address-length, and (with no address
number of addresses, the semantics octet with value 3, and a list of prefixes) the address block consists of the number of addresses, the
the uncompressed addresses. This is also the most efficient way to semantics octet with value 0, and a list of the uncompressed
represent a single address, and the only way to represent, for addresses. This is also the most efficient way to represent a single
example, a.b.c.d and e.f.g.h in one address block. address, and the only way to represent, for 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;
* <addr-semantics> has anotail set (value 2); * <addr-semantics> has ahashead set (value 1);
* <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 1 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;
* <addr-semantics> has anohead set (value 1); * <addr-semantics> has ahasfulltail set (value 2);
* <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 2 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;
* <addr-semantics> = 0. * <addr-semantics> has ahashead and ahasfulltail set (value 3).
The address block is then 2 0 1 a 2 d e b c (9 octets). The address block is then 2 3 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;
* <addr-semantics> has ahaszerotail set (value 4); * <addr-semantics> has ahashead and ahaszerotail set (value 5);
* <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 5 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;
* <addr-semantics> has anohead and ahaszerotail set (value 5); * <addr-semantics> has ahaszerotail set (value 4);
* <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 4 2 a b c d (7 octets).
o To include a.b.0.0/n and c.d.0.0/n: o To include a.b.0.0/n and c.d.0.0/n:
* head-length = 0; * head-length = 0;
* tail-length = 2; * tail-length = 2;
* mid-length = 2; * mid-length = 2;
* <addr-semantics> has anohead, ahaszerotail and ahassingleprelen * <addr-semantics> has ahaszerotail and ahassingleprelen set
set (value 13); (value 12);
* <head> and <tail> are omitted. * <head> and <tail> are omitted.
The address block is then 2 13 2 a b c d n (8 octets). The address block is then 2 12 2 a b c d n (8 octets).
o To include a.b.0.0/n and c.d.0.0/m: o To include a.b.0.0/n and c.d.0.0/m:
* head-length = 0; * head-length = 0;
* tail-length = 2; * tail-length = 2;
* mid-length = 2; * mid-length = 2;
* <addr-semantics> has anohead, ahaszerotail and ahasmultiprelen * <addr-semantics> has ahaszerotail and ahasmultiprelen set
set (value 21); (value 20);
* <head> and <tail> are omitted. * <head> and <tail> are omitted.
The address block is then 2 21 2 a b c d n m (9 octets). The address block is then 2 20 2 a b c d n m (9 octets).
A.2. TLV Examples C.2. TLV Examples
Assuming the definition of an address block TLV with type EXAMPLE1 Assuming the definition of an address block TLV with type EXAMPLE1
(and no type extension) which has single octet single values, then if (and no type extension) which has single octet values per address,
values a, a, b and c are to be associated with the four addresses in then if values a, a, b and c are to be associated with the four
the preceding address block, where c is a default value that can be addresses in the preceding address block, where c is a default value
omitted, then this can be done in a number of ways. Possible that can be omitted, then this can be done in a number of ways.
examples are:
Examples:
o Using one multivalue TLV covering all of the addresses: o Using one multivalue TLV covering all of the addresses:
* <tlv-semantics> has tnoindex and tismultivalue set (value 40); * <tlv-semantics> has thasvalue and tismultivalue set (value 36);
* <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 EXAMPLE1 40 4 a a b c (7 octets). * The TLV is then EXAMPLE1 36 4 a a b c (7 octets).
o Using one multivalue TLV omitting the last address: o Using one multivalue TLV omitting the last address:
* <tlv-semantics> has tismultivalue set (value 32); * <tlv-semantics> has thasvalue, thasmultiindex and tismultivalue
set (value 52);
* <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 EXAMPLE1 32 0 2 3 a a b (8 octets). * The TLV is then EXAMPLE1 52 0 2 3 a a b (8 octets).
o Using two single value TLVs, omitting the last address. First: o Using two single value TLVs, omitting the last address. First:
* <tlv-semantics> = 0; * <tlv-semantics> has thasvalue and thasmultiindex set (value
20);
* <index-start> = 0; * <index-start> = 0;
* <index-stop> = 1; * <index-stop> = 1;
* <length> = 1; * <length> = 1;
* <value> = a. * <value> = a.
* The TLV is then EXAMPLE1 0 0 0 1 1 a (6 octets). * The TLV is then EXAMPLE1 20 0 1 1 a (6 octets).
Second: Second:
* <tlv-semantics> has thassingleindex set (value 16); * <tlv-semantics> has thasvalue and thassingleindex set (value
12);
* <index-start> = 2; * <index-start> = 2;
* <index-stop> is omitted; * <index-stop> is omitted;
* <length> = 1; * <length> = 1;
* <value> = b. * <value> = b.
* The TLV is then EXAMPLE1 16 2 1 b (5 octets). * The TLV is then EXAMPLE1 12 2 1 b (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 EXAMPLE2 Assuming the definition of an address block TLV with type EXAMPLE2
(and no type extension) which has no value, which is to be associated (and no type extension) which has no value, which is to be associated
with the second and third addresses in an address block, then this with the second and third addresses in an address block, then this
can be indicated with a single TLV: can be indicated with a single TLV:
o <tlv-semantics> has tnovalue set (value 4); o <tlv-semantics> has thasmultiindex set (value 16);
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 EXAMPLE2 4 1 2 (4 octets). o The TLV is then EXAMPLE2 16 1 2 (4 octets).
Assuming the definition of a message TLV with type EXAMPLE3 (and no Assuming the definition of a message TLV with type EXAMPLE3 (and no
type extension) which can take a value field of any length, for such type extension) which can take a value field of any length, for such
a TLV with 8 octets of data (a to h): a TLV with 8 octets of data (a to h):
o <tlv-semantics> has tnoindex set (value 8); o <tlv-semantics> has thasvalue set (value 4);
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 EXAMPLE3 8 8 a b c d e f g h (11 octets). o The TLV is then EXAMPLE3 4 8 a b c d e f g h (11 octets).
If, in this example, the number of data octets were 256 or greater If, in this example, the number of data octets were 256 or greater
then <tlv-semantics> would also have thasextlen set and have value then <tlv-semantics> would also have thasextlen set and have value 6.
10. The length would require two octets (most significant first). The length would require two octets (most significant first). The
The TLV length would be 4 + N octets, where N is the number of data TLV length would be 4 + N octets, where N is the number of data
octets (it can be 3 + N octets if N is 255 or less). octets (it can be 3 + N octets if N is 255 or less).
Appendix B. Illustrations Appendix D. 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 Examples with version fields are omitted, as not needed when using
this version of this specification (although permitted). this version of this specification (although permitted).
Bits labeled Rsv or R must be cleared ('0'). Bits labeled C, N, or M Bits labeled Rsv or R must be cleared ('0'). Bits labeled C, N, or M
may be cleared ('0') or set ('1'). Octets labeled Padding must be may be cleared ('0') or set ('1').
zero ('0'), and are optional. (They have been omitted where not
needed for alignment.)
Appendix B.1. Packet D.1. Packet
Possible options for the <packet> element. These are differentiated
by their second (semantics) octet, except the last, which starts with
a non-zero octet. The packet may include any number (zero or more)
of messages, except in the last case, when there must be one or more
messages. The number of messages is determined from the size of the
packet (either the <pkt-size> field if present, or from the network
or transport protocol employed).
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| Rsv |C|0|0|0|0| Packet Sequence Number | |0 0 0 0 0 0 0 0| Rsv |C|0|0|0|0| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Message |
| +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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| Rsv |C|0|0|1|0| Packet Size | |0 0 0 0 0 0 0 0| Rsv |C|0|0|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packet Sequence Number | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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| Rsv |C|0|1|0|0| Padding | |0 0 0 0 0 0 0 0| Rsv |C|0|1|0|0| Packet Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message + Padding | | Message |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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| Rsv |C|0|1|1|0| Packet Size | |0 0 0 0 0 0 0 0| Rsv |C|0|1|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packet Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| | | +-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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| Rsv |C|1|0|0|0| Packet Sequence Number | |0 0 0 0 0 0 0 0| Rsv |C|1|0|0|0| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Packet TLV Block | | Packet TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ |
| | | Message |
| Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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| Rsv |C|1|0|1|0| Packet Size | |0 0 0 0 0 0 0 0| Rsv |C|1|0|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packet Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Packet TLV Block | | Packet TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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| Rsv |C|1|1|0|0| | |0 0 0 0 0 0 0 0| Rsv |C|1|1|0|0| Packet Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Packet TLV Block | | Packet TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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| Rsv |C|1|1|1|0| Packet Size | |0 0 0 0 0 0 0 0| Rsv |C|1|1|1|0| Packet Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packet Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Packet TLV Block | | Packet TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ |
| | | Message |
| Message + Padding |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 + Padding | | Message |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message + Padding | | Message |
| +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B.2. Message and Padding D.2. Message
Possible options for the <message> element. These are differentiated
by their second (semantics) octet. The length of the message body is
determined using the <msg-size> field, which includes all the fields
shown.
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 |R|C|N|0|0|0|0|0| Message Size | | Message Type |R|C|N|0|0|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 Type |R|C|0|0|0|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|0|0|1|0|0| Message Size | | Message Type |R|C|N|0|0|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|0|0|0|1|1|0| Message Size | | Message Type |R|C|N|0|0|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | Message Sequence Number | | | Hop Limit | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|0|1|0|0|0| Message Size | | Message Type |R|C|N|0|0|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Message Sequence Number | | | Hop Limit | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|0|1|0|1|0| Message Size | | Message Type |R|C|N|0|1|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Message Sequence Number | | | Hop Count | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|0|1|1|0|0| Message Size | | Message Type |R|C|N|0|1|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Sequence Number | | | Hop Count | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|0|1|1|1|0| Message Size | | Message Type |R|C|N|0|1|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Sequence Number | | | Hop Limit | Hop Count | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|1|0|0|0|0| Message Size | | Message Type |R|C|N|0|1|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | | | Hop Limit | Hop Count | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|1|0|0|1|0| Message Size | | Message Type |R|C|N|1|0|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | | | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|1|0|1|0|0| Message Size | | Message Type |R|C|N|1|0|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | | | Message Sequence Number | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|1|0|1|1|0| Message Size | | Message Type |R|C|N|1|0|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | | | Hop Limit | Message Sequence Number | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|1|1|0|0|0| Message Size | | Message Type |R|C|N|1|0|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | | | Hop Limit | Message Sequence Number | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|1|1|0|1|0| Message Size | | Message Type |R|C|0|1|1|0|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | | | Hop Count | Message Sequence Number | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 |R|C|N|1|1|1|0|0| Message Size | | Message Type |R|C|N|1|1|0|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Count | Message Sequence Number | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 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 Type |R|C|0|1|1|1|0|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Message Body |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type |R|C|N|1|1|1|1|0| Message Size | | Message Type |R|C|N|1|1|1|1|0| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message Body | | Message Body |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Padding | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B.3. Message Body D.3. Message Body
Format of a message body (the <message> element excluding its initial
<msg-header> element). The message may include any number (zero or
more) of address block and address TLV block pairs.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Message TLV Block | | Message TLV Block |
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
skipping to change at page 43, line 5 skipping to change at page 47, line 5
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| Address TLV Block | | Address TLV Block |
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B.4. Address Block D.4. Address Block
Possible options for the <addr-block> element. These are
differentiated by their second (semantics) octet. The number of
<mid> elements is equal to the number of addresses (except when mid-
length is zero, when there are no <mid> elements). Where a variable
number of <prefix-length> fields is shown, their number is equal to
the number of addresses.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|0|0|0|0| Head Length | Head | | Number Addrs | Rsv |0|0|0|0|0| Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | | | Mid (cont) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|0|0|0|1| Tail Length | Tail | | Number Addrs | Rsv |0|0|0|0|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tail (cont) | Mid | | | Head (cont) | Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|0|0|1|0| Head Length | Head | | Number Addrs | Rsv |0|0|0|1|0| Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Mid | | | Tail (cont) | Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|0|0|1|1| Mid | | Number Addrs | Rsv |0|0|0|1|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | | | Head (cont) | Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|0|1|0|0| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
: ... :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|0|1|0|1| Tail Length | Mid | | Number Addrs | Rsv |0|0|1|0|0| Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | | | Mid (cont) | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|1|0|0|0| Head Length | Head | | Number Addrs | Rsv |0|0|1|0|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Tail | | Head (cont) | Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Length | | Mid |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|1|0|0|1| Tail Length | Tail | | Number Addrs | Rsv |0|1|0|0|0| Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tail (cont) | Mid | | | Mid (cont) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|1|0|1|0| Head Length | Head | | Number Addrs | Rsv |0|1|0|0|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Mid | | | Head (cont) | Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length | | | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|1|0|1|1| Mid | | Number Addrs | Rsv |0|1|0|1|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | | | Head (cont) | Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | Prefix Length | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|1|1|0|0| Head Length | Head | | Number Addrs | Rsv |0|1|0|1|0| Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tail (cont) | Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |0|1|1|0|1| Tail Length | Mid | | Number Addrs | Rsv |0|1|1|0|0| Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | | | Mid (cont) | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length | | | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |1|0|0|0|0| Head Length | Head | | Number Addrs | Rsv |0|1|1|0|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Tail | | Head (cont) | Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | | | |
: ... :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |1|0|0|0|0| Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Length | | | Mid (cont) | Prefix Length | |
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
: ... : : ... :
| +-+-+-+-+-+-+-+-+ | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Prefix Length | | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |1|0|0|0|1| Tail Length | Tail | | Number Addrs | Rsv |1|0|0|0|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tail (cont) | Mid | | | Head (cont) | Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length | | | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
skipping to change at page 48, line 4 skipping to change at page 52, line 23
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length | | | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Prefix Length | | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |1|0|0|1|0| Head Length | Head | | Number Addrs | Rsv |1|0|0|1|0| Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Mid | | | Tail (cont) | Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length | | | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
skipping to change at page 48, line 23 skipping to change at page 53, line 4
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length | | | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Prefix Length | | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |1|0|0|1|1| Mid | | Number Addrs | Rsv |1|0|0|1|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | | | Head (cont) | Tail Length | Tail |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | | | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | Prefix Length | | | Prefix Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ |
| |
: ... : : ... :
| | | +-+-+-+-+-+-+-+-+
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Prefix Length | | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |1|0|1|0|0| Head Length | Head | | Number Addrs | Rsv |1|0|1|0|0| Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | |
+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | Prefix Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Prefix Length | | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number Addrs | Rsv |1|0|1|0|1| Tail Length | Mid | | Number Addrs | Rsv |1|0|1|0|1| Head Length | Head |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head (cont) | Tail Length | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid (cont) | |
+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Mid | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | Prefix Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
: ... : : ... :
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Prefix Length | | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B.5. TLV Block D.5. TLV Block
Format if a <tlv-block> element. There may be any number (zero or
more) of TLVs, with total length (in octets) equal to the length
field.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | | | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| TLV | | TLV |
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | | | | |
skipping to change at page 50, line 29 skipping to change at page 55, line 5
| | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| | | |
| TLV | | TLV |
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix B.6. TLV D.6. TLV
Possible options for the <tlv> element. These are differentiated by
their second (semantics) octet. If there are no index fields then
this may be a packet, message or address block TLV, if there is one
or two index fields then this must be an address block TLV. The
length field gives the length of the value field (in 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type |Rsv|M|0|0|0|0|0| Index Start | Index Stop | | Type |Rsv|0|0|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | |
+-+-+-+-+-+-+-+-+ |
| 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| Type Ext | Index Start | | Type |Rsv|0|0|0|0|0|1| Type Ext |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| 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|0| Index Start | Index Stop | | Type |Rsv|0|0|0|0|1|0| Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| 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| Type Ext | Index Start | | Type |Rsv|0|0|0|0|1|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| 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| Type Ext | 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
skipping to change at page 53, line 4 skipping to change at page 56, line 35
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| Type Ext | 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type |Rsv|M|0|1|0|1|0| Length | | Type |Rsv|0|0|1|0|1|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|M|0|1|0|1|1| Type Ext | Length | | Type |Rsv|0|0|1|0|1|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length (cont) | | | 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|1|1|0|0| | Type |Rsv|M|0|1|1|0|0| Index Start | Index Stop |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | |
+-+-+-+-+-+-+-+-+ |
| 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|1| Type Ext | | Type |Rsv|M|0|1|1|0|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| 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|0| Index Start | Length | | Type |Rsv|M|1|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|0|1|0|0|0|1| Type Ext | Index Start | | Type |Rsv|M|1|1|0|0|1| Type Ext | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | | | 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|1|0|0|1|0| Index Start | Length | | Type |Rsv|0|1|1|0|1|0| Index Start | 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|1|0|0|1|1| Type Ext | Index Start | | Type |Rsv|0|1|1|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|M|1|1|1|0|0| Index Start | Index Stop |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| 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|1| Type Ext | Index Start | | Type |Rsv|M|1|1|1|0|1| Type Ext | Index Start |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index Stop | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
| Value |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+
Appendix C. Complete Example Appendix E. 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 version zero, The packet header has the phasseqnum bit of its semantics octet 4
a packet sequence number, but no packet TLV block. set, and hence has version zero, no packet size (this is taken from
the network or transport protocol carrying this packet), a packet
sequence number, and no packet TLV block.
The packet contains a single message. This message has semantics The packet contains a single message with length 55 octets. This
octet 0, and hence has a complete message header, other than version message has the mhasorig, mhashoplimit, mhashopcount and mhasseqnum
(which is zero), including originator address, hop limit, hop count bits of its semantics octet 30 set, and hence has version zero and
and message sequence number (which is type independent). The message includes an originator address, a hop limit, a hop count and a
has a message TLV block with content length 9 octets, containing a message sequence number (which is type independent). The message has
single message TLV. This TLV has the tnoindex bit of its semantics a message TLV block with content length 9 octets, containing a single
octet 8 set, and has value length 6 octets. The message then has two message TLV. This TLV has the thasvalue bit of its semantics octet 8
address blocks each with a following address TLV block. set, and hence contains a value field, with preceding value length 6
octets. The message then has two address blocks each with a
following address TLV block.
The first address block contains 2 network addresses. It has the The first address block contains 2 address prefixes. It has the
anohead, ahaszerotail and ahassingleprelen bits of its semantics ahaszerotail and ahassingleprelen bits of its semantics octet 12 set,
octet 13 set, and has tail length 2 octets, hence mid length two and hence has no head (head length is zero octets). It has tail
octets. The two tail octets of each address are zero. The address length 2 octets, hence mid length two octets. The two tail octets of
block has a single prefix length. The following address TLV block is each address are not included and have value zero. The address block
empty (content length 0 octets). has a single prefix length. The following address TLV block is empty
(content length 0 octets).
The second address block contains 3 addresses, without prefix The second address block contains 3 addresses. It has the ahashead
lengths. It has the anotail bit of its semantics octet 2 set, and bit of its semantics octet 1 set, and has head length 2 octets, no
has head length 2 octets, hence mid length two octets. It is tail (tail length is zero octets) and hence mid length two octets.
followed by an address TLV block, with content length 9 octets, It is followed by an address TLV block, with content length 9 octets,
containing two address block TLVs. The first of these TLVs has the containing two address block TLVs. The first of these TLVs has the
tnoindex bit of its semantics octet 8 set, and has a single value of thasvalue 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 address length 2 octets, which applies to all of the addresses in the address
block. The second of these TLVs has the tnovalue bit of its block. The second of these TLVs has the thasmultiindex bit of its
semantics octet 4 set, and hence has no length or value fields. It semantics octet 4 set, and hence has no value length or value fields.
does have index fields, which indicate those addresses this TLV It has two index fields, which indicate those addresses this TLV
applies to. applies to (inclusive range, counting from zero).
There is one final padding octet value 0 that is not included in the
message length of 55 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 1 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 0 1 1 1| | Message Type |0 0 0 1 1 1 1 0|0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originator Address | | Originator Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop Limit | Hop Count | Message Sequence Number | | Hop Limit | Hop Count | Message Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1| TLV Type |0 0 0 0 1 0 0 0| |0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1| TLV Type |0 0 0 0 1 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 1 1 0| Value | |0 0 0 0 0 1 1 0| Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont) |0 0 0 0 0 0 1 0| | Value (cont) |0 0 0 0 0 0 1 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 1 1 0 1|0 0 0 0 0 0 1 0| Mid | |0 0 0 0 1 1 0 0|0 0 0 0 0 0 1 0| Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | Prefix Length |0 0 0 0 0 0 0 0| | Mid | Prefix Length |0 0 0 0 0 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 1 1|0 0 0 0 0 0 1 0|0 0 0 0 0 0 1 0| |0 0 0 0 0 0 0 0|0 0 0 0 0 0 1 1|0 0 0 0 0 0 0 1|0 0 0 0 0 0 1 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Head | Mid | | Head | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mid | Mid | | Mid | Mid |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1| TLV Type |0 0 0 0 1 0 0 0| |0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1| TLV Type |0 0 0 0 1 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 1 0| Value | TLV Type | |0 0 0 0 0 0 1 0| Value | TLV Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 1 0 0| Index Start | Index Stop |0 0 0 0 0 0 0 0| |0 0 0 0 0 1 0 0| Index Start | Index Stop |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Appendix D. Contributors Appendix F. 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, INRIA, France, <Emmanuel.Baccelli@inria.fr> o Emmanuel Baccelli, INRIA, France, <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, <h-satoh.yj@sdl.hitachi.co.jp> 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, <monden.vw@sdl.hitachi.co.jp> o Monden Kazuya, Hitachi SDL, Japan, <monden.vw@sdl.hitachi.co.jp>
Appendix E. Acknowledgements Appendix G. Acknowledgements
The authors would like to acknowledge the team behind OLSRv1, as The authors would like to acknowledge the team behind OLSRv1, as
specified in RFC 3626, including Anis Laouiti, Pascale Minet, Laurent specified in RFC 3626, including Anis Laouiti, Pascale Minet, Laurent
Viennot (all at INRIA, France), and Amir Qayyum (Center for Advanced Viennot (all at INRIA, France), and Amir Qayyum (Center for Advanced
Research in Engineering, Pakistan) for their contributions. Research in Engineering, Pakistan) for their contributions.
The authors would like to gratefully acknowledge the following people The authors would like to gratefully acknowledge the following people
for intense technical discussions, early reviews and comments on the for intense technical discussions, early reviews and comments on the
specification and its components: Joe Macker (NRL), Alan Cullen (BAE specification and its components: Joe Macker (NRL), Alan Cullen (BAE
Systems), Ian Chakeres (Motorola), Charlie E. Perkins (Nokia), Systems), Ian Chakeres (Motorola), Charlie E. Perkins (Nokia),
Andreas Schjonhaug (LIX), Florent Brunneau (LIX), Yasunori Owada Andreas Schjonhaug (LIX), Florent Brunneau (LIX), Yasunori Owada
(Niigata University), Teco Boot (Infinity Networks) and the entire (Niigata University), Teco Boot (Infinity Networks) and the entire
IETF MANET working group. IETF MANET working group.
Authors' Addresses Authors' Addresses
Thomas Heide Clausen Thomas Heide Clausen
LIX, Ecole Polytechnique, France LIX, Ecole Polytechnique, France
Phone: +33 6 6058 9349 Phone: +33 6 6058 9349
Email: T.Clausen@computer.org EMail: T.Clausen@computer.org
URI: http://www.thomasclausen.org/ URI: http://www.thomasclausen.org/
Christopher M. Dearlove Christopher M. Dearlove
BAE Systems Advanced Technology Centre BAE Systems Advanced Technology Centre
Phone: +44 1245 242194 Phone: +44 1245 242194
Email: chris.dearlove@baesystems.com EMail: chris.dearlove@baesystems.com
URI: http://www.baesystems.com/ URI: http://www.baesystems.com/
Justin W. Dean Justin W. Dean
Naval Research Laboratory Naval Research Laboratory
Phone: +1 202 767 3397 Phone: +1 202 767 3397
Email: jdean@itd.nrl.navy.mil EMail: jdean@itd.nrl.navy.mil
URI: http://pf.itd.nrl.navy.mil/ URI: http://pf.itd.nrl.navy.mil/
Cedric Adjih Cedric Adjih
INRIA Rocquencourt INRIA Rocquencourt
Phone: +33 1 3963 5215 Phone: +33 1 3963 5215
Email: Cedric.Adjih@inria.fr EMail: Cedric.Adjih@inria.fr
URI: http://menetou.inria.fr/~adjih/ URI: http://menetou.inria.fr/~adjih/
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 61, line 44 skipping to change at line 2504
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 404 change blocks. 
827 lines changed or deleted 977 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/