[IFR2-team] Agenda: IFR2 meeting 10 January 2024 @ 01:00 UTC

Thu Jan 11 11:50:46 UTC 2024

I am sorry, I also missed yesterday’s meeting, which was not in my
calendar. Please could you re-send the invitations.

Regards,
Alan Barrett

On Wed, 10 Jan 2024 at 20:00, Brenda Brewer <brenda.brewer at icann.org> wrote:

> Hello Rajiv,
>
>
>
> The calendar invite was sent from me, Brenda.brewer at icann.org. Future
> meeting dates are sent from my mailbox, also. Please let me know if you
> have not received and I am happy to send again.
>
>    - Meeting 4 - Tuesday 23 January @ 11:00 -12:00 UTC
>    - Meeting 5 - Tuesday 6 February @ 18:00 - 19:00 UTC
>    - Meeting 6 - Wednesday 21 February @ 01:00 - 02:00 UTC
>
> Kind regards,
>
> *Brenda*
>
> --
>
> Brenda Brewer
>
> Policy Operations Coordinator
>
> *I*nternet *C*orporation for *A*ssigned *N*ames and *N*umbers (*ICANN*)
>
>
>
>
>
>
>
>
>
> *From: *IFR2-team <ifr2-team-bounces at icann.org> on behalf of IFR2-team <
> IFR2-team at icann.org>
> *Reply-To: *Rajiv Prasad <rajivprasad at google.com>
> *Date: *Wednesday, January 10, 2024 at 9:27 AM
> *To: *Jennifer Bryce <jennifer.bryce at icann.org>
> *Cc: *IFR2-team <IFR2-team at icann.org>
> *Subject: *Re: [IFR2-team] Agenda: IFR2 meeting 10 January 2024 @ 01:00
> UTC
>
>
>
> Apologies, all. I missed the meeting due to a prior engagement.
>
>
>
> Quick question - was an invitation sent out for this meeting from
> policycalendar at icann.org (or something else)? I did not see an invite for
> this meeting with the Zoom meeting link.
>
>
>
> On Tue, Jan 9, 2024 at 3:09 PM Sami Mohamed Ali via IFR2-team <
> ifr2-team at icann.org> wrote:
>
> Dear Team
>
>
>
> Unfortunately will not be able to attend the meeting.
>
>
>
> Will review the discussion points and comment accordingly if required.
>
>
>
> Regards
>
> Sami
>
>
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------
>
> *From:* IFR2-team <ifr2-team-bounces at icann.org> on behalf of Jonathan
> Robinson <jonathan.robinson at identity.digital>
> *Sent:* Tuesday, January 9, 2024 12:56:06 PM
> *To:* 'Jennifer Bryce' <jennifer.bryce at icann.org>; IFR2-team at icann.org <
> IFR2-team at icann.org>
> *Subject:* Re: [IFR2-team] Agenda: IFR2 meeting 10 January 2024 @ 01:00
> UTC
>
>
>
> You don't often get email from jonathan.robinson at identity.digital. Learn
> why this is important <https://aka.ms/LearnAboutSenderIdentification>
>
> Dear Colleagues,
>
>
>
> Thank-you for the agenda. I will not attend the meeting tomorrow, please
> accept my apologies.
>
>
>
> I will review the agenda and audio and provide any appropriate input I may
> have.
>
>
>
> Jonathan
>
>
>
> *From:* IFR2-team <ifr2-team-bounces at icann.org> *On Behalf Of *Jennifer
> Bryce
> *Sent:* Monday, January 8, 2024 12:42 PM
> *To:* IFR2-team at icann.org
> *Subject:* [IFR2-team] Agenda: IFR2 meeting 10 January 2024 @ 01:00 UTC
>
>
>
> Dear IFR2 members,
>
>
>
> Included is the agenda for the next IFR2 team meeting, scheduled for
> Wednesday 10 January @ 01:00 UTC.
>
>
>
>
>
> *Second IANA Naming Function Review** (IFR2**) Meeting 3*
>
> 10 January 2024 | 01:00 UTC – 02:00 UTC
>
> *Agenda *
>
>
>
>    1. *Welcome, Roll Call, SOI updates *
>
>
>
>    1. *Introduce technical writer, Elizabeth Garber*
>
>
>
>    1. *Action Items *(all action items tracked in the Google sheet linked
>    here
>    <https://docs.google.com/spreadsheets/d/1DFJ30deCZoV7ictJ-sNw3LXzBhp8TMkp/edit?usp=sharing&ouid=108339081225436447454&rtpof=true&sd=true>
>    )
>
>
>
> *Reference *
>
> *Date *
>
> *Action item *
>
> *Status *
>
> 02-01
>
> 5 Dec 2023
>
> Based on Doodle poll results and team discussion at the 5 December
> meeting, ICANN team to schedule the next call for 10 January 01:00 UTC.
>
> Complete
>
> 02-02
>
> 5 Dec 2023
>
> ICANN team to share the Terms of Reference from the first IFR. For the
> review team to call out the specific areas and questions for discussion so
> that an agreement can be reached on the next call.
>
> Redline Terms of Reference shared via email 4 Jan – to be approved on an
> upcoming call or on list.
>
> 02-03
>
> 5 Dec 2023
>
> ICANN team to make sure that the URL on the wiki is separate from the
> first IFR wiki.
>
> Complete
>
> 02-04
>
> 5 Dec 2023
>
> ICANN team to work with Co-Chairs on an agenda for the next meeting and
> share it in advance.
>
> Complete
>
> 02-05
>
> 5 Dec 2023
>
> ICANN team to start working with Co-Chairs on getting the briefings lined
> up. They will start with a briefing at the next meeting.
>
> In progress – IANA briefing scheduled for 10 Jan, next briefing on the CSC
> (Brett) to be scheduled.
>
> 02-06
>
> 5 Dec 2023
>
> ICANN team to come up with suggested meeting plan for January, February,
> and early March to share with the team—that way the review team members can
> check their calendars and send their apologies in advance.
>
> In progress – calendar invites sent up to March – content planning with
> Co-Chairs in progress.
>
> 02-07
>
> 5 Dec 2023
>
> ICANN team to work with the co-chairs to investigate how best to allow
> meeting access to observers.
>
> Proposal included in the Terms of Reference draft document.
>
> 02-08
>
> 5 Dec 2023
>
> For the ICANN team to go back and see if there was a blog published to
> announce the first IFR and if so, republish a similar blog for IFR2.
>
> IFR1 blog published at team approval of Terms of Reference document.
>
>
>
>    1. *IANA Services Overview – IANA team *
>
>
>
>    1. *Next Meetings *
>
>
>    - Meeting 4 - Tuesday 23 January @ 11:00 -12:00 UTC
>    - Meeting 5 - Tuesday 6 February @ 18:00 - 19:00 UTC
>    - Meeting 6 - Wednesday 21 February @ 01:00 - 02:00 UTC
>
>
>
>    1. *AOB, close *
>
>
>
>
>
>
>
> Best,
>
> Jennifer
>
> --
>
> Jennifer Bryce
>
> Project Manager, Office of the Chief Technology Officer (OCTO)
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> www.icann.org
>
> _______________________________________________
> IFR2-team mailing list
> IFR2-team at icann.org
> https://mm.icann.org/mailman/listinfo/ifr2-team
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
>
>
> --
>
> Rajiv Prasad.
> _______________________________________________
> IFR2-team mailing list
> IFR2-team at icann.org
> https://mm.icann.org/mailman/listinfo/ifr2-team
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/ifr2-team/attachments/20240111/09fa134b/attachment-0001.html>