Re: [OPSAWG] [ippm] New Version Notification for draft-tgraf-opsawg-ipfix-on-path-telemetry-00.txt

[Benoit Claise <[e-mail]>]

Hi Tianran,

IPFIX is composed of two components:
1. The IPFIX Metering Process
2. The IPFIX Exporting Process

This draft focuses only on 2.
However, we needed some specific terms to express the IPIFX Metering 
Process location. As an example, see "transit" in the abstract.
It does not make sense to re-invent some new terms to be "independent of 
specific on-path telemetry protocols.", as you wrote.
Hence we selected the IOAM terminology.

I hope this clarifies.

Regards, Benoit
On 10/21/2022 9:29 AM, Tianran Zhou wrote:
> Hi Thomas,
>
> Only looking at the abstraction, I think you do not get Greg's comment on on-path telemetry.
> IMO, this IPFIX extension should only focus on the data export, while independent of specific on-path telemetry protocols.
> The following draft is a very useful reference for on path telemetry:
> https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/18/
>
> " On-Path Telemetry (OPT) refers to data-plane telemetry techniques that directly tap and
>     measure network traffic by embedding instructions or metadata into
>     user packets. "
>
> " It is essential to recognize that existing work on this topic includes a variety of on-path telemetry
>     techniques, including In-situ OAM (IOAM) [RFC9197], IOAM Direct Export (DEX) [I-D.ietf-ippm-ioam-direct-export], Marking-based
>     Postcard-based Telemetry (PBT-M)[I-D.song-ippm-postcard-based-telemetry], Enhanced Alternate Marking
>     (EAM) [I-D.zhou-ippm-enhanced-alternate-marking], and Hybrid Two-Step (HTS) [I-D.mirsky-ippm-hybrid-two-step], have been developed or
>     proposed. "
>
> Hope this is useful for you.
>
> Cheers,
> Tianran
> -----Original Message-----
> From: ippm [mailto:[e-mail]] On Behalf Of [e-mail]
> Sent: Thursday, October 20, 2022 9:42 PM
> To: [e-mail]; [e-mail]
> Cc: [e-mail]
> Subject: Re: [ippm] New Version Notification for draft-tgraf-opsawg-ipfix-on-path-telemetry-00.txt
>
> Dear OPSAWG and IPPM,
>
> On behalf of the authors. Thank you very much for the comments at IETF 114 in Philadelphia and on the list.
>
> We addressed your feedback in a new document version and renamed the draft document from draft-tgraf-opsawg-ipfix-inband-telemetry to draft-tgraf-opsawg-ipfix-on-path-telemetry. Thanks Greg for the input.
>
> Looking forward to your reviews and comments.
>
> Best wishes
> Thomas
>
> -----Original Message-----
> From: [e-mail] <[e-mail]>
> Sent: Thursday, October 20, 2022 3:32 PM
> To: Alex Feng <[e-mail]>; Alex Huang Feng <[e-mail]>; Benoit Claise <[e-mail]>; Graf Thomas, INI-NET-TCZ-ZH1 <[e-mail]>
> Subject: New Version Notification for draft-tgraf-opsawg-ipfix-on-path-telemetry-00.txt
>
>
> A new version of I-D, draft-tgraf-opsawg-ipfix-on-path-telemetry-00.txt
> has been successfully submitted by Thomas Graf and posted to the IETF repository.
>
> Name:		draft-tgraf-opsawg-ipfix-on-path-telemetry
> Revision:	00
> Title:		Export of On-Path Delay in IPFIX
> Document date:	2022-10-20
> Group:		Individual Submission
> Pages:		22
> URL:            https://www.ietf.org/archive/id/draft-tgraf-opsawg-ipfix-on-path-telemetry-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-tgraf-opsawg-ipfix-on-path-telemetry/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-on-path-telemetry
> Diff:      https://www.ietf.org/rfcdiff?url1=draft-tgraf-opsawg-ipfix-inband-telemetry-01&url2=draft-tgraf-opsawg-ipfix-on-path-telemetry-00&difftype=--html
>
> Abstract:
>     This document introduces new IP Flow Information Export (IPFIX)
>     information elements to expose the On-Path Telemetry measured delay
>     on the IOAM transit and decapsulation nodes.
>
>                                                                                    
>
>
> The IETF Secretariat
>
> _______________________________________________
> ippm mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ippm