Re: [ire] "resend" attribute in "deposit" element.

Francisco Obispo <fobispo@isc.org> Tue, 02 April 2013 00:37 UTC

Return-Path: <fobispo@isc.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 C45F921F8F35 for <ire@ietfa.amsl.com>; Mon, 1 Apr 2013 17:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 2sjchGdnDHP4 for <ire@ietfa.amsl.com>; Mon, 1 Apr 2013 17:37:28 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id BE1EA21F844F for <ire@ietf.org>; Mon, 1 Apr 2013 17:37:27 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id A612D5F997C; Tue, 2 Apr 2013 00:37:16 +0000 (UTC) (envelope-from fobispo@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1364863047; bh=HA5usEXfDYkP2D5bRgLMsPkXAZxJH3SnWO67/X0IqZc=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ePC9VibxcCF/I+ao+MS140M+hWdOqUfziQvHU0RyujoC1TpKDP8ul8NnkXctAp08t mCiT9Rt0PXD760G4i0UFNzOV8ZhRJDIjlNC1p/f5Cka7c+DZTQF9u8nfH41xa6l7vB wC/4X9FEoj4gImaWh1WesPEiAD7tZdI8+ieEGJ6I=
Received: from [192.168.255.120] (c-24-7-39-79.hsd1.ca.comcast.net [24.7.39.79]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 1604F216C47; Tue, 2 Apr 2013 00:37:15 +0000 (UTC) (envelope-from fobispo@isc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Francisco Obispo <fobispo@isc.org>
In-Reply-To: <19F54F2956911544A32543B8A9BDE0750982F68A@NICS-EXCH.sbg.nic.at>
Date: Mon, 1 Apr 2013 17:37:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A677006-518B-467A-B3C9-62481094A084@isc.org>
References: <19F54F2956911544A32543B8A9BDE0750982F68A@NICS-EXCH.sbg.nic.at>
To: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
X-Mailer: Apple Mail (2.1503)
Cc: Mark Hofstetter <mark.hofstetter@univie.ac.at>, "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] "resend" attribute in "deposit" element.
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, 02 Apr 2013 00:37:28 -0000

Hi Alexander,

Well, if we have a detached signature that can be used to verify the integrity of the file, why do we neep to record the 'retries'?

I support the idea of removing the 'resend' attribute from the deposit, and in fact, I would go further and remove it from the file name as well.

Francisco




On Mar 29, 2013, at 7:27 AM, Alexander Mayrhofer <alexander.mayrhofer@nic.at>; wrote:

> Hi,
> 
> We're in the late stages of implementing our escrow export script, and have discussed internally the purpose of the "resend" attribute in the "deposit" element itself. 
> 
> Reading through the definition, this attribute is not related to the *creation* of the escrow deposit, but rather to its *transport* (Our understanding is that the id attribute is more related to the creation of the file). 
> 
> More specifically, we don't see a reason why the "resend" attribute should actually be contained in the file itself, because failure to "send" the file to the Escrow provider is completely unrelated to the contents of the file. 
> 
> If a transport attempt fails, a registry should simply be able to rename the (successfully created, validated) escrow file, and just retry the *transport*, rather than the *creation*. However, since the "resend" attribute is included in the (compressed/encrypted/signed) file itself (in addition to the file name!), a failed *transport* attempt (eg. a interrupted upload) requires registries to essentially restart the generation:  modify the original escrow dump, and repeat the whole split/compress/encrypt/sign steps. 
> 
> We hence believe that the "resend" attribute should be removed from the definition of the "deposit" element. It is not only redundant (since it's also included in the file name itself), but its inclusion in the escrow content itself is actually misleading, and puts extra burden on the escrow process. *If* ICANN's intent with the "resend" attribute was to reflect whether a file has been re-*generated* (and not just re-*sent*), we propose to change the current structure as follows:
> 
> - Keep the "resend" part of the file names, and provide clear instructions that this number is to be increased when *transport* of the deposit failed, and is repeated with the identical file contents (retransmission).
> - Remove the "resend" attribute from the "deposit" element.
> - (Optionally) add a "revision" attribute to the "deposit" element, and provide clear instructions that the number contained in that attribute is to be increased when the *creation* of a deposit with an identical "id" is performed (re-generation).
> 
> Feedback appreciated
> 
> Alex
> 
> 
> _______________________________________________
> ire mailing list
> ire@ietf.org
> https://www.ietf.org/mailman/listinfo/ire

Francisco Obispo 
Director of Applications and Services - ISC
email: fobispo@isc.org
Phone: +1 650 423 1374 || INOC-DBA *3557* NOC
PGP KeyID = B38DB1BE