Re: [IPsec] Informal poll on IKEv2 { over TCP | fragmentation }

Yoav Nir <ynir@checkpoint.com> Thu, 14 March 2013 12:09 UTC

Return-Path: <ynir@checkpoint.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E344121F8D0E for <ipsec@ietfa.amsl.com>; Thu, 14 Mar 2013 05:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.85
X-Spam-Level:
X-Spam-Status: No, score=-7.85 tagged_above=-999 required=5 tests=[AWL=0.150, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzk6Fm2M-ysx for <ipsec@ietfa.amsl.com>; Thu, 14 Mar 2013 05:09:57 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3931C21F8F62 for <ipsec@ietf.org>; Thu, 14 Mar 2013 05:09:57 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r2EC9jeX029733; Thu, 14 Mar 2013 14:09:50 +0200
X-CheckPoint: {5141BD2E-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Thu, 14 Mar 2013 14:09:45 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Thread-Topic: [IPsec] Informal poll on IKEv2 { over TCP | fragmentation }
Thread-Index: AQHOIKoDiGWFYKwEBE2odkleAjXVZJik9sIA
Date: Thu, 14 Mar 2013 12:09:44 +0000
Message-ID: <FEC3BAEA-EF5D-4344-AC09-CD13651103AF@checkpoint.com>
References: <20799.34490.611737.922474@fireball.kivinen.iki.fi> <AF3F21AE-8695-47FC-BC41-4097635D0C95@vpnc.org>
In-Reply-To: <AF3F21AE-8695-47FC-BC41-4097635D0C95@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.20.4]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5C496DD8D27B01448E0299E7BA75D0F4@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPsecme WG <ipsec@ietf.org>
Subject: Re: [IPsec] Informal poll on IKEv2 { over TCP | fragmentation }
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 12:09:59 -0000

On Mar 14, 2013, at 7:33 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> <chair-hat on>
> 
> It is seeming that consensus is trending towards "let's document the fragmentation method some vendors are already doing instead of finishing IKEv2-over-TCP", but I would like to check that. Please respond to the informal poll below.
> 
> --Paul Hoffman
> 
> 
> - I would prefer the WG to continue working on IKEv2 over TCP
> 
> - I would prefer the WG to stop working on IKEv2 over TCP and instead work on standardizing IKEv2 fragmentation
> 
> - I would prefer the WG to continue working on IKEv2 over TCP and also work on standardizing IKEv2 fragmentation

In another meeting, I said that standardizing two ways of achieving the same goal is a failure mode. I still believe that. I also believe that fragmentation is easier to fall back on than TCP. IOW an IKE-over-TCP draft would likely become "always use IKE over TCP" in a product (my company's clients that had IKE-over-TCP did exactly that), whereas fragmentation is more likely to become "use fragmentation if the the regular UDP did not get an answer". So:

"I would prefer the WG to stop working on IKEv2 over TCP and instead work on standardizing IKEv2 fragmentation"

However, I would prefer that we clear up the situation with Microsoft's IPR before making such a change to our charter.

Yoav