Re: [eppext] [IANA #814918] INSERT “Extensible Provisioning Protocol Mapping: Suggestion"

"Gould, James" <JGould@verisign.com> Sun, 05 April 2015 14:19 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 43B6F1A8A28 for <eppext@ietfa.amsl.com>; Sun, 5 Apr 2015 07:19:58 -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 MGxUFts6OyXy for <eppext@ietfa.amsl.com>; Sun, 5 Apr 2015 07:19:55 -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 6DBF41A8A04 for <eppext@ietf.org>; Sun, 5 Apr 2015 07:19:55 -0700 (PDT)
Received: by qgdz60 with SMTP id z60so371333qgd.3 for <eppext@ietf.org>; Sun, 05 Apr 2015 07:19:54 -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=nYaXHPEMqFtvZqF+yGL381q+Y0H4b7pHk7LIQTK67V0=; b=j4lXKNFXgJdtJ//13MUNbKBigt1J/08I5CddN6VVFCW2b59ASWlD4g/0pSyjGNYSQX Hszcrs/wB9AXibbS6yac3SmZ/hwaSzH5z8Wqq8zjVvCMYUPrffvBT3POT5WAbXqciEUQ h3uOkXN48gZ8CRDKW/o114vBLjetv/WsdqiE0RkTVgN/T/XSBV8yPZHovTuKrpfrslNI VBqO7R1Wfcq6xG52Dtga0V7ZGHeFywc8cUhWnEWrpneCVEXuRFnURVqbDjOy70UNV0H6 t3c8dLtS+k+qHvjhuFX7r+D/5+UTiiqWf/k1N0ooNAyMAVAZo29HCQm1mpmWCoeDke5N qFSA==
X-Gm-Message-State: ALoCoQntZYbOc8KJ77QhqV2qOf+m9ihOptCqk+FnYNgzeaR1H4W6/cOTqtO/NiZ5kj2iFQn1mInlpodKP7yirzb6avWNwtq/8Q==
X-Received: by 10.140.237.200 with SMTP id i191mr12497100qhc.86.1428243594596; Sun, 05 Apr 2015 07:19:54 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by mx.google.com with ESMTPS id l10sm463015qcs.4.2015.04.05.07.19.54 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 05 Apr 2015 07:19:54 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id t35EJr3T004549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 5 Apr 2015 10:19:53 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Sun, 5 Apr 2015 10:19:53 -0400
From: "Gould, James" <JGould@verisign.com>
To: Ning Kong <nkong@cnnic.cn>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gW0lBTkEgIzgxNDkxOF0gSU5TRVJUIOKAnEV4dGVuc2libGUg?= =?utf-8?Q?Provisioning_Protocol_Mapping:_Suggestion"?=
Thread-Index: AQHQZW/+hBedeuMgX0+tJtytUuwblJ0qVeUwgBKYtQCAAeDEAA==
Date: Sun, 5 Apr 2015 14:19:52 +0000
Message-ID: <3AABA114-B7D8-4C68-9EB3-31A35FE33696@verisign.com>
References: <RT-Ticket-814918@icann.org> <A973DE55-D717-4973-9C8B-733CF04742DD@verisign.com> <rt-4.2.9-2033-1427129077-1113.814918-9-0@icann.org> <831693C2CDA2E849A7D7A712B24E257F49F89B7A@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <AA7E5A6D-0592-4E16-A3D5-B3A59A5E0847@cnnic.cn>
In-Reply-To: <AA7E5A6D-0592-4E16-A3D5-B3A59A5E0847@cnnic.cn>
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_3AABA114B7D84C689EB331A35FE33696verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/4Zrd8WzZ7RmUP3dS1FiBUbfYi7k>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] =?utf-8?q?=5BIANA_=23814918=5D_INSERT_=E2=80=9CExtensibl?= =?utf-8?q?e_Provisioning_Protocol_Mapping=3A_Suggestion=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: Sun, 05 Apr 2015 14:19:58 -0000

Ning,

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 4, 2015, at 5:39 AM, Ning Kong <nkong@cnnic.cn<mailto:nkong@cnnic.cn>> wrote:


I have completed my review of the extension as DE and and I have the following comments to share:
#1 I strongly recommend adding some introduction info about this Suggestion extension in the Introduction section, because it is a little hard for the readers without background info to understand the intent of the extension.

Yes, I agree additional text could be added to the Introduction to provide additional context.  To provide some context, this mapping supports domain name suggestions (info command and response) where the client provides domain name suggestion query preferences and the server responds with a set of domain name suggestions based on the client query preferences.  This mapping demonstrates the use of an EPP mapping to support a server query interface for domain name suggestions.

#2 Furthermore, I think the name of this extension is a little broad. It would be better to choose a more specific name to avoid conflicts with other extensions in future.

I’m not sure if I agree with this since the purpose of the mapping is to provide suggestions, which is the object in this case.  I’m not aware of any existing or future conflicts.


I'm not aware of any conflicts with existing IETF work or other known extensions.

Ning


在 2015年3月24日,上午1:41,Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> 写道:

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:45 PM
Cc: Hollenbeck, Scott
Subject: [IANA #814918] INSERT “Extensible Provisioning Protocol Mapping: Suggestion"

#11 of 18.

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

Document Status:
Informational

Reference:
http://www.verisigninc.com/assets/epp-sdk/EPP-Suggestion-Mapping.pdf

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