PDA

View Full Version : PIR signs contracts for .org translits/translations


Drewbert
15th November 2013, 10:12 PM
http://www.icann.org/en/about/agreements/registries/xn--c1avg

http://www.icann.org/en/about/agreements/registries/xn--i1b6b1a6a2e

http://www.icann.org/en/about/agreements/registries/xn--nqv7f

http://www.icann.org/en/about/agreements/registries/xn--nqv7fs00ema

Anyone know their bundling arrangements?

TrafficDomainer
16th November 2013, 07:45 AM
Not sure about the final bundling arrangement but their position from below is very supportive of the translits of of current TLDs be given to current registrants.

http://intgovforum.org/Substantive_1st_IGF/PIR_Principles_IDN623_FINAL.pdf

Some key highlights that should help translits of .com and .net

It is therefore our belief that the following six basic principles must be
embedded in the foundation of all discussion on IDNs:
1. Retention of public trust—The public trust earned by existing domains
must not be betrayed, or trust in the Domain Name System (DNS) itself
may be eroded;
2. Protect DNS security and stability-An increasingly hostile environment
requires coordinated, not fractured, TLD management;
3. Ensure equity and parity for Registries and Registrars—Contributors to
public trust in the domain space must not be disenfranchised;
4. Minimize regulatory burdens—Fragmented regulation will add
needless complexity and retard DNS expansion rather than aid it;
5. Foster a balanced approach to Intellectual Property protection and
dispute resolution—The need for uniformity dictates fewer authorities;
6. Maintain consistency with proven Internet principles--.RFCs 2825 and
2826 urge single maintainers for symbols with common meaning.

In greater detail, the principles are as follows:

1. Retention of Public Trust

Stewards of the technical administration of the Internet are committed to act
in the best interests of the public (current and future domain name registrants
and Internet users).
All registry operators of top level domains are obligated to operate in
accordance with the technical requirements and guidelines set by ICANN and

the IETF. The generic Top Level Domains (gTLDs) and many country code
Top Level Domains (ccTLDs) have become globally recognized brands as a
result. Users have an expectation of ubiquitous yet coherent worldwide
resolution of the gTLDs and have grown accustomed to consistency in
registration and resolution processes. Regardless of the continent from which
a user accesses a TLD, users expect and deserve a similar, consistent and
coherent experience at the level in the DNS where actual resolution,
propagation and delegation of domains occur.

Users have arrived at a reasonable conclusion that the operator of a globally
resolving TLD registry can be trusted to deal with significant operational
issues as they arrive in the domain; it is reasonable for them to expect the
same comparable level and quality of service in all scripts that represent the
same domain label worldwide.

If the implementation of IDNs is managed in such a way as to result in brand
fragmentation, this will inevitably diminish the public trust of all gTLDs and
ccTLDs. We believe that this factor must be considered in order to avoid
exposing registrants to the dangers flowing from a devaluation of the trust that
has been built up in the DNS and the global single-root system.

Further, registrars and other distributors of gTLD and ccTLD registrations
have implemented automated and standards-compliant systems that result in
rapid and accurate domain name transactions. Should a gTLD or ccTLD be
managed by different operators for each IDN representation, registrars and
other distributors will have to build systems that connect to each of these
separate entities for what is essentially the same string (albeit in different
languages). This raises the prospect of confusion in terms of the identity of
individual registries. In addition, there is a strong possibility of difficulties in
dealing with problems that need to be addressed in a variety of
representations in an accountable manner

5. Foster a Balanced Approach to Intellectual Property Protection and
Dispute Resolution

The uniform application of guidelines providing a consistent process for
Intellectual Property protection and dispute resolution is necessary for all
users of the Internet.

Intellectual property challenges have always been present in the DNS and are
likely to become even more complex in IDN representations of domain
names. The Uniform Dispute Resolution Policy adopted by ICANN for the
resolution of domain name - trademark disputes should be extended and
modified as necessary to cover IDNs.

Uniformity is an essential element of this policy. The adoption of different
dispute resolution procedures for the same TLD in different IDN
representations would seriously compromise public trust in trademarks and
4brand names and inevitably lead to consumer confusion. All users of the
Internet are entitled to the benefits of a balanced and uniform approach to the
protection of intellectual property.

TrafficDomainer
16th November 2013, 07:49 AM
6. Maintain Consistency with Proven Internet Guiding Principles

The IAB (Internet Architecture Board) has provided significant relevant
guidance for the DNS in the following RFCs from May of 2000:

RFC 2825: A Tangled Web: Issues of I18N, Domain Names, and the
other Internet Protocols; and
RFC2826: IAB Technical Comment on the Unique DNS Root.

In RFC 2825, two statements provide useful guidance:

1) “…solutions must not cause users to become more isolated from their
global neighbors even if they appear to solve a local problem.”

2) “One aspect of the challenge is to decide how to represent the names
users want in the DNS in a way that is clear, technically feasible and
ensures that a name always means the same thing.” [emphasis added]

One of the significant challenges of implementing IDNs is to avoid
fragmenting the Internet and isolating users. PIR believes that a key means
of avoiding this problem is to allow all manifestations of a given top level
domain to be managed by a single entity. This simple solution will also
address the second issue: ensure that each TLD name always means the
same thing.

In RFC 2826, the IAB wisely observed that: “Effective communications
between two parties requires two essential preconditions:

-The existence of a common symbol set, and
-The existence of a common semantic interpretation of these symbols.
[emphasis added]

Failure to meet the first of these conditions implies a failure to communicate
at all, while failure to meet the second implies that the meaning of the
communication is lost.”

Further, the IAB says: “Names are then constant symbols, whose
interpretation does not specifically require knowledge of the context of any
individual party.”

Most, if not all, existing TLDs have achieved a “common semantic
interpretation.” Of all domains except .COM, .ORG probably has the most
5consistent interpretation, or meaning, on the Internet—a meaning well
understood and accepted by most Internet users.

Importantly, RFC 2826 goes on to say:

“Since the DNS is hierarchically structured into domains, the uniqueness
requirement for DNS names in their entirety implies that each of the names
(sub-domains) defined within a domain has a unique meaning (i.e., set of
DNS records) within that domain. This is as true for the root domain as for
any other DNS domain. The requirement for uniqueness within a domain
further implies that there be some mechanism to prevent name conflicts
within a domain. In DNS this is accomplished by assigning a single owner or
maintainer to every domain, including the root domain, who is responsible for
ensuring that each sub-domain of the domain has the proper records
associated with it. This is a technical requirement, not a policy choice.”
[emphasis added]

Insofar as .ORG in different scripts is considered the “same domain,” RFC
2826 appears to require that it be managed by a “single owner or maintainer.”
To the extent that .ORG in different scripts is considered a “different domain,”
ICANN should establish an equitable and transparent process for evaluating
both the value of a new domain as well as its prospective management.

Another well accepted principle, the “Principle of Least Astonishment” also
dictates that TLD’s be managed in the most consistent manner possible so as
to lead to the least confusion. Under the IAB principles outlined above, a
“common owner or maintainer” is the likely best solution for this issue as well.

In summary, PIR’s position on this issue is well supported by current thinking
on the technical issues as well as by wisdom applied years ago to similar
problems. It should be remembered that the initial set of IDN problems were
eventually solved through adherence to these simple, but powerful, principles.

Drewbert
16th November 2013, 10:00 AM
Fingers crossed!

Anyone know if Dynadot's signed the 2013 RAA yet? :)

DktoInc
17th November 2013, 07:37 AM
.

Drewbert
17th November 2013, 08:12 AM
Interesting that they've ended up with theirs signed before Verisign.

Rubber Duck
17th November 2013, 09:15 AM
Interesting that they've ended up with theirs signed before Verisign.

Not really as we know neither the game plan of either nor indeed whether they are collaborating.

As Launch Programs have been separated from contracting I would expect public signing in BA this week.

alpha
6th March 2014, 06:55 AM
so .орг has been delegated.

on the PIR site, all it says under their FAQ is:

How will .ORG IDNs be launched?
.ORG IDNs will be launched in two phases: Sunrise and General Availability.



hmmm. looks like current idn.org owners have been thrown under the bus

Drewbert
6th March 2014, 10:55 AM
Yikes.

Rubber Duck
6th March 2014, 12:09 PM
Yep! That should go down like a burning Spitfire!

Do ICANN have a clue about anything?

Drewbert
6th March 2014, 12:23 PM
The launch will be a complete shambles. Pretty much any .орг worth regging is in the block list!

idn
6th March 2014, 05:00 PM
Some days I really wonder why we all wasted so much time.

squirrel
6th March 2014, 06:06 PM
Any launch date ?

DktoInc
6th March 2014, 10:01 PM
The launch will be a complete shambles. Pretty much any .орг worth regging is in the block list!

i thought the block lists were cancelled.

http://www.icann.org/en/news/public-comment/name-collision-26feb14-en.htm