Re: [93attendees] Network experiment during the meeting

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Wed, 15 July 2015 17:54 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: 93attendees@ietfa.amsl.com
Delivered-To: 93attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFFE61B32FD for <93attendees@ietfa.amsl.com>; Wed, 15 Jul 2015 10:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGj1KOXAxXhF for <93attendees@ietfa.amsl.com>; Wed, 15 Jul 2015 10:54:09 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08FD81B32F8 for <93attendees@ietf.org>; Wed, 15 Jul 2015 10:54:09 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id D701BA4EA9746; Wed, 15 Jul 2015 17:54:04 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id t6FHs5eb030249 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Jul 2015 19:54:05 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Wed, 15 Jul 2015 19:54:05 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Toerless Eckert <eckert@cisco.com>, Stephen Botzko <stephen.botzko@gmail.com>
Thread-Topic: [93attendees] Network experiment during the meeting
Thread-Index: AQHQvwO0VBAnRjTXWUWw6jy/Un59CZ3cbPsAgAANAgCAABGsgIAAEzKAgAABloCAACg3kA==
Date: Wed, 15 Jul 2015 17:54:03 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B69741EE2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CAO_Rpc+-fQBU+MuOR03VHDgw3HcbOWPcThUR3nR2Vnj9CcM63w@mail.gmail.com> <C2443FFD-988C-4B31-ADB3-3AEAD994387A@isoc.org> <CAO_RpcKCYBxOW9eYLUCD2qiPuAQE3-tj8hwe_AXVJYUr+Y4h=g@mail.gmail.com> <D1CBF04C.50692%evyncke@cisco.com> <20150715121528.GA7114@puck.nether.net> <55A6629E.8050700@dcrocker.net> <20150715135804.GP1862@cisco.com> <55A671D6.9020707@dcrocker.net> <20150715154753.GS1862@cisco.com> <CAMC7SJ6RGjdnV91PNtA-o6B_VXG0hfhpx54nvvqet002rHtzKQ@mail.gmail.com> <20150715170215.GU1862@cisco.com>
In-Reply-To: <20150715170215.GU1862@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/_ej82NwinxlFJDWE3DdhSLamL6Y>
Cc: "93attendees@ietf.org" <93attendees@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Jared Mauch <jared@puck.nether.net>
Subject: Re: [93attendees] Network experiment during the meeting
X-BeenThere: 93attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 93 attendees that have opted in on this list. " <93attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/93attendees>, <mailto:93attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/93attendees/>
List-Post: <mailto:93attendees@ietf.org>
List-Help: <mailto:93attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/93attendees>, <mailto:93attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2015 17:54:11 -0000

And even if the IETF note well did cover such a thing, in general it could not indemnify an individual or person in breaking the law, but only become complicit is said illegal act. 

If we are talking about the handling of personal data, then the Czech authorities have put all the information together in English here:

https://www.uoou.cz/en/vismo/zobraz_dok.asp?id_org=200156&id_ktg=1107

>From the brief perusal I have done, it appears to mirror similar laws in other EU countries, both in requirements and management, as one might well expect.

Regards

Keith

> -----Original Message-----
> From: 93attendees [mailto:93attendees-bounces@ietf.org] On 
> Behalf Of Toerless Eckert
> Sent: 15 July 2015 18:02
> To: Stephen Botzko
> Cc: Jared Mauch; dcrocker@bbiw.net; 93attendees@ietf.org
> Subject: Re: [93attendees] Network experiment during the meeting
> 
> On Wed, Jul 15, 2015 at 12:56:35PM -0400, Stephen Botzko wrote:
> > >>>
> > I think the note well is trying to do its best to idemnify the IETF 
> > and its participants against lawsuits claiming infringing on trade 
> > secret or claims of novelty for things mentioned in public 
> at the IETF.
> > >>>
> > There is *nothing* in the Note Well (nor in the RFCs it references) 
> > about indemnification.
> 
> Sure, but the note well does not explain why the IETF does 
> it, and why it has attendees accept it. 
> 
> s/idemnify/protect/ ?
> 
> Cheers
>    Toerless
> 
> _______________________________________________
> 93attendees mailing list
> 93attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/93attendees
>