Re: [OPSEC] Start of WGLC for draft-ietf-opsec-vpn-leakages

I support publication of this draft.

I recently ran into this leaking issue on Android with OpenVPN.  An
open OpenVPN server used for security and anonymity only inserted
routes for IPv4 on the client, with the result being all IPv6 does not
go through the VPN.

Many naive users will assume all traffic goes via the VPN, but in fact
only a subset of IPv4-only traffic will go via the VPN while all ipv6
traffic travels outside the VPN

CB

On Wed, Jul 3, 2013 at 1:58 PM, Warren Kumari <warren@kumari.net> wrote:
> Dear OpSec WG,
>
> This starts a Working Group Last Call for draft-ietf-opsec-vpn-leakages.
>
> The draft is available here: https://datatracker.ietf.org/doc/draft-ietf-opsec-vpn-leakages/
>
> The authors of draft-ietf-opsec-vpn-leakages have indicated that they have incorporated feedback and believe that the document is ready for WGLC.
> It is the authors responsibility to drum up additional feedback and review.
>
> Please review this draft to see if you think it is ready for publication
> and comments to the list, clearly stating your view.
>
> This WGLC ends Wed 17-Jul-2013.
>
>
>
> Helpful Notes:
> draft-ietf-opsec-vpn-leakages was originally draft-gont-opsec-vpn-leakages.
>
> There was some discussion in the thread: IPv6 implications on IPv4 nets: IPv6 RAs, IPv4's VPN "leakage"
> and "New IETF I-D about VPN traffic leakages (Fwd: New Version Notification for draft-gont-opsec-vpn-leakages-00.txt)"
>
>
> Thanks,
> Warren Kumari
> (as OpSec WG co-chair)
>
>
> --
> Outside of a dog, a book is your best friend, and inside of a dog, it's too dark to read
>
>
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec