[Gnso-newgtld-wg] Provision of back-end registry services

Tue Aug 30 08:58:29 UTC 2016

I agree with Donna's comments. An accreditation system should be mainly 
focussed on making it easier and cheaper for applicants to get their 
applications approved and to avoid duplications of work at the scale we 
have seen in the current round. Any review of technical details that is 
shared between applications should only have to be reviewed once.

I hope this accreditation process is not viewed as an opportunity to add 
an additional barrier to competition in the application process but 
rather as a chance to simplify and streamline the process.

Best regards,

Volker Greimann

Am 29.08.2016 um 22:51 schrieb Austin, Donna:
>
> Hi All
>
> A working group of the RySG has been formed to consider a number of 
> topics being discussed as part of this PDP. On Friday I posted the 
> following email to the list, which resulted in quite a bit of 
> discussion. I’m working through the ensuing discussion and will 
> attempt to provide a summary for this group.
>
> Sara, I think RSP Accreditation will be discussed as part of WG 1 and 
> request that this input be taken into account.
>
> I repost my email to this list for information and also to encourage 
> more discussion on the topic.
>
> ___
>
> As RSP Accreditation was identified as a high priority, and as Neustar 
> is one of the leading RSP as a result of the new gTLD program, I’d 
> like to start a discussion on the path forward.
>
> I’ve just finished listening to the recording from the GDD summit on 
> the topic of certification of back-end registry providers.
>
> As some of you may recall, during that session Sean Kaine from Neustar 
> requested that we step back from the solution, ie. RSP Accreditation 
> and try to identify the problems we’re trying to solve in order to be 
> sure that we have the correct solution. Sean also acknowledged as part 
> of his intervention that accreditation may well be the answer, but 
> let’s be sure we understand what problems we’re trying to solve first.
>
> I acknowledge that many may consider this to be a dissenting point of 
> view, but I would ask this group if we could at least have the 
> discussion. I understand that many believe these discussions have been 
> had before, but I would argue that those were largely absent the 
> experience we have had since as a result of the implementation of the 
> new gTLD program and 1000+ registry operators going live.
>
> I think it would also be helpful to define what we mean when we say 
> ‘accreditation’. It is possible that it means different things to 
> different people and in this regard it would be helpful to have a 
> common understanding. It may be that we come up with a few different 
> versions of what ‘accreditation’ means and find that some of these are 
> more palatable than others.  I admit that I don’t have a fully 
> developed idea of what ‘accreditation’ actually means in this context, 
> but I do expect that there are a number of ways that ‘accreditation’ 
> could be achieved.
>
> Some of the concerns that Neustar has with accreditation are as follows:
>
> ·The potential to create unnecessary layers of bureaucracy in order to 
> achieve accreditation
>
> ·ICANN being responsible for the development and implementation of any 
> accreditation program—I think we’d all agree that ICANN does not have 
> a good track record in this regard.
>
> ·Ability to maintain product differentiation
>
> ·Creating another contracted party within ICANN—if a contract is 
> required and fees are to be paid to ICANN in order to be accredited 
> then RSPs could potentially create their own stakeholder group within 
> the GNSO, ie a third party in the CPH
>
> ·What are the implications, if any, on the Registry Agreement?
>
> To help us move forward in the manner I’m suggesting, I’ve identified 
> some of the problems I believe we’re trying to solve acknowledging 
> that this list is not exhaustive:
>
> ·The RSP needs the ability to interact directly with ICANN with regard 
> to technical issues.
>
> ·Streamline the 2012 new gTLD processes for any future round:
>
> oRemove the need for the same RSP to undergo the same PDT for every 
> registry operator
>
> oStreamline the application process as it relates to the technical 
> requirements
>
> oMake provision for applicants to select RSPs after securing the TLD
>
> oFind a more efficient way to swap out RSPs
>
> Following the discussion at the GDD Summit, ICANN staff committed to 
> synthesize the discussion, and come back to us with next steps. I 
> don’t believe this has happened, but based on some of the chat on our 
> call earlier this week it does seem that some work that is going on in 
> this regard. I think it would be helpful to our discussion to 
> understand what the status of what that work is and where it’s headed.
>
> Looking forward to everyone’s thoughts.
>
> Donna
>
> *Donna Austin**:****Neustar, Inc.**
> *Policy and Industry Affairs Manager
>
> *Cell:***+1.310.890.9655 *Email: *donna.austin at neustar.biz 
> <mailto:donna.austin at neustar.biz>
>
> ------------------------------------------------------------------------
>
> The information contained in this e-mail message is intended only for 
> the use of the recipient(s) named above and may contain confidential 
> and/or privileged information. If you are not the intended recipient 
> you have received this e-mail message in error and any review, 
> dissemination, distribution, or copying of this message is strictly 
> prohibited. If you have received this communication in error, please 
> notify me immediately and delete the original message.
>
> *Follow Neustar:*cid:image001.png at 01CC3CD3.5F595DC0Facebook 
> <http://www.facebook.com/neustarinc>cid:image002.png at 01CC3CD3.5F595DC0LinkedIn 
> <http://www.linkedin.com/company/5349>cid:image003.png at 01CC3CD3.5F595DC0Twitter 
> <http://www.twitter.com/neustar>
>
> P Please consider the environment before printing this e-mail.
>
>
>
> _______________________________________________
> Gnso-newgtld-wg mailing list
> Gnso-newgtld-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-newgtld-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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20160830/3ab75399/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1144 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20160830/3ab75399/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1089 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20160830/3ab75399/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 800 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20160830/3ab75399/attachment-0005.png>