IETF Logo Mail Archive

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

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Mon, 06 April 2015 14:56 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 C466D1A8969 for <eppext@ietfa.amsl.com>; Mon, 6 Apr 2015 07:56:49 -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 TWCmmEsfANqe for <eppext@ietfa.amsl.com>; Mon, 6 Apr 2015 07:56:46 -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 65B261A897D for <eppext@ietf.org>; Mon, 6 Apr 2015 07:56:44 -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 16:56:43 +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 16:56:39 +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?W0lBTkEgIzgxNDkxN10gSU5TRVJUIOKAnEV4dGVuc2libGUgUHJvdmlzaW9u?= =?utf-8?B?aW5nIFByb3RvY29sIEV4dGVuc2lvbiBNYXBwaW5nOiBQZXJzb25hbCBSZWdp?= =?utf-8?Q?stration"?=
Thread-Index: AQHQZYiQ032d3bC53kyisbeAcyDnBp0qVc+ggBXQKeA=
Date: Mon, 6 Apr 2015 14:56:38 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE0754679B4A8@NICS-EXCH2.sbg.nic.at>
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>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49F89B32@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
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/UtCiUW9myoqSJ80hLTyJeEuswiU>
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 14:56:49 -0000

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..
- (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?)
- in 3.2.1, there seems to be a typo in the XML frame (missing line break after </create>)

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

v2.8.7 | Report a Bug | By Email