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] Rquirements for VPN
- Previous message (by thread): [ipv6-wg] RIPE554-bis
- Next message (by thread): [ipv6-wg] Rquirements for VPN
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
christian bretterhofer
christian.bretterhofer at gmail.com
Wed Oct 28 22:09:24 CET 2020
After reading https://go6.si/wp-content/uploads/2020/10/RIPE554-bis-v_01.pdf I see VPNs as part of the Network Security Equipment. But in my opinium there is not enough definition to be a VPN quality criteria. VPN external Protocol Must support IPv6 clients to IPv6 servers (6-to-6) ( Ipv6 Only) VPN external Protocol Must support IPv4 clients to IPv4 servers (4-to-4) (Ipv4 only) Transport inside of VPN VPN inner Protocol Must support IPv6 clients to IPv6 servers (6-to-6) VPN inner Protocol Must support IPv4 clients to IPv4 servers (4-to-4) VPN inner Protocol should support Dual stack. VPN inner Protocol should support 4in6 6in4 (transition protocols) The Idea from wireguard is maybe also a should the external protocol switch from Ipv6 to Ipv4 or Ipv4 to Ipv6 then the inner protocol should stay connected. Protocols with DNS64/NAT64 support would also help. maybe it fist into this recommendation document. -- --- best regards Christian Bretterhofer Enterprise User: -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20201028/35f2c56e/attachment.html>
- Previous message (by thread): [ipv6-wg] RIPE554-bis
- Next message (by thread): [ipv6-wg] Rquirements for VPN
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]