[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Re: [IPv6] Early Allocation on the IPv6 VTN option
From:       "Dongjie \(Jimmy\)" <jie.dong=40huawei.com () dmarc ! ietf ! org>
Date:       2023-06-05 8:24:55
Message-ID: 065b3245ee1a4209af74ad968d3d75ba () huawei ! com
[Download RAW message or body]

Hi Med, 

Thanks for your detailed review and valuable comments. 

I'm working on the replies to your comments and will send them soon. 

Best regards,
Jie

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of
> mohamed.boucadair@orange.com
> Sent: Friday, June 2, 2023 10:32 PM
> To: Ole Troan <otroan=40employees.org@dmarc.ietf.org>; 6man WG
> <ipv6@ietf.org>
> Cc: 6man Chairs <6man-chairs@ietf.org>; JACQUENET Christian INNOV/NET
> <christian.jacquenet@orange.com>
> Subject: Re: [IPv6] Early Allocation on the IPv6 VTN option
> 
> Hi Ole, all,
> 
> FWIW, please find below some comments to this draft:
> 
> * pdf:
> https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-6
> man-enhanced-vpn-vtn-id-04-rev%20Med.pdf
> * doc:
> https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-6
> man-enhanced-vpn-vtn-id-04-rev%20Med.doc
> 
> I do think that some further work is needed. In particular, there is room for
> the format to be simplified + the behavior better explained.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : ipv6 <ipv6-bounces@ietf.org> De la part de Ole Troan Envoyé :
> > jeudi 1 juin 2023 13:19 À : 6man WG <ipv6@ietf.org> Cc : 6man Chairs
> > <6man-chairs@ietf.org> Objet : [IPv6] Early Allocation on the IPv6 VTN
> > option
> >
> > Dear Working Group,
> >
> > We have received a request for an early allocation of the IPv6 VTN
> > option specified in:
> > draft-ietf-6man-enhanced-vpn-vtn-id-04.txt
> >
> > Conditions for early allocation is outlined in RFC7120.
> >
> > Note specifically this:
> >    c. The specifications of these code points must be stable; i.e., if
> >   there is a change, implementations based on the earlier and later
> >   specifications must be seamlessly interoperable.
> >
> > An early allocation will freeze the option format.
> > Would you mind reviewing the document and especially the option
> > definition and chime in if you think changes are required prior to
> > allocating a code point.
> >
> > For the chairs,
> > Ole
> > ------------------------------------------------------------------
> > --
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests:
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> >
> www.ietf.org%2Fmailman%2Flistinfo%2Fipv6&data=05%7C01%7Cmohamed.
> bo
> >
> ucadair%40orange.com%7Ce61dc67758a644f30a6908db6292274d%7C90c7
> a20a
> >
> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C638212152089785496%7CUnk
> nown%7C
> >
> TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL
> C
> >
> JXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hO6KoAiiNVPls1fFVKhYAKrsLI
> oSrpG
> > Wh1WHaFx20To%3D&reserved=0
> > ------------------------------------------------------------------
> > --
> 
> --------------------------------------------------------------------
> 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
--------------------------------------------------------------------
[prev in list] [next in list] [prev in thread] [next in thread]