This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.
- Previous message (by thread): [ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.
- Next message (by thread): [ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Tue Dec 27 10:15:29 CET 2011
* Merike Kaeo: > On Dec 23, 2011, at 1:06 AM, Florian Weimer wrote: > >> * Jan Zorz: >> >>> The authors of RIPE-501 are finalizing the last comments from previous >>> last call and would like community input for what to do with IPsec. >>> All authors feel that IPsec should be a mandatory requirement for all >>> devices although due to technical limitations, for mobile devices it >>> will be optional. >> >> Shouldn't it be the other way round? Mobile devices are more likely to >> need VPN services than other kinds of devices. > > Mobile devices typically use TLS. Most devices use TLS. I agree with dropping IPsec from the document completely, indepedent of device type. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.
- Next message (by thread): [ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]