[Gnso-rds-pdp-3] lets get started

[Arsène Tungali]

Hi David and all,

I would like to first apologize for missing the call today. I connected like 20 minutes later and i was told by AC that the meeting hasn't started.

Just for info, i only joined the RDS discussions last week and directly came into this request for breakdown groups and decided to join. So, i have a lot to catch up with the work so far and the whole concept.

I have quite no knowledge of the CA stuffs so will likely be learning here, hoping i will be useful at some point.

With regards to the definition bellow on CA, i tend to agree with part of it until where i am wondering why we need to collect ALL data from the registrant. 

I am one of those who believe we should not collect registrants' data at all.

Thanks,
Arsene

-----------------
Arsène Tungali,
about.me/ArseneTungali
+243 993810967
GPG: 523644A0
Goma, Democratic Republic of Congo

Sent from my iPhone (excuse typos)

> On Oct 17, 2017, at 4:07 PM, Deacon, Alex <Alex_Deacon at mpaa.org> wrote:
> 
> FWIW I was a founding engineering at Verisign (the first commercial CA) and worked there from 1995-2010 – so I’ll do my best to represent current interests of commercial CAs – and can reach out to those in the industry if necessary. 
>  
> Agree that we should do as much as we can via email.   The CAB forum guidelines will probably shed some light as to what may be required DNS/WHOIS-wise.
>  
> Alex
>  
>  
>  
> From: <gnso-rds-pdp-3-bounces at icann.org> on behalf of David Cake <dave at davecake.net>
> Date: Tuesday, October 17, 2017 at 4:47 AM
> To: "gnso-rds-pdp-3 at icann.org" <gnso-rds-pdp-3 at icann.org>
> Subject: [Gnso-rds-pdp-3] lets get started
>  
> The first meeting, unfortunately, only two of us attended, so we cancelled it. 
>  
> We will try for another meeting later in the week, but we can’t wait until then to get started, as our 
> ‘m hoping to kick off discussion with this email. 
>  
> Our goal is to produce, over the next week and a bit, roughly two pages or so of definition of DNS Certification as a purpose for RDS data and access. 
>  
> We might want to start by expanding the definition very carefully, specifying the who and why at every stage.
>  
> We might want to expand the use cases in detail, for example looking at the different types of DNS certification, and which data is necessary for each, and being specific about the data required. 
> We might want to look at alternatives to accessing RDS data. 
>  
> I don’t think we have anyone on this call who works for a CA. The closest we probably have is some people from EFF (Jeremy’s employer) are involved in the Lets Encrypt project, and might be able to help us with some technical questions. I know some of the technical issues related to Certification a bit, but only some. We should expect that some of our work may change in detailed discussion with a CA technical expert, but that is no reason not to get started. 
>  
> The EWG report includes this definition, which we might want to consider as a bare minimum starting point
> Tasks within the scope of this purpose include a Certification Authority (CA) issuing an X.509 certificate to a subject identified by a domain name. To accomplish this task, the user needs to confirm that the DN is registered to the certificate subject; doing so requires access to all public and gated data about the Registrant.
>  
> Which parts of that do we agree with, which deserve further consideration?
>  
> David
>  
> _______________________________________________
> Gnso-rds-pdp-3 mailing list
> Gnso-rds-pdp-3 at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-3
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-3/attachments/20171017/c92fd0eb/attachment-0001.html>