> On Jun 24, 2016, at 7:06 PM, David McGrew <[email protected]> wrote: > > Hi Paul, > >> On Jun 23, 2016, at 6:55 PM, Panos Kampanakis (pkampana) >> <[email protected]> wrote: >> >> Introducing quantum computer resistance in IKEv2 helps to avoid the >> implications of having sec admins that want to have quantum computer >> resistance revert back to IKEv1 with shared secrets. The draft adds quantum >> resistance using todays infrastructure. The qkd draft introduced a way to >> add quantum resistance, but it came with many different challenges of how >> practical it is and how costly it would be to introduce a QKD network.
Note that the QKD draft talks in terms of QKD, but the mechanisms developed are in fact generic to out-of-band generated key material that must be named and agreed on. The last status of the nagayama draft was that there was resistance to the concept of QKD from some quarters, and less resistance from others but no sense of urgency. We were encouraged by the ADs and a few others to rework the draft to focus more on generic uses of out-of-band generated key material, but we haven’t managed to put together the right set of hours to get it done. At least one person said, “It may be snake oil, but you’re entitled to interoperable snake oil,” with reference to the fact that we want a published document that has had input and review and improvements, but certainly recognize that the use case remains a specialized corner for the moment. But given the work being done to standardize other parts of QKD inside ETSI, it seems important to have matching IPsec hooks that will be common, and it’s especially important to me that IETF retain control to any changes to IPsec, rather than having another standards organization documenting changes to protocols developed here, which certainly seems a recipe for nightmarish politics and non-interoperable implementations. draft-nagayama-ipsecme-ipsec-with-qkd went through both -00 and -01 drafts a significant time period apart. The protocol in -00 represents our actual implement with actual QKD devices, from some time ago. Shota was working at one point to modify the code to match -01; he would have to remind me how close to complete that code is. The source for the -00-compliant version is downloadable at http://aqua.sfc.wide.ad.jp/research/ipsecwithqkd.html <http://aqua.sfc.wide.ad.jp/research/ipsecwithqkd.html> —Rod
_______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
