Re: [IPsec] Charter update

Yaron Sheffer <yaronf.ietf@gmail.com> Sat, 19 July 2014 19:58 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05A411A00DB for <ipsec@ietfa.amsl.com>; Sat, 19 Jul 2014 12:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vep6fj-u-Rgt for <ipsec@ietfa.amsl.com>; Sat, 19 Jul 2014 12:58:18 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A2B51A00D5 for <ipsec@ietf.org>; Sat, 19 Jul 2014 12:58:18 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id m15so4784922wgh.3 for <ipsec@ietf.org>; Sat, 19 Jul 2014 12:58:17 -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=+7UKrdX7JTDEgkjTXZgyjHLjcPDRH8A7/jw/rpUAw9s=; b=K/8Bkqy4rcIIAYbjoCT/MFm+j0DvUOeYbcnU9Qrpc4p+cq2vM7T/mjWILprPN010ol vIuww/Ll30unzqbG38Sn1cE79eSNmVtXsp8CbB/RaIlXM0YcCQNcG3cDAn4I//tFkLjh CZgou44l7Pl6aAMjKsITsktO1ueB9X0O8glfiI9Tv3oOpkWm6R5UMy8+Z0UuvpBUyMJ1 SkhSd5ifxSdt24lybbsKlKWBDQ9jaPoyC5YWAQw+yQviKxqo3YexppPQdLYfSiB4dWpu d+SxJT0Qe9dpaCNVqw+NY8OgBb2r0+fNx/emdvKzvgKzB6d6u4F8FQba8gma6Gy0CsRh gflA==
X-Received: by 10.194.187.101 with SMTP id fr5mr7630815wjc.125.1405799897078; Sat, 19 Jul 2014 12:58:17 -0700 (PDT)
Received: from [10.0.0.1] ([109.67.0.77]) by mx.google.com with ESMTPSA id x3sm21603260wia.11.2014.07.19.12.58.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 19 Jul 2014 12:58:16 -0700 (PDT)
Message-ID: <53CACDD6.1090707@gmail.com>
Date: Sat, 19 Jul 2014 22:58:14 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Paul Wouters <paul@nohats.ca>
References: <53CAA14C.80301@gmail.com> <alpine.LFD.2.10.1407191539350.22651@bofh.nohats.ca>
In-Reply-To: <alpine.LFD.2.10.1407191539350.22651@bofh.nohats.ca>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipsec/Yfs6_bemxCiJYZYZ8rn_0C3fEvQ
Cc: IPsecME WG <ipsec@ietf.org>
Subject: Re: [IPsec] Charter update
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 19 Jul 2014 19:58:20 -0000

>>    Recently discovered incorrect behavior of ISPs poses a
>>    challenge to IKE, whose UDP messages (especially #3 and #4)
>>    sometimes get fragmented at the IP level and then dropped
>>    by these ISPs. There is interest in solving this issue by
>>    allowing transport of IKE over TCP; this is currently
>>    implemented by some vendors. The group will standardize such
>>    a solution.
>
> The working group had already reached consensus not to support two
> different fragmentation solutions and to only support
> draft-smyslov-ipsecme-ikev2-fragmentation, after Yoav's IKE TCP
> presentation, I believe in London? So I don't think this item belongs
> on the agenda, unless we are looking at revising that earlier decision.

We have a fragmentation draft (almost) past IESG review. So we're not 
revising any decision. "The group will standardize such a solution" is 
still correct, until we actually publish the document.

>
>> Goals and Milestones:
>>
>>   Done - IETF Last Call on large scale VPN use cases and requirements
>>   Done - IETF last call on IKE fragmentation solution
>>   Done - IETF last call on new mandatory-to-implement algorithms
>>
>>   [No current milestones]
>
> Could we add something about assisting  Opportunistic Encryption, or
> whatever term will be used? There is the auth_none draft, and there
> will be an OE draft by the libreswan team soon. Those will end up in
> ipsecme.

Quoting the new text, the group "will only take on new work items if a 
strong community interest can be seen." Do we have other people 
supporting such an addition to the charter?

>
> Paul