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

[Marc Groeneweg <[e-mail]>]

Dear Linlin,

Herewith, as promised, my feedback on the draft proposal on the reseller extension:

General: why is this draft called draft-zhou-eppext-reseller instead of draft-zhou-eppext-reseller-ext? As it is the description of the extensions for reseller to other objects?

What is the reason you reference to [RFC5732] and [RFC5733], as the extension only extends the domain object [RFC5731]?

In general, shouldn’t refer to the reseller elements as reseller ext elements, as it describes the extensions to existing elements with reseller information?
I.e. the extension to the <info> command being a child <resellerExt:infData> instead of <reseller:infData>? This seems more obvious to me. Oh wait a moment, in your example you do call it reseller ext:inflate. The tekst is not in line with the example.

Why do you have an OPTIONAL <resellerext:name> element? Isn’t the name of a reseller part of the reseller object? And when one uses this element, does it refer to the parent reseller?

What is the purpose to he following statement?
"<info> response for the unauthorized client has not been changed, see [RFC5731], [RFC5732] and [RFC5733]for detail.”

In section 4.2.1. EPP <create> command you don’t reference to the OPTIONAL <resellerext:name> element.
Again, I don’t understand the references to the host and contact objects, since they are not extended in any way.

Section 4.2.5. EPP <update> command
I understand the need for the add and rem elements. With this one can add and remove references to reseller objects to the domain object.
I don’t understand the restriction for having only one add, rem or chg element. This prohibits the construction to change the reseller from A to B for given domain object. See following example from within .nl:

   C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   C:  <command>
   C:    <update>
   C:      <domain:update
   C:       xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
   C:        <domain:name>example.com</domain:name>
   C:      </domain:update>
   C:    </update>
   C:    <extension>
   C:      <resellerExt:update
   C:       xmlns:resellerExt="urn:ietf:params:xml:ns:sidn-ext-epp-reseller-1.0">
   C:        <resellerExt:rem>
   C:          <resellerExt:id>rs1234</resellerExt:id>
   C:        </resellerExt:rem>
   C:        <resellerExt:add>
   C:          <resellerExt:id>rs5678</resellerExt:id>
   C:        </resellerExt:add>
   C:      </resellerExt:update>
   C:    </extension>
   C:    <clTRID>ABC-12345</clTRID>
   C:  </command>
   C:</epp>

I guess the chg element is needed for changing the resellerext:name element? There is no mention to this.

Best regards,
Marc Groeneweg