[ca-tf] 1st draft of a charter

Dear All,

Please find below a first shot at a charter for this group.  Please
comment,

Robert & Henk

- - - -

Certification of Resources Authority TF (CA-TF)
(Draft Charter)

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.

As the Regional Internet Registries - based on their communities'
authorization - explore the consequences of such a certification system,
a task force was established at RIPE 53 in Amsterdam to advise, review,
and provide feedback about the proposed solution.

2. Charter

This task force shall:

  * raise awareness about this issue among network operators,
  * 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.

The task force shall have completed its task when:

  * 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 and discuss the outcomes of the work done so
                  far.

RIPE 55 - Oct'07: Report of the work done. Evaluation and potential
                  disbanding of Task Force.

4. Workplan

The group will meet primarily via email.  The RIPE NCC will provide
regular reports on the work done in this area as a starting point for
discussion.

5. Practical

  * Mailing list: ca-tf at ripe.net (closed list)
  * Public archives: http://....



------------------------------------------------------------------------------
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
------------------------------------------------------------------------------