Re: [eppext] Fw: I-D Action: draft-zhou-eppext-reseller-00.txt

Patrick Mevzek <pm@dotandco.com> Sun, 17 May 2015 00:14 UTC

Return-Path: <patrick@shaktot.patoche.org>
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 F31DC1A8868 for <eppext@ietfa.amsl.com>; Sat, 16 May 2015 17:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.388
X-Spam-Level: *
X-Spam-Status: No, score=1.388 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_57=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 8zhdUe0Xy6QP for <eppext@ietfa.amsl.com>; Sat, 16 May 2015 17:14:46 -0700 (PDT)
Received: from shaktot.patoche.org (shaktot.patoche.org [212.85.152.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA39C1A8867 for <eppext@ietf.org>; Sat, 16 May 2015 17:14:45 -0700 (PDT)
Received: from shaktot.patoche.org (localhost.localdomain [127.0.0.1]) by shaktot.patoche.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id t4H0EZ5F010857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 17 May 2015 02:14:35 +0200
Received: (from patrick@localhost) by shaktot.patoche.org (8.14.3/8.14.3/Submit) id t4H0EZR5010856; Sun, 17 May 2015 02:14:35 +0200
Date: Sun, 17 May 2015 02:14:33 +0200
From: Patrick Mevzek <pm@dotandco.com>
To: eppext@ietf.org
Message-ID: <20150517001433.GA26237@home.patoche.org>
References: <20150504162934440371144@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20150504162934440371144@cnnic.cn>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Scanned-By: shaktot_dot_patoche_dot_org on 212.85.152.86
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/moTHniD23aL_IBLKuuB3cS9-LDU>
Subject: Re: [eppext] Fw: I-D Action: draft-zhou-eppext-reseller-00.txt
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: Sun, 17 May 2015 00:14:47 -0000

Hello Linlin, Ning, Chao, Xiaodong, and James,

Linlin Zhou <zhoulinlin@cnnic.cn> 2015-05-04 10:28
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  
>  
>         Title           : Registry Reseller Extension for the Extensible Provisioning Protocol (EPP)
>         Authors         : Linlin Zhou
>                           Ning Kong
>                           Chao Qi
>                           Xiaodong Lee
>                           James Gould
> Filename        : draft-zhou-eppext-reseller-00.txt
> Pages           : 16
> Date            : 2015-05-04
 
I'm implementing it in my opensource EPP client, and I have the
following comments/questions:

- the resName node is of type "string", without any lower limit of
  length, I believe it would make sense to mandate at least one
character…

- since create and update operations are extended for all 3 kind of
  core EPP objects (domain, host, contact), there should be some more
explanations on what happens when a domain name is created with
reseller X, where in-bailiwick hosts of this domain are created with
reseller Y and contacts used for the domain were created with reseller
Z. Does that make any sense? Does the registry want to permit this
case?

- there should be some explanations on what happens for a domain name
  with a reseller that get transfered to another registrar (where
obvisouly the given previous reseller would not exist). Will the
reseller info be automatically removed after the transfer finishes?

- I'm not sure to understand completely the update case.
In short, in my understanding, I would expect that there would be a
sentence stating that "only one add, or rem or chg element is
permitted", so that there are not mix of add/rem/chg, because in that
later case it would be difficult to understand what happens.
Also in that case there should be explanations on what happens when
the registrar does an add where the domain already has a reseller (for
me that should be rejected, because a registrar should do a chg in
that case), and what happens for a del where the domain has no
reseller (this could be handled as a noop), and what happens for a chg
where there is no reseller for now (this should be rejected)

For the chg case, there should be a clear explanation on what happens
if we have a resID+resName currently but the chg element contains only
the resID… will the resName be removed automatically? This should be
more specified, as it is similar to that postalAddress problem in core
EPP.

-- 
Patrick Mevzek