Re: [IPsec] I-D Action: draft-ietf-ipsecme-qr-ikev2-09.txt
"Valery Smyslov" <smyslov.ietf@gmail.com> Wed, 27 November 2019 08:50 UTC
Return-Path: <smyslov.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 3CC8112080A; Wed, 27 Nov 2019 00:50:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 58GEFWyhvs1k; Wed, 27 Nov 2019 00:50:20 -0800 (PST)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9E7212003F; Wed, 27 Nov 2019 00:50:19 -0800 (PST)
Received: by mail-wr1-x429.google.com with SMTP id a15so25652221wrf.9; Wed, 27 Nov 2019 00:50:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=sqPdvKR5fHzEVoem0XDxvpdo26d2z3JXUvHsPHuNnY0=; b=cu+/aJoPOoVk1jJczcjQiuB+6XhsFqHC+2u37UJ+uIG7UDdzozrDBiAS9ExeAnjkrF 4/Cw+6J98RrkUtgNdrNM2af8u2DSlzrueRWqwTItie9rMPTcKc3sOE+dhL8Psd2sNvFs +w5nSdxtEYem4GmSQncKgeitPBx0Nsb5jELUV/JPet5B/7PdAoH5jW7CG6rIy8Km/Zd0 gmw2jY9VwXmHsFkDDHQgMshW7kdFHWj956BnCrCrhU4TnsWSLUQvLFIayKVzmrbxUypy LmK3b1UvoFEB0kmeWQx5ITbDKZRrMpvuJufGo4q9TwmYsqrS43DiCXb8sBwL/6G6c7Eb dBpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=sqPdvKR5fHzEVoem0XDxvpdo26d2z3JXUvHsPHuNnY0=; b=eEsnyIjBr6J/PIcAXayuaMvsSoAOZM/ljY6daUlTpQQl8TMNZJFj6jJzjQ5EGkVKuL /fB56ZF+m5T0EoKXESEjJ973rhgV/5NUiRVi1iyZcnQVNmgniGzbPcBfK+vywShlBh/W QC/1tCFsXjRnWkCOBulF1mk2L09v0mVdfx+FWGivost+p7gQOzB5EpnHpi7tH218TZlF SjG701kgeyz6MUtOndZscdowkdKxNS0wFg+D7uT2Ik3S31yPuJh8cSF2YLHbM+mRPBrM D65r7U8pzGb2z1s2VGNNRGl8KoYi+D4gfWTB9eGpNW/bkUPGO46mDlu6fU+nJTgiyB7P ilWg==
X-Gm-Message-State: APjAAAWtJJJElZbLUfjcNNvcnY2NxZTqlhpvb95p+7IzglsQfLXzfXVi 4kA1OYjW1mdP8hZv/l4c6fY7RVH/
X-Google-Smtp-Source: APXvYqwpChkEsqAlbodIuo7x+F2e8r+BJujladUxWU+073lQ+SYbLogdypLYAjbE8ZBia/u51UYwGA==
X-Received: by 2002:a5d:4445:: with SMTP id x5mr43122952wrr.341.1574844617997; Wed, 27 Nov 2019 00:50:17 -0800 (PST)
Received: from buildpc ([82.138.51.4]) by smtp.gmail.com with ESMTPSA id u187sm6271873wme.15.2019.11.27.00.50.16 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 27 Nov 2019 00:50:17 -0800 (PST)
From: Valery Smyslov <smyslov.ietf@gmail.com>
To: ipsec@ietf.org
Cc: kaduk@mit.edu, draft-ietf-ipsecme-qr-ikev2.all@ietf.org
References: <157484402528.21913.4728906227364823734@ietfa.amsl.com>
In-Reply-To: <157484402528.21913.4728906227364823734@ietfa.amsl.com>
Date: Wed, 27 Nov 2019 11:50:16 +0300
Message-ID: <025501d5a4ff$b16d6550$14482ff0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFnWHSxdi+9LPdGeXwiA6UAHb0Gd6h7S/xg
Content-Language: ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/jtimKkNNodh9pzasjwrGwLWW4h0>
Subject: Re: [IPsec] I-D Action: draft-ietf-ipsecme-qr-ikev2-09.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 08:50:21 -0000
Hi, I've posted a new version of "Postquantum Preshared Keys for IKEv2" draft. This version addresses issues raised by AD review of the draft: https://mailarchive.ietf.org/arch/msg/ipsec/G1yO6oGFtfr-1EMjkT5cprDyMuU We believe that all the issues are resolved. One note regarding the following issue (as its resolution wasn't discussed on the list): > Section 5.2.1 > > I'm kind of confused by the PSKC reference, especially the implication > ("algorithm ("Algorithm=urn:ietf:params:xml:ns:keyprov:pskc:pin") as the > PIN") that a fixed string is to be used as a PIN. (I also think it's > better to discuss what it does as "key transport" than "key exchange", > noting that the latter string does not appear in RFC 6030.) I slightly changed the text, so that the text suggests to re-use "PIN" profile defined in Section 10.2 of RFC6030 with no implication of any fixed PIN. I believe it was the original intent. Regards, Valery. > -----Original Message----- > From: IPsec [mailto:ipsec-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org > Sent: Wednesday, November 27, 2019 11:40 AM > To: i-d-announce@ietf.org > Cc: ipsec@ietf.org > Subject: [IPsec] I-D Action: draft-ietf-ipsecme-qr-ikev2-09.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the IP Security Maintenance and Extensions WG of the IETF. > > Title : Postquantum Preshared Keys for IKEv2 > Authors : Scott Fluhrer > David McGrew > Panos Kampanakis > Valery Smyslov > Filename : draft-ietf-ipsecme-qr-ikev2-09.txt > Pages : 19 > Date : 2019-11-27 > > Abstract: > The possibility of Quantum Computers poses a serious challenge to > cryptographic algorithms deployed widely today. IKEv2 is one example > of a cryptosystem that could be broken; someone storing VPN > communications today could decrypt them at a later time when a > Quantum Computer is available. It is anticipated that IKEv2 will be > extended to support quantum-secure key exchange algorithms; however > that is not likely to happen in the near term. To address this > problem before then, this document describes an extension of IKEv2 to > allow it to be resistant to a Quantum Computer, by using preshared > keys. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-ipsecme-qr-ikev2/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-ipsecme-qr-ikev2-09 > https://datatracker.ietf.org/doc/html/draft-ietf-ipsecme-qr-ikev2-09 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-ipsecme-qr-ikev2-09 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > IPsec mailing list > IPsec@ietf.org > https://www.ietf.org/mailman/listinfo/ipsec
- [IPsec] I-D Action: draft-ietf-ipsecme-qr-ikev2-0… internet-drafts
- Re: [IPsec] I-D Action: draft-ietf-ipsecme-qr-ike… Valery Smyslov