[spring] 答复: [Spring] A new draft on data fields encapsulation model of IOAM TLV in SRv6 network

Qiuyuanxiang <qiuyuanxiang@h3c.com> Mon, 07 June 2021 08:17 UTC

Return-Path: <qiuyuanxiang@h3c.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D164E3A3C09 for <spring@ietfa.amsl.com>; Mon, 7 Jun 2021 01:17:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.097
X-Spam-Status: No, score=0.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.998, HK_RANDOM_FROM=0.998, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9H-WCZ8Rug2t for <spring@ietfa.amsl.com>; Mon, 7 Jun 2021 01:17:32 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com []) (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 9223A3A3BD2 for <spring@ietf.org>; Mon, 7 Jun 2021 01:17:31 -0700 (PDT)
Received: from DAG2EX06-IDC.srv.huawei-3com.com ([]) by h3cspam02-ex.h3c.com with ESMTP id 1578Gvnh025922; Mon, 7 Jun 2021 16:16:58 +0800 (GMT-8) (envelope-from qiuyuanxiang@h3c.com)
Received: from DAG2EX06-IDC.srv.huawei-3com.com ( by DAG2EX06-IDC.srv.huawei-3com.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.4; Mon, 7 Jun 2021 16:17:00 +0800
Received: from DAG2EX06-IDC.srv.huawei-3com.com ([::1]) by DAG2EX06-IDC.srv.huawei-3com.com ([fe80::78f8:e244:d48:c15e%9]) with mapi id 15.01.2242.008; Mon, 7 Jun 2021 16:17:00 +0800
From: Qiuyuanxiang <qiuyuanxiang@h3c.com>
To: "Wangyali(Yali,Data Communication Standards and Patents Dept)" <wangyali11@huawei.com>, "spring@ietf.org" <spring@ietf.org>
CC: Haoyu Song <haoyu.song@futurewei.com>, Tianran Zhou <zhoutianran@huawei.com>
Thread-Topic: [spring] [Spring] A new draft on data fields encapsulation model of IOAM TLV in SRv6 network
Thread-Index: AddY8jd/cv9xYSWQRDiVo/BrDi55N///8GoA//sA9VA=
Date: Mon, 07 Jun 2021 08:17:00 +0000
Message-ID: <9e56f17c86a046eb90b5a2b919a1d636@h3c.com>
References: <47a2d3a236ad4d6daa580ed1b8302a70@h3c.com> <ca1cc9da6160433dae9e475bac4ecbbd@huawei.com>
In-Reply-To: <ca1cc9da6160433dae9e475bac4ecbbd@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
x-sender-location: DAG2
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MAIL: h3cspam02-ex.h3c.com 1578Gvnh025922
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/6oAYcqkLnmdIKvuba2abgIDL4SA>
Subject: [spring] 答复: [Spring] A new draft on data fields encapsulation model of IOAM TLV in SRv6 network
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2021 08:17:37 -0000

Hi yali,
Thank you very much for informing me of the existing draft-song-ippm-ioam-tunnel-mode-00.

For draft-song-ippm-ioam-tunnel-mode-00, I have a little question, which is also the problem that bothers me when I write draft-qiu-spring-srv6-ioam-encap-model-00.

In uniform model, draft-song-ippm-ioam-tunnel-mode-00 uses the method of copying the original header directly. But for some reason, it may not be possible to know in advance how many routers are in the tunnel, Whether this method works for Pre-allocated Trace Option-Type may require further discussion. We may need to specify usage scenarios for Uniform model.

In addition, would it be better to selectively partially synchronize the data fields of the IOAM TLV instead of full copies? 
For data field that needs to be modified hop-by-hop, we still need to modify the data after copying it, which will increases data plane processing. For example, the time delay needs to be calculated on the router, and the packet carries a timestamp, which needs to be modified by hop.

Best Regards,

发件人: Wangyali(Yali,Data Communication Standards and Patents Dept) [mailto:wangyali11@huawei.com] 
发送时间: 2021年6月4日 18:37
收件人: qiuyuanxiang (RD) <qiuyuanxiang@h3c.com>; spring@ietf.org
抄送: Haoyu Song <haoyu.song@futurewei.com>; Tianran Zhou <zhoutianran@huawei.com>
主题: RE: [spring] [Spring] A new draft on data fields encapsulation model of IOAM TLV in SRv6 network

Hi authors,

Glad to see you're also interested in this topic. 

Almost 3 years ago, there was a draft-song-ippm-ioam-tunnel-mode-00 we proposed to discuss the procedure of iOAM processing in tunnels with the uniform model and the pipe model. 

Welcome to join the discussion. Please feel free to let us know your comments and questions.


-----Original Message-----
From: Qiuyuanxiang [mailto:qiuyuanxiang@h3c.com] 
Sent: Friday, June 4, 2021 11:33 AM
To: spring@ietf.org
Subject: [spring] [Spring] A new draft on data fields encapsulation model of IOAM TLV in SRv6 network

Hi WG,

Recently we published a new draft on data fields encapsulation model of IOAM TLV in SRv6 network:

URL:            https://www.ietf.org/archive/id/draft-qiu-spring-srv6-ioam-encap-model-00.txt
Status:         https://datatracker.ietf.org/doc/draft-qiu-spring-srv6-ioam-encap-model/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-qiu-spring-srv6-ioam-encap-model

It introduces the data fields encapsulation model of IOAM TLV for the Segment Routing headend with H.Encaps encapsulation behavior in SRv6 network.

Your review and comments are welcome.

Best regards,

This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!