1. Definitions

"the Company"	refers to Namespace South Africa ('Namespace SA'), a company [to be] registered in terms of section 21 of the Companies Act, registration number [to follow]
"the Board"	refers to the Board of Directors of Namespace SA, as defined in the Articles of Association of Namespace SA
a "subdomain"	is any subdivision of the ZA namespace which begins at the second level. Subdomains may be flat second-level domains, or may have a structure which extends beyond the second level. Unless the context specifies otherwise, the term 'subdomain of ZA' refers to immediate subdomains of ZA (i.e. those starting at the second level), and not further subdomains of subdomains.
a "charter"	is the 'constitution' of a subdomain, specifying inter alia the purpose and nature of the domain, the criteria for registration of names within the domain, and the manner of administration of the domain
a "central facilities provider", abbreviated "CFP"	is any entity providing central co-ordination facilities for the database of information about a subdomain. These services might range from storage and maintenance of a single central database in the case of a small subdomain, to the provision of secure time stamping services in the case of a larger, replicated domain.
a "registrar"	is any entity providing actual registration services in a subdomain. The registrar handles applications for new delegated names within the subdomain and for updates to domain registration information. The registrar causes the central database to be updated, liaising with a CFP where appropriate.
a "registrant"	is any person or entity who has registered a domain name within a subdomain
an "applicant"	is any person or entity requesting the creation of a subdomain, or (depending on the context) any person or entity requesting accreditation as a registrar or CFP
"commissioning"	of a new subdomain refers to the technical and administrative preparations required to ready the subdomain for use on the Internet. This includes ensuring that name service and registration services for the domain are operational. The actions required to commission a domain are typically performed by the successful applicant, in conjunction with the initial CFP and registrars for the domain.
"activation"	of a new subdomain is the formal entry by the Company of the domain into the ZA zone file, thus making it visible on the Internet. A domain will be activated only after it has been successfully commissioned.
"public Internet site"	refers to a publicly-accessible Internet resource which the Company shall maintain for the purpose of disseminating notices and information, and for gathering public comment. Such site should use whatever medium the Company deems appropriate from time to time, in order to allow the widest possible number of Internet users to have access to the site. At the time of writing, a World-Wide Web site would seem the most appropriate, but it is envisaged that technical changes over time might necessitate a review of the medium chosen.
	Wherever reference is made to publication of a document on the Company's public Internet site, the Company shall also ensure that the document is accessible to people who have Internet access, but who do not have access to the Company's public Internet site (e.g. through electronic mail); and to people with no Internet access (e.g. through the keeping of printed records at the Company's offices which may be faxed on request)

2. Introduction

The aim of the following procedures is to ensure a fair and equitable system for the management of the ZA top-level namespace, by providing even-handed mechanisms to be followed for the creation, modification and deletion of domains. The guiding principles in the development of the following policies are as follows:

2.1.	Subdomains of ZA are primarily created in the public interest. Applications for domains should therefore be submitted when the creation of a new division of the ZA namespace would serve a clear need by the public, or some reasonable subsection of the public. Domains are not created, and should not be applied for, for the sole and exclusive benefit of a person or organisation.
2.2	Subdomains should enhance the ZA namespace on an ongoing basis. This requires that they serve a significant community, that they be substantially further delegated, and that there is a strong likelihood of their ongoing continuity and stability.
2.3.	To serve the latter end, domains should not be created unless there is a clear and sustainable plan for the technical and administrative operation of the domain, with specific identified entities willing to assume the various roles necessary
2.4.	The Company, through the board, acts as the 'trustee' of the ZA domain namespace. No 'right' in or 'ownership' of a subdomain of ZA vests in any person or organisation
2.5.	The board has wide discretion to create, delete and alter subdomains of ZA. The Board is required to consider the interests of the public, and the interests of existing registrants. There are two primary checks and balances on the power of the board. The first is a requirement for transparency: all decisions and reasoning must be made public. The second is the accountability of the Board to the membership envisaged in the Articles of Association of the Company.
2.6.	The registration and operation of all domains at every level of ZA, and the actions of the Company and the Board with regard to any domains, must not compromise the integrity of the domain naming system in South Africa or elsewhere on the Internet, and should be in accordance with all relevant RFCs and/or other standards.
2.7.	The administration of the ZA namespace should be founded on a firm contractual basis, starting with the Articles of Association of the Company, and descending into this document and other policy documents; the charters of the individual subdomains; and the application forms signed by registrants in the subdomains
2.8.	The operation of subdomains should be performed in a manner that minimises overhead in all senses of the word, and maximises accountability. To this end, it is envisaged that almost all domains would be open to multiple registrars. Practically, many smaller domains may have only a single registrar (whose function may even be combined with that of a CFP), but the important principle is that all domains should be open to additional registrars, should there be a demand. At the time of writing, technology does not allow the total decentralisation of domain database activities (even in a replicated database, there is some need for central synchronisation to determine which registration is accepted in the case of multiple simultaneous registrations). These functions are consolidated in the CFP, which should be kept as 'lean' as possible (being an unavoidable monopoly bottleneck), given the requirements of each specific subdomain, and the capabilities of available technology.

3. Applications for the creation of subdomains of ZA

3.1.	Each application for a new domain shall specify: -
3.1.1.	the applicant, who should also be the administrative contact for a domain. The applicant shall be a legal persona, and shall consent to the jurisdiction of the South African courts in all matters relating to its dealings with the Company
3.1.2.	The proposed initial central facilities provider for the domain
3.1.3.	The proposed initial registrar or registrars for the domain (the entities who intend to provide registration services for the domain).
3.2.	No domain shall be accepted unless an initial central facilities provider, and at least one initial registrar are nominated.
3.2.1.	The initial CFP may be an existing CFP (one already accredited in terms of section 7 below), the applicant itself, or an alternative organisation. The initial registrar(s) may be any mixture of existing accredited registrars, the applicant itself, and/or alternative organisations.
3.2.2.	Where the proposed initial CFP is not an accredited CFP, or where any proposed initial registrar is not an existing accredited registrar, such proposed initial CFP or registrar shall satisfy the Board that it meets the criteria for accreditation outlined in section 7 below.
3.2.3.	The Applicant may approach the Company for assistance in securing an initial CFP and/or registrar, where necessary.
3.3.	Every application for a domain shall be accompanied by a proposed charter for the domain. No domain shall be created unless a charter has been approved by the Board.
3.4.	Applicants may suggest a structure for the new domain (e.g. further geographical subdivisions under a SLD). The Board may accept this suggestion with or without revision.
3.5.	The application shall contain the following information: -
3.5.1.	Full details of the applicant (full name and company registration number where appropriate; physical, postal and email contact addresses; telephone and fax numbers)
3.5.2.	The proposed name of the new domain
3.5.3.	Details of any proposed structure (e.g. geographical) for the new domain
3.5.4.	A brief statement of the purpose of the domain (e.g. "The CROOK.ZA domain would provide a clear means for the vast number of disreputable individuals and enterprises in the country to identify themselves as such")
3.5.5.	Details of the proposed initial CFP. Where the proposed CFP is not the Applicant, the consent of an authorised representative of the CFP shall be included. Where the proposed CFP (including the Applicant, if appropriate) is not an existing accredited CFP, such additional details as are required by section 7 shall be provided in respect the proposed CFP.
3.5.6.	Details of the proposed initial registrar(s). Where any of the proposed registrars is not the Applicant, the consent of an authorised representative of each such registrar shall be included. Where any of the proposed registrars (including the Applicant, if appropriate) is not an existing accredited registrar, such additional details as are required by section 7.4 shall be provided in respect of each such registrar.
3.5.7.	A brief motivation, which should address each of the points in 3.13 below
3.6.	A charter for a domain shall specify at least: -
3.6.1.	The name and purpose of the domain
3.6.2.	The structure of the domain
3.6.3.	The criteria for acceptance of registration of names within the domain, including: -
3.6.3.1.	Which registrants may register names (e.g. 'The CROOK.ZA domain is open to all individuals who have been sentenced by a competent court for any crime involving a jail term without the option of a fine')
3.6.3.2.	How many names a registrant may register, and what form these names must take (e.g. 'Registrants in CROOK.ZA may register any number of names, provided that they were using the name as an alias at the time of their arrest and/or conviction.')
3.6.3.3.	The process to determine whether a proposed name within the subdomain meets the criteria for registration. This might, for example, require consulting or obtaining documentation from a third party body such as the Law Society or the Registrar of Trademarks
3.6.4.	Details of the management of the policy of the domain: is the policy to be managed by the Company, or by some other means (committee of registrants, etc.)
3.6.5.	Details of the dispute resolution procedure to be followed in the case of an appeal against a decision of the domain administrator(s). This should specify: -
3.6.5.1.	the manner of resolution (typically the involvement of a neutral third party on either an expert determination or arbitration basis);
3.6.5.2.	the nature of any person(s) to be consulted (which may, with the consent of the Board, be the Company, or such experts as the Company may from time to time appoint); and
3.6.5.3.	the manner of apportioning costs (typically, a determination by the person being consulted)
3.6.6.	Additional requirements, if any, which pertain to registrars wishing to be accredited to register names in the domain
3.6.7.	The manner in which name service for the domain is to be provided
3.7.	The charter, together with these procedural rules, forms the contractual basis of name registration in a domain.
3.7.1.	No CFP or registrar may be accredited for a domain unless they agree in writing to adhere to the charter of the domain when providing their respective services to it.
3.7.2.	No registrant shall register a name in any subdomain unless they sign acceptance of the terms of the charter and the procedures outlined in this document. This acceptance would typically be included in the application form which registrants fill in to apply for a name (wording along the lines of 'I hereby acknowledge that I have read and understood the charter of the XXX.ZA domain, along with the procedures and rules for the conduct of the ZA namespace, and I agree to abide by same' may be sufficient). Every registrant shall also assent to the jurisdiction of the South African courts.
3.7.3.	Each registrar shall ensure that all registrants whose registrations they process conform to the provisions of 3.7.2 above. The Company reserves the right to order the deletion of any domain whose registrant has not assented to the charter of the subdomain above it, or to these regulations, and the registrar who processed the registration shall indemnify the Company against any claim for damages arising from such deletion.
3.8.	Any subsequent alterations to a charter must be approved by the Board before they may be effected.
3.9.	The application for a domain does not confer any 'right' to the domain, or 'ownership' of the domain.
3.10.	Domains should normally be open to any registrars who wish to be accredited to register names in that domain, not just to the initial registrars. Applicants may propose additional criteria which registrars should follow (e.g. 'Any registrar of names in the CROOK.ZA domain must check SA Prisons Services records to confirm validity of the application before registering a name')
3.11.	Notwithstanding compliance with the criteria above, the Board may in its sole discretion refuse to process an application which is in its view frivolous or offensive; provided that it shall provide a list of names thus rejected on its public Internet site (except where such names are obscene and/or offensive)
3.12.	Upon receipt of an application which meets the criteria above by the Company, it shall be posted on the Company's public Internet site for a period of no less than thirty (30) days to allow public comment.
3.12.1.	The facility for public comment shall be structured in such a manner as to make comments immediately available to the public view, to allow a more interactive comments process.
3.12.2.	Members of the public should, however, be allowed to specify that their comments remain confidential; in which event such comments and their authors shall be revealed only to the Board, authorised employees and agents of the Company, and the Applicant.
3.12.3.	Notification of this posting shall be sent to all currently serving directors, and to all members who have asked to receive Company notifications.
3.13.	The ultimate decision to accept or reject an application rests with the Board, who will take the following into consideration when deciding whether to accept the application: -
3.13.1.	The extent to which creation of the domain would benefit the public, or the subsection of the public to whom the domain pertains
3.13.2.	The appropriateness of the proposed name (for example, 'CROOK.ZA' would be appropriate for a domain for the criminal element; 'HONESTSOULS.ZA' would not)
3.13.3.	The size of the population of the domain (for example, the domain 'BLIKKIESDORPSHOPS.ZA', designed to serve the eleven traders in the Blikkiesdorp area might be rejected as too small). When considering a 'small' domain, the Board shall consider recommending the creation of a larger subdomain with a sub-structure where appropriate to accommodate the need (in the example above, the board might recommend the creation of a SHOPS.ZA domain, with geographical subdivisions 'BLIKKIESDORP.SHOPS.ZA', etc)
3.13.4.	The likelihood of significant delegation
3.13.5.	The prevention of unnecessary overlap in the namespace (if 'CRIMINAL.ZA' already existed, the application for 'CROOK.ZA' would serve little purpose; 'CROOK.ZA', though in a sense catering for a proper subset of the community for 'NOM.ZA', nonetheless might be deemed not to 'overlap' with it, since it caters for an independently identifiable subset which is worthy of separate identification and which might not lend itself to a sub-structure of the form CROOK.NOM.ZA)
3.13.6.	The appropriateness of the charter to the purpose of the domain
3.13.7.	The permanence of the domain, and the measures in place to ensure its continuity
3.13.8.	The risks involved to the population which the domain serves, to the Internet community, and to the Company, if the Applicant and/or the initial registrars cease to maintain the domain.
3.13.9.	Any trademark or other intellectual property rights issues
3.13.10.	Any public comments received
3.14.	The Board may:
3.14.1.	Accept an application
3.14.2.	Accept an application subject to specific conditions or alterations
3.14.3.	Refer an application back to the Applicant with comments
3.14.4.	Reject an application
3.15.	In all cases, the Board shall notify the Applicant of its decision, along with suitable grounds for this decision, within seven (7) days of the decision being made. Within seven (7) days after the Applicant has been notified, the board shall publish its decision, and the grounds therefor, on its public Internet site.
3.16.	Applicants are encouraged to discuss their application and the accompanying charter informally with the Board prior to the submission thereof. The Board shall render reasonable assistance to potential Applicants when approached
3.17.	Each application for the creation of a new domain shall be accompanied by a non-refundable application fee to cover the costs of processing. This fee shall initially be set at Fifty Rands (R50.00) inclusive of any applicable taxes, and may be revised from time to time by the Company in general meeting. This fee may be waived by the Board in the public interest.

4. Commissioning and activation of new subdomains

4.1.	Once the creation of a new domain has been approved, it must be successfully commissioned before it is activated by the Company.
4.2.	The commissioning of a domain is the responsibility of the applicant, together with the initial CFP and registrars. It involves the following: -
4.2.1.	Establishing of the necessary database and other structures to store information about the domain
4.2.2.	Establishing at least three (3) initial name servers for the domain. A minimum of two (2) of these servers shall be located on physically separate networks within South Africa, and at least one (1) server shall be located outside South Africa.
4.2.3.	Establishing all necessary registration mechanisms for the domain
4.3.	The 'activation' of the domain is performed by the Company once it is satisfied that the requirements for commissioning have been satisfied, along with any additional requirements which may be set by the Board. Activation involves: -
4.3.1.	Entry of the final details for the subdomain in the central database for ZA
4.3.2.	Entry of the necessary records in the master zone file for ZA to perform the appropriate delegation for the domain
4.4.	No domain will be activated unless it has been successfully commissioned. If a domain is not commissioned within thirty (30) days of the application being approved, the approval shall lapse.
4.5.	The Company shall make reasonable efforts to ensure that a domain is activated within fourteen (14) days of its being satisfied of the successful commissioning thereof. It is the responsibility of the Applicant to inform the Company when the domain has been commissioned.

5. Deletion or redelegation of domains

5.1.	The Board may at its discretion delete or redelegate a registered domain:
5.1.1.	If name service for a domain ceases
5.1.2.	If there has been insufficient delegation in a domain within a year of its creation
5.1.3.	Upon request of a substantial majority of registrants in that domain
5.1.4.	Upon failure of all domain registrars to pay the annual domain levy
5.1.5.	For any other reason determined by the board to be in the public interest
5.2.	In considering the deletion or redelegation of a domain, the board shall foremost consider the interests of the community which the domain is supposed to serve, and in particular the existing registrants within that domain.
5.3.	Redelegation has a significantly lower impact on existing registrants that the complete deletion of a domain. The Board shall consider redelegation in preference to deletion in all cases. The board shall make reasonable efforts to find an alternative solution before deletion is considered.
5.4.	If the board considers deleting or redelegating a domain as the result of the action or neglect of any entity, that Board shall attempt to notify the entity of its intentions, and allow the entity a minimum of thirty (30) days to rectify the situation.
5.5.	Where the Board contemplates redelegating a domain, it must first: -
5.5.1.	Attempt to notify the currently registered contacts for the domain, the CFP and the registrars in the domain, at least thirty (30) days before the date of the proposed redelegation. Notification shall be made to the contact addresses supplied by the original Applicant, the CFP and the registrars in their respective applications (or as subsequently amended by written notice to the Company).
5.5.2.	Publish a notice of its intention to delete the domain on its public Internet site at least thirty (30) days before the date of the proposed redelegation, to allow public comment. Notification of this posting shall be sent to all currently serving directors, and to all members who have asked to receive Company notifications.
5.5.3.	Make reasonable efforts to notify the registrants within the domain, and any other interested parties
5.6.	Where the Board contemplates deleting a domain, it must first: -
5.6.1.	Attempt to notify the currently registered contacts for the domain, the CFP and the registrars in the domain, at least sixty (60) days before the date of the proposed redelegation. Notification shall be made to the contact addresses supplied by the original Applicant, the CFP and the registrars in their respective applications (or as subsequently amended by written notice to the Company).
5.6.2.	Publish a notice of its intention to delete the domain on its public Internet site at least sixty (60) days before the date of the proposed deletion, to allow public comment. Notification of this posting shall be sent to all currently serving directors, and to all members who have asked to receive Company notifications.
5.6.3.	Make reasonable efforts to notify the registrants within the domain, and any other interested parties

6. Emergency suspension and redelegation of domains

6.1.	Notwithstanding the above, the board may immediately suspend or alter the details of the registration of a domain on a temporary basis: -
6.1.1.	if the existing operators of a domain either cease to provide domain name service for the domain, or
6.1.2.	if the manner of operation of the domain presents an immediate and serious threat to the integrity of the naming system in South Africa or globally, and/or to existing and potential registrants in the domain
6.2.	As soon as possible after the temporary suspension or redelegation of a domain, but in any event within forty-eight (48) hours, the Board shall publish on its public Internet site notification of such redelegation or suspension, along with its reasons for so doing.
6.2.1.	Wherever possible, the Board shall arrange for such publication to occur before, or simultaneously with, the redelegation or suspension of the domain in question.
6.2.2.	The Board shall make reasonable efforts to notify the administrative contact, the CFP, the registrars and the registrants in a domain prior to, or as soon as possible after, a temporary suspension or redelegation. Should the Board make such attempts at notification after the fact, it shall take cognisance of the possibility that any suspension may affect the ability to communicate electronically with the various parties named above.
6.3.	The Board shall make reasonable efforts to resolve whatever situation led to its decision to redelegate or suspend a domain temporarily, including but not limited to the initiation of appropriate procedures in terms of 5 above.
6.4.	The Board in all of its actions shall attempt to minimise inconvenience to existing registrants in an affected subdomain

7. Accreditation of central facilities providers and registrars

7.1.	No CFP or registrar for any subdomain of ZA may operate as such unless accredited by the Company.
7.2.	CFPs and registrars may be accredited for one or more subdomains within ZA. The requirements for each specific subdomain may be varied by the Board in the public interest, although an attempt should be made to observe a broad uniformity. For example, the requirements imposed on a registrar for a small 'public service' domain serving, say, schools, might be less onerous than the requirements for a large, busy, commercially significant domain.
7.3.	Each CFP and registrar must be a legal persona. All CFPs and registrars shall, regardless of their physical location or region of operation, nominate a domicilium citandi et executandi within the borders of South Africa, and shall accede to the jurisdiction of the South African courts in all matters relating to ZA namespace.
7.4.	Each application for accreditation shall include:
7.4.1.	Full details of the applicant (full name and company registration number where appropriate; physical, postal and email contact addresses; telephone and fax numbers)
7.4.2.	Sufficient details to enable the Board to determine whether the applicant meets the accreditation criteria
7.4.3.	An undertaking, signed by the applicant or an authorised representative thereof, to adhere to the obligations in 7.7 or 7.8 in the case of a CFP or registrar respectively
7.4.4.	A non-refundable application fee. This fee shall initially be set by the Company in general meeting from time to time. This fee may be waived by the Board in the public interest.
7.5.	The board shall set baseline criteria for the accreditation of CFPs and registrars. These criteria shall be published on its public Internet site. The criteria shall cover the following areas: -
7.5.1.	Operational: -
7.5.1.1.	The financial stability of the applicant
7.5.1.2.	An operational plan, including provision for growth in the number of registrations and a reduction in the number of registrations
7.5.1.3.	Details of fee structures, if any
7.5.1.4.	Procedures in the event of the winding down of the applicant
7.5.2.	Administrative: -
7.5.2.1.	Managerial and administrative systems
7.5.2.2.	Personnel size, roles and qualifications
7.5.2.3.	Support mechanisms to be provided
7.5.2.4.	Anticipated capacity (number of registrations/updates per month)
7.5.2.5.	Billing mechanisms, where appropriate
7.5.3.	Technical: -
7.5.3.1.	Technical skills and experience
7.5.3.2.	Equipment, infrastructure and software
7.5.3.3.	Manner of integration with central or shared databases, where necessary
7.5.3.4.	Compliance with any shared, replicated or distributed registry standards and protocols where necessary
7.5.3.5.	Technical procedures to be followed for the creation, updating and deletion of domains
7.5.3.6.	Adherence to relevant RFCs and/or other standards
7.5.4.	Stability: -
7.5.4.1.	Security procedures (both electronic and otherwise) to be followed
7.5.4.2.	Disaster recovery and prevention measures to be followed
7.6.	The Board, in setting baseline criteria, shall attempt to make them the absolute minimum required to ensure the integrity, stability and continuity of the domain naming system. In setting criteria, and evaluating applications, the Board shall attempt to allow potential CFPs and registrars the maximum flexibility in their operational, administrative and technical structure.
7.7.	Applicants for accreditation as a CFP shall commit themselves at the time of application to adhering to the following obligations, should their application be successful. CFPs shall:
7.7.1.	Acknowledge adherence to, and acceptance of, these procedures and policies, along with the charter of each domain in which they are applying for accreditation
7.7.2.	Not cease to provide central facilities for any domain unless a satisfactory alternative CFP has been found and the database has been successfully transferred; or unless required to do so by the Board. If required to cease providing facilities for a domain by the Board, a CFP shall forthwith provide a full copy of the database for that domain to the Company.
7.7.3.	Be willing to operate name servers for each domain in which they are accredited, in addition to the ZA top-level domain, on a free or reasonable cost-recovery basis at the discretion of the CFP. CFPs are not obliged to operate such name servers unless and until requested to do so by the Board, but are free to do so at their own instance, provided that the Company shall not be required to accept any charges for name services provided at the sole instance of a CFP.
7.8.	Applicants for accreditation as a registrar shall commit themselves at the time of application to adhering to the following obligations, should their application be successful. Registrars shall:
7.8.1.	Acknowledge adherence to, and acceptance of, these procedures and policies, along with the charter of each domain in which they are applying for accreditation
7.8.2.	Not cease to provide registration services for any domain unless satisfactory arrangements for the transfer to another registrar of registration services and details of registrants served by the registrar have been made; or unless required to do so by the Board. If required to cease providing facilities for a domain by the Board, a registrar shall forthwith provide a full copy of any and all information it may have relating to registrants in that domain to the Company.
7.8.3.	Be willing to operate name servers for each domain in which they are accredited, in addition to the ZA top-level domain, on a free or reasonable cost-recovery basis at the discretion of the registrar. Registrars are not obliged to operate such name servers unless and until requested to do so by the Board, but are free to do so at their own instance, provided that the Company shall not be required to accept any charges for name services provided at the sole instance of a registrar.
7.8.4.	Agree to pay such levies as are determined from time to time by the Company in general meeting. Such levies will typically be determined on a per-domain basis, and may be recovered from registrants by registrars in any reasonable manner.
7.9.	An existing accredited CFP or registrar may apply for accreditation in additional subdomains. Such application shall adhere to requirements which the Board may from time to time determine. These will typically be simpler than those for the initial application, and shall at least include the following: -
7.9.1.	Acceptance of the charter(s) of the new subdomain(s) applied for
7.9.2.	Demonstration that the applicant satisfies any specific additional criteria in the new subdomain(s) applied for
7.10.	The board, upon receipt of an application for accreditation, shall publish details of the applicant on its public Internet site.
7.10.1.	The applicant may request that details of its application be kept confidential, except for names and contact details.
7.10.2.	The Board shall inform the applicant whether it is prepared to accept the confidentiality of each section so stipulated by the applicant.
7.10.3.	If the Board declines to accept the confidentiality of any section, the applicant may at its discretion remove that section, in which event it will not be considered by the Board in evaluating the application; or retain that section, in which event it will be made public with the rest of the application.
7.11.	The board may: -
7.11.1.	Accept an application for accreditation in all domains for which an applicant seeks accreditation, or for any subset of these domains
7.11.2.	In the case of a combined application for accreditation as a CFP and a registrar, accept the applicant as an accredited CFP, an accredited registrar, or both
7.11.3.	Reject an application
7.12.	In all cases, the Board shall notify the Applicant of its decision, along with suitable grounds for this decision, within seven (7) days of the decision being made. Within seven (7) days after the Applicant has been notified, the board shall publish its decision, and the grounds therefor, on its public Internet site.
7.13.	Applicants are encouraged to discuss their application informally with the Board prior to the submission thereof. The Board shall render reasonable assistance to potential Applicants when approached
7.14.	The Company shall from time to time conduct audits of accredited CFPs and registrars (typically on a six-monthly basis) to ensure that the standards and procedures in the initial application are being adhered to
7.15.	The CFP for each subdomain may be chosen by tender, or by some other fair and equitable process. When appointed as the CFP for a subdomain, the CFP shall, in addition to acceding to the charter of a domain, sign a contract of appointment, which shall specify inter alia the period of appointment of the CFP, which period shall not preclude the suspension or revocation of the accreditation of the CFP, and the procedure for re-appointment (which may be a re-tendering process, or some other fair and equitable process).
7.16.	The Company may, at the discretion of the Board, act directly as CFP for one or more subdomains, or contract out the CFP function for one or more domains to third parties to be determined by the Board; if the Board believes the interests of the public and of the registrants in each such domain would be best served by so doing.

8. Suspension and revocation of accreditation

8.1.	The Board may at its discretion suspend or revoke the accreditation of a CFP or registrar: -
8.1.1.	Should the CFP or registrar fail to adhere to these procedures and rules, including though not limited to the provisions of sections 7.7 or 7.8, as appropriate, or to the charter of any domain, or to any other procedures established by the Company from time to time.
8.1.2.	Should the manner of operation or administration of the CFP or registrar at any time fail to adhere to the standards undertaken to be maintained in the application for accreditation.
8.1.3.	Upon failure by the CFP or registrar to follow any reasonable order of the Board given in terms of these rules
8.1.4.	Upon failure by any CFP or registrar to pay any monies due to the Company, including without limiting the generality of the term, the levy on registered domain names payable by registrars
8.1.5.	Should the CFP or Registrar be unreachable for a protracted period through any of the contact addresses or telephone numbers supplied by it
8.1.6.	For any other reason determined by the board to be in the public interest
8.2.	No such suspension or revocation shall in any way give rise to a claim against the Company for any compensation or damages, or for the refund of any deposit, application fee, or other monies paid to the Company.
8.3.	The Board shall publish details of any suspension or revocation of accreditation, including the reasons therefor, on its public Internet site within fourteen (14) days of such suspension or revocation.
8.4.	Where the Board contemplates revoking the accreditation of a registrar or CFP it must first: -
8.4.1.	Attempt to notify the currently registered contacts for the CFP or registrar in question at least thirty (30) days before the date of the proposed revocation. Notification shall be made to the contact addresses supplied by the original CFP or registrar in its respective applications (or as subsequently amended by written notice to the Company). If it is reasonably possible to do so, the affected CFP or registrar shall be given the opportunity to remedy whatever breach or default gave rise to the Board considering the revocation
8.4.2.	Publish a notice of its intention to revoke the accreditation on its public Internet site at least thirty (30) days before the date of the proposed deletion, to allow public comment. Notification of this posting shall be sent to all currently serving directors, and to all members who have asked to receive Company notifications
8.5.	The board shall not revoke the accreditation of a registrar unless and until satisfactory arrangements have been made to accommodate the registrants who have registered with that registrar, and unless reasonable efforts have been made to notify the said registrants of any changes
8.6.	The board shall not revoke the accreditation of a CFP unless and until satisfactory arrangements have been made to host the central facilities for those subdomains hosted by the CFP
8.7.	Notwithstanding the above, the board may temporarily suspend the accreditation of any CFP or registrar at any time if in its discretion it believes that this would be in the public interest; provided that the conditions of clause 8.3 are complied with.