[gnso-rds-pdp-wg] Mp3, Attendance & AC Chat for Next-Gen RDS PDP WG

Mark Svancarek marksv at microsoft.com
Wed Aug 17 16:29:50 UTC 2016


Pardon me for failing to send regrets.  I went to bed early and missed the meeting.  Thanks to all for the final wordsmithing of the problem statement.

From: gnso-rds-pdp-wg-bounces at icann.org [mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Nathalie Peregrine
Sent: Wednesday, August 17, 2016 7:34 AM
To: gnso-rds-pdp-wg at icann.org
Cc: 'GNSO Secretariats' <gnso-secs at icann.org>
Subject: [gnso-rds-pdp-wg] Mp3, Attendance & AC Chat for Next-Gen RDS PDP WG

Dear All,



Please find the attendance of the call attached to this email and the MP3 recording below for the Next-Gen RDS PDP Working group call held on Wednesday 17 August 2016 at 05:00 UTC.

 Mp3: http://audio.icann.org/gnso/gnso-nextgen-rds-17aug16-en.mp3<http://mailer.samanage.com/wf/click?upn=NrFWbrBstcrPWP369qgbqlXiSKeL20xnUXzI03ZqpsvgRhF8anYZT-2Fu85DJG3jGxIJRW47MgBA0RRQrPrqorQMYwCAeUK6G0DYWia7YuRUU-3D_QuA5zZR9ZZ7J1F2FeF-2FOsgm1hgIDcBrAX2P7Ezxmql7ckJc4ios1-2BxObAoz2rzLSI3c4QB1NGo7bw7XrBjpRCbz74w4vzk48UxZMFoBBQBQaQ0ePdiOjdJ30sQNHkokOf-2F2p-2FBvMgKvMhzp-2B4u8fP-2BRrSytHe2KCf2HpQmtSbpezMgNTUG57PiORAPesOotpHA-2BC4pSmXJRsVmpbNaLqzq35Y6gaVSysiDylmUvPAyBZGbGZ1MOL-2BjI6w6uI6-2FWf5UvYF2PQ5QFkCab-2Fa5CD2uBA2HwmnUGsWrHJuVMMk93ROZiiB9UNBBth3I4N-2BKh5I5JKI0qBp5Oe-2BR8-2BctB9orQ0M4Bv-2BeGzyOenB9MqOdNS4DZrrRpcrPIMZTPBMVmsXCv9H9ZO1exaFkBdzo86iwdXg1WbCyg2BSoAuHsxDY53Qgqh2dD0td49PPgiixL2tzvdMRxj5VOtGyzmG5T8IQDQWIbTKl-2BEV9DnlCvf5QfVGllDLw7BpmH-2BpY2BtM3V>
<http://audio.icann.org/gnso/gnso-nextgen-rds-14jun16-en.mp3>

The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:

http://gnso.icann.org/en/group-activities/calendar<http://gnso.icann.org/en/group-activities/calendar#nov>



** Please let me know if your name has been left off the list **



Mailing list archives:http://mm.icann.org/pipermail/gnso-rds-pdp-wg/



Wiki page: https://community.icann.org/x/DAOsAw


Thank you.

Kind regards,

Nathalie



-------------------------------



Adobe Connect chat transcript for Wednesday 17 August 2016
  Nathalie Peregrine:Dear All, Welcome to the Next-Gen RDS PDP Working Group call on Wednesday 17 August 2017 2016 at 05:00 UTC.
  Nathalie Peregrine:If you wish to speak during the call, please either dial into the audio bridge and give the operator the password RDS, OR click on the telephone icon at the top of the AC room to activate your AC mics.  Please remember to mute your phone and mics when not speaking.
  Nathalie Peregrine:Agenda page: https://community.icann.org/x/ZgisAw
  Maxim Alzoba (FAITID):Hello All
  Nathalie Peregrine:Welcome Maxim and Stuart!
  Chuck Gomes:Hi all.
  Alex Deacon:hello everyone...
  Iliya Bazlyankov:Hello all
  Nathalie Peregrine:Welcome everybody!
  Fabricio Vayra:Hello
  andrew sullivan:I sent regrets for this meeting, and I bet I won't last
  Chuck Gomes:1 more minute
  Susan Kawaguchi:Good evening!
  andrew sullivan:I've a meeting at 10:00 my time (it's 1:00 here) that I chair
  andrew sullivan:so I will probably drop early.  So more regrets :)
  Nathalie Peregrine:Thank you Andrew for bringing this to my attention, we will mark you as present regardless of the duration of your attendance :)
  Maxim Alzoba (FAITID):8am
  andrew sullivan:@Nathalie: it's good to know that even if I flake out I am some sort of participant ;-)
  Fabricio Vayra:We hear you, Alex.
  andrew sullivan:The only worry I have about this is the suggestion that those who are outside the enumerated list are still part of the "some entities" who have the anonymity and privacy requirements. Who are these others?  But I don't care to much about this
  Fabricio Vayra:Looks good, Alex.  Thanks for all the hard work (you and the drafting team)
  Beth Allegretti:+1
  Maxim Alzoba (FAITID):are they secret stakeholders?
  andrew sullivan:Jim is asking basically the worry I have
  Lisa Phifer:the WG is tasked with defining the purpose of the RDS, not just reviewing it
  andrew sullivan:ok, now he's really hitting what I'm worried about it :)
  Fabricio Vayra:valid point, Alan.
  Fabricio Vayra:and good points, Andrew
  Stephanie Perrin:I think we all worry that each document we come up with becomes super important in that adjudication process.  I would agree with the concern about this one in particular.
  Marina Lewis:Based on our discussions in Helsinki, I believe this problem statement was meant as a tool to aid in our discussions, not a constraint.
  Fabricio Vayra:+1 Marina
  Alex Deacon:in the sub group we called it an executive summary of the charter.   its not meant to change/modify the charter.
  andrew sullivan:Very helpful, Chuck, thanks.  It might be useful to say something about working goal, like what Rod just said.  Thanks
  andrew sullivan:And again what Alan is saying: rough principles of operation, not rules
  Lisa Phifer:suggested text: Note that this problem statement is meant as a tool to aid in discussion, consistent with but not a constraint on the Working Group and its Charter.
  andrew sullivan:+1 Lisa
  andrew sullivan:also +1 s/us/wg/
  Jim Galvin (Afilias):Ok Chuck.
  Jim Galvin (Afilias):The changes that Lisa (apologies if it was someone else) made address my first concern.  Specifically, changing "the aforementioned" to "other" does it for me.
  Jim Galvin (Afilias):"meet the needs" -> "meet the needs, as described further below,"
  andrew sullivan:Key thing for me: the "meet the needs" part has working priority to the tech choice
  David Cake:'better meet the needs'?
  andrew sullivan:I believe this is consistent with charter
  Marina Lewis:@Stephanie - I think this was meant as just colorful intro language.  I don't read so much into this.  Again, this is a tool and we are constrained by our charter.
  Alex Deacon:We must not however set policy that will limit future and now unknown users/innovation/etc.
  Alan Greenberg:We are going to have to balance a lot of competing needs. We will NOT meet all the needs by definition.
  Stephanie Perrin:Exactly Alan.
  Alex Deacon:s/users/uses/
  andrew sullivan:I expect Jim's approach will work
  Stephanie Perrin:Ditto
  Alan Greenberg:We are taking a clean concise statement and not adding bumps on to it to make sure that no one will misunderstand. THAT is why I wanted confirmation that it would not be used as a hammer later on.
  andrew sullivan:And we don't need to hammer out text real time -- could be a list edit
  Stephanie Perrin:+1 andrew
  Stephanie Perrin:No, looks good
  Lisa Phifer:the requirements determine the need for a new policy framework - technology decisions then follow policy
  Stephanie Perrin:At the risk of sounding like a former bureaucrat, I would like to add "to the extent possible" at the end of the third paragraph.
  Stephanie Perrin:Rhetorical flourish which is giving me heartburn....
  andrew sullivan:agree with delete the "existing and &c"
  Marina Lewis:We can lose the "excision and ever evolving Internet" if that's too problematic.
  Lisa Phifer:posslble alt text for first sentence: tasked with defining the requirements for and (if appropriate) policies associated with...
  Marina Lewis:"existing..."
  Stephanie Perrin:+1 to DNS
  Jim Galvin (Afilias):Yes
  Marina Lewis:I'm happy with that first red-line comment as is.
  andrew sullivan:yeah, sorry, couldn't edit in vox well on demand :)
  andrew sullivan:something like what I see.  Thnaks
  Fabricio Vayra:+1 Lisa and Alex
  andrew sullivan:+11 (a lot in geek terms!) for great work
  Alex Deacon:Many thanks to the other members of the sub-group who all contributed to this proposed version.
  andrew sullivan:completely agree this is happpening now, and the right thing is to make that better
  andrew sullivan:FSVO "better"
  andrew sullivan:for the transcript: I'm very sorry I've been careless about stating my name.  It's andrew sullivan.
  andrew sullivan:when Chuck calls on "andrew"
  Nathalie Peregrine:Thank you Andrew
  andrew sullivan:I agree completely with Rod here that it's already a use case, but this offers a plan.
  Kal Feher:Under data elements the data is @registration. if an update has been made since registration, should that information also be collected?
  Lisa Phifer:admin contact is often the party you need to reach for domain name renewal, transfer, purchase, etc
  Maxim Alzoba (FAITID):+1
  Maxim Alzoba (FAITID):on the investigation to be done before asking LE to look into the case
  Stephanie Perrin:exactly
  Alan Greenberg:We are not regulating web hosters, but we are providing core Internet infrastructure that will impact all parts of the Internet...
  Fabricio Vayra:+1 Alan
  andrew sullivan:I think that Rod is making the fine distinctions I think would help
  Tjabbe Bos (European Commission):+1 for the excellent use case
  Lisa Phifer:@Andrew - this is where the EWG's purpose-based contacts came from, to unpack the overloaded tech/admin contacts in today's WHOIS
  andrew sullivan:not inconsistent with what Alan and Stephanie said earlier (incl in chat)
  andrew sullivan:and completely agree with Lisa
  Fabricio Vayra:Thanks, Rod
  Kal Feher:the data here combines a mix of things a Registrant will explicitly tell a Registrar about and data that will be derived from their behaviour (IP addresses, their system creds)
  andrew sullivan:if you are to have a website, who your hosting provider is is not PII
  Fabricio Vayra:+1 Andrew
  Kal Feher:your creds at that hosting provider should be tho
  andrew sullivan:@kal: I should hope so.
  andrew sullivan:keep in mind that any reputation service automatically means that those with _good_ reoutation win
  Marika Konings:further details on visa requirements are expected to be posted shortly.
  Fabricio Vayra:thanks ... zzzzz
  andrew sullivan:bye!
  Kal Feher:perfect time
  Fabricio Vayra::)
  Maxim Alzoba (FAITID):bye all
  Marina Lewis:good night/morning everyone!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160817/95a61d2d/attachment.html>


More information about the gnso-rds-pdp-wg mailing list