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

Justin Iurman <justin.iurman@uliege.be> Fri, 14 July 2023 15:10 UTC

Return-Path: <justin.iurman@uliege.be>
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 71D23C151524; Fri, 14 Jul 2023 08:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uliege.be
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 9twIKPhs1Lno; Fri, 14 Jul 2023 08:10:45 -0700 (PDT)
Received: from serv108.segi.ulg.ac.be (serv108.segi.ulg.ac.be [139.165.32.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 373EEC151AE8; Fri, 14 Jul 2023 08:10:43 -0700 (PDT)
Received: from [192.168.1.62] (125.179-65-87.adsl-dyn.isp.belgacom.be [87.65.179.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by serv108.segi.ulg.ac.be (Postfix) with ESMTPSA id 5FE732019D96; Fri, 14 Jul 2023 17:10:41 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 serv108.segi.ulg.ac.be 5FE732019D96
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uliege.be; s=ulg20190529; t=1689347441; bh=lqK9PbiSgfEzTshG286UfdwZG7ga/HM3/eE9kla+bXQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=LYxYQQ0ncItBtZBbm3kao/jTli/2ojN6N+m0eROy4q3yxlOE5I+HhwEy640+0/IU+ IuUn5n6BJ872FEJXepCXZTFsNmUeCpJ4sPbY7MqoXW6c/Pf3EUwkT3KE203Zw926TB man14EfLxvz44n+519zxBKLITMYz9Z0OPunw+5ufMly7DWIUxb3pW+XT6liV4kCS3E GeP7Ef1WlckfPEkC7Ql8K0tHEulsKxwCpNDyJTmsi6KOF37XKbCvOPd3NBIAVEEjjq f7O2iW3KPHn2YlMNYKI6u+SLgxaiaUm7lLfX6WMc5XwFpd+3WT7Njtb7C+n08ABDJh /m5eFHS+Qz6dA==
Message-ID: <f16e5606-dd01-1932-fd90-852a674ed945@uliege.be>
Date: Fri, 14 Jul 2023 17:10:41 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
Content-Language: en-US
To: "Dongjie (Jimmy)" <jie.dong=40huawei.com@dmarc.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Cc: 6man Chairs <6man-chairs@ietf.org>
References: <168869836381.53981.17478975928854194568@ietfa.amsl.com> <85ccf1723eff442b834f2ad47d0405b3@huawei.com>
From: Justin Iurman <justin.iurman@uliege.be>
In-Reply-To: <85ccf1723eff442b834f2ad47d0405b3@huawei.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/F-Lj8xz6QMqiZaSL885MS0pBqc4>
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: Fri, 14 Jul 2023 15:10:49 -0000

Hi Jie,

I think it would make sense to keep value 0 as reserved (just like you 
did for value 255, since they are considered special values) in the "VTN 
Option Context Type" registry. So what I suggest is to move Resource ID 
to value 1.

OLD:
       Value          Description       Reference
       -----------------------------------------------
         0            Resource ID      [this document]
       1-254          Unassigned
        255           Reserved         [this document]

NEW:
       Value          Description       Reference
       -----------------------------------------------
         0            Reserved         [this document]
         1            Resource ID      [this document]
       2-254          Unassigned
        255           Reserved         [this document]

Cheers,
Justin

On 7/8/23 05:12, Dongjie (Jimmy) wrote:
> 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
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------