Dear Greg,

Thanks a lot for the feedback and comments during OPSAWG and the conversation 
afterwards.

We are going to change the terminology from "Inband" to  "On-Path" Telemetry as 
per your suggestion to be inline with IPPM.

Regarding the term "Aggregation" in the slide deck. It refers to RFC 7015, 
IPFIX Flow Aggregation, where data is being aggregated during the metering 
process.

I reviewed draft-ietf-ippm-ioam-direct-export, RFC8321 and 
draft-ietf-ippm-rfc8321bis. I understood that the following sections are 
relevant for the data export
  
  In-situ OAM Direct Exporting
   
https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-direct-export#section-3.1.2
   
https://datatracker.ietf.org/doc/html/draft-spiegel-ippm-ioam-rawexport-06#section-3.1

  Alternate-Marking Method for Passive and Hybrid Performance Monitoring
   https://datatracker.ietf.org/doc/html/rfc8321#section-3.1.3
   
https://datatracker.ietf.org/doc/html/draft-ietf-ippm-rfc8321bis-03#section-4.3
   
https://datatracker.ietf.org/doc/html/draft-chen-ippm-ipfpm-report-01#section-4.4

None of the IPFIX identities are defiing a delay measurement. However they 
describe how timestamps can be exported. In order to ensure that the timestamp 
for every packet can be exposed, timestamps needs to be defined as flow key 
field (https://datatracker.ietf.org/doc/html/rfc7011#section-2). This however 
prevents IPFIX Flow Aggregation (RFC7015) due to the increased cardinality. In 
draft-tgraf-opsawg-ipfix-inband-telemetry, this is described in the use case 
section: 
https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-inband-telemetry#section-4.
 Feel free to comment wherever this needs to be described more approprietly.

As you and also Benoit mentioned, draft-tgraf-opsawg-ipfix-inband-telemetry 
complements draft-ietf-ippm-ioam-direct-export, RFC8321 and 
draft-ietf-ippm-rfc8321bis. Looking forward for additional input to describe 
also this aspect.

Best wishes
Thomas

-----Original Message-----
From: OPSAWG <opsawg-boun...@ietf.org> On Behalf Of Benoit Claise
Sent: Thursday, July 28, 2022 3:02 PM
To: opsawg@ietf.org
Subject: [OPSAWG] FW: New Version Notification for 
draft-tgraf-opsawg-ipfix-inband-telemetry-01.txt

Dear all,

We posted a new version of this draft, which exports forwarding path delay in 
IPFIX.

The updated version includes multiple clarifications:
- the use case is better described
- the mapping between IPFIX Information Elements and Performance Metrics is 
explained
- It includes a figure displaying which forwarding path delay is actually 
exported
- We used a consistent terminology throughout the document
- the IANA considerations section is improved (and double-checked with the IANA 
rep. on site)

Your feedback is welcome, either on the mailing or during the presentation 
tomorrow.

Regards, Thomas, Alex, Benoit

-----Original Message-----
From: internet-dra...@ietf.org <internet-dra...@ietf.org> 
Sent: Thursday, July 28, 2022 10:44 AM
To: Alex Feng <alex.huang-f...@insa-lyon.fr>; Alex Huang Feng 
<alex.huang-f...@insa-lyon.fr>; Benoit Claise <benoit.cla...@huawei.com>; 
Thomas Graf <thomas.g...@swisscom.com>
Subject: New Version Notification for 
draft-tgraf-opsawg-ipfix-inband-telemetry-01.txt


A new version of I-D, draft-tgraf-opsawg-ipfix-inband-telemetry-01.txt
has been successfully submitted by Thomas Graf and posted to the IETF 
repository.

Name:           draft-tgraf-opsawg-ipfix-inband-telemetry
Revision:       01
Title:          Export of Forwarding Path Delay in IPFIX
Document date:  2022-07-28
Group:          Individual Submission
Pages:          21
URL:            
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-tgraf-opsawg-ipfix-inband-telemetry-01.txt&amp;data=05%7C01%7CThomas.Graf%40swisscom.com%7Cd3828009bf9a48ac9e4908da70cc2814%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637946319390764912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=jssrP7zcVggQzkmD7bjpbSbgMOlzRZF8t5eEb5PrCnQ%3D&amp;reserved=0
Status:         
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-tgraf-opsawg-ipfix-inband-telemetry%2F&amp;data=05%7C01%7CThomas.Graf%40swisscom.com%7Cd3828009bf9a48ac9e4908da70cc2814%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637946319390764912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=seW1wx0O3XP%2Fjz0y8UECLqq74MwDYmqFE2zPR%2BBbhKI%3D&amp;reserved=0
Htmlized:       
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tgraf-opsawg-ipfix-inband-telemetry&amp;data=05%7C01%7CThomas.Graf%40swisscom.com%7Cd3828009bf9a48ac9e4908da70cc2814%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637946319390921142%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=%2FPQz0IYAFjdjUtqu5sCm0ZqYjt8HdVe4zakxLSRD9K0%3D&amp;reserved=0
Diff:           
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-tgraf-opsawg-ipfix-inband-telemetry-01&amp;data=05%7C01%7CThomas.Graf%40swisscom.com%7Cd3828009bf9a48ac9e4908da70cc2814%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637946319390921142%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=F8ptQxHifMujhECpjxGdJUooagBKM%2FBAJhhhAbNZ8hc%3D&amp;reserved=0

Abstract:
   This document introduces new IP Flow Information Export (IPFIX)
   information elements to expose the Inband Telemetry measured
   forwarding path delay on the IOAM transit and decapsulation nodes.

                                                                                
  


The IETF Secretariat


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fopsawg&amp;data=05%7C01%7CThomas.Graf%40swisscom.com%7Cd3828009bf9a48ac9e4908da70cc2814%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637946319390921142%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=Sv4SCCpi9cl%2BO4C4nw%2FC%2BF6%2BfkyELYT9%2Bc7QtJGvHI4%3D&amp;reserved=0

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to