network telemetry framework

Haoyu song <haoyu.song@huawei.com> Mon, 02 April 2018 22:53 UTC

Return-Path: <haoyu.song@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 047CB12DA16 for <rtgwg@ietfa.amsl.com>; Mon, 2 Apr 2018 15:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 U8NETiVUKOwA for <rtgwg@ietfa.amsl.com>; Mon, 2 Apr 2018 15:53:07 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 675301252BA for <rtgwg@ietf.org>; Mon, 2 Apr 2018 15:53:07 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 75BB94509996D for <rtgwg@ietf.org>; Mon, 2 Apr 2018 23:53:03 +0100 (IST)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 2 Apr 2018 23:53:04 +0100
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.91]) by SJCEML703-CHM.china.huawei.com ([169.254.5.179]) with mapi id 14.03.0382.000; Mon, 2 Apr 2018 15:53:01 -0700
From: Haoyu song <haoyu.song@huawei.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: network telemetry framework
Thread-Topic: network telemetry framework
Thread-Index: AdPK1GoBudNhopJ7S7az3+/emex4bA==
Date: Mon, 2 Apr 2018 22:53:00 +0000
Message-ID: <78A2745BE9B57D4F9D27F86655EB87F93749E7F6@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.209.217.150]
Content-Type: multipart/alternative; boundary="_000_78A2745BE9B57D4F9D27F86655EB87F93749E7F6SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/iuPGmdwe8hx5kX-2abCZJ14w83I>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2018 22:53:09 -0000

Dear all,

The WG presentation triggered a lot warm discussions on this topic.
We feel there is a need to formalize the terminologies and normalize the taxonomy for network telemetry. This is an important step for us to understand the status quo and the gaps toward the next generation of network structure.
We also believe this work is highly relevant to the routing domain because the new routing paradigms rely on good telemetry to support

The latest version can be found at:
https://tools.ietf.org/html/draft-song-ntf-01
The document is still at its early stage. We welcome any comments and suggestions to scope it and contribute to it.
Thank you very much!

Best regards,
Haoyu