Re: [gnso-vi-feb10] .CH: Another example of Vertical Integration
Eric, I agree that further definitions would be needed.My understanding of a gTLD that would "closely resemble ccTLDs in setup and purpose" would mainly be a (large) subgroup of community TLDs, the geoTLDs which would include TLDs for subnational (dotState, dotCity) and supernational (dotCulturalDesignation) communities. The former would be defined as those TLDs requiring approval or non-objection letters from local governments (as currently already provided for in the DAG), while the latter would be a bit harder to define, but would still fit in the same group. Just for clarification, I am thinking about cultural designations that transcend national borders, such as .kurd, .roma, .innuit, and maybe also .unicef, .redcross and the like). Finding a good definition and contractual provisions for those is not a neglible task, but one I feel ICANN staff is well equipped for.
In any case, the provider would have to qualify as a community TLD, and maybe fulfill further yet TBD requirements as well.
Just to be clear, I am not suddenly advocating limiting VI possibilities to such TLDs. I just see them as prime examples where many of the potential harms are already mitigated by the expected size, the requirements of a community TLD (as defined in the application process) and thus allowing VI should be an even easier call to make.
... it does suggest that VI is a workable principle for community TLDs that closely resemble ccTLDs in setup and purpose.So here is an issue we can mull over, lack of an appropriate application type and the lack of an appropriate contract.When an applicant represents that the registry will "closely resemble ccTLDs in setup and purpose", that representation could be recognized rather than ignored by the evaluation process, and recognized rather than ignored in the contracting process.At that point it would be useful to consider the policy that applies to registries and registrars.Obviously, "closely resemble ccTLDs in setup and purpose" assumes some definitions, and probably excludes repurposed ccTLDs, no matter how vigorous the assertion is made that the Principle of Subsidiarity allows ccTLD operators to ignore the responsibility and duty language of RFC 1591.Also obviously, a type of application that has policy consequences applies just as well to the notions of SRSUs floating about.Eric
-- 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@xxxxxxxxxxxxxxx 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.key-systems.net/facebook www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 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@xxxxxxxxxxxxxxx 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.key-systems.net/facebook www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 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.