[gnso-rds-pdp-wg] RDS Statement of Purpose

Fri Sep 9 12:34:59 UTC 2016

Hi James,

thanks for your questions. I think ICANN wanted to demonstrate a basic 
standard  sample life cycle of a domain, hence the reference to a 
typical domain. There may be differences from TLD to TLD and also 
between domains depending on what the circumstances of their 
registration are. Heck, life cycles may be different even between 
registrars depending on the contractual framework between registrar and 
registrant.

As for non-registered reserved names, I do not consider those as domains 
in the standard domain life cycle, but rather as "unborn" domains. 
Registered reserved names are again different. Some of those will be 
registered through a registrar normally (see Uniregistry premium model) 
and therefore will follow the standard life cycle closely, while others 
will be registered by the registry under the "100 names model" and 
exhibit a unique life cycle as no registrar is involved.

Best,

Volker

Am 09.09.2016 um 14:26 schrieb James Galvin:
> I believe we are in agreement but just to be sure let me ask a 
> specific question related to the diagram you referenced.
>
> In that diagram, a registrant identity would be associated with a 
> domain from the point immediately after the “available” cloud to the 
> point just before the “released” cloud.
>
> Further, I could imagine, going back to a comment that Share Kerr 
> made, that a parallel line exists for names that are reserved by a 
> registry, i.e., the “registrant” (or contact information) for a 
> reserved name is the registry.  My reason for suggesting a separate 
> path is because the events that affect the life cycle of a reserved 
> name are different than those that affect a registered name.
>
> Do you agree?
>
> Jim
>
>
>
>
> On 9 Sep 2016, at 6:07, Volker Greimann wrote:
>
>> Hi Greg,
>>
>> in the industry, the life cycle of a domain refers to the stages a 
>> domain goes through from birth to death, err, from registration to 
>> deletion. See also:
>>
>> https://www.icann.org/resources/pages/gtld-lifecycle-2012-02-25-en
>>
>> This may vary from TLD to TLD and on the terms of your registrar.
>>
>> The minimum standard would in this context be a display of the 
>> current status of the domain in its life cycle, for example: pending 
>> delete for a domain about to die, err, deleted. As a primary purpose, 
>> the domain registration data minimum should include everything 
>> necessary to the management of the domain lifecycle.
>>
>> Best,
>>
>> Volker
>>
>>
>>
>> Am 08.09.2016 um 21:21 schrieb Greg Shatan:
>>> I expressed a concern about this on the call (it may have been in 
>>> the chat), along the following lines:  What exactly is meant by "the 
>>> life-cycle of a domain name"?
>>>
>>> Also, is this meant to be a minimum standard (i.e., RDS must, at a 
>>> minimum, support the life-cycle of a domain name), to which other 
>>> elements can be added?
>>>
>>> Or is this meant to be a limiting standard (i.e., RDS must not do 
>>> more than support the life-cycle of a domain name), to which other 
>>> elements can be added only if they fit within the "life-cycle of a 
>>> domain name"?
>>>
>>> Or is this meant to be a "primary purpose" standard, where other 
>>> elements can be added, but they would not be considered a "primary 
>>> purpose" (which has a significant downstream effect, e.g., in 
>>> certain privacy legislation)?
>>>
>>> Finally, I would ask which of the use cases that we have on our list 
>>> fall within "the life-cycle of a domain name" and which do not?  (I 
>>> suppose this last question is intertwined with my first question above.
>>>
>>> Depending on what other participants believe the answers to these 
>>> questions should be, and what their effect may be, I may have 
>>> significant concerns about this statement.
>>>
>>> Greg
>>>
>>> On Thu, Sep 8, 2016 at 2:52 PM, Gomes, Chuck <cgomes at verisign.com 
>>> <mailto:cgomes at verisign.com>> wrote:
>>>
>>>     In our call earlier this week there seemed to be support for one
>>>     element of a RDS Statement of Purpose as suggested by Jim 
>>> Galvin:     “The RDS should support the life cycle of a domain 
>>> name.” No one
>>>     on the call disagreed with this; if anyone not on the call has
>>>     comments on this please communicate so on this list prior to our
>>>     call next week. Also, if any one who was on the call has comments
>>>     that you did not share, please do so before next week’s meeting.
>>>
>>>     Also, it would be helpful if everyone could be thinking about
>>>     answers to the following questions:
>>>
>>>     ·What are the criteria for a statement of purpose?
>>>
>>>     ·What elements, if any, from the EWG statement of purpose should
>>>     be reflected in the statement of purpose?
>>>
>>>     ·What other elements need to be reflected in the statement of 
>>> purpose?
>>>
>>>     We plan to discuss these questions in next week’s meeting but
>>>     comments would be appreciated on the list before then.
>>>
>>>     Chuck
>>>
>>>     Here’s the EWG statement of purpose that we discussed in our
>>>     meeting earlier this week:
>>>
>>>     To help guide the EWG in its deliberations, the group developed a
>>>     high-level statement of purpose from which to test its conclusions
>>>     and recommendations, as follows:
>>>
>>>     In support of ICANN’s mission to coordinate the global Internet’s
>>>     system of unique identifiers, and to ensure the stable and secure
>>>     operation of the Internet’s unique identifier system, information
>>>     about gTLD domain names is necessary to promote trust and
>>>     confidence in the Internet for all stakeholders.
>>>
>>>     Accordingly, it is desirable to design a system to support domain
>>>     name registration and maintenance which:
>>>
>>>     ·Provides appropriate access to accurate, reliable, and uniform
>>>     registration data
>>>
>>>     ·Protects the privacy of personal information
>>>
>>>     ·Enables a reliable mechanism for identifying, establishing and
>>>     maintaining the ability to contact Registrants
>>>
>>>     ·Supports a framework to address issues involving Registrants,
>>>     including but not limited to: consumer protection, investigation
>>>     of cybercrime, and intellectual property protection
>>>
>>>     ·Provides an infrastructure to address appropriate law enforcement
>>>     needs
>>>
>>>
>>>
>>>     _______________________________________________
>>>     gnso-rds-pdp-wg mailing list
>>>     gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
>>>     https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>>> <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.
>>
>>
>>
>> _______________________________________________
>> 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.