Re: Last Call: <draft-arkko-trip-registry-update-00.txt> (Update to the TRIP IANA Registry Rules Regarding Postal Addresses) to Informational RFC

Paul Wouters <paul@nohats.ca> Fri, 30 November 2018 23:07 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 805D41274D0; Fri, 30 Nov 2018 15:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 abYhN97q7CY8; Fri, 30 Nov 2018 15:07:08 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 17F19126DBF; Fri, 30 Nov 2018 15:07:05 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 43695174WzzMPq; Sat, 1 Dec 2018 00:07:01 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1543619222; bh=yhtx/mU7+JB11GHQTYtP/tQ2zWpz/Glqa0y571cyZfM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=oCLapfiPa6SB6BmI9pDLMVslSX7wawZjGQWevXvjpz+blMfY0cm0xkHYzxF4cPZDG Spb9PM6x/IJeOi5rk+vjgDsqnEywyok7gRiuG7+cH3884eyGsN/xgrFOhKZ79mBW+L ot9dJS9kyFeuKhKaex8xI7kGqqneH04QWJH+hzIc=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 8ULflX7aUZ29; Sat, 1 Dec 2018 00:06:59 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Sat, 1 Dec 2018 00:06:58 +0100 (CET)
Received: from [193.111.228.93] (unknown [193.111.228.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 8B9F7A7E0B; Fri, 30 Nov 2018 18:06:56 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 8B9F7A7E0B
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
Subject: Re: Last Call: <draft-arkko-trip-registry-update-00.txt> (Update to the TRIP IANA Registry Rules Regarding Postal Addresses) to Informational RFC
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (16A405)
In-Reply-To: <39E5F15D-54C0-431B-A54C-36977FFF4296@vigilsec.com>
Date: Fri, 30 Nov 2018 18:06:27 -0500
Cc: IETF <ietf@ietf.org>, Ben Campbell <ben@nostrum.com>, draft-arkko-trip-registry-update@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF6A2EBB-4E8C-4350-B7EA-CA2AD329EB3B@nohats.ca>
References: <154361542734.27535.10383183340180057481.idtracker@ietfa.amsl.com> <39E5F15D-54C0-431B-A54C-36977FFF4296@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CWrj5zNAga7PqGuyLtAhO9cozv4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Nov 2018 23:07:10 -0000

Agreed.

Although the Security Considerstions could mention the extra security gained by this?

Maybe we can also mo longer allow postal addresses and telephone numbers from all existing drafts? :)

Sent from mobile device

> On Nov 30, 2018, at 17:23, Russ Housley <housley@vigilsec.com> wrote:
> 
> I have read this (very short) document.  I agree with the proposed change to the IANA registry.  Let's not collect any unnecessary information from registrants,
> 
> Russ
> 
> 
>> On Nov 30, 2018, at 5:03 PM, The IESG <iesg-secretary@ietf.org> wrote:
>> 
>> 
>> The IESG has received a request from an individual submitter to consider the
>> following document: - 'Update to the TRIP IANA Registry Rules Regarding
>> Postal Addresses'
>> <draft-arkko-trip-registry-update-00.txt> as Informational RFC
>> 
>> The IESG plans to make a decision in the next few weeks, and solicits final
>> comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2018-12-28. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the beginning of
>> the Subject line to allow automated sorting.
>> 
>> Abstract
>> 
>> 
>>  This memo updates the IANA registry rules for the Telephony Routing
>>  over IP (TRIP) protocol, by no longer requiring that postal addresses
>>  be included in contact information.
>> 
>>  This memo updates RFC 3219.
>> 
>> 
>> 
>> 
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-arkko-trip-registry-update/
>> 
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/doc/draft-arkko-trip-registry-update/ballot/
>> 
>> 
>> No IPR declarations have been submitted directly on this I-D.
>> 
>> 
>> 
>>