Re: [Lwip] [IPsec] The LWIG WG has placed draft-mglt-lwig-minimal-esp in state "Call For Adoption By WG Issued"

Paul Wouters <paul@nohats.ca> Thu, 14 February 2019 07:30 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FCA513102D for <lwip@ietfa.amsl.com>; Wed, 13 Feb 2019 23:30:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 ukICM7Y1EN8v for <lwip@ietfa.amsl.com>; Wed, 13 Feb 2019 23:30:32 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A1CA130FFF for <lwip@ietf.org>; Wed, 13 Feb 2019 23:30:32 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 440SjK1PJjz3Nm; Thu, 14 Feb 2019 08:30:29 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1550129429; bh=HNELD0A1SHgHkY0OPPdfkLp+FhdXlLzq6eMejbxvMt4=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=mft0YgRaorwOPP7ICa9uqMEbD+EM+l3oDzHJXbaJeeKxiBUDremZ01EKuQIPPfOjq NBbMfKL5N1YNaA2u0CvFOrF1ZKhdXynVeg4n68CYE6E2xODxLbs5GNaJa9/sw5MKCt xwWkW4n/om79q2wqf/B0UkgFslc9URb+RqbqQT7A=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id XrRNXDdZekpd; Thu, 14 Feb 2019 08:30:27 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 14 Feb 2019 08:30:27 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 835192FCBF; Thu, 14 Feb 2019 02:30:26 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 835192FCBF
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 7782840D358A; Thu, 14 Feb 2019 02:30:26 -0500 (EST)
Date: Thu, 14 Feb 2019 02:30:26 -0500
From: Paul Wouters <paul@nohats.ca>
To: Valery Smyslov <smyslov.ietf@gmail.com>
cc: 'Daniel Migault' <daniel.migault@ericsson.com>, lwip@ietf.org, 'Mohit Sethi M' <mohit.m.sethi@ericsson.com>, 'Tero Kivinen' <kivinen@iki.fi>
In-Reply-To: <054301d4c433$eee63ef0$ccb2bcd0$@gmail.com>
Message-ID: <alpine.LRH.2.21.1902140223530.19964@bofh.nohats.ca>
References: <CAP_kZQqckPJhCn083sg8=PVpiO_+Ke=GhOKre=qujkk4k=dU7A@mail.gmail.com> <CADZyTk=dtJS7bS8oJtSa1bW-Xv3-AkuboX1QoJTFG+DyuN94ow@mail.gmail.com> <CAP_kZQrnmJJaLtzSJ5MeDYSme2mV6sAfGZrE5tnx8P6hbMib7g@mail.gmail.com> <23433.17795.580382.531001@fireball.acr.fi> <alpine.LRH.2.21.1808311231250.27198@bofh.nohats.ca> <VI1PR07MB4717173E61C887FDF4E4D3ABD0F70@VI1PR07MB4717.eurprd07.prod.outlook.com> <CADZyTk=hYhJH8yU5TU6m_dsEr_u+iEfd=c=oasV5=JEHM4dc1g@mail.gmail.com> <alpine.LRH.2.21.1902131236040.458@bofh.nohats.ca> <054301d4c433$eee63ef0$ccb2bcd0$@gmail.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/A6nYXyEHRtL7gIQpF-sMlg1Bo2M>
Subject: Re: [Lwip] [IPsec] The LWIG WG has placed draft-mglt-lwig-minimal-esp in state "Call For Adoption By WG Issued"
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Lightweight IP stack. Official mailing list for IETF LWIG Working Group." <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2019 07:30:35 -0000

On Thu, 14 Feb 2019, Valery Smyslov wrote:

> just a small clarification and a comment.
>
>> This sentence is confusing:
>>
>>  	ESP can be used to authenticate only or to encrypt the communication.
>>
>> Since IPsec-v2 allowed ESP without authentication, and IPsec-v3 only has
>> authenticated ESP. It's better to say ESP allows null-encryption and not
>> mention authentication (which always happens)
>
> In fact, RFC 4303 does allow using encryption w/o authentication for ESP,
> unless NULL encryption is used.

But RFC 8221 does not :)

https://tools.ietf.org/html/rfc8221#section-4

 	4. Encryption Must Be Authenticated

[...]

Although I guess we do not Updatae: 4303 so it sort of does not count.
Steve Kent wrote a lot of words in 4303 to basically say do not use
ESP without authentication (from ESP itself or another AH layer)

> I agree with this.

Ahh, we do agree on something at least :)

Paul