This workspace has been created for use by the At-Large Definition and Structure Drafting Team (DSDT) to prepare draft text on the revision of the ALAC Rules of Procedure. The expectation is that from this drafting a new Introduction and Section 1 of a set of Rules of Procedure (RoPs) or Operating Principals (OPs) for ALAC will be created, adopted/endorsed and in use from end 2012.
The purpose of this workspace is to offer a space where the revised rules are worked on in pre-consensus mode during and between formal meetings of the Drafting Team.
General Notes on Style
It is expected that text for this section and the full document shall :-
- be written in 'plain language' which is easily and accurately translated into languages other than English.
- be clear and unambiguous text.
- be minimalist in approach using the "less is more" or "Keep it Simple" approach.
- wherever possible use a short text introduction / summary / outline to each section and Sub section and for any given (distinct) Principal or Procedure / Rule followed by an example if needed (this could be in a highlight or boxed 'call out' text) and where needed followed by numbered parts or sub-parts to give greater detail and clarity as needed.
Section 1 is envisaged to -
open with a 'What is the At Large Advisory Committee (ALAC)' outline that links to relevant ICANN By-Law references
that defines
the purpose of the ALAC (as distinct from At-Large) clearly, this would include tasks such as the accreditation of At-Large Structures (ALSes) and appointment/selection of Voting Delegates to NomCom and to Seat #15 of the ICANN Board.
as well as its roll in ICANN the organisation/entity and in any wider context with other ICANN elements/ parts including various Actors/Stakeholders;
- to this end, introductory text should draw from both existing ICANN By-Laws, as well as the intent of existing rules and practices both internal to ALAC and At-Large, as well as with the wider ICANN community.
This section should also outline (at least):
the expectations upon, and desired characteristics of, a person appointed to the ALAC as well as cross reference to participation requirements (including minimum criteria and metrics) when established.
the need for the ALAC to act/operate 'by consensus' and define what constitutes a quorum and/or Regional representational balance requirement for decisions and outcomes / work products; etc
and
that the ALAC jointly and severally is expected to act in the best interests of the At-Large Community'
as well as
describe and define any Leadership role(s) **note ICANN By-Laws require a Chair of the ALAC to be elected and post ALAC review this term is to be for 2 years serving end ICANN AGM in any given year they are elected for 2 calendar years until the end of the ICANN AGM of the second year ends)** ; including an ALAC sub -unit (currently called an Executive Committee) which is Regionally Balanced and functions to facilitate work product and activities of the ALAC between monthly meetings of the whole as well as act in support (administratively and as delegated from time to time) of the ALAC Chair.
- list describe the role and define any qualities and characteristics of various Representational Roles that are appointed by and act on behalf of the ALAC (and At-Large) in various fora;
- Note ICANN By-Laws require a Liaison of the ALAC to be appointed to both the GNSO and the ccNSO; But other Liaisons to ICANN AC/SO's should be addressed, as well as any other Appointments and Representational Roles such as (but not limited to) Independent Review Teams, Sub-Committees and Work Groups/ Drafting Teams internal to ALAC and At-Large as well as to other parts of ICANN (often called liaisons) and to ICANN Cross Community activities.
- Other matters pertaining to the Structure and Function of the ALAC.
Area for Draft text Mark Up by Pen Holders
(Please use either version control or simple date and name of editor to track changes in this space)
--- begin ccNSO (Olivier) 26 Aug 2012 ---
The country code Names Supporting Organisation (ccNSO) is a body within the ICANN structure created for and by ccTLD managers. It is described in article IV, Section 1 of the ICANN bylaws as being responsible for:
1. developing and recommending to the Board global policies relating to country-code top-level domains;
2. Nurturing consensus across the ccNSO's community, including the name-related activities of ccTLDs; and
3. Coordinating with other ICANN Supporting Organizations, committees, and constituencies under ICANN.
OCL: It is my recommendation to agree with this definition.
--- end ---
