Re: [Int-area] Feedback on draft-andersdotter-intarea-update-to-rfc6302-00

S Moonesamy <sm+ietf@elandsys.com> Mon, 12 November 2018 19:44 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2043130DE7 for <int-area@ietfa.amsl.com>; Mon, 12 Nov 2018 11:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=IUbAfxp6; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=Xf/9Dpcx
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 raFeNDqzO5_o for <int-area@ietfa.amsl.com>; Mon, 12 Nov 2018 11:44:31 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C57130DCE for <int-area@ietf.org>; Mon, 12 Nov 2018 11:44:31 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.106.228]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id wACJiFp2002785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2018 11:44:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1542051866; x=1542138266; bh=sxSQlBP74dlCwx78VtT83s2xIoHHEEXHzM31sJhtvOY=; h=Date:To:From:Subject:In-Reply-To:References; b=IUbAfxp646aCbjpKhoczEIlH2lXFAuJ9jhNR9nGxbwP68LXwEicBSQMZwwKrQmxpQ FAv6lK3P9ScVJFCO6DZXTWQtzZ5YWPec7AQkYeKUbEYQuxuztmLvnVc/sleWcml4mi 3RhcqcS0RQ6WvgEAlVIf14ltgbb1Ye7GUWATkuWg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1542051866; x=1542138266; i=@elandsys.com; bh=sxSQlBP74dlCwx78VtT83s2xIoHHEEXHzM31sJhtvOY=; h=Date:To:From:Subject:In-Reply-To:References; b=Xf/9DpcxLxY/m/iB5FFSXzAlR8Hh8//giF9S/I1zwxvkbZjrr8Y7gkKlBYjXYqppR K3HV81PrVFUcjqfZvxnOX/PaegJnccv38m/GvijhwQ+Wp91RUg9wQgjgxwN99e9X3T Fu2PKRgXZ1PycodJdglmFd8poi8/VkoknzJHtSnA=
Message-Id: <6.2.5.6.2.20181112112939.0ca0ae70@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 12 Nov 2018 11:43:58 -0800
To: Amelia Andersdotter <amelia@article19.org>, int-area@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <98428911-090a-8959-95cf-b1dc81dc074d@article19.org>
References: <6.2.5.6.2.20181111104756.0bd7f998@elandnews.com> <98428911-090a-8959-95cf-b1dc81dc074d@article19.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/4UBWdE_qUcO_Pt1mVrcrsQLOaKE>
Subject: Re: [Int-area] Feedback on draft-andersdotter-intarea-update-to-rfc6302-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2018 19:44:32 -0000

Hi Amelia,
At 10:32 AM 12-11-2018, Amelia Andersdotter wrote:
>E-mails in this thread:
>https://www.ietf.org/mail-archive/web/int-area/current/msg06335.htmlÂ
>
>and here:
>https://www.ietf.org/mail-archive/web/int-area/current/msg06434.html
>
>It was my sense that the feeling in the group was that, much like
>RFC6302 hasn't necessarily been taken up or solved the problems it
>purported to, neither would updating it in a privacy-conducive direction.

Thank you for summarizing the group discussion.

>I think they've misunderstood the GDPR. It's a highly risk assessment
>based text, which only makes requirements where "possible" or
>"appropriate". This was also one of the feedbacks that inspired my
>draft, or rather grievances expressed with the GDPR (it is a framework
>which is difficult to understand because of its vagueness).

Ok.

>Practically, the use cases for logged data discussed in the WG were
>unrelated to breaches and related to advertising and LEA.

The reasons given are usually anti-abuse and regulatory requirements.

Regards,
S. Moonesamy