Hi Mauricio,
The hop-by-hop collection and processing of buffer occupancy, queue depth,
transit delays is not implemented.
M-Anycast focused on end to end delay by using timestamp in IOAM.
You could implement these 3 elements into the existing IOAM implementation
without having to update IOAM to the latest. Take a look at
vpp:src/plugins/ioam/lib-trace/trace_util.h, following elements are implemented
for tracing:
u32 ttl_node_id;
u16 ingress_if;
u16 egress_if;
u32 timestamp;
u32 app_data;
You can expand it by adding buffer occupancy, queue depth, transit delays.
While Justin and I work on updating the IOAM to latest draft, you are welcome
to work with us and contribute.
Thanks,
Shwetha
On 8/4/20, 6:35 PM, "vpp-dev@lists.fd.io on behalf of Justin Iurman"
<vpp-dev@lists.fd.io on behalf of justin.iur...@uliege.be> wrote:
Mauricio,
> Justin,
>
> I too am working on my master thesis, but I'm set to finish in December.
Hmm, I see.
> Currently, we're looking at video streaming and would like to get
telemetry
> data for buffer occupancy, queue depth, and transit delays. VPP seems
the best
> viable (and free) option for use.
Indeed. You can already take a look at M-Anycast [1] which combines IOAM
and SRv6. There is a demo with video streaming, so you might be interested.
But, again, this is based on the old IOAM implementation inside VPP. If you
really want or need to refresh the IOAM implem, feel free to contact me in
private and I'll put you in touch with the other student so that you can
collaborate.
On a side note, I've recently posted a first version of the IOAM patch for
the Linux kernel [2]. So hopefully, it may be available soon in the kernel too
(this one is up-to-date with drafts).
Justin
[1] https://github.com/CiscoDevNet/iOAM/tree/master/M-Anycast
[2] https://www.mail-archive.com/netdev@vger.kernel.org/msg333936.html
> Mauricio
>
> -----Original Message-----
> From: Justin Iurman <justin.iur...@uliege.be>
> Sent: maandag 3 augustus 2020 17:11
> To: Solis JR, M. (Mauricio) <mauricio.soli...@tno.nl>
> Cc: vpp-dev <vpp-dev@lists.fd.io>; Shwetha Bhandari (shwethab)
> <shwet...@cisco.com>
> Subject: Re: [vpp-dev] Update to iOAM using latest IETF draft #vpp
>
> Mauricio,
>
>> Justin,
>> Do you know the release date for the updated iOAM plugin on the latest
>> ietf draft?
>
> Not really. This is actually a student and he's going to do it for his
master
> thesis. Who knows for the precise date, but he will start soon... so I'd
say
> during first 2021 semester (or trimester hopefully).
>
> Out of curiosity, what are you working on with IOAM so that you want to
refresh
> the VPP implem?
>
> Justin
>
>> Mauricio
>>
>> -----Original Message-----
>> From: Justin Iurman <justin.iur...@uliege.be>
>> Sent: woensdag 29 juli 2020 14:26
>> To: Solis JR, M. (Mauricio) <mauricio.soli...@tno.nl>
>> Cc: vpp-dev <vpp-dev@lists.fd.io>; Shwetha Bhandari (shwethab)
>> <shwet...@cisco.com>
>> Subject: Re: [vpp-dev] Update to iOAM using latest IETF draft #vpp
>>
>> Hi Mauricio,
>>
>> CC'ing Shwetha, she implemented the IOAM plugin. Last time I checked,
>> IOAM namespaces were not included, so it is probably based on the -03
>> version of draft-ietf-ippm-ioam-data. Actually, just to let you know,
>> there is already someone that is going to rebase the implementation on
the last
>> draft version.
>>
>> Justin
>>
>>> Hi,
>>>
>>> I noticed that the current iOAM plugin implementation is using the
>>> first IETF drafts, so I'm thinking about trying to update the iOAM
>>> implementation in VPP using the latest. I first just want to make
>>> sure there that this update is not in the immediate VPP release
>>> pipeline since I do not wish to do work that has already been done.
>>> I'm also uncertain about the amount of work it will require to update
>>> the plugin, but I have already dug into the code and it doesn't seem
"too" bad.
>>>
>>> Regards,
>>>
>>> Mauricio
>> This message may contain information that is not intended for you. If
>> you are not the addressee or if this message was sent to you by
>> mistake, you are requested to inform the sender and delete the
>> message. TNO accepts no liability for the content of this e-mail, for
>> the manner in which you use it and for damage of any kind resulting
> > from the risks inherent to the electronic transmission of messages.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17142): https://lists.fd.io/g/vpp-dev/message/17142
Mute This Topic: https://lists.fd.io/mt/75861366/21656
Mute #vpp: https://lists.fd.io/g/fdio+vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
