Re: [ire] New version (4) of the spec and new draft on DNRD (1)

"Gould, James" <JGould@verisign.com> Fri, 14 December 2012 18:45 UTC

Return-Path: <JGould@verisign.com>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5149B21F8A12 for <ire@ietfa.amsl.com>; Fri, 14 Dec 2012 10:45:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.349
X-Spam-Level:
X-Spam-Status: No, score=-6.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aQ85wwZUqKsZ for <ire@ietfa.amsl.com>; Fri, 14 Dec 2012 10:45:12 -0800 (PST)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD5A21F8A05 for <ire@ietf.org>; Fri, 14 Dec 2012 10:45:10 -0800 (PST)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKUMtztX9sjKaUind1XVSfHbYXl1XFrW3L@postini.com; Fri, 14 Dec 2012 10:45:12 PST
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id qBEIj6qF031911 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Dec 2012 13:45:06 -0500
Received: from BRN1WNEXMBX02.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0318.004; Fri, 14 Dec 2012 13:45:06 -0500
From: "Gould, James" <JGould@verisign.com>
To: Francisco Obispo <fobispo@isc.org>
Thread-Topic: [ire] New version (4) of the spec and new draft on DNRD (1)
Thread-Index: Ac2yTfOti6zvW6WRSs6IEhQPZFwOdwQVYfCABapuHoAADOU0gP//sOEAgABhjYCAAQ6EAIAAds6A//+wp4CAAFaSAIAABSYA//+wigA=
Date: Fri, 14 Dec 2012 18:45:04 +0000
Message-ID: <C41D7AF7FCECBE44940E9477E8E70D7A0D7439BB@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
In-Reply-To: <FE93F5AE-2F6D-462F-983E-6FEC12224681@isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B9A669CE5E4C224F9FDB3A9A14A939E3@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Luis Muñoz <lem@isc.org>, "ire@ietf.org" <ire@ietf.org>
Subject: Re: [ire] New version (4) of the spec and new draft on DNRD (1)
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ire>, <mailto:ire-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ire>
List-Post: <mailto:ire@ietf.org>
List-Help: <mailto:ire-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ire>, <mailto:ire-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 18:45:13 -0000

Francisco,

EPP is the provisioning protocol for the systems that you are going to
escrow, so naturally it is the basis in determining the set of fields and
intent of the fields to escrow.  I don't believe you can separate the two
in the discussion. 

-- 

JG
 

 
James Gould
Principal Software Engineer
jgould@verisign.com
 
703-948-3271 (Office)
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com







On 12/14/12 1:29 PM, "Francisco Obispo" <fobispo@isc.org> wrote:

>
>On Dec 14, 2012, at 10:10 AM, Francisco Obispo <fobispo@isc.org> wrote:
>
>>> You can't simply add text that doesn't exist and then
>>> include that text in a data escrow draft that is based on your
>>> interpretation.
>
>BTW, the fact that Arias, and Noguchi decided to use the EPP format as a
>guideline, is plausible, but if you are correct but what is needed is the
>registrar/client and not the individual user information, then the
>requirement in the escrow needs to reflect what is needed and not what
>the EPP protocol says.
>
>I'm just trying to say that one protocol is not bound to the other, and
>if that was the case, we would not be discussing XML over CSV or
>viceversa.
>
>
>Francisco Obispo 
>Director of Applications and Services - ISC
>email: fobispo@isc.org
>Phone: +1 650 423 1374 || INOC-DBA *3557* NOC
>PGP KeyID = B38DB1BE
>