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

Hi all, 

An updated version of draft-ietf-6man-enhanced-vpn-vtn-id has been submitted. The major changes are:

- Clarifies that the processing procedure of VTN option with non-zero Context Types are out of the scope and will be specified in separate documents. 

- Adds IANA request for the creation of the "VTN option Context Type" registry. 

- Some editorial changes. 

As mentioned in the presentation at IETF 116, with this update, this document is positioned as the base of the VTN option specification, and it allows further extensions based on new Context Types in future. 

Review comments and suggestions are welcome. 

Best regards,
Jie

> -----Original Message-----
> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
> Sent: Thursday, May 18, 2023 2:54 PM
> To: i-d-announce@ietf.org
> Cc: ipv6@ietf.org
> Subject: [IPv6] I-D Action: draft-ietf-6man-enhanced-vpn-vtn-id-04.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-04.txt
>    Pages           : 12
>    Date            : 2023-05-17
> 
> 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 other
>    network scenarios, some existing or new customers may require
>    connectivity services with advanced characteristics comparing to
>    traditional VPNs.  Such kind of network service is called enhanced
>    VPNs (VPN+).  VPN+ can be used to deliver IETF network slices, and
>    could also be used for other application scenarios.
> 
>    A Virtual Transport Network (VTN) is a virtual underlay network which
>    consists of a set of dedicated or shared network resources allocated
>    from the physical underlay network, and is associated with a
>    customized logical network topology.  VPN+ services can be delivered
>    by mapping one or a group of overlay VPNs to the appropriate VTNs as
>    the virtual underlay.  In packet forwarding, some fields in the data
>    packet needs to be used to identify the VTN the packet belongs to, so
>    that VTN-specific processing can be performed on each node the packet
>    traverses.
> 
>    This document proposes a new Hop-by-Hop option of IPv6 extension
>    header to carry the VTN related information in data packets, which
>    could used to identify the VTN specific processing to be performed on
>    the packets.  The procedure of processing the VTN option is also
>    specified.
> 
> 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-0
> 4
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-6man-enhanced-vpn-vtn-id
> -04
> 
> 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
> --------------------------------------------------------------------