Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Rec.

Sub-Task

ImplementationTask

Status

Notes

7.1

 

ReviewofcommunicationandcollaborationneedsconsideredunmetbyALSesandRALOsglobally.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

 

7.1(a)

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

Complete

See: At-Large Technology Taskforce Tools  Workspace

 

7.1(b)

Conduct a survey of ALSes regarding communication & collaboration tools.

Complete

See: At-Large Structure 2010 Survey Workspace

7.2

 

ReviewoftechnologiesusedbyAt‐LargeandacrossICANNthatcouldfillallorsomeofthe7.1needsoftheALSesandRALOs.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

 

7.2(a)

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.

Complete

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.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.4

 

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

7.2technologies).

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.5

 

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

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.6

 

Createandconductimplementationplanfortheperiodicidentificationoftechnologies,eithernewlyintroducedtothemarketorupdated,thatcanbetterfillthe7.1needsoftheALSesandRALOsthanthosetechnologiescurrentlybeing used.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

 

...

7.6

...

 

...

used.

...

Complete

...

 

 

 

...

 

...

 

...

 

...

 

...

 

Rec.Sub-Task Implementation Task Status Notes

8.1

 

DevelopanALACprocessforrequestingextendedconsultationwindow.

Complete

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.”

Complete

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).

Complete

See: Figure D-1

 

See: 8.1(a) Notes Section

8.2

 

DevelopICANNStaffandBoardprocessforimplementingextensionrequests.

Superseded

 

 

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).

Superseded

See: Figure D-1

8.3

 

ReviewofPublicCommentprocesses.

Complete

 

 

 

...

 

 

8.3(a)

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

Complete

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.

Complete

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.

...

 

 

 

...

8.4  

ReviewmeasurestomakepolicydevelopmentactivitiesacrossICANN's

communitiesmoreaccessible.Proposemeasuresforcommunityreview.

CompleteSee:8.1Notessection

 

 

 

Rec.Sub-Task Implementation Task Status Notes

9.1

 

Interimmeasures(nearterm).

WatchingBrief

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

 

9.1(a)

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

Watching Brief

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.

WatchingBrief

See:ALACStatementontheDRAFT- ICANN LanguageServicesPolicyandProcedures

 

See:At-LargePolicyDevelopmentPage

 

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

 

9.2(a)

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.

Watching Brief

See: 9.2 Notes section

9.3

 

ImplementationofTranslationPolicy(byPublicParticipationCommittee).

WatchingBrief

See: 9.2 Notes section

 

 

 

 

Rec.Sub-Task Implementation Task Status Notes

10.1

 

TheALACistheprimaryICANNhomeforthevoiceandconcernsoftheindividualInternetuser.

Complete

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.

 

10.1(a)

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

Complete

See: 10.1 Notes section

 

 

Rec.Sub-Task Implementation Task Status Notes

11.

...

1

 

StatementfromtheICANNBoardthatclearlyrecognizesAt‐LargeasprimaryICANNhomeofindividualInternetusersandclarifiesrelationshipbetweentheALACand  GNSO's User Home.

Complete

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 Public Comment - Proposed ICANN  Bylaw Revisions Regarding the ALAC

 

11.1(a) 

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

 

See: 11.1 Notes section

 11.1(b)

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

Complete

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

 

See: 1.1(b) Notes section

 

 

 

 

 
Rec.Sub-Task Implementation Task Status Notes

 

drafted in collaboration with Legal:

 

12.1

 

At‐Largeoutreachtoconsumerrepresentatives.

Complete

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

 

12.1(a)

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

Complete

See: At-Large Consumer Document 2012  Workspace

 

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

12.2

 

GNSOoutreachtoconsumerrepresentatives.

Watching Brief / Ongoing Interaction with other ICANN

Processes

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

 

 

Rec.Sub-Task Implementation Task Status Notes

13.1

 

ReviewtheALAC's/At‐Large'sPolicyAdviceDevelopmentprocessesandproposemeasurestoreducebarriers.

Complete

 

 

13.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” by which the ALAC could request that a Public Comment (PC) period be extended.

Complete

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

...

 

 

 

 

 

 

Comment (PC) period be extended.

 

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).

Superseded

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).

Superseded

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.

Complete

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.

Complete

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;

 

 

...

 

...

 

...

policy issues not on the PCS but of At- Large interest.

...

 

  • · 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.

Complete

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.

Superseded

/ Watching Brief

· 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.

 

13.2(a)

Review current

...

Superseded

...

Responsibility for this watching brief has been

 

 

 

 

...

 

processes in each of the ACs/SOs.

...

/Watching Brief

Superseded

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

 

13.2(b) 

Develop recommendations to make relevant changes for community consideration.

Superseded

/ Watching Brief

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

13.3

 

ProcessesbetweenSOs,ACsandtheBoardneedtobedeveloped/strengthenedtoprovidefeedbackonhowtheALAC’sadvicehasbeenconsideredandused.

Superseded

/ Watching Brief

ThisRecommendationisnolongerrelevantas:

13.4

 

EnsuretheGNSOPDPincorporatesmeasureswhichguaranteeALACinputisrequested,included,andconsideredintegraltotheprocess.

Superseded

/ Watching Brief

 

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

13.5

 

EnsuretheccNSOPDPincorporatesmeasureswhichguaranteeALACinputisrequested,included,andconsideredintegraltotheprocess.

Superseded

/ Watching Brief

ThestandingALACLiaisontotheccNSOandtheccNSOliaisontotheALACnowensurethattheALAC’sinputisregularlysoughtandconsideredintheccNSO’sPDP

 

ResponsibilityforthiswatchingbriefhasbeenallocatedtotheExecutiveCommittee.

13.6

 

EnsuretheASOPDPincorporatesmeasureswhichguaranteeALACinputisrequested,included,andconsideredintegraltotheprocess.

Complete

TheALACanditsImprovementsTaskforceestablishedthattheongoingresponsibilityforthistaskwillbedisseminatedamongsttheALACChair,theExecutiveCommittee,theDirectorforAt-Large,andRALOleaders.