Re: [ippm] IPPM slides for IOAM data fields and IOAM flags updates

Tianran Zhou <zhoutianran@huawei.com> Tue, 23 July 2019 14:52 UTC

Return-Path: <zhoutianran@huawei.com>
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 C89531201DA for <ippm@ietfa.amsl.com>; Tue, 23 Jul 2019 07:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 4MKIiC-BZCOI for <ippm@ietfa.amsl.com>; Tue, 23 Jul 2019 07:52:46 -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 AF551120072 for <ippm@ietf.org>; Tue, 23 Jul 2019 07:52:45 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id C10F89412568FC18B041 for <ippm@ietf.org>; Tue, 23 Jul 2019 15:52:43 +0100 (IST)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 23 Jul 2019 15:52:38 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.142]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0439.000; Tue, 23 Jul 2019 22:47:18 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: IPPM slides for IOAM data fields and IOAM flags updates
Thread-Index: AdVAemjOpbipKdShRhO+PDmA6kDyjwAPU8xqAAc+p5AAI8p6ew==
Date: Tue, 23 Jul 2019 14:47:17 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21BEECFFFF@NKGEML515-MBS.china.huawei.com>
References: <BYAPR11MB2584C1B270C11A39441F6354DAC40@BYAPR11MB2584.namprd11.prod.outlook.com> <BBA82579FD347748BEADC4C445EA0F21BEECD2E7@NKGEML515-MBS.china.huawei.com>, <BYAPR11MB258489B22F32610A3C02A5F9DAC40@BYAPR11MB2584.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB258489B22F32610A3C02A5F9DAC40@BYAPR11MB2584.namprd11.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.124.93.69]
Content-Type: multipart/alternative; boundary="_000_BBA82579FD347748BEADC4C445EA0F21BEECFFFFNKGEML515MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/b2nqXGG3EkQYkEoEaZc2RbKnrmw>
Subject: Re: [ippm] IPPM slides for IOAM data fields and IOAM flags updates
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Jul 2019 14:52:49 -0000

Hi Frank,

Thanks. I think we are now aligned on the new option now.

With regard to the place, I think we can just evolve the existing PBT draft.

Cheers,
Tianran

________________________________
发件人: Frank Brockners (fbrockne) [fbrockne@cisco.com]
发送时间: 2019年7月23日 5:41
收件人: Tianran Zhou; ippm@ietf.org
主题: RE: IPPM slides for IOAM data fields and IOAM flags updates

Hi Tianran,

IMHO this sounds like a workable path forward, i.e. we’d consolidate things into a new IOAM option for Immediate-Export/PBT, avoid the “I-Flag” and describe actions (e.g. log/forward-a-copy/count/..) per the earlier discussion. We can discuss this in the IPPM WG meeting as part of the IOAM update slot.

Where would we best specify this new option? We could either write a new dedicated document for this new IOAM option (borrowing pieces from draft-song-ippm-postcard-based-telemetry-04), or fold it into the existing IOAM data fields draft. Does the WG have a preference?

Thanks, Frank



From: Tianran Zhou <zhoutianran@huawei.com>
Sent: Montag, 22. Juli 2019 14:16
To: Frank Brockners (fbrockne) <fbrockne@cisco.com>; ippm@ietf.org
Subject: Re: IPPM slides for IOAM data fields and IOAM flags updates

Hi Frank,

I think according to the side meeting in Prague, most of us believed an independent postcard option is better than the using of immediate export flag.
And draft-song-ippm-postcard-based-telemetry-04 has closed the discussion on flow id and sequence number by setting them optional.

Here are some of my thoughts:
- IOAM already has incremental tracing option and pre-allocated tracing option based on the way to operate metadata. Both have clear Semantics on operating metadata. It reasonable to use another option for PBT.
- Hardware is easy to realize the next step process by parsing the option type, without further flag matching.
- A new option will enable the extensibility for PBT related data fields. E.g., actions as proposed in the mailing list

What's your thoughts?

Thanks,
Tianran

________________________________
发件人: ippm [ippm-bounces@ietf.org] 代表 Frank Brockners (fbrockne) [fbrockne@cisco.com]
发送时间: 2019年7月22日 18:44
收件人: ippm@ietf.org<mailto:ippm@ietf.org>
主题: [ippm] IPPM slides for IOAM data fields and IOAM flags updates
Hi IOAM enthusiasts,

I’ve started to craft slides for the IOAM update in the IPPM WG meeting on Wednesday. Here is what I’ve assembled for covering draft-ietf-ippm-ioam-data-06 and draft-mizrahi-ippm-ioam-flags-00: https://docs.google.com/presentation/d/1nSbwvwWlexQ9Ns5VbtWavY9BQMpKT1RgjvCPGpwQFAw/

Appreciate your thoughts and comments.

Thanks, Frank