Re: [eppext] [IANA #814917] INSERT “Extensible Provisioning Protocol Extension Mapping: Personal Registration"

"Gould, James" <JGould@verisign.com> Mon, 06 April 2015 15:37 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 7F6E61A8900 for <eppext@ietfa.amsl.com>; Mon, 6 Apr 2015 08:37:18 -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 JwpWyIQexERD for <eppext@ietfa.amsl.com>; Mon, 6 Apr 2015 08:37:16 -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 1C0C81A878A for <eppext@ietf.org>; Mon, 6 Apr 2015 08:37:16 -0700 (PDT)
Received: by qgaj5 with SMTP id j5so1392217qga.1 for <eppext@ietf.org>; Mon, 06 Apr 2015 08:37:15 -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=q1oHaRMSkD6iph8qGp18DRlT/m7lPuEY/VdlGcv4Qrw=; b=LU3MjqktF3WmfYfpzQmRVgTrVi+312BvJ3wDHvYkffkpZOrSFruKz1BouEHmXXHl1Q KO0Biz71aEseTOoGdY6ozkls5O0cvSATWxdD2Dmn5eDqODymuyAViWrq+gjN9bQPbjIg to5T4oSndc3buAVjNsXCr7qpRPmHSPCdvQwwPKmkDitHst+Y+hIJYj4Uu/kLQZ+i94Hs +ab6cFGWhWaMS+ULaoeOSe6tS+5AXo+po0LcVbiNK4zva1RK1kp58A71XgaMq6snIgZB WsXH369PzF0/p1UoEHRuoOCjpsV5c7ZUW3Pj7TrSoXr3zV0wpmpiwUt2/Ay3Voo9JpkS bXuQ==
X-Gm-Message-State: ALoCoQn6sXLwZMggjLQfUGNDtGRbFcw7yxuPoYU/sQaUiqc7hHUMlcw67CgWsm6z8H15Sc1BR+nXwTYuMFrCIoNpLxAMlJYcLA==
X-Received: by 10.140.165.150 with SMTP id l144mr18724743qhl.39.1428334635322; Mon, 06 Apr 2015 08:37:15 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id q8sm469796qcg.2.2015.04.06.08.37.15 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 06 Apr 2015 08:37:15 -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 t36FbERJ002170 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Apr 2015 11:37:14 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 6 Apr 2015 11:37:14 -0400
From: "Gould, James" <JGould@verisign.com>
To: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gW0lBTkEgIzgxNDkxN10gSU5TRVJUIOKAnEV4dGVuc2libGUg?= =?utf-8?B?UHJvdmlzaW9uaW5nIFByb3RvY29sIEV4dGVuc2lvbiBNYXBwaW5nOiBQZXJz?= =?utf-8?Q?onal_Registration"?=
Thread-Index: AQHQZW/LZazIOaoclkS5MXdUxnrO7Z0qVc+ggBYWIwCAAAtmAA==
Date: Mon, 6 Apr 2015 15:37:14 +0000
Message-ID: <9DBC5BF5-97CD-4234-B83D-8B981095DA57@verisign.com>
References: <RT-Ticket-814917@icann.org> <0859CECA-CCA2-4BD7-B8CC-E91973F3D389@verisign.com> <rt-4.2.9-2033-1427129037-390.814917-9-0@icann.org> <831693C2CDA2E849A7D7A712B24E257F49F89B32@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <19F54F2956911544A32543B8A9BDE0754679B4A8@NICS-EXCH2.sbg.nic.at>
In-Reply-To: <19F54F2956911544A32543B8A9BDE0754679B4A8@NICS-EXCH2.sbg.nic.at>
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_9DBC5BF597CD4234B83D8B981095DA57verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/AMOqFeRxX0ME2lusxaXhhIlKfuo>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] =?utf-8?q?=5BIANA_=23814917=5D_INSERT_=E2=80=9CExtensibl?= =?utf-8?q?e_Provisioning_Protocol_Extension_Mapping=3A_Personal_Registrat?= =?utf-8?q?ion=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: Mon, 06 Apr 2015 15:37:18 -0000

Alexander,

Thank you for the review.  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 6, 2015, at 10:56 AM, Alexander Mayrhofer <alexander.mayrhofer@nic.at<mailto:alexander.mayrhofer@nic.at>> wrote:

All,

I have completed my review of the extension registration request, and i have no significant comments. My nits (as always) are:

- Text about "VERISIGN PROPRIETORY INFORMATION" - same concerns about practicality of this..

Same response to the copyright notice concern.

- (Interesting from a process perspective is that this extension extends yet another extension that is in the process of being registered [email forwarding extension] .. I don't think it has any impact for that specific registration, but i haven't thought about whether or not we should generally register extensions that *depend* on other, yet unregistered extensions?)

I don’t believe this is a typical case, but could be a case if a registry supports a new type of object (email forwarding), that is associated with an existing object (e.g. domain), and that requires a command / response extension to make the two objects work together (bundle pricing, consent, specific error conditions).  Domain needs to be extended via the command / response extension in a consistent manner to a new object extension.  I see this as a corner case, but never say never :-)

- in 3.2.1, there seems to be a typo in the XML frame (missing line break after </create>)


Good catch, thanks.

Note: I have not formally validated the XML syntax under section 4.

tia,
Alex


-----BEGIN FORM-----
Name of Extension:
“Extensible Provisioning Protocol Extension Mapping: Personal Registration"

Document Status:
Informational

Reference:
http://www.verisigninc.com/assets/personal-registration-extension.pdf

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

TLDs: .name

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