BTW, regarding [PSAMP-INFO], the 2 ipHeaderPacketSection and
ipPayloadPacketSection information element descriptions currently
"If insufficient octets are available,
Obviously these sentences will have to be removed.
the remainder of the data should be zero-filled and an additional
information element sent (e.g., ipPayloadLength) indicating how
much of the data is valid."
>From the Vancouver meeting minutes:
Open Issue (not numbered): Chunk with too short length
How to encode "chunk" with a too short length? Padding wouldn't be
by the collector. One solution would be using a new template for each
Proposal: The protocol draft should say that padding MUST NOT be used
variable length IEs.
Here is a new proposed text (actually, only the second paragraph is new)
Basic Packet Report
For each selected packet, the Packet Report MUST contain the
- The associationsId Information Element
- Some number of contiguous bytes from the start of the
packet, including the packet header (which includes link layer, network
and other encapsulation headers) and some subsequent bytes of the
payload. Alternatively, the number of
contiguous bytes may start at the beginning of the payload. The
Layer2PacketSection, l2PayloadPacketSection, mplsLabelStackSection,
ipPacketSection, and ipPayloadPacketSection PSAMP Information Elements
available for this use.
- The input sequence number(s) of any Selectors that acted on
the packet, represented by the selectorInputSequenceNumber Information
The contiguous Information Elements (Layer2PacketSection,
mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and
MAY be encoded with a fixed length field or with a variable sized
field. If one
of these Information Elements is encoded with a fixed length field
is too long for the number of contiguous bytes in the selected packet,
MUST NOT be used. In this case, the Exporting Process MUST export the
information either in a new Template Record with the correct fixed
or either in a new Template Record with a variable length field.