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

Yejinrong <jrong.y@h3c.com> Fri, 04 June 2021 09:28 UTC

Return-Path: <jrong.y@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 5BFE33A3097 for <spring@ietfa.amsl.com>; Fri, 4 Jun 2021 02:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id AsDBwFed2co2 for <spring@ietfa.amsl.com>; Fri, 4 Jun 2021 02:28:52 -0700 (PDT)
Received: from h3cspam01-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 E72F03A3095 for <spring@ietf.org>; Fri, 4 Jun 2021 02:28:51 -0700 (PDT)
Received: from DAG2EX08-IDC.srv.huawei-3com.com ([]) by h3cspam01-ex.h3c.com with ESMTP id 1549SLwD060803 for <spring@ietf.org>; Fri, 4 Jun 2021 17:28:21 +0800 (GMT-8) (envelope-from jrong.y@h3c.com)
Received: from DAG2EX09-IDC.srv.huawei-3com.com ( by DAG2EX08-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; Fri, 4 Jun 2021 17:28:24 +0800
Received: from DAG2EX09-IDC.srv.huawei-3com.com ([fe80::c83b:8401:2e7d:cb1b]) by DAG2EX09-IDC.srv.huawei-3com.com ([fe80::c83b:8401:2e7d:cb1b%6]) with mapi id 15.01.2242.008; Fri, 4 Jun 2021 17:28:24 +0800
From: Yejinrong <jrong.y@h3c.com>
To: "spring@ietf.org" <spring@ietf.org>
CC: Qiuyuanxiang <qiuyuanxiang@h3c.com>
Thread-Topic: [Spring] A new draft on data fields encapsulation model of IOAM TLV in SRv6 network
Thread-Index: AddZI+QkeMpb3cGaQi2oToJuf3Jm/A==
Date: Fri, 4 Jun 2021 09:28:24 +0000
Message-ID: <e7e3c16b91474ae7b24844c549a2fcc3@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_e7e3c16b91474ae7b24844c549a2fcc3h3ccom_"
MIME-Version: 1.0
X-MAIL: h3cspam01-ex.h3c.com 1549SLwD060803
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/8V7DPW1OVTiWZAoCpPVJrN1pF-k>
X-Mailman-Approved-At: Fri, 04 Jun 2021 02:31:13 -0700
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: Fri, 04 Jun 2021 09:28:58 -0000

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!