[OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)

Thomas.Graf@swisscom.com Tue, 29 October 2024 13:07 UTC

Return-Path: <Thomas.Graf@swisscom.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21C15C14F6F7 for <opsawg@ietfa.amsl.com>; Tue, 29 Oct 2024 06:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=swisscom.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LkkwH0HIcKgV for <opsawg@ietfa.amsl.com>; Tue, 29 Oct 2024 06:07:12 -0700 (PDT)
Received: from mail.swisscom.com (mailout120.swisscom.com [138.188.166.120]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 706D6C14F605 for <opsawg@ietf.org>; Tue, 29 Oct 2024 06:07:12 -0700 (PDT)
Received: by mail.swisscom.com; Tue, 29 Oct 2024 14:07:03 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=swisscom.com; s=iscm; t=1730207224; bh=IzcxPzRw0oXR5L1x1MZ8p5jAWAW4mt3Qk1VwVu3C83o=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=hMZM1Z5SxlAcmbePJ9OtyKqYtVbjHGAQ/YlN3YtOMwi2DmUaayFfzETqBVp+IHhnF OrmVBDvE/SO59oQE1a0zwqM99IF/39aLOAJYV13TypH0331MWDsjyV4PoUAzd47uDG OX6RUZ0Ltn35hO95tyJS3epkqJ4e0ELqAEmdMZ+oD8dBzO28IO1iPbG1cko+9Md4UL rmalyyi2QN0MxxMnagnlhZ3TPlbl+H5bdfU/jcr+8vHTzRRMrU0yND6iXC+NvRHjQu 3JnEgslufYfRgnzxV4rYwwxiPwC8AdkOpmZP9yTIfcb3D4iMldtLxNZPzSxEXgdhOt 7raDampTHEGvQ==
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----=_Part_75604_1461682050.1730207223422"
X-Mailer: Totemo_TrustMail_(Notification)
From: Thomas.Graf@swisscom.com
To: giuseppe.fioccola=40huawei.com@dmarc.ietf.org, jclarke=40cisco.com@dmarc.ietf.org, opsawg@ietf.org
Thread-Topic: WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)
Thread-Index: AQHbGyXmnG4iMmoLm0S+z2m4rZ9Cq7KUCYJQgAnGEyA=
Date: Tue, 29 Oct 2024 13:07:00 +0000
Message-ID: <b724f5bf7143407ba170e047957e58ba@swisscom.com>
References: <BN9PR11MB5371560C6FC1E62BE4D7275FB8782@BN9PR11MB5371.namprd11.prod.outlook.com> <6fcc1af3df2c4c659880ff7db400db85@huawei.com>
In-Reply-To: <6fcc1af3df2c4c659880ff7db400db85@huawei.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ActionId=f57c88c4-0192-4697-ab53-9f752786c7c2;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ContentBits=0;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Enabled=true;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Method=Standard;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Name=C2 Internal;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SetDate=2024-10-29T13:03:25Z;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SiteId=364e5b87-c1c7-420d-9bee-c35d19b557a1;
x-originating-ip: [138.188.161.184]
X-CFilter-Loop: Reflected
X-Trustmail: processed
Message-ID-Hash: AX7RSUL3B5BJOTIH3XUBWSW5ZZKUW33J
X-Message-ID-Hash: AX7RSUL3B5BJOTIH3XUBWSW5ZZKUW33J
X-MailFrom: Thomas.Graf@swisscom.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-opsawg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/SzQ4PC6bK_1ZQGZJNVUZWGdZtAE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Owner: <mailto:opsawg-owner@ietf.org>
List-Post: <mailto:opsawg@ietf.org>
List-Subscribe: <mailto:opsawg-join@ietf.org>
List-Unsubscribe: <mailto:opsawg-leave@ietf.org>

Dear Giuseppe,

Thanks a lot for the input. That makes perfectly sense that we also describe the applicability onto the SRv6 Segment Routing Header in the Alternate-Marking Method and mention Alternate-Marking Method when the delay is being calculated outside of the network node.

Could you please review the following changes

https://author-tools.ietf.org/diff?doc_1=draft-ietf-opsawg-ipfix-on-path-telemetry-13&url_2=https://raw.githubusercontent.com/network-analytics/draft-ietf-opsawg-ipfix-on-path-telemetry/refs/heads/main/draft-ietf-opsawg-ipfix-on-path-telemetry-14.txt

and let us wherever it addresses your comments. I will submit it then as soon as the submit window is re-opened.

Best wishes
Thomas

From: Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org>
Sent: Wednesday, October 23, 2024 10:06 AM
To: Joe Clarke (jclarke) <jclarke=40cisco.com@dmarc.ietf.org>; opsawg@ietf.org
Subject: [OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)


Be aware: This is an external email.


Hi All,
I have reviewed the draft and I think it is ready.
Regarding the Alternate-Marking Method, I suggest to add the reference to draft-fz-spring-srv6-alt-mark in section 3.3.2 and section 7.5, since this document also describes the addition of the Timestamp Data Field, similarly to draft-zhou-ippm-enhanced-alternate-marking.
I would also suggest to mention draft-ietf-opsawg-ipfix-alt-mark as another option to use IPFIX to export timestamps and therefore calculate the delay.

Regards,

Giuseppe


From: Joe Clarke (jclarke) <jclarke=40cisco.com@dmarc.ietf.org<mailto:jclarke=40cisco.com@dmarc.ietf.org>>
Sent: Thursday, October 10, 2024 5:08 PM
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
Subject: [OPSAWG]WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)

This starts a two week WG LC for  draft-ietf-opsawg-ipfix-on-path-telemetry<https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-on-path-telemetry/>.  The authors have been polled and there is no known IPR on this work that has been disclosed at this time.

Please post comments and thoughts on this document's readiness to the list.  If you are interested in being the shepherd for this document, please email opsawg-chairs@.

The WG LC will run until October 24.

Thanks.

Joe