Return-Path: <gavin.brown@centralnic.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 268241A886A
 for <eppext@ietfa.amsl.com>; Fri,  3 Apr 2015 04:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.727
X-Spam-Level: 
X-Spam-Status: No, score=-0.727 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553,
 HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001,
 T_FILL_THIS_FORM_SHORT=0.01] autolearn=no
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 8TSCZ9hqa64w for <eppext@ietfa.amsl.com>;
 Fri,  3 Apr 2015 04:23:13 -0700 (PDT)
Received: from smtp.centralnic.com (mail-7.fnb.uk.centralnic.net [5.44.25.120])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id BD3BB1A8890
 for <eppext@ietf.org>; Fri,  3 Apr 2015 04:22:46 -0700 (PDT)
Received: from Gavins-MacBook-Pro.local
 (host81-133-130-171.in-addr.btopenworld.com [81.133.130.171])
 (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by smtp.centralnic.com (Postfix) with ESMTPSA id A2E029E9E;
 Fri,  3 Apr 2015 11:22:38 +0000 (UTC)
Message-ID: <551E77FC.2010803@centralnic.com>
Date: Fri, 03 Apr 2015 12:22:36 +0100
From: Gavin Brown <gavin.brown@centralnic.com>
Organization: CentralNic Ltd
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, 
 "eppext@ietf.org" <eppext@ietf.org>
References: <RT-Ticket-814909@icann.org>
 <8E7296D9-A21D-4F9F-82E0-D019CA8B76A3@verisign.com>
 <rt-4.2.9-8987-1427128151-842.814909-9-0@icann.org>
 <831693C2CDA2E849A7D7A712B24E257F49F89A23@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49F89A23@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
OpenPGP: id=BB55B2CA91510745E798BCF4E87E3920F923B4CE
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="5R3gMArNbNe9mrMwtmsdffELEVOUegGgv"
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/FNS1dWOFVOHHSes66EuZN2g5GN0>
Subject: Re: [eppext] =?utf-8?b?Rlc6IFtJQU5BICM4MTQ5MDldIElOU0VSVCDigJxSR1Ag?=
 =?utf-8?q?Poll_Mapping_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 11:23:15 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--5R3gMArNbNe9mrMwtmsdffELEVOUegGgv
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Here is my review as DE:

1. The extension is useful and implements something that should have
been included in RFC3915. Updating that RFC to include poll messages
might be something this WG could consider post rechartering, at which
point this extension could be retired.

2. It's implicit in the text, but it might be worth stating that when a
client receives a poll message as described by this extension, it's
because the domain has completed step 8 in the RGP state diagram in
RFC3915, and is therefore no longer restorable.

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.

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.

I recommend that this extension be registered in the registry.

G.

On 23/03/2015 17:38, Hollenbeck, Scott wrote:
> Submitted for DE evaluation.
>=20
> Scott
>=20
> -----Original Message-----
> From: Amanda Baber via RT [mailto:iana-prot-param-comment@iana.org]=20
> Sent: Monday, March 23, 2015 12:29 PM
> Cc: Hollenbeck, Scott
> Subject: [IANA #814909] INSERT =E2=80=9CRGP Poll Mapping for the Extens=
ible Provisioning Protocol (EPP)"
>=20
> #3 of 18.
>=20
> -----BEGIN FORM-----
> Name of Extension:
> =E2=80=9CRGP Poll Mapping for the Extensible Provisioning Protocol (EPP=
)"
>=20
> Document Status:=20
> Informational
>=20
> Reference:=20
> http://www.verisigninc.com/assets/epp-sdk/verisign_epp-extension_rgp-po=
ll_v00.html
>=20
> Registrant Name and Email Address:
> VeriSign Inc., epp-registry@verisign.com
>=20
> TLDs: Any
>=20
> IPR Disclosure: None
>=20
> Status: Active
>=20
> Notes: None
> -----END FORM-----
>=20
> =E2=80=94
>=20
>=20
> JG
>=20
>=20
>=20
>=20
>=20
> James Gould
> Distinguished Engineer
> jgould@Verisign.com
>=20
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>=20
> VerisignInc.com
>=20
> =E2=80=9CThis message (including any attachments) is intended only for =
the use of the individual or entity to which it is addressed, and may con=
tain information that is non-public, proprietary, privileged, confidentia=
l and exempt from disclosure under applicable law or may be constituted a=
s attorney work product. If you are not the intended recipient, you are h=
ereby notified that any use, dissemination, distribution, or copying of t=
his communication is strictly prohibited. If you have received this messa=
ge in error, notify sender immediately and delete this message immediatel=
y.=E2=80=9D
>=20
> Download BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png
>=20
> 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
>=20

--=20
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.


--5R3gMArNbNe9mrMwtmsdffELEVOUegGgv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iEYEARECAAYFAlUed/wACgkQ6H45IPkjtM4qoQCeLM/dHaogWtECB00n4l5RBMbV
UBsAnRPeTFyU4Y0/xVtlCawqw7VYu3rR
=mvC1
-----END PGP SIGNATURE-----

--5R3gMArNbNe9mrMwtmsdffELEVOUegGgv--

