- Gnso-rds-pdp-2 - lists.icann.org

Final DT2 doc.
by Deacon, Alex March 8, 2018

March 8, 2018

FYI - Attached is the “final” DT2 doc. Lisa edited it to focus on the questions and to reflect the relevant WG agreements – especially for domain name management. Alex

1 0

ICANN61 Prep Assignment - Domain Name Control and Individual Internet Use
by Deacon, Alex March 6, 2018

March 6, 2018

Drafting Team 2, As those who were on the RDS WG call on Tuesday heard, we have decided to take a week to prep for ICANN61 by working on a specific assignment in drafting team mode. Our team’s assignment is to reexamine our past output on Domain Name Control and Individual Internet Use. As a reminder the final output of your team can be reviewed at https://community.icann.org/download/attachments/74580010/RDS%20WG%20DT2%20… We have now been asked to answer the following questions more explicitly and conceptually: 1. Who associated with the domain name registration needs to be identified and/or contacted for each purpose? 2. What is the objective achieved by identifying and/or contacting each of those entities? 3. What might be expected of that entity with regard to the domain name? To prep for ICANN61, it is imperative that we discuss these questions and produce output over the next week – ideally by 5 March but no later than 7 March. We know this is a tall order, give a short timeframe. However, the leadership believes that this will help us use our F2F time at ICANN61 more effectively, which I hope we all agree would be a terrific idea. I’ve attached a template for us to use in answering these questions. I hope to propose some answer to these questions later today but given the time crunch I wanted to send this email (and the template) to the team sooner rather than later. To learn more about this assignment, please read these instructions: https://community.icann.org/download/attachments/79432608/Drafting%20Team%2…<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.…> If you were unable to attend today’s WG call, please catch up by reading or listening to the call recording/notes/transcript: https://community.icann.org/x/oAu8B<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.…> To get started, please ask any questions you may have about this assignment within the next 24 hours. If you have any suggested edits or additions or deletions to the attached first draft, even better! I encourage you to share them in reply to this message, copying the DT mailing list gnso-rds-pdp-2(a)icann.org<mailto:gnso-rds-pdp-2@icann.org> Thanks for doing what you can to help this drafting team come through on this new assignment.

4 7

Drafting team 2 final - Domain Name Management and Individual Internet User
by Susan Kawaguchi Nov. 13, 2017

Nov. 13, 2017

Hello All, I made a few changes to the document after reviewing with the leadership team and reviewing notes from our F2F in AbuDhabi. I changed the title from Domain Name Control to Domain Name Management as there was discussion pertaining to this in the F2F. Also reformatted the definition of Individual internet use to conform to the required format. Susan

1 0

Updated draft of Domain Name Control and Individual Internet user
by Susan Kawaguchi Nov. 9, 2017

Nov. 9, 2017

Hello, Andrew, Tapani and I were on the call yesterday to discuss edits to the two use cases this team is working on. Please see the attached draft and provide any edits, comments or concerns by Friday evening. This will then be distributed to the full working group for discussion on Tuesday's call. We need a volunteer to lead the discussion of our work, please let me know if you are interested. Best regards, Susan

1 0

**Updated** AC Recording, AC Chat & attendance from Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call on Wednesday, 08 November 2017
by Michelle DeSmyter Nov. 9, 2017

Nov. 9, 2017

Dear all, Please find below the Adobe Connect recording, chat and attendance from the Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call held on Wednesday, 08 November 2017 at 15:00 UTC. Adobe Connect recording: https://participate.icann.org/p1xh5qi4yv5/ Apology: Daniel Nanghaka Attendance: Susan Kawaguchi, Tapani Tarvainen, Andrew Sullivan Staff: Michelle DeSmyter Thank you. Kind regards, Michelle Adobe Connect Chat: Michelle DeSmyter:Welcome to the Next-Gen RDS Drafting team #2: Domain Name Control -and- Individual Internet Use call on 08 November 2017 at 15:00 UTC Susan Kawaguchi:Good morning Michelle, I just emailed you a document for this call, can you upload it when the meeting starts? Michelle DeSmyter:absolutely ;) Susan Kawaguchi:Good morning Tapani Tapani Tarvainen:Good evening Susan :-) Susan Kawaguchi:Ahh I always forget about time zones! Tapani Tarvainen:Apologies in advance, I'll have to leave in about 30 minutes Tapani Tarvainen:Yes. Better leave possibly overlapping stuff there than remove things that might be relevant Tapani Tarvainen:Perhaps also good to clarify that "Individual internet user" means non-registrant (i.e., excluding domain control) Tapani Tarvainen:+1 Andrew andrew sullivan:I can't do it -- I'll be in SIN for the IETF meeting andrew sullivan:I won't make Tuesday Tapani Tarvainen:I'm afraid I may also miss it

1 0

AC Recording, AC Chat & attendance from Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call on Wednesday, 08 November 2017
by Michelle DeSmyter Nov. 8, 2017

Nov. 8, 2017

Dear all, Please find below the Adobe Connect recording, chat and attendance from the Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call held on Wednesday, 08 November 2017 at 15:00 UTC. Adobe Connect recording: https://participate.icann.org/p1xh5qi4yv5/ Attendance: Susan Kawaguchi, Tapani Tarvainen, Andrew Sullivan Staff: Michelle DeSmyter Thank you. Kind regards, Michelle Adobe Connect Chat: Michelle DeSmyter:Welcome to the Next-Gen RDS Drafting team #2: Domain Name Control -and- Individual Internet Use call on 08 November 2017 at 15:00 UTC Susan Kawaguchi:Good morning Michelle, I just emailed you a document for this call, can you upload it when the meeting starts? Michelle DeSmyter:absolutely ;) Susan Kawaguchi:Good morning Tapani Tapani Tarvainen:Good evening Susan :-) Susan Kawaguchi:Ahh I always forget about time zones! Tapani Tarvainen:Apologies in advance, I'll have to leave in about 30 minutes Tapani Tarvainen:Yes. Better leave possibly overlapping stuff there than remove things that might be relevant Tapani Tarvainen:Perhaps also good to clarify that "Individual internet user" means non-registrant (i.e., excluding domain control) Tapani Tarvainen:+1 Andrew andrew sullivan:I can't do it -- I'll be in SIN for the IETF meeting andrew sullivan:I won't make Tuesday Tapani Tarvainen:I'm afraid I may also miss it

1 0

Drafting team 2 template
by Susan Kawaguchi Oct. 27, 2017

Oct. 27, 2017

Hello All, Please see the attached template for drafting team 2 covering Domain Name Control and Individual Internet Users for tomorrow's session. Susan

2 1

Draft of possible purposes
by Susan Kawaguchi Oct. 26, 2017

Oct. 26, 2017

Hello All, Attached please find the chart we worked on yesterday during our call. Please let me know if you have any revisions or additional information. I will put this information into the standard template that Lisa provided for us for the Saturday meeting. We still need a volunteer to present the information in Abu Dhabi. Best regards, Susan

1 0

Attendance, Adobe Connect recording and chat / Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call on Tuesday, 24 October 2017 at 13:00 UTC
by Julie Bisland Oct. 24, 2017

Oct. 24, 2017

Dear all, Please find below the Adobe Connect recording, chat and attendance from the Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call held on Tuesday, 24 October 2017 at 13:00 UTC. Adobe Connect recording: https://participate.icann.org/p4e3e48g3xc/<https://participate.icann.org/p4e3e48g3xc/?OWASP_CSRFTOKEN=ba32205baa7d5c6f…> Apology: Daniel Nanghaka Attendance: Susan Kawaguchi, Maxim Alzoba, Volker Greimann, Tapani Tarvainen, Andrew Sullivan Staff: Julie Bisland Thank you. Kind regards, Julie Adobe Connect Chat: Julie Bisland:Welcome to the Next-Gen RDS Drafting team #2: Domain Name Control -and- Individual Internet Use call on 24 October 2017 at 13:00 UTC Maxim Alzoba(FAITID):Hello All Maxim Alzoba(FAITID):it is Starbucks , music and students :( Maxim Alzoba(FAITID):will use chat mostly Maxim Alzoba(FAITID):I think we need Volker (for Registrars perspective) Tapani Tarvainen:Yes. We won't get very far with just the three of us. :-( Tapani Tarvainen:Unfortunately I haven't had time to go through it with any detail Maxim Alzoba(FAITID):about 1. Account creation: Maxim Alzoba(FAITID):there is a difference between creation of registrant ID in RO system and in Registrar system Maxim Alzoba(FAITID):so it could be Accounts creation and not account creation Maxim Alzoba(FAITID):domain transfer is done via e-mail or offline (fax) usually Maxim Alzoba(FAITID):as parties have to have proof of request e.t.c. and voice does not fit here Tapani Tarvainen:So both registrant-registrant and same owner between two registrars are covered? Any need to differentiate them? Maxim Alzoba(FAITID):we have two elements instead of one and it seems to be important Tapani Tarvainen:Yes, having accounts in plural sounds good to me, can't see it making any difference in the other columns though Tapani Tarvainen:Hi Volker! Julie Bisland:Welcome Volker :) Volker Greimann:Hello. Sorry for the delay, but I think I indicated I would not be available in the doodle, as I have a meeting that usually runs until now... Volker Greimann:but I am fine with now Maxim Alzoba(FAITID):Hi Volker! Tapani Tarvainen:+1 Maxim Tapani Tarvainen:In Data column perhaps expiration date? Tapani Tarvainen:for portfolio mgmt that is Tapani Tarvainen:contact info could also be relevant in Data field for Deletion/Update/Renewals Tapani Tarvainen:Maxim: yes, there're two different use cases. Maxim Alzoba(FAITID):actual deletion is done on behalf of registrant, or by registrar, or by registry (and URS, court actions, ICANN might cause those) Tapani Tarvainen:So perhaps describe two different things in the Tasks column? Tapani Tarvainen:Validation: anyone with a legal gripe ... Maxim Alzoba(FAITID):also Law Enforcement might request it (and Registry itselft) Maxim Alzoba(FAITID):about Contact validation Maxim Alzoba(FAITID):Plese give mic to Voplker Maxim Alzoba(FAITID):Volker Tapani Tarvainen:Volker: at this point I think we're just listing _possible_ users and uses, describing them, not arguing for or against inclusion in the RDS Maxim Alzoba(FAITID):Registrar is in contractual relations with Registrant/Reseller ... and might check validity for business purposes Maxim Alzoba(FAITID):but yes, Volker said it right - using internal data sets Julie Bisland:Welcome Andrew Sullivan! andrew sullivan:a million apologies -- a minor emergency kept me away from my computer so I couldn't even warn I'd be late. Maxim Alzoba(FAITID):Registry has no direct relations with registrant (usually , when they are not registrant themself) Tapani Tarvainen:So let's describe the current transfer process - we're not supposed to decide whether or not that is good or justifies the data in RDS, Tapani Tarvainen:If we try to decide or even collect all reasons for and against including these in RDS there's no way we'll get it done in the time we have. So let's concentrate on defining or describing the things and leave the need for RDS to the large group. andrew sullivan:My point is that nobody needs the RDS for this now. The <domain:info> and <contact:info> commands are enough Maxim Alzoba(FAITID):do we still have audio? andrew sullivan:also, I appear to have lost audio? Maxim Alzoba(FAITID):I lost it andrew sullivan:oh, good :) Tapani Tarvainen:I can hear you Susan Maxim Alzoba(FAITID):I hear you now Tapani Tarvainen:Maybe describe the transfer tasks and put in Users column "nobody" :-) andrew sullivan:ok :) Tapani Tarvainen:Not sure what the Real World Contact is for... Tapani Tarvainen:Keep it in but describe it a bit better Tapani Tarvainen:Use cases could include abuse issues Tapani Tarvainen:website lookup doesn't work for email-only domains Tapani Tarvainen:+1 Andrew Tapani Tarvainen:Another (admittedly geeky) consumer protection use case: when browser alerts about cross-site scripting or similar andrew sullivan:Agree. Indeed, if the RDS were more reliable and useful a number of considerable improvements to anti-abuse efforts would be posible andrew sullivan:possible, even andrew sullivan:It's not the registrar who has this problem Tapani Tarvainen:Volker: without disagreeing, we can't decide that here, let's save arguments about that to the main group andrew sullivan:+1 Volker Greimann:sure\ andrew sullivan:I will not be there and won't even be on the phone Volker Greimann:sadly, I only will arrive on Sat night Tapani Tarvainen:It's 5pm here :-) Volker Greimann:I will be at the second meeting andrew sullivan:No, it's my mother's 80th birthday :) Tapani Tarvainen:In Abu Dhabi I'll probably miss half the RDS session andrew sullivan:that's the reason I'm not going Volker Greimann:that is a very good reason\ andrew sullivan:bye a andrew sullivan:l Tapani Tarvainen:Thank you all and bye Maxim Alzoba(FAITID):I am not sure that I will be able to deliver it properly :) Maxim Alzoba(FAITID):bye all and safe travels

1 0

RDS team 2 Domain Name Control and Individual Internet users
by Susan Kawaguchi Oct. 23, 2017

Oct. 23, 2017

Hello all, Thank you for the good discussion on Tuesday's call. In an effort to move things along I have created a chart in which we can answer the questions we were asked in the template. In addition please think about the following when filling out the chart. - What's missing? - What's confusing? - What really needs to be fleshed out? I have included the EWG examples please indicate whether or not you agree with those uses and if you do please answer the following questions for each of the uses. You may also have additional uses please add those to the chart. *Tasks:* List and briefly describe tasks commonly involved in carrying out this purpose. Hint: Specific use cases for each purpose may be helpful as a starting point for enumerating tasks. * Users:* Describe the parties who often access gTLD registration data in pursuit of this purpose. *Data:* List of gTLD registration data often involved in this purpose – for contact data, please identify the data subject (e.g., registrant, tech contact, registrar, etc.) and data element(s) as applicable. Once we have input from all the members of the team I will create one document for discussion and finalization next week. Best regards, Susan

2 1

*Updated attendance* Attendance, Adobe Connect recording and chat / Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call on Tuesday, 17 October 2017 at 15:00 UTC
by Julie Bisland Oct. 17, 2017

Oct. 17, 2017

Dear all, Please find below the Adobe Connect recording, chat and attendance from the Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call held on Tuesday, 17 October 2017 at 15:00 UTC. Adobe Connect recording: https://participate.icann.org/p6rvjdhf5c5/<https://participate.icann.org/p6rvjdhf5c5/?OWASP_CSRFTOKEN=ba32205baa7d5c6f…> Apologies: Alan Greenberg Attendance: Susan Kawaguchi Maxim Alzoba, Volker Greimann, Brian Winterfeldt, Tapani Tarvainen, Daniel Nanghaka, Andrew Sullivan Staff: Nathalie Peregrine, Julie Bisland Thank you. Kind regards, Julie Adobe Connect Chat: Nathalie Peregrine:Dear all, welcome to the RDS DT2 on Domain Name Control and Individual Internet Use on Tuesday 17 October 2017 at 15:00 UTC Volker Greimann:Still stuck on PPSAI IRT Nathalie Peregrine:Thank you Volker, noted. Volker Greimann:so I have this on mute until that ends Tapani Tarvainen:SRS = Shared Registry System Nathalie Peregrine:Maxim Alzoba has joined the meeting Maxim Alzoba (FAITID):Hello All, sorry for being bit late Maxim Alzoba (FAITID):I think there should be difference between what RDS collects/stores and shows Maxim Alzoba (FAITID):ccTLDs have all kinds of wild things in their data designs Maxim Alzoba (FAITID):for example national IDs Tapani Tarvainen:Stuff in RDS should bejustified indepently of SRS, I think, even though there's a lot of overlap. Tapani Tarvainen:*independently Susan Kawaguchi:Contact information included RDS ? Tapani Tarvainen:So picking a subset of SRS as starting point for what should to to the RDS; I could live with that. Maxim Alzoba (FAITID):Registry SRS recieves two kinds of items (added by Registrar personnel manually and added by Registrar using data of Reseller/Registrant) , mostly Susan Kawaguchi:Registrant name, address, phone number email address and Fax ? Maxim Alzoba (FAITID):the second set is mostly from B2C of Regisrar (facing to Registrart/Reseller) Tapani Tarvainen:I wasn't agreeing on the specific set of elements, only that SRS would be a useful starting point. Maxim Alzoba (FAITID):should we underline that we are talking about collection/storage only now? Tapani Tarvainen:+1 Andrew Susan Kawaguchi:Items that are transmitted through SRS they are candidates for RDS collection, which can be retained and which can be published andrew sullivan:We're not, though. I am talking about it now is all Nathalie Peregrine:@ all, Julie is now taking over from me for call management,thank you. Susan Kawaguchi:Items that are transmitted through SRS they are candidates for RDS collection, which may be retained and which may be published Maxim Alzoba (FAITID):+1 andrew - about items that transferred to SRS , and relevant to functioning of DNS system (but not all transferred items) andrew sullivan:What items that are transmitted via SRS protocol (i.e. EPP) are _not_ candidates for RDS collection? Maxim Alzoba (FAITID):ID's of persons Maxim Alzoba (FAITID):it has nothing to do with DNS Maxim Alzoba (FAITID):but is a requirement for some TLDs andrew sullivan:The RDS is not only about the DNS, though andrew sullivan:If this were only about the DNS, the problem would be trivial andrew sullivan:we'd be done Maxim Alzoba (FAITID):transfer of person's ID to foreing party is heavily regulated almost everywhere Daniel K. Nanghaka:the data must be available to serve there purpose andrew sullivan:Yes. So under some conditions it can't be transferred. But the RDS is a distributed database Maxim Alzoba (FAITID):it is not AMADEUS where you need it for security purposes Tapani Tarvainen:+1 Volker andrew sullivan:therefore there is collection as soon as the registrar has it Daniel K. Nanghaka:Registrar's must provide the data despite of its status despite its publicity status Maxim Alzoba (FAITID):it is not going to be published, and collected by Registry according to it's policy / business cycle and not due to ICANN policy andrew sullivan:@Susan: I think it's a good start Tapani Tarvainen:Hard to disagree with those "may"s in there Tapani Tarvainen:Perhaps we could agree that items in SRS can be used as a starting point but not automatically include everything in there in RDS, too. Maxim Alzoba (FAITID):SRS is a method of B2B interaction done via EPP or sometimes offline Maxim Alzoba (FAITID):so I am not sure we need to refer to SRS at all (in some situations data allowed to be passed to Registry via offline methods (fax, for example)) Maxim Alzoba (FAITID):registry policies enforced only on Registry and Registrar level (if not required by contract then not on Reseller level) Julie Bisland:Daniel is connected via the audio bridge, but may be muted. I'll have operator call out to him andrew sullivan:What data is needed from RDS for transfer? If I'm a registrar, I can get that through the SRS, and non-registrars can't initiate the transfer. No? Daniel K. Nanghaka:I think we have to look at the specific data elements and derive use cases Maxim Alzoba (FAITID):SRS only for contracted Registrars with the particular Registry Maxim Alzoba (FAITID):We shoudl distinguish between parties collecting data , and use we for GNSOrequirements Daniel K. Nanghaka:+1 Maxim Maxim Alzoba (FAITID):and to clearly say "Registry" , "Registrar", "Reseller" whern we talk about the collection point and add "transfer of collected data from __ to ___" Tapani Tarvainen:I certainly occasionally use whois to check suspicious domains... but I may not be a typical Internet user. :-) Daniel K. Nanghaka:have we yet come to the issue of transfer. The transfer should be discussed in the second phase Tapani Tarvainen:Certificates are not so useful for email at present andrew sullivan:I do not think that we can use ICANN-familiar people as examples of "Internet users". We are outliers among outliers. Daniel K. Nanghaka:let's focus discussion to purposes, the certificate shows ownership Daniel K. Nanghaka:I think the layman Internet user does not understand privacy and that there data is out there Volker Greimann:and yet I still use it Maxim Alzoba (FAITID):baisc internet uses does not undersstand sometimes difference between correct and incorrect data/certificates e.t.c. Maxim Alzoba (FAITID):*user Maxim Alzoba (FAITID):domain administrator verification is in contracts so , unfortunately personal data is relevant to domain control Volker Greimann:Then you need another registrar ;-) Maxim Alzoba (FAITID):REgistry is aware only of items given by Registrar Maxim Alzoba (FAITID):some exclusions might be - special procedure of additional verification e.t.c, Volker Greimann:Susan +1, but then we already agreed that registration dates are not personal data ;-) andrew sullivan:I think "verifying status of domain" could be a use case that is purely technical -- the non-renewal in the example would cause an outage andrew sullivan:But the overall management of portfolios -- which of these domains is associated with my account? -- could be outside that line Maxim Alzoba (FAITID):@Andrew, verification is not technical issue , it is business issue (DNS works perfectly even with the non correct data of the Registrant, for example when he/she decided to change name) andrew sullivan:Surely if the registration does not get renewed, it's a technical issue -- the name stops working Maxim Alzoba (FAITID):most probably verification is anti-abuse related andrew sullivan:And also being able to contact someone because they're spewing garbage at me is a technical issie andrew sullivan:issue andrew sullivan::) Maxim Alzoba (FAITID):time needs to be doodle polled Tapani Tarvainen:Same time next Tuesday is good andrew sullivan:ok for me Volker Greimann:ok Julie Bisland:Susan, I'll have a doodle poll sent for Tuesday Maxim Alzoba (FAITID):I have more things happening so need to ensure no overlaps (preparations to ICANN meeting) andrew sullivan:thanks everyone Daniel K. Nanghaka:Thank you andrew sullivan:bye Tapani Tarvainen:bye and thanks all Maxim Alzoba (FAITID):Bye all , good night Daniel K. Nanghaka:bye

1 0

Attendance, Adobe Connect recording and chat / Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call on Tuesday, 17 October 2017 at 15:00 UTC
by Julie Bisland Oct. 17, 2017

Oct. 17, 2017

Dear all, Please find below the Adobe Connect recording, chat and attendance from the Next-Gen RDS drafting team 2 - Domain Name Control -and- Individual Internet Use call held on Tuesday, 17 October 2017 at 15:00 UTC. Adobe Connect recording: https://participate.icann.org/p6rvjdhf5c5/<https://participate.icann.org/p6rvjdhf5c5/?OWASP_CSRFTOKEN=ba32205baa7d5c6f…> Apologies: Alan Greenberg Attendance: Susan Kawaguchi Maxim Alzoba, Volker Greimann, Brian Winterfeldt, Tapani Tarvainen, Alan Greenberg, Daniel Nanghaka, Andrew Sullivan Staff: Nathalie Peregrine, Julie Bisland Thank you. Kind regards, Julie Adobe Connect Chat: Nathalie Peregrine:Dear all, welcome to the RDS DT2 on Domain Name Control and Individual Internet Use on Tuesday 17 October 2017 at 15:00 UTC Volker Greimann:Still stuck on PPSAI IRT Nathalie Peregrine:Thank you Volker, noted. Volker Greimann:so I have this on mute until that ends Tapani Tarvainen:SRS = Shared Registry System Nathalie Peregrine:Maxim Alzoba has joined the meeting Maxim Alzoba (FAITID):Hello All, sorry for being bit late Maxim Alzoba (FAITID):I think there should be difference between what RDS collects/stores and shows Maxim Alzoba (FAITID):ccTLDs have all kinds of wild things in their data designs Maxim Alzoba (FAITID):for example national IDs Tapani Tarvainen:Stuff in RDS should bejustified indepently of SRS, I think, even though there's a lot of overlap. Tapani Tarvainen:*independently Susan Kawaguchi:Contact information included RDS ? Tapani Tarvainen:So picking a subset of SRS as starting point for what should to to the RDS; I could live with that. Maxim Alzoba (FAITID):Registry SRS recieves two kinds of items (added by Registrar personnel manually and added by Registrar using data of Reseller/Registrant) , mostly Susan Kawaguchi:Registrant name, address, phone number email address and Fax ? Maxim Alzoba (FAITID):the second set is mostly from B2C of Regisrar (facing to Registrart/Reseller) Tapani Tarvainen:I wasn't agreeing on the specific set of elements, only that SRS would be a useful starting point. Maxim Alzoba (FAITID):should we underline that we are talking about collection/storage only now? Tapani Tarvainen:+1 Andrew Susan Kawaguchi:Items that are transmitted through SRS they are candidates for RDS collection, which can be retained and which can be published andrew sullivan:We're not, though. I am talking about it now is all Nathalie Peregrine:@ all, Julie is now taking over from me for call management,thank you. Susan Kawaguchi:Items that are transmitted through SRS they are candidates for RDS collection, which may be retained and which may be published Maxim Alzoba (FAITID):+1 andrew - about items that transferred to SRS , and relevant to functioning of DNS system (but not all transferred items) andrew sullivan:What items that are transmitted via SRS protocol (i.e. EPP) are _not_ candidates for RDS collection? Maxim Alzoba (FAITID):ID's of persons Maxim Alzoba (FAITID):it has nothing to do with DNS Maxim Alzoba (FAITID):but is a requirement for some TLDs andrew sullivan:The RDS is not only about the DNS, though andrew sullivan:If this were only about the DNS, the problem would be trivial andrew sullivan:we'd be done Maxim Alzoba (FAITID):transfer of person's ID to foreing party is heavily regulated almost everywhere Daniel K. Nanghaka:the data must be available to serve there purpose andrew sullivan:Yes. So under some conditions it can't be transferred. But the RDS is a distributed database Maxim Alzoba (FAITID):it is not AMADEUS where you need it for security purposes Tapani Tarvainen:+1 Volker andrew sullivan:therefore there is collection as soon as the registrar has it Daniel K. Nanghaka:Registrar's must provide the data despite of its status despite its publicity status Maxim Alzoba (FAITID):it is not going to be published, and collected by Registry according to it's policy / business cycle and not due to ICANN policy andrew sullivan:@Susan: I think it's a good start Tapani Tarvainen:Hard to disagree with those "may"s in there Tapani Tarvainen:Perhaps we could agree that items in SRS can be used as a starting point but not automatically include everything in there in RDS, too. Maxim Alzoba (FAITID):SRS is a method of B2B interaction done via EPP or sometimes offline Maxim Alzoba (FAITID):so I am not sure we need to refer to SRS at all (in some situations data allowed to be passed to Registry via offline methods (fax, for example)) Maxim Alzoba (FAITID):registry policies enforced only on Registry and Registrar level (if not required by contract then not on Reseller level) Julie Bisland:Daniel is connected via the audio bridge, but may be muted. I'll have operator call out to him andrew sullivan:What data is needed from RDS for transfer? If I'm a registrar, I can get that through the SRS, and non-registrars can't initiate the transfer. No? Daniel K. Nanghaka:I think we have to look at the specific data elements and derive use cases Maxim Alzoba (FAITID):SRS only for contracted Registrars with the particular Registry Maxim Alzoba (FAITID):We shoudl distinguish between parties collecting data , and use we for GNSOrequirements Daniel K. Nanghaka:+1 Maxim Maxim Alzoba (FAITID):and to clearly say "Registry" , "Registrar", "Reseller" whern we talk about the collection point and add "transfer of collected data from __ to ___" Tapani Tarvainen:I certainly occasionally use whois to check suspicious domains... but I may not be a typical Internet user. :-) Daniel K. Nanghaka:have we yet come to the issue of transfer. The transfer should be discussed in the second phase Tapani Tarvainen:Certificates are not so useful for email at present andrew sullivan:I do not think that we can use ICANN-familiar people as examples of "Internet users". We are outliers among outliers. Daniel K. Nanghaka:let's focus discussion to purposes, the certificate shows ownership Daniel K. Nanghaka:I think the layman Internet user does not understand privacy and that there data is out there Volker Greimann:and yet I still use it Maxim Alzoba (FAITID):baisc internet uses does not undersstand sometimes difference between correct and incorrect data/certificates e.t.c. Maxim Alzoba (FAITID):*user Maxim Alzoba (FAITID):domain administrator verification is in contracts so , unfortunately personal data is relevant to domain control Volker Greimann:Then you need another registrar ;-) Maxim Alzoba (FAITID):REgistry is aware only of items given by Registrar Maxim Alzoba (FAITID):some exclusions might be - special procedure of additional verification e.t.c, Volker Greimann:Susan +1, but then we already agreed that registration dates are not personal data ;-) andrew sullivan:I think "verifying status of domain" could be a use case that is purely technical -- the non-renewal in the example would cause an outage andrew sullivan:But the overall management of portfolios -- which of these domains is associated with my account? -- could be outside that line Maxim Alzoba (FAITID):@Andrew, verification is not technical issue , it is business issue (DNS works perfectly even with the non correct data of the Registrant, for example when he/she decided to change name) andrew sullivan:Surely if the registration does not get renewed, it's a technical issue -- the name stops working Maxim Alzoba (FAITID):most probably verification is anti-abuse related andrew sullivan:And also being able to contact someone because they're spewing garbage at me is a technical issie andrew sullivan:issue andrew sullivan::) Maxim Alzoba (FAITID):time needs to be doodle polled Tapani Tarvainen:Same time next Tuesday is good andrew sullivan:ok for me Volker Greimann:ok Julie Bisland:Susan, I'll have a doodle poll sent for Tuesday Maxim Alzoba (FAITID):I have more things happening so need to ensure no overlaps (preparations to ICANN meeting) andrew sullivan:thanks everyone Daniel K. Nanghaka:Thank you andrew sullivan:bye Tapani Tarvainen:bye and thanks all Maxim Alzoba (FAITID):Bye all , good night Daniel K. Nanghaka:bye

1 0

Drafting Team #2 – Domain Name Control -and- Individual Internet Use
by Susan Kawaguchi Oct. 17, 2017

Oct. 17, 2017

Hello All, Welcome! You have been selected by the RDS leadership team to serve on a drafting team to define the RDS purposes named in the subject line above. Thank you very much for volunteering to participate in this effort. Here is the list of the team members: Coordinated by: Susan Kawaguchi Members: Maxim Alzoba, Volker Greimann, Brian Winterfeldt, Tapani Tarvainen, Alan Greenberg, Daniel Nanghaka, Andrew Sullivan As you can see, this message is being sent via a dedicated mailing list that has been set up to facilitate email communications over the next two to two and half weeks. Please use the list for all of our electronic team communications. Note that this list is publicly archived. Here are the list details. Mailing list address: gnso-rds-pdp-2(a)icann.org Mailing list archive: http://mm.icann.org/pipermail/gnso-rds-pdp-2 Attached you will find a template that outlines our tasks and provides a timeline. Please review it right away so that we can start discussions as soon as possible. We plan to have at least two teleconference calls over the next two weeks, but additional ones may be scheduled as needed. At the same time, mailing list discussion is encouraged. The first call will be scheduled on Tuesday or Wednesday, October 17 or 18. Please complete the Doodle poll linked below not later than end of day on Saturday, October 14 so that a time can be identified that best meets team member availability. https://icannorg.doodle.com/poll/ehvh66vvutp83yiu Teams were formed using results from this week’s poll which can be found on the WG wiki. Every team includes: · At least one person from each of the perspectives named in the poll wherever possible, but without assigning members to more than one team. · A mix of members who have direct experience regarding the proposed purpose and those who have little or no experience about the proposed purpose. Remember that the purpose of this work is not to make decisions but rather to facilitate communication and understanding. The team is expected to deliver a one to two-page document to the full WG that will be used in our face to face meeting on Saturday, October 28 to help all WG members understand the applicable purpose. If you have any questions, please feel free to ask them on this list. Thanks in advance for completing the Doodle Poll promptly and for participating in our discussions starting today and in the days ahead. Susan Kawaguchi Drafting Team Coordinator

3 5