Re: [Pearg] Proposed work on the topic of: IP Address Privacy

Tommy Pauly <tpauly@apple.com> Mon, 17 May 2021 17:24 UTC

Return-Path: <tpauly@apple.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 888A23A40B1 for <pearg@ietfa.amsl.com>; Mon, 17 May 2021 10:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=apple.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 Hr2R_Osgndb2 for <pearg@ietfa.amsl.com>; Mon, 17 May 2021 10:24:26 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp24.apple.com (rn-mailsvcp-ppex-lapp24.rno.apple.com [17.179.253.38]) (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 EA22E3A40B0 for <pearg@irtf.org>; Mon, 17 May 2021 10:24:26 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp24.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp24.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 14HHM2vY014061; Mon, 17 May 2021 10:24:26 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=RoWBx+R0mbrNeBEI0mfA9E/hcFxdt0+6ORXC6dbx9OI=; b=MavaaiaZiZTR7dAJkyWU78vzY9bzywP2Kq6jzChPoUyeK+0cMwXroS6W5SluhK1/LlZX 7fXNdwJKJZGmJxGTBLBrSdIaBgD13Bxbar7umeHXktHZNiq1MZyDabcCUTZrQdqTF1gq A0ZcMRTTCo1ED24u53NjkGTLq3QXDdBrdzo5qEzRWgk+/Pdmz/sPEYP4RdlYWeZcWcuM JrLpzYVuI3RTKS8sFzLK+LzXFsg5W4zVbLqG+zTgil88Tx3sg/Ytj8zS0r+3f2ZB5SDO F1++oC56C4MxF9NrGS6RR7hqVgUOguhQHCc66tWklUh0VfY9QLfIgobWSLxGXIANKADl 4w==
Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by rn-mailsvcp-ppex-lapp24.rno.apple.com with ESMTP id 38jbw9dtrg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 17 May 2021 10:24:26 -0700
Received: from rn-mailsvcp-mmp-lapp02.rno.apple.com (rn-mailsvcp-mmp-lapp02.rno.apple.com [17.179.253.15]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPS id <0QT9002DVHOQ0VC0@rn-mailsvcp-mta-lapp01.rno.apple.com>; Mon, 17 May 2021 10:24:26 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp02.rno.apple.com by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QT900J00HISKN00@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Mon, 17 May 2021 10:24:26 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 436bb85d015c8f100b68da878f7796c9
X-Va-E-CD: 84722d60e41a1e067a30fdd4877d2024
X-Va-R-CD: b8e40a7465f7cd4ef9651bb2f44da6d5
X-Va-CD: 0
X-Va-ID: 70bc47a4-b912-4aa0-aedb-23b00d643c67
X-V-A:
X-V-T-CD: 436bb85d015c8f100b68da878f7796c9
X-V-E-CD: 84722d60e41a1e067a30fdd4877d2024
X-V-R-CD: b8e40a7465f7cd4ef9651bb2f44da6d5
X-V-CD: 0
X-V-ID: 2563cf5c-94b7-464a-a4cc-787ab2569126
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-05-17_06:2021-05-17, 2021-05-17 signatures=0
Received: from smtpclient.apple (unknown [17.234.102.76]) by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QT900UKTHOPM400@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Mon, 17 May 2021 10:24:25 -0700 (PDT)
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 15.0 \(3674.0.2\))
From: Tommy Pauly <tpauly@apple.com>
In-reply-to: <50FDA194-93E4-488E-B80D-5AE134FD5D82@sinodun.com>
Date: Mon, 17 May 2021 10:24:25 -0700
Cc: pearg@irtf.org
Content-transfer-encoding: quoted-printable
Message-id: <40D3D924-2D50-48F0-9562-078469907150@apple.com>
References: <50FDA194-93E4-488E-B80D-5AE134FD5D82@sinodun.com>
To: Sara Dickinson <sara@sinodun.com>
X-Mailer: Apple Mail (2.3674.0.2)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-05-17_08:2021-05-17, 2021-05-17 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/EqSpgx5IXDaNHZjznH2H9UkwJ60>
Subject: Re: [Pearg] Proposed work on the topic of: IP Address Privacy
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, 17 May 2021 17:24:32 -0000


> On May 14, 2021, at 2:42 AM, Sara Dickinson <sara@sinodun.com> wrote:
> 
> Hi PEARG, 
> 
> This is a belated follow up to the Interim meeting and IETF110 discussion on the topic of "IP Address Privacy".
> 
> There appeared to be interest in working on one or more documents to capture the current status and future research directions in this space. A general proposal for such work could include:
> 
> * An analysis of the current use cases, attempting to categorise/group such use cases where commonalities exist
> * Generating requirements for proposed 'replacement signals' from this analysis (these could be different for each category/group of use cases)
> * Research to evaluate existing technologies or propose new mechanisms for such signals
> 
> One request was to have a broad scope for the range of use cases considered. We may need a first pass at the initial analysis to see if this is really feasible. 
> 
> The chairs would like to hear if
> 1) The above is a reasonable summary of work that folks think could/should be done in PEARG

This summary does sound reasonable, and the proposed work sounds quite useful.

> 2) If people are interested in volunteering to work on some or all of this

I’m happy to contribute, review, and write text, although I’d prefer to not be a primary author or editor.

Best,
Tommy

> 
> Please let us know your thoughts on this topic during the next couple of weeks. Before the end of May, we’ll try to summarise the responses and the plan for moving forward. 
> 
> 
> Best regards
> 
> Sara, on behalf of the chairs.
> -- 
> Pearg mailing list
> Pearg@irtf.org
> https://www.irtf.org/mailman/listinfo/pearg