Re: [IPv6] I-D Action: draft-ietf-6man-enhanced-vpn-vtn-id-05.txt

"Dongjie (Jimmy)" <jie.dong@huawei.com> Sat, 08 July 2023 03:12 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 C4239C151981; Fri, 7 Jul 2023 20:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Level:
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8ucMzXA5dTq; Fri, 7 Jul 2023 20:12:16 -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 C545EC151093; Fri, 7 Jul 2023 20:12:15 -0700 (PDT)
Received: from lhrpeml500003.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4QyZyH6TNYz6J6xJ; Sat, 8 Jul 2023 11:10:15 +0800 (CST)
Received: from kwepemi500018.china.huawei.com (7.221.188.213) by lhrpeml500003.china.huawei.com (7.191.162.67) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Sat, 8 Jul 2023 04:12:12 +0100
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi500018.china.huawei.com (7.221.188.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Sat, 8 Jul 2023 11:12:10 +0800
Received: from kwepemi500017.china.huawei.com ([7.221.188.110]) by kwepemi500017.china.huawei.com ([7.221.188.110]) with mapi id 15.01.2507.027; Sat, 8 Jul 2023 11:12:10 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
CC: 6man Chairs <6man-chairs@ietf.org>
Thread-Topic: [IPv6] I-D Action: draft-ietf-6man-enhanced-vpn-vtn-id-05.txt
Thread-Index: AQHZsH5S3S63CXKcN0W6SZueBRIVJa+vLQlQ
Date: Sat, 08 Jul 2023 03:12:10 +0000
Message-ID: <85ccf1723eff442b834f2ad47d0405b3@huawei.com>
References: <168869836381.53981.17478975928854194568@ietfa.amsl.com>
In-Reply-To: <168869836381.53981.17478975928854194568@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.2.136]
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/S_u4NdtY4hkgeG5FcavpIlIbk40>
Subject: Re: [IPv6] I-D Action: draft-ietf-6man-enhanced-vpn-vtn-id-05.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 08 Jul 2023 03:12:19 -0000

Dear all, 

This update is mainly editorial to solve the review comments and suggestions received during the early allocation call on the IPv6 VTN Option. We also had constructive discussion with Med offline about the comments in detail.

In this version, the description about the VTN Option, its semantics and the processing behavior are further clarified, while its format has been stable. 

The IANA section is also updated to align with the IPv6 "Destination Options and Hop-by-Hop Options" registry.

With this update, the authors believe this document is ready for both the early allocation and the WG last call. 

Best regards,
Jie

> -----Original Message-----
> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
> Sent: Friday, July 7, 2023 10:53 AM
> To: i-d-announce@ietf.org
> Cc: ipv6@ietf.org
> Subject: [IPv6] I-D Action: draft-ietf-6man-enhanced-vpn-vtn-id-05.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This Internet-Draft is a work item of the IPv6 Maintenance (6MAN) WG of the
> IETF.
> 
>    Title           : Carrying Virtual Transport Network (VTN) Information in
> IPv6 Extension Header
>    Authors         : Jie Dong
>                      Zhenbin Li
>                      Chongfeng Xie
>                      Chenhao Ma
>                      Gyan Mishra
>    Filename        : draft-ietf-6man-enhanced-vpn-vtn-id-05.txt
>    Pages           : 12
>    Date            : 2023-07-06
> 
> Abstract:
>    Virtual Private Networks (VPNs) provide different customers with
>    logically separated connectivity over a common network
>    infrastructure.  With the introduction and evolvement of 5G and also
>    in some existing network scenarios, some customers may require
>    network connectivity services with advanced features comparing to
>    conventional VPN services.  Such kind of network service is called
>    enhanced VPNs (VPN+).  VPN+ can be used, for example, to deliver IETF
>    network slice services.
> 
>    A VTN is a virtual underlay network that is associated with a network
>    topology, and is allocated with a set of dedicated or shared
>    resources from the underlay physical network.  VPN+ services can be
>    delivered by mapping one or a group of overlay VPNs to the
>    appropriate VTNs as the virtual underlay.  For packet forwarding in a
>    specific VTN, some fields in the data packet are used to identify the
>    VTN the packet belongs to, so that VTN-specific processing can be
>    performed on each node along a VTN-specific path.
> 
>    This document specifies a new IPv6 Hop-by-Hop option to carry the VTN
>    related information in data packets, which could be used to identify
>    the VTN-specific processing to be performed on the packets by each
>    network node along a VTN-specific path.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-vpn-vtn-id/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-6man-enhanced-vpn-vtn-id-05
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-6man-enhanced-vpn-vtn-id-0
> 5
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------