Re: [eppext] Fw: I-D Action: draft-zhou-eppext-reseller-00.txt
"Linlin Zhou" <zhoulinlin@cnnic.cn> Tue, 19 May 2015 03:51 UTC
Return-Path: <zhoulinlin@cnnic.cn>
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 EA5E31B2E12
for <eppext@ietfa.amsl.com>; Mon, 18 May 2015 20:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.39
X-Spam-Level: *
X-Spam-Status: No, score=1.39 tagged_above=-999 required=5
tests=[BAYES_50=0.8, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001,
J_CHICKENPOX_66=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 oQjvO8KRry3c for <eppext@ietfa.amsl.com>;
Mon, 18 May 2015 20:51:35 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13])
by ietfa.amsl.com (Postfix) with ESMTP id 3CC6F1B2E11
for <eppext@ietf.org>; Mon, 18 May 2015 20:51:34 -0700 (PDT)
Received: from Foxmail (unknown [218.241.111.73])
by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0BpcJQ5s1pVSoBRBw--.1973S2;
Tue, 19 May 2015 11:51:21 +0800 (CST)
Date: Tue, 19 May 2015 11:53:36 +0800
From: "Linlin Zhou" <zhoulinlin@cnnic.cn>
To: "Patrick Mevzek" <pm@dotandco.com>,
"eppext@ietf.org" <eppext@ietf.org>
References: <20150504162934440371144@cnnic.cn>,
<20150517001433.GA26237@home.patoche.org>,
<2015051812000406846958@cnnic.cn>,
<20150518141551.GA10658@home.patoche.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <2015051911532898326091@cnnic.cn>
Content-Type: multipart/alternative;
boundary="----=_001_NextPart237253531471_=----"
X-CM-TRANSID: AQAAf0BpcJQ5s1pVSoBRBw--.1973S2
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73
VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUUOA7k0a2IF6w4kM7kC6x804xWl14x267AK
xVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw
A2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK021l84ACjcxK6xIIjxv20xvE14v26ryj
6F1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26F4j6r4UJwA2z4x0Y4vEx4A2jsIE14v26F
4UJVW0owA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAa
Y2xG8wAqx4xG62kEwI0EY4vaYxAvb48xMc02F40E42I26xC2a48xMc02F40Ex7xS67I2xx
kvbII20VAFz48EcVAYj21lYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j
6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwACY4xI67k04243AVAKzV
AKj4xxM4xvF2IEb7IF0Fy26I8I3I1l7480Y4vEI4kI2Ix0rVAqx4xJMxkIecxEwVAFwVW8
GwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r
106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij
64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr
0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1l
IxAIcVC2z280aVCY1x0267AKxVWUJVW8JwCE64xvF2IEb7IF0Fy7YxBIdaVFxhVjvjDU0x
ZFpf9x07bzR67UUUUU=
X-CM-SenderInfo: p2kr3zplqox0w6fq0xffof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/hEBG8V1IBYS1ovGUjb7ZUxyD3HY>
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: Tue, 19 May 2015 03:51:37 -0000
Hi Patrick, > -----原始邮件----- > 发件人: "Patrick Mevzek" <pm@dotandco.com> > 发送时间: 2015-05-18 22:15:51 (星期一) > 收件人: eppext@ietf.org > 抄送: > 主题: Re: [eppext] Fw: I-D Action: draft-zhou-eppext-reseller-00.txt > > Linlin Zhou <zhoulinlin@cnnic.cn> 2015-05-18 05:59 > > > - 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? > > > > > If a domain is transfered to a new registrar, the registrar or > > reseller will do a domian update operation to update the > > corresponding reseller information. > > Not necessarily possible, if the new registrar does not use at all the > resellerext EPP extension… and I doubt that a registry could mandate > all registrars to use it. > And even if he uses the extension, what mandates him to update the > domain? Technically, nothing. If the reseller info is displayed > somewhere (whois, escrow, etc…), then a wrong information would be > shown. > > This is the same problem as a transfer with secDNS information. > > So it will probably be a registry policy, but we may have some > scenarios where the reseller info will be kept through the transfer, > and other scenarios where it will be wiped out (and if the new > registrar wants to specify its own reseller he will do a domain:update > afterwards). > But maybe the draft should have a sentence about that. > I understand your consideration. I agree that some text should be added to clarify this problem. What do you think about James' suggested text? "This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the [RFC5730], but after a successful transfer of an object with an assigned reseller, the server SHOULD clear the assigned reseller value." > 2 other points while I'm at it and implementing your other draft: > - I will post comments later on your other drafts Comments are welcome. > - I believe there should be somewhere an explanation on how your two > drafts articulate between themselves. My understanding is that > registrars will create reseller objets with the reseller mapping I-D, > and then create domains with the resellerID for the reseller object > they created previsouly. If that is not what is intended, some > clarifications should be added somewhere. > Yes, you are right. This is what I am thinking about. There should be some text to describe the relationship between the two drafts. I intend to add a sentence in the intrduction section, such as "A reseller mapping object defined in [ID.draft-zhou-eppext-reseller-mapping] SHOULD be created first. The reseller information specified in this document SHOULD reference the existing reseller identifier and reseller name." Then indicate the specified elements defined in draft-zhou-eppext-reseller-mapping in section 3.1 and 3.2. For example: 3.1. Reseller Identifier Reseller identifier provides the ID of the reseller of a sponsoring registrar. Its corresponding element is <resellerext:resID> defined in this document. It refers to the <reseller:id> element defined in [ID.draft-zhou-eppext-reseller-mapping]. 3.2. Reseller Name Reseller name provides the name of the reseller of a sponsoring registrar. Its corresponding element is <resellerext:resName> defined in this document. It refers to the <reseller:name> element defined in [ID.draft-zhou-eppext-reseller-mapping]. Regards, Linlin
- [eppext] Fw: I-D Action: draft-zhou-eppext-resell… Linlin Zhou
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Marc Groeneweg
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Linlin Zhou
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Patrick Mevzek
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Patrick Mevzek
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Patrick Mevzek
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Linlin Zhou
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Linlin Zhou
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Linlin Zhou
- Re: [eppext] I-D Action: draft-zhou-eppext-resell… Gould, James
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Patrick Mevzek
- Re: [eppext] I-D Action: draft-zhou-eppext-resell… Linlin Zhou
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Linlin Zhou
- Re: [eppext] Fw: I-D Action: draft-zhou-eppext-re… Patrick Mevzek