[Pearg] Fwd: New Version Notification for draft-rao-pitfol-00.txt

Shivan Kaul Sahib <shivankaulsahib@gmail.com> Mon, 04 November 2019 22:57 UTC

Return-Path: <shivankaul.1993@gmail.com>
X-Original-To: pearg@ietfa.amsl.com
Delivered-To: pearg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3DF12097E for <pearg@ietfa.amsl.com>; Mon, 4 Nov 2019 14:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PN_QHT8MG1os for <pearg@ietfa.amsl.com>; Mon, 4 Nov 2019 14:57:06 -0800 (PST)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 887F0120964 for <pearg@irtf.org>; Mon, 4 Nov 2019 14:57:06 -0800 (PST)
Received: by mail-ed1-x535.google.com with SMTP id f11so3985680edt.10 for <pearg@irtf.org>; Mon, 04 Nov 2019 14:57:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kcL0rJ2t1MzV608godzoyLOKsS2tw0xvPuGDYVmlAIA=; b=IsgTp4vtoimGKxtt+QAVRq2VyQe6Qzsit88CXpJab00T3wlPL0Y07MaZUKu4Kierpl cR8lY3MSrK5wAtQH0RNjhE69TbjyjnxL1sDYi6N+jPHg3n4K2CTYiK0oOFX4SgEzQMxI dtzBuFhHGukxAhnOKTMzfk1GkeUdxrlzdd1DA+i9HO6v3Ejd632+3So5PX++PdgX8odI 6H47HYKlpGsCdvMtuxErj6GaC3t2OecmuTw9S2NdTlWdrwL0bbeu/anFRg0Nlrnh40Zx jo+Atj6ujAShwYVEDIHecpvvyfmkSdx/eFDI3YAElTPZxPIEpvpZ7ywu3YOwgcG0DEeP CfnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kcL0rJ2t1MzV608godzoyLOKsS2tw0xvPuGDYVmlAIA=; b=JKA3tPxm+n7JRO3+JcYRyvTEEP9uSM4ecI1mAoZk3WIfasc3udL5m+Frc8b7zBTcNH t23+J9L3dP3YNcDtK9xNNzFhsY9iudO3u/R6yLyV8Vrv768UB3qNRwl0uVvkUsWbE+KT dK60JVuAcvWkRUUf8kCO9eBq3tkVjgum56BwZgB+SqlsGbHI8QZdkjIhCyNA7hcGngqL 8TFUXUIbgOJbjU+d9B/GuhLcGFVuFsES7gfCqtwwSMWg6B8QM1e6bH2lowTo/18OmAO3 J1i6oPN5bbbyrzq0Oo9+FzLn2NU6+I29RZb9CoLAOtwL+xmoD/mes0P/mWS3bapFRj9U fdkw==
X-Gm-Message-State: APjAAAU9kiliuEASkgT9q15j1QFaTdKJ/znJTXajxEXVh55HrIekJavw SNB39RsYrEQ30PsAW3AxRiihkeegq4XlCrdJuegdWpJ0
X-Google-Smtp-Source: APXvYqwG5AxGayu1pF2cCPDufKBL9jN4Jr4cZJBUNDnLKptZWLRQp1TO2SfOnHFZ+EnhLkxC1R/BIPC4GK6zRfpc5l4=
X-Received: by 2002:a50:b634:: with SMTP id b49mr32361177ede.77.1572908224829; Mon, 04 Nov 2019 14:57:04 -0800 (PST)
MIME-Version: 1.0
References: <157290745098.13968.2286291145434878300.idtracker@ietfa.amsl.com>
In-Reply-To: <157290745098.13968.2286291145434878300.idtracker@ietfa.amsl.com>
From: Shivan Kaul Sahib <shivankaulsahib@gmail.com>
Date: Mon, 4 Nov 2019 14:56:28 -0800
Message-ID: <CAG3f7MjwTehNUq5+V2mTHv+PpzkCm6qMKPf2hWzdGj39SFDXEQ@mail.gmail.com>
To: pearg@irtf.org
Cc: rguest@salesforce.com, sandeeprao.ietf@gmail.com
Content-Type: multipart/alternative; boundary="000000000000015ef005968d3ccc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/QvKDwH0KTfubZGn-_YXGBFlIUNA>
Subject: [Pearg] Fwd: New Version Notification for draft-rao-pitfol-00.txt
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <pearg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/pearg>, <mailto:pearg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pearg/>
List-Post: <mailto:pearg@irtf.org>
List-Help: <mailto:pearg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pearg>, <mailto:pearg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 22:57:16 -0000

Hi all,

Sandeep Rao from Grab, Ryan Guest from Salesforce and I have been
discussing log data classification shortly after Ryan's presentation on log
data privacy at the IETF 104 PEARG meeting. This draft is a first attempt
at exploring ways in which applications can tag log fields as containing
personal information for further anonymization/processing.

Sandeep will be presenting this draft at the upcoming IETF Singapore PEARG
meeting.

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Nov 4, 2019 at 2:44 PM
Subject: New Version Notification for draft-rao-pitfol-00.txt
To: Ryan Guest <rguest@salesforce.com>om>, Sandeep Rao <
sandeeprao.ietf@gmail.com>gt;, Shivan Sahib <shivankaulsahib@gmail.com>



A new version of I-D, draft-rao-pitfol-00.txt
has been successfully submitted by Shivan Sahib and posted to the
IETF repository.

Name:           draft-rao-pitfol
Revision:       00
Title:          Personal Information Tagging for Logs (PITFoL)
Document date:  2019-11-04
Group:          Individual Submission
Pages:          6
URL:            https://www.ietf.org/internet-drafts/draft-rao-pitfol-00.txt
Status:         https://datatracker.ietf.org/doc/draft-rao-pitfol/
Htmlized:       https://tools.ietf.org/html/draft-rao-pitfol-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-rao-pitfol


Abstract:
   Software applications typically generate a large amount of log data
   in the course of their operation in order to help with monitoring,
   troubleshooting, etc.  However, like all data generated and operated
   upon by software systems, logs can contain information sensitive to
   users.  Personal data identification and anonymization in logs is
   thus crucial to ensure that no personal data is being inadvertently
   logged and retained which would make the logging application run
   afoul of laws around storing private information.  This document
   focuses on exploring mechanisms to specify personal or sensitive data
   in logs, to enable any server collecting, processing or analyzing
   logs to identify personal data and thereafter, potentially enforce
   any redaction.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat