Re: [eppext] [IANA #814914] INSERT “Extensible Provisioning Protocol Mapping: Email Forwarding"

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Thu, 02 April 2015 14: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 B02DB1A90F0 for <eppext@ietfa.amsl.com>; Thu, 2 Apr 2015 07:06:54 -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 iyznTRDWcc9O for <eppext@ietfa.amsl.com>; Thu, 2 Apr 2015 07:06:52 -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 06E3F1A92AD for <eppext@ietf.org>; Thu, 2 Apr 2015 07:06:46 -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 ; Thu, 2 Apr 2015 16:06:44 +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; Thu, 2 Apr 2015 16:06:43 +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?W0lBTkEgIzgxNDkxNF0gSU5TRVJUIOKAnEV4dGVuc2libGUgUHJvdmlzaW9u?= =?utf-8?Q?ing_Protocol_Mapping:_Email_Forwarding"?=
Thread-Index: AdBtHj8J6wWovVNkQq+7o8PhIPcoIQ==
Date: Thu, 2 Apr 2015 14:06:41 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE07546799141@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: [10.10.0.163]
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/AyEA-CpKsR1ispyLb1IHJBV668U>
Subject: Re: [eppext] =?utf-8?q?=5BIANA_=23814914=5D_INSERT_=E2=80=9CExtensibl?= =?utf-8?q?e_Provisioning_Protocol_Mapping=3A_Email_Forwarding=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: Thu, 02 Apr 2015 14:06:54 -0000

All,

I've completed my review of the extension registration request, and my (nit-picking level) comments are as follows:

- My previous concerns about the "VERISIGN PROPRIETORY INFORMATION" paragraph apply to this document as well.

- The references to the EPP specifications are outdated

- In Section 2.1, are servers REQUIRED to validate that email forwarding names actually comply to RFC2822? 

- In Section 2.3, service messages are REQUIRED to be sent to clients. However, the document does not specify the format of the actual messages. I assume there is no such formal definition then?

As a summary, the specification is very well written. I have not formally checked the Schema definition.

tia,
Alex


> -----BEGIN FORM-----
> Name of Extension:
> “Extensible Provisioning Protocol Mapping: Email Forwarding"
> 
> Document Status:
> Informational
> 
> Reference:
> http://www.verisigninc.com/assets/email-forwarding-mapping.pdf
> 
> Registrant Name and Email Address:
> VeriSign Inc., epp-registry@verisign.com
> 
> TLDs: .name
> 
> IPR Disclosure: None
> 
> Status: Active
> 
> Notes: None
> -----END FORM-----