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

Qiuyuanxiang <qiuyuanxiang@h3c.com> Fri, 04 June 2021 08:14 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 1E1343A2E6F for <spring@ietfa.amsl.com>; Fri, 4 Jun 2021 01:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.998, HK_RANDOM_FROM=0.998, HTML_MESSAGE=0.001, 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 IgRS4Cws8STQ for <spring@ietfa.amsl.com>; Fri, 4 Jun 2021 01:14:26 -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 90BAE3A2E72 for <spring@ietf.org>; Fri, 4 Jun 2021 01:14:25 -0700 (PDT)
Received: from DAG2EX04-BASE.srv.huawei-3com.com ([]) by h3cspam02-ex.h3c.com with ESMTP id 1548E6a3088250 for <spring@ietf.org>; Fri, 4 Jun 2021 16:14:06 +0800 (GMT-8) (envelope-from qiuyuanxiang@h3c.com)
Received: from DAG2EX06-IDC.srv.huawei-3com.com ( by DAG2EX04-BASE.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 16:14:08 +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; Fri, 4 Jun 2021 16:14:08 +0800
From: Qiuyuanxiang <qiuyuanxiang@h3c.com>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [Spring] A new draft on data fields encapsulation model of IOAM TLV in SRv6 network
Thread-Index: AddZGXUUZuOkRn7RTSGKspr/QYLJVA==
Date: Fri, 04 Jun 2021 08:14:08 +0000
Message-ID: <8e8e8ca8ec20426ab6bcd791ff3fa07b@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_8e8e8ca8ec20426ab6bcd791ff3fa07bh3ccom_"
MIME-Version: 1.0
X-MAIL: h3cspam02-ex.h3c.com 1548E6a3088250
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/01OAmUTQw7qra-ooToMu959iGik>
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 08:14:30 -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!