AT-LARGE GATEWAY

At-Large Website

ALAC

RALOs

At-Large Regional Policy Engagement Program (ARPEP)

At-Large Governance

At-Large Reports

Policy Comments & Advice

Working Groups

ICANN Meetings

At-Large Summit (ATLAS III)

At-Large Review Implementation Plan Development

ALAC and RALO Elections, Selections, and Appointments

At-Large Priority Activities - 2021

IMPORTANT: Please note the (topic or scorecard title) in your comments.

Subsequent Procedures Scorecards

  1. Applicant Support Program, v8 settled 13 Sep 2020, replacing Applicant Support Program, v7 settled 5 May 2020
  2. Application Change Request, v2 settled 15 Sep 2020, replacing Application Change Request, v1 settled 7 May 2020  
  3. Role of Application Comment, v1 settled 7 May 2020
  4. String Similarity, v2 settled 7 May 2020
  5. Universal Acceptance, v4 settled 27 May 2020
  6. Internationalized Domain Names, v4 settled 28 May 2020
  7. Security and Stability, v2 settled 28 May 2020
  8. Name Collision, v2 settled 28 May 2020 
  9. Reserved Names, v3 settled 15 Sep 2020, replacing Reserved Names, v2 draft, 8 Jun 2020
  10. Community Applications, v5 draft, 22 Sep 2020 replacing Community Applications, v4 draft, 10 Jun 2020
    1. At-Large Interventions on CBA and CPE, 11 Jun 2020
    2. Revised CPE Guidelines - A Proposal by At-Large, 11 Jun 2020
  11. Continuing Subsequent Procedures, v3 settled 8 Jul 2020
  12. Geonames, v2 draft, 15 Sep 2020 based on Geonames, v2 indicative, 19 Aug 2020
  13. Conflicts of Interest, v1 settled 3 Sep 2020
  14. Applicant Guidebook, v1 draft, 7 Sep 2020
  15. Communications, v1 draft, 7 Sep 2020
  16. Systems, v1 draft, 7 Sep 2020
  17. Fees, v3 draft, 13 Sep 2020
  18. Applications Assessed in Rounds, v5 draft, 14 Sep 2020
  19. GAC Advice & GAC Early Warning, v1 draft, 14 Sep 2020
  20. Objections, v1 draft, 14 Sep 2020
  21. Registrant Protections, v2 draft, 15 Sep 2020 

See also (23 Sept CPWG Meeting): Google Doc for Metrics for the New gTLD Program - regarding Topic 7 - Metrics & Monitoring.

Go to: SubPro Updates Workspace for other Updates to Issues/Topics under Deliberation by the SubPro PDP WG
For a progress report see: At-Large Scorecard Topic List, 22 Sep 2020

  • No labels

1 Comment

  1. Gopal Tadepalli

    Universal Acceptance [UA] is a fundamental requirement for a truly multilingual and digitally inclusive Internet. DNS is in the application layer. A huge plus in Distributed Computing is "Location Transparency". UA is subtly anti-theistic to this goal of designing applications that happen anywhere. UA is another way of indicating traceability.

    I suggest two parameters for scoring:

    1. Web Scriptability
    2. Incident Responsiveness and Manageability

    A good parameter to have on the score card is "Web Scriptability".

    A Case in Point: A headless browser is a web browser without a GUI. They can Perform DDOS attacks on web sites, Increase advertisement impressions and Automate web sites in unintended ways. Google Chrome and Firefox are headless browsers.

    People use tags to aid classification, mark ownership, note boundaries, and indicate online identity. IMHO, UA at present is on the lines of "tags" in vernacular languages well adapted to the UNICODE. It is still a "metadata" that can be used in programming.

    IMHO, Another parameter to have on the score card is "Incident Responsiveness and Manageability".

    An incident may enable quick traceability to a "Local Geography (small footprint)" but its maximum impact may be elsewhere. 

    Hope this helps.

    Gopal T V