Content Comparison

...

Proposed Agenda: 

Notes and Action Items

1. Welcome and roll call

Adobe connect list as member present. No one on audio only

2. Background

Specific concerns around Contract Co. two submissions explicit alternate proposals ( ALAC and AUDA)

Purpose of Sub-working group

Develop alternate proprosal to "Franfurt Proposal"

Approach to taks at hand 

Relationship to RFP 3

Convenient to ue same terminology, however be mindful of evolution. Comment, MRT could be like a new Supporitng Organization. IANA function to be overseen by similar committee like curent Nominating Committee. 

Start with alternative for Contract Co.

Steve Crocker: 4 pieces to puzzle

1. What mechanism should be in place
2. lack of clarity around what IANA Function is.  IAAN Function is clerical function. Not policy decision. Decision to make delegation or redelgation is outside. This is tool to make 
3. lack of clarity of what seperation. Decision to make what goes into root zone are made by ICANN, is it meaningful if clerical is outside 
4. what are criteria to make judgement of seperation

Question what is minimal proposal to male this work

Interterpretation of IANA Function Contract: (Intended) Clear seperation between policy decision and clerical action 

Upstream decision should not be interpreted as IANA decision

Resistance to perception that IANA is operational. and what are for example new gTLDs is policy decision. Use IANA operational function as leverage of policy function. 

Policy development

• Judgement within policy
• Decision on Amozon or Vine are policy decision ( value decision). IANA porcess after decisions. 
• Independence from the Board: there should be some group that has unfettered access to function, alternate to nomCom, root signing process. Group could be CSC like. 
• Seperation discussion is revisti of discussion 15 years ago. Signal for ICANN Board to look into calls for seperation
• Need for clean and clear distinction between policy and execution/operation. Policy defintion is blurred band blurs dicussion. Start with clear defintion of IANA Fuction.
• Focus discussion on ALAC and Auda propsoal as starting point ( one variant)
• Comment Becky: IAP and other items are reflection of not getting at policy execution and not at operations on the other hand. Focusing on operations is starting point.
• Comment AG on ALAC proposal: need for more details are needed to meet requirement of RFP 3 requred by ICG.ALAC proposal principles far more important then details 

. 

What should be focus of RFP 3b

• Greg Shatan, coordinator RFP 3: Focusing on alternate approach without Contract Co, may ultimately change way how MRT and CSC are viewed. By focusing on all directly would slow down process overall. 
• Suggestion is to focus first on alternate for Contract Co and contract. Short term viable discussion on alternate of Contract Co.
• Steve Crocker: Is focus on non-contracting co?  this will not address core of the problem

• Greg shatan: start agasin with functional discussion. Structure folows function

• Start of functional analysis: After understanding what IAN Functions are: detemine specific risks/issues.( what if IANA does not follow instruction) or does not perform well, then look for mitigating measures.

• The risks are in area of decision making area. The decisions should be out of IANA. After transition this should be clarified. 

• Background for agenda and proposal, based on comment and issues with raised in public comments focus on Contract Co. or go back ground work.

• Suggestion by taking out Contract Co. as mechanism problem can be redefined, and mitigating

• Duty to investigate all proposal and understanding ramifications of these proposals. Understanding benefits and down side, to inform the ccTLD and gTLD operators to make a reasoned decision. 

• Issue is where an by whom will be examination be done. RFP 4 should do stress stest and understand ramifications. Purpose of RFP 3b is to build proposal that is build aournd alternative proposal RFP 3b. Functional analysis includes 3 aspects: clar about IANA Function , role of NTIA in relation to IAN Function and functional alternate to Contract Co

Proposal for functional analysis

- ICANN performs IANA function under contract, what is alternate?

Auda proposal

- Elements not to be addressed by this group (less relevant), such as CSC and MRT aspects, or rebid process.

Current naming function operation done well. Naming function, is narrow this focuses approach. Contract Co  approach is too broad. "Nuclear option", although caues may be highly unlikley they should be developed. Analogy an dprinciple are similar to relation betweeen Auda and Austalian government. Sugested approach soemthing like "golden bylaw" Defintion of power

Singular difference: a single government overseeing. This differnce should drive to a differnt type of solution. 

Resolve issue what is discussed in one group or another

If something goes wrong, first step is to have a discussion. Further if something goes really wrong, there will uproar and as a results in changes, next step is to secure  

No single government argument

Focus must be actual fucntions and incentive to make it work, and reduce the risk of capture to capturing it.

Need to define parameters the IANA Function needs to be performed and what will happen if not preformed adequately.

Need to take have a look functions again

Action Allan: look with staff at functional analysis to be presented to the group

 Specific reason for creation of this group: come up with a proposal without contract Co an dcontract. as alternative 

 Next call to accomodate those whose who are in Frankfurt

Transcript

Transcript RFP3B 14 Jan 2015.doc

...