From mschepers at gmail.com Thu Oct 12 11:30:44 2006 From: mschepers at gmail.com (Menno Schepers) Date: Thu, 12 Oct 2006 11:30:44 +0200 Subject: [ca-tf] test 123 Message-ID: <20061012093044.GA13115@milliways> this is a test From mschepers at gmail.com Thu Oct 12 12:02:32 2006 From: mschepers at gmail.com (Menno Schepers) Date: Thu, 12 Oct 2006 12:02:32 +0200 Subject: [ca-tf] This is a test menno Message-ID: <20061012100231.GA13609@milliways> test From mschepers at ripe.net Thu Oct 12 12:23:23 2006 From: mschepers at ripe.net (Menno Schepers) Date: Thu, 12 Oct 2006 12:23:23 +0200 Subject: [ca-tf] This is mschepers@ripe.net test Message-ID: <452E179B.6080607@ripe.net> -- Kind regards, Menno Schepers -- Menno Schepers | mschepers at ripe.net RIPE NCC | Support Technician From mschepers at gmail.com Thu Oct 12 12:27:18 2006 From: mschepers at gmail.com (Menno Schepers) Date: Thu, 12 Oct 2006 12:27:18 +0200 Subject: [ca-tf] This is mschepers@ripe.net test In-Reply-To: <452E179B.6080607@ripe.net> References: <452E179B.6080607@ripe.net> Message-ID: <1b6081210610120327t31a1fa2ob7631845c8fc1b48@mail.gmail.com> Test once more again sometimes. On 10/12/06, Menno Schepers wrote: > > > -- > Kind regards, > > Menno Schepers > > -- > Menno Schepers | mschepers at ripe.net > RIPE NCC | Support Technician > > -- Met vriendelijke groeten, Menno Schepers -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.ripe.net/ripe/mail/archives/ca-tf/attachments/20061012/35128fb5/attachment.html From mschepers at gmail.com Thu Oct 12 12:39:21 2006 From: mschepers at gmail.com (Menno Schepers) Date: Thu, 12 Oct 2006 12:39:21 +0200 Subject: [ca-tf] Test message from gmail Message-ID: <1b6081210610120339s3e68d337w950c487555b5fd0c@mail.gmail.com> test -- Met vriendelijke groeten, Menno Schepers -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.ripe.net/ripe/mail/archives/ca-tf/attachments/20061012/ff768b73/attachment.html From henk at ripe.net Tue Oct 24 08:06:12 2006 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Tue, 24 Oct 2006 08:06:12 +0200 (CEST) Subject: [ca-tf] 1st draft of a charter Message-ID: 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 ------------------------------------------------------------------------------