Re: [dispatch] Draft on TRIP IANA registry & postal addresses

Jari Arkko <jari.arkko@piuha.net> Fri, 20 July 2018 12:35 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D06127332 for <dispatch@ietfa.amsl.com>; Fri, 20 Jul 2018 05:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_FILL_THIS_FORM_SHORT=0.01] 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 NiLgaITyqOlj for <dispatch@ietfa.amsl.com>; Fri, 20 Jul 2018 05:35:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B1FDD12426A for <dispatch@ietf.org>; Fri, 20 Jul 2018 05:35:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C09076601DA; Fri, 20 Jul 2018 15:35:32 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGFcQjfvXdRV; Fri, 20 Jul 2018 15:35:31 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 7ED74660162; Fri, 20 Jul 2018 15:35:31 +0300 (EEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20180718171158.132b4da0@elandnews.com>
Date: Fri, 20 Jul 2018 08:35:29 -0400
Cc: dispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <48730143-CC13-4CA3-A793-C9249ABDAE9A@piuha.net>
References: <153192515603.3010.16432802912328612304.idtracker@ietfa.amsl.com> <375B94CD-1B80-4A9C-B48F-7ADB7F3EFD87@piuha.net> <CAHBDyN7k=+7RTdygjDX1ZBza7kMsT-=isjORMTXrkqNpJZoZVg@mail.gmail.com> <6.2.5.6.2.20180718171158.132b4da0@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/UYPIUO68oElkaPNCq4GUILqCxGc>
Subject: Re: [dispatch] Draft on TRIP IANA registry & postal addresses
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2018 12:35:36 -0000

SM,

> The Introduction Section mentions "privacy benefit" with respect to postal addresses.  If I understood corectly, the issue is about PII.  Should both postal and email addresses be considered instead of postal addresses only?

Good question.

However, we are targeting only one change with regards to this draft, the postal addresses. This registry is to my knowledge the only one that current requires postal addresses, and we want to fix that because that keeps showing up as an exception in IANA’s explanation of how they handle privacy, how they deal with GDPR, etc.

There’s another and potentially bigger question of many registries including email addresses; the position that we have taken is that those addresses are necessary for the public benefit that these registries provide, e.g., by allowing us to reach out to the people who made requests and ask them about their usage. Nevertheless, it was not the purpose of this draft to go into the email question, and if any change were to be made there, it should probably apply more broadly than the TRIP registry. And be in another draft :-)

Hope this clarifies,

Jari