[SubPro-IRT] REMINDER | SubPro IRT Meeting #14 | 10 October 2023, 20:00-21:00 UTC

Wed Oct 11 18:55:22 UTC 2023

+1 Jeff, thank you.

[image: Logo]

Mike Rodenbaugh

address:

548 Market Street, Box 55819

San Francisco, CA 94104

email:

mike at rodenbaugh.com

phone:

+1 (415) 738-8087

On Wed, Oct 11, 2023 at 11:11 AM Jeff Neuman <jeff at jjnsolutions.com> wrote:

> All,
>
> I agree with the concepts that one should be free of conflict as soon as
> it accepts the appointment.  But that is not what Anne’s language states.
> Anne’s language states that it should be free of conflicts upon application
> which I do not necessarily agree with.
>
> For example, I am a consultant that sometimes advises registries and
> registrars.  Some of those registries and registrars may be applying for a
> TLD in the next round and I may or may not know that.  If I were to accept
> the appointment I would need to make sure that i do not continue to
> represent those registries and registrars going forward.  I should not be
> required to rid myself of those clients on the day I apply for a position
> that I may or may not get.  After all, if I do not get the appointment, now
> I have gotten rid of my clients AND do not have work going forward.
>
> Of course, if I get a position as a vendor, then of course I need to rid
> myself of those potential conflicts.  This is how the normal conflict
> process works.
>
> So if we changed Anne’s language to “upon acceptance of the appointment”,
> I think that makes more sense.
>
> Get Outlook for iOS <https://aka.ms/o0ukef>
> ------------------------------
> *From:* SubPro-IRT <subpro-irt-bounces at icann.org> on behalf of Hickson,
> Nigel (DSIT) via SubPro-IRT <subpro-irt at icann.org>
> *Sent:* Wednesday, October 11, 2023 1:22 PM
> *To:* Amina Ramallan <aramallan at ncc.gov.ng>; Anne ICANN <
> anneicanngnso at gmail.com>; Next Round Policy Implementation <
> NextRound_PolicyImplementation at icann.org>
> *Cc:* subpro-irt at icann.org <subpro-irt at icann.org>
> *Subject:* Re: [SubPro-IRT] REMINDER | SubPro IRT Meeting #14 | 10
> October 2023, 20:00-21:00 UTC
>
>
> Good afternoon
>
>
>
> I agree; this seems eminently sensible; thanks for raising Anne;
>
>
>
> Best
>
>
>
> Nigel
>
>
>
> *From:* SubPro-IRT <subpro-irt-bounces at icann.org> *On Behalf Of *Amina
> Ramallan via SubPro-IRT
> *Sent:* Wednesday, October 11, 2023 6:06 PM
> *To:* Anne ICANN <anneicanngnso at gmail.com>; Next Round Policy
> Implementation <NextRound_PolicyImplementation at icann.org>
> *Cc:* subpro-irt at icann.org
> *Subject:* Re: [SubPro-IRT] REMINDER | SubPro IRT Meeting #14 | 10
> October 2023, 20:00-21:00 UTC
>
>
>
> Hello all,
>
>
>
> Yes, I also agree with Anne as vendors should be free of conflict prior to
> accepting the appointment.
>
>
>
> Thanks,
> Amina
>
>
>
> Get Outlook for iOS <https://aka.ms/o0ukef>
> ------------------------------
>
> *From:* SubPro-IRT <subpro-irt-bounces at icann.org> on behalf of Anne ICANN
> <anneicanngnso at gmail.com>
> *Sent:* Thursday, October 12, 2023 00:55
> *To:* Next Round Policy Implementation <
> NextRound_PolicyImplementation at icann.org>
> *Cc:* subpro-irt at icann.org <subpro-irt at icann.org>
> *Subject:* Re: [SubPro-IRT] REMINDER | SubPro IRT Meeting #14 | 10
> October 2023, 20:00-21:00 UTC
>
>
>
> Hi all - apologies for having had to miss the October 10 meeting.    I
> have just reviewed the Zoom.
>
>
>
> To: Antonietta - I have one comment on the language in 2.4.3 which talks
> about the timing of applying the ethical obligations.
>
>
>
> The current language says that the ethical obligations "begin upon
> acceptance of the appointment" as a vendor.  However, it strikes me that
> the ethical obligations must begin upon application to accept an
> appointment because the vendor should be free and clear of conflicts of
> interest upon application and should represent that it has no conflicts
> upon making application for the appointment.
>
>
>
> If others agree, could you please address by changing "upon acceptance of
> the appointment" to "upon application for the appointment" or some similar
> change in the language?  I don't think we want a vendor who maintains a
> conflict unless and until the vendor is appointed and then drops that
> conflict to address this requirement.
>
>
>
> Thank you,
>
> Anne
>
>
>
> Anne Aikman-Scalese
>
> GNSO Councilor
>
> NomCom Non-Voting 2022-2024
>
> anneicanngnso at gmail.com
>
>
>
>
>
> On Tue, Oct 10, 2023 at 12:00 PM Next Round Policy Implementation <
> NextRound_PolicyImplementation at icann.org> wrote:
>
> Dear All,
>
>
>
> Meeting #14 of the SubPro IRT will be held *in an hour* on *10 October *
> *2023* at *20**:00-21**:00 UTC* [local time
> <https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meeting+%2314+%7C+10+October+2023%2C+20%3A00-21%3A00+UTC&iso=20231010T20&p1=1440&ah=1>].
> The agenda can be consulted here <https://community.icann.org/x/75CZDg>.
> Before the meeting, please be sure you have read the ICANN Expected
> Standards of Behavior
> <https://www.icann.org/resources/pages/expected-standards-2016-06-28-en>.
>
>
>
> We would like to remind participants that to ensure transparency of
> participation in ICANN's multistakeholder model, we ask that you sign in to
> Zoom sessions using your full name. For example, First Name and Last Name
> or Surname. You may be removed from the session if you do not sign in
> using your full name.
>
>
>
> *Zoom information:*
>
>
>
> *Join the Zoom Webinar directly (recommended): *
>
> https://icann.zoom.us/j/98960123523?pwd=SjU0cEtieS9Kc2NZRUNPNGdraGQ0QT09
>
> Meeting ID: 989 6012 3523
>
> Passcode: z6sLS^44 at y
>
>
>
> *Zoom Audio only:*
>
> One tap mobile
>
> +13462487799,,98960123523#,,,,*8399371478# US (Houston)
>
> +16699006833,,98960123523#,,,,*8399371478# US (San Jose)
>
> Dial in directly with your local number: https://icann.zoom.us/u/aIO87mfSF
>
> Meeting ID: 989 6012 3523
>
> Passcode: 8399371478
>
>
>
> Should you be unable to attend the meeting, please let us know in advance.
> A recording will be made available.
>
>
>
> Please do not hesitate to contact us should you have any questions.
>
>
>
> Best regards,
>
> Elisa
>
> _______________________________________________
> SubPro-IRT mailing list
> SubPro-IRT at icann.org
> https://mm.icann.org/mailman/listinfo/subpro-irt
>
> _______________________________________________
> 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.
>
> _______________________________________________
> SubPro-IRT mailing list
> SubPro-IRT at icann.org
> https://mm.icann.org/mailman/listinfo/subpro-irt
>
> _______________________________________________
> 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/subpro-irt/attachments/20231011/099d3bc1/attachment-0001.html>