Re: [ire] Deposit Identifiers

Gustavo Lozano <gustavo.lozano@icann.org> Tue, 09 April 2013 09:04 UTC

Return-Path: <gustavo.lozano@icann.org>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7BC21F8678 for <ire@ietfa.amsl.com>; Tue, 9 Apr 2013 02:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level:
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjARdgMQ6QhY for <ire@ietfa.amsl.com>; Tue, 9 Apr 2013 02:04:07 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id 12E5F21F85A1 for <ire@ietf.org>; Tue, 9 Apr 2013 02:04:06 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Tue, 9 Apr 2013 02:04:05 -0700
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: James Mitchell <james.mitchell@ausregistry.com.au>, "ire@ietf.org" <ire@ietf.org>
Date: Tue, 9 Apr 2013 02:04:03 -0700
Thread-Topic: [ire] Deposit Identifiers
Thread-Index: Ac41ATA99pfAdfKtR9yVPYT5egtIHw==
Message-ID: <CD89F705.FDCA%gustavo.lozano@icann.org>
In-Reply-To: <CD84E325.7531C%james.mitchell@ausregistry.com.au>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CD89F705FDCAgustavolozanoicannorg_"
MIME-Version: 1.0
Subject: Re: [ire] Deposit Identifiers
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ire>, <mailto:ire-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ire>
List-Post: <mailto:ire@ietf.org>
List-Help: <mailto:ire-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ire>, <mailto:ire-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 09:04:12 -0000

Thank you James,

In the new version of the specification the text will be updated to:

A REQUIRED "id" attribute that is used to uniquely identify the escrow deposit. Each registry is responsible for maintaining its own escrow deposits identifier space to ensure uniqueness. The identifier must be unique even for escrow deposits generated for the same Timeline Watermark.

We need the identifier because the data escrow specification was developed for general escrow in mind, resend is optional (but required for new gTLDs) and several deposits could have the same Timeline Watermark (e.g. resending).

Regards,
Gustavo

From: James Mitchell <james.mitchell@ausregistry.com.au<mailto:james.mitchell@ausregistry.com.au>>
Date: Friday, April 5, 2013 6:24 PM
To: "ire@ietf.org<mailto:ire@ietf.org>" <ire@ietf.org<mailto:ire@ietf.org>>
Subject: [ire] Deposit Identifiers

Gustavo,

The definition of the deposit ID is given below:

      A REQUIRED "id" attribute that is used to uniquely identify the
      escrow deposit.  Each registry is responsible for maintaining its
      own escrow deposits identifier space to ensure uniqueness, e.g.,
      using identifiers as described in Section 2.8 of [RFC5730].

Section 2.8 of RFC 5730 describes globally unique identifiers. I do not believe there is a need for globally unique identifiers, and therefore suggest updating the text to remove the reference to RFC5730 and instead require registries produce locally unique deposit identifiers. I actually see no need for deposit identifiers as the watermark is unique, one could use prevWatermark="" in replacement to prevId="".

If global uniqueness is required, we would like to use the concatenation of the TLD name and date, however the format does not currently allow this. We suggest the depositIdType pattern is updated to use a modified ROID pattern that allows hyphens, e.g. <pattern value="(\w|_|-){1,89}"/>, allowing for identifiers such as id="xn--punycode-20130405". This pattern would be reasonably consistent with the reference to RFC 5730.

Regards,
James