RE: Adoption Call for <draft-dong-6man-enhanced-vpn-vtn-id>

Hi Adrian,

Thanks for your support and comment. Please see some replies inline:

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: Wednesday, February 2, 2022 3:45 AM
> To: 'Bob Hinden' <bob.hinden@gmail.com>; 'IPv6 List' <ipv6@ietf.org>
> Subject: RE: Adoption Call for <draft-dong-6man-enhanced-vpn-vtn-id>
> 
> Hi Bob, all,
> 
> I just read the most recent copy of this draft:
> 
> I support adoption and promise to review the document further within the
> working group.
> 
> Here are some comments on the current version which, IMHO, do not need to
> be fixed until after adoption.
> 
> - Admirably short!
> - The BCP 14 boilerplate seems to be very slightly broken

Thanks for pointing this out, we will fix the boilerplate in next version. 

> - I think the reference to draft-hinden-6man-hbh-processing is
>    important, but:
>      - that draft has expired
>      - fortunately there is now draft-ietf-6man-hbh-processing
>         (perhaps the chairs could sort out the "replaced by" links)
>      - I think the reference should actually be normative

We will refer to the recently adopted draft-ietf-6man-hbh-processing in next version. 

> - I looked at this draft from the perspective of
>   draft-ietf-teas-ietf-network-slices, of which I am editor, and
>   draft-ietf-teas-enhanced-vpn, into which I have put some effort.
>      - I'm pleased to see alignment of terminology
>      - It might be helpful to reference the TEAS slicing draft where
>         this document mentions slicing

Agreed and we can add some text and a reference to the teas slicing draft. 

> - I am unclear of the purpose of the editor's note in section 2, nor
>   the inclusion of Figure 2.
>      - The combination of those things makes it seem like the VTN
>         Resource ID must be partitioned 8/24 as shown in the figure.
>         I don't think that is the intention (or a good idea, in general).

No, that was not our intention. It is just to show that the length of the S-NSSAI is 4 octets.

>      - There is not a lot of value in reproducing a figure from another
>         (referenced) document.

Agreed. We can remove that figure in next version.

>      - The "Editor's note" and figure could perhaps be replaced with
>         something like:
>         Note that, if a deployment found it useful, the four-octet VTN
>         Resource ID field could hold the four-octet Single Network Slice
>         Selection Assistance Information (S-NSSAI) defined in 3GPP
>         [TS23501].

Thanks for the suggestion. It looks good to me. 

> - Sections 3, 3.1, and 3.2 contain "SHOULD" and I don't understand
>   how/why an implementation would vary from that. The text needs
>   to give guidance or use "MUST".

We will review the whole document and replace the "SHOULD" with "MUST" where appropriate. 

Many thanks,
Jie

> 
> Best,
> Adrian
> -----Original Message-----
> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Bob Hinden
> Sent: 27 January 2022 05:49
> To: IPv6 List <ipv6@ietf.org>
> Cc: Bob Hinden <bob.hinden@gmail.com>
> Subject: Adoption Call for <draft-dong-6man-enhanced-vpn-vtn-id>
> 
> This message starts a two week 6MAN call on adopting:
> 
>  Title:          Carrying Virtual Transport Network (VTN) Identifier in IPv6
> Extension
>                  Header
>  Authors:        J. Dong, Z. Li, C. Xie, C. Ma, G. Mishra
>  File Name:      draft-dong-6man-enhanced-vpn-vtn-id-06
>  Document date:  October 24, 2021
> 
> https://datatracker.ietf.org/doc/html/draft-dong-6man-enhanced-vpn-vtn-id-0
> 6
> 
> as a working group document.  Substantive comments and statements of
> support for adopting this document should be sent to the mailing list.
> Editorial suggestions can be sent to the authors.  This adoption call will end
> on 10 February 2022.
> 
> Further, if you are willing to work on this document, either as contributor,
> author, or reviewer please notify the list.   This will provide the chairs
> with an indication of the energy level in the working group to work on this
> document.
> 
> Bob & Ole
> 6man Chairs
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------