Re: [IPsec] New version of IKEv2 TCP Encapsulation draft

2016-03-28 Thread Tommy Pauly
arified. This should refer to the TLS NULL cipher, not ESP. > > 8. The draft is silent about ESP Sequence Numbers. I think a few words could > be added that while the ESP SN are unnecessary with TCP encapsulation, > the sender still must increnet it in every sent pack

Re: [IPsec] New version of IKEv2 TCP Encapsulation draft

2016-03-24 Thread Samy Touati
place. Thanks. Samy. From: IPsec <ipsec-boun...@ietf.org> on behalf of Valery Smyslov <sva...@gmail.com> Date: Wednesday, March 23, 2016 at 5:03 AM To: Tommy Pauly <tpa...@apple.com>, "ipsec@ietf.org" <ipsec@ietf.org> Subject: Re: [IPsec] New version of IK

Re: [IPsec] New version of IKEv2 TCP Encapsulation draft

2016-03-23 Thread Valery Smyslov
Sent: Tuesday, February 16, 2016 12:52 AM Subject: [IPsec] New version of IKEv2 TCP Encapsulation draft Hello all, I’ve just posted a new version of the IKEv2 and IPSec TCP Encapsulation draft. The changes include: - Making the use case (as a last resort if UDP is blocked) more clear

[IPsec] New version of IKEv2 TCP Encapsulation draft

2016-02-15 Thread Tommy Pauly
Hello all, I’ve just posted a new version of the IKEv2 and IPSec TCP Encapsulation draft. The changes include: - Making the use case (as a last resort if UDP is blocked) more clear in the introduction - Clarify connection establishment and teardown section (allowing a resumed connection to