Early Global Services I-Name Policies
- This Version: http://www.xdi.org/docref/legal/egs-i-name-policies-v1-2004-10-20.html
- Latest Version: http://www.xdi.org/docref/legal/egs-i-name-policies.html
- Previous Versions: No Previous Versions
1. EGS Policy for =names
This section covers the proposed XDI.ORG policy and process for granting =names (global personal i-names) during the EGS program.
1.1. Introduction
The XDI.ORG/Identity Commons EGS (Early Global Services) program is centered primarily on the introduction and testing of personal i-names (i-names representing individuals) among an initial population of users. Personal i-names come in two forms:
- Global personal i-names (also called "=names" or "equals names") – i-names registered directly in the XDI.ORG "=" registry of globally unique XRIs (Extensible Resource Identifiers) representing human beings. Example: "=Mary.Smith".
- Community i-names (also called "*names" or "star names") - i-names not registered in the global "=" registry but rather registered or delegated to an individual (or another organization) in the context of another global i-name (typically the @name of an organization.) Example: "@PlaNetwork*Bob.Jones". Star names (*names) are unique only within the context of the community or organization in which they are registrated.
Since *names are delegated by other organizations, the local policies governing their assignment are managed by those respective organizations. This section specifies the XDI.ORG policies ONLY for assignment of global =names during the EGS program.
Note: the policies governing the assignment of =names in the future full Global Services begins will be specified in the Global Services Specifications (GSS) which will be published for public review by XDI.ORG. Feedback from the EGS program will be channeled into the GSS.
1.2. Requirements
- The global personal i-name registration policies should be clear and easy for all parties to understand.
- The policies should be easy, coherent, and expeditious enough to be administered primarily by machine.
- The policies should reflect the community-based, non-discriminatory governance requirements of XDI.ORG.
- Should disputes arise, the policies should include a dispute resolution mechanism similar to that for DNS names.
1.3. EGS =Name Assignment Policies
1.3.1. Term Policy
The term for all EGS =name registrations shall be 50 years.
1.3.2. First-Come, First-Served Policy
Registration requests that meet the policies specified herein will be accepted on a first-come, first-served basis on the time and date Identity Commons commences EGS =name registration, which shall be publicly announced.
1.3.3. Reserved Name Policy
Registrants may not register an =name that is in EGS global reserved i-names as specified by XDI.ORG.
1.3.4. Length Policy
A global personal i-name consists of a string of characters. Since the = namespace is intended for common names of individuals in any language or character set, and since there is no pre-defined set of authorities of this type for which names need to be reserved (similar to reserving one- and two-character DNS names for countries), =names of any length (other than null) may be registered.
1.3.5. Terms of Service Policy
Registrants must agree to the EGS Terms of Service for Global Personal I-Name Registrants, including the IPR policy and Dispute Resolution Policy.
1.3.6. IPR Policy
Registrants must be notified in the Terms of Service that if they register a trademark, the name of a public figure (that is not their own name), or other intellectual property as their i-name, it is possible that the owner of such intellectual property rights could seek to compel the registrant to give up that i-name. The registrant must agree to be solely responsible for any resulting costs, fees and damages if it can be shown that they registered that i-name in bad faith.
1.3.7. Dispute Resolution Policy
Registrants must agree to use of the dispute resolution process specified in the EGS Terms of Service for any intellectual property rights disputes that may occur in connection with registration of an =name.
1.3.8. Periodic Confirmation Policy
As a practical matter, to avoid withholding EGS =names from registration that are not in active use, registrants must to confirm their desire to keep their =name(s) at reasonable intervals during their 50-year registration term. Initially the intervals shall be five years. XDI.ORG reserves the right to change this interval if necessary. This requirement shall apply without discrimination to all EGS =name registrants, and all XDI.ORG-registered i-brokers shall be required to give these registrants ample notice and opportunity to confirm their respective registration(s).
1.3.9. Portability Policy
All EGS =name registrations shall be portable to any XDI.ORG-registered i-broker. The fee that may be charged for transfer of a registration must be commercially reasonable.
1.4. Feedback
Please provide any feedback on this proposed policy and process (this is especially important as this feedback will channelled into the XDI.ORG Global Services Specifications.) You can provide feedback by editing a copy of this policy on the XDI.ORG Wiki 
or by sending email to feedback@xdi.org.
2. EGS Policy for @names
This section covers the proposed XDI.ORG policy and process for granting @names (global organizational i-names) during the EGS program.
2.1. Introduction
Although the XDI.ORG/Identity Commons EGS (Early Global Services) program is centered primarily on the introduction and testing of personal i-names (i-names representing individuals), during the development of the EGS program it became apparent that to fully test XRI/XDI infrastructure, the EGS program needed to include the assignment of a limited number of global organizational i-names (@names.)
The primary reason is that the EGS program is designed to test two types of personal i-names:
- Global personal i-names (also called "=names") – i-names registered directly in the XDI.ORG "=" registry of globally unique XRIs representing individuals.
- Community i-names (also called "*names") - i-names delegated to an individual or another organization in the context of another authority, typically an organization.
Since most *names will be registered with organizations that themselves are identified with @names, the EGS program needs to allow these organizations to register the @name from which they can perform this delegation.
However, because @names involve issues of intellectual property rights ownership that need to be addressed in the publicly-reviewed XDI.ORG Global Services Specifications (GSS) prior to the commencement of general registration, in the EGS program the assignment of @names will follow the policies and processes specified below.
2.2. Requirements of the EGS @name Assignment Policy and Processes
- The policy should be clear and easy for all parties to understand.
- The policy should be easy and expeditious to administer.
- The policy should be conservative with regard to intellectual property rights issues and contain safeguards to avoid potential disputes prior to adoption of community-reviewed policies for @name registration.
- Should disputes arise, the policy should include a dispute resolution mechanism similar to that for =names.
2.3. Policies
2.3.1. EGS Participation Policy
To qualify for registration of an @name during the EGS program, an organization must warrant (in written or electronic form) that it will be an active participant in the EGS program by performing one or more of the following activities during the EGS program:
- Co-marketing =names to its employees, members, or other constituencies.
- Providing registration of *names under the organization's @name to its employees, members, or other constituencies.
- Implementing and deploying XRI/XDI infrastructure such as i-name single sign-on (ISSO).
The organization must further agree that if it has not undertaken one or more of these activities during the term of the EGS Program, its @name registration may be terminated 30 days after the conclusion of the EGS program. Note that in such a case the organization may still submit a registration request for the same @name under general registration when it commences.
2.3.2. EGS @Name IPR Policy
An organization that meets the requirements of the EGS Participation Policy above must further warrant that the @name it requests meets the following criteria:
- The @name is a legal tradename or trademark (whether registered or common law) of the organization.
- The @name is at least four characters in length (not including any dots) unless: a) the registrant is the current registry of the DNS top-level domain (TLD) corresponding to the requested @name, or b) the requested @name is the legal name of the registering organization and they are the current registrant of an equivalent DNS first-level domain.
- The @name is not an EGS reserved name as specified by XDI.ORG.
- The @name is not subject to any current dispute by another tradename or trademark holder.
- The registrant agrees to notify XDI.ORG of any special circumstances or intellectual property rights issues that exist at the time of registration or arise during the term of the EGS program regarding the requested @name.
- The @name registrant agrees to the EGS Terms of Service, including the use of the dispute resolution process specified therein for any intellectual property rights disputes that may occur in connection to the @name.
2.3.3. First-Come, First-Served Policy
@name registration requests that meet the two policies above will be accepted on a first-come, first-served basis once Identity Commons announces the commencement of EGS @name registration.
2.3.4. One @Name Per Organization Policy
During the period of the EGS Program, each registering organization shall be limited to registration of one @name.
2.3.5. Term and Fee
The term of an @name registration under the EGS program is 1 year and the fee shall be U.S. $100, payable to Identity Commons as the registrar.
2.4. Process
During the EGS program, @name registration will be a simple three-step process.
2.4.1. Step 1: Submit @Name Registration Request to Identity Commons
The first step in the process is for the requesting organization to submit a written, signed request (in either paper or electronic form, provided the signature is legally enforceable) that includes the following information:
- The @ name being requested.
- The legal name of the registering organization.
- Any current registered domain names for the registering organization (particularly those relevant to the registration, i.e., that include the requested @name).
- The legal mailing address of the registering organization.
- The registered business identifier of the registering organization in its jurisdiction of registration (i.e., U.S. state corporation number, UBI number, or other national ID number).
- The name, work title or role, work email address, work phone, work fax, and work mailing address of the primary contact requesting registration. If the primary contact is not an employee but is acting as an agent of the registering organization, this information must also include an description of the agent's relationship with the organization.
- The same information as above for a secondary contact who can be reached regarding the registration if the primary contact is unavailable.
- A warrant (e.g., checkbox or equivalent mechanism) that the organization will conform to the EGS Participation Policy (above).
- A written explanation of the specific activies the organization plans to undertake as required by the EGS Participation Policy.
- A warrant (e.g., checkbox or equivalent mechanism) that the registration conforms to the EGS @Name IPR Policy (above).
- If the requested @name is less than four characters in length, a written explanation of how it conforms to the requirements of item 2 of the EGS @Name IPR Policy (above).
- A written list of any tradename or trademark registrations or applications for the requested @name, pending or granted, and the applicable jurisdictions.
- A written explanation of any special circumstances or issues regarding the requested @name as required by the EGS @Name IPR Policy.
- A warrant (e.g., checkbox or equivalent mechanism) that the registering organization agrees to the EGS Terms of Service as specified by XDI.ORG.
This data can be collected by a web form (currently at http://2idi.idcommons.net/org/index.html)
2.4.2. Step 2: Receive Approval from Identity Commons
The second step is for Identity Commons to confirm that the application is true and complete. If so, Identity Commons is empowered to grant the registration request and begin providing local resolution service for the @name.
If there are any questions about this step that cannot be resolved to Identity Commons satisfaction, Identity Commons may refer the request to the Managing Director of XDI.ORG or his/her designee for resolution.
If the Managing Director of XDI.ORG or his/her designee cannot resolve these questions to his/her satisfaction, the Managing Director may request resolution directly by the XDI.ORG Board of Trustees.
2.4.3. Step 3: Notification of XDI.ORG, Cordance, and NeuStar
Once an @name registration has been granted by the two steps above, the final step is for Identity Commons to send a copy of the request to the Managing Director of XDI.ORG, the EGS Program Manager for Cordance, and the EGS Program Manager for NeuStar. Cordance and NeuStar shall manually enter the registration in the EGS registry if such process is not automated in the EGS registry interface.
2.5. Feedback
Please provide any feedback on this proposed policy and process. You can provide feedback by editing a copy of this policy on the XDI.ORG Wiki or by sending email to feedback@xdi.org.