Re: [IPsec] Proposed method to achieve quantum resistant IKEv2

"Graham Bartlett (grbartle)" <grbartle@cisco.com> Wed, 27 September 2017 20:04 UTC

Return-Path: <grbartle@cisco.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 7E0DD1342F7 for <ipsec@ietfa.amsl.com>; Wed, 27 Sep 2017 13:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 lj692oZZC1Hd for <ipsec@ietfa.amsl.com>; Wed, 27 Sep 2017 13:04:46 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C932713501E for <ipsec@ietf.org>; Wed, 27 Sep 2017 13:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7270; q=dns/txt; s=iport; t=1506542682; x=1507752282; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=322TCE0XipyD/l6wuG7nfeEXjqjaVOftcQp0vxNTtqg=; b=ayu0jLtvAo8snH8Rhl5eEfg8efS/Trcp19rdaN7US6znoFnxhcguGR/o fFeMJQBYHsA1bYYZBiCUF/A9Mpmkm26MpNTvBvltKHq2Z2BOUtFczYYeV 6xCxpk0yfyqv5sIajZvKUgM0QUiq1eeCFH6N6qVU6mqHMSlGRAspn5Q1n k=;
X-Files: smime.p7s : 4557
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CeAADpAsxZ/4ENJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1yBUicHg3GKH49emCGCEgcDhTsCI4Q5PxgBAgEBAQEBAQFrKIUZBiNmAgEIQgICAjAlAgQBEg6KI6d9gieLAgEBAQEBAQEBAQEBAQEBAQEBAQEBAQ4PgyuCAoFRgWksgn2FG4J8L4IxBaEjAoQ6giGOApMGlRwCERkBgTgBHziBDngVSRIBhwp2h0aBEAEBAQ
X-IronPort-AV: E=Sophos;i="5.42,446,1500940800"; d="p7s'?scan'208";a="298939667"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Sep 2017 20:04:41 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v8RK4fJQ030523 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 27 Sep 2017 20:04:41 GMT
Received: from xch-aln-007.cisco.com (173.36.7.17) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 27 Sep 2017 15:04:41 -0500
Received: from xch-aln-007.cisco.com ([173.36.7.17]) by XCH-ALN-007.cisco.com ([173.36.7.17]) with mapi id 15.00.1320.000; Wed, 27 Sep 2017 15:04:41 -0500
From: "Graham Bartlett (grbartle)" <grbartle@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "ipsec@ietf.org" <ipsec@ietf.org>
Thread-Topic: [IPsec] Proposed method to achieve quantum resistant IKEv2
Thread-Index: AQHTDE+mPH5PNqQgTkK9LOvm4SvL2qJ0fkoAgAIguwCABYr/gIAAg/cAgE012QA=
Date: Wed, 27 Sep 2017 20:04:41 +0000
Message-ID: <04B7D970-30B0-4AE8-BAF9-210746B56FFF@cisco.com>
References: <BBEB2C9C-9B96-4C6C-BB9B-4415F096FAE1@cisco.com> <041b01d30d21$8d33f230$a79bd690$@gmail.com> <1501968567726.89885@post-quantum.com> <22922.57101.227283.113155@fireball.acr.fi> <7769.1502301632@obiwan.sandelman.ca>
In-Reply-To: <7769.1502301632@obiwan.sandelman.ca>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1a.0.160910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.142.69]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha256"; boundary="B_3589391116_935333229"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/RP-El8IdIjOlBBy1HJWzJ5CN9Qs>
Subject: Re: [IPsec] Proposed method to achieve quantum resistant IKEv2
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 27 Sep 2017 20:04:52 -0000

Hi Michael

Is the main rational for not having fragmentation in IKE_SA_INIT that it could break the features of IKE that you list below?

The reason I ask, we’re working on the current draft and looking to implement optional fragmentation in the IKE_SA_INIT, but this would be friendly to cookies, TCP encaps, NAT-T etc

cheers

On 09/08/2017, 19:00, "IPsec on behalf of Michael Richardson" <ipsec-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:

    I agree.  All of the DoS (cookie, etc.) defense and switch to TCP, and
    detection of NAT-T, etc. is in the IKE_SA_INIT, and so doing any kind of
    framentation in IKE_SA_INIT is a bad idea.