[Pearg] New Version Notification for draft-rao-pitfol-01.txt

Sandeep Rao <sandeeprao.ietf@gmail.com> Thu, 19 March 2020 13:57 UTC

Return-Path: <sandeeprao.ietf@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 A2F123A29DA for <pearg@ietfa.amsl.com>; Thu, 19 Mar 2020 06:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 5A3L9cL-3qqu for <pearg@ietfa.amsl.com>; Thu, 19 Mar 2020 06:57:30 -0700 (PDT)
Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (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 9BF7C3A29DB for <pearg@irtf.org>; Thu, 19 Mar 2020 06:57:30 -0700 (PDT)
Received: by mail-io1-xd43.google.com with SMTP id o127so2365787iof.0 for <pearg@irtf.org>; Thu, 19 Mar 2020 06:57:30 -0700 (PDT)
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=QuF7b3EPapikoUw+gCSuIMPH9kv5UGs6d7mOJhEArC4=; b=nY5OrYTvQATSnu3asXuo+pAL2xPYbiLrNGUaefxDr93F+Xe6Sake2EIAJoGO0s4dkO p5KzCrMnhAXv+ukENvaI6lrX4xbbQYkmoS5eu06ak1TtWDcJX4Ybo4MOBMBvkk/ila5F 2iBzJqu1NwBwMpNs1i6yD6/YkJnLjz0G/GLzadWXuFYR/PO24iSKy8IMp1OAuYp9vT0j yLMjfAhxojMPrrhS1fl7O84rQQGkRuDxjKgPtOPaCeb0PLFwq4C5rDs2gYrQGYrvTJF1 WS8pZDdI1Hnebky7Scsge3nqf6y3zIFLya2mmui4cKhArHWRbfJ6bCcOMiOAYStlhaGV wKcQ==
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=QuF7b3EPapikoUw+gCSuIMPH9kv5UGs6d7mOJhEArC4=; b=St++gbjZzI+GxqzjagyDBD1JfbxBsUQycaKIKNdrlhBliFHxHVk+UUlit4bqjS/pwa HUC7ft25GX5rBmkR3UKXOEsOAGcqJnIfC48533xVrFqMh0cCSVnLFN55utPhZO1Lf+mJ hiRhDX1JRwOIDB1veP4Dpf/XM4TgB+nvqSqBFKIG7rA9dDz4CaNznw+ejhVNPMtJbR3s kEE89qgpXUJPxBvs5+4i1EzTYAy6ToFnVUzoHcpPsdFeBNKvtIIFnkzQaBluR+q+21+5 ZwJWYwMw2GZFgWS8U1wK8+Xz3JQWAwWc+76Geoga1PZHG2A8CGScL8Zw7YtmnTyieGlj HA4Q==
X-Gm-Message-State: ANhLgQ2dbTjaI9dXRDuXANdYm37STDXboxNzuN3B36b8cXDZJethK3oJ V7iHZKSd8lxxLWPL5see7m1P6aW0OArh+SuRdOTn5A==
X-Google-Smtp-Source: =?utf-8?q?ADFU+vvneBmmhtue7fhy7aHJ15b6IrwdDBObMEB/x/5v?= =?utf-8?q?OaDIWbj7Rb1epjP5dBjfsqzdnYT8s4Mya5RYaKq3H62evqw=3D?=
X-Received: by 2002:a6b:c813:: with SMTP id y19mr2768300iof.125.1584626249421; Thu, 19 Mar 2020 06:57:29 -0700 (PDT)
MIME-Version: 1.0
References: <158379105516.5655.7823300520616107415@ietfa.amsl.com>
In-Reply-To: <158379105516.5655.7823300520616107415@ietfa.amsl.com>
From: Sandeep Rao <sandeeprao.ietf@gmail.com>
Date: Thu, 19 Mar 2020 19:27:18 +0530
Message-ID: <CAAeK7Ps-SUR5LeJNKLiXc1dfeRbvQ1bxNevFVhELxUjBe9qHoA@mail.gmail.com>
To: pearg@irtf.org
Cc: shivankaulsahib@gmail.com, rguest@salesforce.com, santoshcn1@gmail.com
Content-Type: multipart/alternative; boundary="000000000000b2fa4605a1358cc6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/fD9q1s2k8woO1ektLnF0eXjjIl8>
Subject: [Pearg] New Version Notification for draft-rao-pitfol-01.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: Thu, 19 Mar 2020 13:57:33 -0000

Hi All,


Here’s updated (version -01) of  Personal Information Tagging for Logs

https://www.ietf.org/internet-drafts/draft-rao-pitfol-01.txt


Thanks everyone for your inputs on the earlier version during IETF 106.


Key updates in this version are:

   1. Model for structured logging and use of standardized identifiers for
   personal information.
   2. Illustration of Personal Information Identifiers Registry and
   associating sensitivity level for each identifier.
   3. Role based Redaction and access control

Appreciate your review comments and feedback.


Thanks

-Sandeep

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Tue, Mar 10, 2020 at 3:27 AM
Subject: New Version Notification for draft-rao-pitfol-01.txt
To: Sandeep Rao <sandeeprao.ietf@gmail.com>om>, Santhosh C N <
santoshcn1@gmail.com>gt;, Ryan Guest <rguest@salesforce.com>om>, Shivan Sahib <
shivankaulsahib@gmail.com>



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

Name:           draft-rao-pitfol
Revision:       01
Title:          Personal Information Tagging for Logs
Document date:  2020-03-09
Group:          Individual Submission
Pages:          10
URL:            https://www.ietf.org/internet-drafts/draft-rao-pitfol-01.txt
Status:         https://datatracker.ietf.org/doc/draft-rao-pitfol/
Htmlized:       https://tools.ietf.org/html/draft-rao-pitfol-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-rao-pitfol
Diff:           https://www.ietf.org/rfcdiff?url2=draft-rao-pitfol-01

Abstract:
   Software systems typically generate log messages in the course of
   their operation.  These log messages (or 'logs') record events as
   they happen, thus providing a trail that can be used to understand
   the state of the system and help with troubleshooting issues.  Given
   that logs try to capture state that is useful for monitoring and
   debugging, they can contain information that can be used to identify
   users.  Personal data identification and anonymization in logs is
   crucial to ensure that no personal data is being inadvertently logged
   and retained which would make the logging system run afoul of laws
   around storing private information.  This document focuses on
   exploring mechanisms that can be used by a generating or intermediary
   logging service to specify personal or sensitive data in log
   message(s), thus allowing a downstream logging server to potentially
   enforce any redaction or transformation.





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