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

Hi all, just a reminder to select "All Panelists and Attendees" for chat.

the pace in RPMs pdp improved a lot

nothing to add, thx Keith, but happy to answer questions

Quick check: how will the new IGO track fit in with the timing? It's not dependent on either phase I know.

I don’t have anything to add.

Thanks, Keith.

Email from Keith to the Council mailing list on the Draft Operational Design Phase: https://mm.icann.org/pipermail/council/2020-October/024119.html

One question that the GNSO Council and community can provide valuable input on is how this design phase can work with (or possibly be integrated in some way with) the current GNSO desire for data-driven policy making. While there is an expectation that PDP Working Groups will perform impact analysis and can obtain external guidance, to date this does not appear to have been done consistently. In this regard, the proposed phase can perhaps be helpful.

Check out the ICANN69 edition of GNSO Policy Briefing for more information about IRTs’ and PDPs’ current status. The briefing has been redesigned to be more concise and engaging: https://go.icann.org/gnsobriefing

Reminder: questions and comments will be taken when asked by councillors only.

this design is for assessment, not for damage prevention (seems to be)

Thanks Theresa.

Thank you Rafik - that is helpful input.

Thank you all for the good discussion -

The timing section actually talks already about the possibility to start some of this work earlier during the later stages of the PDP to provide information to the PDP when formulating their recommendations where appropriate

Thank you all

Thank you everyone.

Tom made a suggestion re the ccNSO meeting on the list

What's meant by "private use TLD" here?

"user assigned" or RFC2606 TLDs?

@Philippe, the term refers to the most recent SSAC advisory that was just published: https://www.icann.org/en/system/files/files/sac-113-en.pdf

Thanks Mary.

(thanks, si it's essentialy enterprise TLDs then - my reading)

Scoping team?

@Philippe, assuming I’m understanding your terminology as you intended, yes, I believe those TLDs would be included if they are used as privately resolvable name spaces and not intended for delegation into the public root zone.

@Mary thanks, yes, "skimming through" their report (which I should have read...) it's my understanding.

The SSAC advisory on DNS abuse has not yet been published (to our knowledge), but GNSO community members and the Council may be interested to know that it has been brought up in the planning group for the upcoming DNS abuse plenary session at ICANN69 (in which SSAC is participating).

We might consider the same (to my intervention) for the Board topic on Enhancing MSM. We could use visibility about the work impact and what those next steps will do to our program mgmt. pipeline planning.

+ 1 Michele - Furthermore, PDP may not be the most appropriate path

@Philippe, Mary, just to add, I believe the SSAC paper talks about only a single string being set aside for private use.

example, files on websites stay there despite of actions of registries or registrars and still accessible via IP, but it does not mean SSAC goes to IANA

And I’ve no idea why / how IANA could do anything :)

or PTI

it is the same as we can not do things to the actual content

@Pam, there is no set timeline for feedback as it is a new proposal and that’s why we wanted to get the paper out to the community well ahead of ICANN69.

@steve - thanks. a sort of RFC2606 reserved TLD, for these use cases. (I forget what the label was discussed at the IETF, but a sort of .local, .private or something)

I assume they’re trying to avoid conflicts by making some of them formally reserved?

I think I read the SSAC paper

But they didn’t have an actual list of strings

Because they couldn’t decide on which strings

To put on a list

does it mean SSAC can now deal TLDs?

no

thanks all

Bye for now then... … … Thanks everyone!

Thank you all - stay safe!

Thanks all. See you at ICANN

Thank you all.

Thank you all, have a good ICANN 69 mtg!