[regext] Alissa Cooper's No Objection on draft-ietf-regext-rdap-object-tag-04: (with COMMENT)

Alissa Cooper <alissa@cooperw.in> Tue, 31 July 2018 17:27 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C744130F4F; Tue, 31 Jul 2018 10:27:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-regext-rdap-object-tag@ietf.org, James Gould <jgould@verisign.com>, regext-chairs@ietf.org, jgould@verisign.com, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153305805904.3273.14937489699671784628.idtracker@ietfa.amsl.com>
Date: Tue, 31 Jul 2018 10:27:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/8qhIhx4hIuiH6-r1nw8dmlIdsuQ>
Subject: [regext] Alissa Cooper's No Objection on draft-ietf-regext-rdap-object-tag-04: (with COMMENT)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.27
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2018 17:27:50 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-regext-rdap-object-tag-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-object-tag/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm not sure why anyone would do this, but I'll ask anyway: is there no concern
about someone maliciously registering an identifier against an existing RDAP
URL, given that the registry is specified to be FCFS? Let's say I have a grudge
against MyLocalRIR and I go register "fubar" as the service provider name
together with an existing mylocalrir.org RDAP URL. This maybe has little
practical effect but surely MyLocalRIR would not be too happy with it.