هذا المحتوى متوفر فقط باللغة (أو اللغات)
Appendix S — Part 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.
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.
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:
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
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:
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
Registry will implement the following Start-up Plan for the .cat Sponsored TLD:
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.
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).
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.
Registry will conduct comprehensive testing of the registry system and registration procedures (including the interfaces with Registrars).
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.
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:
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.
All legal entities proving prior online communications in Catalan will be admitted in Phase II, which will last for 60 days.
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.
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:
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:
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].
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.
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:
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:
In addition, the following search options are available:
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:
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
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
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.
Domain Data Format
Depending on the query and options, either a short or a long format is produced.
Domain ID: D38482
Domain ID: D38482
Regarding the included contact data, see below also.
Host Data Format
Host ID: H38473
Host ID: H38473
Contact Data Format
Contact ID: C394583
Contact ID: C394583
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.
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.
Application ID: A38482
Application ID: A38482
Registrar Data FormatRegistrar ID: IANA-15
Organization: CORE Internet Council Of Registrars
Street: WTC II, 29 route de Pre-Bois
Postal Code: 1215
Whois Server: whois.core.info
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.
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
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:
The list of non-ASCII-characters for Catalan language and their ASCII equivalent for the purposes of the defined service are:
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:
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
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ú
Arnau de Vilanova
Felip de Malla
Ramon de Perellós
Isabel de Villena
Jordi de Sant Jordi
Joan Roís de Corella
Història de Xacob Xalabín
Curial e Güelfa
Espill de la vida religiosa
Francesc Vicenç Garcia
Joan Ramis i Ramis
Rafael d'Amat i de Cortada, baró de Maldà
Bonaventura Carles Aribau
Lo Rat Penat
Joaquim Rubió i Ors
Josep Lluís Pons i Gallarza
Manuel Milà i Fontanals
Magí Morera i Galícia
Frederic Soler, 'Pitarra'
Carles Bosch de la Trinxeria
Josep Pin i Soler
Miquel Costa i Llobera
Miquel dels Sants Oliver
Romanços de cec
Milacres de Sant Vicent
Cant de la Sibil·la