+1 to adding privacy text to the charter. This seems like it will be increasingly relevant if we’re doing host-to-host communication and we want to protect the privacy of various peers.
—Tommy > On Feb 16, 2018, at 12:09 PM, Paul Wouters <[email protected]> wrote: > > On Fri, 16 Feb 2018, Tero Kivinen wrote: > >> IKEv2 is currently vulnerable to the two following privacy concerns: >> >> 1) It's not possible to run a server that obfuscates IKEv2/IPsec using >> TLS. > >> 2) The privacy of the initiator's identity in the presence of a man in >> the middle attacker is not protected. > >> Is this something that we should add to charter? Do people understand >> the issue? > > I would be in favour of adding this issue to the charter in some to be > written text. > > Paul > > _______________________________________________ > IPsec mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ipsec _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
