
From francisco.arias@icann.org  Wed Feb 10 23:59:44 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48C903A6FF9 for <ire@core3.amsl.com>; Wed, 10 Feb 2010 23:59:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzk4gki6oJ6E for <ire@core3.amsl.com>; Wed, 10 Feb 2010 23:59:43 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 98AF93A75C2 for <ire@ietf.org>; Wed, 10 Feb 2010 23:59:43 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 11 Feb 2010 00:00:56 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: "ire@ietf.org" <ire@ietf.org>
Date: Thu, 11 Feb 2010 00:00:54 -0800
Thread-Topic: High level requirements for Internet Registration Data Escrow
Thread-Index: Acqq8FWwAGeq6p6M7kO50P1uwtXJpg==
Message-ID: <C798F936.2427%francisco.arias@icann.org>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 11 Feb 2010 07:59:44 -0000

If we were to start from the beginning, i.e., the requirements; what do you
think about the list below as an starting point for high level requirements=
?

A solution for Internet Registration Data Escrow SHALL:

1. Define the format of Full and Incremental Deposits of Registration
Objects that a Registration Organization submits periodically to an
independent third party (the Escrow Agent) for its custody.

2. Allow a Registration Organization (different to the one making the
Deposits) to rebuild the Registration Services of the former in a timely
manner, with minimum harm to the users of those services (e.g., Registrants=
,
Registrars, Internet users, etc.) using only the Deposits from the Escrow
Agent.

3. Provide a format for Deposits with mechanisms that allow its
extensibility to accommodate new and extended Registration Objects.

4. Use authentication, confidentiality and integrity mechanisms when
transferring the Deposits to and from the Escrow Agent.

5. Support internationalization of "social" data (e.g., contact names,
addresses) in Registration Objects.

6. Identify parameters that are a matter of policy, e.g., frequency and typ=
e
of Deposits (Full or Incremental), the set of Registration Objects to
deposit, the time the Deposits have to be kept in custody.

Registration Organization would mean whatever we decide to be in our scope.
Looking horizontally: TLD registries, RIRs, routing registries; or
vertically: Registries, Registrars, Resellers, etc.

Regards,

__=20
Francisco



From paul.hoffman@vpnc.org  Thu Feb 11 08:20:21 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 135B13A7207 for <ire@core3.amsl.com>; Thu, 11 Feb 2010 08:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.032
X-Spam-Level: 
X-Spam-Status: No, score=-6.032 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5j3WJNSxfTO for <ire@core3.amsl.com>; Thu, 11 Feb 2010 08:20:19 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 1FB813A76F6 for <ire@ietf.org>; Thu, 11 Feb 2010 08:20:18 -0800 (PST)
Received: from [192.168.1.70] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o1BGL910026462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Feb 2010 09:21:11 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240847c799d957cff8@[192.168.1.70]>
In-Reply-To: <C798F936.2427%francisco.arias@icann.org>
References: <C798F936.2427%francisco.arias@icann.org>
Date: Thu, 11 Feb 2010 08:20:40 -0800
To: Francisco Arias <francisco.arias@icann.org>, "ire@ietf.org" <ire@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 11 Feb 2010 16:20:21 -0000

At 12:00 AM -0800 2/11/10, Francisco Arias wrote:
>If we were to start from the beginning, i.e., the requirements; what do you
>think about the list below as an starting point for high level requirements?
>
>A solution for Internet Registration Data Escrow SHALL:
>
>1. Define the format of Full and Incremental Deposits of Registration
>Objects that a Registration Organization submits periodically to an
>independent third party (the Escrow Agent) for its custody.

>From earlier comments on this list, it seems clear that there will be different views about what should and should not be in the deposits. Also, it seems likely that these formats are also useful for self-escrowing, not just with third-party agents. So, I think that should be:

Define a base format for Deposits of Registration Objects that a Registration Organization submits to an Escrow Agent for storage and possible later retrieval. The base format will have an extension mechanism for adding one or more sets of data to different types of Deposits.

>2. Allow a Registration Organization (different to the one making the
>Deposits) to rebuild the Registration Services of the former in a timely
>manner, with minimum harm to the users of those services (e.g., Registrants,
>Registrars, Internet users, etc.) using only the Deposits from the Escrow
>Agent.

What kind of "harm to the users" are you thinking of?

>3. Provide a format for Deposits with mechanisms that allow its
>extensibility to accommodate new and extended Registration Objects.

This should not be a second format; it needs to be part of the base format, as indicated above.

>4. Use authentication, confidentiality and integrity mechanisms when
>transferring the Deposits to and from the Escrow Agent.

There was not strong agreement that we should define the protocol for moving Deposits around. If a Deposit is a single blob, specifying a mandatory protocol is (typical IETF) overkill. For example, if we specify a client-server protocol, we need to specify how clients both push and pull Deposits from "servers" who really are supposed to mostly be repositories. Do I need to run this protocol just to store my own Deposit on a secured hard drive?

I strongly suggest we leave this item out completely.

>5. Support internationalization of "social" data (e.g., contact names,
>addresses) in Registration Objects.

This is way too limited in scope: *all* text data should be Unicode characters. The IETF would never produce a spec in 2010 without that, so I think it can either be left unsaid. If you really want to say this, append to the first item "All text data in a Deposit is encoded in UTF-8" and be done with it.

>6. Identify parameters that are a matter of policy, e.g., frequency and type
>of Deposits (Full or Incremental), the set of Registration Objects to
>deposit, the time the Deposits have to be kept in custody.

Why? Of what value would that be to the protocol?

>Registration Organization would mean whatever we decide to be in our scope.
>Looking horizontally: TLD registries, RIRs, routing registries; or
>vertically: Registries, Registrars, Resellers, etc.

This seems unnecessarily limited to the current ICANN model. How about "Registration Organizations include DNS zone administrators, IP address administrators, Internet route administrators, and businesses affiliated with them".

--Paul Hoffman, Director
--VPN Consortium

From bortzmeyer@nic.fr  Fri Feb 12 02:31:56 2010
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B6D53A74C7 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 02:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.24
X-Spam-Level: 
X-Spam-Status: No, score=-6.24 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4x+5HqOJYaI for <ire@core3.amsl.com>; Fri, 12 Feb 2010 02:31:55 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id 91DF13A6B82 for <ire@ietf.org>; Fri, 12 Feb 2010 02:31:55 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id E1B7D1C01A9; Fri, 12 Feb 2010 11:28:11 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id DD7141C0091; Fri, 12 Feb 2010 11:28:11 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay1.nic.fr (Postfix) with ESMTP id D1B0EA1D98A; Fri, 12 Feb 2010 11:28:11 +0100 (CET)
Date: Fri, 12 Feb 2010 11:28:11 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20100212102811.GA8849@nic.fr>
References: <C798F936.2427%francisco.arias@icann.org> <p06240847c799d957cff8@[192.168.1.70]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06240847c799d957cff8@[192.168.1.70]>
X-Operating-System: Debian GNU/Linux 5.0.4
X-Kernel: Linux 2.6.26-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 10:31:56 -0000

On Thu, Feb 11, 2010 at 08:20:40AM -0800,
 Paul Hoffman <paul.hoffman@vpnc.org> wrote 
 a message of 57 lines which said:

> I strongly suggest we leave this item [authentication,
> confidentiality and integrity mechanisms] out completely.

I strongly agree.
 
> This is way too limited in scope: *all* text data should be Unicode
> characters.

I also agree. Do note it conflicts with the current ICANN requirments
which say (why?) that the escrow of IDN must be done in ASCII :-(

From daniel@digsys.bg  Fri Feb 12 02:47:56 2010
Return-Path: <daniel@digsys.bg>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 121EB28C170 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 02:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_82=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EG+taoDFkvvQ for <ire@core3.amsl.com>; Fri, 12 Feb 2010 02:47:54 -0800 (PST)
Received: from relay2.digsys.bg (varna.digsys.bg [192.92.129.9]) by core3.amsl.com (Postfix) with ESMTP id 6E08028C161 for <ire@ietf.org>; Fri, 12 Feb 2010 02:47:54 -0800 (PST)
Received: from dcave.digsys.bg (daniel@dcave.digsys.bg [192.92.129.5]) by relay2.digsys.bg (8.14.3/8.14.3) with ESMTP id o1CAn9UQ018605 for <ire@ietf.org>; Fri, 12 Feb 2010 12:49:09 +0200 (EET) (envelope-from daniel@digsys.bg)
Message-ID: <4B753225.5050503@digsys.bg>
Date: Fri, 12 Feb 2010 12:49:09 +0200
From: Daniel Kalchev <daniel@digsys.bg>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100210 Thunderbird/3.0.1
MIME-Version: 1.0
To: ire@ietf.org
References: <C798F936.2427%francisco.arias@icann.org> <p06240847c799d957cff8@[192.168.1.70]>
In-Reply-To: <p06240847c799d957cff8@[192.168.1.70]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 10:47:56 -0000

On 11.02.10 18:20, Paul Hoffman wrote:
>> Registration Organization would mean whatever we decide to be in our scope.
>> Looking horizontally: TLD registries, RIRs, routing registries; or
>> vertically: Registries, Registrars, Resellers, etc.
>>      
> This seems unnecessarily limited to the current ICANN model. How about "Registration Organizations include DNS zone administrators, IP address administrators, Internet route administrators, and businesses affiliated with them".
>
>    
I would rather not limit the scope to even this list of organizations.

The escrow data format should ideally be suited for storing and 
retrieving arbitrary 'operational' and 'administrative' information. 
Example operational information would be the domain names and list of 
nameservers, DNSSEC keys etc, while administrative information would be 
all ownership, contact information etc. that is attributed to the 
operational information.. Perhaps there could be another type of 
information, sort of metadata to link them all.

Having the protocol usable outside 'internet registries' will make it 
more widely adopted in the internet-based business practice.

In my opinion, the more important consideration is whether the escrow 
protocol will be interactive, like EPP (which might just do the job), or 
more storage oriented. In the latter case the object format might well 
be opaque and understandable only to the specific source.

Daniel Kalchev
Register.BG

From Ed.Lewis@neustar.biz  Fri Feb 12 06:28:52 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3B2F3A7563 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 06:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.406
X-Spam-Level: 
X-Spam-Status: No, score=-2.406 tagged_above=-999 required=5 tests=[AWL=0.193,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9HQ0KdSNrA2 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 06:28:52 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id A324D3A756C for <ire@ietf.org>; Fri, 12 Feb 2010 06:28:49 -0800 (PST)
Received: from jbis-lt61.cis.neustar.com (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1CEU38K064947; Fri, 12 Feb 2010 09:30:03 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.200.127] by jbis-lt61.cis.neustar.com (PGP Universal service); Fri, 12 Feb 2010 09:30:05 -0500
X-PGP-Universal: processed; by jbis-lt61.cis.neustar.com on Fri, 12 Feb 2010 09:30:05 -0500
Mime-Version: 1.0
Message-Id: <a06240801c79b124487d0@[192.168.1.103]>
In-Reply-To: <C798F936.2427%francisco.arias@icann.org>
References: <C798F936.2427%francisco.arias@icann.org>
Date: Fri, 12 Feb 2010 09:15:59 -0500
To: "ire@ietf.org" <ire@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: ed.lewis@neustar.biz
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 14:28:52 -0000

At 0:00 -0800 2/11/10, Francisco Arias wrote:
>If we were to start from the beginning, i.e., the requirements; what do you
>think about the list below as an starting point for high level requirements?
>
>A solution for Internet Registration Data Escrow SHALL:
>

I would also extend escrow to include data used to operate Internet 
services, for example in an RIR: DNS, WhoIs, Billing, Registration, 
RWhoIs, IRIS, etc.

Where this comes from is the desire to reconstitute a registration 
entity's function by another in a timely manner.  Database schema and 
contents are vital, but there are other pieces of information needed.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From jaap@bartok.nlnetlabs.nl  Fri Feb 12 06:41:54 2010
Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 040DB3A7569 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 06:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.044
X-Spam-Level: 
X-Spam-Status: No, score=-2.044 tagged_above=-999 required=5 tests=[AWL=0.555,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5lYYIXh8+y1 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 06:41:49 -0800 (PST)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by core3.amsl.com (Postfix) with ESMTP id D44833A71D7 for <ire@ietf.org>; Fri, 12 Feb 2010 06:41:48 -0800 (PST)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id o1CEh1SC058797; Fri, 12 Feb 2010 15:43:01 +0100 (CET) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl>
To: Edward Lewis <Ed.Lewis@neustar.biz>
In-reply-to: <a06240801c79b124487d0@[192.168.1.103]> 
References: <C798F936.2427%francisco.arias@icann.org> <a06240801c79b124487d0@[192.168.1.103]>
Comments: In-reply-to Edward Lewis <Ed.Lewis@neustar.biz> message dated "Fri, 12 Feb 2010 09:15:59 -0500."
Date: Fri, 12 Feb 2010 15:43:01 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (bartok.nlnetlabs.nl [127.0.0.1]); Fri, 12 Feb 2010 15:43:01 +0100 (CET)
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 14:41:54 -0000

    
    Where this comes from is the desire to reconstitute a registration 
    entity's function by another in a timely manner.  Database schema and 
    contents are vital, but there are other pieces of information needed.
    
Ideally it would also include  (non-standard) applications used by
the registry, specific configuration files etc.

	jaap

From bortzmeyer@nic.fr  Fri Feb 12 07:03:32 2010
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3B993A76FE for <ire@core3.amsl.com>; Fri, 12 Feb 2010 07:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.24
X-Spam-Level: 
X-Spam-Status: No, score=-6.24 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcH6IdaVmv9b for <ire@core3.amsl.com>; Fri, 12 Feb 2010 07:03:31 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id C30333A76EF for <ire@ietf.org>; Fri, 12 Feb 2010 07:03:31 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 753FD1C01B0; Fri, 12 Feb 2010 15:59:48 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 6FFB31C01AF; Fri, 12 Feb 2010 15:59:48 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay1.nic.fr (Postfix) with ESMTP id 642DCA1D9C9; Fri, 12 Feb 2010 15:59:48 +0100 (CET)
Date: Fri, 12 Feb 2010 15:59:48 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>
Message-ID: <20100212145948.GA14630@nic.fr>
References: <C798F936.2427%francisco.arias@icann.org> <a06240801c79b124487d0@[192.168.1.103]> <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl>
X-Operating-System: Debian GNU/Linux 5.0.4
X-Kernel: Linux 2.6.26-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 15:03:32 -0000

On Fri, Feb 12, 2010 at 03:43:01PM +0100,
 Jaap Akkerhuis <jaap@NLnetLabs.nl> wrote 
 a message of 13 lines which said:

> Ideally it would also include (non-standard) applications used by
> the registry,

And the Oracle licence used by the previous registry :-)

From daniel@digsys.bg  Fri Feb 12 07:49:59 2010
Return-Path: <daniel@digsys.bg>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B78EB3A737D for <ire@core3.amsl.com>; Fri, 12 Feb 2010 07:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MeSdYuJV5M1U for <ire@core3.amsl.com>; Fri, 12 Feb 2010 07:49:59 -0800 (PST)
Received: from relay2.digsys.bg (varna.digsys.bg [192.92.129.9]) by core3.amsl.com (Postfix) with ESMTP id 8F37E3A6ED9 for <ire@ietf.org>; Fri, 12 Feb 2010 07:49:58 -0800 (PST)
Received: from dcave.digsys.bg (daniel@dcave.digsys.bg [192.92.129.5]) by relay2.digsys.bg (8.14.3/8.14.3) with ESMTP id o1CFpFuc031367 for <ire@ietf.org>; Fri, 12 Feb 2010 17:51:15 +0200 (EET) (envelope-from daniel@digsys.bg)
Message-ID: <4B7578F3.6000209@digsys.bg>
Date: Fri, 12 Feb 2010 17:51:15 +0200
From: Daniel Kalchev <daniel@digsys.bg>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100210 Thunderbird/3.0.1
MIME-Version: 1.0
To: ire@ietf.org
References: <C798F936.2427%francisco.arias@icann.org>	<a06240801c79b124487d0@[192.168.1.103]>	<201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl> <20100212145948.GA14630@nic.fr>
In-Reply-To: <20100212145948.GA14630@nic.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 15:49:59 -0000

On 12.02.10 16:59, Stephane Bortzmeyer wrote:
> And the Oracle licence used by the previous registry :-)
This may be serious security issue -- Internet registries might be 
destroyed for their software licenses. :)

Is there portable way to store applications? Not with their intended 
hardware, I hope.

How about the documentation needed to operate the software? Processes 
flowcharts..

Daniel

From paul.hoffman@vpnc.org  Fri Feb 12 10:13:07 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 894AC3A7734 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 10:13:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.033
X-Spam-Level: 
X-Spam-Status: No, score=-6.033 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WNWrT5NVuMVV for <ire@core3.amsl.com>; Fri, 12 Feb 2010 10:13:05 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id BB42E3A7445 for <ire@ietf.org>; Fri, 12 Feb 2010 10:13:04 -0800 (PST)
Received: from [75.101.18.87] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o1CIEM2Y012538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ire@ietf.org>; Fri, 12 Feb 2010 11:14:23 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624081dc79b48f85e8f@[75.101.18.87]>
In-Reply-To: <4B753225.5050503@digsys.bg> <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl> <20100212102811.GA8849@nic.fr> <20100212145948.GA14630@nic.fr> <a06240801c79b124487d0@[192.168.1.103]> <4B7578F3.6000209@digsys.bg>
References: <C798F936.2427%francisco.arias@icann.org> <p06240847c799d957cff8@[192.168.1.70]> <4B753225.5050503@digsys.bg> <C798F936.2427%francisco.arias@icann.org> <a06240801c79b124487d0@[192.168.1.103]> <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl> <C798F936.2427%francisco.arias@icann.org> <p06240847c799d957cff8@[192.168.1.70]> <20100212102811.GA8849@nic.fr> <20100212145948.GA14630@nic.fr> <C798F936.2427%francisco.arias@icann.org> <a06240801c79b124487d0@[192.168.1.103]> <C798F936.2427%francisco.arias@icann.org> <a06240801c79b124487d0@[192.168.1.103]> <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl> <20100212145948.GA14630@nic.fr> <4B7578F3.6000209@digsys.bg>
Date: Fri, 12 Feb 2010 10:14:20 -0800
To: "ire@ietf.org" <ire@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 18:13:07 -0000

At 11:28 AM +0100 2/12/10, Stephane Bortzmeyer wrote:
> > This is way too limited in scope: *all* text data should be Unicode
>> characters.
>
>I also agree. Do note it conflicts with the current ICANN requirments
>which say (why?) that the escrow of IDN must be done in ASCII :-(

This conflict is a non-issue. If one user of the registry wants to make more restriction in their profiles, they can.

At 12:49 PM +0200 2/12/10, Daniel Kalchev wrote:
>On 11.02.10 18:20, Paul Hoffman wrote:
>>>Registration Organization would mean whatever we decide to be in our scope.
>>>Looking horizontally: TLD registries, RIRs, routing registries; or
>>...snip...
>>... include DNS zone administrators, IP address administrators, Internet route administrators, and businesses affiliated with them".
>
>I would rather not limit the scope to even this list of organizations.

I support widening beyond my list, but not too far. There is no such thing as "generic escrow".

>The escrow data format should ideally be suited for storing and retrieving arbitrary 'operational' and 'administrative' information. Example operational information would be the domain names and list of nameservers, DNSSEC keys etc, while administrative information would be all ownership, contact information etc. that is attributed to the operational information..

Fully agree. This is precisely why I want the extensibility to be in the primary requirement.

> Perhaps there could be another type of information, sort of metadata to link them all.

That would be the schema.

>Having the protocol usable outside 'internet registries' will make it more widely adopted in the internet-based business practice.

But having a base spec that is too generic will prevent it from being useful to the core audience. We can't know ahead of time which way to tip the balance.

>In my opinion, the more important consideration is whether the escrow protocol will be interactive, like EPP (which might just do the job), or more storage oriented. In the latter case the object format might well be opaque and understandable only to the specific source.

My preference is towards storage-oriented because all interactive protocols impose access policies, and we have no idea to what extent the escrow agents want to (or are allowed to!) release the data they are storing. But having an "opaque format" is silly: we already have those now.

At 3:43 PM +0100 2/12/10, Jaap Akkerhuis wrote:
>Ideally it would also include  (non-standard) applications used by
>the registry, specific configuration files etc.

Absolutely.

--Paul Hoffman, Director
--VPN Consortium

From Ed.Lewis@neustar.biz  Fri Feb 12 11:27:44 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B99673A787A for <ire@core3.amsl.com>; Fri, 12 Feb 2010 11:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVfy5FZpNjdc for <ire@core3.amsl.com>; Fri, 12 Feb 2010 11:27:44 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id D015C3A7736 for <ire@ietf.org>; Fri, 12 Feb 2010 11:27:43 -0800 (PST)
Received: from jbis-lt61.cis.neustar.com (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1CJSvNC067283; Fri, 12 Feb 2010 14:28:58 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.200.127] by jbis-lt61.cis.neustar.com (PGP Universal service); Fri, 12 Feb 2010 14:29:03 -0500
X-PGP-Universal: processed; by jbis-lt61.cis.neustar.com on Fri, 12 Feb 2010 14:29:03 -0500
Mime-Version: 1.0
Message-Id: <a06240802c79b5b7b13ca@[10.31.200.127]>
In-Reply-To: <20100212145948.GA14630@nic.fr>
References: <C798F936.2427%francisco.arias@icann.org> <a06240801c79b124487d0@[192.168.1.103]> <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl> <20100212145948.GA14630@nic.fr>
Date: Fri, 12 Feb 2010 14:28:56 -0500
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, Jaap Akkerhuis <jaap@NLnetLabs.nl>, "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 19:27:44 -0000

At 15:59 +0100 2/12/10, Stephane Bortzmeyer wrote:
>On Fri, Feb 12, 2010 at 03:43:01PM +0100,
>  Jaap Akkerhuis <jaap@NLnetLabs.nl> wrote
>  a message of 13 lines which said:
>
>>  Ideally it would also include (non-standard) applications used by
>>  the registry,
>
>And the Oracle licence used by the previous registry :-)

In an ideal world, whether one registry uses commercial database 
product one and the other uses schools of trained dolphins, it 
shouldn't matter so long as the registration activity can be 
supported from escrow.  (Ok, in an ideal world, the dolphins will be 
feeding us fish for swimming through hoops.)
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From cbbrowne@ca.afilias.info  Fri Feb 12 12:35:06 2010
Return-Path: <cbbrowne@ca.afilias.info>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B6F628C203 for <ire@core3.amsl.com>; Fri, 12 Feb 2010 12:35:06 -0800 (PST)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAf7K5fNlUOo for <ire@core3.amsl.com>; Fri, 12 Feb 2010 12:35:05 -0800 (PST)
Received: from tor-gateway.afilias.info (tor-gateway.afilias.info [199.15.87.4]) by core3.amsl.com (Postfix) with ESMTP id 4CE3428C202 for <ire@ietf.org>; Fri, 12 Feb 2010 12:35:05 -0800 (PST)
Received: from [10.10.68.46] (helo=dba2.int.libertyrms.com ident=postfix) by tor-gateway.afilias.info with smtp (Exim 4.69) (envelope-from <cbbrowne@ca.afilias.info>) id 1Ng2FI-0006bz-7g; Fri, 12 Feb 2010 15:36:12 -0500
Received: by dba2.int.libertyrms.com (Postfix, from userid 1000) id 50C9986C042; Fri, 12 Feb 2010 15:36:12 -0500 (EST)
From: Christopher Browne <cbbrowne@ca.afilias.info>
To: Edward Lewis <Ed.Lewis@neustar.biz>
Organization: Afilias Canada - Architecture Department
References: <C798F936.2427%francisco.arias@icann.org> <a06240801c79b124487d0@[192.168.1.103]> <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl> <20100212145948.GA14630@nic.fr> <a06240802c79b5b7b13ca@[10.31.200.127]>
Date: Fri, 12 Feb 2010 15:36:12 -0500
In-Reply-To: <a06240802c79b5b7b13ca@[10.31.200.127]> (Edward Lewis's message of "Fri\, 12 Feb 2010 14\:28\:56 -0500")
Message-ID: <87wryi8a4j.fsf@ca.afilias.info>
User-Agent: Gnus/5.110009 (No Gnus v0.9) XEmacs/21.4.22 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 12 Feb 2010 20:35:06 -0000

Edward Lewis <Ed.Lewis@neustar.biz> writes:
> At 15:59 +0100 2/12/10, Stephane Bortzmeyer wrote:
>>On Fri, Feb 12, 2010 at 03:43:01PM +0100,
>>  Jaap Akkerhuis <jaap@NLnetLabs.nl> wrote
>>  a message of 13 lines which said:
>>
>>>  Ideally it would also include (non-standard) applications used by
>>>  the registry,
>>
>>And the Oracle licence used by the previous registry :-)
>
> In an ideal world, whether one registry uses commercial database
> product one and the other uses schools of trained dolphins, it
> shouldn't matter so long as the registration activity can be supported
> from escrow.  (Ok, in an ideal world, the dolphins will be feeding us
> fish for swimming through hoops.)

This points at the important point that the format be abstracted enough
away from the deepest darkest details of the activity, whether those be
software licenses, billing policies, or whatever else.

It seems to me that it's a mighty good thing to abstract things enough
that the form is NOT shackled to be identical to individual
implementations.

This may mean that the data carried over gets carried in a rather
"lossy" fashion.

It's legitimate to feel some discomfort about that - but if I was taking
over a registry, I'd be uncomfortable with having every bit of legacy
policy forced on my implementation.  It's a good thing to lose some of
the mistakes, especially if they contributed to the failure.
-- 
output = reverse("ofni.sailifa.ac" "@" "enworbbc")
Christopher Browne
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"

From francisco.arias@icann.org  Mon Feb 15 02:02:59 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1842428C199 for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.656
X-Spam-Level: 
X-Spam-Status: No, score=-5.656 tagged_above=-999 required=5 tests=[AWL=-0.916, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BUEJ6hOQ6ej for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:02:58 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 101F828C197 for <ire@ietf.org>; Mon, 15 Feb 2010 02:02:58 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 15 Feb 2010 02:04:27 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "ire@ietf.org" <ire@ietf.org>
Date: Mon, 15 Feb 2010 02:04:20 -0800
Thread-Topic: [ire] High level requirements for Internet Registration Data Escrow
Thread-Index: AcqrNkaaGxoRIyujRPuUb5fMbQrfqwC7/cMB
Message-ID: <C79E5C24.2544%francisco.arias@icann.org>
In-Reply-To: <p06240847c799d957cff8@[192.168.1.70]>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:02:59 -0000

On 2/11/10 8:20 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
> At 12:00 AM -0800 2/11/10, Francisco Arias wrote:
>> 2. Allow a Registration Organization (different to the one making the
>> Deposits) to rebuild the Registration Services of the former in a timely
>> manner, with minimum harm to the users of those services (e.g., Registra=
nts,
>> Registrars, Internet users, etc.) using only the Deposits from the Escro=
w
>> Agent.
>=20
> What kind of "harm to the users" are you thinking of?

Basically loss of service, but also malfunction ... caused by missing,
incomplete or simply unintelligible data in the Escrow Deposits.
=20
>> 3. Provide a format for Deposits with mechanisms that allow its
>> extensibility to accommodate new and extended Registration Objects.
>=20
> This should not be a second format; it needs to be part of the base forma=
t, as
> indicated above.

I didn't mean there should be two formats. I guess I didn't expressed it
correctly. I agree with you, Paul, it should be and extensible format,
that's it.

>> 5. Support internationalization of "social" data (e.g., contact names,
>> addresses) in Registration Objects.
>=20
> This is way too limited in scope: *all* text data should be Unicode
> characters. The IETF would never produce a spec in 2010 without that, so =
I
> think it can either be left unsaid. If you really want to say this, appen=
d to
> the first item "All text data in a Deposit is encoded in UTF-8" and be do=
ne
> with it.

ok
=20
>> 6. Identify parameters that are a matter of policy, e.g., frequency and =
type
>> of Deposits (Full or Incremental), the set of Registration Objects to
>> deposit, the time the Deposits have to be kept in custody.
>=20
> Why? Of what value would that be to the protocol?

Not to the protocol, but to the implementers. I believe the spec should
indentify parameters that are matter of policy so the implementers of a
"Data Escrow engagement" (e.g., ICANN, a registry, an Escrow Agent) would
know a list of parameters they need to define to have something actually
usable.

__=20
Francisco



From francisco.arias@icann.org  Mon Feb 15 02:03:01 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B92828C1A5 for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.433
X-Spam-Level: 
X-Spam-Status: No, score=-6.433 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0rQH6RdH6Vbk for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:03:00 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 9A22928B56A for <ire@ietf.org>; Mon, 15 Feb 2010 02:03:00 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 15 Feb 2010 02:04:30 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Edward Lewis <Ed.Lewis@neustar.biz>, "ire@ietf.org" <ire@ietf.org>
Date: Mon, 15 Feb 2010 02:04:28 -0800
Thread-Topic: [ire] High level requirements for Internet Registration Data Escrow
Thread-Index: Acqr7/KMT/9fI5BCRmSDHBXDUFIX1ACNk/jh
Message-ID: <C79E5C2C.2544%francisco.arias@icann.org>
In-Reply-To: <a06240801c79b124487d0@[192.168.1.103]>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:03:01 -0000

On 2/12/10 6:15 AM, "Edward Lewis" <Ed.Lewis@neustar.biz> wrote:

> At 0:00 -0800 2/11/10, Francisco Arias wrote:
>> If we were to start from the beginning, i.e., the requirements; what do =
you
>> think about the list below as an starting point for high level requireme=
nts?
>>=20
>> A solution for Internet Registration Data Escrow SHALL:
>=20
> I would also extend escrow to include data used to operate Internet
> services, for example in an RIR: DNS, WhoIs, Billing, Registration,
> RWhoIs, IRIS, etc.

I agree.

> Where this comes from is the desire to reconstitute a registration
> entity's function by another in a timely manner.  Database schema and
> contents are vital, but there are other pieces of information needed.

Ed, what other pieces of information?

__=20
Francisco


From francisco.arias@icann.org  Mon Feb 15 02:03:01 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74D4A28B56A for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.457
X-Spam-Level: 
X-Spam-Status: No, score=-6.457 tagged_above=-999 required=5 tests=[AWL=0.142,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvGPEQsNEigv for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:03:00 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id B1DBA28C197 for <ire@ietf.org>; Mon, 15 Feb 2010 02:03:00 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Mon, 15 Feb 2010 02:04:30 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>
Date: Mon, 15 Feb 2010 02:04:24 -0800
Thread-Topic: [ire] High level requirements for Internet Registration Data Escrow
Thread-Index: Acqr8cNthg3TTjkLSBqqm0VdUEhQTACNHyft
Message-ID: <C79E5C28.2544%francisco.arias@icann.org>
In-Reply-To: <201002121443.o1CEh1SC058797@bartok.nlnetlabs.nl>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:03:01 -0000

On 2/12/10 6:43 AM, "Jaap Akkerhuis" <jaap@NLnetLabs.nl> wrote:
>   =20
>>     Where this comes from is the desire to reconstitute a registration
>>     entity's function by another in a timely manner.  Database schema an=
d
>>     contents are vital, but there are other pieces of information needed=
.
>   =20
> Ideally it would also include  (non-standard) applications used by
> the registry, specific configuration files etc.

Jaap, what do you mean by including applications used by the registry?

__=20
Francisco


From francisco.arias@icann.org  Mon Feb 15 02:04:11 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25D563A682F for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yA7q8kceAqUp for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:10 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 77D583A67DB for <ire@ietf.org>; Mon, 15 Feb 2010 02:04:10 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Mon, 15 Feb 2010 02:05:40 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Daniel Kalchev <daniel@digsys.bg>
Date: Mon, 15 Feb 2010 02:05:38 -0800
Thread-Topic: Interactive vs. storage-oriented protocol
Thread-Index: AcqsD0bLSRY5Zr3jT0mrwMsYUUTFoQCFyVc/
Message-ID: <C79E5C72.2547%francisco.arias@icann.org>
In-Reply-To: <p0624081dc79b48f85e8f@[75.101.18.87]>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: [ire] Interactive vs. storage-oriented protocol
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:04:11 -0000

On 2/12/10 10:14 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
> At 12:49 PM +0200 2/12/10, Daniel Kalchev wrote:
>> In my opinion, the more important consideration is whether the escrow
>> protocol will be interactive, like EPP (which might just do the job), or=
 more
>> storage oriented. In the latter case the object format might well be opa=
que
>> and understandable only to the specific source.
>=20
> My preference is towards storage-oriented because all interactive protoco=
ls
> impose access policies, and we have no idea to what extent the escrow age=
nts
> want to (or are allowed to!) release the data they are storing. But havin=
g an
> "opaque format" is silly: we already have those now.

I agree with Paul, storage-oriented makes more sense for Data Escrow. It
solves the problem and it is much more easier to implement than interactive=
.

I also agree about the format, it has to be pre-defined (vs. opaque) to
allow a different organization to rebuild the services of the original
organization without help from it.

__=20
Francisco


From francisco.arias@icann.org  Mon Feb 15 02:04:33 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31BF228C104 for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.488
X-Spam-Level: 
X-Spam-Status: No, score=-6.488 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qCK17TP9cjsU for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:32 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 79EFA28B56A for <ire@ietf.org>; Mon, 15 Feb 2010 02:04:32 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 15 Feb 2010 02:06:02 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Daniel Kalchev <daniel@digsys.bg>
Date: Mon, 15 Feb 2010 02:05:58 -0800
Thread-Topic: Scope of Registration Organization
Thread-Index: AcqsD0bLSRY5Zr3jT0mrwMsYUUTFoQCFzFLg
Message-ID: <C79E5C86.2547%francisco.arias@icann.org>
In-Reply-To: <p0624081dc79b48f85e8f@[75.101.18.87]>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: [ire] Scope of Registration Organization
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:04:33 -0000

On 2/12/10 10:14 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
>
> At 12:49 PM +0200 2/12/10, Daniel Kalchev wrote:
>> On 11.02.10 18:20, Paul Hoffman wrote:
>>>> Registration Organization would mean whatever we decide to be in our s=
cope.
>>>> Looking horizontally: TLD registries, RIRs, routing registries; or
>>> ...snip...
>>> ... include DNS zone administrators, IP address administrators, Interne=
t
>>> route administrators, and businesses affiliated with them".
>>=20
>> I would rather not limit the scope to even this list of organizations.
>=20
> I support widening beyond my list, but not too far. There is no such thin=
g as
> "generic escrow".

In principle I agree we have to somewhat limit the type of organizations
that may find useful the spec but I do not know how to describe that. Do yo=
u
have an idea Paul?

__=20
Francisco


From francisco.arias@icann.org  Mon Feb 15 02:04:46 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E38328C1A3 for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kdLRT6KH+uBB for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:45 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 7BD1B28C1A5 for <ire@ietf.org>; Mon, 15 Feb 2010 02:04:45 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Mon, 15 Feb 2010 02:06:15 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date: Mon, 15 Feb 2010 02:06:11 -0800
Thread-Topic: Authentication, confidentiality and integrity
Thread-Index: AcqrNkaaGxoRIyujRPuUb5fMbQrfqwC8Dk7j
Message-ID: <C79E5C93.2547%francisco.arias@icann.org>
In-Reply-To: <p06240847c799d957cff8@[192.168.1.70]>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: [ire] Authentication, confidentiality and integrity
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:04:46 -0000

On 2/11/10 8:20 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
>
> At 12:00 AM -0800 2/11/10, Francisco Arias wrote:
>> 4. Use authentication, confidentiality and integrity mechanisms when
>> transferring the Deposits to and from the Escrow Agent.
>=20
> There was not strong agreement that we should define the protocol for mov=
ing
> Deposits around. If a Deposit is a single blob, specifying a mandatory
> protocol is (typical IETF) overkill. For example, if we specify a
> client-server protocol, we need to specify how clients both push and pull
> Deposits from "servers" who really are supposed to mostly be repositories=
. Do
> I need to run this protocol just to store my own Deposit on a secured har=
d
> drive?
>=20
> I strongly suggest we leave this item out completely.
>
On 2/12/10 2:28 AM, "Stephane Bortzmeyer" <bortzmeyer@nic.fr> wrote:
>
> I strongly agree.

I didn't mean to specify a transport protocol for the Deposits and yes, I
agree that transporting a physical media to the Escrow Agent is a
possibility we need to consider.

What I tried to say is that the spec has to define something the involved
parties (registries and Escrow Agent) have to do in order to authenticate
that the information comes from the right party, it is only readable by
whomever is authorized (e.g., the Escrow Agent) and that the Deposits are a=
s
the depositing registry produced them.

For example, the spec could require the Deposits to be digitally signed and
encrypted.

__=20
Francisco


From francisco.arias@icann.org  Mon Feb 15 02:04:56 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4418A3A682F for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yx+zygSvJGQ8 for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:04:55 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 78AD93A67DB for <ire@ietf.org>; Mon, 15 Feb 2010 02:04:55 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 15 Feb 2010 02:06:25 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Christopher Browne <cbbrowne@ca.afilias.info>, Edward Lewis <Ed.Lewis@neustar.biz>
Date: Mon, 15 Feb 2010 02:06:22 -0800
Thread-Topic: Abstraction of the data
Thread-Index: AcqsIxtbPgSMNhuyTdKSxFHMMNkabACA2sGp
Message-ID: <C79E5C9E.2548%francisco.arias@icann.org>
In-Reply-To: <87wryi8a4j.fsf@ca.afilias.info>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: [ire] Abstraction of the data
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:04:56 -0000

On 2/12/10 12:36 PM, "Christopher Browne" <cbbrowne@ca.afilias.info> wrote:
> Edward Lewis <Ed.Lewis@neustar.biz> writes:
>> At 15:59 +0100 2/12/10, Stephane Bortzmeyer wrote:
>>> On Fri, Feb 12, 2010 at 03:43:01PM +0100,
>>>  Jaap Akkerhuis <jaap@NLnetLabs.nl> wrote
>>>  a message of 13 lines which said:
>>>=20
>>>>  Ideally it would also include (non-standard) applications used by
>>>>  the registry,
>>>=20
>>> And the Oracle licence used by the previous registry :-)
>>=20
>> In an ideal world, whether one registry uses commercial database
>> product one and the other uses schools of trained dolphins, it
>> shouldn't matter so long as the registration activity can be supported
>> from escrow.  (Ok, in an ideal world, the dolphins will be feeding us
>> fish for swimming through hoops.)
>=20
> This points at the important point that the format be abstracted enough
> away from the deepest darkest details of the activity, whether those be
> software licenses, billing policies, or whatever else.
>=20
> It seems to me that it's a mighty good thing to abstract things enough
> that the form is NOT shackled to be identical to individual
> implementations.

I agree with Christopher, the definition of the objects comprising the data
should be abstract and implementation independent; we should care about the
data needed to run the services not about the way they used to be run.

__=20
Francisco


From bortzmeyer@nic.fr  Mon Feb 15 02:36:52 2010
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB1373A7B40 for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.241
X-Spam-Level: 
X-Spam-Status: No, score=-6.241 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UsPL-9nNNdfX for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:36:52 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id CBCC23A68E9 for <ire@ietf.org>; Mon, 15 Feb 2010 02:36:51 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 0A0201C0022; Mon, 15 Feb 2010 11:33:16 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 057301C0020; Mon, 15 Feb 2010 11:33:16 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay1.nic.fr (Postfix) with ESMTP id 03546A1DA30; Mon, 15 Feb 2010 11:33:16 +0100 (CET)
Date: Mon, 15 Feb 2010 11:33:16 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Francisco Arias <francisco.arias@icann.org>
Message-ID: <20100215103315.GA14067@nic.fr>
References: <p06240847c799d957cff8@[192.168.1.70]> <C79E5C93.2547%francisco.arias@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C79E5C93.2547%francisco.arias@icann.org>
X-Operating-System: Debian GNU/Linux 5.0.4
X-Kernel: Linux 2.6.26-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: ire@ietf.org
Subject: Re: [ire] Authentication, confidentiality and integrity
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:36:52 -0000

On Mon, Feb 15, 2010 at 02:06:11AM -0800,
 Francisco Arias <francisco.arias@icann.org> wrote 
 a message of 39 lines which said:

> What I tried to say is that the spec has to define something the
> involved parties (registries and Escrow Agent) have to do in order
> to authenticate that the information comes from the right party,

No, I disagree. The spec has to explain (that's a good idea for the
Security Considerations section) what are the risks associated with
the transport and the possible solutions. But not to mandate a
specific solution.

As you said, "I believe the spec should indentify parameters that are
matter of policy so the implementers of a "Data Escrow engagement"
(e.g., ICANN, a registry, an Escrow Agent) would know a list of
parameters they need to define to have something actually usable."

> For example, the spec could require the Deposits to be digitally
> signed and encrypted.

Overspecification. I suggest instead a Security Considerations section
with something like:

The escrowed data could be read in transit by unauthorized
third-parties. If it is an issue, a possible solution is to encrypt
the escrowed data for the transport, using solutions like [RFC 4301]
or [RFC 5246].

It is important for the Escrow Agent to check that the escrowed data
is really the authentic one. The Agent may consider the use of digital
signatures like in [RFC 4880].

From jaap@bartok.nlnetlabs.nl  Mon Feb 15 02:49:36 2010
Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6FDD3A7B48 for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.229
X-Spam-Level: 
X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4xnNaeGyoCkK for <ire@core3.amsl.com>; Mon, 15 Feb 2010 02:49:36 -0800 (PST)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by core3.amsl.com (Postfix) with ESMTP id 3E9643A7B46 for <ire@ietf.org>; Mon, 15 Feb 2010 02:49:33 -0800 (PST)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id o1FAowUD043502 for <ire@ietf.org>; Mon, 15 Feb 2010 11:50:58 +0100 (CET) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201002151050.o1FAowUD043502@bartok.nlnetlabs.nl>
To: "ire@ietf.org" <ire@ietf.org>
In-reply-to: <C79E5C28.2544%francisco.arias@icann.org> 
References: <C79E5C28.2544%francisco.arias@icann.org>
Comments: In-reply-to Francisco Arias <francisco.arias@icann.org> message dated "Mon, 15 Feb 2010 02:04:24 -0800."
Date: Mon, 15 Feb 2010 11:50:58 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (bartok.nlnetlabs.nl [127.0.0.1]); Mon, 15 Feb 2010 11:50:58 +0100 (CET)
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 15 Feb 2010 10:49:36 -0000

    >    
    > Ideally it would also include  (non-standard) applications used by
    > the registry, specific configuration files etc.
    
    Jaap, what do you mean by including applications used by the registry?
    
As quoted above, I said none-standard applications. Lot's of TLDs
have requirements to the registration process which are beyond what
is needed for running a nameserver and register a name. Things that
deal with what that Ed calls "other pieces of information needed".

I one wants to restore a registry from the escrowed data and not
change the operation that piece is needed as well.

	jaap

From francisco.arias@icann.org  Tue Feb 16 08:09:03 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 579C23A6A2F for <ire@core3.amsl.com>; Tue, 16 Feb 2010 08:09:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7ezfiJOX8RG for <ire@core3.amsl.com>; Tue, 16 Feb 2010 08:09:02 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id A896A3A6906 for <ire@ietf.org>; Tue, 16 Feb 2010 08:09:02 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Tue, 16 Feb 2010 08:10:37 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date: Tue, 16 Feb 2010 08:10:36 -0800
Thread-Topic: Authentication, confidentiality and integrity
Thread-Index: AcquKlZIt9dTgJ7qTweRPDmPyhwb5AA+DyDN
Message-ID: <C7A0037C.259D%francisco.arias@icann.org>
In-Reply-To: <20100215103315.GA14067@nic.fr>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] Authentication, confidentiality and integrity
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 16 Feb 2010 16:09:03 -0000

On 2/15/10 2:33 AM, "Stephane Bortzmeyer" <bortzmeyer@nic.fr> wrote:

> On Mon, Feb 15, 2010 at 02:06:11AM -0800,
>  Francisco Arias <francisco.arias@icann.org> wrote
>  a message of 39 lines which said:
>=20
>> What I tried to say is that the spec has to define something the
>> involved parties (registries and Escrow Agent) have to do in order
>> to authenticate that the information comes from the right party,
>=20
> No, I disagree. The spec has to explain (that's a good idea for the
> Security Considerations section) what are the risks associated with
> the transport and the possible solutions. But not to mandate a
> specific solution.
>
> As you said, "I believe the spec should indentify parameters that are
> matter of policy so the implementers of a "Data Escrow engagement"
> (e.g., ICANN, a registry, an Escrow Agent) would know a list of
> parameters they need to define to have something actually usable."

Why not?=20

I understand your point about policy parameters, but I think the question o=
f
the confidentiality, integrity and authenticity of the information involved
in Data Escrow is of such importance that a solution has to be specified.

__=20
Francisco


From francisco.arias@icann.org  Tue Feb 16 08:16:21 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52C1928C275 for <ire@core3.amsl.com>; Tue, 16 Feb 2010 08:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8H1jHduQzKU for <ire@core3.amsl.com>; Tue, 16 Feb 2010 08:16:20 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 6FB6728C1FB for <ire@ietf.org>; Tue, 16 Feb 2010 08:16:20 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Tue, 16 Feb 2010 08:17:55 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>, "ire@ietf.org" <ire@ietf.org>
Date: Tue, 16 Feb 2010 08:17:52 -0800
Thread-Topic: [ire] High level requirements for Internet Registration Data Escrow
Thread-Index: AcquLNX6rsCduwCIS9KTeyyw8awefQA9sCzS
Message-ID: <C7A00530.25A1%francisco.arias@icann.org>
In-Reply-To: <201002151050.o1FAowUD043502@bartok.nlnetlabs.nl>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 16 Feb 2010 16:16:21 -0000

On 2/15/10 2:50 AM, "Jaap Akkerhuis" <jaap@NLnetLabs.nl> wrote:
>>  =20
>> Ideally it would also include (non-standard) applications used by
>> the registry, specific configuration files etc.
>   =20
>     Jaap, what do you mean by including applications used by the registry=
?
>   =20
> As quoted above, I said none-standard applications. Lot's of TLDs
> have requirements to the registration process which are beyond what
> is needed for running a nameserver and register a name. Things that
> deal with what that Ed calls "other pieces of information needed".
>=20
> I one wants to restore a registry from the escrowed data and not
> change the operation that piece is needed as well.

Do you mean extra data (wrt EPP schemas) required by some registries in
order to accept a registration (e.g., identity document number) or data
needed to run services different to basic DNS resolution (e.g., directory
information like in .TEL)?

__=20
Francisco


From jaap@bartok.nlnetlabs.nl  Wed Feb 17 03:14:24 2010
Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A779528C1F5 for <ire@core3.amsl.com>; Wed, 17 Feb 2010 03:14:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level: 
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KYca27HQ91MW for <ire@core3.amsl.com>; Wed, 17 Feb 2010 03:14:02 -0800 (PST)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by core3.amsl.com (Postfix) with ESMTP id C51273A7CC3 for <ire@ietf.org>; Wed, 17 Feb 2010 03:14:00 -0800 (PST)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id o1HBFXjU086431 for <ire@ietf.org>; Wed, 17 Feb 2010 12:15:33 +0100 (CET) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201002171115.o1HBFXjU086431@bartok.nlnetlabs.nl>
To: "ire@ietf.org" <ire@ietf.org>
In-reply-to: <C7A00530.25A1%francisco.arias@icann.org> 
References: <C7A00530.25A1%francisco.arias@icann.org>
Comments: In-reply-to Francisco Arias <francisco.arias@icann.org> message dated "Tue, 16 Feb 2010 08:17:52 -0800."
Date: Wed, 17 Feb 2010 12:15:33 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (bartok.nlnetlabs.nl [127.0.0.1]); Wed, 17 Feb 2010 12:15:33 +0100 (CET)
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 17 Feb 2010 11:14:25 -0000

    
    Do you mean extra data (wrt EPP schemas) required by some registries in
    order to accept a registration (e.g., identity document number) or data
    needed to run services different to basic DNS resolution (e.g., directory
    information like in .TEL)?

Both. Whatever is needed to reconstitute the registry to it's
original state (I made the remark in that context) and function.

When the goal is just to keep the status quo of a registered domains,
it is likely that less data will suffice.

	jaap

From lconroy@insensate.co.uk  Wed Feb 17 03:47:02 2010
Return-Path: <lconroy@insensate.co.uk>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 051D63A7CE1 for <ire@core3.amsl.com>; Wed, 17 Feb 2010 03:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dyMcyeJV7-nJ for <ire@core3.amsl.com>; Wed, 17 Feb 2010 03:47:01 -0800 (PST)
Received: from insensate.co.uk (ghost.insensate.co.uk [213.152.49.121]) by core3.amsl.com (Postfix) with ESMTP id B52E53A7CD0 for <ire@ietf.org>; Wed, 17 Feb 2010 03:47:00 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 1D55210C4D6; Wed, 17 Feb 2010 11:48:37 +0000 (GMT)
References: <C7A00530.25A1%francisco.arias@icann.org> <201002171115.o1HBFXjU086431@bartok.nlnetlabs.nl>
In-Reply-To: <201002171115.o1HBFXjU086431@bartok.nlnetlabs.nl>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
Message-Id: <5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk>
Content-Transfer-Encoding: quoted-printable
From: Lawrence Conroy <lconroy@insensate.co.uk>
Date: Wed, 17 Feb 2010 11:48:37 +0000
To: Francisco Arias <francisco.arias@icann.org>, Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1077)
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 17 Feb 2010 11:47:02 -0000

Hi Japp, Francisco, folks,
  This has moved the scope a LOOOONG way from Registry data.

For .tel, the directory information stuff is just delegated zone =
provisioning.
For users, .tel is a standard "delegation only" TLD, so the registry =
doesn't hold this data.

Did you mean to include standard delegated zone provisioning (of the =
child zone content) in the Escrow specs?

all the best,
  Lawrence



On 17 Feb 2010, at 11:15, Jaap Akkerhuis wrote:
>    Do you mean extra data (wrt EPP schemas) required by some =
registries in
>    order to accept a registration (e.g., identity document number) or =
data
>    needed to run services different to basic DNS resolution (e.g., =
directory
>    information like in .TEL)?
>=20
> Both. Whatever is needed to reconstitute the registry to it's
> original state (I made the remark in that context) and function.
>=20
> When the goal is just to keep the status quo of a registered domains,
> it is likely that less data will suffice.
>=20
> 	jaap
> _______________________________________________
> ire mailing list
> ire@ietf.org
> https://www.ietf.org/mailman/listinfo/ire


From Marc.Groeneweg@sidn.nl  Wed Feb 17 03:52:56 2010
Return-Path: <Marc.Groeneweg@sidn.nl>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9753E3A7B3B for <ire@core3.amsl.com>; Wed, 17 Feb 2010 03:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.504
X-Spam-Level: 
X-Spam-Status: No, score=-1.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZTvKWpzayNhJ for <ire@core3.amsl.com>; Wed, 17 Feb 2010 03:52:56 -0800 (PST)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [94.198.152.69]) by core3.amsl.com (Postfix) with ESMTP id ADAEF3A7B07 for <ire@ietf.org>; Wed, 17 Feb 2010 03:52:55 -0800 (PST)
Received: from sidn.nl ([192.168.2.12]) by ede1-kamx.sidn.nl  with ESMTP id o1HBsSIH001539 for <ire@ietf.org>; Wed, 17 Feb 2010 12:54:28 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Feb 2010 12:54:27 +0100
Message-ID: <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ire] High level requirements for Internet Registration DataEscrow
Thread-Index: AcqvxyixRK1OqObHR5OMj/2g0lGddQAADzVA
References: <C7A00530.25A1%francisco.arias@icann.org><201002171115.o1HBFXjU086431@bartok.nlnetlabs.nl> <5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk>
From: "Marc Groeneweg" <Marc.Groeneweg@sidn.nl>
To: <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration DataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 17 Feb 2010 11:52:56 -0000

Dear all,

>   This has moved the scope a LOOOONG way from Registry data.
>=20
> For .tel, the directory information stuff is just delegated zone
> provisioning.
> For users, .tel is a standard "delegation only" TLD, so the registry
> doesn't hold this data.
>=20
> Did you mean to include standard delegated zone provisioning (of the
> child zone content) in the Escrow specs?
SNAP

It's the standard definition between a thin registry and a fat registry.
As a thin registry, one only handles delegation information, nothing
else. I guess in this case, the Escrow data is almost the same as the
zonefile contents (and probably the registrar who registered the
domainname).

As a fat registry, one also handles contact information. Most registries
(no gTLD's I guess) are of this type. And it's not only the data, also
the policies which are modeled in the registry operation. Local policies
like privacy issues are built in the processing of the domainname
registration. I believe this is what Jaap mentions and makes a point of.

Regards,

Marc Groeneweg

From jaap@bartok.nlnetlabs.nl  Wed Feb 17 04:32:53 2010
Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 196563A7E97 for <ire@core3.amsl.com>; Wed, 17 Feb 2010 04:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=0.222,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LczLwY4V86Pi for <ire@core3.amsl.com>; Wed, 17 Feb 2010 04:32:52 -0800 (PST)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by core3.amsl.com (Postfix) with ESMTP id 10D3F3A7CA2 for <ire@ietf.org>; Wed, 17 Feb 2010 04:32:51 -0800 (PST)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id o1HCYOfQ046821 for <ire@ietf.org>; Wed, 17 Feb 2010 13:34:25 +0100 (CET) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201002171234.o1HCYOfQ046821@bartok.nlnetlabs.nl>
To: "ire@ietf.org" <ire@ietf.org>
In-reply-to: <5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk> 
References: <C7A00530.25A1%francisco.arias@icann.org> <201002171115.o1HBFXjU086431@bartok.nlnetlabs.nl> <5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk>
Comments: In-reply-to Lawrence Conroy <lconroy@insensate.co.uk> message dated "Wed, 17 Feb 2010 11:48:37 +0000."
Date: Wed, 17 Feb 2010 13:34:24 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (bartok.nlnetlabs.nl [127.0.0.1]); Wed, 17 Feb 2010 13:34:25 +0100 (CET)
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 17 Feb 2010 12:32:53 -0000

    Hi Japp, Francisco, folks,
      This has moved the scope a LOOOONG way from Registry data.

Yes, it has moved into discussing "what is the problem we want to
solve with this". In other words, what are the High level requirements
for Internet Registration Data Escrow?

	jaap

From myoung@ca.afilias.info  Wed Feb 17 05:16:18 2010
Return-Path: <myoung@ca.afilias.info>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 935F73A7BAB for <ire@core3.amsl.com>; Wed, 17 Feb 2010 05:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wjGBtPsaNIeW for <ire@core3.amsl.com>; Wed, 17 Feb 2010 05:16:17 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id 724DC3A7993 for <ire@ietf.org>; Wed, 17 Feb 2010 05:16:17 -0800 (PST)
Received: from ms5.yyz2.afilias-ops.info ([10.50.129.111] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <myoung@ca.afilias.info>) id 1Nhjmt-0004h3-42; Wed, 17 Feb 2010 13:17:55 +0000
Received: from phl-nat.afilias.info ([67.200.48.3] helo=DUN345) by smtp.afilias.info with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <myoung@ca.afilias.info>) id 1Nhjms-0000EX-5C; Wed, 17 Feb 2010 13:17:55 +0000
From: "Michael Young" <myoung@ca.afilias.info>
To: "'Marc Groeneweg'" <Marc.Groeneweg@sidn.nl>, <ire@ietf.org>
References: <C7A00530.25A1%francisco.arias@icann.org><201002171115.o1HBFXjU086431@bartok.nlnetlabs.nl>	<5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk> <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local>
In-Reply-To: <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local>
Date: Wed, 17 Feb 2010 08:17:41 -0500
Message-ID: <001701caafd3$973f9fd0$c5bedf70$@afilias.info>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqvxyixRK1OqObHR5OMj/2g0lGddQAADzVAAAKEmfA=
Content-Language: en-ca
Subject: Re: [ire] High level requirements for Internet Registration	DataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 17 Feb 2010 13:16:18 -0000

Policies and proprietary schemas are outside the scope basic escrow data
services. This is not about trying to reconstitute a registry operator in
situ, its about basic disaster recovery.  What is the minimum required data
to reconstitute a working/functioning registry? Certainly the specification
MUST support extensions and MUST allow one to describe data relationships,
as there are many customized versions of registries. (I think the current
draft already provides for both). However, how those data relationships are
executed in a operational schema design is entirely up to new Operator
reconstituting the registry.  There are many ways to approach a schema
design to achieve the same data relationship.

The original goal in this discussion seemed to be to have a generic object
that could represent optional submissions like a copy of the registry
software (if the operator was so inclined).  I believe this could already be
handled through the proposed extension framework.

I also think we should agree on the scope and tasks of this working group as
a starting point. Otherwise we are bound to drift sideways on objectives.

Best Regards,

Michael Young

Vice-President,
Product Development
Afilias
O: +14166734109
C: +16472891220


-----Original Message-----
From: Marc Groeneweg [mailto:Marc.Groeneweg@sidn.nl] 
Sent: February-17-10 6:54 AM
To: ire@ietf.org
Subject: Re: [ire] High level requirements for Internet Registration
DataEscrow

Dear all,

>   This has moved the scope a LOOOONG way from Registry data.
> 
> For .tel, the directory information stuff is just delegated zone
> provisioning.
> For users, .tel is a standard "delegation only" TLD, so the registry
> doesn't hold this data.
> 
> Did you mean to include standard delegated zone provisioning (of the
> child zone content) in the Escrow specs?
SNAP

It's the standard definition between a thin registry and a fat registry.
As a thin registry, one only handles delegation information, nothing
else. I guess in this case, the Escrow data is almost the same as the
zonefile contents (and probably the registrar who registered the
domainname).

As a fat registry, one also handles contact information. Most registries
(no gTLD's I guess) are of this type. And it's not only the data, also
the policies which are modeled in the registry operation. Local policies
like privacy issues are built in the processing of the domainname
registration. I believe this is what Jaap mentions and makes a point of.

Regards,

Marc Groeneweg
_______________________________________________
ire mailing list
ire@ietf.org
https://www.ietf.org/mailman/listinfo/ire


From JGould@verisign.com  Wed Feb 17 15:01:49 2010
Return-Path: <JGould@verisign.com>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BECB28C27F for <ire@core3.amsl.com>; Wed, 17 Feb 2010 15:01:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.914
X-Spam-Level: 
X-Spam-Status: No, score=-1.914 tagged_above=-999 required=5 tests=[AWL=3.288,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CmAgPQPEAt0t for <ire@core3.amsl.com>; Wed, 17 Feb 2010 15:01:36 -0800 (PST)
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74]) by core3.amsl.com (Postfix) with ESMTP id 7EFFC28C284 for <ire@ietf.org>; Wed, 17 Feb 2010 15:01:36 -0800 (PST)
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id o1HMveIx011263 for <ire@ietf.org>; Wed, 17 Feb 2010 17:57:41 -0500
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Feb 2010 18:03:15 -0500
Received: from 10.131.29.63 ([10.131.29.63]) by dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) with Microsoft Exchange Server HTTP-DAV ;  Wed, 17 Feb 2010 23:03:14 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Wed, 17 Feb 2010 18:03:06 -0500
From: James Gould <jgould@verisign.com>
To: <ire@ietf.org>
Message-ID: <C7A1DFDA.377A4%jgould@verisign.com>
Thread-Topic: [ire] I-D Action:draft-arias-registry-data-escrow-00.txt
Thread-Index: AcqeKIp6I/URS8W7QoavXtjs1uRKGAR/NLjd
In-Reply-To: <p062408d2c783f85ddcb3@[10.20.30.158]>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3349274591_47813164"
X-OriginalArrivalTime: 17 Feb 2010 23:03:15.0953 (UTC) FILETIME=[6349A610:01CAB025]
Subject: Re: [ire] I-D Action:draft-arias-registry-data-escrow-00.txt
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 17 Feb 2010 23:01:49 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3349274591_47813164
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

All,

I finally got around to reviewing the draft created by Francisco.  I hope
that we discuss some of this at the BOF, but I want to highlight some of my
initial feedback to the draft:

1. High level
> 1. It would be best to establish some high level format and policies arou=
nd
> the data content within an RFC that can be extended by additional RFC=B9s o=
r
> custom specifications in a similar fashion to EPP RFC 5730 and the associ=
ated
> mappings (Domain Name RFC 5731, Host RFC 5732, Contact 5733).   I know fo=
r
> .NAME that we have additional provisioning objects to escrow including Em=
ail
> Forwarding, Defensive Registration, and NameWatch which is not covered by=
 the
> draft.  What is the process for including additional objects?
> 2. We should use terminology consistent with the EPP RFC=B9s and define at =
a
> minimum the same set of attributes as the EPP RFC=B9s.  For example, use of=
 Host
> instead of Name Server.
> 3. The references to {creatorRegistrar} and {updateRegistrar} should be
> changed to {createUser} and {updateUser}, respectively.  There can be mul=
tiple
> users per Registrar and there can be multiple users including Registry us=
ers
> that can create and update objects, so these should reference a User Hand=
le
> and not a Registrar Handle and be named appropriately.
> 4. Users are completely missing from the draft.  I=B9m assuming that at lea=
st
> the User Handle and User Identifier (login name), along with other user
> details would be needed.
> 5. It=B9s assumed that the roids are derived by the handles?  The Registry
> should indicate in some way what the format of the roids are based on the
> handles. =20
> 6. {authInfo} - Question of whether this can be an encrypted value?  This
> functions as a password, so it=B9s not a good practice to store them unencr=
ypted
> in the database and I=B9m pretty sure that the escrow creation shouldn=B9t go
> through the process of decrypted all of the values.  If the value were
> encrypted the Registry should deposit the decryption program and decrypti=
on
> key. =20
2. Section 5.1 Domain
> 1. There needs to be a method of defining additional attributes at the do=
main
> level to accommodate a larger set of Registries.
> 2. {creatorRegistrar} - Refer to high-level comment 1.3.
> 3. {authInfo} - Refer to high-level comment 1.6.
> 4. {updateRegistrar} - Refer to high-level comment 1.3.
> 5. {deletionDate} - This should be optional, since this could be dynamica=
lly
> calculated based on a combination of reference data and live data.  Maybe=
 the
> policy reference data should be deposited.
> 6. How are hostAttr name servers addressed in RFC 5731?
3. Section 5.2 Contacts
> 1. Where are the RFC 5733 <contact:id> attribute captured?
> 2. {creatorRegistrar} - Refer to high-level comment 1.3.
> 3. {authInfo} - Refer to high-level comment 1.6.
> 4. {updateRegistrar} - Refer to high-level comment 1.3.
> 5. I see the need for additional custom attributes that have been handled=
 by
> EPP extensions by various Registries.
4. Section 5.4 is called Name servers.  Why wouldn=B9t we use the EPP 5732
term of Hosts?
> 1. Where are the {createUser}, {UpdateUser}, {lastUpdate}, and
> {lastTransferDate} attributes?
> 2. There should be an optional {parentDomainHandle} added to support chil=
d
> hosts.
5. Section 5.5 Name server IP Addresses
> 1. Should be called Host IP Addresses to be consistent with RFC 5731.
6. Section 5.6 Delegation Signer (DS) records
> 1. This will need to be updated based on the work being done on rfc4310bi=
s.
> Specifically, {maximumSigLife} is not an attribute of an individual Deleg=
ation
> Signer record, so it should be up in Section 5.1 Domain as an option
> attribute.  In addition rfc4310bis support a DS Data Interface as well as=
 a
> Key Data Interface where there could be a handle for the the DNSKEY and t=
hen
> have multiple DS records referencing the DNSKEY.
> 2. It would be good to add a {dsHandle} to be the unique identifier for a=
n
> individual DS. =20
7. Section 5.7 Registrars
> 1. We might want to capture some additional information for the Registrar
> like:
>> 1. address=20
>> 2. url=20
>> 3. whois server=20
>> 4. status =AD The possible values could include ACTIVE, HOLD, INACTIVE and
>> could be up to the definition of the server.
>> 5. createdDate=20
>> 6. createdBy=20
>> 7. updatedDate=20
>> 8. updatedBy
> 2. Should the Registrar Contacts be deposited as well?
> 3. I=B9m not sure from the draft what is required and what is not required,=
 but
> the {ianaId} might need to be optional to support escrow of non-regulated
> TLD=B9s. =20
8. Users - I believe it would be good to include information about the
users, where there could be more than one user per account.  It is the user=
s
that create and update objects.  I would propose the following attributes
for a user:
> 1. {userHandle}, User Handle
> 2. {registrarHandle}, Registrar Handle for the user=B9s Registrar.  A Regis=
try
> User could be linked to a Registry Registrar record, but there could be a
> special value for Registry users like REGISTRY.
> 3. {status} - Status of the user like ACTIVE, INACTIVE.  The possible val=
ues
> and meanings might be defined by the server.
> 4. {type} - Type of user.  This could include types like EPP, CSR, ADMIN,
> etc..=20
> 5. {name} - User name
> 6. {password} - Hash of password.  The hashing tool and source used by th=
e
> Registry could be deposited, for use of the passwords.  The alternative i=
s
> having to reset all of the passwords
> 7. {phoneNumber} - Phone number of user
> 8. {faxNumber} - FAX number of user
> 9. {email} - E-mail address of user
9. Section 5.16 DS deletions
> 1. It would be good if this referenced the {dsHandle} instead of the
> {domainHandle}=20
> 2. Based on rfc4310bis there would be the need for Key deletions as well =
to
> handle Registries supporting the Key Data Interface.
10. Section 5.17 Internationalized Domain Names (IDNs)
> 1. This is too specific to a single implementation of IDN=B9s.  The only fi=
elds
> that might be common across Registries would be:
>> 1. {domainHandle}
>> 2. {languageCode} - Which is currently missing from the draft
>> 3. {variant} - General variant information that is server specific.  The
>> question is whether this is needed at all since the variant can be
>> regenerated from the domain name and the code tables.
11. Section 5.18 IANA IDN Tables index
> 1. This should be optional
12. Section 5.19 EPP Contact information disclosure
> 1. This should be optional based on support by the server of the optional
> <contact:disclose> element.
13. Section 5.20 through 5.24 could be handled by simply depositing the EPP
Greeting.  This rarely ever changes, so I=B9m not sure what the value is for
depositing this information each time.
14. Section 6
> 1. Why would be deposit the XML schemas for the RFC XML schemas?  I could=
 see
> depositing the XML schemas for custom mappings and extensions, but the RF=
C
> URI=B9s should be good enough for identifying the XML schemas.

--=20


JG=20

-------------------------------------------------------
James F. Gould
Principal Software Engineer
VeriSign Naming Services
jgould@verisign.com
Direct: 703.948.3271
Mobile: 703.628.7063

=20
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

Notice to Recipient:  This e-mail contains confidential, proprietary and/or
Registry  Sensitive information intended solely for the recipient and, thus
may not be  retransmitted, reproduced or disclosed without the prior writte=
n
consent of  VeriSign Naming and Directory Services.  If you have received
this e-mail message in error, please notify the sender immediately by
telephone or reply e-mail and destroy the original message without making a
copy.  Thank you.



From: by way of Paul Hoffman <Internet-Drafts@ietf.org>
Date: Mon, 25 Jan 2010 20:40:06 -0500
To: <ire@ietf.org>
Subject: [ire] I-D Action:draft-arias-registry-data-escrow-00.txt




A New Internet-Draft is available from the on-line Internet-Drafts
directories.

        Title           : Internet Domain Registry Data Escrow specificatio=
n
        Author(s)       : F. Arias
        Filename        : draft-arias-registry-data-escrow-00.txt
        Pages           : 24
        Date            : 2010-01-25

This document specifies the format and contents of Data Escrow
deposits for Domain Registries.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-arias-registry-data-escrow-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


[The following attachment must be fetched by ftp.  Command-click the URL
below to ask your ftp client to fetch it.]
<ftp://ftp.ietf.org/internet-drafts/draft-arias-registry-data-escrow-00.txt=
>
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
_______________________________________________
ire mailing list
ire@ietf.org
https://www.ietf.org/mailman/listinfo/ire



--B_3349274591_47813164
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [ire] I-D Action:draft-arias-registry-data-escrow-00.txt</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>All,<BR>
<BR>
I finally got around to reviewing the draft created by Francisco. &nbsp;I h=
ope that we discuss some of this at the BOF, but I want to highlight some of=
 my initial feedback to the draft:<BR>
<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>High level<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>It would be best to establish some high level format=
 and policies around the data content within an RFC that can be extended by =
additional RFC&#8217;s or custom specifications in a similar fashion to EPP =
RFC 5730 and the associated mappings (Domain Name RFC 5731, Host RFC 5732, C=
ontact 5733). &nbsp;&nbsp;I know for .NAME that we have additional provision=
ing objects to escrow including Email Forwarding, Defensive Registration, an=
d NameWatch which is not covered by the draft. &nbsp;What is the process for=
 including additional objects?
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>We should use terminology consistent with the EPP RFC&#8=
217;s and define at a minimum the same set of attributes as the EPP RFC&#821=
7;s. &nbsp;For example, use of Host instead of Name Server. &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>The references to {creatorRegistrar} and {updateRegistra=
r} should be changed to {createUser} and {updateUser}, respectively. &nbsp;T=
here can be multiple users per Registrar and there can be multiple users inc=
luding Registry users that can create and update objects, so these should re=
ference a User Handle and not a Registrar Handle and be named appropriately.=
 &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>Users are completely missing from the draft. &nbsp;I&#82=
17;m assuming that at least the User Handle and User Identifier (login name)=
, along with other user details would be needed.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>It&#8217;s assumed that the roids are derived by the han=
dles? &nbsp;The Registry should indicate in some way what the format of the =
roids are based on the handles. &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{authInfo} - Question of whether this can be an encrypte=
d value? &nbsp;This functions as a password, so it&#8217;s not a good practi=
ce to store them unencrypted in the database and I&#8217;m pretty sure that =
the escrow creation shouldn&#8217;t go through the process of decrypted all =
of the values. &nbsp;If the value were encrypted the Registry should deposit=
 the decryption program and decryption key. &nbsp;<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.1 Domain <BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>There needs to be a method of defining additional at=
tributes at the domain level to accommodate a larger set of Registries. &nbs=
p;&nbsp;&nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{creatorRegistrar} - Refer to high-level comment 1.3.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{authInfo} - Refer to high-level comment 1.6. &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{updateRegistrar} - Refer to high-level comment 1.3.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{deletionDate} - This should be optional, since this cou=
ld be dynamically calculated based on a combination of reference data and li=
ve data. &nbsp;Maybe the policy reference data should be deposited.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>How are hostAttr name servers addressed in RFC 5731? <BR=
>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.2 Contacts<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>Where are the RFC 5733 &lt;contact:id&gt; attribute =
captured?
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{creatorRegistrar} - Refer to high-level comment 1.3.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{authInfo} - Refer to high-level comment 1.6. &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{updateRegistrar} - Refer to high-level comment 1.3.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>I see the need for additional custom attributes that hav=
e been handled by EPP extensions by various Registries. &nbsp;<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.4 is called Name servers. &nbsp;Why would=
n&#8217;t we use the EPP 5732 term of Hosts?<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>Where are the {createUser}, {UpdateUser}, {lastUpdat=
e}, and {lastTransferDate} attributes?
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>There should be an optional {parentDomainHandle} added t=
o support child hosts.<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.5 Name server IP Addresses<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>Should be called Host IP Addresses to be consistent =
with RFC 5731.<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.6 Delegation Signer (DS) records<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>This will need to be updated based on the work being=
 done on rfc4310bis. &nbsp;Specifically, {maximumSigLife} is not an attribut=
e of an individual Delegation Signer record, so it should be up in Section 5=
.1 Domain as an option attribute. &nbsp;In addition rfc4310bis support a DS =
Data Interface as well as a Key Data Interface where there could be a handle=
 for the the DNSKEY and then have multiple DS records referencing the DNSKEY=
. &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>It would be good to add a {dsHandle} to be the unique id=
entifier for an individual DS. &nbsp;<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.7 Registrars<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>We might want to capture some additional information=
 for the Registrar like:<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>address
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>url
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>whois server
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>status &#8211; The possible values could include ACTIVE,=
 HOLD, INACTIVE and could be up to the definition of the server.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>createdDate
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>createdBy
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>updatedDate
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>updatedBy<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Should the Registrar Contacts be deposited as well?
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>I&#8217;m not sure from the draft what is required and w=
hat is not required, but the {ianaId} might need to be optional to support e=
scrow of non-regulated TLD&#8217;s. &nbsp;<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Users - I believe it would be good to include infor=
mation about the users, where there could be more than one user per account.=
 &nbsp;It is the users that create and update objects. &nbsp;I would propose=
 the following attributes for a user:<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>{userHandle}, User Handle
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{registrarHandle}, Registrar Handle for the user&#8217;s=
 Registrar. &nbsp;A Registry User could be linked to a Registry Registrar re=
cord, but there could be a special value for Registry users like REGISTRY.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{status} - Status of the user like ACTIVE, INACTIVE. &nb=
sp;The possible values and meanings might be defined by the server.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{type} - Type of user. &nbsp;This could include types li=
ke EPP, CSR, ADMIN, etc..
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{name} - User name
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{password} - Hash of password. &nbsp;The hashing tool an=
d source used by the Registry could be deposited, for use of the passwords. =
&nbsp;The alternative is having to reset all of the passwords &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{phoneNumber} - Phone number of user
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{faxNumber} - FAX number of user
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{email} - E-mail address of user<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.16 DS deletions<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>It would be good if this referenced the {dsHandle} i=
nstead of the {domainHandle}
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>Based on rfc4310bis there would be the need for Key dele=
tions as well to handle Registries supporting the Key Data Interface.<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.17 Internationalized Domain Names (IDNs)<=
BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>This is too specific to a single implementation of I=
DN&#8217;s. &nbsp;The only fields that might be common across Registries wou=
ld be:<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>{domainHandle}
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{languageCode} - Which is currently missing from the dra=
ft
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>{variant} - General variant information that is server s=
pecific. &nbsp;The question is whether this is needed at all since the varia=
nt can be regenerated from the domain name and the code tables.<BR>
</SPAN></FONT></OL></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Section 5.18 IANA IDN Tables index<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>This should be optional<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.19 EPP Contact information disclosure<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>This should be optional based on support by the serv=
er of the optional &lt;contact:disclose&gt; element.<BR>
</SPAN></FONT></OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'>Section 5.20 through 5.24 could be handled by simpl=
y depositing the EPP Greeting. &nbsp;This rarely ever changes, so I&#8217;m =
not sure what the value is for depositing this information each time. &nbsp;
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:11pt'>Section 6<BR>
</SPAN></FONT><OL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=
 STYLE=3D'font-size:11pt'>Why would be deposit the XML schemas for the RFC XML=
 schemas? &nbsp;I could see depositing the XML schemas for custom mappings a=
nd extensions, but the RFC URI&#8217;s should be good enough for identifying=
 the XML schemas. &nbsp;<BR>
</SPAN></FONT></OL></OL><FONT SIZE=3D"1"><FONT FACE=3D"Verdana, Helvetica, Aria=
l"><SPAN STYLE=3D'font-size:9pt'><BR>
-- <BR>
<BR>
<BR>
JG <BR>
<BR>
</SPAN></FONT><FONT COLOR=3D"#800000"><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-si=
ze:7.5pt'>-------------------------------------------------------<BR>
</SPAN></FONT></FONT></FONT><FONT FACE=3D"Arial"><FONT COLOR=3D"#7F0000"><FONT =
SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'><B>James F. Gould<BR>
</B></SPAN></FONT></FONT><FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'><B><FO=
NT COLOR=3D"#4C4C4C">Principal Software Engineer<BR>
</FONT></B><FONT COLOR=3D"#4C4C4C">VeriSign Naming Services<BR>
</FONT></SPAN></FONT><FONT COLOR=3D"#1100EF"><FONT SIZE=3D"1"><SPAN STYLE=3D'font=
-size:9pt'><a href=3D"jgould@verisign.com">jgould@verisign.com</a><BR>
</SPAN></FONT></FONT><FONT SIZE=3D"1"><FONT COLOR=3D"#4C4C4C"><SPAN STYLE=3D'font=
-size:7.5pt'><B>Direct:</B> 703.948.3271<BR>
<B>Mobile:</B> 703.628.7063<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:7.5pt'><BR>
&nbsp;<BR>
<FONT COLOR=3D"#4C4C4C">21345 Ridgetop Circle<BR>
LS2-2-1<BR>
Dulles, VA 20166<BR>
</FONT><BR>
<FONT COLOR=3D"#7F0000"><B><I>Notice to Recipient: &nbsp;</I></B></FONT></SPA=
N><I><SPAN STYLE=3D'font-size:9pt'>This e-mail contains confidential, propriet=
ary and/or Registry &nbsp;Sensitive information intended solely for the reci=
pient and, thus may not be &nbsp;retransmitted, reproduced or disclosed with=
out the prior written consent of &nbsp;VeriSign Naming and Directory Service=
s. &nbsp;<B>If you have received &nbsp;this e-mail message in error, please =
notify the sender immediately by &nbsp;telephone or reply e-mail and destroy=
 the original message without making a &nbsp;copy.</B> &nbsp;Thank you.<BR>
</SPAN></I></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><S=
PAN STYLE=3D'font-size:11pt'><BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"><B>From: </B>by way of Paul Hoffman &=
lt;<a href=3D"Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a>&gt;<BR>
<B>Date: </B>Mon, 25 Jan 2010 20:40:06 -0500<BR>
<B>To: </B>&lt;<a href=3D"ire@ietf.org">ire@ietf.org</a>&gt;<BR>
<B>Subject: </B>[ire] I-D Action:draft-arias-registry-data-escrow-00.txt<BR=
>
<BR>
<BR>
<BR>
<BR>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Internet Domain Registry Data Escro=
w specification<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Author(s) &nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;: F. Arias<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Filename &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;: draft-arias-registry-data-escrow-00.txt<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pages &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 24<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Date &nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2010-01-25<BR>
<BR>
This document specifies the format and contents of Data Escrow<BR>
deposits for Domain Registries.<BR>
<BR>
A URL for this Internet-Draft is:<BR>
<a href=3D"http://www.ietf.org/internet-drafts/draft-arias-registry-data-escr=
ow-00.txt">http://www.ietf.org/internet-drafts/draft-arias-registry-data-esc=
row-00.txt</a><BR>
<BR>
Internet-Drafts are also available by anonymous FTP at:<BR>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-d=
rafts/</a><BR>
<BR>
Below is the data which will enable a MIME compliant mail reader<BR>
implementation to automatically retrieve the ASCII version of the<BR>
Internet-Draft.<BR>
<BR>
<BR>
[The following attachment must be fetched by ftp. &nbsp;Command-click the U=
RL below to ask your ftp client to fetch it.]<BR>
&lt;<a href=3D"ftp://ftp.ietf.org/internet-drafts/draft-arias-registry-data-e=
scrow-00.txt">ftp://ftp.ietf.org/internet-drafts/draft-arias-registry-data-e=
scrow-00.txt</a>&gt;<BR>
_______________________________________________<BR>
I-D-Announce mailing list<BR>
<a href=3D"I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce">https://www.ie=
tf.org/mailman/listinfo/i-d-announce</a><BR>
Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.html">http:=
//www.ietf.org/shadow.html</a><BR>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/i=
etf/1shadow-sites.txt</a><BR>
_______________________________________________<BR>
ire mailing list<BR>
<a href=3D"ire@ietf.org">ire@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/ire">https://www.ietf.org/ma=
ilman/listinfo/ire</a><BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3349274591_47813164--


From Ed.Lewis@neustar.biz  Thu Feb 18 06:25:33 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5345F3A7CFD for <ire@core3.amsl.com>; Thu, 18 Feb 2010 06:25:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level: 
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[AWL=-0.594, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itdYDFR9Yhiv for <ire@core3.amsl.com>; Thu, 18 Feb 2010 06:25:32 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 422B928C0F4 for <ire@ietf.org>; Thu, 18 Feb 2010 06:25:32 -0800 (PST)
Received: from fjaf2-lt61.cis.neustar.com (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1IEQhE0023875; Thu, 18 Feb 2010 09:26:49 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.200.157] by fjaf2-lt61.cis.neustar.com (PGP Universal service); Thu, 18 Feb 2010 09:26:53 -0500
X-PGP-Universal: processed; by fjaf2-lt61.cis.neustar.com on Thu, 18 Feb 2010 09:26:53 -0500
Mime-Version: 1.0
Message-Id: <a06240802c7a2fae2b7e0@[10.31.200.166]>
In-Reply-To: <C79E5C2C.2544%francisco.arias@icann.org>
References: <C79E5C2C.2544%francisco.arias@icann.org>
Date: Thu, 18 Feb 2010 09:18:44 -0500
To: Francisco Arias <francisco.arias@icann.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 18 Feb 2010 14:25:33 -0000

At 2:04 -0800 2/15/10, Francisco Arias wrote:

>Ed, what other pieces of information?

For instance - DNS configuration information (the DNS "data-driven" 
portion is derived from the database contents but the stuff that is 
usually in static "config" files is not).

Perhaps it also depends on what one considers the database - but 
there is billing information (account balances, stuff other than 
expiration dates, etc.) that may be stored elsewhere.

I usually view a registry of consisting of the following roughly 
defined interfaces and protocols:

Administrative -> Billing, legal support (think law enforcement...)
Provisioning -> The registration "desk" (like EPP)
Relying Party -> DNS (DN/RI-R), WhoIS other inspection protocols

The information needed to set up these "external" interfaces are also 
needed - if the goal is to reconstitute and continue operations and 
not just "re-host the database."
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From Ed.Lewis@neustar.biz  Thu Feb 18 06:42:48 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BB043A7B5E for <ire@core3.amsl.com>; Thu, 18 Feb 2010 06:42:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.417
X-Spam-Level: 
X-Spam-Status: No, score=-2.417 tagged_above=-999 required=5 tests=[AWL=0.182,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WfztEjHKZk8P for <ire@core3.amsl.com>; Thu, 18 Feb 2010 06:42:47 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id DB78C3A69DA for <ire@ietf.org>; Thu, 18 Feb 2010 06:42:46 -0800 (PST)
Received: from fjaf2-lt61.cis.neustar.com (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1IEiLBH024006; Thu, 18 Feb 2010 09:44:22 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.200.157] by fjaf2-lt61.cis.neustar.com (PGP Universal service); Thu, 18 Feb 2010 09:44:27 -0500
X-PGP-Universal: processed; by fjaf2-lt61.cis.neustar.com on Thu, 18 Feb 2010 09:44:27 -0500
Mime-Version: 1.0
Message-Id: <a06240804c7a300c61977@[10.31.200.157]>
In-Reply-To: <001701caafd3$973f9fd0$c5bedf70$@afilias.info>
References: <C7A00530.25A1%francisco.arias@icann.org><201002171115.o1HBFXjU086431@bart ok.nlnetlabs.nl>	<5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk> <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local> <001701caafd3$973f9fd0$c5bedf70$@afilias.info>
Date: Thu, 18 Feb 2010 09:44:21 -0500
To: <ire@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: ed.lewis@neustar.biz
Subject: [ire] BoFfing...
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 18 Feb 2010 14:42:48 -0000

At 8:17 -0500 2/17/10, Michael Young wrote:

>I also think we should agree on the scope and tasks of this working group as
>a starting point. Otherwise we are bound to drift sideways on objectives.

And this is the time to start and do that.  The BoF meeting coming 
(still officially unapproved but James and I have slipped into the 
Apps Area list of chairs) in Anaheim will be a public "hearing" so to 
speak on setting the objectives.

One item to present and discuss at the meeting is a would-be WG 
charter.  That's a given.  I think it might be constructive to have 
some short "show-and-tells" from registries describing what they 
think belongs in escrow.

One of the questions to consider, is the goal of the effort to:
   Allow a thick registry be reconstituted in a thin registry operator?

Registries operate under a lot of policies (we have some registries 
that have oodles of rules to follow), complying with these policies 
is core to "continued operations."  How does this relate?

BTW - We run a few gTLDs and they are thick.  (To answer one comment 
on the list made a few days ago.)
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From JGould@verisign.com  Thu Feb 18 08:29:45 2010
Return-Path: <JGould@verisign.com>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E625A28C12F for <ire@core3.amsl.com>; Thu, 18 Feb 2010 08:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.027
X-Spam-Level: 
X-Spam-Status: No, score=-2.027 tagged_above=-999 required=5 tests=[AWL=3.175,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I1Jj60wBBwQh for <ire@core3.amsl.com>; Thu, 18 Feb 2010 08:29:39 -0800 (PST)
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74]) by core3.amsl.com (Postfix) with ESMTP id 8495E28C108 for <ire@ietf.org>; Thu, 18 Feb 2010 08:29:39 -0800 (PST)
Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [10.170.12.113]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id o1IGPjIE002140;  Thu, 18 Feb 2010 11:25:45 -0500
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 18 Feb 2010 11:31:21 -0500
Received: from 10.131.29.63 ([10.131.29.63]) by dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 18 Feb 2010 16:31:20 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Thu, 18 Feb 2010 11:31:13 -0500
From: James Gould <jgould@verisign.com>
To: Edward Lewis <Ed.Lewis@neustar.biz>, <ire@ietf.org>
Message-ID: <C7A2D581.377E3%jgould@verisign.com>
Thread-Topic: [ire] BoFfing...
Thread-Index: AcqwqONgN5IuXdPXSgi/hTeJRWk5TQADuWNK
In-Reply-To: <a06240804c7a300c61977@[10.31.200.157]>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3349337475_48596034"
X-OriginalArrivalTime: 18 Feb 2010 16:31:21.0685 (UTC) FILETIME=[CE1AD850:01CAB0B7]
Subject: Re: [ire] BoFfing...
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 18 Feb 2010 16:29:46 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3349337475_48596034
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Ed,

> One of the questions to consider, is the goal of the effort to:
>    Allow a thick registry be reconstituted in a thin registry operator?

I don=B9t believe we should consider the target operator system, but focus on
storing all of the provisioning data in a consistent and secure manor no
matter what makes up the Registry system.  I agree that there should be som=
e
requirements around additional information that needs to be deposited to
make the data usable for reconstituting a system, but I want to ensure that
the format is extensible, simple, and straight forward for a target operato=
r
to utilize.  For example, I wouldn=B9t want to not include information in the
data escrow because it is Registry specific and was not defined in the RFC.
The target operator should be able to count on at least an agreed upon
subset of information to work with.

--=20


JG=20

-------------------------------------------------------
James F. Gould
Principal Software Engineer
VeriSign Naming Services
jgould@verisign.com
Direct: 703.948.3271
Mobile: 703.628.7063

=20
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

Notice to Recipient:  This e-mail contains confidential, proprietary and/or
Registry  Sensitive information intended solely for the recipient and, thus
may not be  retransmitted, reproduced or disclosed without the prior writte=
n
consent of  VeriSign Naming and Directory Services.  If you have received
this e-mail message in error, please notify the sender immediately by
telephone or reply e-mail and destroy the original message without making a
copy.  Thank you.



From: Edward Lewis <Ed.Lewis@neustar.biz>
Date: Thu, 18 Feb 2010 09:44:21 -0500
To: <ire@ietf.org>
Cc: <ed.lewis@neustar.biz>
Subject: [ire] BoFfing...

At 8:17 -0500 2/17/10, Michael Young wrote:

>I also think we should agree on the scope and tasks of this working group =
as
>a starting point. Otherwise we are bound to drift sideways on objectives.

And this is the time to start and do that.  The BoF meeting coming
(still officially unapproved but James and I have slipped into the
Apps Area list of chairs) in Anaheim will be a public "hearing" so to
speak on setting the objectives.

One item to present and discuss at the meeting is a would-be WG
charter.  That's a given.  I think it might be constructive to have
some short "show-and-tells" from registries describing what they
think belongs in escrow.

One of the questions to consider, is the goal of the effort to:
   Allow a thick registry be reconstituted in a thin registry operator?

Registries operate under a lot of policies (we have some registries
that have oodles of rules to follow), complying with these policies
is core to "continued operations."  How does this relate?

BTW - We run a few gTLDs and they are thick.  (To answer one comment
on the list made a few days ago.)
--
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.
_______________________________________________
ire mailing list
ire@ietf.org
https://www.ietf.org/mailman/listinfo/ire



--B_3349337475_48596034
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [ire] BoFfing...</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>Ed,<BR>
<BR>
&gt; One of the questions to consider, is the goal of the effort to:<BR>
&gt; &nbsp;&nbsp;&nbsp;Allow a thick registry be reconstituted in a thin re=
gistry operator?<BR>
<BR>
I don&#8217;t believe we should consider the target operator system, but fo=
cus on storing all of the provisioning data in a consistent and secure manor=
 no matter what makes up the Registry system. &nbsp;I agree that there shoul=
d be some requirements around additional information that needs to be deposi=
ted to make the data usable for reconstituting a system, but I want to ensur=
e that the format is extensible, simple, and straight forward for a target o=
perator to utilize. &nbsp;For example, I wouldn&#8217;t want to not include =
information in the data escrow because it is Registry specific and was not d=
efined in the RFC. &nbsp;&nbsp;The target operator should be able to count o=
n at least an agreed upon subset of information to work with. &nbsp;<BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN S=
TYLE=3D'font-size:9pt'><BR>
-- <BR>
<BR>
<BR>
JG <BR>
<BR>
</SPAN></FONT><FONT COLOR=3D"#800000"><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-si=
ze:7.5pt'>-------------------------------------------------------<BR>
</SPAN></FONT></FONT></FONT><FONT FACE=3D"Arial"><FONT COLOR=3D"#7F0000"><FONT =
SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'><B>James F. Gould<BR>
</B></SPAN></FONT></FONT><FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'><B><FO=
NT COLOR=3D"#4C4C4C">Principal Software Engineer<BR>
</FONT></B><FONT COLOR=3D"#4C4C4C">VeriSign Naming Services<BR>
</FONT></SPAN></FONT><FONT COLOR=3D"#1100EF"><FONT SIZE=3D"1"><SPAN STYLE=3D'font=
-size:9pt'><a href=3D"jgould@verisign.com">jgould@verisign.com</a><BR>
</SPAN></FONT></FONT><FONT SIZE=3D"1"><FONT COLOR=3D"#4C4C4C"><SPAN STYLE=3D'font=
-size:7.5pt'><B>Direct:</B> 703.948.3271<BR>
<B>Mobile:</B> 703.628.7063<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:7.5pt'><BR>
&nbsp;<BR>
<FONT COLOR=3D"#4C4C4C">21345 Ridgetop Circle<BR>
LS2-2-1<BR>
Dulles, VA 20166<BR>
</FONT><BR>
<FONT COLOR=3D"#7F0000"><B><I>Notice to Recipient: &nbsp;</I></B></FONT></SPA=
N><I><SPAN STYLE=3D'font-size:9pt'>This e-mail contains confidential, propriet=
ary and/or Registry &nbsp;Sensitive information intended solely for the reci=
pient and, thus may not be &nbsp;retransmitted, reproduced or disclosed with=
out the prior written consent of &nbsp;VeriSign Naming and Directory Service=
s. &nbsp;<B>If you have received &nbsp;this e-mail message in error, please =
notify the sender immediately by &nbsp;telephone or reply e-mail and destroy=
 the original message without making a &nbsp;copy.</B> &nbsp;Thank you.<BR>
</SPAN></I></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><S=
PAN STYLE=3D'font-size:11pt'><BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"><B>From: </B>Edward Lewis &lt;<a href=
=3D"Ed.Lewis@neustar.biz">Ed.Lewis@neustar.biz</a>&gt;<BR>
<B>Date: </B>Thu, 18 Feb 2010 09:44:21 -0500<BR>
<B>To: </B>&lt;<a href=3D"ire@ietf.org">ire@ietf.org</a>&gt;<BR>
<B>Cc: </B>&lt;<a href=3D"ed.lewis@neustar.biz">ed.lewis@neustar.biz</a>&gt;<=
BR>
<B>Subject: </B>[ire] BoFfing...<BR>
<BR>
At 8:17 -0500 2/17/10, Michael Young wrote:<BR>
<BR>
&gt;I also think we should agree on the scope and tasks of this working gro=
up as<BR>
&gt;a starting point. Otherwise we are bound to drift sideways on objective=
s.<BR>
<BR>
And this is the time to start and do that. &nbsp;The BoF meeting coming<BR>
(still officially unapproved but James and I have slipped into the<BR>
Apps Area list of chairs) in Anaheim will be a public &quot;hearing&quot; s=
o to<BR>
speak on setting the objectives.<BR>
<BR>
One item to present and discuss at the meeting is a would-be WG<BR>
charter. &nbsp;That's a given. &nbsp;I think it might be constructive to ha=
ve<BR>
some short &quot;show-and-tells&quot; from registries describing what they<=
BR>
think belongs in escrow.<BR>
<BR>
One of the questions to consider, is the goal of the effort to:<BR>
&nbsp;&nbsp;&nbsp;Allow a thick registry be reconstituted in a thin registr=
y operator?<BR>
<BR>
Registries operate under a lot of policies (we have some registries<BR>
that have oodles of rules to follow), complying with these policies<BR>
is core to &quot;continued operations.&quot; &nbsp;How does this relate?<BR=
>
<BR>
BTW - We run a few gTLDs and they are thick. &nbsp;(To answer one comment<B=
R>
on the list made a few days ago.)<BR>
--<BR>
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
<BR>
Edward Lewis<BR>
NeuStar &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;You can leave a voice message=
 at +1-571-434-5468<BR>
<BR>
As with IPv6, the problem with the deployment of frictionless surfaces is<B=
R>
that they're not getting traction.<BR>
_______________________________________________<BR>
ire mailing list<BR>
<a href=3D"ire@ietf.org">ire@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/ire">https://www.ietf.org/ma=
ilman/listinfo/ire</a><BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3349337475_48596034--


From Ed.Lewis@neustar.biz  Thu Feb 18 18:48:20 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B4F33A7F39 for <ire@core3.amsl.com>; Thu, 18 Feb 2010 18:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPE-CytkdwFK for <ire@core3.amsl.com>; Thu, 18 Feb 2010 18:48:19 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 28C553A7F26 for <ire@ietf.org>; Thu, 18 Feb 2010 18:48:19 -0800 (PST)
Received: from Work-Laptop-2.local (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1J2nrUW029927; Thu, 18 Feb 2010 21:49:58 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [192.168.1.103] by Work-Laptop-2.local (PGP Universal service); Thu, 18 Feb 2010 21:50:02 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 18 Feb 2010 21:50:02 -0500
Mime-Version: 1.0
Message-Id: <a06240801c7a3ab51021b@[10.31.200.157]>
In-Reply-To: <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local>
References: <C7A00530.25A1%francisco.arias@icann.org><201002171115.o1HBFXjU086431@bart ok.nlnetlabs.nl>	<5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk> <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local>
Date: Thu, 18 Feb 2010 21:49:09 -0500
To: "Marc Groeneweg" <Marc.Groeneweg@sidn.nl>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: ire@ietf.org
Subject: Re: [ire] High level requirements for Internet Registration DataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Feb 2010 02:48:20 -0000

At 12:54 +0100 2/17/10, Marc Groeneweg wrote:

>It's the standard definition between a thin registry and a fat registry.
>As a thin registry, one only handles delegation information, nothing
>else. I guess in this case, the Escrow data is almost the same as the
>zonefile contents (and probably the registrar who registered the
>domainname).

The comment above is tailored to domain name registries.  In a thin 
registry the information to be put in the DNS is stored as well as 
the sponsoring registrar (using the ICANN environment terminology). 
For that, the escrow data would be the DNS stuff plus at least the 
sponsor stuff.

>As a fat registry, one also handles contact information. Most registries
>(no gTLD's I guess) are of this type.

As this caused some confusion (expressed to me privately) - Neustar 
for one operates gTLDs under a (we prefer) "thick" model.  (Fat is 
not a "positive" term. ;))

>And it's not only the data, also
>the policies which are modeled in the registry operation. Local policies
>like privacy issues are built in the processing of the domainname
>registration. I believe this is what Jaap mentions and makes a point of.

The policies, I think that is open for debate.  I'm not questioning 
the statement here, but I am not convinced whether the policies are 
in the escrow or not.  It might be that the "goal is to reconstitute 
the registry" is an overstatement of what we need to be able to 
achieve.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From daniel@digsys.bg  Thu Feb 18 23:19:25 2010
Return-Path: <daniel@digsys.bg>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B95B3A80CF for <ire@core3.amsl.com>; Thu, 18 Feb 2010 23:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, J_CHICKENPOX_82=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jbgJdNSBjTVo for <ire@core3.amsl.com>; Thu, 18 Feb 2010 23:19:23 -0800 (PST)
Received: from relay2.digsys.bg (varna.digsys.bg [192.92.129.9]) by core3.amsl.com (Postfix) with ESMTP id D18343A7D11 for <ire@ietf.org>; Thu, 18 Feb 2010 23:19:17 -0800 (PST)
Received: from dcave.digsys.bg (daniel@dcave.digsys.bg [192.92.129.5]) by relay2.digsys.bg (8.14.3/8.14.3) with ESMTP id o1J7L0DO060402 for <ire@ietf.org>; Fri, 19 Feb 2010 09:21:00 +0200 (EET) (envelope-from daniel@digsys.bg)
Message-ID: <4B7E3BDC.6060908@digsys.bg>
Date: Fri, 19 Feb 2010 09:21:00 +0200
From: Daniel Kalchev <daniel@digsys.bg>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100210 Thunderbird/3.0.1
MIME-Version: 1.0
To: ire@ietf.org
References: <C7A00530.25A1%francisco.arias@icann.org><201002171115.o1HBFXjU086431@bart	ok.nlnetlabs.nl>	<5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk>	<850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local> <a06240801c7a3ab51021b@[10.31.200.157]>
In-Reply-To: <a06240801c7a3ab51021b@[10.31.200.157]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ire] High level requirements for Internet Registration DataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Feb 2010 07:19:26 -0000

On 19.02.10 04:49, Edward Lewis wrote:
> The policies, I think that is open for debate.  I'm not questioning 
> the statement here, but I am not convinced whether the policies are in 
> the escrow or not.  It might be that the "goal is to reconstitute the 
> registry" is an overstatement of what we need to be able to achieve.
In my opinion, this is the most important point, that should be 
discussed before creating any working group to handle any design task.

What is the purpose of the escrow data? So far, there have been two 
opinions:

1. Registry data should be sufficient to facilitate takeover of the 
registry. With possible change in business practices. Apparently, the 
zonefile itself is not. This is why, other mechanisms are sought.

2. Registry data should be sufficient to restore the state of the 
registry in case of failure, with the goal that registry users 
(registrars, direct registrant interface, others) is not affected.

I would like to point out, that in some countries there are laws that 
govern 'database ownership'. It may be unlawful to allow third party to 
obtain and operate whatever database, without prior consent (and what 
not else, according to the law). This makes the first option, although 
very much desired by some, unlikely to happen in this world. No matter, 
how ICANN is trying to enforce it.

Clarifying this issue will help greatly focus on appropriate data model.

Daniel Kalchev
Register.BG

From jaap@bartok.nlnetlabs.nl  Fri Feb 19 01:39:16 2010
Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 518BE28C1F5 for <ire@core3.amsl.com>; Fri, 19 Feb 2010 01:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level: 
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id csZ74j0ukKAg for <ire@core3.amsl.com>; Fri, 19 Feb 2010 01:39:15 -0800 (PST)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by core3.amsl.com (Postfix) with ESMTP id 34A2628C148 for <ire@ietf.org>; Fri, 19 Feb 2010 01:39:14 -0800 (PST)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id o1J9eqCq027164 for <ire@ietf.org>; Fri, 19 Feb 2010 10:40:52 +0100 (CET) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201002190940.o1J9eqCq027164@bartok.nlnetlabs.nl>
To: ire@ietf.org
In-reply-to: <a06240801c7a3ab51021b@[10.31.200.157]> 
References: <C7A00530.25A1%francisco.arias@icann.org><201002171115.o1HBFXjU086431@bart ok.nlnetlabs.nl> <5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk> <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local> <a06240801c7a3ab51021b@[10.31.200.157]>
Comments: In-reply-to Edward Lewis <Ed.Lewis@neustar.biz> message dated "Thu, 18 Feb 2010 21:49:09 -0500."
Date: Fri, 19 Feb 2010 10:40:52 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.3 (bartok.nlnetlabs.nl [127.0.0.1]); Fri, 19 Feb 2010 10:40:52 +0100 (CET)
Subject: Re: [ire] High level requirements for Internet Registration DataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Feb 2010 09:39:16 -0000

    The policies, I think that is open for debate.  I'm not questioning
    the statement here, but I am not convinced whether the policies
    are in the escrow or not.  It might be that the "goal is to
    reconstitute the registry" is an overstatement of what we need
    to be able to achieve.

Yes, it is open for debate and needs to be debated. It should be
clear what escrow will give you and what not. In various circles
data escrow is often seen as the silver bullet which will fix (all
possible) registry failures.

I really won't like to see that this effort creates the wrong
expectations.

	jaap

From JGould@verisign.com  Fri Feb 19 06:17:47 2010
Return-Path: <JGould@verisign.com>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15A3D28C1D3 for <ire@core3.amsl.com>; Fri, 19 Feb 2010 06:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.833
X-Spam-Level: 
X-Spam-Status: No, score=-1.833 tagged_above=-999 required=5 tests=[AWL=2.769,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_82=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63ViGqJMlNxg for <ire@core3.amsl.com>; Fri, 19 Feb 2010 06:17:40 -0800 (PST)
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74]) by core3.amsl.com (Postfix) with ESMTP id 1EC6228C1EE for <ire@ietf.org>; Fri, 19 Feb 2010 06:17:40 -0800 (PST)
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id o1JEDfXU001911;  Fri, 19 Feb 2010 09:13:41 -0500
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Feb 2010 09:19:19 -0500
Received: from 10.131.29.63 ([10.131.29.63]) by dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) with Microsoft Exchange Server HTTP-DAV ;  Fri, 19 Feb 2010 14:19:18 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Fri, 19 Feb 2010 09:19:14 -0500
From: James Gould <jgould@verisign.com>
To: Daniel Kalchev <daniel@digsys.bg>, <ire@ietf.org>
Message-ID: <C7A40812.3782A%jgould@verisign.com>
Thread-Topic: [ire] High level requirements for Internet RegistrationDataEscrow
Thread-Index: AcqxNCE//R9K/5QxRRy9vpQuIH0ePQAOmIAO
In-Reply-To: <4B7E3BDC.6060908@digsys.bg>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3349415955_50040525"
X-OriginalArrivalTime: 19 Feb 2010 14:19:19.0674 (UTC) FILETIME=[86A1A5A0:01CAB16E]
Subject: Re: [ire] High level requirements for Internet RegistrationDataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Feb 2010 14:17:47 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3349415955_50040525
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Daniel ,

It sounds like option #2 is an extension of option #1, where restoration of
the registry without impact to clients means that the data is sufficient to
facilitate takeover of the registry.  I believe that the goal of the escrow
is to deposit the critical sponsorship information so that another registry
could be created based on the data.  Items like business policies and other
features built into the software of the original registry I don=B9t believe i=
s
part of the data escrow.  Otherwise all of the source code and libraries
would have to escrowed as well, which I believe is out of scope.

--=20


JG=20

-------------------------------------------------------
James F. Gould
Principal Software Engineer
VeriSign Naming Services
jgould@verisign.com
Direct: 703.948.3271
Mobile: 703.628.7063

=20
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

Notice to Recipient:  This e-mail contains confidential, proprietary and/or
Registry  Sensitive information intended solely for the recipient and, thus
may not be  retransmitted, reproduced or disclosed without the prior writte=
n
consent of  VeriSign Naming and Directory Services.  If you have received
this e-mail message in error, please notify the sender immediately by
telephone or reply e-mail and destroy the original message without making a
copy.  Thank you.



From: Daniel Kalchev <daniel@digsys.bg>
Date: Fri, 19 Feb 2010 02:21:00 -0500
To: <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet
RegistrationDataEscrow




On 19.02.10 04:49, Edward Lewis wrote:
> The policies, I think that is open for debate.  I'm not questioning
> the statement here, but I am not convinced whether the policies are in
> the escrow or not.  It might be that the "goal is to reconstitute the
> registry" is an overstatement of what we need to be able to achieve.
In my opinion, this is the most important point, that should be
discussed before creating any working group to handle any design task.

What is the purpose of the escrow data? So far, there have been two
opinions:

1. Registry data should be sufficient to facilitate takeover of the
registry. With possible change in business practices. Apparently, the
zonefile itself is not. This is why, other mechanisms are sought.

2. Registry data should be sufficient to restore the state of the
registry in case of failure, with the goal that registry users
(registrars, direct registrant interface, others) is not affected.

I would like to point out, that in some countries there are laws that
govern 'database ownership'. It may be unlawful to allow third party to
obtain and operate whatever database, without prior consent (and what
not else, according to the law). This makes the first option, although
very much desired by some, unlikely to happen in this world. No matter,
how ICANN is trying to enforce it.

Clarifying this issue will help greatly focus on appropriate data model.

Daniel Kalchev
Register.BG
_______________________________________________
ire mailing list
ire@ietf.org
https://www.ietf.org/mailman/listinfo/ire



--B_3349415955_50040525
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [ire] High level requirements for Internet RegistrationDataEscro=
w</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>Daniel ,<BR>
<BR>
It sounds like option #2 is an extension of option #1, where restoration of=
 the registry without impact to clients means that the data is sufficient to=
 facilitate takeover of the registry. &nbsp;I believe that the goal of the e=
scrow is to deposit the critical sponsorship information so that another reg=
istry could be created based on the data. &nbsp;Items like business policies=
 and other features built into the software of the original registry I don&#=
8217;t believe is part of the data escrow. &nbsp;Otherwise all of the source=
 code and libraries would have to escrowed as well, which I believe is out o=
f scope. &nbsp;&nbsp;<BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN S=
TYLE=3D'font-size:9pt'><BR>
-- <BR>
<BR>
<BR>
JG <BR>
<BR>
</SPAN></FONT><FONT COLOR=3D"#800000"><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-si=
ze:7.5pt'>-------------------------------------------------------<BR>
</SPAN></FONT></FONT></FONT><FONT FACE=3D"Arial"><FONT COLOR=3D"#7F0000"><FONT =
SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'><B>James F. Gould<BR>
</B></SPAN></FONT></FONT><FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'><B><FO=
NT COLOR=3D"#4C4C4C">Principal Software Engineer<BR>
</FONT></B><FONT COLOR=3D"#4C4C4C">VeriSign Naming Services<BR>
</FONT></SPAN></FONT><FONT COLOR=3D"#1100EF"><FONT SIZE=3D"1"><SPAN STYLE=3D'font=
-size:9pt'><a href=3D"jgould@verisign.com">jgould@verisign.com</a><BR>
</SPAN></FONT></FONT><FONT SIZE=3D"1"><FONT COLOR=3D"#4C4C4C"><SPAN STYLE=3D'font=
-size:7.5pt'><B>Direct:</B> 703.948.3271<BR>
<B>Mobile:</B> 703.628.7063<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:7.5pt'><BR>
&nbsp;<BR>
<FONT COLOR=3D"#4C4C4C">21345 Ridgetop Circle<BR>
LS2-2-1<BR>
Dulles, VA 20166<BR>
</FONT><BR>
<FONT COLOR=3D"#7F0000"><B><I>Notice to Recipient: &nbsp;</I></B></FONT></SPA=
N><I><SPAN STYLE=3D'font-size:9pt'>This e-mail contains confidential, propriet=
ary and/or Registry &nbsp;Sensitive information intended solely for the reci=
pient and, thus may not be &nbsp;retransmitted, reproduced or disclosed with=
out the prior written consent of &nbsp;VeriSign Naming and Directory Service=
s. &nbsp;<B>If you have received &nbsp;this e-mail message in error, please =
notify the sender immediately by &nbsp;telephone or reply e-mail and destroy=
 the original message without making a &nbsp;copy.</B> &nbsp;Thank you.<BR>
</SPAN></I></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><S=
PAN STYLE=3D'font-size:11pt'><BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"><B>From: </B>Daniel Kalchev &lt;<a hr=
ef=3D"daniel@digsys.bg">daniel@digsys.bg</a>&gt;<BR>
<B>Date: </B>Fri, 19 Feb 2010 02:21:00 -0500<BR>
<B>To: </B>&lt;<a href=3D"ire@ietf.org">ire@ietf.org</a>&gt;<BR>
<B>Subject: </B>Re: [ire] High level requirements for Internet Registration=
DataEscrow<BR>
<BR>
<BR>
<BR>
<BR>
On 19.02.10 04:49, Edward Lewis wrote:<BR>
&gt; The policies, I think that is open for debate. &nbsp;I'm not questioni=
ng<BR>
&gt; the statement here, but I am not convinced whether the policies are in=
<BR>
&gt; the escrow or not. &nbsp;It might be that the &quot;goal is to reconst=
itute the<BR>
&gt; registry&quot; is an overstatement of what we need to be able to achie=
ve.<BR>
In my opinion, this is the most important point, that should be<BR>
discussed before creating any working group to handle any design task.<BR>
<BR>
What is the purpose of the escrow data? So far, there have been two<BR>
opinions:<BR>
<BR>
1. Registry data should be sufficient to facilitate takeover of the<BR>
registry. With possible change in business practices. Apparently, the<BR>
zonefile itself is not. This is why, other mechanisms are sought.<BR>
<BR>
2. Registry data should be sufficient to restore the state of the<BR>
registry in case of failure, with the goal that registry users<BR>
(registrars, direct registrant interface, others) is not affected.<BR>
<BR>
I would like to point out, that in some countries there are laws that<BR>
govern 'database ownership'. It may be unlawful to allow third party to<BR>
obtain and operate whatever database, without prior consent (and what<BR>
not else, according to the law). This makes the first option, although<BR>
very much desired by some, unlikely to happen in this world. No matter,<BR>
how ICANN is trying to enforce it.<BR>
<BR>
Clarifying this issue will help greatly focus on appropriate data model.<BR=
>
<BR>
Daniel Kalchev<BR>
Register.BG<BR>
_______________________________________________<BR>
ire mailing list<BR>
<a href=3D"ire@ietf.org">ire@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/ire">https://www.ietf.org/ma=
ilman/listinfo/ire</a><BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3349415955_50040525--


From Marc.Groeneweg@sidn.nl  Fri Feb 19 06:26:59 2010
Return-Path: <Marc.Groeneweg@sidn.nl>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECBFE28C1E3 for <ire@core3.amsl.com>; Fri, 19 Feb 2010 06:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level: 
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,  HTML_MESSAGE=0.001, J_CHICKENPOX_82=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uz1UMJFWX8yz for <ire@core3.amsl.com>; Fri, 19 Feb 2010 06:26:52 -0800 (PST)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [94.198.152.69]) by core3.amsl.com (Postfix) with ESMTP id D3C753A6A3D for <ire@ietf.org>; Fri, 19 Feb 2010 06:26:51 -0800 (PST)
Received: from sidn.nl ([192.168.2.12]) by ede1-kamx.sidn.nl  with ESMTP id o1JESaQ0027631 for <ire@ietf.org>; Fri, 19 Feb 2010 15:28:36 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAB16F.D2CE7D73"
Date: Fri, 19 Feb 2010 15:28:36 +0100
Message-ID: <850A39016FA57A4887C0AA3C8085F94901BE7349@KAEVS1.SIDN.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ire] High level requirements for InternetRegistrationDataEscrow
Thread-Index: AcqxNCE//R9K/5QxRRy9vpQuIH0ePQAOmIAOAAAYEPA=
References: <C7A40812.3782A%jgould@verisign.com>
From: "Marc Groeneweg" <Marc.Groeneweg@sidn.nl>
To: <ire@ietf.org>
Subject: Re: [ire] High level requirements for InternetRegistrationDataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Feb 2010 14:27:00 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAB16F.D2CE7D73
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

=20

I tend to incline with the statement of James. Only the data should be
escrowed, not the policies built into the software/processes. When one
wants to ensure this, separate Escrow agreements should be made,
regarding the software and procedures needed to support those policies.
So, it's the question of the data. You have the information necessary to
create a zonefile. No discussion on this I guess ;-) The sponsoring
information is also needed (who is the original source concerning the
domainname).

=20

Extensible (or needed?) is other information like registrant, admin and
tech contacts (at least). I see a need for an extension for legal
attributes (or any other attributes a TLD has a need for)  within the
DataEscrow.

=20

Regards,

Marc

=20

From: ire-bounces@ietf.org [mailto:ire-bounces@ietf.org] On Behalf Of
James Gould
Sent: vrijdag 19 februari 2010 15:19
To: Daniel Kalchev; ire@ietf.org
Subject: Re: [ire] High level requirements for
InternetRegistrationDataEscrow

=20

Daniel ,

It sounds like option #2 is an extension of option #1, where restoration
of the registry without impact to clients means that the data is
sufficient to facilitate takeover of the registry.  I believe that the
goal of the escrow is to deposit the critical sponsorship information so
that another registry could be created based on the data.  Items like
business policies and other features built into the software of the
original registry I don't believe is part of the data escrow.  Otherwise
all of the source code and libraries would have to escrowed as well,
which I believe is out of scope.  =20

--=20


JG=20

-------------------------------------------------------
James F. Gould
Principal Software Engineer
VeriSign Naming Services
jgould@verisign.com
Direct: 703.948.3271
Mobile: 703.628.7063

=20
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

Notice to Recipient:  This e-mail contains confidential, proprietary
and/or Registry  Sensitive information intended solely for the recipient
and, thus may not be  retransmitted, reproduced or disclosed without the
prior written consent of  VeriSign Naming and Directory Services.  If
you have received  this e-mail message in error, please notify the
sender immediately by  telephone or reply e-mail and destroy the
original message without making a  copy.  Thank you.



________________________________

From: Daniel Kalchev <daniel@digsys.bg>
Date: Fri, 19 Feb 2010 02:21:00 -0500
To: <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet
RegistrationDataEscrow




On 19.02.10 04:49, Edward Lewis wrote:
> The policies, I think that is open for debate.  I'm not questioning
> the statement here, but I am not convinced whether the policies are in
> the escrow or not.  It might be that the "goal is to reconstitute the
> registry" is an overstatement of what we need to be able to achieve.
In my opinion, this is the most important point, that should be
discussed before creating any working group to handle any design task.

What is the purpose of the escrow data? So far, there have been two
opinions:

1. Registry data should be sufficient to facilitate takeover of the
registry. With possible change in business practices. Apparently, the
zonefile itself is not. This is why, other mechanisms are sought.

2. Registry data should be sufficient to restore the state of the
registry in case of failure, with the goal that registry users
(registrars, direct registrant interface, others) is not affected.

I would like to point out, that in some countries there are laws that
govern 'database ownership'. It may be unlawful to allow third party to
obtain and operate whatever database, without prior consent (and what
not else, according to the law). This makes the first option, although
very much desired by some, unlikely to happen in this world. No matter,
how ICANN is trying to enforce it.

Clarifying this issue will help greatly focus on appropriate data model.

Daniel Kalchev
Register.BG
_______________________________________________
ire mailing list
ire@ietf.org
https://www.ietf.org/mailman/listinfo/ire


------_=_NextPart_001_01CAB16F.D2CE7D73
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: [ire] High level requirements for Internet =
RegistrationDataEscrow</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DNL link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>All,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I tend to incline with the statement of James. Only the =
data
should be escrowed, not the policies built into the software/processes. =
When
one wants to ensure this, separate Escrow agreements should be made, =
regarding
the software and procedures needed to support those policies. So, =
it&#8217;s
the question of the data. You have the information necessary to create a
zonefile. No discussion on this I guess ;-) The sponsoring information =
is also
needed (who is the original source concerning the =
domainname).<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Extensible (or needed?) is other information like =
registrant,
admin and tech contacts (at least). I see a need for an extension for =
legal
attributes (or any other attributes a TLD has a need for) &nbsp;within =
the DataEscrow.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Marc<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> ire-bounces@ietf.org
[mailto:ire-bounces@ietf.org] <b>On Behalf Of </b>James Gould<br>
<b>Sent:</b> vrijdag 19 februari 2010 15:19<br>
<b>To:</b> Daniel Kalchev; ire@ietf.org<br>
<b>Subject:</b> Re: [ire] High level requirements for
InternetRegistrationDataEscrow<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif"'>Daniel ,<br>
<br>
It sounds like option #2 is an extension of option #1, where restoration =
of the
registry without impact to clients means that the data is sufficient to
facilitate takeover of the registry. &nbsp;I believe that the goal of =
the
escrow is to deposit the critical sponsorship information so that =
another
registry could be created based on the data. &nbsp;Items like business =
policies
and other features built into the software of the original registry I
don&#8217;t believe is part of the data escrow. &nbsp;Otherwise all of =
the
source code and libraries would have to escrowed as well, which I =
believe is
out of scope. &nbsp;&nbsp;<br>
</span><span =
style=3D'font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
-- <br>
<br>
<br>
JG <br>
<br>
</span><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";
color:maroon'>-------------------------------------------------------<br>=

</span><b><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:#7F0000'>James F. Gould<br>
</span></b><b><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:#4C4C4C'>Principal Software Engineer<br>
</span></b><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:#4C4C4C'>VeriSign Naming Services<br>
</span><span style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";
color:#1100EF'><a =
href=3D"jgould@verisign.com">jgould@verisign.com</a><br>
</span><b><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";
color:#4C4C4C'>Direct:</span></b><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";
color:#4C4C4C'> 703.948.3271<br>
<b>Mobile:</b> 703.628.7063<br>
</span><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'><br>
&nbsp;<br>
<span style=3D'color:#4C4C4C'>21345 Ridgetop Circle<br>
LS2-2-1<br>
Dulles, VA 20166<br>
</span><br>
<b><i><span style=3D'color:#7F0000'>Notice to Recipient: =
&nbsp;</span></i></b></span><i><span
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif"'>This e-mail =
contains
confidential, proprietary and/or Registry &nbsp;Sensitive information =
intended
solely for the recipient and, thus may not be &nbsp;retransmitted, =
reproduced
or disclosed without the prior written consent of &nbsp;VeriSign Naming =
and
Directory Services. &nbsp;<b>If you have received &nbsp;this e-mail =
message in
error, please notify the sender immediately by &nbsp;telephone or reply =
e-mail
and destroy the original message without making a &nbsp;copy.</b> =
&nbsp;Thank
you.<br>
<br>
</span></i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>

<hr size=3D3 width=3D"95%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif"'>From: </span></b><span =
style=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif"'>Daniel Kalchev &lt;<a
href=3D"daniel@digsys.bg">daniel@digsys.bg</a>&gt;<br>
<b>Date: </b>Fri, 19 Feb 2010 02:21:00 -0500<br>
<b>To: </b>&lt;<a href=3D"ire@ietf.org">ire@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: [ire] High level requirements for Internet
RegistrationDataEscrow<br>
<br>
<br>
<br>
<br>
On 19.02.10 04:49, Edward Lewis wrote:<br>
&gt; The policies, I think that is open for debate. &nbsp;I'm not =
questioning<br>
&gt; the statement here, but I am not convinced whether the policies are =
in<br>
&gt; the escrow or not. &nbsp;It might be that the &quot;goal is to
reconstitute the<br>
&gt; registry&quot; is an overstatement of what we need to be able to =
achieve.<br>
In my opinion, this is the most important point, that should be<br>
discussed before creating any working group to handle any design =
task.<br>
<br>
What is the purpose of the escrow data? So far, there have been two<br>
opinions:<br>
<br>
1. Registry data should be sufficient to facilitate takeover of the<br>
registry. With possible change in business practices. Apparently, =
the<br>
zonefile itself is not. This is why, other mechanisms are sought.<br>
<br>
2. Registry data should be sufficient to restore the state of the<br>
registry in case of failure, with the goal that registry users<br>
(registrars, direct registrant interface, others) is not affected.<br>
<br>
I would like to point out, that in some countries there are laws =
that<br>
govern 'database ownership'. It may be unlawful to allow third party =
to<br>
obtain and operate whatever database, without prior consent (and =
what<br>
not else, according to the law). This makes the first option, =
although<br>
very much desired by some, unlikely to happen in this world. No =
matter,<br>
how ICANN is trying to enforce it.<br>
<br>
Clarifying this issue will help greatly focus on appropriate data =
model.<br>
<br>
Daniel Kalchev<br>
Register.BG<br>
_______________________________________________<br>
ire mailing list<br>
<a href=3D"ire@ietf.org">ire@ietf.org</a><br>
<a =
href=3D"https://www.ietf.org/mailman/listinfo/ire">https://www.ietf.org/m=
ailman/listinfo/ire</a></span><o:p></o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01CAB16F.D2CE7D73--

From Stephen.Morris@nominet.org.uk  Fri Feb 19 07:43:25 2010
Return-Path: <Stephen.Morris@nominet.org.uk>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCB4F3A7F80 for <ire@core3.amsl.com>; Fri, 19 Feb 2010 07:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.423
X-Spam-Level: 
X-Spam-Status: No, score=-4.423 tagged_above=-999 required=5 tests=[AWL=2.175,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lXIRehNwioWR for <ire@core3.amsl.com>; Fri, 19 Feb 2010 07:43:24 -0800 (PST)
Received: from mx3.nominet.org.uk (mx3.nominet.org.uk [213.248.199.23]) by core3.amsl.com (Postfix) with ESMTP id 6F2583A7F71 for <ire@ietf.org>; Fri, 19 Feb 2010 07:43:23 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:In-Reply-To:References:To:Cc: MIME-Version:Subject:X-Mailer:Message-ID:From:Date: X-MIMETrack:Content-Type; b=HQoK5gJ72VKpnc+l6URThTjRxM058dEZbkMhlHmQH6jGsiMUK9v9Kq5q 8zuskJoqLI0YpvUzpD/VLyxXg+tNM5kx/4ZKkcLfjSFhRyzHYlC06BXIp HJH9MQv1F7/xbzv;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Stephen.Morris@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1266594311; x=1298130311; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Stephen.Morris@nominet.org.uk|Subject:=20Re:=20[ ire]=20High=20level=20requirements=20for=20Internet=20Reg istration=20Data=20Escrow|Date:=20Fri,=2019=20Feb=202010 =2015:45:08=20+0000|Message-ID:=20<OF02C78962.17BD7A63-ON 802576CF.00557981-802576CF.00568864@nominet.org.uk>|To: =20Ed.Lewis@neustar.biz|Cc:=20ire@ietf.org|MIME-Version: =201.0|In-Reply-To:=20<a06240802c7a2fae2b7e0@[10.31.200.1 66]>|References:=20<C79E5C2C.2544%francisco.arias@icann.o rg>=20<a06240802c7a2fae2b7e0@[10.31.200.166]>; bh=9r6ryVbKDD2T/gJdBBSqb4qmvB/c/6/B6M9C9+HJhL4=; b=YqMeBHjho6/YM6GB1iVqtFbentJ6f+XFp4qGfaOTP6u7px1c1HTsRtFS 0tI7dchbnfI1Z+uo9MWVGcoL122mu6eKXMTVpLf1tqKSTKx9+C3/JeihC lXi13kIlVWUs+2m;
X-IronPort-AV: E=Sophos;i="4.49,504,1262563200"; d="scan'208";a="21881575"
Received: from notes1.nominet.org.uk ([213.248.197.128]) by mx3.nominet.org.uk with ESMTP; 19 Feb 2010 15:45:09 +0000
In-Reply-To: <a06240802c7a2fae2b7e0@[10.31.200.166]>
References: <C79E5C2C.2544%francisco.arias@icann.org> <a06240802c7a2fae2b7e0@[10.31.200.166]>
To: Ed.Lewis@neustar.biz
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 8.5 December 05, 2008
Message-ID: <OF02C78962.17BD7A63-ON802576CF.00557981-802576CF.00568864@nominet.org.uk>
From: Stephen.Morris@nominet.org.uk
Date: Fri, 19 Feb 2010 15:45:08 +0000
X-MIMETrack: Serialize by Router on notes1/Nominet(Release 7.0.1FP1 | May 25, 2006) at 19/02/2010 03:45:09 PM, Serialize complete at 19/02/2010 03:45:09 PM
Content-Type: multipart/alternative; boundary="=_alternative 00568863802576CF_="
Cc: ire@ietf.org
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Feb 2010 15:43:25 -0000

This is a multipart message in MIME format.
--=_alternative 00568863802576CF_=
Content-Type: text/plain; charset="US-ASCII"

Edward Lewis <Ed.Lewis@neustar.biz> wrote on 18/02/2010 14:18:44:

> Perhaps it also depends on what one considers the database - but 
> there is billing information (account balances, stuff other than 
> expiration dates, etc.) that may be stored elsewhere.
> 
> I usually view a registry of consisting of the following roughly 
> defined interfaces and protocols:
> 
> Administrative -> Billing, legal support (think law enforcement...)
> Provisioning -> The registration "desk" (like EPP)
> Relying Party -> DNS (DN/RI-R), WhoIS other inspection protocols
> 
> The information needed to set up these "external" interfaces are also 
> needed - if the goal is to reconstitute and continue operations and 
> not just "re-host the database."

So the first question seems to be "What are the minimum set of services 
(and level of services) that an organisation can offer and still be 
classed as a registry?".  From this we can derive the core data we need to 
store in escrow.

As a first step, focusing on what we can't do without may be easier than 
reaching a conclusion on what we could do with.

Stephen
--=_alternative 00568863802576CF_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>Edward Lewis &lt;Ed.Lewis@neustar.biz&gt; wrote on 18/02/2010
14:18:44:<br>
<br>
&gt; Perhaps it also depends on what one considers the database - but <br>
&gt; there is billing information (account balances, stuff other than <br>
&gt; expiration dates, etc.) that may be stored elsewhere.<br>
&gt; <br>
&gt; I usually view a registry of consisting of the following roughly <br>
&gt; defined interfaces and protocols:<br>
&gt; <br>
&gt; Administrative -&gt; Billing, legal support (think law enforcement...)<br>
&gt; Provisioning -&gt; The registration &quot;desk&quot; (like EPP)<br>
&gt; Relying Party -&gt; DNS (DN/RI-R), WhoIS other inspection protocols<br>
&gt; <br>
&gt; The information needed to set up these &quot;external&quot; interfaces
are also <br>
&gt; needed - if the goal is to reconstitute and continue operations and
<br>
&gt; not just &quot;re-host the database.&quot;<br>
</font></tt>
<br><tt><font size=2>So the first question seems to be &quot;What are the
minimum set of services (and level of services) that an organisation can
offer and still be classed as a registry?&quot;. &nbsp;From this we can
derive the core data we need to store in escrow.</font></tt>
<br>
<br><tt><font size=2>As a first step, focusing on what we can't do without
may be easier than reaching a conclusion on what we could do with.</font></tt>
<br>
<br><tt><font size=2>Stephen</font></tt>
--=_alternative 00568863802576CF_=--

From cbbrowne@ca.afilias.info  Fri Feb 19 09:23:31 2010
Return-Path: <cbbrowne@ca.afilias.info>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E377428C317 for <ire@core3.amsl.com>; Fri, 19 Feb 2010 09:23:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_31=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K6HsKuxe2InC for <ire@core3.amsl.com>; Fri, 19 Feb 2010 09:23:30 -0800 (PST)
Received: from tor-gateway.afilias.info (tor-gateway.afilias.info [199.15.87.4]) by core3.amsl.com (Postfix) with ESMTP id BC15F28C2BE for <ire@ietf.org>; Fri, 19 Feb 2010 09:23:30 -0800 (PST)
Received: from [10.10.68.46] (helo=dba2.int.libertyrms.com ident=postfix) by tor-gateway.afilias.info with smtp (Exim 4.69) (envelope-from <cbbrowne@ca.afilias.info>) id 1NiWb3-0007Jb-6r; Fri, 19 Feb 2010 12:24:57 -0500
Received: by dba2.int.libertyrms.com (Postfix, from userid 1000) id 0C9996B4019; Fri, 19 Feb 2010 12:24:57 -0500 (EST)
From: Christopher Browne <cbbrowne@ca.afilias.info>
To: James Gould <jgould@verisign.com>
Organization: Afilias Canada - Architecture Department
References: <C7A40812.3782A%jgould@verisign.com>
Date: Fri, 19 Feb 2010 12:24:56 -0500
In-Reply-To: <C7A40812.3782A%jgould@verisign.com> (James Gould's message of "Fri, 19 Feb 2010 09:19:14 -0500")
Message-ID: <87iq9t5eaf.fsf@ca.afilias.info>
User-Agent: Gnus/5.110009 (No Gnus v0.9) XEmacs/21.4.22 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ire@ietf.org
Subject: Re: [ire] High level requirements for Internet RegistrationDataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Feb 2010 17:23:32 -0000

James Gould <jgould@verisign.com> writes:
> It sounds like option #2 is an extension of option #1, where
> restoration of the registry without impact to clients means that the
> data is sufficient to facilitate takeover of the registry.  I believe
> that the goal of the escrow is to deposit the critical sponsorship
> information so that another registry could be created based on the
> data.  Items like business policies and other features built into the
> software of the original registry I don?t believe is part of the data
> escrow.  Otherwise all of the source code and libraries would have to
> escrowed as well, which I believe is out of scope.

I'm inclined to go even a little further than that.

I'm don't think that "without impact to clients" is particularly
plausible.  Nitpicking a little bit, if there's a new service provider,
then:

 - IP addresses will have changed for services.

 - authentication information will need to change so that clients are
   assured that they're dealing with "NewOperatorCo," and not
   "OldFailedOperatorCo."

 - clients are dealing with a different legal entity, and hence it is
   likely to be rather important for there to be *new* legal contracts
   and such.

In that there has been a catastrophic failure, clearly something
undesirable has happened, and it is undesirable to assume carriage of
*every* detail of business policy over to the new operator, as the
catastrophe may well have resulted from some aspects of those policies.

This isn't a "seamless" change - nay, it's pretty important to validate
that expected "seams" have been observed, otherwise there are risks of
fraud.

I don't imagine that much of the "legacy" billing information would be
able to apply to the new organization.  A new registry operator, being a
separate legal entity, needs to establish *new* contractual arrangements
with the clients.  In view of that, while it is essential for there to
be sufficient client data to be able to identify and contact the
clients, I would expect other sorts of "billing data" to effectively be
invalidated by a takeover.
-- 
(format nil "~S@~S" "cbbrowne" "ca.afilias.info")
Christopher Browne
Database Architect
Afilias Canada

From bernie@ietf.hoeneisen.ch  Sat Feb 20 03:00:59 2010
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DE4028C0D0 for <ire@core3.amsl.com>; Sat, 20 Feb 2010 03:00:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9Lm5blHsRNE for <ire@core3.amsl.com>; Sat, 20 Feb 2010 03:00:58 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id A96CC3A7AC4 for <ire@ietf.org>; Sat, 20 Feb 2010 03:00:58 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1Nin6k-0004hX-2Y for ire@ietf.org; Sat, 20 Feb 2010 12:02:46 +0100
Date: Sat, 20 Feb 2010 12:02:46 +0100 (CET)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: ire@ietf.org
Message-ID: <alpine.DEB.2.00.1002201150390.16536@softronics.hoeneisen.ch>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Subject: [ire] Separation of data sets / another aspect (testability)
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 20 Feb 2010 11:00:59 -0000

Hi,

After reading all the emails another aspect crossed my mind:

- It is (hopefully) unlikely that we can properly test the
   restoration of a Registry in real life. So we can never
   conclusively proove what is the set of data absolutely needed in
   case of restoration. This means implementations will be based on
   assumptions, as we can never test them under real circumstances.

- As a consequence we should logically separate the set of data
   we believe is absolutely needed for restoring Registry
   operations and any additional data that might be of importance.
   The later should be escrowed too, although unlikely to ever be
   used.

Thus, there should be one set of data to be specified "both
ways" (tuned for fast restoration, primary usage), and another
set of data "one way" (tuned for storage/retrieval, secondary
usage).
[Whether of not the "tuning" matters at the end of the day is FFS.]

The former can be tested to a certain extent (at least I hope so... ;-) ), 
the latter might get too complex for proper testing.


cheers,
  Bernie

From bortzmeyer@nic.fr  Mon Feb 22 01:00:20 2010
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBC593A764F for <ire@core3.amsl.com>; Mon, 22 Feb 2010 01:00:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.601
X-Spam-Level: 
X-Spam-Status: No, score=-4.601 tagged_above=-999 required=5 tests=[AWL=-1.633, BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, SARE_MONEYTERMS=0.681]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLONtmME7H+U for <ire@core3.amsl.com>; Mon, 22 Feb 2010 01:00:19 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id 3E4CB3A7C1F for <ire@ietf.org>; Mon, 22 Feb 2010 01:00:19 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 979AF1C010B; Mon, 22 Feb 2010 09:57:15 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 92F4D1C00FE; Mon, 22 Feb 2010 09:57:15 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay1.nic.fr (Postfix) with ESMTP id 907B2A1DE36; Mon, 22 Feb 2010 09:57:15 +0100 (CET)
Date: Mon, 22 Feb 2010 09:57:15 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Daniel Kalchev <daniel@digsys.bg>
Message-ID: <20100222085715.GA16317@nic.fr>
References: <5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk> <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local> <a06240801c7a3ab51021b@[10.31.200.157]> <4B7E3BDC.6060908@digsys.bg>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B7E3BDC.6060908@digsys.bg>
X-Operating-System: Debian GNU/Linux 5.0.4
X-Kernel: Linux 2.6.26-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: ire@ietf.org
Subject: Re: [ire] High level requirements for Internet Registration DataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 22 Feb 2010 09:00:20 -0000

On Fri, Feb 19, 2010 at 09:21:00AM +0200,
 Daniel Kalchev <daniel@digsys.bg> wrote 
 a message of 36 lines which said:

> 1. Registry data should be sufficient to facilitate takeover of the
> registry. With possible change in business practices.

Yes, this is what escrow is for.

> Apparently, the zonefile itself is not.

Of course not. It lacks info about the registrants, for instance.

> 2. Registry data should be sufficient to restore the state of the
> registry in case of failure,

I do not really understand the difference between the two. For me,
there is "escrow" (allowing a *different* organisation to restore the
registry in face of a *business* failure) and "backup" (allowing the
*same* organisation to restore the registry in face of a *technical*
failure). Only escrow is on-topic here.

Whether the takeover was because of a hostile redelegation or because
of a bankruptcy or alien invasion is immaterial: escrowing always
assume that the old registry won't be here to help so the new registry
has only the escrowed data. (And, of course, being the IETF, we should
work on technical issues, not on political ones such as "should the
law mandate an escrow for the local ccTLD?")

> I would like to point out, that in some countries there are laws
> that govern 'database ownership'. It may be unlawful to allow third
> party to obtain and operate whatever database, without prior consent
> (and what not else, according to the law).

I work in such a country but I do not see your point. Escrowing is not
stealing data, it is storing data at a trusted third-party, to allow a
future registry to resume service. It is a frequent requirment for
TLDs (for instance, for .FR, it is a legal obligation, so that the
governement can start a new .FR registry, should the AFNIC employees
leave with the money, settle in Cayman Islands and drop the service).

> No matter, how ICANN is trying to enforce it.

ICANN is irrelevant here.

From daniel@digsys.bg  Mon Feb 22 05:44:20 2010
Return-Path: <daniel@digsys.bg>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0149D3A82F0 for <ire@core3.amsl.com>; Mon, 22 Feb 2010 05:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.736
X-Spam-Level: 
X-Spam-Status: No, score=-0.736 tagged_above=-999 required=5 tests=[AWL=-0.596, BAYES_20=-0.74, J_CHICKENPOX_82=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mcg8vXcrn0mL for <ire@core3.amsl.com>; Mon, 22 Feb 2010 05:44:18 -0800 (PST)
Received: from relay2.digsys.bg (varna.digsys.bg [192.92.129.9]) by core3.amsl.com (Postfix) with ESMTP id 6AD8E28C0E4 for <ire@ietf.org>; Mon, 22 Feb 2010 05:44:17 -0800 (PST)
Received: from dcave.digsys.bg (daniel@dcave.digsys.bg [192.92.129.5]) by relay2.digsys.bg (8.14.3/8.14.3) with ESMTP id o1MDkCc4072537 for <ire@ietf.org>; Mon, 22 Feb 2010 15:46:12 +0200 (EET) (envelope-from daniel@digsys.bg)
Message-ID: <4B828AA4.1080303@digsys.bg>
Date: Mon, 22 Feb 2010 15:46:12 +0200
From: Daniel Kalchev <daniel@digsys.bg>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100210 Thunderbird/3.0.1
MIME-Version: 1.0
To: ire@ietf.org
References: <C7A40812.3782A%jgould@verisign.com> <87iq9t5eaf.fsf@ca.afilias.info>
In-Reply-To: <87iq9t5eaf.fsf@ca.afilias.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ire] High level requirements for Internet	RegistrationDataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 22 Feb 2010 13:44:20 -0000

I think we should avoid mixing 'data' with 'business practices'. The 
escrow is about data.

Whatever the reasons for failure of entity A, it's operation should be 
restored by entity B 'fully'.

Here is the problem: we don't have any definition of what the particular 
registry does.

Therefore 'keep the database license' and 'we don't need any billing 
data' may be both valid, even at the same time.

either settle on the minimum necessary to operate an registry (whether 
DNS registry or other, doesn't matter)

On 19.02.10 19:24, Christopher Browne wrote:
>
> I'm don't think that "without impact to clients" is particularly
> plausible.

This is what is most desirable. If it can be achieved, depends on not 
only having good enough specifications, but also on uncertain factors, 
such as good will and diligence.

>   - IP addresses will have changed for services.
>
>    
These days people use domain names. So this might not be valid argument.

>   - authentication information will need to change so that clients are
>     assured that they're dealing with "NewOperatorCo," and not
>     "OldFailedOperatorCo."
>
>    
Yes, and no. It all depends on the 'business practice' of the new 
operator and should be outside of the scope of this working group.
>   - clients are dealing with a different legal entity, and hence it is
>     likely to be rather important for there to be *new* legal contracts
>     and such.
>    
Same as above. There might not be any legal contract in the first place 
at all. Or, like most mass services, the registry might operate under 
General Terms and Conditions.
> I don't imagine that much of the "legacy" billing information would be
> able to apply to the new organization.  A new registry operator, being a
> separate legal entity, needs to establish *new* contractual arrangements
> with the clients.  In view of that, while it is essential for there to
> be sufficient client data to be able to identify and contact the
> clients, I would expect other sorts of "billing data" to effectively be
> invalidated by a takeover.
>    
Correct. But this does not mean we should eliminate the 'billing data' 
property. Whether or not the new operator will use this data is not 
important. They may no use (parts of) it even out of ignorance.

What worries me however, is we spend more time discussing non-technical 
issues. :)


Best Regards,
Daniel Kalchev
Register.BG Ltd

From paul.hoffman@vpnc.org  Mon Feb 22 07:23:19 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A6CB28C1F1 for <ire@core3.amsl.com>; Mon, 22 Feb 2010 07:23:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.249
X-Spam-Level: 
X-Spam-Status: No, score=-5.249 tagged_above=-999 required=5 tests=[AWL=-0.692, BAYES_05=-1.11, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XOwqkJW5C1US for <ire@core3.amsl.com>; Mon, 22 Feb 2010 07:23:18 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id D435B28C1D8 for <ire@ietf.org>; Mon, 22 Feb 2010 07:23:18 -0800 (PST)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o1MFP4kq082634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Feb 2010 08:25:06 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240840c7a851cb883f@[10.20.30.158]>
In-Reply-To: <4B828AA4.1080303@digsys.bg>
References: <C7A40812.3782A%jgould@verisign.com> <87iq9t5eaf.fsf@ca.afilias.info> <4B828AA4.1080303@digsys.bg>
Date: Mon, 22 Feb 2010 07:25:02 -0800
To: Daniel Kalchev <daniel@digsys.bg>, ire@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [ire] High level requirements for Internet RegistrationDataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 22 Feb 2010 15:23:19 -0000

At 3:46 PM +0200 2/22/10, Daniel Kalchev wrote:
>I think we should avoid mixing 'data' with 'business practices'. The escrow is about data.

You can avoid mixing data with business practices, and still have both in an escrow object. Assuming that the object is encoded in a hierarchical format (JSON, ASN.1, XML, ...), you have one section be for data and one for business practices.

>From a spec standpoint, we can more tightly define the data part than the business practices part. Having said that, *both* parts should be fully extensible.

--Paul Hoffman, Director
--VPN Consortium

From vika@zadna.org.za  Mon Feb 22 23:49:20 2010
Return-Path: <vika@zadna.org.za>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BF4F3A7A59 for <ire@core3.amsl.com>; Mon, 22 Feb 2010 23:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.682
X-Spam-Level: 
X-Spam-Status: No, score=0.682 tagged_above=-999 required=5 tests=[BAYES_50=0.001, SARE_MONEYTERMS=0.681]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2+XxTiUd6Hsa for <ire@core3.amsl.com>; Mon, 22 Feb 2010 23:49:19 -0800 (PST)
Received: from relay31.internext.co.za (relay31.internext.co.za [209.62.121.99]) by core3.amsl.com (Postfix) with ESMTP id 5C1653A7929 for <ire@ietf.org>; Mon, 22 Feb 2010 23:49:16 -0800 (PST)
Received: from intele1.intelegence.co.za ([172.17.0.4]) by relay31.internext.co.za (8.14.3/8.14.3) with ESMTP id o1N7lV4P002828; Tue, 23 Feb 2010 09:47:34 +0200
Received: from VikaMpisaneGM ([10.2.1.46]) by intele1.intelegence.co.za (8.14.2/8.14.2) with ESMTP id o1N7o6wF017295; Tue, 23 Feb 2010 09:50:07 +0200
From: "Vika Mpisane" <vika@zadna.org.za>
To: "'Stephane Bortzmeyer'" <bortzmeyer@nic.fr>, "'Daniel Kalchev'" <daniel@digsys.bg>
References: <5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk>	<850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local>	<a06240801c7a3ab51021b@[10.31.200.157]>	<4B7E3BDC.6060908@digsys.bg> <20100222085715.GA16317@nic.fr>
In-Reply-To: <20100222085715.GA16317@nic.fr>
Date: Tue, 23 Feb 2010 09:50:08 +0200
Organization: .ZA Domain Name Authority
Message-ID: <014a01cab45c$d2328e80$7697ab80$@org.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqznQd3p2yC16BeQ86fNQqUGrI5dwAvp9MA
Content-Language: en-za
X-Scanned-By: MIMEDefang 2.67 on 10.2.1.3
Cc: ire@ietf.org
Subject: Re: [ire] High level requirements for Internet Registration	DataEscrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: vika@zadna.org.za
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Feb 2010 07:49:20 -0000

Sorry for my late comments to this interesting discussion. See below.


> -----Original Message-----
> From: Stephane Bortzmeyer [mailto:bortzmeyer@nic.fr]
> Sent: 22 February 2010 10:57 AM

> On Fri, Feb 19, 2010 at 09:21:00AM +0200,
>  Daniel Kalchev <daniel@digsys.bg> wrote
>  a message of 36 lines which said:
> 
> > 1. Registry data should be sufficient to facilitate takeover of the
> > registry. With possible change in business practices.
> 
> Yes, this is what escrow is for.
> 
> > Apparently, the zonefile itself is not.
> 
> Of course not. It lacks info about the registrants, for instance.
> 
> > 2. Registry data should be sufficient to restore the state of the
> > registry in case of failure,
> 
> I do not really understand the difference between the two. For me,
> there is "escrow" (allowing a *different* organisation to restore the
> registry in face of a *business* failure) and "backup" (allowing the
> *same* organisation to restore the registry in face of a *technical*
> failure). Only escrow is on-topic here.
> 
> Whether the takeover was because of a hostile redelegation or because
> of a bankruptcy or alien invasion is immaterial: escrowing always
> assume that the old registry won't be here to help so the new registry
> has only the escrowed data. (And, of course, being the IETF, we should
> work on technical issues, not on political ones such as "should the
> law mandate an escrow for the local ccTLD?")

I get your point here Stephane. As much as data escrow may be political,
depending on how you look at it, an entity like IETF would do well to
constrain itself to the technical how-tos & procedures. 
 

> > I would like to point out, that in some countries there are laws
> > that govern 'database ownership'. It may be unlawful to allow third
> > party to obtain and operate whatever database, without prior consent
> > (and what not else, according to the law).
> 
> I work in such a country but I do not see your point. Escrowing is not
> stealing data, it is storing data at a trusted third-party, to allow a
> future registry to resume service. It is a frequent requirment for
> TLDs (for instance, for .FR, it is a legal obligation, so that the
> governement can start a new .FR registry, should the AFNIC employees
> leave with the money, settle in Cayman Islands and drop the service).

I fully agree here as well. Data escrow is purely about data protection.
Typically, whatever a country's law says about database ownership, data will
still need to be escrowed. I'm from South Africa & there's an electronic
communications law that classifies certain databases as critical. Assuming
that .za registry database is critical, the law itself encourages data
protection measures, and I see escrow as being such a measure.

Regards,

Vika Mpisane
.ZA Domain Name Authority
Johannesburg, South Africa
+27 11 275 0082



From Ed.Lewis@neustar.biz  Tue Feb 23 10:12:47 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B853D3A84B2 for <ire@core3.amsl.com>; Tue, 23 Feb 2010 10:12:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level: 
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=0.525,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rWTF8JBz2CT1 for <ire@core3.amsl.com>; Tue, 23 Feb 2010 10:12:46 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 799BF3A8497 for <ire@ietf.org>; Tue, 23 Feb 2010 10:12:46 -0800 (PST)
Received: from Work-Laptop-2.dhcp.nanog.merit.net (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1NIEbIt075083; Tue, 23 Feb 2010 13:14:43 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [192.35.165.216] by Work-Laptop-2.dhcp.nanog.merit.net (PGP Universal service); Tue, 23 Feb 2010 12:14:49 -0500
X-PGP-Universal: processed; by Work-Laptop-2.dhcp.nanog.merit.net on Tue, 23 Feb 2010 12:14:49 -0500
Mime-Version: 1.0
Message-Id: <a06240801c7a9cad1f802@[192.35.165.216]>
Date: Tue, 23 Feb 2010 12:14:01 -0600
To: ire@ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: multipart/alternative; boundary="============_-945173607==_ma============"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: ed.lewis@neustar.biz
Subject: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Feb 2010 18:12:47 -0000

--============_-945173607==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Our slot, and the conflicts:

WEDNESDAY, March 24, 2010

1030-1130  Morning Session II

Registry Data Escrow/Internet Registration Escrow BOF
Access Node Control Protocol WG
Locator/ID Separation Protocol WG
Operations and Management Area Working Group WG
Data for Reachability of Inter/tra-NetworK SIP WG
Secure Inter-Domain Routing WG
Simple Authentication and Security Layer WG

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis             
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.
--============_-945173607==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>We're on the agenda of the
IETF</title></head><body>
<div>Our slot, and the conflicts:</div>
<div><br></div>
<div>WEDNESDAY, March 24, 2010</div>
<div><br></div>
<div>1030-1130&nbsp; Morning Session II</div>
<div><br></div>
<div>Registry Data Escrow/Internet Registration Escrow BOF</div>
<div>Access Node Control Protocol WG</div>
<div>Locator/ID Separation Protocol WG</div>
<div>Operations and Management Area Working Group WG</div>
<div>Data for Reachability of Inter/tra-NetworK SIP WG</div>
<div>Secure Inter-Domain Routing WG</div>
<div>Simple Authentication and Security Layer WG</div>
<div><br></div>
<x-sigsep><pre>-- 
</pre></x-sigsep>
<div
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<span
></span>-=-=-=-</div>
<div>Edward
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span>&nbsp;&nbsp;&nbsp;<br>
NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; You can
leave a voice message at +1-571-434-5468</div>
<div><br></div>
<div>As with IPv6, the problem with the deployment of frictionless
surfaces is</div>
<div>that they're not getting traction.</div>
</body>
</html>
--============_-945173607==_ma============--

From Ed.Lewis@neustar.biz  Tue Feb 23 10:23:38 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A23A3A84B3 for <ire@core3.amsl.com>; Tue, 23 Feb 2010 10:23:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.351,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFlFgX4qkHUT for <ire@core3.amsl.com>; Tue, 23 Feb 2010 10:23:37 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 75A7F3A8497 for <ire@ietf.org>; Tue, 23 Feb 2010 10:23:37 -0800 (PST)
Received: from Work-Laptop-2.dhcp.nanog.merit.net (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1NIPWlT075200; Tue, 23 Feb 2010 13:25:33 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [192.35.165.216] by Work-Laptop-2.dhcp.nanog.merit.net (PGP Universal service); Tue, 23 Feb 2010 12:25:39 -0500
X-PGP-Universal: processed; by Work-Laptop-2.dhcp.nanog.merit.net on Tue, 23 Feb 2010 12:25:39 -0500
Mime-Version: 1.0
Message-Id: <a06240804c7a9cc3d4d22@[192.35.165.216]>
In-Reply-To: <a06240801c7a3ab51021b@[10.31.200.157]>
References: <C7A00530.25A1%francisco.arias@icann.org><201002171115.o1HBFXjU086431@bart ok.nlnetlabs.nl>	<5CAB2052-D85A-4423-9C39-F840E1AB6130@insensate.co.uk> <850A39016FA57A4887C0AA3C8085F94901BE703E@KAEVS1.SIDN.local> <a06240801c7a3ab51021b@[10.31.200.157]>
Date: Tue, 23 Feb 2010 12:25:34 -0600
To: ire@ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: ed.lewis@neustar.biz
Subject: [ire] Are we focusing too much on registries?
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Feb 2010 18:23:38 -0000

At 21:49 -0500 2/18/10, Edward Lewis wrote:

>It might be that the "goal is to reconstitute the registry" is an
>overstatement of what we need to be able to achieve.

I think that the above statement might have caused us to miss something.

I do doubt that we want to escrow everything that is known by a 
registry (that includes policies and billing for examples).  What is 
misleading is that the applicability of the escrow "protocol" 
probably should be broader than registries - that is - including 
registrars (especially in thin models) and other involved parties.

So I'll throw the doors open on this, perhaps we want to look for the 
information needed to reconstitute the core knowledge of the 
registration entity elsewhere in case of failure.  It's not the 
replication of the entity (like one registry operator assuming the 
role for a registry who's operator has failed) but being able to keep 
stability in the Internet.

I'd also like to repeat that we might be looking outside of just the 
domain name registration activity on this.

OTOH, I am not saying that we want a universal vault that will hold 
RIR data and domain name registration data - just a format that is 
available.  And consider whether there are parallels between 
registrar/registry and LIR/RIR in all this.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From francisco.arias@icann.org  Wed Feb 24 00:27:12 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDF403A79B5 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.528
X-Spam-Level: 
X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOs-OZ9V7krc for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:27:12 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 34A753A7884 for <ire@ietf.org>; Wed, 24 Feb 2010 00:27:12 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Wed, 24 Feb 2010 00:29:17 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Edward Lewis <Ed.Lewis@neustar.biz>, "ire@ietf.org" <ire@ietf.org>
Date: Wed, 24 Feb 2010 00:29:16 -0800
Thread-Topic: [ire] We're on the agenda of the IETF
Thread-Index: Acq0tCY1qkWWEWKGRbiFp0n9MxS/RgAd01Sb
Message-ID: <C7AA235C.282F%francisco.arias@icann.org>
In-Reply-To: <a06240801c7a9cad1f802@[192.35.165.216]>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 24 Feb 2010 08:27:12 -0000

Shouldn=B9t we try to avoid conflicting with SIDR WG given the possible
interest from the RIR=B9s in Data Escrow?

__=20
Francisco



On 2/23/10 10:14 AM, "Edward Lewis" <Ed.Lewis@neustar.biz> wrote:

> Our slot, and the conflicts:
>=20
> WEDNESDAY, March 24, 2010
>=20
> 1030-1130  Morning Session II
>=20
> Registry Data Escrow/Internet Registration Escrow BOF
> Access Node Control Protocol WG
> Locator/ID Separation Protocol WG
> Operations and Management Area Working Group WG
> Data for Reachability of Inter/tra-NetworK SIP WG
> Secure Inter-Domain Routing WG
> Simple Authentication and Security Layer WG


From francisco.arias@icann.org  Wed Feb 24 00:41:47 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCFAD3A7A90 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:41:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level: 
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6F9c57GJ558 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:41:46 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id A88223A6A48 for <ire@ietf.org>; Wed, 24 Feb 2010 00:41:46 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Wed, 24 Feb 2010 00:43:52 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: "ire@ietf.org" <ire@ietf.org>
Date: Wed, 24 Feb 2010 00:43:48 -0800
Thread-Topic: [ire] Separation of data sets / another aspect (testability)
Thread-Index: AcqyHEyeSdPyOs22T3WR7uJ8DV4geADES6rs
Message-ID: <C7AA26C4.2834%francisco.arias@icann.org>
In-Reply-To: <alpine.DEB.2.00.1002201150390.16536@softronics.hoeneisen.ch>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7AA26C42834franciscoariasicannorg_"
MIME-Version: 1.0
Subject: Re: [ire] Separation of data sets / another aspect (testability)
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 24 Feb 2010 08:41:48 -0000

--_000_C7AA26C42834franciscoariasicannorg_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I agree with Bernie about the difficulty for testing but, maybe we could le=
arn from slightly similar experiences. For example there have been a few ca=
ses of TLDs that have been transitioned from one operator to another; .ORG =
and .CO come to my mind at this moment.

I know the aforementioned cases are not strictly compared to a transition i=
n which only escrowed data is available, but at least those who had the exp=
erience of rebuilding registry services of those TLDs may want to share the=
ir experiences about what data and policies (if any) were needed to rebuild=
.

__
Francisco



On 2/20/10 3:02 AM, "Bernie Hoeneisen" <bernie@ietf.hoeneisen.ch> wrote:

Hi,

After reading all the emails another aspect crossed my mind:

- It is (hopefully) unlikely that we can properly test the
   restoration of a Registry in real life. So we can never
   conclusively proove what is the set of data absolutely needed in
   case of restoration. This means implementations will be based on
   assumptions, as we can never test them under real circumstances.

- As a consequence we should logically separate the set of data
   we believe is absolutely needed for restoring Registry
   operations and any additional data that might be of importance.
   The later should be escrowed too, although unlikely to ever be
   used.

Thus, there should be one set of data to be specified "both
ways" (tuned for fast restoration, primary usage), and another
set of data "one way" (tuned for storage/retrieval, secondary
usage).
[Whether of not the "tuning" matters at the end of the day is FFS.]

The former can be tested to a certain extent (at least I hope so... ;-) ),
the latter might get too complex for proper testing.


cheers,
  Bernie
_______________________________________________
ire mailing list
ire@ietf.org
https://www.ietf.org/mailman/listinfo/ire


--_000_C7AA26C42834franciscoariasicannorg_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [ire] Separation of data sets / another aspect (testability)</TI=
TLE>
</HEAD>
<BODY>
<FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:12pt'>I agree with Bernie abo=
ut the difficulty for testing but, maybe we could learn from slightly simil=
ar experiences. For example there have been a few cases of TLDs that have b=
een transitioned from one operator to another; .ORG and .CO come to my mind=
 at this moment.<BR>
<BR>
I know the aforementioned cases are not strictly compared to a transition i=
n which only escrowed data is available, but at least those who had the exp=
erience of rebuilding registry services of those TLDs may want to share the=
ir experiences about what data and policies (if any) were needed to rebuild=
.<BR>
<BR>
__ <BR>
Francisco<BR>
<BR>
<BR>
<BR>
On 2/20/10 3:02 AM, &quot;Bernie Hoeneisen&quot; &lt;<a href=3D"bernie@ietf=
.hoeneisen.ch">bernie@ietf.hoeneisen.ch</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:12p=
t'>Hi,<BR>
<BR>
After reading all the emails another aspect crossed my mind:<BR>
<BR>
- It is (hopefully) unlikely that we can properly test the<BR>
&nbsp;&nbsp;&nbsp;restoration of a Registry in real life. So we can never<B=
R>
&nbsp;&nbsp;&nbsp;conclusively proove what is the set of data absolutely ne=
eded in<BR>
&nbsp;&nbsp;&nbsp;case of restoration. This means implementations will be b=
ased on<BR>
&nbsp;&nbsp;&nbsp;assumptions, as we can never test them under real circums=
tances.<BR>
<BR>
- As a consequence we should logically separate the set of data<BR>
&nbsp;&nbsp;&nbsp;we believe is absolutely needed for restoring Registry<BR=
>
&nbsp;&nbsp;&nbsp;operations and any additional data that might be of impor=
tance.<BR>
&nbsp;&nbsp;&nbsp;The later should be escrowed too, although unlikely to ev=
er be<BR>
&nbsp;&nbsp;&nbsp;used.<BR>
<BR>
Thus, there should be one set of data to be specified &quot;both<BR>
ways&quot; (tuned for fast restoration, primary usage), and another<BR>
set of data &quot;one way&quot; (tuned for storage/retrieval, secondary<BR>
usage).<BR>
[Whether of not the &quot;tuning&quot; matters at the end of the day is FFS=
.]<BR>
<BR>
The former can be tested to a certain extent (at least I hope so... ;-) ),<=
BR>
the latter might get too complex for proper testing.<BR>
<BR>
<BR>
cheers,<BR>
&nbsp;&nbsp;Bernie<BR>
_______________________________________________<BR>
ire mailing list<BR>
<a href=3D"ire@ietf.org">ire@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/ire">https://www.ietf.org/=
mailman/listinfo/ire</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C7AA26C42834franciscoariasicannorg_--

From robert@ripe.net  Wed Feb 24 00:51:38 2010
Return-Path: <robert@ripe.net>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C8493A6C40 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:51:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level: 
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DK-sFvg-Pr6e for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:51:37 -0800 (PST)
Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id 669BB3A6825 for <ire@ietf.org>; Wed, 24 Feb 2010 00:51:37 -0800 (PST)
Received: from ayeaye.ipv6.ripe.net ([2001:610:240:1::c100:167] helo=ayeaye.ripe.net) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <robert@ripe.net>) id 1NkCzw-0008NV-EK for ire@ietf.org; Wed, 24 Feb 2010 09:53:42 +0100
Received: from dog.ripe.net ([193.0.1.217] helo=Kistel-Mac.local) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <robert@ripe.net>) id 1NkCzw-0003AA-Bs for ire@ietf.org; Wed, 24 Feb 2010 09:53:36 +0100
Message-ID: <4B84E910.7000508@ripe.net>
Date: Wed, 24 Feb 2010 09:53:36 +0100
From: Robert Kisteleki <robert@ripe.net>
Organization: RIPE NCC
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "ire@ietf.org" <ire@ietf.org>
References: <C7AA235C.282F%francisco.arias@icann.org>
In-Reply-To: <C7AA235C.282F%francisco.arias@icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-RIPE-Signature: 72e00e6d7601fa19264e98abc238a27444709fe5e3f4a709f229dd9672dff0e1
X-RIPE-Spam-Level: ----
X-RIPE-Signature: 72e00e6d7601fa19264e98abc238a27444709fe5e3f4a709f229dd9672dff0e1
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 24 Feb 2010 08:51:38 -0000

Francisco Arias wrote:
> Shouldnąt we try to avoid conflicting with SIDR WG given the possible
> interest from the RIRąs in Data Escrow?

Yes, that would be much appreciated!

Robert


> __ 
> Francisco
> 
> 
> 
> On 2/23/10 10:14 AM, "Edward Lewis" <Ed.Lewis@neustar.biz> wrote:
> 
>> Our slot, and the conflicts:
>>
>> WEDNESDAY, March 24, 2010
>>
>> 1030-1130  Morning Session II
>>
>> Registry Data Escrow/Internet Registration Escrow BOF
>> Access Node Control Protocol WG
>> Locator/ID Separation Protocol WG
>> Operations and Management Area Working Group WG
>> Data for Reachability of Inter/tra-NetworK SIP WG
>> Secure Inter-Domain Routing WG
>> Simple Authentication and Security Layer WG
> 
> _______________________________________________
> ire mailing list
> ire@ietf.org
> https://www.ietf.org/mailman/listinfo/ire


From francisco.arias@icann.org  Wed Feb 24 00:58:05 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 957953A7C42 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level: 
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q37N5BlBaLio for <ire@core3.amsl.com>; Wed, 24 Feb 2010 00:58:04 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id CEBB23A7B46 for <ire@ietf.org>; Wed, 24 Feb 2010 00:58:04 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Wed, 24 Feb 2010 01:00:10 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: James Gould <jgould@verisign.com>, Edward Lewis <Ed.Lewis@neustar.biz>, "ire@ietf.org" <ire@ietf.org>
Date: Wed, 24 Feb 2010 01:00:08 -0800
Thread-Topic: [ire] BoFfing...
Thread-Index: AcqwqONgN5IuXdPXSgi/hTeJRWk5TQADuWNKAR3+n80=
Message-ID: <C7AA2A98.283B%francisco.arias@icann.org>
In-Reply-To: <C7A2D581.377E3%jgould@verisign.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ire] BoFfing...
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 24 Feb 2010 08:58:05 -0000

I fully agree with James, we should focus on what the current registry has
to escrow (as much as possible) and let conversions from thick to thin be a
problem for the successor registry.

__=20
Francisco



On 2/18/10 8:31 AM, "James Gould" <jgould@verisign.com> wrote:

> Ed,
>=20
>> One of the questions to consider, is the goal of the effort to:
>>    Allow a thick registry be reconstituted in a thin registry operator?
>=20
> I don=B9t believe we should consider the target operator system, but focu=
s on
> storing all of the provisioning data in a consistent and secure manor no
> matter what makes up the Registry system.  I agree that there should be s=
ome
> requirements around additional information that needs to be deposited to =
make
> the data usable for reconstituting a system, but I want to ensure that th=
e
> format is extensible, simple, and straight forward for a target operator =
to
> utilize.  For example, I wouldn=B9t want to not include information in th=
e data
> escrow because it is Registry specific and was not defined in the RFC.   =
The
> target operator should be able to count on at least an agreed upon subset=
 of
> information to work with. =20


From francisco.arias@icann.org  Wed Feb 24 01:08:18 2010
Return-Path: <francisco.arias@icann.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AD873A7929 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 01:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.54
X-Spam-Level: 
X-Spam-Status: No, score=-6.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHsH8wWeo1ke for <ire@core3.amsl.com>; Wed, 24 Feb 2010 01:08:17 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id BFD3C3A67AC for <ire@ietf.org>; Wed, 24 Feb 2010 01:08:17 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Wed, 24 Feb 2010 01:10:23 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: "Stephen.Morris@nominet.org.uk" <Stephen.Morris@nominet.org.uk>
Date: Wed, 24 Feb 2010 01:10:20 -0800
Thread-Topic: [ire] High level requirements for Internet Registration Data Escrow
Thread-Index: AcqxepS9Ut5SRhrZQz2d13X/O9FZbQDtptwZ
Message-ID: <C7AA2CFC.283D%francisco.arias@icann.org>
In-Reply-To: <OF02C78962.17BD7A63-ON802576CF.00557981-802576CF.00568864@nominet.org.uk>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] High level requirements for Internet Registration Data Escrow
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 24 Feb 2010 09:08:18 -0000

I believe we first need to define our scope horizontally (Domain names, RIR
objects, routing objects, etc.) and vertically (registries, registrars/LIRs=
,
DNS zone administrators, IP address administrators, Internet route
administrators, etc.) and then work on defining the minimum set of services=
.

Without the scope definition it doesn't seem possible to define this set, i=
f
ever will.

__=20
Francisco



On 2/19/10 7:45 AM, "Stephen.Morris@nominet.org.uk"
<Stephen.Morris@nominet.org.uk> wrote:

> Edward Lewis <Ed.Lewis@neustar.biz> wrote on 18/02/2010 14:18:44:
>=20
>> Perhaps it also depends on what one considers the database - but
>> there is billing information (account balances, stuff other than
>> expiration dates, etc.) that may be stored elsewhere.
>>=20
>> I usually view a registry of consisting of the following roughly
>> defined interfaces and protocols:
>>=20
>> Administrative -> Billing, legal support (think law enforcement...)
>> Provisioning -> The registration "desk" (like EPP)
>> Relying Party -> DNS (DN/RI-R), WhoIS other inspection protocols
>>=20
>> The information needed to set up these "external" interfaces are also
>> needed - if the goal is to reconstitute and continue operations and
>> not just "re-host the database."
>=20
> So the first question seems to be "What are the minimum set of services (=
and
> level of services) that an organisation can offer and still be classed as=
 a
> registry?".  From this we can derive the core data we need to store in es=
crow.
>=20
> As a first step, focusing on what we can't do without may be easier than
> reaching a conclusion on what we could do with.
>=20
> Stephen


From lconroy@insensate.co.uk  Wed Feb 24 09:31:29 2010
Return-Path: <lconroy@insensate.co.uk>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E3C828C204 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 09:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level: 
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gx21Dg31m1d2 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 09:31:28 -0800 (PST)
Received: from insensate.co.uk (ghost.insensate.co.uk [213.152.49.121]) by core3.amsl.com (Postfix) with ESMTP id 18EEB28C25C for <ire@ietf.org>; Wed, 24 Feb 2010 09:30:58 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 232AE10F4C2; Wed, 24 Feb 2010 17:33:04 +0000 (GMT)
References: <C7AA26C4.2834%francisco.arias@icann.org>
In-Reply-To: <C7AA26C4.2834%francisco.arias@icann.org>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
Message-Id: <4B2B4A4C-0F01-4F5A-BE8D-1931F119366B@insensate.co.uk>
Content-Transfer-Encoding: quoted-printable
From: Lawrence Conroy <lconroy@insensate.co.uk>
Date: Wed, 24 Feb 2010 17:33:04 +0000
To: Francisco Arias <francisco.arias@icann.org>
X-Mailer: Apple Mail (2.1077)
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] Separation of data sets / another aspect (testability)
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 24 Feb 2010 17:31:29 -0000

Hi Francisco, folks,
 You could always ask Ed about the provider transition of .us and how =
smoothly that went.
all the best,
  Lawrence

On 24 Feb 2010, at 08:43, Francisco Arias wrote:
> I agree with Bernie about the difficulty for testing but, maybe we =
could learn from slightly similar experiences. For example there have =
been a few cases of TLDs that have been transitioned from one operator =
to another; .ORG and .CO come to my mind at this moment.
>=20
> I know the aforementioned cases are not strictly compared to a =
transition in which only escrowed data is available, but at least those =
who had the experience of rebuilding registry services of those TLDs may =
want to share their experiences about what data and policies (if any) =
were needed to rebuild.
>=20
> __
> Francisco
>=20
>=20
>=20
> On 2/20/10 3:02 AM, "Bernie Hoeneisen" <bernie@ietf.hoeneisen.ch> =
wrote:
>=20
> Hi,
>=20
> After reading all the emails another aspect crossed my mind:
>=20
> - It is (hopefully) unlikely that we can properly test the
>   restoration of a Registry in real life. So we can never
>   conclusively proove what is the set of data absolutely needed in
>   case of restoration. This means implementations will be based on
>   assumptions, as we can never test them under real circumstances.
>=20
> - As a consequence we should logically separate the set of data
>   we believe is absolutely needed for restoring Registry
>   operations and any additional data that might be of importance.
>   The later should be escrowed too, although unlikely to ever be
>   used.
>=20
> Thus, there should be one set of data to be specified "both
> ways" (tuned for fast restoration, primary usage), and another
> set of data "one way" (tuned for storage/retrieval, secondary
> usage).
> [Whether of not the "tuning" matters at the end of the day is FFS.]
>=20
> The former can be tested to a certain extent (at least I hope so... =
;-) ),
> the latter might get too complex for proper testing.
>=20
>=20
> cheers,
>  Bernie
> _______________________________________________
> ire mailing list
> ire@ietf.org
> https://www.ietf.org/mailman/listinfo/ire
>=20
> _______________________________________________
> ire mailing list
> ire@ietf.org
> https://www.ietf.org/mailman/listinfo/ire


From shollenbeck@verisign.com  Wed Feb 24 10:21:19 2010
Return-Path: <shollenbeck@verisign.com>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C90628C245 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 10:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.148
X-Spam-Level: 
X-Spam-Status: No, score=-5.148 tagged_above=-999 required=5 tests=[AWL=1.450,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3qP+Wec1RY69 for <ire@core3.amsl.com>; Wed, 24 Feb 2010 10:21:17 -0800 (PST)
Received: from osprey.verisign.com (osprey.verisign.com [216.168.239.75]) by core3.amsl.com (Postfix) with ESMTP id 6630728C0E5 for <ire@ietf.org>; Wed, 24 Feb 2010 10:21:16 -0800 (PST)
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id o1OI3EPo007935; Wed, 24 Feb 2010 13:03:14 -0500
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Feb 2010 13:23:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAB57E.65EE4684"
Date: Wed, 24 Feb 2010 13:23:00 -0500
Message-ID: <046F43A8D79C794FA4733814869CDF07031D03CA@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <C7AA26C4.2834%francisco.arias@icann.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ire] Separation of data sets / another aspect (testability)
Thread-Index: AcqyHEyeSdPyOs22T3WR7uJ8DV4geADES6rsABQHY0A=
References: <alpine.DEB.2.00.1002201150390.16536@softronics.hoeneisen.ch> <C7AA26C4.2834%francisco.arias@icann.org>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Francisco Arias" <francisco.arias@icann.org>, <ire@ietf.org>
X-OriginalArrivalTime: 24 Feb 2010 18:23:02.0569 (UTC) FILETIME=[669F1990:01CAB57E]
Subject: Re: [ire] Separation of data sets / another aspect (testability)
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 24 Feb 2010 18:21:19 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAB57E.65EE4684
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I managed the VeriSign side of the .org data transition from VeriSign to
Afilias.  The short answer is that we provided them with a database dump
that included the thin registry data and table structures.  There was no
formal exchange of policy information.
=20
Someone from Afilias will have to describe what it took to reconstitute
things on their side.  They were up and running soon afterwards, and
both teams agreed that the transition went very well.
=20
Scott


________________________________

	From: ire-bounces@ietf.org [mailto:ire-bounces@ietf.org] On
Behalf Of Francisco Arias
	Sent: Wednesday, February 24, 2010 3:44 AM
	To: ire@ietf.org
	Subject: Re: [ire] Separation of data sets / another aspect
(testability)
=09
=09
	I agree with Bernie about the difficulty for testing but, maybe
we could learn from slightly similar experiences. For example there have
been a few cases of TLDs that have been transitioned from one operator
to another; .ORG and .CO come to my mind at this moment.
=09
	I know the aforementioned cases are not strictly compared to a
transition in which only escrowed data is available, but at least those
who had the experience of rebuilding registry services of those TLDs may
want to share their experiences about what data and policies (if any)
were needed to rebuild.
=09
	__=20
	Francisco


------_=_NextPart_001_01CAB57E.65EE4684
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [ire] Separation of data sets / another aspect =
(testability)</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16981" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCalibri color=3D#0000ff><SPAN=20
class=3D329171718-24022010>I managed the VeriSign side of&nbsp;the .org=20
data&nbsp;transition from VeriSign to Afilias.&nbsp; The short answer is =
that we=20
provided them with a database dump that included the thin registry data =
and=20
table structures.&nbsp; There was no formal exchange of policy=20
information.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCalibri color=3D#0000ff><SPAN=20
class=3D329171718-24022010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCalibri color=3D#0000ff><SPAN=20
class=3D329171718-24022010>Someone from Afilias will have to describe =
what it took=20
to reconstitute things on their side.&nbsp; <SPAN =
class=3D329171718-24022010>They=20
were up and running soon afterwards, and both teams agreed that the =
transition=20
went very well.</SPAN></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCalibri color=3D#0000ff><SPAN=20
class=3D329171718-24022010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCalibri color=3D#0000ff><SPAN=20
class=3D329171718-24022010>Scott</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ire-bounces@ietf.org=20
  [mailto:ire-bounces@ietf.org] <B>On Behalf Of </B>Francisco=20
  Arias<BR><B>Sent:</B> Wednesday, February 24, 2010 3:44 =
AM<BR><B>To:</B>=20
  ire@ietf.org<BR><B>Subject:</B> Re: [ire] Separation of data sets / =
another=20
  aspect (testability)<BR></FONT><BR></DIV>
  <DIV></DIV><FONT face=3DArial><SPAN style=3D"FONT-SIZE: 12pt">I agree =
with Bernie=20
  about the difficulty for testing but, maybe we could learn from =
slightly=20
  similar experiences. For example there have been a few cases of TLDs =
that have=20
  been transitioned from one operator to another; .ORG and .CO come to =
my mind=20
  at this moment.<BR><BR>I know the aforementioned cases are not =
strictly=20
  compared to a transition in which only escrowed data is available, but =
at=20
  least those who had the experience of rebuilding registry services of =
those=20
  TLDs may want to share their experiences about what data and policies =
(if any)=20
  were needed to rebuild.<BR><BR>__=20
<BR>Francisco</SPAN></FONT></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAB57E.65EE4684--

From bortzmeyer@nic.fr  Thu Feb 25 05:49:50 2010
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CC7F28C0FB for <ire@core3.amsl.com>; Thu, 25 Feb 2010 05:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.168
X-Spam-Level: 
X-Spam-Status: No, score=-6.168 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W43Vhz2Ax7E0 for <ire@core3.amsl.com>; Thu, 25 Feb 2010 05:49:48 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id 0691628C0F2 for <ire@ietf.org>; Thu, 25 Feb 2010 05:49:48 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id B96AC1C0117; Thu, 25 Feb 2010 14:46:57 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id A16121C0029; Thu, 25 Feb 2010 14:46:57 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay1.nic.fr (Postfix) with ESMTP id 9E861A1DC9C; Thu, 25 Feb 2010 14:46:57 +0100 (CET)
Date: Thu, 25 Feb 2010 14:46:57 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Francisco Arias <francisco.arias@icann.org>
Message-ID: <20100225134657.GA10264@nic.fr>
References: <alpine.DEB.2.00.1002201150390.16536@softronics.hoeneisen.ch> <C7AA26C4.2834%francisco.arias@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C7AA26C4.2834%francisco.arias@icann.org>
X-Operating-System: Debian GNU/Linux 5.0.4
X-Kernel: Linux 2.6.26-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] Separation of data sets / another aspect (testability)
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 25 Feb 2010 13:49:50 -0000

On Wed, Feb 24, 2010 at 12:43:48AM -0800,
 Francisco Arias <francisco.arias@icann.org> wrote 
 a message of 154 lines which said:

> those who had the experience of rebuilding registry services of
> those TLDs may want to share their experiences about what data and
> policies (if any) were needed to rebuild.

My colleague Olivier Guillard provided this summary about the
transition of .TF:


I have conducted the .tf migration from adamsnames
to AFNIC in 2004.

The information to read is here:

http://www.nic.tf/news/20041103.en.html
http://www.adamsnames.tc/tf.html

This is a report that Adamnames and AFNIC wrote together to
inform the community once the redelegation was done.

Be to be a bit more precise about operational actions, you first
have to consider the context :

Of course, .tf was not a very big zone (only several thousand
domains), so the operational pressure was relative : I had in
mind that, at the end, manual actions in the migration process
would be acceptable in such a situation.

I suspect that guys working on .org are not the same situation :)

Also, relations with adamsnames were very good, they were very
cooperative and since I was the beneficiary at the end, I considered
that it was my job to ensure the transition from the data structure
provided by adamsname to the data structure our data model.
We worked in real confidence with Martin and Sean from adamsnames,
at the end, that is in my view at least as important as anything
else to perform a good job.

Last main thing : there were no real AFNIC business plan behind the
.tf redelgation since AFNIC didn't plan to bill the domain name holders
at that time. I didn't have any constraint on that field.

My main focus in the process was really to ensure DNS continuity.

THIS BEING SAID, HERE IS A SUMMARY OF WHAT WE HAVE DONE AT THE END :
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- Adamsnames has furnish three spread sheets with various
  administrative data :

  foreach domain : registration and invoice dates,
                   an "adamsnames-handle" for each domain contacs:
                              (registrants,admin,billing and tech)
                   authoritative servers

  foreach adamnames-handle : administrative data (adresse, etc.)

  Another spreadshhet was simply a combination of the two previous
  one, kindly provided by Martin for checking.

To ensure a smooth DNS migration, adamsnames also accepted to
provide AXFR access to an authoritative .tf DNS server.

The rest is simple :
^^^^^^^^^^^^^^^^^^^

We extracted data from the spreadsheet, rearranged information that
we needed into our db format for insertion (and whois generation).

We AXFR DNS data from adamsnames (and checked coherence with information
in the spredsheet) and coordinated together (Adamsnames and AFNIC) to
ensure a smooth transition when asking DNS changes to IANA (adamsnames
also stayed autoritative for several month after the redelegation).

Last thing :
^^^^^^^^^^^

An important issue was of course communication to the community and
to contacts.

Before the redelegation, we (AFNIC) sent a mail to all contacts to
tell them about what would happen and when. That also was a good
opportnity to evaluate if administrative data was correct.
We then also sent a snail mail to all registrant contacts for whic
mails had bounced.

After the work was done, Adamnames and AFNIC also wrote a common
text to inform the community:

http://www.nic.tf/news/20041103.en.html
http://www.adamsnames.tc/tf.html

Shortly after this job was done, I stopped to be involved in .tf
issues (.tf management and issue was reorganised with other people).

So I can't tell you what was/had to be done after 2005.

Hope this helps,

Kindest Regards,

---
Olivier Guillard

From Ed.Lewis@neustar.biz  Thu Feb 25 06:49:53 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C95E28C327 for <ire@core3.amsl.com>; Thu, 25 Feb 2010 06:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.31
X-Spam-Level: 
X-Spam-Status: No, score=0.31 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pYXoaVJfYPSs for <ire@core3.amsl.com>; Thu, 25 Feb 2010 06:49:52 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 59B5A28C30C for <ire@ietf.org>; Thu, 25 Feb 2010 06:49:52 -0800 (PST)
Received: from Work-Laptop-2.local (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1PEprCo096191; Thu, 25 Feb 2010 09:51:54 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [0.0.0.0] by Work-Laptop-2.local (PGP Universal service); Thu, 25 Feb 2010 09:52:01 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 25 Feb 2010 09:52:01 -0500
Mime-Version: 1.0
Message-Id: <a06240801c7ac3cc193b5@[172.27.167.25]>
In-Reply-To: <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com>
References: <a06240801c7a9cad1f802@[192.35.165.216]> <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com>
Date: Thu, 25 Feb 2010 09:51:54 -0500
To: "ire@ietf.org" <ire@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 25 Feb 2010 14:49:53 -0000

In the original request the list of potential conflicts was short. 
Before I try to negotiate a new slot, let's get a more complete list 
of conflicts.

So far - DNSEXT and DNSOP are the ones that directly hit domain 
(including IP) name registrations.

SIDR is the request now.

What else?  APPAREA (for the AD's), V6OPS, IDR, OPSEC, 6MAN, SOFTWIRE, IRI

I'm trying to guess overlaps in the RIR interest in v6 and IDN 
remaining work.  (I don't see IDNABIS listed.)

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis             
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From Ed.Lewis@neustar.biz  Thu Feb 25 07:54:39 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 007BC28C374 for <ire@core3.amsl.com>; Thu, 25 Feb 2010 07:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.21
X-Spam-Level: 
X-Spam-Status: No, score=0.21 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eHMGma3RIrw for <ire@core3.amsl.com>; Thu, 25 Feb 2010 07:54:38 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 1BB6628C1D3 for <ire@ietf.org>; Thu, 25 Feb 2010 07:54:38 -0800 (PST)
Received: from Work-Laptop-2.local (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1PFudpx096770; Thu, 25 Feb 2010 10:56:40 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [0.0.0.0] by Work-Laptop-2.local (PGP Universal service); Thu, 25 Feb 2010 10:56:46 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 25 Feb 2010 10:56:46 -0500
Mime-Version: 1.0
Message-Id: <a06240803c7ac4e10a21f@[0.0.0.0]>
In-Reply-To: <p06240805c7ac4c58b4e5@[10.20.30.158]>
References: <a06240801c7a9cad1f802@[192.35.165.216]> <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com> <a06240801c7ac3cc193b5@[172.27.167.25]> <p06240805c7ac4c58b4e5@[10.20.30.158]>
Date: Thu, 25 Feb 2010 10:56:42 -0500
To: "ire@ietf.org" <ire@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 25 Feb 2010 15:54:39 -0000

At 7:49 -0800 2/25/10, Paul Hoffman wrote:

>Why are V6OPS, IDR, OPSEC, 6MAN, SOFTWIRE listed?

Guesses.  I am not sure what people might find to be a conflict.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From paul.hoffman@vpnc.org  Thu Feb 25 08:06:02 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 157A328C34E for <ire@core3.amsl.com>; Thu, 25 Feb 2010 08:06:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.676
X-Spam-Level: 
X-Spam-Status: No, score=-5.676 tagged_above=-999 required=5 tests=[AWL=-0.230, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7v+saahzBjdh for <ire@core3.amsl.com>; Thu, 25 Feb 2010 08:06:01 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 465BB3A83C2 for <ire@ietf.org>; Thu, 25 Feb 2010 08:06:01 -0800 (PST)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o1PFnMJd052578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Feb 2010 08:49:23 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240805c7ac4c58b4e5@[10.20.30.158]>
In-Reply-To: <a06240801c7ac3cc193b5@[172.27.167.25]>
References: <a06240801c7a9cad1f802@[192.35.165.216]> <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com> <a06240801c7ac3cc193b5@[172.27.167.25]>
Date: Thu, 25 Feb 2010 07:49:21 -0800
To: Edward Lewis <Ed.Lewis@neustar.biz>, "ire@ietf.org" <ire@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 25 Feb 2010 16:06:02 -0000

At 9:51 AM -0500 2/25/10, Edward Lewis wrote:
>In the original request the list of potential conflicts was short. Before I try to negotiate a new slot, let's get a more complete list of conflicts.
>
>So far - DNSEXT and DNSOP are the ones that directly hit domain (including IP) name registrations.
>
>SIDR is the request now.
>
>What else?  APPAREA (for the AD's), V6OPS, IDR, OPSEC, 6MAN, SOFTWIRE, IRI
>
>I'm trying to guess overlaps in the RIR interest in v6 and IDN remaining work.  (I don't see IDNABIS listed.)

IDNAbis is not meeting; we have finished our work.

Why are V6OPS, IDR, OPSEC, 6MAN, SOFTWIRE listed?

--Paul Hoffman, Director
--VPN Consortium

From cbbrowne@ca.afilias.info  Thu Feb 25 08:25:37 2010
Return-Path: <cbbrowne@ca.afilias.info>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0E1D3A847B for <ire@core3.amsl.com>; Thu, 25 Feb 2010 08:25:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 510ul6zsmqJf for <ire@core3.amsl.com>; Thu, 25 Feb 2010 08:25:36 -0800 (PST)
Received: from tor-gateway.afilias.info (tor-gateway.afilias.info [199.15.87.4]) by core3.amsl.com (Postfix) with ESMTP id 6152828C1DE for <ire@ietf.org>; Thu, 25 Feb 2010 08:25:36 -0800 (PST)
Received: from [10.10.68.46] (helo=dba2.int.libertyrms.com ident=postfix) by tor-gateway.afilias.info with smtp (Exim 4.69) (envelope-from <cbbrowne@ca.afilias.info>) id 1NkgYX-0007ZV-6o; Thu, 25 Feb 2010 11:27:17 -0500
Received: by dba2.int.libertyrms.com (Postfix, from userid 1000) id 95C8A86C03D; Thu, 25 Feb 2010 11:27:16 -0500 (EST)
From: Christopher Browne <cbbrowne@ca.afilias.info>
To: "Hollenbeck\, Scott" <shollenbeck@verisign.com>
Organization: Afilias Canada - Architecture Department
References: <alpine.DEB.2.00.1002201150390.16536@softronics.hoeneisen.ch> <C7AA26C4.2834%francisco.arias@icann.org> <046F43A8D79C794FA4733814869CDF07031D03CA@dul1wnexmb01.vcorp.ad.vrsn.com>
Date: Thu, 25 Feb 2010 11:27:16 -0500
In-Reply-To: <046F43A8D79C794FA4733814869CDF07031D03CA@dul1wnexmb01.vcorp.ad.vrsn.com> (Scott Hollenbeck's message of "Wed, 24 Feb 2010 13:23:00 -0500")
Message-ID: <873a0p5li3.fsf@ca.afilias.info>
User-Agent: Gnus/5.110009 (No Gnus v0.9) XEmacs/21.4.22 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ire@ietf.org
Subject: Re: [ire] Separation of data sets / another aspect (testability)
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 25 Feb 2010 16:25:37 -0000

"Hollenbeck, Scott" <shollenbeck@verisign.com> writes:
> I managed the VeriSign side of the .org data transition from VeriSign
> to Afilias.  The short answer is that we provided them with a database
> dump that included the thin registry data and table structures.  There
> was no formal exchange of policy information.
>  
> Someone from Afilias will have to describe what it took to
> reconstitute things on their side.  They were up and running soon
> afterwards, and both teams agreed that the transition went very well.

I was the "technical guy" on the other side of that, and I'd consider
Scott's comments to be a fair assessment.

There were some limited discussions of the meanings of status data, but
that sort of thing was generally assessed via data analysis without
engaging in exchanges of "meta" policy information.  

That seems similar to the thinking about escrow in a pretty relevant
fashion.

There is a distinction worth noting, though.  In the dealings between
Verisign and Afilias, there *was* opportunity for interactive exchange
of information, and as the participants behaved in a professional
fashion, the interaction helped the transition to take place quite
smoothly.

Unfortunately, in a situation where there has been a failure requiring
the exercise of escrow, there can't be any expectation of being able to
interact usefully with the previous operator.  They may be unavailable,
or intractably adversarial, and it's not self-evident which might be
worse.

As to Scott's comments on reconstitution...  We obviously needed to go
through some efforts to reconstitute it into a form suitable for our
use; I'm not sure there is anything about that which is useful to
discuss here.  I worked on later transitions of other TLDs, which
provided some parallel observations - we received data in a number of
formats, frequently less-well-defined and more painful to work with than
the data used for the .org transition.

The data structures presented in the document Francisco presented to
this list bear intentional resemblance to the database dumps used for
the .org transition, which is a credit to how well that worked.
-- 
select 'cbbrowne' || '@' || 'ca.afilias.info';
Christopher Browne
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"

From yoshiro.yoneya@jprs.co.jp  Thu Feb 25 20:36:07 2010
Return-Path: <yoshiro.yoneya@jprs.co.jp>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2023828C267 for <ire@core3.amsl.com>; Thu, 25 Feb 2010 20:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.51
X-Spam-Level: 
X-Spam-Status: No, score=0.51 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oq418vWnGg2o for <ire@core3.amsl.com>; Thu, 25 Feb 2010 20:36:06 -0800 (PST)
Received: from send11.jprs.co.jp (send11.jprs.co.jp [202.11.17.110]) by core3.amsl.com (Postfix) with ESMTP id 1578D28C4DD for <ire@ietf.org>; Thu, 25 Feb 2010 20:36:02 -0800 (PST)
Received: from sendsms11.jprs.co.jp (sendsms11.jprs.co.jp [202.11.17.111]) by send11.jprs.co.jp (8.13.8+Sun/8.13.8) with ESMTP id o1Q4cEbk020375 for <ire@ietf.org>; Fri, 26 Feb 2010 13:38:14 +0900 (JST)
Received: from sendsms11.jprs.co.jp (unknown [127.0.0.1]) by sendsms11.jprs.co.jp (Symantec Mail Security) with ESMTP id C67FC35D5 for <ire@ietf.org>; Fri, 26 Feb 2010 13:38:14 +0900 (JST)
X-AuditID: ca0b116f-00000007000007eb-81-4b8750361232 
Received: from NOTE233 (bxx0114.jprs.co.jp [172.18.4.53]) by sendsms11.jprs.co.jp (Symantec Mail Security) with SMTP id 894F735D4 for <ire@ietf.org>; Fri, 26 Feb 2010 13:38:14 +0900 (JST)
Date: Fri, 26 Feb 2010 13:38:05 +0900
From: Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
To: ire@ietf.org
Message-Id: <20100226133805.17570402.yoshiro.yoneya@jprs.co.jp>
In-Reply-To: <a06240801c7ac3cc193b5@[172.27.167.25]>
References: <a06240801c7a9cad1f802@[192.35.165.216]> <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com> <a06240801c7ac3cc193b5@[172.27.167.25]>
X-Mailer: Sylpheed 3.0.0 (GTK+ 2.10.14; i686-pc-mingw32)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 26 Feb 2010 04:36:07 -0000

On Thu, 25 Feb 2010 09:51:54 -0500 Edward Lewis <Ed.Lewis@neustar.biz> wrote:

> In the original request the list of potential conflicts was short. 
> Before I try to negotiate a new slot, let's get a more complete list 
> of conflicts.
> 
> So far - DNSEXT and DNSOP are the ones that directly hit domain 
> (including IP) name registrations.
> 
> SIDR is the request now.
> 
> What else?  APPAREA (for the AD's), V6OPS, IDR, OPSEC, 6MAN, SOFTWIRE, IRI

+ NEWPREP

-- 
Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>


From bernie@ietf.hoeneisen.ch  Fri Feb 26 01:10:31 2010
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C9C228C0F3 for <ire@core3.amsl.com>; Fri, 26 Feb 2010 01:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6UYrdKS5gPg for <ire@core3.amsl.com>; Fri, 26 Feb 2010 01:10:29 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id AE3E83A8625 for <ire@ietf.org>; Fri, 26 Feb 2010 01:10:26 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1NkwFR-0005h6-Mu; Fri, 26 Feb 2010 10:12:37 +0100
Date: Fri, 26 Feb 2010 10:12:37 +0100 (CET)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
In-Reply-To: <20100226133805.17570402.yoshiro.yoneya@jprs.co.jp>
Message-ID: <alpine.DEB.2.00.1002261007410.21578@softronics.hoeneisen.ch>
References: <a06240801c7a9cad1f802@[192.35.165.216]> <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com> <a06240801c7ac3cc193b5@[172.27.167.25]> <20100226133805.17570402.yoshiro.yoneya@jprs.co.jp>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Cc: ire@ietf.org
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 26 Feb 2010 09:10:31 -0000

> WG re-scheduling cutoff is February 22, 2010 17:00 PST

As the deadline for re-scheduling the agenda has passed,
I wonder whether it still makes sense to discuss about now...

cheers,
  Bernie


On Fri, 26 Feb 2010, Yoshiro YONEYA wrote:

> On Thu, 25 Feb 2010 09:51:54 -0500 Edward Lewis <Ed.Lewis@neustar.biz> wrote:
>
>> In the original request the list of potential conflicts was short.
>> Before I try to negotiate a new slot, let's get a more complete list
>> of conflicts.
>>
>> So far - DNSEXT and DNSOP are the ones that directly hit domain
>> (including IP) name registrations.
>>
>> SIDR is the request now.
>>
>> What else?  APPAREA (for the AD's), V6OPS, IDR, OPSEC, 6MAN, SOFTWIRE, IRI
>
> + NEWPREP
>
> -- 
> Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
>
> _______________________________________________
> ire mailing list
> ire@ietf.org
> https://www.ietf.org/mailman/listinfo/ire
>

From Ed.Lewis@neustar.biz  Fri Feb 26 10:56:56 2010
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0716D3A8710 for <ire@core3.amsl.com>; Fri, 26 Feb 2010 10:56:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=0.157,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zt6ifpozdhm1 for <ire@core3.amsl.com>; Fri, 26 Feb 2010 10:56:55 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 1A8FC3A86F1 for <ire@ietf.org>; Fri, 26 Feb 2010 10:56:54 -0800 (PST)
Received: from Work-Laptop-2.local (gatt.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id o1QIwxsL010188; Fri, 26 Feb 2010 13:59:00 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.200.181] by Work-Laptop-2.local (PGP Universal service); Fri, 26 Feb 2010 13:59:07 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Fri, 26 Feb 2010 13:59:07 -0500
Mime-Version: 1.0
Message-Id: <a06240800c7adc87d0112@[10.31.200.181]>
In-Reply-To: <alpine.DEB.2.00.1002261007410.21578@softronics.hoeneisen.ch>
References: <a06240801c7a9cad1f802@[192.35.165.216]> <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com> <a06240801c7ac3cc193b5@[172.27.167.25]> <20100226133805.17570402.yoshiro.yoneya@jprs.co.jp> <alpine.DEB.2.00.1002261007410.21578@softronics.hoeneisen.ch>
Date: Fri, 26 Feb 2010 13:53:07 -0500
To: ire@ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Cc: ed.lewis@neustar.biz
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 26 Feb 2010 18:56:56 -0000

At 10:12 +0100 2/26/10, Bernie Hoeneisen wrote:
>>  WG re-scheduling cutoff is February 22, 2010 17:00 PST
>
>As the deadline for re-scheduling the agenda has passed,
>I wonder whether it still makes sense to discuss about now...
>

It appears so.

I asked if it was still possible just minutes before a message went 
out to all chairs that "only an AD can request a swap."

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

As with IPv6, the problem with the deployment of frictionless surfaces is
that they're not getting traction.

From paul.hoffman@vpnc.org  Fri Feb 26 11:29:04 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ire@core3.amsl.com
Delivered-To: ire@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C43473A882F for <ire@core3.amsl.com>; Fri, 26 Feb 2010 11:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.975
X-Spam-Level: 
X-Spam-Status: No, score=-5.975 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id smStHT7DZuUj for <ire@core3.amsl.com>; Fri, 26 Feb 2010 11:29:04 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 09E853A882E for <ire@ietf.org>; Fri, 26 Feb 2010 11:29:03 -0800 (PST)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o1QJVHpO048782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Feb 2010 12:31:19 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240819c7add1a6f6eb@[10.20.30.158]>
In-Reply-To: <a06240800c7adc87d0112@[10.31.200.181]>
References: <a06240801c7a9cad1f802@[192.35.165.216]> <046F43A8D79C794FA4733814869CDF07031D039B@dul1wnexmb01.vcorp.ad.vrsn.com> <a06240801c7ac3cc193b5@[172.27.167.25]> <20100226133805.17570402.yoshiro.yoneya@jprs.co.jp> <alpine.DEB.2.00.1002261007410.21578@softronics.hoeneisen.ch> <a06240800c7adc87d0112@[10.31.200.181]>
Date: Fri, 26 Feb 2010 11:31:16 -0800
To: Edward Lewis <Ed.Lewis@neustar.biz>, ire@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [ire] We're on the agenda of the IETF
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 26 Feb 2010 19:29:04 -0000

At 1:53 PM -0500 2/26/10, Edward Lewis wrote:
>At 10:12 +0100 2/26/10, Bernie Hoeneisen wrote:
>>> WG re-scheduling cutoff is February 22, 2010 17:00 PST
>>
>>As the deadline for re-scheduling the agenda has passed,
>>I wonder whether it still makes sense to discuss about now...
>>
>
>It appears so.
>
>I asked if it was still possible just minutes before a message went out to all chairs that "only an AD can request a swap."

Everyone hates Friday, but Friday after lunch looks free of conflict, and yet has a lot of Apps folks who care about URIs still there. I could even see Friday morning up against the new IRI WG, but I suspect that some of the data-heads would want to be in both.

--Paul Hoffman, Director
--VPN Consortium
