IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Fri, 14 December 2012 18:30 UTC

Return-Path: <shollenbeck@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 0CE1121F8AFB for <ire@ietfa.amsl.com>; Fri, 14 Dec 2012 10:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.216
X-Spam-Level:
X-Spam-Status: No, score=-6.216 tagged_above=-999 required=5 tests=[AWL=0.383, 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 mf8DoHncTXlH for <ire@ietfa.amsl.com>; Fri, 14 Dec 2012 10:30:01 -0800 (PST)
Received: from exprod6og106.obsmtp.com (exprod6og106.obsmtp.com [64.18.1.191]) by ietfa.amsl.com (Postfix) with ESMTP id D616821F8AE1 for <ire@ietf.org>; Fri, 14 Dec 2012 10:29:57 -0800 (PST)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob106.postini.com ([64.18.5.12]) with SMTP ID DSNKUMtwJWLRvyGcLpSRQHlR9m0nJBSx1Lds@postini.com; Fri, 14 Dec 2012 10:30:01 PST
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id qBEITsBd028632 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Dec 2012 13:29:54 -0500
Received: from BRN1WNEXMBX02.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0318.004; Fri, 14 Dec 2012 13:29:54 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Francisco Obispo <fobispo@isc.org>, "Gould, James" <JGould@verisign.com>
Thread-Topic: [ire] New version (4) of the spec and new draft on DNRD (1)
Thread-Index: AQHN2iLMS0sBietkZ0GdZPo8OnE6WpgY6Y6AgAACtwD//6388A==
Date: Fri, 14 Dec 2012 18:29:53 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F0D6C873C@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
References: <C41D7AF7FCECBE44940E9477E8E70D7A0D7437F6@BRN1WNEXMBX02.vcorp.ad.vrsn.com> <148D81EC-63B1-4C71-B630-B50686BE82B4@isc.org>
In-Reply-To: <148D81EC-63B1-4C71-B630-B50686BE82B4@isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
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] 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:30:02 -0000

> -----Original Message-----
> From: ire-bounces@ietf.org [mailto:ire-bounces@ietf.org] On Behalf Of
> Francisco Obispo
> Sent: Friday, December 14, 2012 1:11 PM
> To: Gould, James
> Cc: Luis Muñoz; ire@ietf.org
> Subject: Re: [ire] New version (4) of the spec and new draft on DNRD
> (1)
> 
> 
> On Dec 14, 2012, at 10:01 AM, "Gould, James" <JGould@verisign.com>
> wrote:
> 
> > Francisco,
> >
> > You are adding text to the RFC that doesn't exist.  If the intention
> > was to include the "sponsoring client" or "registrar" it would have
> > stated it, but it does not.
> 
> The problem is, that it doesn't say it's a user either, it says
> "client", and you could ask yourself, who is the "client" of an EPP
> service ? we can't assure a registrar, because in a registry model
> without registrars' it could be the registry or anyone.

The EPP fields are intended to capture the value of the <clID> element provided with the <login> command of the client (in the context of a client-server relationship) that performed the create or update action. The clID, crID, and upID values don't tell you anything about the client's role.

Scott

v2.23.0 | Report a Bug | By Email