IETF Logo Mail Archive

Re: [ippm] Export of IOAM data

Justin Iurman <justin.iurman@uliege.be> Thu, 08 February 2024 16:17 UTC

Return-Path: <justin.iurman@uliege.be>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18E79C14F680; Thu, 8 Feb 2024 08:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uliege.be
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 PcL1OFmPBXBC; Thu, 8 Feb 2024 08:17:12 -0800 (PST)
Received: from serv108.segi.ulg.ac.be (serv108.segi.ulg.ac.be [139.165.32.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A2C1C14F738; Thu, 8 Feb 2024 08:17:05 -0800 (PST)
Received: from [192.168.1.55] (125.179-65-87.adsl-dyn.isp.belgacom.be [87.65.179.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by serv108.segi.ulg.ac.be (Postfix) with ESMTPSA id 95DC7200BE4A; Thu, 8 Feb 2024 17:17:03 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.11.0 serv108.segi.ulg.ac.be 95DC7200BE4A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uliege.be; s=ulg20190529; t=1707409023; bh=S7wk3a/L/ogTHR9i11u17GplFiooJCfNUPImSEqNiEI=; h=Date:Subject:To:References:From:In-Reply-To:From; b=z6AnoyG1mpJ9+qqqQUPg6Ngd2RtpAIMUDUI1Uxzmx+M74GFBnzvre13ISNBi0enlF L2Xw0EIpOorr33EP9e/Zk9ylt+xNFUpfw0TdRywJEJl7MAeElOsRBsdDf37eEWiavR BqXxUpObTz2XKJVknqH9Y7vA53otJEwh0KxE5AxdsC7lrg3Jsf+NywUQApw7sr8cXz RpmcumV3xA3O+5dXCAAFDrmvtghLqwyGzrUDY0SMzrHMQtXGW7iXOOvY12OrEnRGqh do2iNrKjv2bFQ/qcidOIdqtihaThEYZZpK3iBUWleSTLg3GRw84/pDnyWoubvrZM7U 45+2FUcf4HHFg==
Message-ID: <f103cd4d-19fb-4d66-b156-d1c705f27631@uliege.be>
Date: Thu, 08 Feb 2024 17:17:03 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Thomas.Graf@swisscom.com, reshad@yahoo.com, ippm@ietf.org, draft-spiegel-ippm-ioam-rawexport@ietf.org
References: <2067307430.3577031.1707315253438.ref@mail.yahoo.com> <2067307430.3577031.1707315253438@mail.yahoo.com> <3812022b361249e19f28cf255af46d96@swisscom.com>
From: Justin Iurman <justin.iurman@uliege.be>
In-Reply-To: <3812022b361249e19f28cf255af46d96@swisscom.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/txyURWR0dfcblTTfNUr-iX9DzAs>
Subject: Re: [ippm] Export of IOAM data
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2024 16:17:17 -0000

Hi Thomas,

+1, now might be a good time to revive (again) 
draft-spiegel-ippm-ioam-rawexport. FWIW, I'd be available to help too.

Justin

On 2/8/24 05:36, Thomas.Graf@swisscom.com wrote:
> Dear Reshad,
> 
> I am not aware of that draft-spiegel-ippm-ioam-rawexport was update or 
> any other draft defining IPFIX entities for IOAM.
> 
> draft-ietf-opsawg-ipfix-on-path-telemetry describes in section 7.4 
> (https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-on-path-telemetry-06#section-7.4 <https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-on-path-telemetry-06#section-7.4>) the application of on-path delay measurement export with IOAM.
> 
> draft-gfz-opsawg-ipfix-alt-mark was resecently published and describes 
> for Alternate Marking the IPFIX entities.
> 
> I would available to support the co-authoring of such a document.
> 
> Best wishes
> 
> Thomas
> 
> *From:*ippm <ippm-bounces@ietf.org> *On Behalf Of *Reshad Rahman
> *Sent:* Wednesday, February 7, 2024 3:14 PM
> *To:* IETF IPPM WG <ippm@ietf.org>; 
> draft-spiegel-ippm-ioam-rawexport@ietf.org
> *Subject:* [ippm] Export of IOAM data
> 
> 	
> 
> *Be aware:*This is an external email.
> 
> Hi,
> 
> Did the WG ever close on an export format for info obtained via IOAM? I 
> don't actively follow this WG but checked the archive and it's been more 
> than a year since draft-spiegel-ippm-ioam-rawexport was mentioned (and 
> it has expired).
> 
> Regards,
> 
> Reshad.
> 
> 
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm

v2.23.0 | Report a Bug | By Email