From henk at ripe.net Fri Nov 10 02:30:53 2006 From: henk at ripe.net (Henk Uijterwaal) Date: Fri, 10 Nov 2006 02:30:53 +0100 Subject: [ca-tf] Charter version 2. Message-ID: <4553D64D.10403@ripe.net> Dear All, Please find below version 2 of the charter. Please comment, Henk -------- Original Message -------- Date: Thu, 2 Nov 2006 14:35:16 +0100 (CET) From: henk at ripe.net (Henk Uijterwaal) To: henk at ripe.net Certification of Resources Authority TF (CA-TF) (Draft Charter, version 2.0). 1. Introduction =============== Resource certification is seen as a reliable method for proving the association between resource holders (RIRs, LIRs, ISPs and end entities) and Internet resources (in this context: IPv4 and IPv6 address blocks, and AS numbers). There could be a number of advantages of resource certification, once such a system is introduced: * The resource holders have proof that they hold a certain Internet resource * The resource holders are able to make attestations about resources when delegating (assigning) them to other entities * The resource certificates could be used in securing routing information (either through IRR, *BGP or other means) * The resource certificates can serve as "proof of possession" when doing resource trades between entities Such a system is envisioned to be based on accepted and open standards such as X.509 and RFC3280. It potentially also includes RIR policy changes, and new services provided by the RIRs to their members. The Regional Internet Registries - based on their communities' authorization - are currently exploring the consequences of providing a certification system. The RIPE NCC wishes to inform the RIPE Community about these efforts and obtain guidance from it about providing such a service in the RIPE region. The RIPE Community wishes to raise awareness within the community and provide guidance to the RIPE NCC. A Task force was established at RIPE 53 in Amsterdam to advise, review, and provide feedback about a certification system. 2. Charter ========== This task force shall: * Raise awareness about this issue among network operators. * Solicit and collect requirements and opinions about such a service. * Follow and advise the RIRs joint work on the subject, especially in relation with RIPE NCC. * Evaluate and review the anticipated technical, policy and business relation changes between LIRs and RIRs. * Produce a report on its work. The report will include, but is not limited to: * Usefulness of number resource certification in general. * Business implications of a number resource certification service for resource holders * General and specific requirements for a number resource certification service * Implications of such a service for number resource policies * Expected uptake of such a service among resource holders The task force shall have completed its task when this report is published _AND_ * a resource certification (prototype) system is in place and operational, and the corresponding technical, policy and related questions and implications are clearly seen, _OR_ * there is a consensus within the RIPE community that RIPE NCC shall not provide resource certification services. The task force shall be disbanded when these tasks have been completed or when there is consensus within RIPE that completion of the tasks is no longer realistic. 3. Time-Line ============ RIPE 53 - Nov'06: Proposal to establish the Task Force. RIPE 54 - May'07: Publish a progress report and discuss the outcomes of the work done so far. - Sep'07: Publish a report RIPE 55 - Oct'07: Discuss work done. Evaluation and potential disbanding of the Task Force. 4. Practicalities ================= The task force will organise its own business, such as appointing chairpersons or spokespersons. The RIPE NCC will provide secretariat services such as mailing lists and support staff. Upon request by the task force, the RIPE NCC will provide briefings, information material and prototype software that may help the task force to solicit and compile input from the RIPE Community. The mailing list for the task force is: ca-tf at ripe.net Public archives are available at: http://www.ripe.net/ripe/maillists/archives/ca-tf/2006/index.html -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ I can't believe grown engineers are afraid of a dot. (Ed Lewis) -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ I can't believe grown engineers are afraid of a dot. (Ed Lewis)