At-Large Ad-hoc WG on the Transition of US Government Stewardship of the IANA Function 2014-11-26

At-Large Ad-hoc WG on the Transition of US Government Stewardship of the IANA Function 

Date: Wednesday, 26 November  2014      

Time: 13:30 UTC - 15:00 UTC (for the time in various timezones click here)

---

How can I participate in this meeting?   English Conference ID = 1638      

¿Cómo se puede participar en la teleconferencia? Spanish Conference ID = 1738

Adobe Connect room: https://icann.adobeconnect.com/iana-issues/

---

Action Items:  EN     

Recording: EN , ES

Adobe Connect Chat Transcript: EN

Transcription:  EN and   ES  

---

Participants: 

EN: Olivier Crepin-Leblond, Eduardo Diaz, Gordon Chillcott, Cheryl Langdon-Orr, Seun Ojedeji, Yasuichi Kitamura, Leon Sanchez, Jean Jacques Subrenat, Alan Greenberg, Christopher Wilkinson, Tomorhio Fujisaki, Tom Lowenhaupt, Glenn McKnight,

ES: Fatima Cambronero, Aida Noblia, Alberto Soto

Apologies: Tijani Ben Jemaa, Mohamed El Bashir

Staff: Heidi Ullrich, Terri Agnew

Interpreter:   Veronica

Call Management: Terri Agnew

---

A G E N D A:  

1. Introduction Roll Call, adoption of Agenda (Olivier Crépin-Leblond - 4 minutes)

2. Review of Action Items from the meeting of 24 November 2014 (Olivier Crépin-Leblond - 1 minute)

3. Review of ICG Activities - (Jean Jacques Subrenat; Mohamed El Bashir - 10 minutes)

Announcement of more IANA Coordination Group Calls

Next IANA Coordination Group Call - Wednesday 26 November 2014 02:00-03:00 UTC

4. Review of other Operational Community Progress (All, 10 minutes)

Updates and Status of the different communities IANA Proposal Development 

• RIRs
  • RIPE 69 
    
• IETF
  At-Large ICANN Evolution Working Group

5. Follow-up to IANA CWG Face-to-Face Meeting (Meeting #7 & Meeting #8) (19-20 November) (All - 60 minutes)

a. Review of Flow Chart

1. Review of IANA Periodic Review Team
2. Review of IANA Contracting Entity
3. Review of First Draft of Document from CWG (to be linked when published)

b. Important Questions

1. NTIA Backstop Function - should it be retained?
2. Contracting Function:
   1. limited term for the contract (3, 5, 8, 10 years?)
   2. open and transparent contest involving a RFP every time?
   3. is there a presumption that the contract be renewed by default?
3. Link with the Accountability Process? How do we want this?
   Do we support:
   
   "The transition must not take place until:
   

   1. the requisite accountability mechanisms have been identified by the CWG on Enhancing ICANN Accountability (“Accountability CCWG”),

   2. mechanisms that the community determines are necessary pre-transition have been put in place and

   3. agreements and other guarantors are in place to ensure timely implementation of mechanisms that the Accountability CCWG decides may be implemented post-transition". 

c. RFP4 / RFP5

1. CWG-RFP4 - Transition Implications
   1. progress update
   2. Meeting #1 CWG RFP4 (25 November)
2. CWG-RFP5 - NTIA Requirements (validation of)
   

   1. Consultations within Communities that have taken place to date

6.  AoB - 5 minutes

For reference (meeting structure & working groups)

• IANA CWG Face-to-Face Meeting (Meeting #7 & Meeting #8) (19-20 November)

• DAY 1: IANA CWG Meeting #7 Face to Face - Frankfurt (19 November)
  • Introduction, Review of Agenda, Timeline & Principles (08:45 - 10:40 local time)
  • Review of 1, 2A, 2B (11:00 - 13:00 local time)
  • RFP 3 (14:00 - 15:40 local time)
  • RFP 3 (16:00 - 18:00 local time)
  • Additional RFP3 Session (19:30 - 21:30 local time)
• DAY 2: IANA CWG Meeting #8 Face to Face - Frankfurt (20 November)
  • RFP3 (8:00 -9:40 local time)
• • RFP3 continued (10:00 – 12:45 local time)
  • Way Forward for RFP 4 (13:45 - 15:25 local time)
• • Update / Revisit RFP 1, 2A, 2B & Schedule for the day (15:45 - 17:00 local time)
• Wrap Up Session & Review of Action Items (17:00 - 18:00 local time)

For reference (documents):

• Current Drafts  (includes Principles, RFP1, 2A, etc.)
• Resulting Flow Chart of the groups to be created  <<= FLOW CHART USED ON CALL

Older work

• Current Drafts of documents being developed
• Principles & Criteria Document (Probably Complete)
• [Archive] Work Item Sub Groups
  • CWG-RFP1-2A-2B (Seun Ojedeji, Fouad Bajwa, Olivier Crépin-Leblond) 
  • CWG-RFP2C - Existing, Pre-Transition Arrangements, NTIA IANA Functions Contract Triage (Eduardo Diaz) 
  • CWG-RFP3 - Proposed Post-Transition Oversight and Accountability Arrangements (Eduardo Diaz, Fouad Bajwa, Olivier Crépin-Leblond) 
  • STRAWMAN MATRIX DRAFT – FOR DISCUSSION PURPOSES ONLY 13-NOV-2014
  • Strawman matrix
    • Meeting #1 CWG-RFP3 (6 November 2014)
    • Meeting #2 CWG-RFP3 (12 November 2014)
    • Meeting #3 CWG-RFP3 --Special Session on RFP3 (convened at 15:30 UTC on 13 November 2014)
    • (work continued in Frankfurt F2F meeting)
      

Core At-Large RFP3 Work

• • • RFP3 Strawman Matrix (Initial PDF Document)
    • RFP3 Strawman Matrix (Google DOC evolving document includes Strawman 4)
    • Results of IANA Issues WG & ALAC Poll
      • 16 responses from IANA Issues WG members (include completed & partial ones)
      • 7 responses from non-IANA Issues WG members
      • pdf copy of the survey 

 

More References: Meetings of the CWG to Develop an IANA Stewardship Transition Proposal on Naming Related Functions

• IANA CWG Meeting #1 (6 October)
• IANA CWG Meeting #2 (13 October)
• IANA CWG Meeting #3 (22 October) 
• IANA CWG Meeting #4 (30 October) 
• IANA CWG Meeting #5 (4 November)
• IANA CWG Meeting #6 (13 November) 
• IANA CWG Meeting #7 (19 & 20 November)   
• IANA CWG Meeting #9 (27 November) << NEXT MEETING

• At-Large Positions

• http://la51.icann.org/en/schedule/tue-atlarge-iana-stewardship
• At-Large Ad-hoc WG on the Transition of US Government Stewardship of the IANA Function 2014-10-14 Los Angeles
• Notes from IANA Issues WG brainstorming in Los Angeles DOCX / PDF
• Notes from the Flip Chart

  • Post transition Safeguards

  • Performance metrics accomplished regularly

  • Response strategies

  • Risk management matrix

  • How do we recognize satisfaction

  • Confidence in root zone

  • Continuity of allocation of IP addresses and fairness

  • No change to current IP policies

  • Keep processes that work - do not change them

  • Creation of another oversight body