[ippm] a flag proposal to draft-ietf-ippm-ioam-data
Tianran Zhou <zhoutianran@huawei.com> Tue, 19 March 2019 09:50 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 837FF131218; Tue, 19 Mar 2019 02:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 aajmXB-d6xKG; Tue, 19 Mar 2019 02:50: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 59F21131200; Tue, 19 Mar 2019 02:50:46 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 6C9CB8457F1BCD4C7F43; Tue, 19 Mar 2019 09:50:44 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 19 Mar 2019 09:50:43 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0415.000; Tue, 19 Mar 2019 17:50:37 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: "draft-ietf-ippm-ioam-data.all@ietf.org" <draft-ietf-ippm-ioam-data.all@ietf.org>
CC: IETF IPPM WG <ippm@ietf.org>
Thread-Topic: a flag proposal to draft-ietf-ippm-ioam-data
Thread-Index: AdTeNhoC6KBfr+L7Ql2B4/3nxLFBKA==
Date: Tue, 19 Mar 2019 09:50:36 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21B582F4B1@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.116]
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/H_d6ArjpD5izt5kg4cOERu2kR4w>
Subject: [ippm] a flag proposal to draft-ietf-ippm-ioam-data
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, 19 Mar 2019 09:50:48 -0000
Hi Authors, Here I am going to propose a flag bit to indicate the important data for IOAM tracing mode. Although I see the Flag is used up in the latest draft-ietf-ippm-ioam-data-05, I want to see the proposed feature can be implemented in some way. As we can see, the IOAM tracing mode will generate large amount of data to export at the tail node. This will cost a lot of export bandwidth, and collector/analytics will suffer the big data processing. So I am thinking an easy way to reduce the exporting data. This proposal is to use a flag bit to indicate the important data. Initially, the flag is unset. Whenever a transit node feel the data is important to notice the collector, it sets the flag. For example, when the buffer breach the ECN water mark, or the transit delay breach the threshold. At the tail node, only the tagged packet will trigger the metadata export. What's your thoughts? Best, Tianran
- [ippm] a flag proposal to draft-ietf-ippm-ioam-da… Tianran Zhou