MTS - AV: Hello, and welcome to the Ppsa Irt session. My name is Jens Shen, and I'm a participation manager for this session.
MTS - AV: Please note that this session is being recorded and is governed by the Ican expected standards of behavior.
MTS - AV: If you would like to speak during the session, please raise your hand in zoom.
MTS - AV: when called upon, virtual participants will be given permission to unmute in zoom
MTS - AV: onsite participants will use a physical microphone to speak.
MTS - AV: Please state your name for the record and speak at a reasonable pace.
MTS - AV: I'll now hand the floor over to Dennis Ching.
MTS - AV: Good morning, everyone.
MTS - AV: My name's Dennis Chang.
MTS - AV: I am the project director
MTS - AV: for this policy implementation.
MTS - AV: and
MTS - AV: I think I know everyone on the table here. The 1st I'd like to invite all the Irt members
MTS - AV: or those of you who is interested in joining the Irt members.
MTS - AV: Please sit at the table.
MTS - AV: Don't shy away.
MTS - AV: not yet.
MTS - AV: But today we will be talking about.
MTS - AV: And this is
MTS - AV: the agenda that we will follow will start with some introduction.
MTS - AV: This is our very 1st meeting, and even though I think we know each other, all of us.
MTS - AV: There's some, maybe new to
MTS - AV: others, and then we're covered briefly the background and the purpose of our implementation and talk
MTS - AV: mostly about our work plan.
MTS - AV: And then I'm going to introduce you to the tools that we will be using for this implementation project and talk about the next steps.
MTS - AV: And finally.
MTS - AV: at the end, we reserve some time for Community Q&A.
MTS - AV: So this is an Ir. T working session.
MTS - AV: and therefore during the session until agenda 5.
MTS - AV: Only the Irt members can speak and participate in discussion, and I will ask the public the non irt members.
MTS - AV: to
MTS - AV: hold your question till the end
MTS - AV: for the community. Q. And a.
MTS - AV: Thank you. Okay, so let's start with the introduction.
MTS - AV: as of yesterday.
MTS - AV: We have 47 irt members sign up.
MTS - AV: and there's 2 gns or liaisons.
MTS - AV: and 3 stakeholder groups have
MTS - AV: appointed their representative and and alternative for this implementation.
MTS - AV: So here's what we'll do
MTS - AV: for those of you in the room, starting with Eric over there.
MTS - AV: Pay attention.
MTS - AV: I would like you to say your name and your affiliation, and then we'll keep going down
MTS - AV: the list, and for those people who are in remotely please type your name and your affiliation in the chat. Go, Eric.
MTS - AV: Thank you, Dennis. Good morning. Everyone Eric Brokabauer, Squarespace, Domains, Registrar.
MTS - AV: Greg, Dbiaci, Amazon, registrar.
MTS - AV: registrar stakeholder group.
MTS - AV: any Samuelson bikes to our stakeholder group
MTS - AV: Hi I'm Sarah wild I'm with 2 cows and the register, stakeholder group.
MTS - AV: Owens, Miguel ski registrar name, cheap thanks.
MTS - AV: Prudence, Melinky, registrar, Mark Monitor, RRSG. Thanks.
MTS - AV: and I'm Zoe, registrar secretary
MTS - AV: looks of Her namespace registrar.
MTS - AV: Good morning. Everyone. Nigar, Conrad layer, 9 technologies, independent stakeholder.
MTS - AV: Hi, everyone. Chris Evans cleanediness participant by myself.
MTS - AV: Hi Jensen, I can org
MTS - AV: Steve Crocker Edgemore Research Institute. I'm a member of the Security Advisory Committee and also the business constituency. But I'm participating here as a participant and not as a representative of either.
MTS - AV: Roger Carney. Godaddy Registrar
MTS - AV: Karen. Let's I can't work
MTS - AV: Allen Greenberg at large.
MTS - AV: Marjimal. I'm with Meta Platforms, and I'm representing the BC. On this IRT.
MTS - AV: Who understand Core Association, not on the Irt just sitting here.
MTS - AV: I'm also not sure if I'm actually on the irt. I started signing up yesterday. But I'm Katherine Paletta, and I'm with name, com and identity. Digital.
MTS - AV: Thank you everyone.
MTS - AV: So about joining the Rt. We, we'll talk about that a little little bit. It's really easy to join the Irt, and we are encouraging everyone to join, of course.
MTS - AV: and if you want to participate, there are different ways to participate. Then we'll talk about that. So the implementation team we often refer to as the Ipt you hear about Irt, and you know a lot about Irt ipt is the I can org staff team
MTS - AV: with me as the project manager.
MTS - AV: and
MTS - AV: we have a core team that works this project daily. And then, of course, we have the what I call an extended team that we bring in to help us as we go. So
MTS - AV: the ipt I can stab
MTS - AV: is responsible and accountable for implementing this policy, and Irt is here to support us, making sure that we are implementing in line with the recommendation.
MTS - AV: and at times provide us with technical support and your subject matter expertise.
MTS - AV: We were neat as we go.
MTS - AV: So next topic.
MTS - AV: If this is
MTS - AV: I think that everybody probably is aware of the background. We started this in 2,016,
MTS - AV: and we had an Irt. And I will refer to that Ir. T. As a 2,016, IRT.
MTS - AV: Let me see a show of hand, who was a member of the 2016 original Ir. T. Let me see.
MTS - AV: 1, 2, 3, 4,
MTS - AV: 5, 6. Wow!
MTS - AV: We're very fortunate to have you. Thank you for joining us again.
MTS - AV: Apparently it was fun you came back for more. Excellent! This is great news So
MTS - AV: would you know. And with the Irt support, right, we put this implementation on hold right because things were going on and Gdpr was happening. And there was like redundant work
MTS - AV: that was happening, such as
MTS - AV: the registration data policy implementation.
MTS - AV: And what happened is that the registration data policy
MTS - AV: was
MTS - AV: published
MTS - AV: in February of 2024.
MTS - AV: So now we have a good, well-defined
MTS - AV: foundation of how the registration data works.
MTS - AV: And now we can get started again, and that's why we decided to resume at this moment
MTS - AV: to pick up this implementation. Now, show of Hands, who was a member of the registration data policy. IRT.
MTS - AV: Very good. Thank you so much.
MTS - AV: And that will be important as we go. Because
MTS - AV: and that is the foundational one. Anyway, the the
MTS - AV: what we're doing is, of course, implementing the policy following our framework, which you should all be familiar with, and the
MTS - AV: these slides will be provided to you after the session and post posted.
MTS - AV: And we call some consensus policy implementation framework. Cp. Cpif
MTS - AV: is where we documented how we do the policy implementation.
MTS - AV: So agenda 3, I call it the general policy implementation steps here.
MTS - AV: This is typical. And we did this with the registration data policy. Now.
MTS - AV: it seems sort of obvious. The workflow right? 1st thing you have to do is really understand the recommendations in the final report
MTS - AV: that Gnso approved
MTS - AV: and
MTS - AV: Board approve and directed. I can work to implement
MTS - AV: but number one. Everybody on the IRT. Must
MTS - AV: understand what's in the recommendations, because that is what we are implementing. We're not here
MTS - AV: to develop a new policy on privacy that was already done.
MTS - AV: And so we have our charter and
MTS - AV: very narrow limit to implement to the language that we are given.
MTS - AV: and then we're going to be doing what I call an implementation design.
MTS - AV: And you will see, as we go on.
MTS - AV: that there are many ways to implement the policy recommendations.
MTS - AV: and there may be options. We'll look at that, and we'll choose one, and we'll bring it to you to review our approach.
MTS - AV: and that's what you would do for us. The this IRT.
MTS - AV: And of course
MTS - AV: the design, were produced
MTS - AV: a policy language.
MTS - AV: and I
MTS - AV: emphasize when I say policy language, because
MTS - AV: many times I hear
MTS - AV: people confuse confusion, that
MTS - AV: the recommendations in the final report is the policy language. Well, it is not.
MTS - AV: What's in the final report that will approve is the recommendations language
MTS - AV: and our job here together is to produce the actual policy language
MTS - AV: that gets published
MTS - AV: on the consensus policy page.
MTS - AV: which in turn becomes
MTS - AV: the requirement
MTS - AV: and use set of obligations for the contracted parties. And I can work.
MTS - AV: That's what we're doing.
MTS - AV: Of course, when we develop that policy language and any other supporting document we need for the implementation.
MTS - AV: we will go to the public comment
MTS - AV: and we follow our normal process
MTS - AV: or
MTS - AV: incorporating whatever comment we get.
MTS - AV: And then we were
MTS - AV: publish the policy and issue a legal notice to the contracted parties. That's when
MTS - AV: the implementation
MTS - AV: activity actually starts
MTS - AV: and everybody goes off. And then we're designing processes and changing building new systems to
MTS - AV: basically implement the policy and then
MTS - AV: to be compliant with the policy language.
MTS - AV: And of course, at the end we'll have a celebration.
MTS - AV: And those of you
MTS - AV: who joined who helped me with the registration data policy for 5 years. Right? You all got your stickers.
MTS - AV: So look forward to your new sticker.
MTS - AV: So the way we are going to do the Pps AI and I call these work modules, and we're going to be
MTS - AV: kind of tackling this as modules of work.
MTS - AV: And the 1st thing, of course, is the final report review.
MTS - AV: This is a
MTS - AV: This will take some time, and it could get confusing.
MTS - AV: But I think we is the hard work that we expect all of you to do
MTS - AV: on your own.
MTS - AV: and when we do the final review report
MTS - AV: we will have discussions. But what I like to do is have that discussions and question and answers as much as we can
MTS - AV: using the email.
MTS - AV: So do not
MTS - AV: rely on the meetings only to have that discussion is what I want to ask you to do.
MTS - AV: The
MTS - AV: tell you more about how the Irt task and instructions will be given.
MTS - AV: and then we're going to be tackling what we call a threshold. Questions.
MTS - AV: There's some.
MTS - AV: There was like 3 important questions that the staff came up with.
MTS - AV: and we discussed this
MTS - AV: with the gns so console and
MTS - AV: and kind of vetted them to be an appropriate questions to be asking
MTS - AV: before we delve into implementation. Why?
MTS - AV: Because
MTS - AV: so much has changed
MTS - AV: since the last time we were implementing.
MTS - AV: Now, this is a new group
MTS - AV: and with a fresh set of eyes.
MTS - AV: Knowing today's
MTS - AV: landscape and the business environment.
MTS - AV: we want to make sure that we are asking the right question, and you should all be asking the question too.
MTS - AV: Let me know and share your questions
MTS - AV: with the Ir, T. And we will have an Ir T email list that we will establish. And we will use that to communicate
MTS - AV: on a daily basis. And of course, those of you who work with me on the registration data policy. You know how I work already. So it's not going to be different this time.
MTS - AV: But
MTS - AV: if you are new with me, then you will learn very quickly. The way I like to work is
MTS - AV: try to make it as much as I can quote unquote self-service model.
MTS - AV: I will provide
MTS - AV: and make available or information that I have
MTS - AV: to the IRT. And you can access them
MTS - AV: at any time.
MTS - AV: So these are the 3 questions, and I will not go over it there. But also.
MTS - AV: then we will analyze subject matter by subject matter, and I will show you what we think is the topic for the implementations in the workbook
MTS - AV: later.
MTS - AV: So
MTS - AV: this is sort of a pictorial view of how the recent or near term
MTS - AV: work will be
MTS - AV: first, st is sort of an introduction and education. Right?
MTS - AV: We're going to be talking about the final report.
MTS - AV: What does this recommendation means.
MTS - AV: and if there is interpretation of recommendation and there were be, and we ran into this a lot on just about any policy implementation. I was doing the recommendations. Language could be interpreted in a multiple, different ways.
MTS - AV: And it's very important to me and course to you that
MTS - AV: we consider or
MTS - AV: possible interpretation, document them and choose the appropriate interpretation.
MTS - AV: and share that openly. And I have a way of doing that.
MTS - AV: And
MTS - AV: you are all going to help me to do that for this policy.
MTS - AV: And then the scoping phase is what I would call
MTS - AV: you know, thinking about the policy, implementation, and design of the policy. Right? How should we
MTS - AV: take this implementation approach? This is when we're asking all these questions.
MTS - AV: quote unquote high level questions. And this will be challenging because the questions that we have to ask must be limited to the implementation of the recommendation language.
MTS - AV: not what we should do about privacy or
MTS - AV: proxy
MTS - AV: in general
MTS - AV: is is gonna be challenging. And you were. You will see what I mean. Because and it's part of Irt's duty
MTS - AV: when
MTS - AV: a discussion comes up and it evolves into quote unquote policy, making
MTS - AV: versus policy implementation.
MTS - AV: Expect all of you to raise your hands and stop me and what you know.
MTS - AV: Don't let me
MTS - AV: go on with that. And so, and and
MTS - AV: I know some of you are very good at, you know.
MTS - AV: watching carefully
MTS - AV: how we don't do policy and policy development here
MTS - AV: and those of you who have been involved in the Pdp working group. This will be challenging for you because this job is completely different than
MTS - AV: Pdp working group job where you were developing policy. Right?
MTS - AV: So now make sure that you're in the implementation mindset when you come here
MTS - AV: to work with us.
MTS - AV: And then there is what I would call sort of a decision point
MTS - AV: where we have to decide. Are we going to implement it this way or that way, and when I looked at it
MTS - AV: with our internal team there's a big.
MTS - AV: great spectrum of what we possibly could do.
MTS - AV: One extreme to another.
MTS - AV: and we're going to be thinking about that together
MTS - AV: and choose the optimum implementation. Approach the design, the path.
MTS - AV: And I would need your help there, too.
MTS - AV: though
MTS - AV: you know. I've been thinking about it for some time, but I want to make sure that there isn't a new approach
MTS - AV: that we are missing out, and maybe you can see that, and
MTS - AV: and help me with it, too.
MTS - AV: Let's talk about the
MTS - AV: logistics and tools.
MTS - AV: So IoT membership
MTS - AV: very easy to join.
MTS - AV: So those of you in the bat, and you're not sure whether you want to join.
MTS - AV: You might consider just joining.
MTS - AV: It's very easy right to the IRTR. svp@ican.org.
MTS - AV: and what you will get back is an acknowledgement
MTS - AV: with a request for you to sign a form.
MTS - AV: simple form
MTS - AV: with a statement of interest.
MTS - AV: Now, to
MTS - AV: end up as an official, IRT. You must publish
MTS - AV: post your. So I, because it's important for us to know when you are speaking, and when you are writing to the irt your affiliation, and I think that's a transparency we all need.
MTS - AV: and is is mandatory for the IoT.
MTS - AV: Oh, one thing is, it's not mandatory, is
MTS - AV: you do not have to belong to any stakeholder group.
MTS - AV: You can be an individual
MTS - AV: at any with the from anywhere.
MTS - AV: So I've had irt members
MTS - AV: who's not ever been to an IRT. Meeting.
MTS - AV: and not associated with any associate, any stakeholder group. But still we invite them to join us
MTS - AV: and
MTS - AV: help us
MTS - AV: with the implementation.
MTS - AV: And what we will use is IRT email.
MTS - AV: And this Ir T email will be used for a couple of things. Number one, of course.
MTS - AV: to have conversations
MTS - AV: email conversation among the IRT.
MTS - AV: And I. It will have all the Irt members and all the ipt for team members on it. And we're going to be talking about this implementation together.
MTS - AV: So one thing that I want to stress is
MTS - AV: when we are here. We are one implementation team. We are one team.
MTS - AV: right? I know we have stakeholder representative.
MTS - AV: And we were. We will use that representation when we need to. But
MTS - AV: I would like all of us to be
MTS - AV: a 1 team and trying to
MTS - AV: go in the same direction
MTS - AV: to find the best implementation we can.
MTS - AV: And of course
MTS - AV: it is my job
MTS - AV: to
MTS - AV: make that happen.
MTS - AV: So if you see anything wrong.
MTS - AV: okay, anything that is happening, please come to me. The Irt email will also be used to send
MTS - AV: meeting notices meeting invitation with the meeting information.
MTS - AV: The IRT. Meetings are
MTS - AV: limited for
MTS - AV: IRT. Members only.
MTS - AV: so only the Irt members can attend the meeting and participate.
MTS - AV: If you're a non irt member, you are not know about the meeting. An I can meeting is special, because at every I can meeting Irt me working meeting is public, and this is a special meeting where anybody can come and join us, but after this.
MTS - AV: until the next IRT. Session. At the next Ican meeting
MTS - AV: we will have many meetings, so if you're a public you will not know. Oh.
MTS - AV: what we were talking about when we're talking about it.
MTS - AV: Now, one thing about the IRT. Email.
MTS - AV: there is a status that you can choose. And this is what I recommend after you come to this 1st session and you decide.
MTS - AV: Maybe this is not for me, and maybe you know
MTS - AV: you do not have the bandwidth. This is much work, but you're still interested in tracking what's happening. You might consider an
MTS - AV: observer status.
MTS - AV: What that means is that you will have.
MTS - AV: You. You will have the ability to watch the emails flowing so you can see what's happening, what the discussion is.
MTS - AV: but you will not be able to participate
MTS - AV: in the
MTS - AV: IRT. Meetings.
MTS - AV: So let's talk about the meetings. Of course, at the Ican meeting. It's in person.
MTS - AV: and
MTS - AV: we are using zoom here, too.
MTS - AV: and we would use we would have a special zoom room set up for the Irt meetings outside of the Ican meetings.
MTS - AV: and that's what we'll do.
MTS - AV: Now, IRT. Workspace
MTS - AV: to do your work. I use 2 tools. One is the public Wiki space.
MTS - AV: and the other is what I call irt workbook. This may not be familiar with you familiar
MTS - AV: to you, so I'm going to show you what those things are
MTS - AV: so less
MTS - AV: are showing you.
MTS - AV: I think you're familiar with
MTS - AV: confluence.
MTS - AV: This is the Irt Wiki, and those of you who are
MTS - AV: have been participating.
MTS - AV: You will see
MTS - AV: that we have a gnso tab.
MTS - AV: and under the gnso tab
MTS - AV: we have all the
MTS - AV: links
MTS - AV: and
MTS - AV: the all the pdps
MTS - AV: and the implementation team.
MTS - AV: Thank you.
MTS - AV: So that's the
MTS - AV: that's the page.
MTS - AV: So you can find it. But of course, if you are an Irt member you'll be constantly
MTS - AV: posting. We'll be posting this link.
MTS - AV: because we will be using this as a space.
MTS - AV: So this is the
MTS - AV: homepage, and in the homepage it gives you status.
MTS - AV: some background and
MTS - AV: and maybe some meeting information. Then also we will have
MTS - AV: the meetings and agenda
MTS - AV: tab.
MTS - AV: We will keep track of every single meeting
MTS - AV: that IRT. Has.
MTS - AV: and it will have the agenda.
MTS - AV: the meeting material, and
MTS - AV: whatever
MTS - AV: else information that we need now keep in mind. This is public.
MTS - AV: so everybody can have access to this.
MTS - AV: besides the
MTS - AV: meeting and agenda about the meeting and agenda. What I do is I use
MTS - AV: the same space
MTS - AV: to post the agenda and the meet minutes, so I don't use a separate document for agenda or meetings, and I use, and it'll it'll just be here. So when I communicate with the Irt about the meeting. They'll be pointed to this wiki space
MTS - AV: where we can update our agenda as we go, and then you will find the minutes for that meeting.
MTS - AV: We maintain the Irt Member list here.
MTS - AV: So so far
MTS - AV: we have, I said. Let's see, let's go down quickly here
MTS - AV: till the end.
MTS - AV: Last person to join is Jeff Newman.
MTS - AV: we're missing is affiliation, and so I
MTS - AV: but
MTS - AV: we will go ahead and collect that from Jeff.
MTS - AV: But the important thing about this list is, if you should wonder
MTS - AV: who our Gns. So Council is
MTS - AV: is Stephanie Perrin
MTS - AV: and Paul Mcgrady.
MTS - AV: Oh, you joined us. Please introduce yourself.
MTS - AV: Morning, everybody. Paul Mcgrady. I am your genius. So council liaison to this
MTS - AV: working group. Apologies for being
MTS - AV: late. They have us triple scheduled this morning.
MTS - AV: And so I, the Stephanie and I are.
MTS - AV: I'm going to be keeping the Council up to date on how the work is progressing. We are also a
MTS - AV: another resource in the event that anybody thinks anything is going
MTS - AV: off, the rails feel free to reach out to either Stephanie or me.
MTS - AV: I will attend as many of these working group calls as I can, but I can't promise perfect attendance, and apparently I can't promise showing up on time, either. So thank you.
MTS - AV: Thank you, Paul.
MTS - AV: So, Paul and Stephanie.
MTS - AV: you, too, and I will be
MTS - AV: communicating on a regular basis.
MTS - AV: and
MTS - AV: check in with each other, even between the IRT. Meetings.
MTS - AV: to make sure that the 3 of us are in line, and if there's any kind of a communication that needs to happen to the Gnso.
MTS - AV: Paul and Stephanie, are
MTS - AV: the conduit to the gnso.
MTS - AV: so I don't go to the gnas so myself.
MTS - AV: It's our liaison who will do that for us.
MTS - AV: and we have Marge, Margie is our, as we heard, is the BC. Representative. Steve Essec is noted here. And let's see. And park yak.
MTS - AV: Brian.
MTS - AV: that is for our stakeholder.
MTS - AV: Okay, so you can find this page for our membership. And then this will be updated
MTS - AV: as we go.
MTS - AV: What else can I show you?
MTS - AV: I think that's that's for that is important. Now
MTS - AV: let me show you the workbook
MTS - AV: we call this the IRT. Workbook.
MTS - AV: and the about tab.
MTS - AV: Tells you what this is, that's what we're trying to do and how to use it.
MTS - AV: And then
MTS - AV: this also has a membership, and it has a sort of a different layout
MTS - AV: of our members.
MTS - AV: And this is the important part.
MTS - AV: This tab here.
MTS - AV: So IRT in its work
MTS - AV: is
MTS - AV: defined
MTS - AV: and focus and direct it.
MTS - AV: So I would ask you
MTS - AV: to help us, and exactly how
MTS - AV: we need the help.
MTS - AV: So it's not in general.
MTS - AV: but I would tell you, step by step, what I expect the ir to be irt to be
MTS - AV: doing between meetings.
MTS - AV: and
MTS - AV: when we need results from the irt. So 1st job.
MTS - AV: your homework
MTS - AV: is to submit the soi if you haven't submitted the so I. And if you're not going to submit the soi, what we will do is to not bug you about it, but we will just move you to an observer status, which means you can track
MTS - AV: our work. But if you're not doing the so, I we take that mean to
MTS - AV: mean that you you do not want to participate at the Irt level. And that's fine.
MTS - AV: That's not a problem.
MTS - AV: So 1st of all, I would like all of you to fill out that form and
MTS - AV: submit. And as but post your Si.
MTS - AV: Okay.
MTS - AV: next is
MTS - AV: the final report.
MTS - AV: of course.
MTS - AV: that's what I said. Right. This is
MTS - AV: this
MTS - AV: dot textbook, the Bible.
MTS - AV: if you will.
MTS - AV: that we will be working from.
MTS - AV: And
MTS - AV: this was produced by what they would the Pdp working group. Right?
MTS - AV: So here's another question.
MTS - AV: Who was a member of the Pdp working group that produced this final report? Let me see a show of hands?
MTS - AV: 3.
MTS - AV: Wow!
MTS - AV: That's great. Thank you so much for continuing to help us.
MTS - AV: When did you guys get started? What year do you remember when you started with the issues paper. Yes, that was after the arc rested on. Now Erat
MTS - AV: and the dove.
MTS - AV: anyway. This it's been a while I I think the date for me that is important is when it was published. I, you know, I think, is was very relevant in 2,016 when it was published. And I think that's the date that I have to keep in mind. How is the word change from 2,016 to 2024. When I look at this report.
MTS - AV: So this is
MTS - AV: how many pages is
MTS - AV: the long
MTS - AV: report?
MTS - AV: 93 pages.
MTS - AV: So
MTS - AV: IRT. Members must read.
MTS - AV: or 90
MTS - AV: 3 pages. And one thing that I will listen carefully for, and I hear this time to time is that
MTS - AV: somebody saying, an Irt member, saying.
MTS - AV: I have not read the final report, but
MTS - AV: this is a this is a red flag for me, because if for us to have a meaningful, productive discussion.
MTS - AV: We all have to know what the recommendations language says, so that when we produce our policy language.
MTS - AV: then we can talk about how
MTS - AV: it is if a line or not align.
MTS - AV: so 1st stop for you is
MTS - AV: final report. Now this, let me tell you about the due dates.
MTS - AV: so I decide on the due date, and and I push it out.
MTS - AV: And the way I push this assignment out is using the IRT email.
MTS - AV: So all IRT. Members get the assignment at the same time
MTS - AV: with the due date.
MTS - AV: and this is my request that you finish this homework by this time.
MTS - AV: But
MTS - AV: if there is a reason why you need more time.
MTS - AV: please let me know. Because
MTS - AV: yes, things happen right? Typically, if the Ican meetings happens in the middle of
MTS - AV: that period, and you need more time, or you need to maybe talk to your colleague to do some research. Please let us know, because we do revise due days
MTS - AV: per your request. And as as you need us to do
MTS - AV: the
MTS - AV: second homework.
MTS - AV: so the 1st one or the final report, let's just so make sure.
MTS - AV: July 10, th
MTS - AV: the next month. 10.th
MTS - AV: Oh.
MTS - AV: let me see a reaction.
MTS - AV: Not those of you who wrote this thing, but those of you who
MTS - AV: never read this thing. Do you think that's a reasonable
MTS - AV: due date?
MTS - AV: Okay? Got thumbs up? Good. I wasn't totally
MTS - AV: pulling.
MTS - AV: so we'll get to know each other. Well, but I have a tendency to drive things, and maybe more demanding, and I don't mean to be pushy, but you can push back, and I'm just fine with that Sarah and I've been
MTS - AV: doing this for a while together. She's the one who who's very good about
MTS - AV: you know.
MTS - AV: changing days as we need to. Now, next is the
MTS - AV: we call this thing implementation analysis.
MTS - AV: So the staff here has done an analysis of the recommendations recently, this is a recent document.
MTS - AV: So this document
MTS - AV: moved
MTS - AV: looks like this.
MTS - AV: and
MTS - AV: it goes through
MTS - AV: all the topics, is designed by topics.
MTS - AV: and
MTS - AV: what we feel is sort of the level of the complexity.
MTS - AV: difficulty of implementation, the things that are easy to do, hard to do there are more significant in terms of complexity and needing to discuss, perhaps.
MTS - AV: and
MTS - AV: this is our 1st cut at what we think the recommendations
MTS - AV: language says
MTS - AV: for implementation.
MTS - AV: and this will take some time for you
MTS - AV: to read.
MTS - AV: But
MTS - AV: you're reading. You're reviewing our analysis right? We're not asking you to go ahead and
MTS - AV: read the final report and produce an anonymous report for us. No, that's our job. We did that.
MTS - AV: Now your job is to review our work. Did
MTS - AV: did we do this correctly? I mean it was was there anything. That is what I call. And I I continued to use the misaligned with the recommendations language.
MTS - AV: and there's a difference.
MTS - AV: There's a total misalignment
MTS - AV: not
MTS - AV: complying with the recommendation. Language versus
MTS - AV: a different approach. Right? Perhaps.
MTS - AV: Yes, what we did was align. But maybe there's a different interpretation and different approach. So we're going to be listening carefully
MTS - AV: for that subtle teeth as we do our analysis.
MTS - AV: So this document.
MTS - AV: is pretty thorough, and it took
MTS - AV: it took months
MTS - AV: literally right
MTS - AV: for us to do this.
MTS - AV: and last of us
MTS - AV: internally, has gone through this.
MTS - AV: and not only the core team, as I said, but the extended team has gone through
MTS - AV: this. And now we end up with 34 pages
MTS - AV: of our analysis document. But if you notice
MTS - AV: the due dates.
MTS - AV: this is designed intentionally
MTS - AV: to be after you finish your recommendations
MTS - AV: review.
MTS - AV: So the 1st thing you got to do is read the final report right? Understand that.
MTS - AV: and then come to this analysis and
MTS - AV: look at the analysis report.
MTS - AV: Okay.
MTS - AV: so is about 2 weeks after the due date of the final report
MTS - AV: analysis. Okay.
MTS - AV: so this is a task list
MTS - AV: and the other tab that we will carry. Is this work plan? I called.
MTS - AV: And you've seen
MTS - AV: some of this.
MTS - AV: But here is where we
MTS - AV: we'll go ahead, and each individual topic is our work module, and we will approach this together and talk about it and get through it, or and
MTS - AV: all the
MTS - AV: the topical by recommendation and by requirement is what we'll be discussing. And this is where we we will be adding the work modules as we go. So this is our 1st meeting. This is a start.
MTS - AV: but I'm
MTS - AV: showing you what we've done so far, and letting you know this is where we will do the work in the future.
MTS - AV: This is a meeting attendance.
MTS - AV: so note that we will be taking attendance.
MTS - AV: so everyone who attend will get a 1, and we will keep track of how many people attended each session.
MTS - AV: and how many meetings you have attended, and whether or not you were at that meeting or not when we talked about a certain topic.
MTS - AV: And here is another requirement for the Irt. If you miss submitting
MTS - AV: meeting will be recorded
MTS - AV: and documented, and with full transcript, is your job
MTS - AV: to catch up with the rest of the Ir. T. By
MTS - AV: listening to the
MTS - AV: recorded session.
MTS - AV: Okay?
MTS - AV: And
MTS - AV: so you can come here and look at this. Now about this workbook. Only the Irt members have access to the workbook. And this this is an editable workbook tool. So you can edit as much as we can edit, and that's fine.
MTS - AV: and we'll work at it together. And when we start talking about timeline.
MTS - AV: this is where we were kind of a sketch out our timeline. Now, 1st question that you will all get
MTS - AV: right outside this meeting, because you're part part of the IRT. When you go back
MTS - AV: they're you're all going to be asked, how long is this going to take?
MTS - AV: Okay? The
MTS - AV: the true answer is that I don't know
MTS - AV: if I don't know if you know, maybe you can tell me, but
MTS - AV: I don't think that we can
MTS - AV: say how long it's going to take, because
MTS - AV: to
MTS - AV: figure out how long a implementation project will take, we have to 1st scope
MTS - AV: the project. Right?
MTS - AV: So this is what I meant by. Let's study the requirements.
MTS - AV: Let's understand the requirement and then scope out
MTS - AV: the project. Then we can
MTS - AV: sketch out our timeline
MTS - AV: and we'll do that together.
MTS - AV: Not a surprise to anyone, and I would make sure that I get plenty of inputs from the Irt
MTS - AV: to make the project
MTS - AV: schedule
MTS - AV: achievable and realistic, right? Something that we can all support.
MTS - AV: This is sort of a 13 steps I sketched out, and I gave you one slide, but
MTS - AV: sort of the steps that I follow
MTS - AV: on. How a implementation.
MTS - AV: Yes, done. And then that's it.
MTS - AV: So this workbook is a free, flowing, changing, living document.
MTS - AV: and we will add to it and delete from it and make it useful for us.
MTS - AV: Any questions about the workbook
MTS - AV: is, is this new tool?
MTS - AV: Some of you?
MTS - AV: Yeah.
MTS - AV: Okay.
MTS - AV: So I think I talked about all the
MTS - AV: work tools.
MTS - AV: Email meetings, workspaces where you can find things.
MTS - AV: Now, is there anything else missing
MTS - AV: that as you, as we start doing our work? Do you feel like we need anything more than what we have here that you've seen.
MTS - AV: Question to the IRT.
MTS - AV: This Rogers. Thanks, Dennis. Just a question on the workbook, since it's Air T. Only. Are you sending that link? Once we leave here to that to the mailing list?
MTS - AV: Then I said, yes.
MTS - AV: yes, I said, yes, so Irt email will be created. And to get on the Irt email one more time you must
MTS - AV: post your. So I
MTS - AV: if you don't post your sla. You will not be on the email, and you will not get the access to these working tools.
MTS - AV: That's very important.
MTS - AV: And once you, we will. Once we work together, this will be very, very familiar to you is going to be a daily activity. Almost.
MTS - AV: Okay.
MTS - AV: So let's talk about next steps.
MTS - AV: So
MTS - AV: when you
MTS - AV: leave this room.
MTS - AV: you're going to be studying the
MTS - AV: what? What are we gonna study the final report right?
MTS - AV: The final report. Where do you find the final report
MTS - AV: you're not on the IRT. Email yet.
MTS - AV: So how would you know where to go? Find the Ir team.
MTS - AV: find find the final report. Let me see if anybody
MTS - AV: has an answer for my question. You're you want to join the Irt.
MTS - AV: Well, one easy way was. It was linked in the call for the IRT. Membership.
MTS - AV: Hmm.
MTS - AV: who does not have access to the final report.
MTS - AV: I don't see a single hand. This is a good sign.
MTS - AV: Everybody knows how to get to it, and that means you can start your homework today.
MTS - AV: Perfect. Thank you. And of course the other homework assignments. That's on the list, right on the workbook that
MTS - AV: I showed you
MTS - AV: the these slides that will be posted on the wiki after the meeting, so you can look at this again
MTS - AV: the and then let's see.
MTS - AV: the next Irt meeting is what I was thinking about. And I was thinking that tentative tentatively, we're gonna Target 11 July on Thursday. I don't know if Thursday is a good day for all of us, and this is one of the challenges
MTS - AV: finding the optimum time slot for all IRT.
MTS - AV: Extremely difficult.
MTS - AV: but we have to try and do the best we can.
MTS - AV: So I picked this time slot, and there will be a port sent out to the Irt members, and
MTS - AV: we will see if this slot works on another slot works better. But we can be flexible, but what I like to do is set a time slot
MTS - AV: and stay with it.
MTS - AV: and that, I find, is
MTS - AV: easiest. Instead of trying to change it as we go.
MTS - AV: and next time we meet the agenda will be
MTS - AV: the
MTS - AV: recommendations language right?
MTS - AV: Your reaction to it.
MTS - AV: questions about it.
MTS - AV: And I would like to have a very comfortable feeling that everyone is on the same page on the Recommendations language.
MTS - AV: and that is
MTS - AV: our goal for our next meeting.
MTS - AV: Dennis. It's David Hughes. How long do you plan to have each one of these sessions?
MTS - AV: 1 h sessions, is you? Is that what you're gonna start with?
MTS - AV: That's a good question. Actually, I know that I started with 90 me sessions, and then we cut it back to 1 h session as we.
MTS - AV: and then we kind of modulated the frequency as well.
MTS - AV: And now that's your first, st let me hear your 1st input. How long should our sessions be to get started? Go ahead.
MTS - AV: So Steve is asking, What is the cadence?
MTS - AV: What do you think?
MTS - AV: Give me some inputs?
MTS - AV: Well, my 1st input is that if the 1st call is an hour.
MTS - AV: We're not going to even finish the 1st discussion, probably, but
MTS - AV: it's just my gut feeling
MTS - AV: at the beginning. I think what you said before was, start with longer calls more frequently and then
MTS - AV: shorten them and make them less frequent. If things are going well.
MTS - AV: Steve, do you have an input
MTS - AV: we've got a sizable group here, so that slows things down just naturally. No, you're you're driving. This is fine. I was waiting to see whether or not you had a cadence whether it was weekly bi-weekly, whatever you've given us 4 weeks from today to for the next meeting, but I presume that things are going to speed up after that.
MTS - AV: Yeah, I think it depends a lot on the Irt whether the Irt is responsive and they can have a meaningful productive conversation online, using the emails
MTS - AV: or more of this, Irt has the characteristics of a a talking irt. And you need that.
MTS - AV: So it's highly tailored to each irt and the job on hand. So the reason that I gave 4 weeks right is is a maybe a long time is to make sure that
MTS - AV: number one. You had enough time and plenty of time to review the final report, but also to give the opportunity for other people to join the Irt. And I've while I'm here.
MTS - AV: I noticed that a lot of people didn't know that we are starting this Irt. There was an announcement made
MTS - AV: right and a blog written, but of course you know not. Everybody is attentive. So I'm looking in the back, and we're going to be starting the community. Q. And a
MTS - AV: anybody who wants to join the Irt you have a chance to join, and if you join, then you'll still have enough time to do. Your 1st homework is what I was thinking
MTS - AV: before we go to the public. QQQ. And a. I just want to leave you with this one slide. Go ahead.
MTS - AV: Thanks, Dennis. I I know you said. We can't know how long this is going to take without scoping it out.
MTS - AV: When will we know how long. It's gonna take.
MTS - AV: I mean, because we I mean, I don't think anybody I mean, it's not fair
MTS - AV: to ask people just to write a blank check to forever land
MTS - AV: right on an irt, and so like, when when will we? What's the point at which we know
MTS - AV: how much longer it's going to take? Because every other working group I've ever been on has a working plan that you work against, and if you start to slip, then you know you're in trouble.
MTS - AV: So what? What? When will we know the timing? Thanks. So let me give you another homework. Then
MTS - AV: our next meeting is being targeted for
MTS - AV: tentatively right on July 11, th
MTS - AV: and
MTS - AV: by that time you should have finished reviewing the final report.
MTS - AV: but not have done any analysis yet.
MTS - AV: and if you look at this chart. Here we have this
MTS - AV: scoping phase
MTS - AV: that we like to consider, and that's what I think we should be talking about
MTS - AV: timeframe.
MTS - AV: Now, of course, I can independently go and just set a time.
MTS - AV: But what I would like to do is
MTS - AV: ask the IRT. To help me to set a
MTS - AV: good, reasonable timeline for this implementation.
MTS - AV: There is a ton of expertise and experience in this room.
MTS - AV: I mean, you know, I mean, some of you have written this final report and worked on this implementation.
MTS - AV: You know much more about this than I do.
MTS - AV: though
MTS - AV: I would like your advice to me.
MTS - AV: Thanks. Can I just do a follow up real quick. So we look at 3 to 4 meetings and then 6 to 8 meetings. I, as far as I know, we've not settled on the cadence of the meetings.
MTS - AV: Right? So we've got it. So why don't we? Because this chart doesn't have any meaning to me?
MTS - AV: Is, if, because if our meetings are once a month.
MTS - AV: then that is a
MTS - AV: you know, that's a 1 year timeframe to get to the end of scoping. That seems nutty and are so
MTS - AV: well, I mean, I guess I don't understand why we can't answer these questions now, while we have any everybody in the room. And so and I'm sorry if I'm being way, too. Type a here, Dennis. But
MTS - AV: why not ask? Do do we want to meet once a week. Do we want to meet twice a week? And so that way we can attach numbers to these things and say, Okay, if it's if it's I mean not twice week, what you know once every 2 weeks. So if we know it's you know once every 2 weeks, then we know, you know we know what 3 to 4 meetings mean. We know what 6 to 8 meetings mean, and then we'll know what the end of the scoping phase is. So, thanks.
MTS - AV: Great point. Would love to hear from the rit on this. Karen was next. Go ahead, Karen.
MTS - AV: Sure. So. I think you know our intention from coming out of this kickoff meeting is, as Dennis said, to update the email list, send out the poll with regard to to scheduling and then be able to provide a work plan for the next. You know X number of meetings that follow the kind of general outline here.
MTS - AV: But but the thing I raised my hand to to say was.
MTS - AV: I guess, a little bit what Dennis said, but also, you know, the the establishment of a project plan with a timeline is is is
MTS - AV: essential. And what we envision here is that once we have answered the the threshold, questions right? We've decided. Are there any
MTS - AV: policy questions that are going back to the Gina? So that affects the timeline? Are, are we agreed on? You know we've agreed on what particular model. We're using that. Then we can build a timeline based on that. So that decision point that big line is where we establish. Then this is this is the time that it takes for the rest of the project our estimate for the 1st
MTS - AV: 1st 2 pieces, you know. Again, it will vary a little bit, depending on how long we take to discuss those questions. But it's shouldn't take longer than I would say a quarter or quarter and a half, maybe.
MTS - AV: Thanks.
MTS - AV: But yeah. My! My comment was.
MTS - AV: where do we want to be when we meet again in person, in Istanbul in terms of this line, and maybe we can just use that to determine our cape.
MTS - AV: That's a good way to think about it. Yes.
MTS - AV: I'm sorry, Brian, next. Why don't you introduce yourself, Brian? Good morning, Brian Beckham, for the record and and apology that I was sitting in the back
MTS - AV: earlier. 1st of all, happy birthday, Owen. And
MTS - AV: and also to you
MTS - AV: and
MTS - AV: I my my question was, and when you mentioned the homework for the 1st meeting, and and Paul mentioned scoping. And then I think Karen sort of answered the question and and mentioned a potential need to go back to council.
MTS - AV: If there were any policy questions, which, of course, raises its own question, because this is by its name and implementation group of an existing policy recommendation. So I guess what would be helpful for me at least, is if you could point us to any guidance on
MTS - AV: how that concept of if there are policy questions
MTS - AV: that have
MTS - AV: newly emerged from the existing recommendations that would need to go back to council.
MTS - AV: Are, are there guidelines for how to to size that up otherwise. It. It strikes me as pretty clear from the title that this is here to implement existing policy. And so I'm just kind of curious the contours of of you know this, this question that Karen raised.
MTS - AV: Okay, we'll discuss that. But let me see, Alan, you wanted to speak.
MTS - AV: Actually, Brian covered what I just wanted to ask that we're here to implement
MTS - AV: recommendations. But the threshold questions which we're supposed to look at 1st
MTS - AV: very clearly, say, are these the right policy recommendations? Does anything need to be changed? Does anything need to be added? Which clearly, if the answer is yes to any of that
MTS - AV: is really going to skew what we're doing going forward.
MTS - AV: I mean, if we decide, this recommendation needs to be added or changed.
MTS - AV: it would be foolish for us to then carefully implement it in detail, knowing that something's going to be different. So how do.
MTS - AV: how do we handle that? I mean, this is not normal for an Irt.
MTS - AV: Well, actually, it's not that unusual, but the Irt when we run into issues like that. And we do.
MTS - AV: if you need to consume.
MTS - AV: consult gns. So we have the gns or liaison exactly for that.
MTS - AV: And that's why Paul's here, Stephanie, is our. We have 2 gns so lias on, and we'll be talking about it. And if we feel the need to.
MTS - AV: we have a channel built into the Ir T process.
MTS - AV: you know it. It just struck me that
MTS - AV: accidentally discovering something along the way is very different from asking the questions at the very beginning. So
MTS - AV: yeah, so exact. That's exactly why we have this at the beginning? So that if there are areas that are going to potentially need to go back to the Council for guidance that we do that at the front and not midway
MTS - AV: through. But here's maybe an example. So we've you know, we've tried to make this not just sort of an open, ended question in terms of what policy issues would people like to discuss? But rather, is there something in the final report?
MTS - AV: We're in the tech in the recommendations we're in the text that raises questions about, does this does this work anymore? Does this make sense anymore? Potential example? The there's a request or a reference for
MTS - AV: somebody to be able to request either to reveal or publish registration data. And there's been a lot of work going on in the you know, disclosure area. But the concept of publishing somebody goes, you know, to a contracted party and says, I'd like to submit a request for this to be published.
MTS - AV: this data to be published. Does that work anymore? Does that make sense anymore? Right. But that's what the policy says. So it's those kind of questions is in terms of, you know. Is there a different way to do this to to implement the spirit of this, or does, or to have some of the
MTS - AV: events that have occurred in the last several years since we worked on this? Do they raise more questions? So that's what we're trying to get at in this in this number one.
MTS - AV: Steve, did you want to speak? Go ahead. Yeah. So the the question that
MTS - AV: and Brian's raising and that Alan is speaking to so we have a the form of the question was, well, what happens if existential questions, or that
MTS - AV: are raised in the in this process where we can't find a way forward because there's something flawed within the policy itself. And what is our procedure for raising that? And that was the question.
MTS - AV: So in a
MTS - AV: bonding experience between Dennis and me in the last irt that we participated in we had such an issue raised with respect to the notion of quote urgent requests in the in the matter of
MTS - AV: the the Epdp policy implementation
MTS - AV: and so I I, too, was puzzled as to what the process was for that, and it took
MTS - AV: multiple attempts. And finally we found what the
MTS - AV: process turned out to be
MTS - AV: which was multiple attempts within the scope of an Irt. The answer was, we can't make any changes. We can't make any changes. We can't make any changes. We can't make any changes, because that would require going back and reopening the policy development process. And we don't want to do that.
MTS - AV: So went
MTS - AV: around in other quarters and published a document out of sack about the notion of fit for purpose.
MTS - AV: and managed to get the idea of, if something's not fit for purpose, that in some sense trumps
MTS - AV: pardon that word the basic assumptions about consensus, multi-stakeholder, bottom up process, and so forth.
MTS - AV: And the net of it is which has been published and and the
MTS - AV: Published with a little bit of soft landing. But basically the the board, not the Gnso Council, but the board
MTS - AV: interacted with various parties, and the net of it was that that requirement was been removed from the policy set aside to be determined later. Basically, so in
MTS - AV: in simple terms, a sort of rocket to the top, and a small explosion, and that got dealt with.
MTS - AV: So there's your process.
MTS - AV: Thanks. So the reason why these questions are upfront.
MTS - AV: Is a couple of things. One. The Council doesn't want us to spend.
MTS - AV: You know. However long it takes to get to the end of the implementation implementation process
MTS - AV: only to have
MTS - AV: years of work thrown away because there has been a law change.
MTS - AV: That that was knowable at the beginning of this process.
MTS - AV: And if there haven't been any law changes or anything to the ecosystem that we need to worry about great, we'll move forward.
MTS - AV: If there are things that need to be considered better to do it now.
MTS - AV: The Council has in its toolbox all kinds of things that are not Pdps
MTS - AV: in terms of being able to resolve questions like that. I don't think anybody would be particularly happy if we spent a couple of years doing this only to find out we had to scrap it.
MTS - AV: So that's the reason why they're up front. Agree, Brian, normally, you would just plow through this and and see what you see.
MTS - AV: But as the manager, you know, you know the Council wants to be a good
MTS - AV: manager of of time. Also it goes to council workload. And you know, if there are issues that need to be resolved that has to be baked into all the other work that Council's doing so.
MTS - AV: It. It is meant to be
MTS - AV: a way to make sure that we keep moving
MTS - AV: and that at the end of the day we have something that is actually implementable. It's not meant as a delay. And I hope you guys can tell from the tone of my voice this morning. I don't want any more delay on this than than we've already. We've had years and years and years of forgive me, staff, delay and it's time that we get this across the finish line. So I understand the skepticism because it's working a little bit different.
MTS - AV: But I will say that if if
MTS - AV: people don't take the time to read the report, consider the ecosystem, and don't raise the issues at the beginning. If we will all have long memories on this, and if they you know, if folks start to lob grenades into the mix, you know, at the 10th hour.
MTS - AV: you know, we will say there was an opportunity to raise these issues right?
MTS - AV: So it's incumbent upon that anybody. It's coming on everybody to do their homework. And that's 1 of the reasons why Dennis has given us a month
MTS - AV: to do the initial homework. It's not because the report's long. It's because he wants you to read the report.
MTS - AV: talk to the people in your constituencies, and Sgs and Acs
MTS - AV: find out whether or not they see any issues. Find out whether or not you see any issues
MTS - AV: read up on the wall right, and come back fully informed and ready to talk.
MTS - AV: But it's going to be important to raise the issues early, so that Council can resolve them if they need to be resolved. So thanks. Hope that's helpful.
MTS - AV: very helpful. Thank you so much. Who's next?
MTS - AV: Thanks, Dennis. Just Roger. I I appreciate the question here, and it is interesting that this question's first.st But having worked in an Irt multiple times.
MTS - AV: this question is a constant question as you work through an irt. So I'm surprised that there's so much
MTS - AV: discussion around it, because this is a constant question on every step of an irt. So every irt I've worked on has
MTS - AV: not openly started with this. But this question exists in every IRT. So thanks
MTS - AV: anyone else.
MTS - AV: Nope.
MTS - AV: nothing, nothing on the chat.
MTS - AV: Okay, so let's go to the public open. Q&A session. So
MTS - AV: the public here
MTS - AV: and online is now invited to ask questions
MTS - AV: about
MTS - AV: the policy implementation, the process about the team. And you can ask questions to me or to staff. Yeah.
MTS - AV: And the Ir. T, that we have around the table and online.
MTS - AV: And hmm.
MTS - AV: we'll see if we can cover all the questions.
MTS - AV: Let's see, how much time do we have left? I think we got plenty of time. Right?
MTS - AV: 8 min. That's fine. Okay.
MTS - AV: let me see. Any questions from anyone here.
MTS - AV: Okay, thank you so much.
MTS - AV: I don't have any issue or any problem of ending the meeting early.
MTS - AV: I know that this was a what 60 plus 1575 min session, and we got through all the agenda, and we answer all of your questions hopefully. And you
MTS - AV: now, what we have done is set the expectation with you of what the work is.
MTS - AV: so please join us in the back and help us do this work
MTS - AV: and
MTS - AV: do your homework, and as soon as I get the IRT. Email set up.
MTS - AV: we're going to be start
MTS - AV: having a conversation.
MTS - AV: So look for that to come next
MTS - AV: from us.
MTS - AV: Thank you. Everyone.
MTS - AV: Go ahead and
MTS - AV: stop the recording.