[gnso-rds-pdp-wg] Proposed Agreement for Original Registration Date

Volker Greimann vgreimann at key-systems.net
Thu Sep 21 14:16:12 UTC 2017


Hi Paul,

the original registration date in its original conception was a date 
that could be equal or lower than the created date, but never higher, if 
that makes sense as it would only refer to previous registrations of 
this same string or the current one if that were the earliest. If you 
changed whois informations, the registration object would remain the 
same, so the ORD would not change. If a domain object is deleted at the 
registry and then a new registration object consisting of the same 
string were to be registered the ORD would refer to the earlier 
registration of that string, not the current one.

But as Andrew pointed out, we moved away from proposing a date and 
instead proposed a marker.

Best,

Volker



Am 21.09.2017 um 15:53 schrieb Paul Keating:
> So that leads me to further questions.
>
> What data element is it keying from to determine original status?
>
> Would it change if I changed the WHOIS elements below (e.g. My name to a
> company name or my address to a different address?)
>
> Thanks
>
> Paul
>
> On 9/21/17, 3:27 PM, "Andrew Sullivan" <gnso-rds-pdp-wg-bounces at icann.org
> on behalf of ajs at anvilwalrusden.com> wrote:
>
>> On Thu, Sep 21, 2017 at 03:21:27PM +0200, Paul Keating wrote:
>>> Question:  What is the definition of ³Original Registration Date².  How
>>> does
>>> it operate when a domain has expired and is re-registered?
>> The idea is to track the date of creation of a previous domain object
>> that had the same name.  Note that some of us who worked on this
>> problem have some reservations, which is why we have recommended
>> something else.
>>
>> Best regards,
>>
>> A
>>
>> -- 
>> Andrew Sullivan
>> ajs at anvilwalrusden.com
>> _______________________________________________
>> gnso-rds-pdp-wg mailing list
>> gnso-rds-pdp-wg at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg

-- 
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.

Mit freundlichen Grüßen,

Volker A. Greimann
- Rechtsabteilung -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann at key-systems.net

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems
www.twitter.com/key_systems

Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534

Member of the KEYDRIVE GROUP
www.keydrive.lu

Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.

--------------------------------------------

Should you have any further questions, please do not hesitate to contact us.

Best regards,

Volker A. Greimann
- legal department -

Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann at key-systems.net

Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com

Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems
www.twitter.com/key_systems

CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534

Member of the KEYDRIVE GROUP
www.keydrive.lu

This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.





More information about the gnso-rds-pdp-wg mailing list