@techreport{dschinazi-ipsecme-sa-init-privacy-addition-00,
    number =    {draft-dschinazi-ipsecme-sa-init-privacy-addition-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-dschinazi-ipsecme-sa-init-privacy-addition/00/},
    author =    {David Schinazi},
    title =     {{Privacy Addition to the Internet Key Exchange Protocol Version 2 (IKEv2) IKE\_SA\_INIT Exchange}},
    pagetotal = 9,
    year =      2018,
    month =     mar,
    day =       5,
    abstract =  {The Internet Key Exchange Protocol version 2 (IKEv2) provides strong security and privacy properties to both endpoints once they have authenticated each other. However, before an endpoint has validated the peer's AUTH payload, it could be divulging information to an untrusted host. An example of such information is the Identification payload of the initiator. Another example is the fact that a host is running an IKEv2 responder. This document introduces a new "Initialization Authentication Code" notify payload that can be included in IKE\_SA\_INIT messages to increase their trustworthiness. This new protection is meant to be used in addition to current IKEv2 mechanisms and is not meant to replace the AUTH payload in any way.},
}