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/ipv6-wg@ripe.net/
[ipv6-wg] RIPE-501 and IPSEC on CPEs
- Previous message (by thread): [ipv6-wg] RIPE-501 and IPSEC on CPEs
- Next message (by thread): [ipv6-wg] RIPE-501 and IPSEC on CPEs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ivan Pepelnjak
ip at ioshints.info
Wed Jul 20 18:40:30 CEST 2011
Don't forget that although IPsec is part of IPv6 functionality, supporting null encapsulation (whatever it's properly called ;) and no authentication or encryption protocol also makes you compliant. We might make it optional ;) Ivan > -----Original Message----- > From: ipv6-wg-admin at ripe.net [mailto:ipv6-wg-admin at ripe.net] On Behalf Of > Jan Zorz @ go6.si > Sent: Wednesday, July 20, 2011 6:36 PM > To: ipv6-wg at ripe.net > Subject: Re: [ipv6-wg] RIPE-501 and IPSEC on CPEs > > On 7/20/11 2:42 PM, Ahmed Abu-Abed wrote: > > Hello All, > > Reading RIPE-501 spec for basic CPEs, I see that IPSEC & IKE are > > mandatory under "host" equipment. Is this a necessity ? Many IPv4 CPEs > > do not support IPSEC to keep the costs down. > > Regards, > > -Ahmed > > Yes, host must support this. CPE not necessarily, that's why it's under > optional requirements. > > Cheers, Jan
- Previous message (by thread): [ipv6-wg] RIPE-501 and IPSEC on CPEs
- Next message (by thread): [ipv6-wg] RIPE-501 and IPSEC on CPEs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]