Implement parser for the IOAM Template Option #1

Merged

ramon merged 6 commits from implement-template-option into master 2026-07-26 09:57:23 +00:00

Conversation 0 Commits 6 Files changed 1 +386 -118

ramon commented 2026-04-21 19:04:02 +00:00

Owner

Copy link

I adjusted the dissector implementation to be capable of parsing the IOAM Template Option.
Currently the Aggregation template is the only supported template.

For details refer to:

• IOAM Template Option
• Aggregation Trace Option for IOAM (Now used as template)

I adjusted the dissector implementation to be capable of parsing the IOAM Template Option. Currently the Aggregation template is the only supported template. For details refer to: - [IOAM Template Option](https://www.ietf.org/archive/id/draft-mbci-ippm-ioam-template-option-01.html) - [Aggregation Trace Option for IOAM](https://www.ietf.org/archive/id/draft-cxx-ippm-ioamaggr-04.html) (Now used as template)

ramon added 2 commits 2026-04-21 19:04:03 +00:00

Replace IOAM Aggregation Trace Option with Template Option 9b70d936cb

Add template parsing for the IOAM Aggregation Template a88c85e813

ramon added 1 commit 2026-07-02 13:27:41 +00:00

Add stand-alone IOAM Aggregation Trace Option dissector ... 25e6435bdf

The IOAM Template Option and the IOAM Aggregation Trace Option
are for now considered complimentary. Therefore it makes sense
to have an independent dissector for the IOAM Template Option
including the Aggregation Template and another one for the
IOAM Aggregation Trace Option.

ramon added 1 commit 2026-07-13 14:35:48 +00:00

Adjust dissector of IOAM Template Option ... 0d90ddee40

The format of the IOAM Template Option Aggregation Template
has been adjusted in draft version 2.

The format now looks like this:

  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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |        Namespace-ID           |  TBD_1        |   Length=3    |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |          IOAM Data Param      |  Aggregator   |     Flags     |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                           Aggregate                           |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                Auxil-data Node-Id             |  Hop Count    |
 +---------------------------------------------------------------+

ramon added 1 commit 2026-07-18 19:36:28 +00:00

Refactor IOAM Template Option dissector another time ... 709534a5cf

During the IETF hackathon we noticed that the length field in the
IOAM Template Option is actually implicitely clear based on the
Template ID value. Therefore it can be omitted. We then figured
out that without the length field the only field required to add
template functionality to the IOAM trace option is adding the
Template followed by the Template-Data. Luckily there is exactly
one byte of reserved space in the trace option header where we
can put the Template. To not mess around with existing implemen-
tations of the IOAM Trace Option we decided to create an addtional
option the IOAM Trace + Template Option which combines the two
for use cases where the template data and the path needs to be
traced simultaneously. The following header structures evolved:

IOAM Trace + Template Option

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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         Namespace-ID          | NodeLen | Flags | RemainingLen|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                IOAM-Trace-Type                |  Template-ID  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~       Template-Data depending on the Template-ID value        ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+
|                                                               |  |
|                        node data list [0]                     |  |
|                                                               |  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  D
|                                                               |  a
|                        node data list [1]                     |  t
|                                                               |  a
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                             ........                          ~  S
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  p
|                                                               |  a
|                        node data list [n-1]                   |  c
|                                                               |  e
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  |
|                                                               |  |
|                        node data list [n]                     |  |
|                                                               |  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+

IOAM Template Option

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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        Namespace-ID           |   Template ID |      FEP      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~       Template-Data depending on the Template-ID value        ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Aggregation Template has been defined as follows:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          IOAM Data Param                      |  Aggr | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           Aggregate                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                Auxil-data Node-Id             |  Hop Count    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

ramon force-pushed implement-template-option from 709534a5cf to 117350eecd 2026-07-20 15:42:50 +00:00 Compare

ramon added 1 commit 2026-07-26 09:14:47 +00:00

Add dissector for the IOAM Aggregation Trace Option ... 2e10c1bf83

I added again the dissector for the IOAM Aggregation Trace Option
according to the structure defined in the drafts:

- draft-mbci-ippm-ioam-template-option-03
- draft-cxx-ippm-ioamaggr-06

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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        Namespace-ID           |           Reserved            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          IOAM Data Param                      | AggrF | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           Aggregate                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                Auxil-data Node-Id             |  Hop Count    |
+---------------------------------------------------------------+

The structure of the aggregated data is supposed to be the same
for the IOAM Aggregation Template and the IOAM Aggregation Trace
Option. Currently the fields AggrF and Flags are swapped in
the definitions in the two drafts. The current implementation
follows the template option draft.

ramon force-pushed implement-template-option from 2e10c1bf83 to 70b021f46c 2026-07-26 09:54:11 +00:00 Compare

ramon force-pushed implement-template-option from 70b021f46c to e845fad603 2026-07-26 09:56:40 +00:00 Compare

ramon merged commit edb5c87d60 into master 2026-07-26 09:57:23 +00:00

ramon referenced this pull request from a commit 2026-07-26 09:57:23 +00:00

Merge pull request 'Implement parser for the IOAM Template Option' (#1) from implement-template-option into master

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ramon/wireshark!1

No description provided.