IETF Logo Mail Archive

Re: A draft on the encapsulation of end-to-end IETF network slice information in IPv6 data plane

otroan@employees.org Fri, 21 May 2021 08:58 UTC

Return-Path: <otroan@employees.org>
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 1EAF63A203E for <ipv6@ietfa.amsl.com>; Fri, 21 May 2021 01:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=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 bsE6jSqVwIl6 for <ipv6@ietfa.amsl.com>; Fri, 21 May 2021 01:58:02 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E38D43A203D for <6man@ietf.org>; Fri, 21 May 2021 01:58:02 -0700 (PDT)
Received: from astfgl.hanazo.no (unknown [IPv6:2a01:799:151f:d300:8968:9138:cfab:fe3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id E761C4E11AF9; Fri, 21 May 2021 08:58:00 +0000 (UTC)
Received: from smtpclient.apple (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 746DF58DB524; Fri, 21 May 2021 10:57:56 +0200 (CEST)
From: otroan@employees.org
Message-Id: <DBB92575-BEF4-4EE2-81E7-D62755940F52@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_F2D7936E-D2A5-4BF7-BC71-1B170F09439F"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Subject: Re: A draft on the encapsulation of end-to-end IETF network slice information in IPv6 data plane
Date: Fri, 21 May 2021 10:57:55 +0200
In-Reply-To: <e4844158fd844388bba27293e91b2265@huawei.com>
Cc: "6man@ietf.org" <6man@ietf.org>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
References: <e4844158fd844388bba27293e91b2265@huawei.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/t6aEzHPkmCViPnBzQOiIvusrBxE>
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: Fri, 21 May 2021 08:58:07 -0000

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

v2.23.0 | Report a Bug | By Email