Re: [eppext] : [IANA #814928] INSERT “Related Domain Extension for the Extensible Provisioning Protocol (EPP)"
"Gould, James" <JGould@verisign.com> Mon, 06 April 2015 15:45 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 7311B1A8A4F
for <eppext@ietfa.amsl.com>; Mon, 6 Apr 2015 08:45:13 -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 WMH9tWZNmuNU for <eppext@ietfa.amsl.com>;
Mon, 6 Apr 2015 08:45:05 -0700 (PDT)
Received: from mail-qg0-f100.google.com (mail-qg0-f100.google.com
[209.85.192.100])
(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 3378F1A8A57
for <eppext@ietf.org>; Mon, 6 Apr 2015 08:45:03 -0700 (PDT)
Received: by qgdq107 with SMTP id q107so1405034qgd.2
for <eppext@ietf.org>; Mon, 06 Apr 2015 08:45:02 -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=eaCwNg6bxkE7O0HC/m6O2/E6hGKNpIPdkD1sZGStUDY=;
b=I4B2oLM0qOB+oyOhtfJ7AyRgRpQ83d+oRdSkdJB5bsZPYbPmp8eAcRNqUOS/WigVdv
wCswQetB12Jx/4AzDlwoZRmqxYH8LuJ/IKo3jgAKfcQ6Q9rj0XVIxC9Ii+10wulnMviS
kP+6GekBlOoMgZ89fSwMcACEKJsDDAN/XxZvFCDS5kFRt+Did/inC3Td28DhwbrJahZW
qnT7keSQpYjw6J+Y+RiH/Qk8lxVGi7R59+pqgYsS8Yr+N/7SbQsEWFFSLuLSPrcL62ZZ
nRwGT78jny++qR0p3WlUrdJn2uNQWKDeimF3z5CMrsLQucWzpnXiIXhhv+GO49FkoBrk
bF8w==
X-Gm-Message-State: ALoCoQnzP9epRMR76OOipbcf6qyJeLtnsd7e0/61CYM7cOQnsBdbMUzrsBx+CNBabtPkA+z5NwvoV3AXHZ30IiVaQ5OLnkAKDg==
X-Received: by 10.140.21.233 with SMTP id 96mr17682375qgl.78.1428335102400;
Mon, 06 Apr 2015 08:45:02 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com.
[72.13.63.42])
by mx.google.com with ESMTPS id y7sm253209qci.3.2015.04.06.08.45.02
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Mon, 06 Apr 2015 08:45:02 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205])
by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id t36Fj1QV014073
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Mon, 6 Apr 2015 11:45:01 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by
brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 6
Apr 2015 11:45:01 -0400
From: "Gould, James" <JGould@verisign.com>
To: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
Thread-Topic: =?utf-8?B?W2VwcGV4dF0gOiBbSUFOQSAjODE0OTI4XSBJTlNFUlQg4oCcUmVsYXRlZCBE?=
=?utf-8?B?b21haW4gRXh0ZW5zaW9uIGZvciB0aGUgRXh0ZW5zaWJsZSBQcm92aXNpb25p?=
=?utf-8?Q?ng_Protocol_(EPP)"?=
Thread-Index: AdBwefzdthS5w6SfS3CKuakPfIY0xAAKDXCA
Date: Mon, 6 Apr 2015 15:45:01 +0000
Message-ID: <2BAF3FDF-2C69-488C-860F-5441037DFE20@verisign.com>
References: <19F54F2956911544A32543B8A9BDE0754679B4F0@NICS-EXCH2.sbg.nic.at>
In-Reply-To: <19F54F2956911544A32543B8A9BDE0754679B4F0@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_2BAF3FDF2C69488C860F5441037DFE20verisigncom_";
type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/wYwIcE94LcDjp55hicdBhRMHRZ0>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>,
"eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] =?utf-8?b?OiBbSUFOQSAjODE0OTI4XSBJTlNFUlQg4oCcUmVsYXRl?=
=?utf-8?q?d_Domain_Extension_for_the_Extensible_Provisioning_Protocol_=28?=
=?utf-8?b?RVBQKSI=?=
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:45:13 -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 11:06 AM, Alexander Mayrhofer <alexander.mayrhofer@nic.at<mailto:alexander.mayrhofer@nic.at>> wrote: I have completed my review of the extension registration request, and i have no significant comments. Nits: - Again, I'm concerned about the practicality of the implications of the "VERISIGN PROPRIETARY INFORMATION” paragraph Same response to the copyright notice concern. - Even though the extension tries to achieve a slightly different problem, there are other extensions attempting to solve "bundling related" problems. Yes, this extension addresses our specific approach to bundling. in the end, we may want to look at how to solve the broader set of bundling problems by as stated in a prior reply “bundle the bundles”. - I have slight concerns about the process of the "transfer" of domain objects using this extension. Particularly because there's description of the "transfer request" command only, which makes me think about situations where a losing registrar would issue a "mixed" set of accepts and rejects for a pending transfer? However, i understand that this extension is in production for a TLD, so maybe the specification just needs more description of these cases. Any one of the transfer operations is supported, but you are correct that there is only a sample provided for the transfer request. The goal is to enable clients (gaining or losing) to be capable of treating the related domains as a single set. Note: I have not formally validated the XML Schema. tia, Alex -----BEGIN FORM----- Name of Extension: “Related Domain Extension for the Extensible Provisioning Protocol (EPP)" Document Status: Informational Reference: http://www.verisigninc.com/assets/epp-sdk/verisign_epp- extension_related-domain_v00.html Registrant Name and Email Address: VeriSign Inc., epp-registry@verisign.com TLDs: Any IPR Disclosure: https://datatracker.ietf.org/ipr/2553/ Status: Active Notes: None -----END FORM----- _______________________________________________ EppExt mailing list EppExt@ietf.org<mailto:EppExt@ietf.org> https://www.ietf.org/mailman/listinfo/eppext
- Re: [eppext] : [IANA #814928] INSERT “Related Dom… Alexander Mayrhofer
- Re: [eppext] : [IANA #814928] INSERT “Related Dom… Gould, James