About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

Re: [ca-tf] Draft pre-read document for the CA-TF workshop of 13February

  • To: Leo Vegoda <
    >
  • From: Róbert Kisteleki <
    >
  • Date: Thu, 15 Feb 2007 10:31:26 +0100
  • Cc: Henk Uijterwaal <
    >,
  • Organization: RIPE NCC


And this is where the problem lies. If the RIPE NCC provides a CA outsourcing service then it significantly reduces the need for network people to be involved in the certificate renewal. But by reducing this need it risks a deterioration in contact information when registrants' internal communications are less than exemplary.
During the renewal process, we can also define a step between acknowledgment of payment and the actual renewal of the certificate, where we ask the LIR to confirm contact information details. This could be coupled with other steps, like "check the bill and the contact information attached, and pay if okay", but it might be better to separate the two. Anyway, the idea is that _before_ renewal, we ask for confirmation from the LIR, which IMHO does not slow down the process significantly.

Cheers,
Robert



 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community