Re: [IPsec] I-D Action: draft-ietf-ipsecme-ikev2-fragmentation-03.txt

Yaron Sheffer <yaronf.ietf@gmail.com> Thu, 10 October 2013 06:00 UTC

Return-Path: <yaronf.ietf@gmail.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 90E7D21E8283 for <ipsec@ietfa.amsl.com>; Wed, 9 Oct 2013 23:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 dkYUI-JbHhE7 for <ipsec@ietfa.amsl.com>; Wed, 9 Oct 2013 23:00:14 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id AF8F721E80DB for <ipsec@ietf.org>; Wed, 9 Oct 2013 23:00:13 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id u56so1968935wes.33 for <ipsec@ietf.org>; Wed, 09 Oct 2013 23:00:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=aDyX5FbIlFqq/jcRQrVMpG7Z/54bD/BLb1oZdhQIVlE=; b=zDYZ+p+NE0bbrbjfP/2esHsqBeUIdn3khJeI9qtN6pWsM3uLKWAOyORL8/jsEcbuq6 M2cjQCvQ+fF24mAPCgS7OfZsuzqIrCcEcGkEQy0s8zbUOb/U22aZT2JJcU3fIkkI49hO WTo/qyS4bZBsThFcpWdB4QaPTHf5QFub8u6Wi5/3S6NdEb1JuPMAbKnjVLw41lNPX0q6 woBu2bsAi/QsdOCkg07TXKn2tBvppH3rA0PKszaenrqsA1qrj+UY2iFMztiB0ivyBLqL 4H2d5sf2SQA+tGpW2hdnlN9y1qaBaITwiKL30rUYm8OrS3MBIkC7iAdFrjLKEVtF4FU4 SkRw==
X-Received: by 10.195.13.164 with SMTP id ez4mr10415437wjd.11.1381384812665; Wed, 09 Oct 2013 23:00:12 -0700 (PDT)
Received: from [10.0.0.8] ([109.65.223.20]) by mx.google.com with ESMTPSA id jf2sm22093641wic.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 23:00:12 -0700 (PDT)
Message-ID: <5256426B.4030707@gmail.com>
Date: Thu, 10 Oct 2013 09:00:11 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Valery Smyslov <svanru@gmail.com>, Paul Wouters <paul@cypherpunks.ca>
References: <20131004123552.12797.87073.idtracker@ietfa.amsl.com> <44D6A1836A274C98907D95D59E530FE6@buildpc> <524EC6D8.9040006@gmail.com> <8B0A76CCEF2F4C65A9101BBD717B5C0F@buildpc> <alpine.LFD.2.10.1310041144500.10965@bofh.nohats.ca> <E46CD124E88F442495758F38BC026897@chichi> <alpine.LFD.2.10.1310081048530.7675@bofh.nohats.ca> <1B20E03AB216428AA7F16B898AA49FFD@buildpc>
In-Reply-To: <1B20E03AB216428AA7F16B898AA49FFD@buildpc>
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ipsec@ietf.org
Subject: Re: [IPsec] I-D Action: draft-ietf-ipsecme-ikev2-fragmentation-03.txt
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, 10 Oct 2013 06:00:14 -0000

>>> I also think that PMTU discovery isn't very useful for IKE.
>>> That's why it is MAY.
>>
>> That does not help implementors who still have to implement the MAY's.
>> if even you as a document author does not think it is veru usefil,
>> then I think it should just not be in the document.
>
> Sorry, I wasn't very clear. By "isn't very useful" I meant that it is
> not useful
> for the usual PMTU discovery goal in TCP - to find _maximum_ IP datagram
> size that is not fragmented by IP level. In IKE its the goal is different -
> to find _some_reasonable_ IP datagram size that is not fragmented by IP.
>
> If we have the size that is guaranteed to not be fragmented,
> no PMTU discovery will be needed. As far as I understand, for IPv6
> it is 1280 bytes. But as far as I know, there's no such value for IPv4.
> If we mandate (or recommend) using really small value e.g. 128 bytes,
> than the perfomance will suffer badly, so it it not a good option.
> I'm especially worring about network I'm not familiar with -
> mobile networks or other constrained environments.
> It would be great if some experts in such networks could clarify this.
>
I'm even more worried that if we use small fragments, reliability will 
deteriorate. Because we do not have per-packet acknowledgement, and so 
if any fragment is dropped, the whole message must be resent. This is 
probably a greater risk in mobile networks.