[ipv6-wg] RIPE-501 replacement document - IPsec question tocommunity - 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 tocommunity - we need your input.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Eric Vyncke (evyncke)
evyncke at cisco.com
Tue Dec 27 16:43:43 CET 2011
I think that we should keep IPsec/IKEv2 only for firewall and mention to any place where OSPFv3 is mentioned that the support of AH is required. > -----Original Message----- > From: ipv6-wg-bounces at ripe.net [mailto:ipv6-wg-bounces at ripe.net] On Behalf > Of Florian Weimer > Sent: mardi 27 décembre 2011 13:41 > To: Jan Zorz @ go6.si > Cc: ipv6-wg at ripe.net > Subject: Re: [ipv6-wg] RIPE-501 replacement document - IPsec question > tocommunity - we need your input. > > * Jan Zorz: > > > On 12/27/11 10:15 AM, Florian Weimer wrote: > >> Most devices use TLS. > >> > >> I agree with dropping IPsec from the document completely, indepedent of > >> device type. > > > So you suggest not mentioning IPsec in any form at all in whole > > document? Am I reading this correctly? > > Yes. Even if we could achieve agreement on a subset of devices where > it's supposed to make sense, "IPsec" is really a catchphrase for a set > of related protocols, so anyone who actually needs some of it needs to > ask for it explicitly anyway. > > -- > 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 tocommunity - we need your input.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]