Re: [ca-tf] Next steps & Write-up of the CA-TF kick-off meeting

[Leo Vegoda <]

On Feb 28, 2007, at 2:32 AM, Martin Papik wrote:

> I totally agree, we need clear goals or we're doomed. Some of the  
> goals are listed below (in random order). Please add anything I  
> left out. And not all need to be a part of this project. Right now  
> we need to clarify what this project will be about, what we're  
> going to put a chunk of our lives into.
>
> The actual goals:
>
> * Better accuracy of data regarding IP address allocations
> * Legal accountability of IP address usage
> * Increased routing security
The system in place now reports the last known information held for  
the 'registrant'. That doesn't really scale to an Internet with tens  
of thousands of ASs. It is also unlikely to provide the legal  
certainty needed by resource holders in an age of scarcity. If we  
move to a certification system it needs to certify that the  
certificate holder has a right to use the resources that are  
certified. Whoever controls the certificate needs to be able use it  
to assure other people that they can authorise the use of the  
resources and the transfer of the resources.

I think that means that accurate registration data, legal  
accountability and better routing security should follow  
automatically from a system with a hard certification of a right to  
use resources.


> Supportive goals:
>
> * design/build infrastructure, both technical (CA, protocols, etc)  
> and non technical (policies, procedures) to support the  
> certification process
> * document policies, procedures, typical examples (small ISP, large  
> telco, multinational company, etc.)
> * make it a viable option for everybody
> * make it a desired choice for most
> * educate people why they want it (even they've never heard of it,  
> especially)
> * decide on data validity hierarchy (e.g. WHOIS supplemented by  
> certificates or vice versa)
> * do a case study of what segment of resource holders would  
> cooperate, which would not and why (for both answers if possible)
> * design the transition between the current state and the desired  
> end result
> * consider technical implications and requirements (data  
> availability, fault tolerance, data access)
> * consider non-technical implications and requirements (legal  
> responsibility, disputes, penalties, changes to existing  
> procedures, question of IP address ownership/sale)
> * eat a lot of good lunches and dinners in good company, have fun  
> and be merry
These are all god goals.

Regards,

--
Leo Vegoda
IANA Numbers Liaison