Skip to main content
Resources

.CAT Registry Agreement Appendix S

(17 July 2012)

Appendix S — Part I

.CAT Charter

I

The .cat TLD will be established to serve the needs of the Catalan Linguistic and Cultural Community on the Internet (the "Community")

The Community consists of those who use the Catalan language for their online communications, and/or promote the different aspects of Catalan culture online, and/or want to specifically address their online communications to that Community.

II

The .cat TLD will be managed by Fundació puntCAT in accordance with (i) the provisions of this Charter (the "Charter"); (ii) the interests of the Community; (iii) Consensus Policies and Temporary Specifications or Policies (as defined in Section 3.1 (a) of the Agreement), as they may be applicable to Sponsored TLDs, and (iv) the interests of the global Internet community, with special consideration for interoperability, technical stability, and security aspects.

Fundació puntCAT shall be responsible for establishing registration requirements for second-level domains in the .cat TLD, consistent with this Charter.

III

For the purposes of this Charter, without being exhaustive, and as may be amended or clarified from time to time as contemplated by item IV, below, the Registry's policies may permit registrations in .cat TLD to the following:

  • Universities, schools, research institutions and other academic entities that use Catalan in their academic activities or teach/promote aspects of Catalan culture

  • public or private entities whose aim is promoting the Catalan culture

  • writers, translators, correctors and journalists publishing (or contributing to) works in Catalan

  • publishing companies that publish works in the Catalan language or relating to the Catalan culture

  • media using the Catalan language for their communications

  • individuals, groups, businesses, organizations, entities or initiatives, however constituted, carrying online communications in Catalan

  • individuals, groups, businesses, organizations, entities or initiatives, however constituted, proving their belonging to the Community by way of sponsorship from other members of the Community in the form established in the Registration Policies

  • members of Fundació puntCAT

IV

The Registry may amend, clarify, extend or re-enumerate the industry sectors identified in clause III, above, provided that such changes are within the scope of the definition set out in clause I, above. The Registry will promptly inform ICANN of such changes.

Appendix S - Part II

Delegated Authority

The following areas of responsibility for development of policies for the Sponsored TLD are delegated to the Registry, provided the other provisions of the Agreement and its Appendices are followed:

  1. Establishment of naming conventions to be used in the Sponsored TLD.

  2. Restrictions on what types of people or entities may register Domain Names (which need not be uniform for all names within the Sponsored TLD), provided the scope of the Charter is not exceeded.

  3. Restrictions on how Registered Names may be used (which need not be uniform for all names within the Sponsored TLD), provided the scope of the Charter is not exceeded.

  4. Performance of Eligibility and Name-Selection Services (ENS Services), either directly by the Registry or by one or more organizations or individuals to which it delegates the responsibility for performing ENS Services.

  5. Mechanisms for enforcement of the restrictions in items 2 and 3, including procedures for revocation or cancellation of registrations.

  6. Mechanisms for resolution of disputes concerning eligibility and of disputes between owners of rights (who may or may not be registrants) in names and registrants, that do not supplant ICANN's dispute-resolution policies or remedies that may be available under law, such as Charter Compliance Policy, Charter Reconsideration Policy and Mediation Procedure.

  7. Accreditation, in conjunction with ICANN, of additional dispute resolution providers for the administration of .cat-specific dispute resolution policies.

  8. Selection of back-end registry provider and establishment of the terms of agreement between the Registry and the provider.

  9. Selection of other service providers.

  10. Functional and performance specifications for Registry Services.

  11. Pricing of Registry Services.

  12. Modifications of Registry Services that do not represent material changes to approved Registry Services.

  13. Matters concerning the operation of the registry for the Sponsored TLD.

  14. Selection of ICANN-Accredited Registrars to act as registrars for the Sponsored TLD, consistent with Part V of this Appendix S.

  15. Terms of agreement to be offered by the Registry to ICANN-Accredited Registrars selected by Registry, including provisions for fair treatment by the Registry and the Registry Operator of those registrars.

  16. Practices of ICANN-Accredited Registrars selected by Registry with respect to (a) Registered Names and their registration and (b) other Registry Services and (c) Registry technical platform, including limiting their access to the registration system due to abuses on those areas.

  17. Terms of agreement between registrars and registrants under which Registered Names are registered.

  18. Uses and practices by registrants with respect to Registered Names, including a Code of Conduct.

  19. Procedures and schedule for the start-up of the Sponsored TLD, provided they are consistent with Part IV of this Appendix S.

  20. Provisions for publication of registry and registrar data consistent with the TLD Sponsorship Agreement and Registrar Accreditation Agreements.

  21. Terms of agreement between or among Registry, registrars, and registrants necessary to give effect to the above.

  22. Management and modification of .cat Policy Development Procedures

  23. Establishment and update of a list of Community-assigned Domain Names

  24. Reservation of names to be withheld from reservation in the sTLD (in addition to those names reserved by ICANN and set forth in Appendix 6).

  25. Other areas of responsibility as agreed to in writing by both ICANN and Registry

  26. Any other policies or practices not inconsistent with the Agreement, ICANN Temporary Specifications and Policies, or Consensus Policy.

Appendix S — Part III

Description of Sponsored TLD Community

The .cat TLD is intended to serve the needs of the Catalan Linguistic and Cultural Community on the Internet (the "Community").

"Catalan Linguistic and Cultural Community" refers to those individuals, groups, businesses, organizations, entities or initiatives, however constituted, eligible to register in the .cat TLD according to this Agreement and the .cat Charter (Part I to this Appendix S). The Community includes those who (1) use the Catalan language for their online communications, (2) and/or promote the different aspects of Catalan culture online, (3) and/or want to specifically address their online communications to that Community.

The Registry may extend or amend the description of the Community consistent with the terms of the Agreement and the .cat Charter.

Appendix S — Part IV

Start-Up Plan

Registry will implement the following Start-up Plan for the .cat Sponsored TLD:

BACKGROUND

The Start-up Plan provides for the orderly introduction of the .cat sTLD for the purpose of ensuring competition, fairness and reliability for ICANN-Accredited Registrars, registrants, and the .cat Community (as defined in Part III of this Appendix S). It is intended to create a stable and effective registration process for the benefit of the Internet community in general, and effected stakeholders in particular, while minimizing the number of conflicts within the Community or with third parties.

TIMELINE

Registry plans to introduce and begin to support products and services on the following approximate and estimated timeline. All referenced dates are based on the Effective Date of the Registry Agreement (ED).

POLICY & STRUCTURE

DATE

EVENT

2003-In Process

  • Policy Development

  • Community Awareness

ED + 30

  • Publication of Draft Registration Agreement

  • Publication of Draft Dispute Resolution Mechanisms

(15 days comment period)

ED + 30

  • Registry selects Dispute Resolution Provider for .cat specific DR policies

ED + 30

  • Registry signs contract with technical operator

ED + 30

  • Registrar Accreditation begins

ED + 60

  • Publication of Final version of Registration Agreement & Dispute Resolution Policies

REGISTRATION OPERATIONS

ED + 30

  • OT&E testing

ED + 75

  • Defensive registrations (60 days)

ED + 75

  • Start of Sunrise Period. Phase I (90 days)

ED + 135

  • Start of Sunrise Period. Phase II (60 days)

ED + 195

  • Start of Sunrise Period. Phase III (15 days)

ED + 210

  • Full Operations Mode


AGREEMENT AND POLICY DEVELOPMENT

Registry has commenced development of the various agreements and policies needed in connection with the operation of the .cat sTLD. All those documents and policies will be published for a two-week comment period.

OT&E TESTING

Registry will conduct comprehensive testing of the registry system and registration procedures (including the interfaces with Registrars).

DEFENSIVE REGISTRATIONS

Registry will allow intellectual property owners not otherwise eligible to register a .cat Domain Name to register trademarks to which they have title as Defensive Registrations in the .cat sTLD through ICANN Accredited Registrars. Registrants must validate their interests in requested domains through a trademark validation process to avoid abusive or ineligible registrations. The Defensive Registration Period is currently scheduled for a period of 60 days.

SUNRISE PERIOD

The goal of the Sunrise period is double: on one hand, to ensure stable registry operations and prepare for full operations, adjusting policies and process if required; on the other hand, to allow prospective registrants with special title to have priority in their registrations, as a means to control possible disputes.

The .cat Sunrise Period will consist of three phases:

Phase I

In this phase only entities having a relevant and direct relationship with the promotion of the Catalan language or culture will be entitled to register domain names. The Registry will publish for public comment the criteria and the lists or registers used for validating such qualification. This Phase I will last for 90 days.

Phase II

All legal entities proving prior online communications in Catalan will be admitted in Phase II, which will last for 60 days.

Phase III

All those individuals and entities (over 68.000 in total) who provided support to the .cat application will receive a special ENS ID & code allowing them to participate in this Phase III during 15 days after the end of Phase II.

Overlap of Phases, and Priority within Phases

While the three successive Phases represent a logical order, they may overlap chronologically. No application for Phase II applicants will be evaluated until the end of the review of all Phase I applications. No application for Phase III will be evaluated until the end of the review for the previous two Phases.

Within each phase, and provided eligibility has been validated, names will be assigned in a first come, first served basis.

Phase II is currently scheduled to start 60 days after Phase I, running for 30 days in parallel with Phase I. Nevertheless, Registry may decide to allow applications for all three Phases in parallel, maintaining the priority among Phases for validations and domain name delegations.

FULL OPERATIONS

The goal of the full operations period is to provide continuous and stable registry operation to the Community.

Registry may from time to time update registration operations and procedures and include new products and services consistent with the .cat Sponsored TLD Registry Agreement.

MODIFICATION OF TIMELINE

Registry will publish within 30 days of the Effective Date a new Timeline.

Appendix S — Part V

Selection of Registrars

Registry will select among ICANN-accredited registrars wishing to register domain names in .cat Sponsored TLD in a manner that promotes the following characteristics:

1. Thorough and demonstrated understanding of the principles and intentions underlying .cat TLD policies and procedures;

2. Recognition of the specific nature of the .cat Sponsored TLD and demonstrated willingness to participate in providing registrar services to registrants in full support of the policy requirements established for Eligibility and Name Selection [ENS];

3. Dedicated willingness and ability to propagate and enforce sTLD policies in an observant and diligent manner and in accordance with policies and procedures prescribed by Registry;

4. Demonstration that sufficient staff resources are available and that the Registrar has the technical ability to interface with automated and manual elements of the .cat TLD registry;

5. Demonstrated systems designed to avoid submission of unqualified or incomplete applications that will burden the ENS system or make it impossible for Registry to fulfill its commitments to ICANN;

6. Demonstrated systems designed to avoid any disputes regarding transfers among Registrars and acceptance of any .cat policies and procedures established in that regard;

7. Acceptance of Registry policies and designated procedures for grace periods for registrants;

8. Willingness and ability to post and refresh a minimum deposit against which fees will be drawn;

9. Demonstrated willingness and ability to publicize and market the .cat TLD, and to follow all .cat TLD marketing guidelines and to use its materials as appropriate;

Registry has not established a minimum or maximum number of Registrars that will be selected for the .cat TLD. Registry will evaluate and, in its reasonable discretion, determine whether to qualify an applicant Registrar to serve as a Registrar for the TLD.

Registry will accept applications from any ICANN-accredited Registrar and will enter into agreements with Registrars only after a decision with respect to the selection of each applicant to serve as a Registrar based on all of the above criteria and will periodically review and, as appropriate, revise its selection of Registrars based on such criteria.

Appendix S — Part VI

Public Whois Specification

Subject to Registry's compliance with this .cat TLD Registry Agreement, including all attachments and appendices thereto (the "Agreement") and any Temporary Specifications or Policies or Consensus Policies as defined in the Agreement, and provided the scope of the Charter is not exceeded:

Registry will implement the following Public Whois Specification:

SPECIFICATION

Subject to any future policy regarding Whois data adopted by ICANN, domain name registrants will be required to provide correct contact information and, as permitted by applicable law, consent to selected information being made public for legitimate purposes.

Until a generally accepted specification replacing RFC 3912 is available, the Registry will provide RFC 3912-compliant Whois service. The specification contained in this Part VI to Appendix S is subject to change by agreement of the Registry and ICANN during the design process as well as during the IETF standards process. However, the following provides the target architecture and initial functionality. In addition, Registry agrees to implement changes to this specification specified by ICANN to conform to IETF provreg working group's protocol specification no later than 135 days after the IETF specification is adopted as a Proposed Standard [RFC 2026, section 4.1.1].

DATA PROVIDED IN RESPONSE TO WHOIS QUERIES

With respect to the amount and type of domain name registrant data provided in response to queries of the WHOIS service by the general public, the WHOIS service will distinguish between domain name registrants that are companies, businesses, partnerships, non-profit entities, associations, or other types of legal constructs ("Legal Persons"), and domain name registrants that are human beings, perceptible through the senses and subject to physical laws ("Individuals"). Domain name registrants will be required to specify whether they qualify as Legal Persons or Individuals by clicking the appropriate box during the registration process.

1. WHOIS Data for Legal Persons

Full WHOIS data for domain name registrants that are Legal Persons will always be available to the general public. Queries of the WHOIS service related to Legal Persons will always return full and complete standard WHOIS data, including applicable personal data such as Registrant ID, Registrant Name, Organization, Address (street, city, state, postal code, and country), Phone Number, Facsimile Number, and Email Address. Legal Persons will not be permitted to opt out of disclosing such information in response to queries submitted to the WHOIS service. The Registry Operator reserves the right, however, to take any preventive action necessary to prohibit any requestor of WHOIS data from using the WHOIS service to collect WHOIS data on Legal Persons for marketing purposes, spamming, data-mining, or unlawful purposes.

For the fields returned in response to queries of the WHOIS service for Legal Persons, and an example of a returned record, please see the "WHOIS Output Format Specification" below.

2. WHOIS Data for Individuals

Full WHOIS data for domain name registrants that are individuals may or may not be available to the general public depending on whether the applicable domain name registrant elects to make his or her personal information available in response to queries of the WHOIS service. Unlike Legal Persons, domain name registrants that are individuals will be given the option to elect whether or not their personal information is disclosed by the WHOIS service in response to queries from the general public. The default option will be for all personal information to be disclosed by the WHOIS service. In order to override this default option, the domain name registrant that is an individual will have to specifically elect not to have such personal information disclosed by clicking the appropriate box during the registration process.

3. Individuals Who Opt-In (Default Option)

For any domain name registrant that is an Individual and that does not elect to have his or her personal information withheld from disclosure by the WHOIS service, queries by the general public of the WHOIS service related to such individual will return full and complete standard WHOIS data, including personal data such as Registrant ID, Registrant Name, Organization, Address (street, city, state, postal code, and country), Phone Number, Facsimile Number, and Email Address. The Registry Operator reserves the right to take any preventive action necessary to prohibit any requestor of WHOIS data from using the WHOIS service to collect WHOIS data on Individuals for marketing purposes, spamming, data-mining, or unlawful purposes. For the fields returned in response to queries of the WHOIS service for Individuals that opt-in to disclosure (or that do not elect to change the default setting), and an example of a returned record, please see the "WHOIS Output Format Specification" section below.

4. Individuals Who Opt-Out

If a domain name registrant that is an Individual elects to withhold his or her personal information from disclosure by the WHOIS service, queries by the general public of the WHOIS service related to such individual will return only limited WHOIS data, including Domain Name, Domain ID, Sponsoring Registrar, Sponsoring Registrar IANA ID, Domain Status, Registrant ID, Name Server, created by registrar, last updated by registrar, domain registration date, domain expiration date, and domain last updated date. No personal information related to the domain name registrant will be available through the WHOIS service for individuals who have opted-out of disclosing their personal information.

Instead of such personal information, requestors of WHOIS data on Individuals will be informed that the registrant has elected to withhold certain personal information from disclosure by the WHOIS service, and will be provided with a link to the Registry Operator's Contact webform. Through this mechanism, requestors will be able to fulfill a webform. The content of this webform, including name of the requestor, and reason for the contact will be sent by the Registry Operator to the registrant's and administrative provided contact e-mail addresses.

For the fields returned in response to queries of the WHOIS service for Individuals that opt-out of full disclosure, and an example of a returned record, please see the "WHOIS Output Format Specification - Individuals (opt out)" section below.

5. Contact Webform

As described above, the WHOIS service will provide a link to the Contact webform in response to queries for WHOIS data on Individuals that have opted not to disclose personal information. The Registry will not store anything the requestors may introduce in such webform, retaining only the logs and the reports of success or failure of deliverance

The webform will allow the requestor to provide an e-mail address to be contacted, the reasons for contacting the registrant, and a free text field.

The Registry Operator will process the content provided by the requestor, and will deliver it to the registrant's and administrative contact e-mail addresses. The requestor must necessarily accept that the Registry provides this service as is, that the Registry will not be liable for, and that the use of the Registry Operator's contact webform does not guarantee ant answer from the registrant. Nor the Registry will be liable for any liability that may originate from the request's content. The requestor must as well accept that the registrant may or may not answer the requestor's request.

The Registry will offer access to the full data of individuals that have chose non disclosure to law enforcement agencies.

ADDITIONAL FIELDS CAPABILITY

If necessary, the Registry may introduce additional fields to the list of Whois fields described in this document. Those fields will be preceded and identified by appropriate tags.

INTERNATIONALIZED DATA

The Registry uses so-called "localized" address fields for contacts (see also RFC 3733). These fields may contain non-US-ASCII characters according to the IDN Table for Catalan Language (ca) that Registry will register with IANA upon signature of this Agreement. In order to support transmission of such characters, the system will provide an option specifying an alternative character set which should be used instead of the default US-ASCII character set.

INPUT FORMAT SPECIFICATION

The input to the Whois server consists of two parts: the options and the query itself.

The following options are available:

  • the -C option allows to specify the character set for both input and output

If the -C option is specified, the Whois server expects a character set name as the next token. The name must correspond to one of the IANA character set names. Only a limited set of character sets is supported by the server. It can be determined with the HELP query described below. At least US-ASCII and UTF-8 are supported. If the specified character set is supported, the server tries to reinterpret the octet sequence that has been sent as input via this character set. If it succeeds, it continues processing, otherwise, an error response is generated. The use of this option does not guarantee in general that all characters that are intended to be sent to the client can properly be represented. If during the conversion of the output to the specified character set a character is found that cannot be represented, it is replaced with a question mark. In addition, a comment is added to the output that notifies the recipient of the response about this problem.

By default, the Whois service searches for domain names. By the following keywords, the search type can be determined:

Keywords (case insensitive)

Type

do, domain

Search for domain objects. Either the "Domain Name", "Domain Name ACE" or "Domain ID" field is used

ho, host

Search for name server objects. Either the "Host Name", "Host Name ACE" or the "Host ID" field is used

Contact

Search for contact objects in the "Contact ID" field

ap, application

Search for an application object. Either the "Domain Name", "Domain Name ACE" or "Application ID" field is used. Only valid during the sunrise period.

Registrar

Search for registrar objects in the "Registrar ID" or "Registrar Organization" field


In addition, the following search options are available:

Keywords (case insensitive)

Option

Id

Search is performed in the respective ID field

Ace

Search is performed in the respective ACE field


In general, domain names in the input are considered as being Internationalized Domain Names (IDNs, as defined in section 2, "Terminology", RFC 3490). By using the ace option, a given domain name is considered as being an ACE domain name. The use of the option does not have an influence on the response.

The output can be controlled by the following keywords:

Keywords (case insensitive)

Option

=, full

Always return the complete data, even if multiple entries are found

sum, summary

Always return summarized data, even if only a single entry is found


The last token in the input is taken as the search parameter.

If the search parameter is "help" and no object type is given, no search is performed, but a short summary about the input format is returned.

OUTPUT FORMAT SPECIFICATION

The results of the query are encoded using either the US-ASCII character set or, if a valid character set has been specified via the -C option, the selected character set. If the output contains characters for which no encoding does exist, it is handled in different ways depending on the location. For domain names, they are replaced with a question mark and a respective warning comment is added to the beginning of the output:

[Note: the following two warnings are provided as an example]

% WARNING: THIS RESPONSE IS NOT AUTHENTIC
%
% The selected character encoding "XXX" is not able to
% represent all characters in this output. Those
% characters that could not be represented have been
% replaced with "?". Please resubmit your query with a
% suitable character encoding in order to receive an
% authentic response.
%

Within contact fields, accented letters are replaced by their non-accented equivalent letters (which are part of the ASCII character set) and a respective warning comment is added to the beginning of the output:

% WARNING: THIS RESPONSE IS NOT AUTHENTIC
%
% The selected character encoding "XXX" is not able to
% represent all characters in this output. Those
% characters that could not be represented have been
% replaced with the unaccented ASCII equivalent. Please
% resubmit your query with a suitable character encoding
% in order to receive an authentic response.
%

If both cases appear, a suitable combined warning is generated. The different handling of characters that cannot be represented lies in the different importance of the correct spelling. While it is a common practice to remove accents from names and addresses in order to further process them in ASCII-only contexts, such a methodology is considered harmful regarding domain names. In this case it is better to produce an invalid domain name with question marks in it instead of a name that might be considered as the actual spelling.

All lines are terminated by CR/LF pairs. Lines that contain comments, legal notes or similar, start with a percent sign ('%'). If the output consists of multiple objects, they are separated by at least one empty line. The objects themselves (including the related subobjects, like referenced contacts of a domain) do not contain empty lines. If no objects match the search query, "NOT FOUND" is returned. The object data is composed of multiple key-value lines. Key and value of a key-value pair are separated by a colon (':'). The key may contain space characters. For domain names that appear in the output, both the IDN version and the ACE version are supplied, even if the IDN consists of LDH characters only and is identical to the ACE representation. This applies to names of domains and hosts as well as name server references in domains. It does not apply to e-mail addresses (which contain domain names as part of the address) in the contact data.

Example:

...
Domain Name: fundació.cat
Domain Name ACE: xn--fundaci-r0a.cat
...
Name Server: blau.exemple.cat 192.0.2.1
Name Server: marró.exemple.cat 192.0.2.2
Name Server ACE: blau.exemple.cat 192.0.2.1
Name Server ACE: xn--marr-tqa.exemple.cat 192.0.2.2
...

Domain Data Format

Depending on the query and options, either a short or a long format is produced.

Short format:

Domain ID: D38482
Domain Name: exemple.cat
Domain Name ACE: exemple.cat

Full Format:

Domain ID: D38482
Domain Name: exemple.cat
Variant Name: éxemple.cat
Variant Name: exemplè.cat
Domain Name ACE: exemple.cat
Variant Name ACE: xn--xemple-9ua.cat
Variant Name ACE: xn--exempl-8ua.cat
Domain Language: ca
Registrar ID: IANA-15
Created On: 2001-07-23 17:53:02 GMT
Last Updated On: 2002-11-01 09:21:47 GMT
Expiration Date: 2005-07-23 17:53:02 GMT
Status: ok
Registrant ID: C343238
Registrant Name: CORE Internet Council Of Registrars
Registrant Organization: CORE Internet Council Of Registrars
Registrant Street: WTC II, 29 route de Pre-Bois
Registrant City: Geneva
Registrant State/Province: Geneva
Registrant Postal Code: 1215
Registrant Country: CH
Registrant Phone: +41.229295744
Registrant Phone Ext:
Registrant Fax: +41.229295745
Registrant Fax Ext:
Registrant Email: secretariat@corenic.org
Admin ID: C343238
Admin Name: CORE Internet Council Of Registrars
Admin Organization: CORE Internet Council Of Registrars
Admin Street: WTC II, 29 route de Pre-Bois
Admin City: Geneva
Admin State/Province: Geneva
Admin Postal Code: 1215
Admin Country: CH
Admin Phone: +41.229295744
Admin Phone Ext:
Admin Fax: +41.229295745
Admin Fax Ext:
Admin Email: secretariat@corenic.org
Tech ID: C343238
Tech Name: CORE Internet Council Of Registrars
Tech Organization: CORE Internet Council Of Registrars
Tech Street: WTC II, 29 route de Pre-Bois
Tech City: Geneva
Tech State/Province: Geneva
Tech Postal Code: 1215
Tech Country: CH
Tech Phone: +41.229295744
Tech Phone Ext:
Tech Fax: +41.229295745
Tech Fax Ext:
Tech Email: secretariat@corenic.org
Billing ID: C343238
Billing Name: CORE Internet Council Of Registrars
Billing Organization: CORE Internet Council Of Registrars
Billing Street: WTC II, 29 route de Pre-Bois
Billing City: Geneva
Billing State/Province: Geneva
Billing Postal Code: 1215
Billing Country: CH
Billing Phone: +41.229295744
Billing Phone Ext:
Billing Fax: +41.229295745
Billing Fax Ext:
Billing Email: secretariat@corenic.org
Name Server: ns1.exemple.cat 192.0.2.1
Name Server: ns2.exemple.cat 192.0.2.2
Name Server ACE: ns1.exemple.cat 192.0.2.1
Name Server ACE: ns2.exemple.cat 192.0.2.2

Regarding the included contact data, see below also.

Host Data Format

Short Format:

Host ID: H38473
Host Name: ns3.exemple.cat
Host Name ACE: ns3.exemple.cat

Full format:

Host ID: H38473
Host Name: ns3.exemple.cat
Host Name ACE: ns3.exemple.cat
Registrar ID: IANA-15
Created On: 2001-07-23 17:53:02 GMT
Last Updated On: 2002-11-01 09:21:47 GMT
Status: ok
IP Address: 192.0.2.3
IP Address: 3FFE:3273:1002::FE99:3BC7

Contact Data Format

Short format:

Contact ID: C394583
Name: Núria Ferrer i Puig

Full format:

Contact ID: C394583
Status: ok
Name: Núria Ferrer i Puig
Organization:
Street: Plaça de l'Església, 1
City: Castelló d'Empúries
State/Province: Catalunya
Postal Code: 17486
Country: ES
Phone: +34.123456789
Phone Ext:
Fax: +34.987654321
Fax Ext:
Email: nuria.ferrer@exemple.cat

The actual published data depends on the registry policy and the contact's disclosure settings (see RFC 3733). If data is not disclosed, the respective key-value pair is omitted. In contrast, empty fields (like the organization in the given example), are included. This allows the client to differentiate between the two cases.

Application Format

During the Sunrise period, the Whois is enabled to return information about pending applications. Since multiple applications may be possible for a single domain name, a query using a domain name may return more than one record. Similar to the wild card search, the short report format is used by default if more than one record is found.

Short Format:

Application ID: A38482
Domain Name: exemple.cat
Domain Name ACE: exemple.cat
Name: Núria Ferrer i Puig
Organization:

Full format:

Application ID: A38482
Domain Name: exemple.cat
Variant Name: éxemple.cat
Variant Name: exemplè.cat
Domain Name ACE: exemple.cat
Variant Name ACE: xn--xemple-9ua.cat
Variant Name ACE: xn--exampl-8ua.cat
Domain Language: ca
Registrar ID: IANA-15
Created On: 2001-07-23 17:53:02 GMT
Last Updated On: 2002-11-01 09:21:47 GMT
Expiration Date: 2005-07-23 17:53:02 GMT
Status: pending
Registrant ID: C343238
Registrant Name: CORE Internet Council Of Registrars
Registrant Organization: CORE Internet Council Of Registrars
Registrant Street: WTC II, 29 route de Pre-Bois
Registrant City: Geneva
Registrant State/Province: Geneva
Registrant Postal Code: 1215
Registrant Country: CH
Registrant Phone: +41.229295744
Registrant Phone Ext:
Registrant Fax: +41.229295745
Registrant Fax Ext:
Registrant Email: secretariat@corenic.org
Admin ID: C343238
Admin Name: CORE Internet Council Of Registrars
Admin Organization: CORE Internet Council Of Registrars
Admin Street: WTC II, 29 route de Pre-Bois
Admin City: Geneva
Admin State/Province: Geneva
Admin Postal Code: 1215
Admin Country: CH
Admin Phone: +41.229295744
Admin Phone Ext:
Admin Fax: +41.229295745
Admin Fax Ext:
Admin Email: secretariat@corenic.org
Tech ID: C343238
Tech Name: CORE Internet Council Of Registrars
Tech Organization: CORE Internet Council Of Registrars
Tech Street: WTC II, 29 route de Pre-Bois
Tech City: Geneva
Tech State/Province: Geneva
Tech Postal Code: 1215
Tech Country: CH
Tech Phone: +41.229295744
Tech Phone Ext:
Tech Fax: +41.229295745
Tech Fax Ext:
Tech Email: secretariat@corenic.org
Billing ID: C343238
Billing Name: CORE Internet Council Of Registrars
Billing Organization: CORE Internet Council Of Registrars
Billing Street: WTC II, 29 route de Pre-Bois
Billing City: Geneva
Billing State/Province: Geneva
Billing Postal Code: 1215
Billing Country: CH
Billing Phone: +41.229295744
Billing Phone Ext:
Billing Fax: +41.229295745
Billing Fax Ext:
Billing Email: secretariat@corenic.org
Name Server: ns1.exemple.cat 192.0.2.1
Name Server: ns2.exemple.cat 192.0.2.2
Name Server ACE: ns1.exemple.cat 192.0.2.1
Name Server ACE: ns2.exemple.cat 192.0.2.2

Registrar Data Format

Registrar ID: IANA-15
Status: ok
Organization: CORE Internet Council Of Registrars
Street: WTC II, 29 route de Pre-Bois
City: Geneva
State/Province: Geneva
Postal Code: 1215
Country: CH
Phone: +41.229295744
Phone Ext:
Fax: +41.229295745
Fax Ext:
Email: secretariat@corenic.org
Whois Server: whois.core.info
URL: http://www.corenic.net

For ICANN-accredited registrars, the registrar ID is composed of the prefix "IANA-" and the registrar ID as specified in the registrar list maintained by IANA (http://www.iana.org/assignments/registrar-ids). Other administrative accounts operated by the registry use a different prefix.

WHOIS Output Format Specification—Individuals (Opt-Out)

% puntCAT Whois Server Copyright (C) 2007 Fundacio puntCAT
%
% NOTICE: Access to puntCAT Whois information is provided to assist in
% determining the contents of an object name registration record in the
% puntCAT database. The data in this record is provided by puntCAT for
% informational purposes only, and puntCAT does not guarantee its
% accuracy. This service is intended only for query-based access. You
% agree that you will use this data only for lawful purposes and that,
% under no circumstances will you use this data to: (a) allow, enable,
% or otherwise support the transmission by e-mail, telephone or
% facsimile of unsolicited, commercial advertising or solicitations; or
% (b) enable automated, electronic processes that send queries or data
% to the systems of puntCAT or registry operators, except as reasonably
% necessary to register object names or modify existing registrations.
% All rights reserved. puntCAT reserves the right to modify these terms at
% any time. By submitting this query, you agree to abide by this policy.
%
% WARNING: THIS RESPONSE IS NOT AUTHENTIC
%
% The selected character encoding "US-ASCII" is not able to represent all
% characters in this output. Those characters that could not be represented
% have been replaced with "?". Please resubmit your query with a suitable
% character encoding in order to receive an authentic response.
%
% Els camps que no apareixen a continuació s'han omès en virtud dels
% previsions de la normativa de protecció de dades/Fields not appearing below have been omitted according to european data protection provisions.
%
% En cas de voler contactar amb el titular, utilitzeu el formulari:
% http://contact.whois.cat
%
% En cas de que el domini estigui abusant de la política de protecció de dades
% utilitzeu el formulari:
% http://misuse.whois.cat
%
% En cas que el domini tingui un comportament anòmal (spam, phising,
% ...) utilizeu el formulari:
% http://problems.whois.cat
%
Domain ID: REG-D672590
Domain Name: exampleindividualoptout.cat
Domain Name ACE: exampleindividualoptout.cat
Variant Name: ex?mpleindividualopto?t.cat
Variant Name ACE: xn--exampleindividualoptout.cat
Domain Language: ca
Registrar ID: R-2021 (Registrar of record)
Created On: 2010-05-17 19:50:19 GMT
Last Updated On: 2011-05-13 09:44:21 GMT
Expiration Date: 2012-05-17 19:52:01 GMT
Status: clientDeleteProhibited, clientTransferProhibited
Name Server: ns4.example.com
Name Server ACE: ns4.example.com
Name Server: ns. example.com
Name Server ACE: ns. example.com
Name Server: ns3. example.com
Name Server ACE: ns3. example.com
Name Server: ns2. example.com
Name Server ACE: ns2.example.com

WEB WHOIS SERVICE

The web Whois service shares the same functionality as the port 43 service, with the exception that the input is implemented by using the means of HTML, i.e. by text input fields, radio buttons and check boxes. The output format is the same as described above. It is included in the HTML page in a way that can easily be copied by common browsers. To support the input and output of non-US-ASCII characters, the service uses the UTF-8 encoding.

Appendix S — Part VII

Miscellaneous Provisions

A) Domain Names Excluded from the Registry-Level Transaction Fee

As provided in Section 7.2 (c) of the Registry Agreement, Domain Names registered according to certain enumerated services in this Appendix S, Part VII, shall not initially be counted for the purposes of the Registry-Level Transaction Fee established in that Section.

These Services are initially the following:

1.Community-Assigned Domain Names

Community-Assigned Domain Names are names to be registered to the Registry and used as shared resources for cultural purposes. These names will not be subject to delegation or transfer. By way of example, Community-Assigned Domain Names may include names of relevant Catalan literary and/or popular culture figures, as well as collective designations of popular literary works relating to the Sponsored Community.

The number of Community-Assigned Domain Names shall not exceed 1000 at any given time, and, upon request, the Registry will provide to ICANN an up to date listing of such names. Upon termination of the Registry Agreement all Community-Assigned Domain Names will be assigned to the successor Registry or the entity specifically designed by ICANN for this purpose.

2. IDN Service

Registry will be offering the registration of Internationalized Domain Names (IDNs), with the special characters used in Catalan language. Registry will take a very cautious approach in its IDN offerings (as they are still in experimental stage, and don't offer the same level of functionality as regular ASCII domains do), according to the following guidelines:

  • Registry will accept IDNs in strict compliance with the technical requirements described in RFCs 3490, 3491, and 3492 (collectively, the "IDN standards") and following current and future ICANN Guidelines in this area.

  • Only one Language Table and language tag or label (Catalan language) and the characters contained therein will be accepted. The .cat IDN Language Table for Catalan language (ca) will be submitted to IANA immediately after signature of this Agreement.

  • IDNs will not initially be charged to Registrars or Registrants. Instead, they will be "bundled" with the "equivalent" ASCII domains (according to the table below), which will be charged at the regular prices.

  • IDNs cannot be registered if the subjacent ("equivalent") ASCII string is registered by a different Registrant (Domain Name Holder). It MUST have the same Registrant, contact details and nameservers as the bundled ASCII Domain Name. IDNs cannot be transferred independently (without the "equivalent" ASCII domain). "Equivalent" or "subjacent" are used for the purposes of this service only, as the pairs of characters listed below are certainly not equivalent in linguistic terms, but only represent the closest ASCII characters in which such names have been used in ASCII-only environments such as the DNS.

The list of non-ASCII-characters for Catalan language and their ASCII equivalent for the purposes of the defined service are:

  1. U+00E0 à->a U+0061

  2. U+00E8 è->e U+0065

  3. U+00E9 é->e U+0065

  4. U+00ED í->i U+0069

  5. U+00EF ï->i U+0069

  6. U+00F2 ò->o U+006F

  7. U+00F3 ó->o U+006F

  8. U+00FA ú->u U+0075

  9. U+00FC ü->u U+0075

  10. U+00E7 ç->c U+0063

  11. U+006C + U+00B7 + U+006C l·l ->l-l U+006C + U+002D + U+006C

Registry may eventually change this policy, unbundling IDNs from the artificially established variants, or "equivalent" ASCII domains. This will occur following discussion with ICANN when IDNs are considered to be a stable solution and, more specifically, when the following objective criteria are met:

  • IDNs natively resolve (i.e., resolve without the need of user-installed plug-ins) in browsers representing at least 75% of the installed base, including at least one major browser in the following Operating Systems (in their respective current form or their successors): Windows XP (including Windows PocketPC/Mobile); Mac OS X, and Linux.

  • IDNs are accepted and usable within email clients representing at least 75% of the installed base, including at least one major client for the following Operating Systems/platforms (in their respective current form or their successors) : Windows XP and successors (including Windows PocketPC/Mobile and successors); Mac OS X and successor; Linux; Palm OS; Symbian and Blackberry.

Registry will provide ICANN with 90 days advance written notice prior to (i) the unbundling of IDNs and their "equivalent" ASCII string and (ii) if for any reason Registry intends to start charging for the registration of IDNs separate and apart from the "equivalent" ASCII string.

Notwithstanding the above, ICANN may determine in ICANN's discretion that the above objective criteria are met, and withdraw the exception of IDNs from the calculation of the Registry-Level Transaction Fee described in Section 7.2 of the Registry Agreement. ICANN will notify Registry no less than 90 days in advance of an intent to withdraw the exception set forth above and thereby include IDNs within the calculation of the Registry-Level Transaction Fee.

B) Privacy Considerations

The Registry may, at its discretion, submit to ICANN for its consideration a proposal for additional measures to be implemented by the Registry that are designed to further safeguard data provided by Registrants.

Exhibit A to Part VII of Appendix S

Community-Assigned Names

Non-Exhaustive list of most relevant writers in Catalan language whose literary works are in the public domain (including some anonymous works and some collective designation of popular genres)

(Not yet posted for Public Comment)

Guerau de Cabrera

Guillem de Berguedà

Cerverí de Girona

Ramon Vidal de Besalú

Ramon Llull

Jaume I

Bernat Desclot

Ramon Muntaner

Pere III

Arnau de Vilanova

Francesc Eiximenis

Vicent Ferrer

Anselm Turmeda

Pero Martínez

Felip de Malla

Ramon de Perellós

Isabel de Villena

Bernat Metge

Antoni Canals

Ferran Valentí

Jaume March

Pere March

Andreu Febrer

Jordi de Sant Jordi

Ausiàs March

Joan Roís de Corella

Bernat Fenollar

Guillem Torroella

Jaume Roig

Història de Xacob Xalabín

Curial e Güelfa

Joanot Martorell

Espill de la vida religiosa

Cristòfor Despuig

Pere Serafí

Francesc Vicenç Garcia

Francesc Fontanella

Joan Ramis i Ramis

Rafael d'Amat i de Cortada, baró de Maldà

Miquel Ribes

Bonaventura Carles Aribau

Lo Rat Penat

Víctor Balaguer

Joaquim Rubió i Ors

Josep Lluís Pons i Gallarza

Teodor Llorente

Marià Aguiló

Manuel Milà i Fontanals

Pere Talrich

Magí Morera i Galícia

Jacint Verdaguer

Frederic Soler, 'Pitarra'

Àngel Guimerà

Gabriel Maura

Emili Vilanova

Carles Bosch de la Trinxeria

Josep Pin i Soler

Marià Vayreda

Dolors Monserdà

Joan Maragall

Raimon Casellas

Miquel Costa i Llobera

Miquel dels Sants Oliver

Joan Salvat-Papasseit

Joaquim Folguera

Cançoner popular/Cançoners

Cròniques

Noves rimades

Romanços de cec

Col.loquis

Consuetes mallorquines

Milacres de Sant Vicent

Goigs

Passions

Pastorets

Cant de la Sibil·la

Misteri d'Elx/Misteris

Jocs Florals

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."