November 2017 - Gnso-rds-pdp-3

DT3 job done
by David Cake Nov. 16, 2017

Nov. 16, 2017

Though some of the other Drafting Teams are not quite done yet, Drafting Team 3 has submitted its work and there is no reason to think we will be doing more at this time. So thanks for all of your contributions, especially Alex. Myself and the leadership team appreciate it. Of course see you in the main group discussion etc. David

1 0

Re: [Gnso-rds-pdp-3] [EXTERNAL] Re: finishing report
by David Cake Nov. 13, 2017

Nov. 13, 2017

I made only one major change - removing the link to the EWG definition, which I think we all agree is flawed, and I felt was redundant now. The only other change I made was turning website into web site. Thank you all for your efforts. David > On 12 Nov 2017, at 10:15 am, Feher, Kal <Kalman.Feher(a)team.neustar> wrote: > > Sorry for my delayed response, I've been traveling to IETF. > > I think the document is complete. I don't have any further changes. > > Kal Feher > > > From: "Deacon, Alex" <Alex_Deacon(a)mpaa.org <mailto:Alex_Deacon@mpaa.org>> > Date: Saturday, 11 November 2017 at 06:15 > To: Kal Feher <kalman.feher(a)team.neustar <mailto:kalman.feher@team.neustar>>, "gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>>, David Cake <dave(a)davecake.net <mailto:dave@davecake.net>> > Subject: Re: [EXTERNAL] Re: [Gnso-rds-pdp-3] finishing report > > Thanks Kal. > > Apologies for the typo’s and auto-correct issues – I was in a rush to send it out. > > Anyway - Here is one more update on top of yours with a few more mods to the purpose up front. It now states. > > Purpose: > Information collected by a certificate authority to enable contact between the registrant, or a technical or administrative representative of the registrant, to assist in verifying that the identity of the certificate applicant is the same as the entity that controls the domain name. > > Alex > > > From: "Feher, Kal" <Kalman.Feher(a)team.neustar <mailto:Kalman.Feher@team.neustar>> > Date: Thursday, November 9, 2017 at 5:52 PM > To: "Deacon, Alex" <Alex_Deacon(a)mpaa.org <mailto:Alex_Deacon@mpaa.org>>, "gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>>, David Cake <dave(a)davecake.net <mailto:dave@davecake.net>> > Subject: Re: [EXTERNAL] Re: [Gnso-rds-pdp-3] finishing report > > Please note that none of my emails to the subgroup mailing list have been received for some reason. > > I've made some minor edits to the purpose. I fixed up a recurring typo for "identity". I replaced domain ownership with "control". That is the term used by CAs and the baseline guidelines. Ownership is not determined in this method. Bearing in mind that certificate requests could be delegated to hosting operators. With that minor and slightly pedantic change, I think the purpose is fine. If we wanted to be really pedantic then it would be "authorised control" as it appears in the certificate guideline glossary. > > I disagree with adding the organisation field in the data elements. They are not required by Certificate Authorities and the guidelines are quite clear on this. This includes guidelines for basic certs (the domain control part of the baseline guide), organisation validated certs (domain control plus org validation from baseline guidelines) and extended validation certs (domain control from baseline plus the EV guidelines). As I stated in the f2f, the only thing the CAB forums use the RDS for is to contact the registrant/admin/tech contact to prove authorised control. RDS is not used to prove organisation identity. If a CA chose to do this, they'd actually be less secure and increase risks of fraudulent certificate validation. > > Kal Feher > Neustar Inc. > Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 > Office +61 3 9866 3710 / kal.feher(a)team.neustar <mailto:kal.feher@team.neustar> / www.neustar.biz <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protect…> > > Follow Neustar: <image001.png> Facebook <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protect…> <image002.png> LinkedIn <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protect…> <image003.png> Twitter <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protect…> > The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message. > > > From: <gnso-rds-pdp-3-bounces(a)icann.org <mailto:gnso-rds-pdp-3-bounces@icann.org>> on behalf of "Deacon, Alex" <Alex_Deacon(a)mpaa.org <mailto:Alex_Deacon@mpaa.org>> > Date: Friday, 10 November 2017 at 07:03 > To: "gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>> > Subject: [EXTERNAL] Re: [Gnso-rds-pdp-3] finishing report > > Here is my “Post Abu Dhabi” update. I added a “purpose in one sentence” up top and then beefed up the data elements section to bring it in line with what other groups have done. > > Thanks! > Alex > > > From: <gnso-rds-pdp-3-bounces(a)icann.org <mailto:gnso-rds-pdp-3-bounces@icann.org>> on behalf of "Deacon, Alex" <Alex_Deacon(a)mpaa.org <mailto:Alex_Deacon@mpaa.org>> > Date: Tuesday, November 7, 2017 at 10:47 AM > To: David Cake <dave(a)davecake.net <mailto:dave@davecake.net>>, "gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>> > Cc: thomascovenant <dinasolveig(a)thomascovenant.org <mailto:dinasolveig@thomascovenant.org>> > Subject: Re: [Gnso-rds-pdp-3] finishing report > > I’ll take a shot at an update and send a revision on Thursday for review. > > Aelx > > > From: <gnso-rds-pdp-3-bounces(a)icann.org <mailto:gnso-rds-pdp-3-bounces@icann.org>> on behalf of David Cake <dave(a)davecake.net <mailto:dave@davecake.net>> > Date: Tuesday, November 7, 2017 at 10:08 AM > To: "gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org <mailto:gnso-rds-pdp-3@icann.org>> > Cc: thomascovenant <dinasolveig(a)thomascovenant.org <mailto:dinasolveig@thomascovenant.org>> > Subject: [Gnso-rds-pdp-3] finishing report > > The DT3 report is due to be completed this friday. > I have not scheduled a meeting, as previous discussion suggested there were only minor changes needed and it could be performed via email. > > I have attached the report as presented - please suggest revisions and updates that you feel would make the report clearer. > > David > > > > > _______________________________________________ > Gnso-rds-pdp-3 mailing list > Gnso-rds-pdp-3(a)icann.org <mailto:Gnso-rds-pdp-3@icann.org> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.o… <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense…><image001.png><image002.png><image003.png>

2 1

Re: [Gnso-rds-pdp-3] [EXTERNAL] Re: finishing report
by Deacon, Alex Nov. 10, 2017

Nov. 10, 2017

Thanks Kal. Apologies for the typo’s and auto-correct issues – I was in a rush to send it out. Anyway - Here is one more update on top of yours with a few more mods to the purpose up front. It now states. Purpose: Information collected by a certificate authority to enable contact between the registrant, or a technical or administrative representative of the registrant, to assist in verifying that the identity of the certificate applicant is the same as the entity that controls the domain name. Alex From: "Feher, Kal" <Kalman.Feher(a)team.neustar> Date: Thursday, November 9, 2017 at 5:52 PM To: "Deacon, Alex" <Alex_Deacon(a)mpaa.org>, "gnso-rds-pdp-3(a)icann.org" <gnso-rds-pdp-3(a)icann.org>, David Cake <dave(a)davecake.net> Subject: Re: [EXTERNAL] Re: [Gnso-rds-pdp-3] finishing report Please note that none of my emails to the subgroup mailing list have been received for some reason. I've made some minor edits to the purpose. I fixed up a recurring typo for "identity". I replaced domain ownership with "control". That is the term used by CAs and the baseline guidelines. Ownership is not determined in this method. Bearing in mind that certificate requests could be delegated to hosting operators. With that minor and slightly pedantic change, I think the purpose is fine. If we wanted to be really pedantic then it would be "authorised control" as it appears in the certificate guideline glossary. I disagree with adding the organisation field in the data elements. They are not required by Certificate Authorities and the guidelines are quite clear on this. This includes guidelines for basic certs (the domain control part of the baseline guide), organisation validated certs (domain control plus org validation from baseline guidelines) and extended validation certs (domain control from baseline plus the EV guidelines). As I stated in the f2f, the only thing the CAB forums use the RDS for is to contact the registrant/admin/tech contact to prove authorised control. RDS is not used to prove organisation identity. If a CA chose to do this, they'd actually be less secure and increase risks of fraudulent certificate validation. Kal Feher Neustar Inc. Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / kal.feher(a)team.neustar / www.neustar.biz<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.neustar…> Follow Neustar: [ttp://neunet.neustar.biz/sites/default/files/295/New%20Picture.png] Facebook<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.faceboo…> [ttp://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(1)(1).png] LinkedIn<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedi…> [ttp://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(2).png] Twitter<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter…> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message. From: <gnso-rds-pdp-3-bounces(a)icann.org<mailto:gnso-rds-pdp-3-bounces@icann.org>> on behalf of "Deacon, Alex" <Alex_Deacon(a)mpaa.org<mailto:Alex_Deacon@mpaa.org>> Date: Friday, 10 November 2017 at 07:03 To: "gnso-rds-pdp-3(a)icann.org<mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org<mailto:gnso-rds-pdp-3@icann.org>> Subject: [EXTERNAL] Re: [Gnso-rds-pdp-3] finishing report Here is my “Post Abu Dhabi” update. I added a “purpose in one sentence” up top and then beefed up the data elements section to bring it in line with what other groups have done. Thanks! Alex From: <gnso-rds-pdp-3-bounces(a)icann.org<mailto:gnso-rds-pdp-3-bounces@icann.org>> on behalf of "Deacon, Alex" <Alex_Deacon(a)mpaa.org<mailto:Alex_Deacon@mpaa.org>> Date: Tuesday, November 7, 2017 at 10:47 AM To: David Cake <dave(a)davecake.net<mailto:dave@davecake.net>>, "gnso-rds-pdp-3(a)icann.org<mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org<mailto:gnso-rds-pdp-3@icann.org>> Cc: thomascovenant <dinasolveig(a)thomascovenant.org<mailto:dinasolveig@thomascovenant.org>> Subject: Re: [Gnso-rds-pdp-3] finishing report I’ll take a shot at an update and send a revision on Thursday for review. Aelx From: <gnso-rds-pdp-3-bounces(a)icann.org<mailto:gnso-rds-pdp-3-bounces@icann.org>> on behalf of David Cake <dave(a)davecake.net<mailto:dave@davecake.net>> Date: Tuesday, November 7, 2017 at 10:08 AM To: "gnso-rds-pdp-3(a)icann.org<mailto:gnso-rds-pdp-3@icann.org>" <gnso-rds-pdp-3(a)icann.org<mailto:gnso-rds-pdp-3@icann.org>> Cc: thomascovenant <dinasolveig(a)thomascovenant.org<mailto:dinasolveig@thomascovenant.org>> Subject: [Gnso-rds-pdp-3] finishing report The DT3 report is due to be completed this friday. I have not scheduled a meeting, as previous discussion suggested there were only minor changes needed and it could be performed via email. I have attached the report as presented - please suggest revisions and updates that you feel would make the report clearer. David _______________________________________________ Gnso-rds-pdp-3 mailing list Gnso-rds-pdp-3(a)icann.org<mailto:Gnso-rds-pdp-3@icann.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.o…<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense…>

1 0

finishing report
by David Cake Nov. 9, 2017

Nov. 9, 2017

The DT3 report is due to be completed this friday. I have not scheduled a meeting, as previous discussion suggested there were only minor changes needed and it could be performed via email. I have attached the report as presented - please suggest revisions and updates that you feel would make the report clearer. David

2 2

Any changes?
by David Cake Nov. 1, 2017

Nov. 1, 2017

Our report seemed relatively well received on Saturday, I think people appreciated that we had looked at the issues in detail. Based on feedback and questions from those in the room, do you think there are any changes we should make before the meeting on Wednesday? David

3 2