Re: [eppext] [IANA #814927] INSERT “Registry Mapping for the Extensible Provisioning Protocol (EPP)"

"Gould, James" <JGould@verisign.com> Fri, 03 April 2015 15:47 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 DF9A01ABD3F for <eppext@ietfa.amsl.com>; Fri, 3 Apr 2015 08:47:01 -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 Lsx7mhITHURH for <eppext@ietfa.amsl.com>; Fri, 3 Apr 2015 08:46:59 -0700 (PDT)
Received: from mail-qg0-f97.google.com (mail-qg0-f97.google.com [209.85.192.97]) (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 3346D1A044D for <eppext@ietf.org>; Fri, 3 Apr 2015 08:46:59 -0700 (PDT)
Received: by qgdq107 with SMTP id q107so2591966qgd.2 for <eppext@ietf.org>; Fri, 03 Apr 2015 08:46:58 -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=ebSgL8BGeBsKgVrqFuZ2dOK59iPGzFJa6GDMuwUK3ZQ=; b=gABZaaICZ/43M6ngblt9DLacS+sWxrlWNbiZkHTS+ZrlmvZfbBWoBEV/1wt0qNaaT/ /6Q4aPrMzufjM+ihMmS+qMPlArmmHvHA7RH98kvGQ5G8+T5Tt8DQpSQbNPhuV0ac23+W zX+Le4IVdzCdK+BtYfq+AxMj4vdQtFqofAr0t3lGjJK5o5qPD7249mRyUf8D+9XYt2/h MgvsixtmzVyqHNNRX8WkT0jbVMjVGlY7wlzRtakpBS8lfdfvWoDTEQnEKG09CDPuAN+z RfBvy3t7rTi01kbnNZ4gDmeGpFH46SSUzZ0qBYjWOcD6kpz0Ff1CRYllrCOxIia4jzI/ e61w==
X-Gm-Message-State: ALoCoQnlHt+3C8Q7pq1uKagRDXlDiLpqy0hx9k0dEV/Qp5kVwg+pWRQBaMx70e7pyIV3/hhhE1LL9x4bsnDBc75kF1eO2snc4A==
X-Received: by 10.140.195.5 with SMTP id q5mr3494752qha.58.1428076018441; Fri, 03 Apr 2015 08:46:58 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id cd6sm1994541qcb.2.2015.04.03.08.46.58 for <eppext@ietf.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 03 Apr 2015 08:46:58 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t33Fkvr4031568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <eppext@ietf.org>; Fri, 3 Apr 2015 11:46:57 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 3 Apr 2015 11:46:57 -0400
From: "Gould, James" <JGould@verisign.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gW0lBTkEgIzgxNDkyN10gSU5TRVJUIOKAnFJlZ2lzdHJ5IE1h?= =?utf-8?B?cHBpbmcgZm9yIHRoZSBFeHRlbnNpYmxlIFByb3Zpc2lvbmluZyBQcm90b2Nv?= =?utf-8?Q?l_(EPP)"?=
Thread-Index: AQHQZXD3rt2CmKt8tU6Q/rfhCyKYV50qVokwgBEpJoCAAENXAA==
Date: Fri, 3 Apr 2015 15:46:57 +0000
Message-ID: <3CAE75B0-6575-4C5A-9D3E-8D580229F9DC@verisign.com>
References: <RT-Ticket-814927@icann.org> <99A9181F-4A2C-4C16-B8AA-03F185A29B53@verisign.com> <rt-4.2.9-13014-1427129324-773.814927-9-0@icann.org> <831693C2CDA2E849A7D7A712B24E257F49F89BED@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F49F945EA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49F945EA@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_3CAE75B065754C5A9D3E8D580229F9DCverisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/ZwrgVoRz2XtwNWfVn1ZQC4FJ_Lg>
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] =?utf-8?q?=5BIANA_=23814927=5D_INSERT_=E2=80=9CRegistry_?= =?utf-8?q?Mapping_for_the_Extensible_Provisioning_Protocol_=28EPP=29=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 15:47:02 -0000

Scott,

Thanks, I made note of the need for the informative reference to the “Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)”.


—


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:46 AM, Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> wrote:

I've completed my review of this extension. The extension includes a link to the "Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)" (a current EPPEXT work item), but that extension isn't included as a reference - it should be listed as an informative reference. I'll note that the phases described in this extension are described as "based on" the phases specified in draft-ietf-eppext-launchphase, but they apparently are not intended to match one-for-one.

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

Scott

-----Original Message-----
From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Hollenbeck,
Scott
Sent: Monday, March 23, 2015 1:43 PM
To: eppext@ietf.org<mailto:eppext@ietf.org>
Subject: [eppext] FW: [IANA #814927] INSERT “Registry Mapping 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:49 PM
Cc: Hollenbeck, Scott
Subject: [IANA #814927] INSERT “Registry Mapping for the Extensible
Provisioning Protocol (EPP)"

#17 of 18.

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

Document Status:
Informational

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

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

TLDs: Any

IPR Disclosure: https://datatracker.ietf.org/ipr/2552/

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