Public Comment CloseStatement
Name 

Status

Assigned Working Group

Assignee(s)

Call for
Comments Open
Call for
Comments
Close 
Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number

22 March 2021

ADOPTED

13Y, 0N, 0A

OFB-WG

03 March 2021

17 March 2021

17 March 2021

21 March 2021

22 March 2021

AL-ALAC-ST-0321-01-00-EN

Hide the information below, please click here 

FINAL VERSION SUBMITTED (IF RATIFIED)

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 



FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

The ALAC appreciates the opportunity to comment on the IANA Naming Function Review: Recommendation for IANA Naming Function Contact Amendment as drafted by the IANA Naming Function Review Team.

The ALAC encouraged the ICANN Board to fulfil their initial report recommendations in our response to the IANA Naming Function Review (IFR) Initial Report, and as this Contract Amendment is recommendation #4 of the report, we support it.

Please note that ALAC support for this proposed contract amendment is premised on our acceptance of the IFRT's rationale that it seeks to remove a now operational impracticality arising from a legacy statement from the NTIA contract (i.e., to eliminate redundancy).



DRAFT SUBMITTED FOR DISCUSSION

The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).

The ALAC appreciates the opportunity to comment on the IANA Naming Function Review: Recommendation for IANA Naming Function Contact Amendment.

The ALAC encouraged the ICANN Board to fulfil their initial report recommendations, and as this Contract Amendment is recommendation #4 of the report, we support it.

3 Comments

  1. ALAC appreciates the opportunity to comment on the IANA Naming Function Review: Recommendation for IANA Naming Function Contact Amendment. As we encouraged the ICANN Board to fulfil their initial report recommendations, and being recommendation number 4 of the report  this Contract Amendment, we support it.

      1. As it stands, it's not clear who the they is in "their initial report recommendations".
      2. Could we have the source for the phrase, "As we encouraged the ICANN Board to fulfil ...."?  Are there prior statements that we can refer or hyperlink to?
      3. Most importantly, isn't our support for this proposed contract amendment premised on our acceptance of the IFRT's rationale that it seeks to remove a now operational impracticality arising from a legacy statement from the NTIA contract (i,e, to eliminate redundancy)?

      Thanks.

  2. Thank you Justine, yes, it should mention the IANA Naming Function Review Team, as it was their initial report the one we supported. As per the hyperlink, it might be added a link to our IFRT Initial Report comment. And Finally, yes, our support to the amendment implies a support in the change of the contract based in the actual redundancy.