[NCUC-EC] [Ext] Re: issue Forum Status?
Andrea Glandon
andrea.glandon at icann.org
Wed Jun 5 23:01:17 CEST 2024
Hello all,
The staff members who can update the description in the schedule is going to start traveling tomorrow. Please let me know when the description is ready for posting.
Thanks!
Kind Regards,
Andrea
From: NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> on behalf of Ken Herman <ken at kherman.com>
Date: Wednesday, June 5, 2024 at 14:45
To: 'Pedro de Perdigão Lana' <pedrodeperdigaolana at gmail.com>
Cc: "ncuc-ec at lists.ncuc.org" <ncuc-ec at lists.ncuc.org>, 'farzaneh badii' <farzaneh.badii at gmail.com>
Subject: [Ext] Re: [NCUC-EC] issue Forum Status?
Thanks again, Pedro. Agree we should try and keep the communications consolidated.
Got it that Kathy wants to speak last. All of the documents you refer to are very useful, especially the NCSG statement, which I had not seen before.
Regarding the actual running of the event, beyond my transfer policy brief presentation (many changes to transfer restrictions, aka “locks”), I am available to do whatever the group feels will be helpful. I can do a brief introduction, basically based around the ICANN policies in the 2013 document with a reference to the NCSG statement, and introduce speakers. I would expect Benjamin to come in at some point, perhaps as a wrap-up at the end to summarize and thank everyone?
Ken
From: Pedro de Perdigão Lana <pedrodeperdigaolana at gmail.com>
Sent: Wednesday, June 5, 2024 1:15 PM
To: Johan Helsingius <julf at julf.com>; Ken Herman <ken at kherman.com>
Cc: Benjamin Akinmoyeje <benakin at gmail.com>; ncuc-ec at lists.ncuc.org; farzaneh badii <farzaneh.badii at gmail.com>
Subject: Re: [NCUC-EC] issue Forum Status?
Coming back to this thread (btw, I think we should avoid creating others and centering them all just in one so it's easier to find information) to share with you Kathy's slides (she may still change something there),
@Ken Herman<mailto:ken at kherman.com>, Kathy also asked to be last to speak, so she may dialogue with others before her.
In the conversation we had, talking a bit about the idea of "registrants rights", because it is not well defined within the ICANN ecosystem (we don't need to try to conceptualize it, just remembering how important it is to debate it again and move forward) and it seems like there is an important gap during the last 10 years. Some background is available here<https://www.icann.org/resources/pages/responsibilities-2014-03-14-en>, with a previous NCSG statement here<https://community.icann.org/download/attachments/29591060/Registrants%27_Real_Rights_and_Responsibilities.pdf?version=1&modificationDate=1368650508000&api=v2>, while the current policy is available here<https://www.icann.org/resources/pages/benefits-2013-09-16-en>. Do you all thing this is an interesting starting point? (and, just to be sure, Ken, you'll be doing the introduction or someone else from the NCUC?)
Cordially,
Pedro de Perdigão Lana
Lawyer [nic.br]<https://urldefense.com/v3/__https:/www.nic.br/__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq262ZnOgK-A$>, GEDAI/UFPR [gedai.com.br]<https://urldefense.com/v3/__https:/www.gedai.com.br/__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq260VJ0_MbQ$> Researcher
PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
Board Member @ NCUC (ICANN) [ncuc.org]<https://urldefense.com/v3/__https:/www.ncuc.org/__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq26387ikI1Q$>, ISOC BR [isoc.org.br]<https://urldefense.com/v3/__https:/isoc.org.br/__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq263s1BAauA$>, CC Brasil [br.creativecommons.net]<https://urldefense.com/v3/__https:/br.creativecommons.net/__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq263lEJKxTA$> and IODA [ioda.org.br]<https://urldefense.com/v3/__https:/ioda.org.br/__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq260gnUJVFA$>
This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it.
Em seg., 3 de jun. de 2024 às 16:33, Johan Helsingius via NCUC-EC <ncuc-ec at lists.ncuc.org<mailto:ncuc-ec at lists.ncuc.org>> escreveu:
Unfortunately it seems there is a conflict with a RrSG "all hands
on deck" session.
Was there any contact with the RrSG before I contacted their
leadership? I would have expected them to flag the conflict...
Julf
On 29/05/2024 17:28, Benjamin Akinmoyeje wrote:
> Dear Julf,
> Thank you for offering to help invite RrSG leadership. Any assistance
> would be greatly appreciated in getting the audience and speakers to
> participate.
>
> Farzii is also reaching out to some stakeholders as well.
>
> All hands are needed here.
>
>
> Kind regards,
> Benjamin
>
> On Wed, May 29, 2024 at 1:20 PM Johan Helsingius via NCUC-EC
> <ncuc-ec at lists.ncuc.org<mailto:ncuc-ec at lists.ncuc.org> <mailto:ncuc-ec at lists.ncuc.org<mailto:ncuc-ec at lists.ncuc.org>>> wrote:
>
> Benjamin, Ken,
>
> Let me know if you need me to talk to the RrSG leadership.
>
> Julf
>
>
> On 29/05/2024 05:13, Ken Herman wrote:
> > Dear Benjamin, Thank you.
> >
> > As one of the participants, I remain available to provide additional
> > input, beyond the input I already provided. However, since the theme
> > seems to require participation by registrars, I ask, again, if
> you, in
> > your capacity as Chair of the NCUC, will be reaching out to the RrSG
> > requesting their participation. We can work out the details, but it
> > would be good to know whom we can call upon. If you have some other
> > approach, then please let us know.
> >
> > Mili and Pedro, perhaps we can speak in the next day or so to
> work on
> > those details.
> >
> > Ken
> >
> > *From:*Benjamin Akinmoyeje <benakin at gmail.com<mailto:benakin at gmail.com>
> <mailto:benakin at gmail.com<mailto:benakin at gmail.com>>>
> > *Sent:* Tuesday, May 28, 2024 5:12 PM
> > *To:* Ken Herman <ken at kherman.com<mailto:ken at kherman.com> <mailto:ken at kherman.com<mailto:ken at kherman.com>>>
> > *Cc:* Exec. Comm <ncuc-ec at lists.ncuc.org<mailto:ncuc-ec at lists.ncuc.org>
> <mailto:ncuc-ec at lists.ncuc.org<mailto:ncuc-ec at lists.ncuc.org>>>
> > *Subject:* Re: issue Forum Status?
> >
> > Dear Ken,
> >
> > Thank you for your email. The NCUC Issue Forum and NCUC membership
> > meeting require the input of NCUC official representatives to
> the ICANN
> > meeting.
> >
> > I have asked and requested topics and speakers; below is what I
> have so
> > far; the process is open to those of us attending ICANN80 to organize
> >
> > NCUC Issue forum
> >
> >
> https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq263g7jSx-Q$> <https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq263g7jSx-Q$>> <https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq263g7jSx-Q$> <https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq263g7jSx-Q$>>>
> >
> > NCUC membership meeting
> >
> >
> https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq2614pPCmmg$> <https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq2614pPCmmg$>> <https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq2614pPCmmg$> <https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq2614pPCmmg$>>>
> >
> > Additionally, contributions from you and Mili will go a long way in
> > finalizing the events.
> >
> > Kind regards,
> >
> > Benjamin
> >
> > On Tue, May 28, 2024 at 6:21 PM Ken Herman <ken at kherman.com<mailto:ken at kherman.com>
> <mailto:ken at kherman.com<mailto:ken at kherman.com>>
> > <mailto:ken at kherman.com<mailto:ken at kherman.com> <mailto:ken at kherman.com<mailto:ken at kherman.com>>>> wrote:
> >
> > Benjamin, I’m wondering where we are with the issue forum
> planning.
> > Last I recall there were some ideas around registrant
> > rights/security, and the need to reach out to the Registrar
> SG, but
> > haven’t heard if anything has developed.
> >
> > Where do we stand, please?
> >
> > Thanks
> >
> > Ken
> >
> >
> > _______________________________________________
> > NCUC-EC mailing list
> > NCUC-EC at lists.ncuc.org<mailto:NCUC-EC at lists.ncuc.org> <mailto:NCUC-EC at lists.ncuc.org<mailto:NCUC-EC at lists.ncuc.org>>
> > https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]<https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq261yYI6CNw$>
> <https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]<https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq261yYI6CNw$>>
> _______________________________________________
> NCUC-EC mailing list
> NCUC-EC at lists.ncuc.org<mailto:NCUC-EC at lists.ncuc.org> <mailto:NCUC-EC at lists.ncuc.org<mailto:NCUC-EC at lists.ncuc.org>>
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]<https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq261yYI6CNw$>
> <https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]<https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq261yYI6CNw$>>
>
_______________________________________________
NCUC-EC mailing list
NCUC-EC at lists.ncuc.org<mailto:NCUC-EC at lists.ncuc.org>
https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]<https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!5zGgJEIdeexL7e6FvWUGa5QtflOjvWS2F0abE38_gFZ-P5NU1ozv1FKdiSI7-EyDK6e9GkRWu9cq261yYI6CNw$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20240605/db2ac64b/attachment-0001.htm>
More information about the NCUC-EC
mailing list