Re: [Ippm-ioam-ix-dt] IPPM IOAM Virtual Meeting Summary

Tianran Zhou <zhoutianran@huawei.com> Wed, 17 June 2020 06:48 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: ippm-ioam-ix-dt@ietfa.amsl.com
Delivered-To: ippm-ioam-ix-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695FA3A0F22 for <ippm-ioam-ix-dt@ietfa.amsl.com>; Tue, 16 Jun 2020 23:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MfLbeJ3laFo3 for <ippm-ioam-ix-dt@ietfa.amsl.com>; Tue, 16 Jun 2020 23:48:26 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B3093A0EC6 for <ippm-ioam-ix-dt@ietf.org>; Tue, 16 Jun 2020 23:48:26 -0700 (PDT)
Received: from lhreml733-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id BB3B044BD2FA7A0393CC; Wed, 17 Jun 2020 07:48:24 +0100 (IST)
Received: from nkgeml709-chm.china.huawei.com (10.98.57.40) by lhreml733-chm.china.huawei.com (10.201.108.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 17 Jun 2020 07:48:24 +0100
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by nkgeml709-chm.china.huawei.com (10.98.57.40) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 17 Jun 2020 14:48:21 +0800
Received: from nkgeml707-chm.china.huawei.com ([10.98.57.157]) by nkgeml707-chm.china.huawei.com ([10.98.57.157]) with mapi id 15.01.1913.007; Wed, 17 Jun 2020 14:48:21 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Barak Gafni <gbarak@mellanox.com>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>, "ippm-ioam-ix-dt@ietf.org" <ippm-ioam-ix-dt@ietf.org>
Thread-Topic: [Ippm-ioam-ix-dt] IPPM IOAM Virtual Meeting Summary
Thread-Index: AQHWRHB/h6vm5IXBAkusNpmrMY+ebajb1guAgACGkcA=
Date: Wed, 17 Jun 2020 06:48:21 +0000
Message-ID: <1afcb0bfe94f445f9acd5953fc91fa31@huawei.com>
References: <CABUE3XnwH5u0w+HFXYBf+ZvHw=7fcYuRUwU6+Gj58ffee2zyFQ@mail.gmail.com> <AM6PR05MB4118DC1D96397522A4576F11B99A0@AM6PR05MB4118.eurprd05.prod.outlook.com>
In-Reply-To: <AM6PR05MB4118DC1D96397522A4576F11B99A0@AM6PR05MB4118.eurprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.203.247]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm-ioam-ix-dt/Pb_DdrOFDZldnRB84TCqbE0fyOg>
Subject: Re: [Ippm-ioam-ix-dt] IPPM IOAM Virtual Meeting Summary
X-BeenThere: ippm-ioam-ix-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPPM iOAM Immediate Export \(IX\) design team" <ippm-ioam-ix-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm-ioam-ix-dt>, <mailto:ippm-ioam-ix-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm-ioam-ix-dt/>
List-Post: <mailto:ippm-ioam-ix-dt@ietf.org>
List-Help: <mailto:ippm-ioam-ix-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm-ioam-ix-dt>, <mailto:ippm-ioam-ix-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2020 06:48:27 -0000

In brief, IOAM-DEX is PBT-I method, and the srv6 o-flag is PBT-M method.
Both methods are discussed in draft-song-ippm-postcard-based-telemetry.
I really think this draft worth to document as generic methods that could be used in many transports, and the protocol design. 

Cheers,
Tianran

-----Original Message-----
From: Ippm-ioam-ix-dt [mailto:ippm-ioam-ix-dt-bounces@ietf.org] On Behalf Of Barak Gafni
Sent: Wednesday, June 17, 2020 2:43 PM
To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>; ippm-ioam-ix-dt@ietf.org
Subject: Re: [Ippm-ioam-ix-dt] IPPM IOAM Virtual Meeting Summary

Greg, thanks for pointing out.
Some differences compared to DEX from in my view:
1. It applies only for SRv6, while DEX doesn't limit for IPv6 or any other protocol 2. It should get processed only at the segment end point, while DEX should get processed potentially at every node in the network 3. This may be implantation dependent, but the draft calls for processing of this bit ahead of the SR processing, copy the packet etc. which may theoretically cause different behavior than what one may expect from DEX 4. The way to communicate required data is through management plane rather than through the data plane

Thanks,
Barak

-----Original Message-----
From: Ippm-ioam-ix-dt <ippm-ioam-ix-dt-bounces@ietf.org> On Behalf Of Tal Mizrahi
Sent: Tuesday, June 16, 2020 11:27 PM
To: ippm-ioam-ix-dt@ietf.org
Subject: [Ippm-ioam-ix-dt] IPPM IOAM Virtual Meeting Summary

IPPM IOAM Design Team
Virtual meeting
June 17th, 2020, 06:00 UTC
Webex meeting

Attendees:
Greg Mirsky, Mickey Spiegel, Tal Mizrahi.

Minutes by Tal Mizrahi.

Summary
========
- Due to low attendance we had a very short meeting.
- Next meeting will be held on July 1st.


Direct Exporting
============
-  Greg: there is a draft in WG last call in 6man we should take a look at (draft-ietf-6man-spring-srv6-oam). The O-Flag in that draft is a trigger for IPFIX-based exporting. This is similar to direct exporting. Why do we need two different methods for the same thing?
- Mickey: I believe that is a bit different, and I still believe there is a valid use case for having IOAM direct exporting.
- Tal: the O-Flag sounds a bit similar to the marking bit in alternate marking, which was also discussed in the PBT-M concept in draft-song-ippm-postcard-based-telemetry.
- Greg: this issue may be worth discussing in IPPM.
- Tal: next meeting will be in two weeks.

--
Ippm-ioam-ix-dt mailing list
Ippm-ioam-ix-dt@ietf.org
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fippm-ioam-ix-dt&amp;data=02%7C01%7Cgbarak%40mellanox.com%7Cfdf004bb414a4e67ac7e08d81287a024%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C637279720999229145&amp;sdata=Xx62FvG%2FMx0H66uCzzq7ZGeZQpgQuSP3BdTqwzkqJDw%3D&amp;reserved=0

--
Ippm-ioam-ix-dt mailing list
Ippm-ioam-ix-dt@ietf.org
https://www.ietf.org/mailman/listinfo/ippm-ioam-ix-dt