
36:21
Please review ICANN Expected Standards of Behavior here: https://www.icann.org/resources/pages/expected-standards-2016-06-28-en

36:30
Reminders:**Members: when using chat, please select Panelists and Attendees in order for everyone to see chat.

36:36
**Alternates not replacing a member are not permitted to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing.

40:32
As a reminder only members and alternates replacing members on this call should vote.

47:29
+1 Kristian

47:44
Yeah a very good point Kristian. I was planning to mark the losing Rr FOA as dependant on FOA also

48:17
+1 Sarah

48:54
**Members: when using chat, please select Panelists and Attendees in order for everyone to see chat.

49:22
repeating for all - +1 Kristian and Sarah

52:28
I think the topics listed are sufficient

53:30
so i'm marking q2 as "yes" because we said this is tied to the FOAs

53:36
wait

53:39
this is still the FOAs! i'm sorry

57:06
Is it a security measure relating to the registered domain itself or to the dns for that domain? Like, is it directly related to the transfer process?

57:11
**Members: when using chat, please select Panelists and Attendees in order for everyone to see chat.

57:32
Based on Jim's intervention, this could be an appropriate area for when we seek early input from the SOs/ACs. So starting to think about some questions that we can add here will be helpful.

57:57
I think if we're discussing this we'll need some education on how DNSSEC works, what the current method is to move the DNSSEC provider from one to another, how it ties to the transfer process, etc. before we can confirm if it's even in scope for this PDP

59:30
+1 Sarah

59:55
I think first we must figure out if it's in scope for what we want to accomplish here. (I am not convinced that it is)

59:57
+1 Sarah

01:00:03
Kristian - right, which I think is out of scope here

01:00:03
+1 Sarah

01:00:47
sure but if we're considering changing scope I would want to see a Very Good Reason for that

01:01:30
Absolutely agree.

01:01:49
not a 1st resort, but last.

01:05:21
Standards relating to authcode accessibility

01:06:13
Agree that those topics are connected

01:06:33
that could work, but maybe losing before gaining

01:07:50
Got it. Thanks Sarah.

01:08:56
Thanks for that dry run repeat of last weeks topics. Very helpful to me.

01:09:23
I thought this was great re pace etc

01:12:30
New territory here, so encourage members to speak up.

01:15:31
**Members: when using chat, please select Panelists and Attendees in order for everyone to see chat.

01:17:45
Here is a link to the report: https://mm.icann.org/pipermail/council/attachments/20200219/94112f0f/Rec27-Wave1-Updated-14feb20-0001.pdf

01:18:00
See item 5 and 9 on page 23-25

01:18:26
As well as two items on FOA on page 28

01:25:43
Great, sounds good

01:40:27
@Steve good distinctions that should be looked at

01:41:40
Apologies if I'm misunderstanding (I had to step away) but I thought Steve referred to a situation where a law firm registers a domain on behalf of their client. I'm not sure that's something to even consider here? The law firm would be the registrant, nothing further to say. It may be a consideration for the PPSAI group.

01:44:31
I agree that the different incarnations of having a private/proxied registration have different implications, with the one mentioned above probably being out of scope, but worthy of some discussion.

01:48:02
Thank you