Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-19.txt

2017-04-25 Thread Miika Komu
, Christer -Original Message- From: Hipsec [mailto:hipsec-boun...@ietf.org] On Behalf Of Miika Komu Sent: 27 March 2017 10:41 To: hipsec@ietf.org Subject: Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-19.txt Hi, the preliminary version is now published as it is (except I had

Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-19.txt

2017-04-10 Thread Miika Komu
Hi Jeff, thanks, good catch. This change will be in the next version. On 03/28/2017 06:11 PM, Jeff Ahrenholz wrote: Hi Miika, The new paragraph on keepalives (Section 5.3) looks good. For the NOTIFY code, NAT_KEEPALIVE value (“TBD by IANA: 16384”) maybe suggest 16385? ...since we already

Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-19.txt

2017-03-28 Thread Christer Holmberg
Of Miika Komu Sent: 27 March 2017 10:41 To: hipsec@ietf.org Subject: Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-19.txt Hi, the preliminary version is now published as it is (except I had to change publication the date). The suggestions from Christer are not yet here and will require

Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-19.txt

2017-03-28 Thread Jeff Ahrenholz
Hi Miika, The new paragraph on keepalives (Section 5.3) looks good. For the NOTIFY code, NAT_KEEPALIVE value (“TBD by IANA: 16384”) maybe suggest 16385? ...since we already have “I2_ACKNOWLEDGEMENT 16384” in RFC 5201 and RFC 7401. thanks, -Jeff On 3/27/17, 12:41 AM, "Hipsec on behalf of Miika

Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-19.txt

2017-03-27 Thread Miika Komu
Hi, the preliminary version is now published as it is (except I had to change publication the date). The suggestions from Christer are not yet here and will require some time to be fixed. On 03/27/2017 10:37 AM, internet-dra...@ietf.org wrote: A New Internet-Draft is available from the