Re: [eppext] [IANA #814924] INSERT “Premium Domain Extension for the Extensible Provisioning Protocol (EPP)"

"Gould, James" <JGould@verisign.com> Sun, 05 April 2015 13:48 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 2852C1A897F for <eppext@ietfa.amsl.com>; Sun, 5 Apr 2015 06:48:04 -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 N4HxQHKwY9mS for <eppext@ietfa.amsl.com>; Sun, 5 Apr 2015 06:48:01 -0700 (PDT)
Received: from mail-qg0-f98.google.com (mail-qg0-f98.google.com [209.85.192.98]) (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 326761A00F8 for <eppext@ietf.org>; Sun, 5 Apr 2015 06:48:01 -0700 (PDT)
Received: by qgdz60 with SMTP id z60so361663qgd.0 for <eppext@ietf.org>; Sun, 05 Apr 2015 06:48:00 -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=bZj8Nzp02hT18bUCS5Lynm2f3a9U4ImsXCLUH4XhZwU=; b=agtNhsmGyg+QACI6LaoSfp31Bn7wXWGAUd9qZqXnBncfDd0wwa7Mu9/kLmfyRH8kHD bW5sY9WtPWMHXQVtAAzkjq7kgBJMrYrbifRXfw5zYiCnP27Iwx6vpSm7Fo+bNMsSwpvh h32EZap/4qjLrnZjmzLOl59Abm0HObCWxF+lieUAANx6VjK+Wv4RJhaa4plvlcTcKmF7 YWSfpuja9KEzCrDGcqUMhoTtnnGOFpKUnSSHu5Xr8cpz39Vljsl6h60+0vdlBpCrMFGR 1CRv8ocxmZaSo1qygAe1PnJOdF20tC6nBEHu2Q1v190uIQPquTu+T1tbuY/HC0o1uG/d kDUw==
X-Gm-Message-State: ALoCoQlXcxaF4SoBD5VkYWPUEQVsQ6WI8locJKSXjp6RDV7OdVg4V8e7atU/W8pEi1UVqPf9qnkV20hd69bpcFSKsf8TJuf9yw==
X-Received: by 10.140.85.113 with SMTP id m104mr12027864qgd.7.1428241680243; Sun, 05 Apr 2015 06:48:00 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id l10sm447769qcs.4.2015.04.05.06.47.59 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 05 Apr 2015 06:48:00 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t35DlxYn020612 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 5 Apr 2015 09:47:59 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Sun, 5 Apr 2015 09:47:58 -0400
From: "Gould, James" <JGould@verisign.com>
To: Gavin Brown <gavin.brown@centralnic.com>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gW0lBTkEgIzgxNDkyNF0gSU5TRVJUIOKAnFByZW1pdW0gRG9t?= =?utf-8?B?YWluIEV4dGVuc2lvbiBmb3IgdGhlIEV4dGVuc2libGUgUHJvdmlzaW9uaW5n?= =?utf-8?Q?_Protocol_(EPP)"?=
Thread-Index: AQHQb6cgKwtSL7TULEWpOCOmRyv0Ig==
Date: Sun, 5 Apr 2015 13:47:58 +0000
Message-ID: <36E9E0E2-9440-4378-81C7-C8D5CE0F7902@verisign.com>
References: <RT-Ticket-814924@icann.org> <FE7ADF4A-218B-4F03-B495-28D29E647616@verisign.com> <rt-4.2.9-2033-1427129255-993.814924-9-0@icann.org> <831693C2CDA2E849A7D7A712B24E257F49F89BD1@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <551EBE7B.20301@centralnic.com>
In-Reply-To: <551EBE7B.20301@centralnic.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_36E9E0E29440437881C7C8D5CE0F7902verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/KqWmodWcOaxszHgCtdd84dqUVxk>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] =?utf-8?q?=5BIANA_=23814924=5D_INSERT_=E2=80=9CPremium_D?= =?utf-8?q?omain_Extension_for_the_Extensible_Provisioning_Protocol_=28EPP?= =?utf-8?b?KSI=?=
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: Sun, 05 Apr 2015 13:48:04 -0000

Gavin,

Thank you for the review and feedback.  Below is my feedback.


—


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 12:23 PM, Gavin Brown <gavin.brown@centralnic.com<mailto:gavin.brown@centralnic.com>> wrote:

Here is my review as DE:

1. This extension implements a subset of the functionality of
draft-brown-epp-fees. As they have been developed in parallel (and I am
the author of that draft) I won't comment on the duplication of
functionality.


Yes, the premium domain extension was created prior the registry fee extension, and the plan is to transition to use the registry fee extension.


2. The <premiumdomain:price> element has a mandatory "unit" attribute
which is only permitted to contain the string "USD". If there is only
one possible value, then there is no reason for the attribute to exist;
if the intention is to allow other values than "USD", the schema should
allow it (and the specification should probably reference ISO 4217 as
draft-brown-epp-fees does).

You are correct that the unit should have been just a token in the schema to support more units than “USD”.  This is noted, although the plan is to transition to the registry fee extension.


3. As others have, I'd also like to voice my concerns about the IP terms
in the Legal Disclaimer. The purpose of registering an EPP exension in
the registry is to facilitate harmonisation and interoperability, and
yet the Legal Disclaimer seems designed to discourage that.


Same response to the copyright notice concern.

4. The specification seems to meet the requirements in RFC 7451 Section
2.1.1, in that:

* it meets the guidelines in RFC 3735

* Security considerations have been addressed. Privacy considerations
are not addressed, but this specification does not have any particular
problems in these areas.

G.

On 23/03/2015 17:42, Hollenbeck, Scott wrote:
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:48 PM
Cc: Hollenbeck, Scott
Subject: [IANA #814924] INSERT “Premium Domain Extension for the Extensible Provisioning Protocol (EPP)"

#15 of 18.

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

Document Status:
Informational

Reference:
http://www.verisigninc.com/assets/epp-sdk/verisign_epp-extension_premium-domain_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


--
Gavin Brown
Chief Technology Officer
CentralNic Group plc (LSE:CNIC)
Innovative, Reliable and Flexible Registry Services
for ccTLD, gTLD and private domain name registries
https://www.centralnic.com/

CentralNic Group plc is a company registered in England and Wales with
company number 8576358. Registered Offices: 35-39 Moorgate, London,
EC2R 6AR.

_______________________________________________
EppExt mailing list
EppExt@ietf.org
https://www.ietf.org/mailman/listinfo/eppext