Page History

1.1

AmendBylaws ArticleXI.s2(4)(a)toclarifypurposes,asproposed.

1.1(a)

Submit to the Board the following revision to ICANN Bylaws  XI.2.4.a, drafted in collaboration with Legal:

The At-Large Advisory Committee (ALAC) is the primary organizational home within ICANN for individual Internet users. The role of the ALAC shall be to consider and provide advice on the activities of ICANN, insofar as they relate to the interests of the individual Internet users. This includes policies created through ICANN’s Supporting Organizations, as well as the many other issues for which community input and advice is appropriate. The ALAC, which plays an important role in ICANN’s accountability mechanisms, also coordinates some of ICANN's outreach to individual Internet users.

See: ICANN Bylaws VI.2.1.e 

See: ICANN Public Comment - Proposed Bylaws  Amendment to Add Voting Director from the At-  Large Community to the ICANN Board of Directors 

See: ICANN Public Comment - Proposed ICANN  Bylaw Revisions Regarding the ALAC

1.1(b)

Submit to the Board the following revisions to ICANN  Bylaws XI.2.4.j, drafted in collaboration with Legal:

The ALAC is also responsible, working in conjunction with the RALOs, for coordinating the following activities:

1. Making a selection by the At-Large Community to fill Seat 15 on the Board. Notification of the At- Large Community’s selection shall be given by the ALAC Chair in writing to the ICANN Secretary, consistent with Article VI, Sections 8(4) and 12(1).
2. Keeping the community of individual Internet users informed about the significant news from ICANN;
3. Distributing (through posting or otherwise) an updated agenda, news about ICANN, and information about items in the ICANN policy- development process;
4. Promoting outreach activities in the community of individual Internet users;
5. Developing and maintaining on-going information and education programs, regarding ICANN and its work;
6. Establishing an outreach strategy about ICANN issues in each RALO's Region;
7. Participating in the ICANN policy development processes and providing input and advice that accurately reflects the views of individual Internet users;
8. Making public, and analyzing, ICANN's proposed policies and its decisions and their (potential) regional impact and (potential) effect on individuals in the region;
9. Offering Internet-based mechanisms that enable discussions among members of At-Large structures; and
10. Establishing mechanisms and processes that enable two-way communication between members of At-Large Structures and those involved in ICANN decision-making, so interested individuals can share their views on pending ICANN issues.

See: ReviewoftheAt‐LargeAdvisoryCommittee-  FinalReportoftheALACReviewWorkingGroup  onALACImprovements

The ALAC has a continuing purpose in the ICANN structure. This continuing purpose has four key elements:

• Providing advice on policy;
• Providing input into ICANN operations and structure;
• Part of ICANN’s accountability mechanisms;
• An organizing mechanism for some of ICANN’s outreach; and
• The section of the ICANNBylawsthat deals with the ALAC should be changed to reflect this purpose.

1.4(a)

This review should include consideration of the role, selection process and term length of the ALAC Chair & Vice Chairs.

As noted above, any change of the term length of the ALAC Chair, as suggest by Recommendation 1.4, would require a change to the ALAC’s Rules of Procedures.

2.1

IdentifyallthestepsrequiredtoimplementtheadditionofonevotingmemberappointedfromtheAt‐LargeCommunitytotheICANNBoard.

See:At-LargeDirectorCandidate2013Workspace

At-LargeselectedICANNBoardmemberhasbeencompletedasSeat15isnowoccupiedbyanAt-LargeselectedvotingDirector.However,theALACanditsTaskforcehavedeterminedthatthe ALAC ABSdtandtheALACBCECwillneedtoreconveneforfutureappointmentsonthisissue.

2.2

SubmitthefinalselectionprocesstotheBoardviatheSICforapproval.

See:2.1Notessection

2.3

ImplementorconfirmrelatedBylawchanges.

See:2.1Notessection

2.4

Onceapproved,beginselectionprocess,ina careful and systematic manner, within the At‐Large Community.

See:2.1Notessection

2.5

EndorsementofselectionchoicebytheALAC.

See:2.1Notessection

2.6

ApprovalofselectionchoicebyICANNBoardandseatingofBoardmember.

See:2.1Notessection

2.7

ConsideroptionsregardingtheAt‐LargeLiaisontoBoardvis‐à‐visa new Director.

See:2.1Notessection

3.1

Ensureexistingstructuredoesnotpresentobstaclestocommunityoperationanddevelopment.

3.1(a)

Establish a Working Group (WG) to ensure that the At- Large information already available is organized properly and easily accessible by end users.

Allocated to the Policy Staff in support of the ALAC, the ALAC, and Regional Leadership.

3.1(b)

Introduce to the ALSes selected information- dissemination, communication and collaboration tools (such as Posterous, Twitter Tweets, mobile-device compatibility) and provide training.

Allocated to the At-Large Technology Taskforce.

3.1(c)

Promote further use of the At-Large Calendar to ALSes.

Allocated to the Policy Staff in support of the ALAC, the ALAC, and Regional Leadership.

3.1(d)

Create and distribute a brief orientation/ instruction package about information dissemination, communication, & collaboration tools introduced to ALSes.

See: ICANN's e-learning page.

Additionally, the ALS Starter Kit already includes some of this information. Please click one of the links below to download the ALS Starter Kit in one of the six UN Languages.

English, Español, Français, Pусский, 中文, العربية

ExternalEducation.

AllocatedtothePolicyStaffinsupportoftheALAC,theALAC,RegionalLeadership,ALSes,andotherrelevantpartiestoensurethatthesystemisinteractivewithICANNwideactivities.

4.1(a)

Establish the ICANN Academy, an annual training program for new At-Large ALS members, modeled after aspects of the ICANN Fellowship and Diplo Foundation.

See: At-Large ICANN Academy Expanded Working  Group Workspace

The intent is to establish a Pilot Program during the ICANN Meeting in Toronto in October 2012.

InternalEngagement.

4.2(a)

Establish an engagement program for existing At-Large ALS members, to be conducted year- round and modeled after certain aspects of the Diplo Foundation (specifically, this is the At-Large Capacity Building Program).

See: LACRALO Capacity Building Budget Request

See: AFRALO Dakar Events See: LACRALO San Jose Events

Allocated to the ALAC Chair, the Executive Committee, and the Director for At-Large.

The intent is for this program to start (be funded for) FY2012.

4.2(b)

Make available Confluence pages for communication with ICANN.

See: RALO Confluence Pages

• AFRALO ALS Confluence pages
• APRALO ALS Confluence pages
• EURALO ALS Confluence pages
• LACRALO ALS confluence pages
• NARALO ALS confluence pages

4.2(c)

Make available to ALSes the use of an Adobe Connect Room.

See: RALO Adobe Connect Rooms

• · AFRALO ALS Adobe Connect Room
• · APRALO ALS Adobe Connect Room
• · EURALO ALS Adobe Connect Room
• · LACRALO ALS Adobe Connect Room
• · NARALO ALS Adobe Connect Room

4.3

Externaloutreachandrecruitment.

4.3(a)

Request that selected At-Large members be funded to attend

non-ICANN meetings (e.g., the IGF, the Consumer Electronics Show (CES), etc.).

The ALAC made this request in FY11, FY12, and FY13. FY11 and FY12 requests were not accepted; FY13 request is still being evaluated.

This request is supported by the fact that At-Large should constitute an essential part of ICANN's global outreach process.

4.3(b)

Request that the ALAC be invited and funded to participate in all outreach programs launched by ICANN.

In accepting such invitations, the ALAC should be given the option to send At-Large members as representatives who are located within the region of the specific outreach event. This request is supported by the fact that At-Large should constitute an essential part of ICANN's global outreach process.

4.3(c)

The aim of the At- Large is to have at least one ALS in every country.

Allocated to the At-Large Outreach Sub- Committee. To accomplish this task, the At-Large will use outreach items such as teleconferences, webinars, promotional materials; and invitations to various meetings and events.

4.3(d)

Recommend that each RALO start an individual member program.

Allocated to the Director for At-Large and the RALO Leaders.

4.3(e)

Continue collaborating with ICANN

Communications on Beginner’s Guides devoted to topics relevant to At-Large.

See: ICANN's e-learning page

Allocated to the ICANN Communications Department, ALAC Chair, Executive Committee, Director for At-Large, and RALO leaders.

The goal should be to produce one Guide for each ICANN Public Meeting.

In close collaboration with ICANN Communications, At-Large has already co-produced a Beginner’s  Guide to Domain Names and Beginner’s Guide to  Internet Protocol (IP) Addresses.

Future Beginner’s Guides include “Participating in ICANN” and “CyberSavvy.”

4.3(f)

Recommend to the RALOs that they formalize their outreach/“inreach” role in whatever way each finds appropriate (e.g., by including in their Rules of Procedure).

Allocated to the Director for At-Large and the RALO Leaders.

ExplorewhetheradditionalmeasuresneedbetakentoinvolveindividualInternetusersinAt‐Largework,wheretheywishtocontributeintheirpersonalcapacities.

AllocatedtothePolicyStaffinsupportoftheALAC,At-LargeRulesofProcedureWorking Group,RegionalLeadership,RALOs,andotherrelevantpartiestoensurethatthesystemisinteractivewithICANNwideactivities.

Internalleadershipengagementanddevelopment.

Increase significantly the ALAC’s creation of “inreach” materials aimed at leadership engagement and development throughout At-Large (including brochures, radio programs, podcasts, webinars, and online videos).

For purposes of encouraging continued engagement of ALSes, this task has been allocated to the standing committee of the ALAC on Inreach

4.5(b)

Create job descriptions for ALAC members, liaisons and other At-Large leaders that include qualification requirements, responsibilities and objective criteria for performance evaluation.

Allocated to the At-Large Rules of Procedure  Working Group and the At-Large Metrics Working  Group.

4.5(c)

Create and implement a transparent sanctions process for nonperformance of ALAC, RALO, and ALS

members.

Allocated to the At-Large Rules of Procedure  Working Group and the At-Large Metrics Working  Group.

4.5(d)

In collaboration with ICANN’s Nominating Committee (NomCom), create a process for the midterm replacement, both of NomCom appointments to the ALAC and of ALAC appointments to the NomCom.

Allocated to the At-Large Rules of Procedure  Working Group.

IdentifybarrierswithinALACprocessesusedtocontributetostrategicplanningandproposefollow‐up.

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.1(a)

Ratify the strategic planning process reflected in the flowchart titled “Figure C-1: Proposed At-Large Strategic Planning Process.”

See: At-Large Policy Development Page See: Figure C-1

5.1(b)

Review and amend the ALAC’s strategic planning process yearly, in line with annual amendments to ICANN’s overall Strategic Plan.

See: At-Large Policy Development Page

See: ICANN Strategic and Operating Plan Process

5.1(c)

Conduct periodic “SWOT” (strengths, weaknesses, opportunities and threats) analyses of the At-Large strategic planning process, in conjunction with the RALOs and compare the results of these analyses to identify areas that have improved or deteriorated.

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

See: At-Large Work Team C SWOT Analysis 1-3  Workspace

5.1(d)

Articulate the ALAC’s and At-Large’s vision and mission.

See: ALAC/At-Large Vision Statement

See: ALAC vote results endorsing the At-Large  Visions Statement as Proposed by the At-Large  Improvements Taskforce.

5.1(e)

Use appropriate metrics to ensure that the ALSes are diverse, effective and well informed.

See: ALAC Metrics Sub-Committee

Allocated to the Metrics Sub-Committee and the ALAC as a whole.

• The Global Diversity of At-Large ALSes is clearly shown through this map:  http://www.atlarge.icann.org/maps/
• RALO ALSes: AFRALO ALSes, APRALO ALSes,  EURALO ALSes, LACRALO ALSesNARALO ALSes
• RALO Brochures: AFRALO Brochure, APRALO  Brochure, EURALO Brochure, LACRALO  Brochure, NARALO Brochure

5.1(f)

Initiate, develop and maintain an institutional knowledge management and retention system for At-Large.

Allocated to Policy Staff in support of the ALAC and At-Large Members as past and present Members of the ALAC and At-Large Community and will be required to integrate with required future ICANN wide systems.

5.1(g)

Encourage the five RALOs to coordinate their outreach and “inreach” policies in order to facilitate the search for new skill sets needed within At-Large.

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large Director for At-Large, and RALO leaders.

5.1(h)

Continue actively pursuing At-Large growth, for ICANN’s overall benefit.

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.1(i)

When requesting ALAC outreach project funding, the ALAC emphasizes their role not only as a strategic resource benefiting the ALAC and RALOs but also as part of a wider ICANN legitimacy process.

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.1(j)

Continue to encourage ICANN to prioritize & increase funding for outreach.

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.2

IdentifybarrierswithinALACprocessesusedtocontributetooperationalplanningandproposefollow‐up.

5.2(a)

Ratify the operational and financial planning process reflected in the flowchart titled “Figure C-3: Proposed At-Large Operational and Financial Planning Process.”

The ALAC has determined that, for this action item to be effective, it must be performed on a recurring schedule.

The item has been completed previously in February 2012. Each January, the ALAC and Policy Staff in support of the ALAC have will consider when it should be next repeated by the At-Large community.

See: Figure C-3

5.2(b)

Acknowledge and encourage a continuation of the better collaboration between the ALAC and ICANN’s Finance Staff seen in preparing the FY2012 Budget.

This proposal is in addition to the fact that most At- Large operational planning is done by Policy Staff in support of the ALAC.

5.2(c)

Conduct periodic “SWOT” (strengths, weaknesses, opportunities and threats) analyses of the At-Large operational and financial planning process, in conjunction with the RALOs (as WT C did), and compare the results of these analyses to identify areas that have improved or deteriorated.

See: At-Large Improvement WT C SWOT Analysis

In the first SWOT analysis conducted by WT C, the main barriers to operational and financial planning were identified as the ALAC’s being slow to react; translation processes being slow, and translations not being available for all documents; the ALAC members’ potential conflicts of interest; a lack of travel funding, putting At-Large in a second-class tier; and not enough informational materials for the ALSes.

5.2(d)

Formalize the process by which the ALAC collects operational demands from the RALOs and includes them in its operational plans.

See: At-Large Policy Development Page

5.2(e)

Clearly estimate and document the time required for the ALAC’s operational processes (e.g., responding to a call for Public Comments) and use these estimates to formalize its operational processes.

The Director for At-Large has consulted with the ICANN Staff responsible for the implementation of the Public Comment Enhancements regarding Recommendation 8 of the ALAC/At-Large Improvements Implementation Project. Following discussion between the Director for At-Large, the ALAC Chair and the Chair of the ALAC/At-Large Improvements Taskforce, the ALAC confirmed its understanding that the guidelines for Public Comments recognize flexibility in extending the Public Comment period beyond the minimum requirements. The ALAC may, on a case-by-case basis, request extensions of 5, 10, 15, 21 or 30 days (in exceptional circumstances). Such requests will be made directly to the Staff person responsible for the specific Public Comment period thereby notifying them that the ALAC intends to submit a comment. The ALAC further requests that a Staff response to such requests for an extension to a Public Comment period be granted or denied in an expeditious manner. If the request is denied, the ALAC may use its right to submit advice to the ICANN Board as per the ICANN Bylaws.

We note that the ATRT implementation process  includes the following relevant text: 

16. Publicnoticeandcommentprocessesshouldprovideforbotha distinct “Comment” cycle and a “Reply Comment” cycle that allows community respondents to address and rebut arguments raised in opposing parties’ comments.

17. Aspartofimplementingrecommendations15and16,timelinesforpublicnoticeandcommentshouldbereviewedandadjustedtoprovideadequateopportunityformeaningfulandtimelycomment.CommentandReplyCommentperiodsshouldbeofa fixed duration.  

The ALAC and its Improvements Taskforce established that the ALAC Chair, the ALAC Executive Committee and the Director for At-Large will continue to monitor this issue and will provide input to the Senior Director for Participation and Engagement and the Board PPC.

5.2(f)

Continue requesting face-to-face funded general assemblies (GAs) for each RALO every three years and an At-Large Summit.

See: At-Large Event Roadmap

The Events Roadmap has been submitted to ICANN Finance for their review.

5.2(g)

Continue to assist the RALOs in completing their annual ICANN requests for funding, as needed, in terms of writing, packaging and advocacy.

The item has been completed previously in February 2012. Each January, the ALAC and Policy Staff in support of the ALAC have will consider when it should be next repeated by the At-Large community.

ReviewongoingPolicyStaffinsupportoftheALAClevelsandbudgetallocationsandincreasesupportasprovidedthroughoutthisproject,consistentwiththerecommendationsinFinalReport.

AllocatedtotheALACChairandtheDirectorforAt-Large.

5.3(a)

Continue to monitor its level of needed Policy Staff in support of the ALAC and ICANN’s commitment to and progress in filling open

positions.

As of September 2011, all allotted positions for Policy Staff in support of the ALAC had been filled.

5.3(b)

The ALAC and Policy Staff in support of the ALAC should develop an annual support agreement

This task is no longer relevant due to the following changes within ICANN in recent years (i.e., since submission of the ALAC Review Final Report). An increase in Policy Staff in support of the ALAC (as of September 2011, all allotted positions for Policy Staff in support of the ALAC had been filled.

6.1

ReviewofadditionalAt‐Largeinformationthatwouldbeuseful,subsequenttoimprovementsinfinancialreporting.

See: ALAC Subcommittee on Finance and Budget

Encourage the same high level of input into ICANN’s annual financial planning from ALSes & RALOs.

Allocated to the ALAC Finance and Budget Sub- Committees Working Group.

Continue to assist the RALOs in completing their annual ICANN requests for funding (writing, advocacy, & packaging)

The item has been completed previously in February 2012. Each January, the ALAC and Policy Staff in support of the ALAC have will consider when it should be next repeated by the At-Large community.

Continue to monitor the accommodations given to At-Large members at Meetings to ensure they are equal to those of others.

Allocated to the Executive Committee.

7.1

ReviewofcommunicationandcollaborationneedsconsideredunmetbyALSesandRALOsglobally.

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

Introduce to the ALSes selected information- dissemination, communication and collaboration tools (such as Posterous, Twitter Twibes, mobile-device compatibility) and provide training.

See: At-Large Technology Taskforce Tools  Workspace

Conduct a survey of ALSes regarding communication & collaboration tools.

See: At-Large Structure 2010 Survey Workspace

7.2

ReviewoftechnologiesusedbyAt‐LargeandacrossICANNthatcouldfillallorsomeofthe7.1needsoftheALSesandRALOs.

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

Establish a Technology Task Force (TTF) of community members that will periodically review the appropriateness of available technology, train RALOs/ALSes in new technologies, and possibly staff a help desk.

Allocated to the Technology Taskforce, its continuous progress will be supervised by the Policy Staff in support of the ALAC.

7.3

ReviewofavailabletechnologiesnotalreadyusedbyAt‐LargeorelsewhereinICANNthatcouldfillthe7.1needsoftheALSesandRALOs.

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.4

CreateandconductimplementationplanfortrainingICANN'sITSupportinthe7.3technologies(and,asneeded,inkeepingITSupportcurrentin 7.2technologies).

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.5

BasedonAt‐Large'schoiceofthecommunicationandcollaborationtoolstobestfillitsneeds,makeneededrecommendations foruse,ornot,ofthesetoolsacrossICANN.

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.6

Createandconductimplementationplanfortheperiodicidentificationoftechnologies,eithernewlyintroducedtothemarketorupdated,thatcanbetterfillthe7.1needsoftheALSesandRALOsthanthosetechnologiescurrentlybeing used.

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

8.1

DevelopanALACprocessforrequestingextendedconsultationwindow.

The Director for At-Large has consulted with the ICANN Staff responsible for the implementation of the Public Comment Enhancements regarding Recommendation 8 of the ALAC/At-Large Improvements Implementation Project. Following discussion between the Director for At-Large, the ALAC Chair and the Chair of the ALAC/At-Large Improvements Taskforce, the ALAC confirmed its understanding that the guidelines for Public Comments recognize flexibility in extending the Public Comment period beyond the minimum requirements. The ALAC may, on a case-by-case basis, request extensions of 5, 10, 15, 21 or 30 days (in exceptional circumstances). Such requests will be made directly to the Staff person responsible for the specific Public Comment period thereby notifying them that the ALAC intends to submit a comment. The ALAC further requests that a Staff response to such requests for an extension to a Public Comment period be granted or denied in an expeditious manner. If the request is denied, the ALAC may use its right to submit advice to the ICANN Board as per the ICANN Bylaws.

We note that the ATRT implementation process  includes the following relevant text:

16.Publicnoticeandcommentprocessesshouldprovideforbotha distinct “Comment” cycle and a

“ReplyComment”cyclethatallowscommunityrespondentstoaddressandrebutargumentsraisedinopposingparties’comments.

17.Aspartofimplementingrecommendations15and16,timelinesforpublicnoticeandcommentshouldbereviewedandadjustedtoprovideadequateopportunityformeaningfulandtimelycomment.CommentandReplyCommentperiodsshouldbeofa fixed duration.

The ALAC and its Improvements Taskforce established that the ALAC Chair, the ALAC Executive Committee and the Director for At-Large will continue to monitor this issue and will provide input to the Senior Director for Participation and Engagement and the Board PPC.

8.1(a)

Ratify the process reflected in the flowchart titled “Figure D-1: How the ALAC Should Request an Extension to a Public Comment Period.”

See: Figure D-1

8.1(b)

Request that extensions to Public Comment periods be allowed of any length up to 30 additional days (see “A” on Figure D-1).

See: Figure D-1

See: 8.1(a) Notes Section

8.2

DevelopICANNStaffandBoardprocessforimplementingextensionrequests.

8.2(a)

Request that any extension to a Public Comment period be granted or denied within an expeditious manner (see “B” on Figure D-1).

See: Figure D-1

8.3

ReviewofPublicCommentprocesses.

8.3(a)

Recommend the establishment of a Policy Scheduling Team (PST), consisting of ICANN Staff, to coordinate the opening of Public Comment periods.

The ALAC will be reviewing its policy scheduling policy to include a Standing Committee as opposed to a PSC.

The PST should:

• Be comprised of an ICANN Staff member assigned to each SO/AC and the Language Services Manager; and
• Maintain a publicly available Policy Comment Schedule (PCS), which tracks upcoming Public Comment periods, in order to (a) avoid many such periods opening around the same time, (b) allow the ACs and SOs to better plan their time and (c) allow better planning for needed translations.  (For each upcoming Public Comment period, the PCS should Include the policy name, a synopsis, the responsible AC or SO, and tentative opening date.)

8.3(b)

Establish a standing committee, the ALAC/At-Large Policy Review Committee (PRC), responsible for advising the ALAC of actions needed regarding upcoming PCs policy issues, as well as policy issues not on the PCs but of At-Large interest.

See: Figure D-2

The ALAC will be reviewing its scheduling policy to include a Standing Committee as opposed to a PSC. The specific responsibilities of the PRC should include advising the ALAC as early as possible of:

• ALAC comments needed in response to upcoming Policy Comment periods;
• At-Large community briefings, documentation or translations needed for upcoming Policy Comment periods;
• The degree of interest that the RALOs and ALSes have in the ALAC’s submitting comments during Policy Comment periods;
• Issues and other concerns relevant to end users that are noton the PCs but that RALOs and ALSes are interested in bringing to ICANN’s attention.

In order to perform its function, the PRC should be comprised of:

• The Chair and Secretariat of each RALO;
• At least two more members from each RALO;
• The ALAC Rapporteur; and
• The ALAC Liaisons to the various ACs, SOs and cross-constituency WGs.

ReviewmeasurestomakepolicydevelopmentactivitiesacrossICANN's communitiesmoreaccessible.Proposemeasuresforcommunityreview.

9.1

Interimmeasures(nearterm).

ThistaskisnolongerrelevantduetoimprovementsinICANN’stranslationservicessincetheALACReviewFinalReportandtheimminentreleaseofICANN’snewLanguageServicesPolicy.  Responsibility for this watching brief has been allocated to the Executive Committee.

Build into At-Large’s consideration of ICANN policy issues (open Policy Forums) more and earlier translation of relevant materials.

This task is no longer relevant due to improvements in ICANN’s translation services since the ALAC Review Final Report and the imminent release of ICANN’s new Language Services Policy.

Responsibility for this watching brief has been allocated to the Executive Committee.

9.2

Adoptionofa Translation Policy.

See:ALACStatementontheDRAFT- ICANN LanguageServicesPolicyandProcedures

See:At-LargePolicyDevelopmentPage

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

Review ICANN’s new Language Services Policy (once available) and request that Policy Staff in support of the ALAC do the same, focusing on At-Large needs, particularly related to ICANN policy issues.

See: 9.2 Notes section

9.3

ImplementationofTranslationPolicy(byPublicParticipationCommittee).

See: 9.2 Notes section

10.1

TheALACistheprimaryICANNhomeforthevoiceandconcernsoftheindividualInternetuser.

See: ICANN Public Comment - Proposed ICANN  Bylaw Revisions Regarding the ALAC

The At-Large Advisory Committee (ALAC) is the primary organizational home within ICANN for individual Internet users. The role of the ALAC shall be to consider and provide advice on the activities of ICANN, insofar as they relate to the interests of the individual Internet users. This includes policies created through ICANN’s Supporting Organizations, as well as the many other issues for which community input and advice is appropriate. The ALAC, which plays an important role in ICANN’s accountability mechanisms, also coordinates some of ICANN's outreach to individual Internet users.

Submit to the Board the following revision to ICANN Bylaws  XI.2.4.a, drafted in collaboration with ICANN Legal.

See: 10.1 Notes section

12.1

At‐Largeoutreachtoconsumerrepresentatives.

See: At-Large Consumer Document 2012  Workspace which includes a copy of the document entitled “ICANN and the At-Large Community: Join us to Help Protect Consumers on the Internet”.

Allocated to the Policy Staff in support of the ALAC, ALAC, Regional Leadership, ALSes, and other relevant parties to ensure that the system is able to cope with the changing landscape of the consumer issues

Create and maintain a consumer outreach document for use by At-Large in its outreach efforts aimed at getting consumer organizations involved in ICANN.

See: At-Large Consumer Document 2012  Workspace

See: WT D’s proposed consumer recruitment document, Defending Consumers on the Internet.

12.2

GNSOoutreachtoconsumerrepresentatives.

Interaction with other ICANN Processes

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

13.1

ReviewtheALAC's/At‐Large'sPolicyAdviceDevelopmentprocessesandproposemeasurestoreducebarriers.

Ratify the process reflected in the flowchart titled “Figure D-1: How the ALAC Should Request an Extension to a Public Comment Period” by which the ALAC could request that a Public Comment (PC) period be extended.

See: ICANN Public Participation Committee See: Figure D-1

Establish a standing committee, the ALAC/At-Large Policy Review Committee (PRC), responsible for advising the ALAC of actions needed regarding upcoming PCS policy issues, as well as policy issues not on the PCS but of At-Large interest. The working of the PCS is depicted in the flowchart titled “ALAC/At-Large Complete

13.1(b)

Request that extensions to Public Comment periods be allowed of any length up to 30 additional days (see “A” on Figure D-1).

This sub-task was superseded as it subject to change in ICANN's Public Participation Committee.

See: Figure D-1

13.1(c)

Request that any extension request to a Public Comment period be granted or denied within 24 hours (see “B” on Figure D-1).

This sub-task was superseded as it subject to change in ICANN's Public Participation Committee.

See: Figure D-1

13.1(d)

Recommend the establishment of a Policy Scheduling Team (PST), consisting of ICANN Staff, to coordinate the opening of Public Comment periods.

The Policy Staff provide one another with weekly updates on the policy updates of the ACs/SOs that they each support.

The PST should:

• Be comprised of an ICANN Staff member assigned to each SO/AC and the Language Services Manager; and
• Maintain a publicly available Policy Comment Schedule (PCS), which tracks upcoming Public Comment periods, in order to (a) avoid many such periods opening around the same time, (b) allow the ACs and SOs to better plan their time and (c) allow better planning for needed translations. (For each upcoming Public Comment period, the PCS should Include the policy name, a synopsis, the responsible AC or SO, and tentative opening date.)

13.1(e)

Establish a standing committee, to be known as the ALAC/At-Large Policy Review Committee (PRC), which will be responsible for advising the ALAC of any and all actions needed regarding upcoming PCs policy issues, as well as policy issues not on the PCS but of At- Large interest.

See: At-Large Meeting with ASO See: Figure D-2

The working of the PCS is depicted in the flowchart titled “ALAC/At-Large Policy Review Committee (PRC)” (see Figure D-2).

The specific responsibilities of the PRC should include advising the ALAC as early as possible of:

• ALAC comments needed in response to upcoming Policy Comment periods;
• At-Large community briefings, documentation or translations needed for upcoming Policy Comment periods;
• The degree of interest that the RALOs and ALSes have in the ALAC’s submitting comments during Policy Comment periods; and
• Policy issues (and other concerns) relevant to end users that are noton the PCS but that the RALOs and ALSes are interested in bringing to ICANN’s attention. In order to perform its function, the PRC should be comprised of:
• The Chair and Secretariat of each RALO;
• At least two additional representatives from each RALO;
• The ALAC Rapporteur; and
• The ALAC Liaisons to the various ACs, SOs and cross-constituency WGs.

13.1(f)

Ratify the process reflected in the flowchart titled “ALAC/At-Large Policy Advice Development (PAD) Process” (shown in Figures D-3, D-4 and D-5), by which the ALAC could systematically respond to Public Comment periods.

See: Figure D-3 See: Figure D-4 See: Figure D-5

This flowchart represents a comprehensive, flexible, systematic process that would replace the At-Large Policy Advice Development  process currently in use.

If the final comment is ratified, the ALAC requests the Policy Staff in support of the ALAC, to transmit the comment to the ICANN Staff person responsible for the Public Comment period.

13.2

Strengthenpolicy‐developmentprocesseswithintheSOsandACsforrequestingandconsideringtheALAC’sinput.

As part of the GNSO’s reviewandrevisionofits  PolicyDevelopmentProcess(PDP)during the last year, it now regularly requests and considers the ALAC’s input;

• ThestandingALACLiaisontotheccNSOandtheccNSOliaisontotheALACnowensurethattheALAC’sinputisregularlysoughtandconsideredintheccNSO’sPDP;and

• TheASOPDP,viatheRIRs,isalreadyopentopublicinput.

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

Review current processes in each of the ACs/SOs.

Responsibility for this watching brief has been allocated to the Executive Committee.

Develop recommendations to make relevant changes for community consideration.

Responsibility for this watching brief has been allocated to the Executive Committee.

13.3

ProcessesbetweenSOs,ACsandtheBoardneedtobedeveloped/strengthenedtoprovidefeedbackonhowtheALAC’sadvicehasbeenconsideredandused.

ThisRecommendationisnolongerrelevantas:

• A strengthening of AC/SO communication, including a mailing list and regular AC/SO call.
• TheactionsofICANN
• GrowthinCross-CommunityWorkingGroupssuchastheDSSA
• ThistaskisalreadyspecificallyaddressedbyRecommendation7 of the Final RecommendationsoftheAccountabilityand TransparencyReviewTeam(ATRT).

13.4

EnsuretheGNSOPDPincorporatesmeasureswhichguaranteeALACinputisrequested,included,andconsideredintegraltotheprocess.

• AspartoftheGNSO’sreviewandrevisionofits PolicyDevelopmentProcess(PDP)duringthelastyear,itnowregularlyrequestsandconsiderstheALAC’sinput.

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

13.5

EnsuretheccNSOPDPincorporatesmeasureswhichguaranteeALACinputisrequested,included,andconsideredintegraltotheprocess.

ThestandingALACLiaisontotheccNSOandtheccNSOliaisontotheALACnowensurethattheALAC’sinputisregularlysoughtandconsideredintheccNSO’sPDP

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

13.6

EnsuretheASOPDPincorporatesmeasureswhichguaranteeALACinputisrequested,included,andconsideredintegraltotheprocess.

TheALACanditsImprovementsTaskforceestablishedthattheongoingresponsibilityforthistaskwillbedisseminatedamongsttheALACChair,theExecutiveCommittee,theDirectorforAt-Large,andRALOleaders.