SSAC Advisory Concerning the Mitigation of Name Collision Risk (R-1)

Date IssuedDocumentReference IDCurrent Phase

  

SSAC Advisory Concerning the Mitigation of Name Collision Risk (R-1)SAC062

CLOSED



  1. Phase 1 Receive
  2. Phase 2 Understand
  3. Phase 3 Evaluate
  4. Phase 4 Implement
  5. Phase 5 Close
  6. Closed



Description:

ICANN should work with the wider Internet community, including at least the IAB and the IETF, to identify:

  1. what strings are appropriate to reserve for private namespace use, and
  2. what type of private namespace use is appropriate (i.e., at the TLD level only or at any additional lower level)


STATUS UPDATES

DatePhaseTypeStatus Updates

 

ClosedPhase ChangeThis Advice Item is now Closed

 

Phase 5Board UpdateResolved (2021.05.12.08), the Board finds that ICANN org has implemented all of SAC062's Recommendations, and considers SAC062 to be completed. See full resolution at https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b. Board Rationale for Recommendation 1: Recommendation 1 on Special-Use Domain Names recommended that ICANN org should work with the wider Internet community, including at least the Internet Architecture Board (IAB) and the Internet Engineering Task Force (IETF), to identify (1) what strings are appropriate to reserve for private namespace use and (2) what type of private namespace use is appropriate (i.e., at the TLD level only or at any additional lower level). ICANN org attempted to update RFC 6761 through the IETF process. The Domain Name System Operations (DNSOP) Working Group raised awareness on its work in this area by organizing a webinar entitled, "IETF Overview and Special-Use Domain Names Problem Statement" held on 23 May 2017. Despite these efforts, this subject was unable to gain momentum in the DNSOP Working Group. OCTO's (Office of the Chief Technical Officer, ICANN org) attempts at working with the wider Internet community failed to achieve consensus on how to move forward with updating Request For Comment (RFC) 6761, despite OCTO's direct involvement.

 

Phase 5Phase UpdateMatt Larson sent a letter to Rod Rasmussen advising that SAC062 is complete (https://www.icann.org/en/system/files/correspondence/larson-to-rasmussen-13jan21-en.pdf). SAC062’s Recommendation 1 called for ICANN org to work with the wider Internet community, including the Internet Architecture Board (IAB) and the Internet Engineering Task Force (IETF), to identify what strings are appropriate to reserve for private namespace use and what type of private namespace use is appropriate (i.e., at the top-level domain [TLD] level only or at any additional lower level). Members of OCTO worked diligently in an attempt to update RFC 6761 (Special-Use Domain Names) through the IETF process, but were unable to gain traction in the DNSOP Working Group. OCTO requested closing this recommendation because the wider Internet community was not able to achieve consensus on how to move forward with updating RFC 6761, despite OCTO’s efforts.

 

Phase 5Phase ChangeNow in Phase 5: Close

 

Phase 4Phase UpdateThe OCTO Research group will continue its work (already in progress) in the IETF dnsop (DNS Operations) Working Group on specifying a process to reserve “special use” names. This effort will update RFC6761, “Special-Use Domain Names”. These special-use domain names correspond to the “strings…appropriate to reserve for private namespace use” in the recommendation from SAC062 that is the focus of this document.

 

Phase 4Phase ChangeNow in Phase 4: Implement

 

Phase 3Phase UpdateOn 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b).

 

Phase 3Board UpdateResolved (2017.06.24.19), the Board adopts the SSAC recommendations outlined in the document titled "Implementation Recommendations for SSAC Advice Documents SAC062, SAC063, SAC064, SAC065, SAC070, and SAC073 (08 June 2017) [PDF, 433 KB]", and directs the CEO to implement the advice as described in the document. See full resolution at (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b). SAC062 Rec 1 proposed solution: The Office of the CTO Research group will continue its work (already in progress), including providing data and analysis to the community, the IAB, and the IETF DNSOP (DNS Operations) Working Group, to inform discussions relating to the process of reserving “special use” names. These special-use domain names correspond to the “strings [. . .] appropriate to reserve for private namespace use” in the recommendation from SAC062 that is the focus of this document.

 

Phase 3Phase ChangeNow in Phase 3: Evaluate & Consider

 

Phase 4Board UpdateBoard consideration is complete and implementation of advice item is ongoing. Status provided in 19 October 2016 letter from ICANN Board Chair to SSAC Chair (https://www.icann.org/en/system/files/correspondence/crocker-to-faltstrom-19oct16-en.pdf). The ICANN Board passed a resolution on 21 Nov 2013 that, "directs ICANN's President and CEO to have the advice provided in SAC062 evaluated,” (https://www.icann.org/resources/boardmaterial/resolutions-2013-11-21-en#2.d). ICANN staff will continue to work with the wider internet community on this issue in the context of the IETF.

 

Phase 4Phase ChangeNow in Phase 4: Implement

 

Phase 1Phase UpdateSSAC published SAC062: SSAC Advisory Concerning the Mitigation of Name Collision Risk: https://www.icann.org/en/system/files/files/sac-062-en.pdf.