Rare project developers

[Ronald van der Pol <>]

Hi Csaba,

Thanks. That clarifies things. I think I have one question left:
What is the "java sw forwarder"?

Just some FYI:

I looked through my code and I made a couple of decissions.

I use the ioam extension header option:

/*
 * Implementation of draft-ioametal-ippm-6man-ipv6-options and
 *                   draft-ietf-ippm-ioam-data
 */

/*
 * IPv6 Hop-by-Hop and Destination Option format for carrying
 * in-situ OAM data fields.
 */
header ipv6_ioam_option_h {
    bit<8> reserved;
    bit<8> ioam_type;
}

but the INT data header, bacause it is simpler:
https://github.com/rvdpdotorg/P4include/blob/master/int.p4

draft-ietf-ippm-ioam-data-12.txt has the concept of 
namespaces. But for interop, we may need to use that.

My current code also does padding for the HBH extension
header. But I found out this is not needed. There is a
requirement (MUST) that the data that you record is
aligned properly.

draft-ietf-ippm-ioam-ipv6-options-05.txt
section 3:
In addition, to maintain IPv6
extension header 8-octet alignment and avoid the need to add or
remove padding at every hop, the Trace-Type for Incremental Trace
Option in IPv6 MUST be selected such that the IOAM node data length
is a multiple of 8-octets.

    rvdp