IETF Logo Mail Archive

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

"Smith, Donald" <Donald.Smith@CenturyLink.com> Thu, 15 August 2013 20:05 UTC

Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E835821F99BF for <opsec@ietfa.amsl.com>; Thu, 15 Aug 2013 13:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BHLX2SVnQAIi for <opsec@ietfa.amsl.com>; Thu, 15 Aug 2013 13:05:12 -0700 (PDT)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by ietfa.amsl.com (Postfix) with ESMTP id 5789421F9A6D for <OpSec@ietf.org>; Thu, 15 Aug 2013 13:05:12 -0700 (PDT)
Received: from lxomavmpc030.qintra.com (lxomavmpc030.qintra.com [151.117.207.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id r7FK5ANk018692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Aug 2013 15:05:11 -0500 (CDT)
Received: from lxomavmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 6C1851E003F; Thu, 15 Aug 2013 15:05:05 -0500 (CDT)
Received: from sudnp796.qintra.com (unknown [10.6.10.61]) by lxomavmpc030.qintra.com (Postfix) with ESMTP id 371A91E004F; Thu, 15 Aug 2013 15:05:05 -0500 (CDT)
Received: from sudnp796.qintra.com (localhost [127.0.0.1]) by sudnp796.qintra.com (8.14.4/8.14.4) with ESMTP id r7FK541p023282; Thu, 15 Aug 2013 14:05:04 -0600 (MDT)
Received: from vddcwhubex501.ctl.intranet (vddcwhubex501.qintra.com [151.119.128.28]) by sudnp796.qintra.com (8.14.4/8.14.4) with ESMTP id r7FK53nc023254 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 15 Aug 2013 14:05:03 -0600 (MDT)
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex501.ctl.intranet ([2002:9777:801c::9777:801c]) with mapi id 14.02.0318.001; Thu, 15 Aug 2013 14:05:02 -0600
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: 'Warren Kumari' <warren@kumari.net>, "'OpSec@ietf.org'" <OpSec@ietf.org>, "'draft-ietf-opsec-vpn-leakages@tools.ietf.org'" <draft-ietf-opsec-vpn-leakages@tools.ietf.org>
Thread-Topic: [OPSEC] Start of WGLC for draft-ietf-opsec-vpn-leakages
Thread-Index: AQHOmfJC4y+ujlVqxUGGwzUJhkGa05mWsRMA
Date: Thu, 15 Aug 2013 20:05:02 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D0A3D75F2@PDDCWMBXEX503.ctl.intranet>
References: <BD8A5CB6-A6CB-41E0-A907-49E11F40FEC5@kumari.net> <573A4AA8-625E-48E2-AC3C-9ADF4C23AC76@kumari.net>
In-Reply-To: <573A4AA8-625E-48E2-AC3C-9ADF4C23AC76@kumari.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [151.119.128.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [OPSEC] Start of WGLC for draft-ietf-opsec-vpn-leakages
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 20:05:18 -0000

Can we change the name?
The reason I ask is the v6 traffic never gets into the tunnel so it can't really leak out.

It is a potential data leak or exposure but not really a vpn leak;)


"Pampers use multiple layers of protection to prevent leakage. Rommel used defense in depth to defend European fortresses." (A.White) Donald.Smith@CenturyLink.com


>-----Original Message-----
>From: opsec-bounces@ietf.org [mailto:opsec-bounces@ietf.org] On Behalf
>Of Warren Kumari
>Sent: Thursday, August 15, 2013 2:01 PM
>To: OpSec@ietf.org; draft-ietf-opsec-vpn-leakages@tools.ietf.org
>Cc: Warren Kumari
>Subject: Re: [OPSEC] Start of WGLC for draft-ietf-opsec-vpn-leakages
>
>
>On Jul 3, 2013, at 4:58 PM, Warren Kumari <warren@kumari.net> wrote:
>
>> Dear OpSec WG,
>>
>> This starts a Working Group Last Call for draft-ietf-opsec-vpn-
>leakages.
>
>And the WGLC is now completed (and the chairs finally had a chase to
>chat after Berlin :-)).
>
>We see consensus for publication. Author, please incorporate the
>comments received, and then we can toss it over the wall...
>
>Thanks to all those who reviewed, and for shame to those who didn't.
>
>W
>
>>
>> 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
>>
>
>--
>Do not meddle in the affairs of wizards, for they are subtle and quick
>to anger.
>    -- J.R.R. Tolkien
>
>
>_______________________________________________
>OPSEC mailing list
>OPSEC@ietf.org
>https://www.ietf.org/mailman/listinfo/opsec

v2.23.0 | Report a Bug | By Email