[sfc] Regarding draft-li-6man-ipv6-sfc-ifit-00.txt
Lizhenbin <lizhenbin@huawei.com> Mon, 18 March 2019 16:57 UTC
Return-Path: <lizhenbin@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF3D13111D; Mon, 18 Mar 2019 09:57:38 -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 pR5q39FPdTnM; Mon, 18 Mar 2019 09:57:36 -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 5479B130E94; Mon, 18 Mar 2019 09:57:32 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E413D4C0367324A3793A; Mon, 18 Mar 2019 16:57:29 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 18 Mar 2019 16:57:29 +0000
Received: from DGGEMM512-MBX.china.huawei.com ([169.254.3.122]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0415.000; Tue, 19 Mar 2019 00:57:23 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
CC: "sfc@ietf.org" <sfc@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: Regarding draft-li-6man-ipv6-sfc-ifit-00.txt
Thread-Index: AQHU3amW8zFsio6B9kGSEVW4vD19Xg==
Date: Mon, 18 Mar 2019 16:57:23 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F56D5F9@dggemm512-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.45.104.117]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/um34EH_ObuHkUC36pYqAsMTNhxs>
Subject: [sfc] Regarding draft-li-6man-ipv6-sfc-ifit-00.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2019 16:57:39 -0000
Hi Folks, As the new services develops, there proposed several encapsulations related with SFC, In-situ OAM, etc. These services are tried to define independent headers. But in the scenario of IPv6, especially when SRH is introduced for SRv6, such encapsulations faces some challenges. The draft, draft-li-6man-ipv6-sfc-ifit-00, tries to identify the possible problems and proposes the consideration on how to optimize these encapsulations in the scenarios of IPv6/SRv6 which includes: 1. Separate the SFC/IFIT path service into two parts, i.e. instruction and recording parts. 2. Defines the unified options as path service instruction which can be used in both Hop-by-Hop options Header and SRH. 3. Defines the independent metadata header for IPv6 to record metadata info for services. SFC WG and IPPM WG are copied. Comments and suggestions are very welcome! Best Regards, Zhenbin (Robin) ________________________________________ 发件人: internet-drafts@ietf.org [internet-drafts@ietf.org] 发送时间: 2019年3月12日 0:20 收件人: Pengshuping (Peng Shuping); Lizhenbin 主题: New Version Notification for draft-li-6man-ipv6-sfc-ifit-00.txt A new version of I-D, draft-li-6man-ipv6-sfc-ifit-00.txt has been successfully submitted by Zhenbin Li and posted to the IETF repository. Name: draft-li-6man-ipv6-sfc-ifit Revision: 00 Title: Consideration of IPv6 Encapsulation for SFC and IFIT Document date: 2019-03-11 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/internet-drafts/draft-li-6man-ipv6-sfc-ifit-00.txt Status: https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/ Htmlized: https://tools.ietf.org/html/draft-li-6man-ipv6-sfc-ifit-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-li-6man-ipv6-sfc-ifit Abstract: Service Function Chaining (SFC) and In-situ Flow Information Telemetry (IFIT) are important path services along with the packets. In order to support these services, several encapsulations have been defined. The document analyzes the problems of these encapsulations in the IPv6 scenario and proposes the possible optimized encapsulation for IPv6. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat