Re: [EPP-discuss] RE: waiting list offering, pending deletion and the EPP command info domain

From: Jonas Brømsø Nielsen <jonasbn_at_dk-hostmaster.dk>
Date: Mon, 24 Oct 2016 09:05:14 +0000

Hi Tom,

In regard to extensions and their use, it is kind of a minefield.

We have aimed to keep our extension use limited and the same time the protocol opens up for using extensions and we have to fulfil certain requirements and this can only be done using extensions. We have tried to keep our extensions small and uniform.

We are following the work done in relation to RFC:7451 and we are trying to hold back, in order to change to EPP standard extensions when available.

Thanks for the inspirational resource, it will be evaluated for possible future improvements for our EPP service.

jonasbn

On 30 Sep 2016, at 11:18, Tom Sommer - Zitcom A/S <ts_at_zitcom.dk<mailto:ts_at_zitcom.dk>> wrote:

For inspiration, here is how EURid does it (https://filedump.zitcom.dk/download/9863/8aeedee346/EPP_0.zip):

Also look at their domain-check examples, if you like :)


<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:domain-ext="http://www.eurid.eu/xml/epp/domain-ext-2.1" xmlns:idn="http://www.eurid.eu/xml/epp/idn-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1">
    <response>
        <result code="1000">
            <msg>Command completed successfully</msg>
        </result>
        <resData>
            <domain:infData>
                <domain:name>domínio-qq.eu<http://xn--domnio-qq-i5a.eu/></domain:name>
                <domain:roid>xn__domnio_qq_i5a_eu-EURID</domain:roid>
                <domain:status s="ok"/>
                <domain:registrant>c160</domain:registrant>
                <domain:contact type="billing">c10</domain:contact>
                <domain:contact type="tech">c159</domain:contact>
                <domain:ns>
                    <domain:hostAttr>
                        <domain:hostName>ns.some-domain.biz<http://ns.some-domain.biz/></domain:hostName>
                    </domain:hostAttr>
                </domain:ns>
                <domain:clID>a987654</domain:clID>
                <domain:crID>a987654</domain:crID>
                <domain:crDate>2014-09-13T16:11:14.448Z</domain:crDate>
                <domain:upID>a987654</domain:upID>
                <domain:upDate>2014-09-13T16:11:55.000Z</domain:upDate>
                <domain:exDate>2015-09-13T21:59:59.999Z</domain:exDate>
            </domain:infData>
        </resData>
        <extension>
            <domain-ext-2.1:infData>
                <domain-ext-2.1:onHold>false</domain-ext-2.1:onHold>
                <domain-ext-2.1:quarantined>true</domain-ext-2.1:quarantined>
                <domain-ext-2.1:suspended>false</domain-ext-2.1:suspended>
                <domain-ext-2.1:seized>false</domain-ext-2.1:seized>
                <domain-ext-2.1:availableDate>2014-10-23T16:11:55.109Z</domain-ext-2.1:availableDate>
                <domain-ext-2.1:deletionDate>2014-09-13T16:11:55.109Z</domain-ext-2.1:deletionDate>
                <domain-ext-2.1:contact type="onsite">c163</domain-ext-2.1:contact>
                <domain-ext-2.1:delayed>true</domain-ext-2.1:delayed>
            </domain-ext-2.1:infData>
            <secDNS:infData>
                <secDNS:keyData>
                    <secDNS:flags>257</secDNS:flags>
                    <secDNS:protocol>3</secDNS:protocol>
                    <secDNS:alg>5</secDNS:alg>
                    <secDNS:pubKey>AwEAAc8mj6eqspwxX/E+OVoA/+MTawDce72K8UOgFmDAvilVqWKsXv9a6HQVPW/feDGHQ3cvGAisb1tv4/DFJBqWniLVr77S20JhhpB+MtuJkKSmb59basCItUo/B9MohZ4hFWsgWtL8HnIuJq1jMwXzmAO236EsUjXVzAdxhqsVX7v1</secDNS:pubKey>
                </secDNS:keyData>
            </secDNS:infData>
            <idn:mapping>
                <idn:name>
                    <idn:ace>xn--domnio-qq-i5a.eu<http://domnio-qq-i5a.eu/></idn:ace>
                    <idn:unicode>domínio-qq.eu<http://xn--domnio-qq-i5a.eu/></idn:unicode>
                </idn:name>
            </idn:mapping>
        </extension>
        <trID>
            <svTRID>e52408637-6911-438d-8264-3ab6f53d9350</svTRID>
        </trID>
    </response>
</epp>

--
Tom Sommer
UnoEuro Webhosting

From: Tom Sommer - Zitcom A/S [mailto:ts_at_zitcom.dk]
Sent: 30. september 2016 11:11
To: Jonas Brømsø Nielsen <jonasbn_at_dk-hostmaster.dk<mailto:jonasbn_at_dk-hostmaster.dk>>
Cc: epp-discuss_at_liste.dk-hostmaster.dk<mailto:epp-discuss_at_liste.dk-hostmaster.dk>
Subject: RE: [EPP-discuss] RE: waiting list offering, pending deletion and the EPP command info domain

> It would make sense to have to present it on domain:check, but I do not see what you should not have it on both after all it is an extension.

There is no reason to have the waitinglist status in domain:info, at all. It’s not the correct place to show the availability of a domain.

> We will use that, as I also stated, but that cannot communicate the advisory date.

True, the ’correct’ way to do it (compared to other EPP systems, and your own), would be:

<dkhm:domainDeletionDate xmlns:dkhm="urn:dkhm:params:xml:ns:dkhm-2.0”>2016-09-27T00:00:00.0Z</dkhm:domainDeletionDate>

Please use this format throughout your EPP system, and not change it.


--
Tom Sommer
UnoEuro Webhosting

From: Jonas Brømsø Nielsen [mailto:jonasbn_at_dk-hostmaster.dk]
Sent: 30. september 2016 11:05
To: Tom Sommer - Zitcom A/S <ts_at_zitcom.dk<mailto:ts_at_zitcom.dk>>
Cc: epp-discuss_at_liste.dk-hostmaster.dk<mailto:epp-discuss_at_liste.dk-hostmaster.dk>
Subject: Re: [EPP-discuss] RE: waiting list offering, pending deletion and the EPP command info domain

Hello Tom,

On 30 Sep 2016, at 10:37, Tom Sommer - Zitcom A/S <ts_at_zitcom.dk<mailto:ts_at_zitcom.dk>> wrote:

offeredOnWaitingList should be in domain:check, not domain:info

It would make sense to have to present it on domain:check, but I do not see what you should not have it on both after all it is an extension.


Also I believe there is an ‘official’ EPP status for pending delete? Why not use that?


We will use that, as I also stated, but that cannot communicate the advisory date.

jonasbn



--
Tom Sommer
UnoEuro Webhosting

From: Jonas Brømsø Nielsen [mailto:jonasbn_at_dk-hostmaster.dk]
Sent: 29. september 2016 21:49
To: epp-discuss_at_liste.dk-hostmaster.dk<mailto:epp-discuss_at_liste.dk-hostmaster.dk>
Subject: [EPP-discuss] waiting list offering, pending deletion and the EPP command info domain

hello All,

Since we want to be able to offer the same information via multiple channels, such as WHOIS, DAS, EPP and self-service.

We are evaluating how to communicate that a given domain has been offered to the first person on the waiting list via EPP and that a domain is pending a deletion.

This waiting list information is currently under evaluation in the DAS service and is specified in a draft of the specification and available in the DAS sandbox.

https://github.com/DK-Hostmaster/das-service-specification/tree/waiting_list_info

Our initial proposal is to use our own extension: domainAdvisory, used to communicate the special domain status of “blocked”

https://github.com/DK-Hostmaster/epp-service-specification#dkhmdomainadvisory

The idea would be to extend this with another enumerated value for waiting list, with a special advisory.


<dkhm:domainAdvisory xmlns:dkhm=“urn:dkhm:params:xml:ns:dkhm-1.6" domain=“offeredonwaitinglist.dk<http://offeredonwaitinglist.dk/>" advisory=“offeredOnWaitingList" />


For pending deletions we would use the EPP status code indicating the state, but with the additional use of the extension to communicate the advisory and the calculated deletion date.


<dkhm:domainAdvisory xmlns:dkhm="urn:dkhm:params:xml:ns:dkhm-2.0" domain="domainpendingdelete.dk<http://domainpendingdelete.dk/>" advisory="pendingDeletionDate" date="2016-09-27T00:00:00.0Z" />


For reference the XSD draft, version 1.6, enumerations not added, since it is basically a token.

         https://github.com/DK-Hostmaster/epp-xsd-files/tree/epp_domain_info_v1

Looking forward to your feedback,

jonasbn


<image001.png>


DK Hostmaster A/S
Kalvebod Brygge 45, 3. sal
DK-1560 København V

+45 3364 6060 • +45 3154 6056 • jonasbn_at_dk-hostmaster.dk<mailto:usc_at_dk-hostmaster.dk> • www.dk-hostmaster.dk<http://www.dk-hostmaster.dk/>


<image002.png>



This is an email from DIFO/ DK Hostmaster A/S. This message may contain confidential information and is intended solely for the use of the intended addressee. If you are not the intended addressee, please notify the sender immediately and delete this e-mail from your system.

<image001.png>


DK Hostmaster A/S
Kalvebod Brygge 45, 3. sal
DK-1560 København V

+45 3364 6060 • +45 3154 6056 • jonasbn_at_dk-hostmaster.dk<mailto:usc_at_dk-hostmaster.dk> • www.dk-hostmaster.dk<http://www.dk-hostmaster.dk/>


<image002.png>



This is an email from DIFO/ DK Hostmaster A/S. This message may contain confidential information and is intended solely for the use of the intended addressee. If you are not the intended addressee, please notify the sender immediately and delete this e-mail from your system.

[cid:65C7ED51-AD0F-4703-A79C-5E74CB78DF54]


DK Hostmaster A/S
Kalvebod Brygge 45, 3. sal
DK-1560 København V

+45 3364 6060 • +45 3154 6056 • jonasbn_at_dk-hostmaster.dk<mailto:usc_at_dk-hostmaster.dk> • www.dk-hostmaster.dk<http://www.dk-hostmaster.dk>






This is an email from DIFO/ DK Hostmaster A/S. This message may contain confidential information and is intended solely for the use of the intended addressee. If you are not the intended addressee, please notify the sender immediately and delete this e-mail from your system.


image001.png
(image/png attachment: image001.png)

image002.png
(image/png attachment: image002.png)

Received on Mon Oct 24 2016 - 11:05:14 CEST

This archive was generated by hypermail 2.3.0 : Mon Oct 24 2016 - 11:06:00 CEST