Re: [eppext] [IANA #814919] INSERT “Whois Info Extension for the Extensible Provisioning Protocol (EPP)"

"Gould, James" <JGould@verisign.com> Fri, 03 April 2015 14:26 UTC

Return-Path: <JGould@verisign.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E264E1A8BC4 for <eppext@ietfa.amsl.com>; Fri, 3 Apr 2015 07:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level:
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itaikRQuZy87 for <eppext@ietfa.amsl.com>; Fri, 3 Apr 2015 07:26:37 -0700 (PDT)
Received: from mail-qg0-f99.google.com (mail-qg0-f99.google.com [209.85.192.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420501A8AF5 for <eppext@ietf.org>; Fri, 3 Apr 2015 07:26:37 -0700 (PDT)
Received: by qgdz60 with SMTP id z60so4474453qgd.0 for <eppext@ietf.org>; Fri, 03 Apr 2015 07:26:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=+Ow417UM0utqh4dUM5wiSPpwgkxyEZzL6aUucVxCd+M=; b=FM4lwoSXI4OTx23o5/jr+G5NyG1qs/92qB5Zy30kgvyxSwbEvDI4jmGOk/IlPMoHvr 42zjNwrCPPae2aGRJ1Cm85Fu0bCwh5e3k038mn6G42++gabTpZ2ZVH5prYP0vopZtly2 z5a/hTnCPa4xnMZrU63okgH9ShD7cn3PTWx/46n8bii/7+WHg2CGiYmr9TGSAH6T1vkZ SW1siVsRMJ4S2uC7+25tY5WhSWyprMhfJi+0TIIBsWIAtCDrY256xfeLvibY91kc8ZLd c5dYMrUEqV+4B6qNnOxZYbW8sQuP+2WzMPpJ8oXrBY0+yGnHkAdfAAQrpk/qPFHs63ST BhNQ==
X-Gm-Message-State: ALoCoQmaQk8GLx1dPK9CZw//6YCzaIARCOmJvXEf0O6FFarHw4bMsRcjtESY5ikTWwW6olggLhDKhAxw2fzvtndKB5y01+KD6A==
X-Received: by 10.140.107.72 with SMTP id g66mr2833249qgf.70.1428071196348; Fri, 03 Apr 2015 07:26:36 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by mx.google.com with ESMTPS id hx9sm1939034qcb.3.2015.04.03.07.26.35 for <eppext@ietf.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 03 Apr 2015 07:26:36 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id t33EQZJ4007394 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <eppext@ietf.org>; Fri, 3 Apr 2015 10:26:35 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 3 Apr 2015 10:26:35 -0400
From: "Gould, James" <JGould@verisign.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gW0lBTkEgIzgxNDkxOV0gSU5TRVJUIOKAnFdob2lzIEluZm8g?= =?utf-8?B?RXh0ZW5zaW9uIGZvciB0aGUgRXh0ZW5zaWJsZSBQcm92aXNpb25pbmcgUHJv?= =?utf-8?Q?tocol_(EPP)"?=
Thread-Index: AQHQZXAqfp/NFxe2x0ugurFzAunPZ50qVjGQgBEk8ICAADFxgA==
Date: Fri, 3 Apr 2015 14:26:34 +0000
Message-ID: <D3BAE73A-4208-4FCA-AB69-4A521F839FFA@verisign.com>
References: <RT-Ticket-814919@icann.org> <6497ECBE-C745-494A-A40D-04B29FF5A074@verisign.com> <rt-4.2.9-2033-1427129135-813.814919-9-0@icann.org> <831693C2CDA2E849A7D7A712B24E257F49F89B85@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F49F94575@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49F94575@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_D3BAE73A42084FCAAB694A521F839FFAverisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/dO6UzyHUDMYzgnal5z_BbPZjkhs>
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] =?utf-8?q?=5BIANA_=23814919=5D_INSERT_=E2=80=9CWhois_Inf?= =?utf-8?q?o_Extension_for_the_Extensible_Provisioning_Protocol_=28EPP=29?= =?utf-8?q?=22?=
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 14:26:41 -0000

Scott,

Thanks for the review.  My feedback is below.


—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Apr 3, 2015, at 7:29 AM, Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> wrote:

I've completed my review of this extension. A few comments:

"<whoisInf:flag>element MUST contain a boolean value of "1" or "true" to indicate that additional whois information is desired in the response or a value of "0" or "false" to indicate that no additional whois information is desired in the response."

One could also say "don't use this extension at all to indicate that you don't want additional WHOIS info.

Yes, you are correct, a better approach would have been to include an empty <whoisInf:whoisInf/> element as the marker to include the extension in the response, as opposed to using the <whoisInf:flag> boolean sub-element.  We started using the empty marker elements in later extensions.


<whoisInf:irisServer>OPTIONAL element element that contains the sponsoring Registrar's referral IRIS server name.

Is anyone anywhere running IRIS servers?

Jim, have you given any thought to the future of this extension in the context of RDAP development and eventual deployment?


No, I’m not aware of the use of IRIS anywhere, so this is a historic element that never actually got used.  I really have not considered how inclusion of RDAP would impact the registrar and registry EPP interface in support of transfers, but I and we should start to.  This extension was created based on feedback from registrars that they needed to query WHOIS in support of transfers, which made little sense since they have a trusted connection directly to the registry.  It would be interesting to see if other registries have created similar WHOIS extensions based on registrar feedback, and how a transition to RDAP should be handled.


Scott

-----Original Message-----
From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Hollenbeck,
Scott
Sent: Monday, March 23, 2015 1:42 PM
To: eppext@ietf.org<mailto:eppext@ietf.org>
Subject: [eppext] FW: [IANA #814919] INSERT “Whois Info Extension for
the Extensible Provisioning Protocol (EPP)"

Submitted for DE evaluation.

Scott

-----Original Message-----
From: Amanda Baber via RT [mailto:iana-prot-param-comment@iana.org]
Sent: Monday, March 23, 2015 12:46 PM
Cc: Hollenbeck, Scott
Subject: [IANA #814919] INSERT “Whois Info Extension for the Extensible
Provisioning Protocol (EPP)"

#12 of 18.

-----BEGIN FORM-----
Name of Extension:
“Whois Info Extension for the Extensible Provisioning Protocol (EPP)"

Document Status:
Informational

Reference:
http://www.verisigninc.com/assets/epp-sdk/verisign_epp-extension_whois-
info_v00.html

Registrant Name and Email Address:
VeriSign Inc., epp-registry@verisign.com

TLDs: Any

IPR Disclosure: None

Status: Active

Notes: None
-----END FORM-----

—


JG





James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com

“This message (including any attachments) is intended only for the use
of the individual or entity to which it is addressed, and may contain
information that is non-public, proprietary, privileged, confidential
and exempt from disclosure under applicable law or may be constituted
as attorney work product. If you are not the intended recipient, you
are hereby notified that any use, dissemination, distribution, or
copying of this communication is strictly prohibited. If you have
received this message in error, notify sender immediately and delete
this message immediately.”

Download BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png

image/png 4KiB
Image not shown because display is disabled in system configuration.
_______________________________________________
EppExt mailing list
EppExt@ietf.org
https://www.ietf.org/mailman/listinfo/eppext
_______________________________________________
EppExt mailing list
EppExt@ietf.org<mailto:EppExt@ietf.org>
https://www.ietf.org/mailman/listinfo/eppext