RE: A draft on the encapsulation of end-to-end IETF network slice information in IPv6 data plane
"Dongjie (Jimmy)" <jie.dong@huawei.com> Mon, 24 May 2021 11:25 UTC
Return-Path: <jie.dong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710813A24B3 for <ipv6@ietfa.amsl.com>; Mon, 24 May 2021 04:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cKbTubtVvG83 for <ipv6@ietfa.amsl.com>; Mon, 24 May 2021 04:25:45 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36FB83A24E4 for <6man@ietf.org>; Mon, 24 May 2021 04:25:45 -0700 (PDT)
Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FpZRY659xz6rmLm for <6man@ietf.org>; Mon, 24 May 2021 19:16:57 +0800 (CST)
Received: from dggeme753-chm.china.huawei.com (10.3.19.99) by fraeml703-chm.china.huawei.com (10.206.15.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 24 May 2021 13:25:41 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme753-chm.china.huawei.com (10.3.19.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 24 May 2021 19:25:39 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2176.012; Mon, 24 May 2021 19:25:39 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "otroan@employees.org" <otroan@employees.org>
CC: "6man@ietf.org" <6man@ietf.org>
Subject: RE: A draft on the encapsulation of end-to-end IETF network slice information in IPv6 data plane
Thread-Topic: A draft on the encapsulation of end-to-end IETF network slice information in IPv6 data plane
Thread-Index: AddN6qlZvQtgESJJSb+tDwu4II3fPf//41eA//rsWcA=
Date: Mon, 24 May 2021 11:25:39 +0000
Message-ID: <a661bbb138704ff1b5130ee4922f3318@huawei.com>
References: <e4844158fd844388bba27293e91b2265@huawei.com> <DBB92575-BEF4-4EE2-81E7-D62755940F52@employees.org>
In-Reply-To: <DBB92575-BEF4-4EE2-81E7-D62755940F52@employees.org>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.143]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AHtofQb16gukCYGqcw2LKu0Ticw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 May 2021 11:25:56 -0000
Hi Ole, Thanks for your comment. It is expected that the identifiers defined in this draft will be parsed or processed by some network nodes along the path, rather than only the endpoints, thus maybe it is more convenient to carry them in the IPv6 header. This could also reduce the overhead of introducing other tunnel layers to the IPv6 network. Best regards, Jie > -----Original Message----- > From: otroan@employees.org [mailto:otroan@employees.org] > Sent: Friday, May 21, 2021 4:58 PM > To: Dongjie (Jimmy) <jie.dong@huawei.com> > Cc: 6man@ietf.org > Subject: Re: A draft on the encapsulation of end-to-end IETF network slice > information in IPv6 data plane > > Hi Jie, > > > Recently we published a draft on the encapsulation of end-to-end IETF > network slice information in IPv6 data plane: > > > > > https://datatracker.ietf.org/doc/html/draft-li-6man-e2e-ietf-network-slicing > > > > This document defines the mechanism of encapsulating the end-to-end > network slice related identifiers in IPv6 packet, which is aligned with the > framework as defined in draft-li-teas-e2e-ietf-network-slicing. > > What are the benefits of using an IPv6 extension header to carry the meta > data? > In contrast to embedding it in a tunnel header (like what GRE, Geneve, etc, > etc does). > > Best regards, > Ole
- A draft on the encapsulation of end-to-end IETF n… Dongjie (Jimmy)
- Re: A draft on the encapsulation of end-to-end IE… otroan
- RE: A draft on the encapsulation of end-to-end IE… Dongjie (Jimmy)
- Re: A draft on the encapsulation of end-to-end IE… Tom Herbert
- Re: A draft on the encapsulation of end-to-end IE… Carsten Bormann
- RE: A draft on the encapsulation of end-to-end IE… Dongjie (Jimmy)
- RE: A draft on the encapsulation of end-to-end IE… Dongjie (Jimmy)
- Re: A draft on the encapsulation of end-to-end IE… Tom Herbert