Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Mailbox Transport; Mon, 25 Feb 2019 09:19:04 -0800 Received: from PFE112-CA-2.pexch112.icann.org (64.78.40.18) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 25 Feb 2019 09:19:03 -0800 Received: from ppa2.lax.icann.org (192.0.33.77) by PFE112-CA-2.pexch112.icann.org (64.78.40.12) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Mon, 25 Feb 2019 09:19:03 -0800 Received: from pps.reinject (ppa2.lax.icann.org [127.0.0.1]) by ppa2.lax.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id x1PHJ33j021677 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 25 Feb 2019 17:19:03 GMT Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [127.0.0.1]) by pps.reinject (8.16.0.27/8.16.0.27) with SMTP id x1PHJ3Bn021674 for ; Mon, 25 Feb 2019 17:19:03 GMT Received: from pechora2.lax.icann.org (pechora2.icann.org [192.0.33.72]) by ppa2.lax.icann.org with ESMTP id x1PHJ2ZO021673 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 Feb 2019 17:19:02 +0000 Received: from smtp01.icann.org (smtp01.icann.org [192.0.46.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora2.lax.icann.org (Postfix) with ESMTPS id 5F2541E0591; Mon, 25 Feb 2019 17:19:02 +0000 (UTC) Received: from mm.icann.org (mm.icann.org [192.0.32.100]) by smtp01.icann.org (Postfix) with ESMTP id B3BB4E016A; Mon, 25 Feb 2019 17:19:01 +0000 (UTC) Received: from mm.icann.org (localhost [127.0.0.1]) by mm.icann.org (Postfix) with ESMTP id 7B9B4EE03C6; Mon, 25 Feb 2019 17:19:01 +0000 (UTC) Received: from pechora8.dc.icann.org (pechora8.icann.org [192.0.46.74]) by mm.icann.org (Postfix) with ESMTP id 802C7EE03C6; Mon, 25 Feb 2019 17:18:59 +0000 (UTC) Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by pechora8.dc.icann.org (Postfix) with ESMTPS id F3540C05EE; Mon, 25 Feb 2019 17:18:58 +0000 (UTC) Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 25 Feb 2019 09:18:56 -0800 Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Mon, 25 Feb 2019 09:18:56 -0800 From: Julie Bisland To: "gnso-newgtld-wg@icann.org" CC: "gnso-secs@icann.org" Subject: [gnso-secs] ICANN64: GNSO Sessions How to Get Organized and Remote Participation Details Thread-Topic: ICANN64: GNSO Sessions How to Get Organized and Remote Participation Details Thread-Index: AdTNK0fgljnQNdGvSHyzeS38jk0+uw== Sender: Gnso-secs Date: Mon, 25 Feb 2019 17:18:56 +0000 Message-ID: <1cc0ea540f954f53aa2f88e577ea3d28@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> List-Help: List-Subscribe: , List-Unsubscribe: , Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthSource: PFE112-CA-2.pexch112.icann.org X-MS-Has-Attach: yes X-Auto-Response-Suppress: All X-MS-TNEF-Correlator: x-proofpoint-virus-version: vendor=fsecure engine=2.50.10434:,, definitions=2019-02-25_08:,, signatures=0 errors-to: gnso-secs-bounces@icann.org x-proofpoint-spam-reason: eusafe x-beenthere: gnso-secs@icann.org x-mailman-version: 2.1.15 list-id: x-originating-ip: [192.0.32.236] list-post: x-original-to: gnso-secs@mm.icann.org delivered-to: gnso-secs@mm.icann.org authentication-results: ppa1.lax.icann.org; spf=pass smtp.mailfrom=gnso-secs-bounces@icann.org; dmarc=pass header.from=icann.org x-organizationheaderspreserved: PMBX112-W1-CA-1.pexch112.icann.org Content-Type: multipart/mixed; boundary="_004_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_" MIME-Version: 1.0 --_004_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_ Content-Type: multipart/alternative; boundary="_000_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_" --_000_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, The one-stop wiki page for all your Remote Participation queries is now ava= ilable. This wiki page covers remote participation details for all GNSO ope= n and public meetings. In addition to this, ICANN meetings' team has put together an updated ICANN= meeting website which allows you to download all GNSO-related meetings to = your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN64 Meeting Schedule [64.schedule.icann.org] GNSO Remote Participation Wiki Page Step 1 - Create a profile and your personalized ICANN64 schedule Go to the Meeting Schedule webpage and create a profile and login. Every se= ssion on the schedule can be selected and added to your individual schedule= by clicking the Add box to the bottom right of each meeting, this adds it = to your individual schedule which you can then email to yourself or add to = your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you'= ve added all your chosen meetings to "My Schedule" go to Export. * Importing creates a one-time snapshot of your schedule and copies i= t into Outlook. If you subsequently make changes to your Pathable calendar,= they will not be reflected in Outlook. * Subscribing creates a live feed of your schedule in Outlook. Outloo= k checks for changes every few hours and updates your calendar appropriatel= y. Step 3 All Adobe Connect rooms (which can be found on the session information on t= he ICANN64 Meeting Schedule [64.schedule.icann.org] and on the GNSO Remote Participation Wiki = Page) will provide audio streaming on= ly, Adobe Connect room microphones will not be enabled. If you cannot join = an Adobe Connect room for a session, and will need to dial in with your pho= ne, please refer to the GNSO Remote Participation Wiki Page for the audio pass codes and dial in numbers. Please also = follow the previous steps if you wish to take part in the session over the = phone. Step 4 Please download the mobile app by searching for "ICANN64" in your app store= s. Nathalie Peregrine and Terri Agnew will be onsite in Kobe to assist you dir= ectly. For all GNSO meeting related queries (RP or others), please email us= at: gnso-secs@icann.org and we will be more th= an happy to assist! Kind regards, GNSO SO/AC Support team Julie Bisland Secretariat Operations Coordinator for the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland@icann.org Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting the GNSO Newcomer pages [gnso.ican= n.org] --_000_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_ Content-Type: text/html; charset="us-ascii" Content-ID: <9033C2E01B3C3744B3CD7E9A7BB2FE59@pexch112.icann.org> Content-Transfer-Encoding: quoted-printable

D= ear all,

 

The one-stop wiki page for all your Remote Participation queries is now avai= lable. This wiki page covers remote participation details for all GNSO open= and public meetings.

 

I= n addition to this, ICANN meetings’ team has put together an updated = ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go.

&= nbsp;

2 LINKS TO BOOKMARK NOW:

ICANN64 Meeting Schedule [64.schedule.icann.org]  

GNSO Remote Participation Wiki Page

 

Step 1 – Create a profile and your personalized ICANN64 schedule

G= o to the Meeting Schedule webpage and create a profile and login. Every ses= sion on the schedule can be selected and added to your individual schedule = by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you = can then email to yourself or add to your calendar. See next step.

 

Step 2 - There are two ways to import your sche= dule into Outlook: once you’ve added all your chosen meetings to “My Schedule&#= 8221; go to Export.

  • Importing creates a one-time snapshot of your s= chedule and copies it into Outlook. If you subsequently make changes to you= r Pathable calendar, they will not be reflected in Outlook.
  • Subscribing creates a live feed of your schedul= e in Outlook. Outlook checks for changes every few hours and updates your c= alendar appropriately.

 

Step 3

A= ll Adobe Connect rooms (which can be found on the session information on th= e ICANN64 Meeting Schedule [64.schedule.icann.org] and on the GNSO Remote Participation Wiki Page) will provide audio streaming only, Adobe Connect room micro= phones will not be enabled. If you cannot join an Adobe Connect room for a sessi= on, and will need to dial in with your phone, please refer to the GNSO Remote Participation Wiki Page for the audio pass codes and dial in numbers. Please also fo= llow the previous steps if you wish to take part in the session over the phone.

 

Step 4

P= lease download the mobile app by searching for “ICANN64” in you= r app stores.

 

N= athalie Peregrine and Terri Agnew will be onsite in Kobe to assist you dire= ctly. For all GNSO meeting related queries (RP or others), please email us = at: gnso-secs@icann.org and we will = be more than happy to assist!

 

K= ind regards,

 

G= NSO SO/AC Support team

 

 

<= /span>

Julie Bisland

Secretariat Operations Coordinator for the GNSO

Internet Corporation for Assigned Names and Numbers = (ICANN)

Email:  julie.bisland@icann.org

Skype ID:  79613b691cb8a6c1

 

Find out more about the = GNSO by visiting the GNSO Newcomer pages [gnso.icann.org]

 

 

--_000_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_-- --_004_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_ Content-Type: text/plain; name="ATT00001.txt" Content-Description: ATT00001.txt Content-Disposition: attachment; filename="ATT00001.txt"; size=141; creation-date="Mon, 25 Feb 2019 17:19:04 GMT"; modification-date="Mon, 25 Feb 2019 17:19:04 GMT" Content-ID: <4D6F2E3D6AC54B45946FF41D5056B573@pexch112.icann.org> Content-Transfer-Encoding: base64 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkduc28tc2Vj cyBtYWlsaW5nIGxpc3QNCkduc28tc2Vjc0BpY2Fubi5vcmcNCmh0dHBzOi8vbW0uaWNhbm4ub3Jn L21haWxtYW4vbGlzdGluZm8vZ25zby1zZWNz --_004_1cc0ea540f954f53aa2f88e577ea3d28PMBX112W1CA1PEXCH112ICA_--