Re: [eppext] : [IANA #814928] INSERT “Related Domain Extension for the Extensible Provisioning Protocol (EPP)"
Alexander Mayrhofer <alexander.mayrhofer@nic.at> Mon, 06 April 2015 15:06 UTC
Return-Path: <alexander.mayrhofer@nic.at>
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 439951A8A08
for <eppext@ietfa.amsl.com>; Mon, 6 Apr 2015 08:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.431
X-Spam-Level:
X-Spam-Status: No, score=-5.431 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745,
MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5,
T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-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 f761A8YspOd5 for <eppext@ietfa.amsl.com>;
Mon, 6 Apr 2015 08:06:28 -0700 (PDT)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227])
(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 7B19C1A8A07
for <eppext@ietf.org>; Mon, 6 Apr 2015 08:06:27 -0700 (PDT)
Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at
over TLS secured channel (TLSv1:AES128-SHA:128) with XWall v3.50 ;
Mon, 6 Apr 2015 17:06:26 +0200
Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by
NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id
14.03.0224.002; Mon, 6 Apr 2015 17:06:23 +0200
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "eppext@ietf.org"
<eppext@ietf.org>
Thread-Topic: =?utf-8?B?OiBbSUFOQSAjODE0OTI4XSBJTlNFUlQg4oCcUmVsYXRlZCBEb21haW4gRXh0?=
=?utf-8?B?ZW5zaW9uIGZvciB0aGUgRXh0ZW5zaWJsZSBQcm92aXNpb25pbmcgUHJvdG9j?=
=?utf-8?Q?ol_(EPP)"?=
Thread-Index: AdBwefzdthS5w6SfS3CKuakPfIY0xA==
Date: Mon, 6 Apr 2015 15:06:23 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE0754679B4F0@NICS-EXCH2.sbg.nic.at>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.3.102]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-XWALL-BCKS: auto
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/EaN198Ntg4e0fEDUEYXdBkJ4sqk>
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:06:29 -0000
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 - Even though the extension tries to achieve a slightly different problem, there are other extensions attempting to solve "bundling related" problems. - 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. 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-----
- Re: [eppext] : [IANA #814928] INSERT “Related Dom… Alexander Mayrhofer
- Re: [eppext] : [IANA #814928] INSERT “Related Dom… Gould, James