
From nobody Wed Mar  4 15:46:57 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pearg@irtf.org
Delivered-To: pearg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 91D903A0C14; Wed,  4 Mar 2020 15:46:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pearg@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.119.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pearg@irtf.org
Message-ID: <158336561242.29291.14945943222496920347@ietfa.amsl.com>
Date: Wed, 04 Mar 2020 15:46:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/x3erRSukZo0rRlbukTMxedW8UD8>
Subject: [Pearg] I-D Action: draft-irtf-pearg-censorship-01.txt
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.29
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: Wed, 04 Mar 2020 23:46:53 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Privacy Enhancements and Assessments Research Group RG of the IRTF.

        Title           : A Survey of Worldwide Censorship Techniques
        Authors         : Joseph Lorenzo Hall
                          Michael D. Aaron
                          Stan Adams
                          Ben Jones
                          Nick Feamster
	Filename        : draft-irtf-pearg-censorship-01.txt
	Pages           : 33
	Date            : 2020-03-04

Abstract:
   This document describes the technical mechanisms used by censorship
   regimes around the world to block or impair Internet traffic.  It
   aims to make designers, implementers, and users of Internet protocols
   aware of the properties being exploited and mechanisms used to censor
   end-user access to information.  This document makes no suggestions
   on individual protocol considerations, and is purely informational,
   intended to be a reference.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-pearg-censorship/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-pearg-censorship-01
https://datatracker.ietf.org/doc/html/draft-irtf-pearg-censorship-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-irtf-pearg-censorship-01


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Mar  4 15:52:44 2020
Return-Path: <hall@isoc.org>
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 6EE783A0C36 for <pearg@ietfa.amsl.com>; Wed,  4 Mar 2020 15:52:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.org
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 A5L743wigWHy for <pearg@ietfa.amsl.com>; Wed,  4 Mar 2020 15:52:40 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770077.outbound.protection.outlook.com [40.107.77.77]) (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 9E9C93A0C33 for <pearg@irtf.org>; Wed,  4 Mar 2020 15:52:40 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QJpxtKkKW5VfUkFCbYj3Vup9Keak8M0Uy+a/7SrxtXpKcYwPWnzyZA8IOeIXlS9uzSJhTx1Pru2Oba4fu1BpFBJBuyovONr2SsatsyEplFrpvYz71oq5chNf4Xt8RYOja/6uWHusmaRhmoH/jt5GAxrJv6JepuSInPutRVZ4nhAGK0VG0+PN6V9r9X/esnDovQe46jiW6fRwJ1vVvrQWU1nG0GNfqLZc0f2YLFzwGPWnRCyX9Lio3ISC4ksmXzmteN3Ru8kbrmjjiI+hnrbjSrC7t9Mm3ptLlegdNx2hbcX+JON+daJNphIkhWOJi/7D6jnqw7L69VpstIP8/jUdtA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pqgknaxKVUNT/1iCyNJP4r55g1wasUZmi41WO0hobaU=; b=CkCgXc+jtLjzdds1G1kdBnvJMxFFKU1nQm97ILOzzR0oNkZxPtGLnf/nNne+YrWLZqRgDXxaddU8CmLfbx6i5MHg1xCHWMP0wimk9zbdaryWEgwLnoIKYDqb2BR0thDQwfDZyv7WcLIM44nuJxTMnPGy4ajrUBgLQdomKeX0CbGJ403kAJ63KP5GgdBVnlnPjXIGEIEy6ZRw3mrV00v8ZhAvzOOlTC+oKs8eygR1DQ0ogMAlrmrjOlnTMS1VEeFZjNIsxiiocuIFwQma7tuwNevVOyOhOPOFfb0P2ZPQoNuNAwFzUTYCfOFppl7kfn7/j1LNplN3zwKbDWGjda3Opw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isoc.org; dmarc=pass action=none header.from=isoc.org; dkim=pass header.d=isoc.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector2;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pqgknaxKVUNT/1iCyNJP4r55g1wasUZmi41WO0hobaU=; b=XexFxlG1/Xuf9srqML8LQFXZsI3LFuADcJcT/F5D2OoXLlMzi1oif70c/w3hqxOkCRbtW90C8INpb/Xr/8mIf6tZo/4XTRQZobqplmPTJ7fpmqpmhuTvux49YSDmq6VJ6ypUStd2JIeOJ37D4sksOcwAyajSN0oDdnOjFEh17KM=
Received: from BY5PR06MB6451.namprd06.prod.outlook.com (2603:10b6:a03:21e::20) by BY5PR06MB6644.namprd06.prod.outlook.com (2603:10b6:a03:239::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.14; Wed, 4 Mar 2020 23:52:37 +0000
Received: from BY5PR06MB6451.namprd06.prod.outlook.com ([fe80::3891:1ca6:1667:cbd]) by BY5PR06MB6451.namprd06.prod.outlook.com ([fe80::3891:1ca6:1667:cbd%2]) with mapi id 15.20.2772.019; Wed, 4 Mar 2020 23:52:37 +0000
From: Joseph Lorenzo Hall <hall@isoc.org>
To: "pearg@irtf.org" <pearg@irtf.org>
Thread-Topic: [Pearg] I-D Action: draft-irtf-pearg-censorship-01.txt
Thread-Index: AQHV8n9FPLBrQUyXHUS7WpR3DRcPgqg5GjtF
Date: Wed, 4 Mar 2020 23:52:37 +0000
Message-ID: <BY5PR06MB645144AB6EF1CF6A9D3E7737B1E50@BY5PR06MB6451.namprd06.prod.outlook.com>
References: <158336561242.29291.14945943222496920347@ietfa.amsl.com>
In-Reply-To: <158336561242.29291.14945943222496920347@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hall@isoc.org; 
x-originating-ip: [173.73.251.251]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b4779dc9-06cd-4ddd-d31a-08d7c0971e4e
x-ms-traffictypediagnostic: BY5PR06MB6644:
x-microsoft-antispam-prvs: <BY5PR06MB664464426EB1C660E92259EFB1E50@BY5PR06MB6644.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0332AACBC3
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(39850400004)(396003)(366004)(376002)(346002)(199004)(189003)(186003)(26005)(8936002)(2906002)(33656002)(316002)(6916009)(52536014)(478600001)(966005)(7696005)(81166006)(55016002)(64756008)(8676002)(9686003)(71200400001)(81156014)(66574012)(66946007)(5660300002)(53546011)(66476007)(86362001)(66446008)(19627405001)(6506007)(76116006)(91956017)(66556008); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR06MB6644; H:BY5PR06MB6451.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: npgzYZ9O1359uxXAM6tK44vn6wKepu8qYe/+WF2IQUuZySal6AMsCMk/1COk1oUyChAfjJ4EJg+7LNO6XuhrOMDTBpm39dMYdi/ErR+Ntph7nET0BEzlq4wPpXcM3UGq5U7r0AYmLk5xugjFRnX0jaEqztedtbI7OZCkhkt8IXoCukduE6+9d71mOk+JSfNwsuXAbI+cGEkuM02xUga10NmS8wtOlIEwjWhunMAIwWJsxxNop+y9HBySZibkFOdFQkWwKnR/TtuXYEvZxlE+MeJ7UE2kTq/oVnRdUaOLIEuNcDTHCdiRUg6zgKEXHPn2jgrFSCup46E24m825SDYoRYhBjU21C0Ghe8VdauPguV/7boQPs3as6AqQsTGrmI/PK1V25jCwHH6iWp+ttxBa3vQeCYRorLs+mFuiPZSVd9XO+PN09iZV2woz5THGc9r5YIJF76g/7wKvQKqsO2TgBaRNFbA8QYNrb5X26mlaBVOr0H9pkxQrrKfz/YxrWYJL8ZJ+cyCtb2RNle3OuCfnw==
x-ms-exchange-antispam-messagedata: /k8eyhSaMT9fTJ7SCDIHWoW0q0oZumlj+YMBDOYq0YLt5RtQWepZIVaBrRdTXGGirmBQzwX5MfwuiXlzCqnVZE1qqliEptWaNN6m9MWoLqxuRPBDm4RY/5tcE9/T8SbCKEKyx69YUXWD3iv8yQiNlA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BY5PR06MB645144AB6EF1CF6A9D3E7737B1E50BY5PR06MB6451namp_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-Network-Message-Id: b4779dc9-06cd-4ddd-d31a-08d7c0971e4e
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2020 23:52:37.5300 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: J/8ci/hNeCRvijbk2Q4AGzdxmSZ+lChOLzg4gOXDCDRbe9vdw07ljh4EFktH5DDx
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR06MB6644
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/_CrA78_XUvJnso2RJB-4eFQpFwk>
Subject: Re: [Pearg] I-D Action: draft-irtf-pearg-censorship-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: Wed, 04 Mar 2020 23:52:43 -0000

--_000_BY5PR06MB645144AB6EF1CF6A9D3E7737B1E50BY5PR06MB6451namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This version incorporates a series of edits I had been meaning to get to, n=
otably from Ameila Andersdotter, Michael Richardson and a few others.

I'll probably give it one last good read through before the drafts deadline=
 on Monday but should otherwise be ready for RG LC at that time and present=
ation in Vancouver for 107 (if you read this version and think it is not re=
ady, please say so on-list and/or wander over to the github Issues list for=
 the associated repository): https://github.com/josephlhall/rfc-censorship-=
tech/issues

cheers, Joe
________________________________
From: Pearg <pearg-bounces@irtf.org> on behalf of internet-drafts@ietf.org =
<internet-drafts@ietf.org>
Sent: Wednesday, March 4, 2020 18:46
To: i-d-announce@ietf.org <i-d-announce@ietf.org>
Cc: pearg@irtf.org <pearg@irtf.org>
Subject: [Pearg] I-D Action: draft-irtf-pearg-censorship-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Privacy Enhancements and Assessments Resea=
rch Group RG of the IRTF.

        Title           : A Survey of Worldwide Censorship Techniques
        Authors         : Joseph Lorenzo Hall
                          Michael D. Aaron
                          Stan Adams
                          Ben Jones
                          Nick Feamster
        Filename        : draft-irtf-pearg-censorship-01.txt
        Pages           : 33
        Date            : 2020-03-04

Abstract:
   This document describes the technical mechanisms used by censorship
   regimes around the world to block or impair Internet traffic.  It
   aims to make designers, implementers, and users of Internet protocols
   aware of the properties being exploited and mechanisms used to censor
   end-user access to information.  This document makes no suggestions
   on individual protocol considerations, and is purely informational,
   intended to be a reference.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-pearg-censorship/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-pearg-censorship-01
https://datatracker.ietf.org/doc/html/draft-irtf-pearg-censorship-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-irtf-pearg-censorship-01


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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


--
Pearg mailing list
Pearg@irtf.org
https://www.irtf.org/mailman/listinfo/pearg

--_000_BY5PR06MB645144AB6EF1CF6A9D3E7737B1E50BY5PR06MB6451namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
This version incorporates a series of edits I had been meaning to get to, n=
otably from Ameila Andersdotter, Michael Richardson and a few others.</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
I'll probably give it one last good read through before the drafts deadline=
 on Monday but should otherwise be ready for RG LC at that time and present=
ation in Vancouver for 107 (if you read this version and think it is not re=
ady, please say so on-list and/or
 wander over to the github Issues list for the associated repository): <a h=
ref=3D"https://github.com/josephlhall/rfc-censorship-tech/issues">
https://github.com/josephlhall/rfc-censorship-tech/issues</a></div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
cheers, Joe<br>
</div>
<div id=3D"appendonsend"></div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Pearg &lt;pearg-bounc=
es@irtf.org&gt; on behalf of internet-drafts@ietf.org &lt;internet-drafts@i=
etf.org&gt;<br>
<b>Sent:</b> Wednesday, March 4, 2020 18:46<br>
<b>To:</b> i-d-announce@ietf.org &lt;i-d-announce@ietf.org&gt;<br>
<b>Cc:</b> pearg@irtf.org &lt;pearg@irtf.org&gt;<br>
<b>Subject:</b> [Pearg] I-D Action: draft-irtf-pearg-censorship-01.txt</fon=
t>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Privacy Enhancements and Assessments Resea=
rch Group RG of the IRTF.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : A Survey of Worldwide Censorship Techni=
ques<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Authors&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; : Joseph Lorenzo Hall<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Michael D. Aaron<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Stan Adams<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Ben Jones<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Nick Feamster<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; : draft-irtf-pearg-censorship-01.txt<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 33<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2020-03-04<br>
<br>
Abstract:<br>
&nbsp;&nbsp; This document describes the technical mechanisms used by censo=
rship<br>
&nbsp;&nbsp; regimes around the world to block or impair Internet traffic.&=
nbsp; It<br>
&nbsp;&nbsp; aims to make designers, implementers, and users of Internet pr=
otocols<br>
&nbsp;&nbsp; aware of the properties being exploited and mechanisms used to=
 censor<br>
&nbsp;&nbsp; end-user access to information.&nbsp; This document makes no s=
uggestions<br>
&nbsp;&nbsp; on individual protocol considerations, and is purely informati=
onal,<br>
&nbsp;&nbsp; intended to be a reference.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-irtf-pearg-censorship/">h=
ttps://datatracker.ietf.org/doc/draft-irtf-pearg-censorship/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-irtf-pearg-censorship-01">http=
s://tools.ietf.org/html/draft-irtf-pearg-censorship-01</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-irtf-pearg-censorshi=
p-01">https://datatracker.ietf.org/doc/html/draft-irtf-pearg-censorship-01<=
/a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-irtf-pearg-censorship-=
01">https://www.ietf.org/rfcdiff?url2=3Ddraft-irtf-pearg-censorship-01</a><=
br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at tools.ietf.org.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet=
-drafts/</a><br>
<br>
<br>
-- <br>
Pearg mailing list<br>
Pearg@irtf.org<br>
<a href=3D"https://www.irtf.org/mailman/listinfo/pearg">https://www.irtf.or=
g/mailman/listinfo/pearg</a><br>
</div>
</span></font></div>
</body>
</html>

--_000_BY5PR06MB645144AB6EF1CF6A9D3E7737B1E50BY5PR06MB6451namp_--


From nobody Mon Mar  9 11:10:45 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pearg@irtf.org
Delivered-To: pearg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4791F3A147A; Mon,  9 Mar 2020 11:10:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pearg@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pearg@irtf.org
Message-ID: <158377743223.5683.14796831663415131774@ietfa.amsl.com>
Date: Mon, 09 Mar 2020 11:10:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/ZjlvIT7vk3BD12gNq82SISCR7DU>
Subject: [Pearg] I-D Action: draft-irtf-pearg-censorship-02.txt
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.29
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, 09 Mar 2020 18:10:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Privacy Enhancements and Assessments Research Group RG of the IRTF.

        Title           : A Survey of Worldwide Censorship Techniques
        Authors         : Joseph Lorenzo Hall
                          Michael D. Aaron
                          Stan Adams
                          Amelia Andersdotter
                          Ben Jones
                          Nick Feamster
	Filename        : draft-irtf-pearg-censorship-02.txt
	Pages           : 34
	Date            : 2020-03-09

Abstract:
   This document describes the technical mechanisms used by censorship
   regimes around the world to block or impair Internet traffic.  It
   aims to make designers, implementers, and users of Internet protocols
   aware of the properties being exploited and mechanisms used to censor
   end-user access to information.  This document makes no suggestions
   on individual protocol considerations, and is purely informational,
   intended to be a reference.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-pearg-censorship/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-pearg-censorship-02
https://datatracker.ietf.org/doc/html/draft-irtf-pearg-censorship-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-irtf-pearg-censorship-02


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Mar  9 16:34:25 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pearg@irtf.org
Delivered-To: pearg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6C13A095C; Mon,  9 Mar 2020 16:34:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pearg@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pearg@irtf.org
Message-ID: <158379685903.5446.1947503840647416682@ietfa.amsl.com>
Date: Mon, 09 Mar 2020 16:34:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/KLwMHFzpoLNEYJIDstozXkE-LOA>
Subject: [Pearg] I-D Action: draft-irtf-pearg-numeric-ids-history-01.txt
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.29
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, 09 Mar 2020 23:34:19 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Privacy Enhancements and Assessments Research Group RG of the IRTF.

        Title           : Unfortunate History of Transient Numeric Identifiers
        Authors         : Fernando Gont
                          Ivan Arce
	Filename        : draft-irtf-pearg-numeric-ids-history-01.txt
	Pages           : 25
	Date            : 2020-03-09

Abstract:
   This document analyzes the timeline of the specification and
   implementation of different types of "transient numeric identifiers"
   used in IETF protocols, and how the security and privacy implications
   of such protocols have been affected as a result of it.  It provides
   empirical evidence that advice in this area is warranted.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-pearg-numeric-ids-history/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-pearg-numeric-ids-history-01
https://datatracker.ietf.org/doc/html/draft-irtf-pearg-numeric-ids-history-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-irtf-pearg-numeric-ids-history-01


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Thu Mar 19 06:57:34 2020
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: ADFU+vvneBmmhtue7fhy7aHJ15b6IrwdDBObMEB/x/5vOaDIWbj7Rb1epjP5dBjfsqzdnYT8s4Mya5RYaKq3H62evqw=
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

--000000000000b2fa4605a1358cc6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi All,


Here=E2=80=99s updated (version -01) of  Personal Information Tagging for L=
ogs

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>, Santhosh C N <
santoshcn1@gmail.com>, Ryan Guest <rguest@salesforce.com>, 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.tx=
t
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=3Ddraft-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 submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--000000000000b2fa4605a1358cc6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br>





<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">Hi All,</p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">Here=E2=80=99s updated (versio=
n -01) of<span class=3D"gmail-Apple-converted-space">=C2=A0 </span>Personal=
 Information Tagging for Logs</p>
<p class=3D"gmail-p3" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;;color:rgb(220,161,13)"><span cl=
ass=3D"gmail-s1" style=3D"text-decoration-line:underline"><a href=3D"https:=
//www.ietf.org/internet-drafts/draft-rao-pitfol-01.txt">https://www.ietf.or=
g/internet-drafts/draft-rao-pitfol-01.txt</a></span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;;min-height:14px"><span class=3D=
"gmail-s1" style=3D"text-decoration-line:underline"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">Thanks everyone for your input=
s on the earlier version during IETF 106.</p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">Key updates in this version ar=
e:</p>
<ol class=3D"gmail-ol1">
<li class=3D"gmail-li1" style=3D"margin:0px;font-variant-numeric:normal;fon=
t-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:=
normal;font-family:&quot;Helvetica Neue&quot;">Model for structured logging=
 and use of standardized identifiers for personal information.</li>
<li class=3D"gmail-li1" style=3D"margin:0px;font-variant-numeric:normal;fon=
t-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:=
normal;font-family:&quot;Helvetica Neue&quot;">Illustration of Personal Inf=
ormation Identifiers Registry and associating sensitivity level for each id=
entifier.</li>
<li class=3D"gmail-li1" style=3D"margin:0px;font-variant-numeric:normal;fon=
t-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:=
normal;font-family:&quot;Helvetica Neue&quot;">Role based Redaction and acc=
ess control</li></ol>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;;min-height:14px">Appreciate you=
r review comments and feedback.</p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">Thanks</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">-Sandeep</p><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr"><br></div><div dir=3D"ltr" c=
lass=3D"gmail_attr">---------- Forwarded message ---------<br>From: <span d=
ir=3D"auto">&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts=
@ietf.org</a>&gt;</span><br>Date: Tue, Mar 10, 2020 at 3:27 AM<br>Subject: =
New Version Notification for draft-rao-pitfol-01.txt<br>To: Sandeep Rao &lt=
;<a href=3D"mailto:sandeeprao.ietf@gmail.com">sandeeprao.ietf@gmail.com</a>=
&gt;, Santhosh C N &lt;<a href=3D"mailto:santoshcn1@gmail.com">santoshcn1@g=
mail.com</a>&gt;, Ryan Guest &lt;<a href=3D"mailto:rguest@salesforce.com">r=
guest@salesforce.com</a>&gt;, Shivan Sahib &lt;<a href=3D"mailto:shivankaul=
sahib@gmail.com">shivankaulsahib@gmail.com</a>&gt;<br></div><br><br><br>
A new version of I-D, draft-rao-pitfol-01.txt<br>
has been successfully submitted by Shivan Sahib and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-rao-pitfol<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A001<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Personal Information Tagging for L=
ogs<br>
Document date:=C2=A0 2020-03-09<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 10<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-rao-pitfol-01.txt" rel=3D"noreferrer" target=3D"_b=
lank">https://www.ietf.org/internet-drafts/draft-rao-pitfol-01.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-rao-pitfol/" rel=3D"noreferrer" target=3D"_blank">https://d=
atatracker.ietf.org/doc/draft-rao-pitfol/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-rao-pitfol-01" rel=3D"noreferrer" target=3D"_blank">https://tools.iet=
f.org/html/draft-rao-pitfol-01</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-rao-pitfol" rel=3D"noreferrer" target=3D"_blank">https://da=
tatracker.ietf.org/doc/html/draft-rao-pitfol</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-rao-pitfol-01" rel=3D"noreferrer" target=3D"_blank"=
>https://www.ietf.org/rfcdiff?url2=3Ddraft-rao-pitfol-01</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0Software systems typically generate log messages in the course=
 of<br>
=C2=A0 =C2=A0their operation.=C2=A0 These log messages (or &#39;logs&#39;) =
record events as<br>
=C2=A0 =C2=A0they happen, thus providing a trail that can be used to unders=
tand<br>
=C2=A0 =C2=A0the state of the system and help with troubleshooting issues.=
=C2=A0 Given<br>
=C2=A0 =C2=A0that logs try to capture state that is useful for monitoring a=
nd<br>
=C2=A0 =C2=A0debugging, they can contain information that can be used to id=
entify<br>
=C2=A0 =C2=A0users.=C2=A0 Personal data identification and anonymization in=
 logs is<br>
=C2=A0 =C2=A0crucial to ensure that no personal data is being inadvertently=
 logged<br>
=C2=A0 =C2=A0and retained which would make the logging system run afoul of =
laws<br>
=C2=A0 =C2=A0around storing private information.=C2=A0 This document focuse=
s on<br>
=C2=A0 =C2=A0exploring mechanisms that can be used by a generating or inter=
mediary<br>
=C2=A0 =C2=A0logging service to specify personal or sensitive data in log<b=
r>
=C2=A0 =C2=A0message(s), thus allowing a downstream logging server to poten=
tially<br>
=C2=A0 =C2=A0enforce any redaction or transformation.<br>
<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
<br>
</div></div>

--000000000000b2fa4605a1358cc6--


From nobody Sat Mar 28 17:44:57 2020
Return-Path: <caw@heapingbits.net>
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 302C73A0C31 for <pearg@ietfa.amsl.com>; Sat, 28 Mar 2020 17:44:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=heapingbits.net header.b=J5fjXBGf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=uTP2D/KQ
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 rF6TGBj8ILhr for <pearg@ietfa.amsl.com>; Sat, 28 Mar 2020 17:44:53 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 748613A0C35 for <pearg@irtf.org>; Sat, 28 Mar 2020 17:44:53 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id C47BD654 for <pearg@irtf.org>; Sat, 28 Mar 2020 20:44:51 -0400 (EDT)
Received: from imap4 ([10.202.2.54]) by compute1.internal (MEProxy); Sat, 28 Mar 2020 20:44:51 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:date:from:to:subject:content-type; s= fm1; bh=ZXZHDplA/JOwLue/pw2j2LKyoQ6aal5CDWCTXnCBDdw=; b=J5fjXBGf vaT50t7gHl0LsSoQhC9iWrAP0YM5zMYmi8IS22BOutQsOk2UQJf5UNkhr0tZcVEd y1P8k9C+Kq3ssGJDnjOyS6H7BfyhvBwxkerfPLZj/joxCVsGloaG/HkmeLgUsDvY TgjUDYwfTFthuyOQF0n3TeAI/hxQ79YZ0TM9o+rGZ3rCgYk2XqsY7wX8RFuI2GpL fSVkNUEtWKfq3ivV2S/i15VeS2qDSOVkAT0/za2yJvUGidaqFLKBwhN+KDhHviH7 ZtPjAPLBLdQckztWMdsyciGc+W01pkdq974tKocHngnIq1paL+Js5xGPdV0i85u+ GM6mDrvZ5jPlMA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=ZXZHDplA/JOwLue/pw2j2LKyoQ6aa l5CDWCTXnCBDdw=; b=uTP2D/KQtjxrIy2ss5Dq2AbZp1nlsIXDvM8/ZuZUCaS57 BKoUpvwVuT3PKBBmwE1oVo4cVNqkKp2tOxVIIdA2A6sksuTSOY62VbnQNwD5yImD q3B2fcQF/QMoM7Vop0aznY6nngJZWnOjYnwl5MNiXQRzAdHyM+Twq0sX3rcWEZ36 RSzYjxsynEAVmFsRQkbHxHj0DBvaRTUK8Rqv//ogCfy47c7ApmAMxFRiNQWMuEFZ I4hRZaVAymFaXtOJkF2eo151Wg8Delj7FRBSSHKxwcqHFV/L9r7OV6FRajGOlALX XWlpKHVPEo85Uff4gq3S4fhSgs5oV/O8LnlIc6LBw==
X-ME-Sender: <xms:g-9_XrpQfjf9AcXsMg-zakrnALEusbBEMotc9URpR2d49ho7OjIa4g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudeivddgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsehttdertd erredtnecuhfhrohhmpedfvehhrhhishhtohhphhgvrhcuhghoohgufdcuoegtrgifsehh vggrphhinhhgsghithhsrdhnvghtqeenucffohhmrghinhepihgvthhfrdhorhhgnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheptggrfieshhgv rghpihhnghgsihhtshdrnhgvth
X-ME-Proxy: <xmx:g-9_Xh9FSYJ-tVfGeKuqhtuGPX685DXI3NHUJMj9xGQcw21wwH-9VA> <xmx:g-9_Xp3q1aGEXzb3ERH5e3JLq5PW6fqibo-7xEa60zVkfG1Dcwvgrg> <xmx:g-9_XsCx3tDP8HKvmShWM1muSpEviFvaMJw7Yn6WqgR2leoR18Cx1Q> <xmx:g-9_Xhu4fYx2bxadxcX-SQD5NDKwDC93kBE-FyqvJ-rHZRz2ENXj3w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0DA423C00A1; Sat, 28 Mar 2020 20:44:51 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-1021-g152deaf-fmstable-20200319v1
Mime-Version: 1.0
Message-Id: <819285e9-f34e-4815-a046-852c453d23f8@www.fastmail.com>
Date: Sat, 28 Mar 2020 17:44:30 -0700
From: "Christopher Wood" <caw@heapingbits.net>
To: pearg@irtf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/iOAyuVRrwbODpeaSUfLKq7Es_0Q>
Subject: [Pearg] Review of draft-irtf-pearg-numeric-ids-history-01
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: Sun, 29 Mar 2020 00:44:55 -0000

Document: draft-irtf-pearg-numeric-ids-history-01 [https://tools.ietf.org/id/draft-irtf-pearg-numeric-ids-history-01.txt]

Assessment: Almost ready

Thanks for putting this information together! I think the analysis and timeline are 
a testament to the importance and subtleties of numeric identifier generation. 
The amount of detail is quite comprehensive. Even if there are glaring omissions,
I think the overall point is made clear.

I only have some high level comments on the document, along with several nits. 
(If it'd be easier, and if you have the repository on GitHub, I can submit a PR 
for the nits.)

Comments:

- Section 2: Neither hard nor soft failures are used in the document. Can we just remove 
these terms altogether?
- Section 3: Perhaps it's worth mentioning that we consider the standard Dolev-Yao 
style attacker as outlined in RFC3552?
- Section 5, second paragraph: It looks the start of this sentence (or paragraph)
was accidentally deleted:

   he interoperability requirements for TCP ISNs are probably not
   clearly spelled out as one would expect.  

Nits:
    
- Abstract: "implications" seems like the wrong word. Perhaps "properties" can be
used instead? (That is, identifiers can affect security and privacy properties, not
affect *implications*. This is what's used in Section 1, too.)
- Section 1: s/the poor selection of the aforementioned/poor selection of numeric
- Section 1: The sentence, "While it is generally possible... is non-trivial" seems like
it can come at the *end* of the introduction, or removed altogether as it's redundant
with a later sentence in the same section.
- Section 1 (and elsewhere): and/or is not a word -- please use or.
- Section 1: it might help to clarify what is an "inappropriate" algorithm.
- Section 1: s/The analysis of such timelines indicate that/This analysis indicates that
- Section 4: s/The above mas been/The above has been
- Section 4: s/specification misses a/specification omits
- Section 4: s/This has resulted in virtually all/This resulted in many
- Section 4: In the December 2014 entry, it would be good to reference 
I-D.gont-6man-predictable-fragment-id specifically rather than say "the aforementioned
IETF Internet Draft".
- Section 5: s/leads to negative security and privacy implications/harms security 
and privacy properties (Let's make this change through the document, please!)
- Section 6: s/replacement of such flawed scheme/replacement of this flawed scheme
- Section 6: s/wg item of the 6man wg/WG item of the 6man WG (capitalize WG here and elsewhere)
- Section 7: s/The NTP [RFC5905] is employed to avoid/NTP [RFC5905] avoids
- Section 8: s/The proposal experiments/The proposal experiences
- Section 10: s/This document analyzes the timeline of the specification of different types of "numeric identifiers" used in IETF protocols/This document analyzes the timeline of IETF protocol "numeric identifiers"


From nobody Sat Mar 28 17:45:20 2020
Return-Path: <caw@heapingbits.net>
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 C65F53A0C39 for <pearg@ietfa.amsl.com>; Sat, 28 Mar 2020 17:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=heapingbits.net header.b=QZu6vbca; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=FzU4/3Ez
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 oh9ibbr2lSZS for <pearg@ietfa.amsl.com>; Sat, 28 Mar 2020 17:45:17 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 451653A0C38 for <pearg@irtf.org>; Sat, 28 Mar 2020 17:45:17 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id BB6A4654 for <pearg@irtf.org>; Sat, 28 Mar 2020 20:45:16 -0400 (EDT)
Received: from imap4 ([10.202.2.54]) by compute1.internal (MEProxy); Sat, 28 Mar 2020 20:45:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=htHb3vWo1UfsG+MdEHd4Zvx+maHdUWf UlKKhyYUTRiE=; b=QZu6vbcabYRGDWvU/KN1iyWRfG0rPg6SozaoBEaN8pjJLZA kMVe4tPPtWaJjbKEkxWbHtu6rzRkyM9RsmYs/QCTSkZiEvXwqyN9ZuLgU/ppzTDZ 8o8qGl5NXr2R/V459H9+nbBajPL97D5nz9N6RQECqFYWpmLjdqnl3MNVOadj0pje Z95xi/Zv2pGnaEg0oPQQBOKRa+/b8ZcERYv1FaiFs3r4pKMukQ0qWt2YM454jY++ RChIMYHLilRLQzaMQOeNtOlL+QsncOIVLoqYGzt4HWFL4ylusle9HQ/DEKIOs4OT 5dz3JYlKbyvGHM4c+IR0RIFsYIYGO2cSBGZ50zw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=htHb3v Wo1UfsG+MdEHd4Zvx+maHdUWfUlKKhyYUTRiE=; b=FzU4/3Ezekcn/8XCJq0lju zdLrUTp5x78CR/fJlvqA+II584dtG7HCsyn9nfcYMZeKzNzF4JOl6uqUTMp2+mHW bQRKsjIB36gknDgxZQLWlAlz81tzjXkuIzVoEeBdNT6N04JkXhSWMcUdGelkiRl0 5rcPUZoIzxyS5900mAerY+6MwE+9650/eyGaQY31ZtO3m/5ndXWcCyWm+KVkdXN1 jQrNXCosI0IicggOzqEuQh2BfVIfTipYQQbVSGwTbZzS/CP6vHxlCIDzbLf+lJxh cYRHVcMDtEof5HHbFSOBfEoEFdnmOBUOxv+3312UcTUWXHqzUZrp/UW2kIaOLmyg ==
X-ME-Sender: <xms:nO9_XnWIRv7cQfHocKUw6FPosyQwMI3-wu_pd9v2WTyaHoyW4WPQ7w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudeivddgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfvehhrhhishhtohhphhgvrhcuhghoohgufdcuoegtrgif sehhvggrphhinhhgsghithhsrdhnvghtqeenucffohhmrghinhepihgvthhfrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheptggrfies hhgvrghpihhnghgsihhtshdrnhgvth
X-ME-Proxy: <xmx:nO9_XiIJ64OzOUBIm2T4xcy9K-YhHua-TvyHYfK5yxXK3Vbmp03_Dw> <xmx:nO9_XkVuhSzcwFMPOUT_Y2-FhSW4k0RQa-BoFdUF909bNRGKUuXTvA> <xmx:nO9_XnUPYNxr6VDr_pf_anMraKfYrFzJY-yvOVIUIdSFDj422lV7Kw> <xmx:nO9_Xu5vQm1_SZgjIKXEwXnnC6wvQY9r_iMyjQqnFEdEhvlOLT93zQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3BC7A3C00A1; Sat, 28 Mar 2020 20:45:16 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-1021-g152deaf-fmstable-20200319v1
Mime-Version: 1.0
Message-Id: <7a456b7f-e218-4345-95d8-1c7195a84f4a@www.fastmail.com>
In-Reply-To: <819285e9-f34e-4815-a046-852c453d23f8@www.fastmail.com>
References: <819285e9-f34e-4815-a046-852c453d23f8@www.fastmail.com>
Date: Sat, 28 Mar 2020 17:44:56 -0700
From: "Christopher Wood" <caw@heapingbits.net>
To: pearg@irtf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/2Qxw11OlEus2autTpVpqc8U5vK0>
Subject: Re: [Pearg] Review of draft-irtf-pearg-numeric-ids-history-01
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: Sun, 29 Mar 2020 00:45:19 -0000

... with no hat on!

Best,
Chris

On Sat, Mar 28, 2020, at 5:44 PM, Christopher Wood wrote:
> Document: draft-irtf-pearg-numeric-ids-history-01 
> [https://tools.ietf.org/id/draft-irtf-pearg-numeric-ids-history-01.txt]
> 
> Assessment: Almost ready
> 
> Thanks for putting this information together! I think the analysis and 
> timeline are 
> a testament to the importance and subtleties of numeric identifier 
> generation. 
> The amount of detail is quite comprehensive. Even if there are glaring 
> omissions,
> I think the overall point is made clear.
> 
> I only have some high level comments on the document, along with several nits. 
> (If it'd be easier, and if you have the repository on GitHub, I can submit a PR 
> for the nits.)
> 
> Comments:
> 
> - Section 2: Neither hard nor soft failures are used in the document. 
> Can we just remove 
> these terms altogether?
> - Section 3: Perhaps it's worth mentioning that we consider the 
> standard Dolev-Yao 
> style attacker as outlined in RFC3552?
> - Section 5, second paragraph: It looks the start of this sentence (or 
> paragraph)
> was accidentally deleted:
> 
>    he interoperability requirements for TCP ISNs are probably not
>    clearly spelled out as one would expect.  
> 
> Nits:
>     
> - Abstract: "implications" seems like the wrong word. Perhaps 
> "properties" can be
> used instead? (That is, identifiers can affect security and privacy 
> properties, not
> affect *implications*. This is what's used in Section 1, too.)
> - Section 1: s/the poor selection of the aforementioned/poor selection 
> of numeric
> - Section 1: The sentence, "While it is generally possible... is 
> non-trivial" seems like
> it can come at the *end* of the introduction, or removed altogether as 
> it's redundant
> with a later sentence in the same section.
> - Section 1 (and elsewhere): and/or is not a word -- please use or.
> - Section 1: it might help to clarify what is an "inappropriate" 
> algorithm.
> - Section 1: s/The analysis of such timelines indicate that/This 
> analysis indicates that
> - Section 4: s/The above mas been/The above has been
> - Section 4: s/specification misses a/specification omits
> - Section 4: s/This has resulted in virtually all/This resulted in many
> - Section 4: In the December 2014 entry, it would be good to reference 
> I-D.gont-6man-predictable-fragment-id specifically rather than say "the 
> aforementioned
> IETF Internet Draft".
> - Section 5: s/leads to negative security and privacy 
> implications/harms security 
> and privacy properties (Let's make this change through the document, 
> please!)
> - Section 6: s/replacement of such flawed scheme/replacement of this 
> flawed scheme
> - Section 6: s/wg item of the 6man wg/WG item of the 6man WG 
> (capitalize WG here and elsewhere)
> - Section 7: s/The NTP [RFC5905] is employed to avoid/NTP [RFC5905] 
> avoids
> - Section 8: s/The proposal experiments/The proposal experiences
> - Section 10: s/This document analyzes the timeline of the 
> specification of different types of "numeric identifiers" used in IETF 
> protocols/This document analyzes the timeline of IETF protocol "numeric 
> identifiers"
>


From nobody Sun Mar 29 17:49:28 2020
Return-Path: <fgont@si6networks.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 D01663A110B for <pearg@ietfa.amsl.com>; Sun, 29 Mar 2020 17:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 HOKyAd6vTRz5 for <pearg@ietfa.amsl.com>; Sun, 29 Mar 2020 17:49:24 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 449B43A09F4 for <pearg@irtf.org>; Sun, 29 Mar 2020 17:49:22 -0700 (PDT)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id D250A82820; Mon, 30 Mar 2020 02:49:16 +0200 (CEST)
To: Christopher Wood <caw@heapingbits.net>, pearg@irtf.org
References: <819285e9-f34e-4815-a046-852c453d23f8@www.fastmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <f43466a1-68c8-b631-a459-872dcedf8175@si6networks.com>
Date: Sun, 29 Mar 2020 21:49:03 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <819285e9-f34e-4815-a046-852c453d23f8@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/W_30xk4lFN6zr9RXvMSgvduTvhU>
Subject: Re: [Pearg] Review of draft-irtf-pearg-numeric-ids-history-01
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, 30 Mar 2020 00:49:27 -0000

Hello, Chris,

Thanks a lot for your feedback! In-line!

On 28/3/20 21:44, Christopher Wood wrote:
> Document: draft-irtf-pearg-numeric-ids-history-01 [https://tools.ietf.org/id/draft-irtf-pearg-numeric-ids-history-01.txt]
> 
> Assessment: Almost ready
> 
> Thanks for putting this information together! I think the analysis and timeline are
> a testament to the importance and subtleties of numeric identifier generation.
> The amount of detail is quite comprehensive. Even if there are glaring omissions,
> I think the overall point is made clear.

I'm curious about the omissions... which ones? If only for the sake of 
curiousity. :-)  (FWIW, for the most part we documented numeric IDs from 
different layers that we were closely involved in... not that there are 
not other, though!)




> I only have some high level comments on the document, along with several nits.
> (If it'd be easier, and if you have the repository on GitHub, I can submit a PR
> for the nits.)

Here it is: https://github.com/fgont/numeric-ids  . The working copy of 
the I-Ds are the ones with the "-latest" suffix.


> 
> Comments:
> 
> - Section 2: Neither hard nor soft failures are used in the document. Can we just remove
> these terms altogether?

Definitely yes. Done!


> - Section 3: Perhaps it's worth mentioning that we consider the standard Dolev-Yao
> style attacker as outlined in RFC3552?

Does RFC3552 actually mention it?


> - Section 5, second paragraph: It looks the start of this sentence (or paragraph)
> was accidentally deleted:
> 
>     he interoperability requirements for TCP ISNs are probably not
>     clearly spelled out as one would expect.

s/he/The/ -- done, thanks!




> Nits:

[...]
I have not applied these yet. If you want, you can send pull requests. 
Otherwise I will incorporate these comments tomorrow.

Thanks a lot!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




