<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [gnso-secs] Re: [council] Proposed Agenda GNSO Council Meeting 1 December 2016 at 21:00UTC
- To: Johan Helsingius <julf@xxxxxxxx>, "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
- Subject: RE: [gnso-secs] Re: [council] Proposed Agenda GNSO Council Meeting 1 December 2016 at 21:00UTC
- From: Terri Agnew <terri.agnew@xxxxxxxxx>
- Date: Thu, 1 Dec 2016 19:40:26 +0000
- Accept-language: en-US
- Cc: "gnso-secs@xxxxxxxxx" <gnso-secs@xxxxxxxxx>
- In-reply-to: <c23fb1bc-d9d2-e066-266d-41925ec501e7@julf.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <D4658E57.EC404%nathalie.peregrine@icann.org> <c23fb1bc-d9d2-e066-266d-41925ec501e7@julf.com>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AQHSS6PYTz55jp29nkS7D7VDKko5i6Dz/oIA//9/nSA=
- Thread-topic: [gnso-secs] Re: [council] Proposed Agenda GNSO Council Meeting 1 December 2016 at 21:00UTC
Hi Johan,
https://participate.icann.org/gnsocouncil
Kind regards,
Terri
-----Original Message-----
From: owner-gnso-secs@xxxxxxxxx [mailto:owner-gnso-secs@xxxxxxxxx] On Behalf Of
Johan Helsingius
Sent: Thursday, December 1, 2016 1:20 PM
To: council@xxxxxxxxxxxxxx
Cc: gnso-secs@xxxxxxxxx
Subject: [gnso-secs] Re: [council] Proposed Agenda GNSO Council Meeting 1
December 2016 at 21:00UTC
What adobe connect link should we use?
Julf
On 01-12-16 08:23, Nathalie Peregrine wrote:
> Dear All,
>
>
>
> Please find the updated proposed Agenda for the GNSO Council Meeting
> on
> 1 December 2016 at 21:00 UTC. Links will be provided for Item 5 when
> available.
>
> Please note that *all documents *referenced *in the agenda have been
> gathered on a Wiki page for convenience and easier
> access:*
> https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.o
> rg_x_l5LDAw-5Bcommunity.icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVz
> gfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=
> oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=ShGzoSBeiV8yUZVZN2a5U9Is
> M8KgAYScfiN6oyvg1Ps&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.
> org_x_l5LDAw&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=
> U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFg
> PZ8rQYMg1u-6Fisv8RY&s=djndonGNmPB9XCz2YEo57E3RP7MHwylV59HZzjjUgUk&e=>
>
> This agenda was established according to the GNSO Operating Procedures
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_e
> n_council_op-2Dprocedures-2D01sep16-2Den.pdf&d=DQMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=55oYi9y1UeIL5juaxAkqpioz33PyWq>
> v3.2, updated on 01 September 2016.
>
> For convenience:
>
> * An excerpt of the ICANN Bylaws defining the voting thresholds is
> provided in _Appendix 1_ at the end of this agenda.
> * An excerpt from the Council Operating Procedures defining the
> absentee voting procedures is provided in _Appendix 2_ at the end of
> this agenda.
>
> Coordinated Universal Time: 21:00 UTC
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_zqkas4
> h-5Btinyurl.com-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I
> 5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5uk
> TPKhkKh8-cBX7KOQW3kmtnjDM&s=LDKZD89yu5n7-RtfrKbHZXKpboztO38jBMAiBMjTt5
> U&e=
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_zqkas
> 4h&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko
> 8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u
> -6Fisv8RY&s=GQrrb-5wfVwExPeuYPyTdP-lCTA795_FUFaUNe77cYs&e=>**
> *
> *13:00 Los Angeles; 16:00 Washington; 21:00 London; (Friday 2^nd
> December) 00:00 Istanbul; 08:00 Hobart
>
> *___________________________________*
>
> *Item 1. Administrative Matters (5 mins)*
>
> 1.1 - Roll Call
>
> 1.2 - Updates to Statements of Interest
>
> 1.3 - Review / Amend Agenda
>
> 1.4 - Note the status of minutes for the previous Council meetings per
> the GNSO Operating Procedures:
>
> Minutes of the meeting of the GNSO Council on 7 November 2016 and
> posted on XXXXXXX 2016.
>
>
>
> *Item 2. Opening Remarks / Review of Projects & Action List (5 mins)*
>
> 2.1 - Review focus areas and provide updates on specific key themes /
> topics, to include review of Projects List [gnso.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_e
> n_council_project&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5
> cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o0
> 9HkFgPZ8rQYMg1u-6Fisv8RY&s=kBZ003hIhGjPzEdgi-PFtncJOOcmeqCM1PbKkUgsVz0
> &e=>and Action Item List[community.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.
> org_x_RgZlAg&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=
> U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFg
> PZ8rQYMg1u-6Fisv8RY&s=viVDWlTD9pBSbRA0Ca9MrDY09WT9NdhpdDGZvRmdL5A&e=>
>
>
>
> *Item 3. Consent Agenda (0 mins)*
>
> * *
>
> *Item 4. COUNCIL VOTE - Adoption of Consensus Recommendations from the
> GNSO Bylaws Drafting Team (10 minutes)*
>
> On 30 June 2016, the GNSO Council created a Drafting Team (DT) to work
> with ICANN staff to identify the GNSO's new rights and obligations
> under the revised ICANN Bylaws, and prepare an implementation plan to
> address any needed changes by 30 September
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_e
> n_council_resolutions-2320160630-2D2-29-5Bgnso.icann.org-5D&d=DgID-g&c
> =FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7a
> r9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=U
> adZRQ0z4PHh6ZhNXIMem-bUNbCvvLib0s3-N3EQqt4&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_resolutions-2320160630-2D2-2529&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=nlpNf0f4WasXPnr1kqv8mJsHTDYbhmHr_L1TGrWRFcg&e=>.
> On 29 September 2016, the Council received an update on the status of
> the DT's work and, pending the completion of the DT's work, the
> Council voted to appoint the GNSO Chair as its interim representative
> to the Empowered Community (EC) Administration. At its meeting on 13
> October, the Council reviewed the DT's report and recommendations
> (Final
> Report:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en
> _drafts_bylaws-2Ddrafting-2Dteam-2Dfinal-2Dreport-2D12oct16-2Den.pdf-5
> Bgnso.icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I
> 5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5uk
> TPKhkKh8-cBX7KOQW3kmtnjDM&s=n_qCcw-sbIo9Xq9Wdttbp-zMNKEm4RjVfc9CiRMvzU
> c&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_e
> n_drafts_bylaws-2Ddrafting-2Dteam-2Dfinal-2Dreport-2D12oct16-2Den.pdf&
> d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8ge
> LjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6F
> isv8RY&s=dLiArWhrBsDH0mNsmfMBx8uVcWdDdXRQ-M4x0nabfmU&e=>;
> Minority
> Statement:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en
> _drafts_bylaws-2Ddrafting-2Dteam-2Dminority-2Dreport-2D10oct16-2Den.pd
> f-29-5Bgnso.icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms
> 7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlr
> Svz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=RLgQ2WgFKVvHX2q1Ddtv2WwtQWZrBEj9QiCc
> 1zqrcGo&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_drafts_bylaws-2Ddrafting-2Dteam-2Dminority-2Dreport-2D10oct16-2Den.pdf-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=suPjvX8K-WP7q2gBcepEOIr65RdoU3dVx1qAKoW00AU&e=>.
> At ICANN57, the Council agreed to amend the original motion that had
> been submitted for Council consideration.
>
> Here the Council will vote on whether or not to pass the amended motion.
> Following the passage of a final motion, the GNSO is expected to
> confirm its process for appointing its EC representative going forward.
>
> 4.1 - Presentation of the motion[community.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.
> org_display_gnsocouncilmeetings_Motions-26-2343-3B1-26-2343-3BDecember
> -26-2343-3B2016&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM
> &r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09H
> kFgPZ8rQYMg1u-6Fisv8RY&s=0kK5l26dGz6hzECC6KdEKVRFat-Dr99n1u8u2CEimS8&e
> => (James
> Bladel)
>
> 4.2 - Council discussion
>
> 4.3 - Council vote (voting threshold: simple majority)
>
> * *
>
> *Item 5. COUNCIL VOTE - GNSO Council Response to the Board on gTLD
> Policy Matters related to the GAC Communique from Hyderabad (20
> minutes)*
>
> Beginning in July 2015, the GNSO Council has reviewed each GAC
> Communiqué for issues relating to gTLD policy, with a view toward
> providing feedback to the ICANN Board as well as the broader community
> concerning past, present or future GNSO policy activities concerning
> advice provided by the GAC. In the GAC Communique from ICANN57 in
> Hyderabad, the GAC had provided specific advice regarding protections
> in the domain name system for International Governmental Organization
> (IGO) names and acronyms as well as identifiers associated with the
> international Red Cross movement and its National Societies
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en
> _system_files_correspondence_gac-2Dto-2Dicann-2D08nov16-2Den.pdf-29-5B
> icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=
> DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkK
> h8-cBX7KOQW3kmtnjDM&s=JH7UPNftWCAWm3SFJqp5TNfbTF16daYlVtUbb2DHzvA&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_gac-2Dto-2Dicann-2D08nov16-2Den.pdf-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=mFzheCtf9IBwsuYUAtgU96EyKBKNVArCndR3Ok2ppVE&e=>.
> Also at ICANN57, the ICANN Board had suggested that a facilitated
> discussion between the GAC and the GNSO on remaining inconsistencies
> between GAC advice and GNSO policy recommendations on these matters be
> considered as a possible path forward
> (https://urldefense.proofpoint.com/v2/url?u=http-3A__schd.ws_hosted-5F
> files_icann572016_60_I57-2520HYD-5FTue08Nov2016-2DPublic-2520Forum-252
> 02-2Den.pdf-29-5Bschd.ws-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6s
> Jms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1K
> KlrSvz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=f0JF-w7iYJsmN0FENrU_DWVRl40qqJ6Y6
> ERQMKvvuTs&e=
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__schd.ws_hosted-5Ffiles_icann572016_60_I57-2520HYD-5FTue08Nov2016-2DPublic-2520Forum-25202-2Den.pdf-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=gZAtGNidxQ7zKOxlxeBcxRX1fkdx79cD7BP37JWkX6o&e=>.
>
> A draft response [INSERT LINK] to the GAC's Communique from ICANN57 in
> Hyderabad was circulated to the GNSO Council on [INSERT DATE]. Here
> the Council will consider whether or not to approve a response to the
> Board, and confirm its intended next steps with regard to reconciling
> its policy recommendations with GAC advice on the topic of Red Cross and IGO
> protections.
>
> 5.1 - Presentation of the motion[community.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.
> org_display_gnsocouncilmeetings_Motions-26-2343-3B1-26-2343-3BDecember
> -26-2343-3B2016&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM
> &r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09H
> kFgPZ8rQYMg1u-6Fisv8RY&s=0kK5l26dGz6hzECC6KdEKVRFat-Dr99n1u8u2CEimS8&e
> => (Paul
> McGrady)
>
> 5.2 - Council discussion
>
> 5.3 - Council vote (voting threshold: simple majority)
>
>
>
> *Item 6: *(may be removed from agenda pending decision on sending
> letter) *COUNCIL VOTE - Approval of Letter to the ICANN Board
> concerning Implementation Issues with Part C of the Inter-Registrar
> Transfer Policy
> (10 minutes)*
>
> Part C of ICANN's Inter-Registrar Transfer Policy (IRTP), aimed at
> combatting domain name theft, is scheduled to come into effect on 1
> December 2016
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_re
> sources_pages_transfer-2Dpolicy-2D2016-2D06-2D01-2Den-29-5Bicann.org-5
> D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFp
> CIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW
> 3kmtnjDM&s=fi1O7Qt4oCpOnaPJxu2FV_c1V-SUPqrWtPP7PtjJmMA&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_transfer-2Dpolicy-2D2016-2D06-2D01-2Den-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=0CI4SN9VTlI4coanEdMPFs4jfj7-eSRVaSm2Gkfd0no&e=>.
> On 31 October 2016, the Registrar Stakeholder Group identified and
> raised a critical issue concerning the implementation of IRTP Part C
> in relation to the provision of privacy and proxy services
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_m
> ailing-2Dlists_archives_council_msg19339.html-29-5Bgnso.icann.org-5D&d
> =DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIg
> mkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3km
> tnjDM&s=4PCEd2jeoHON2a7GTYad0rVZ7GV1lDOkux9E9NFw1bw&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_mailing-2Dlists_archives_council_msg19339.html-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=3nI-aswx9lbyAP35FYEs6-KNKBZvr2yFspqBKuTnriA&e=>.
> At ICANN57 in Hyderabad, the GNSO Council discussed the issue with
> ICANN's Global Domains Division staff in charge of policy
> implementation, and it was suggested that the most appropriate course
> of action would be to to request that the ICANN Board direct staff to
> remove the privacy/proxy services aspect from the IRTP and place it
> for evaluation and recommendation by the newly formed Privacy Proxy
> Services Accreditation Issues Implementation Review Team.
>
> A draft letter to the Board was circulated to the Council on 21 November.
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en
> _correspondence_gnso-2Dcouncil-2Dto-2Dicann-2Dboard-2D21nov16-2Den.pdf
> -5Bgnso.icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl
> 4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5
> ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=S-8bucVOn_EBSoIz8hoo1I3v-MtqasLdWWB9jgMK
> Fdo&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_e
> n_correspondence_gnso-2Dcouncil-2Dto-2Dicann-2Dboard-2D21nov16-2Den.pd
> f&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8
> geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-
> 6Fisv8RY&s=UfhJM16l04kGffwoyLGta1ejPDXeldiJ5GPZzuxrNC0&e=>
> Here the Council will discuss whether or not to approve the letter for
> transmission to the ICANN Board.
>
> 6.1 - Presentation of the motion[community.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.
> org_display_gnsocouncilmeetings_Motions-26-2343-3B1-26-2343-3BDecember
> -26-2343-3B2016&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM
> &r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09H
> kFgPZ8rQYMg1u-6Fisv8RY&s=0kK5l26dGz6hzECC6KdEKVRFat-Dr99n1u8u2CEimS8&e
> => (Darcy
> Southwell)
>
> 6.2 - Council discussion
>
> 6.3 - Council vote (voting threshold: simple majority)
>
>
>
> *Item 7. COUNCIL VOTE - Adoption of Proposed Implementation Plan for
> Recommendations relating to the 2014 GNSO Review (10 minutes)*
>
> Along with the ICANN Board's adoption in June 2016 of certain
> recommendations from the 2014 GNSO Review, the GNSO Council requested
> that ICANN policy staff prepare a discussion paper outlining the
> possible options for implementation, taking into account past
> implementation of previous GNSO Reviews as well as existing mechanisms.
> At ICANN56 in Helsinki in June 2016, the GNSO Council discussed the
> options outlined in the staff discussion paper
> (https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en
> _drafts_review-2Dimplementation-2Drecommendations-2Ddiscussion-2Dpaper
> -2D20jun16-2Den.pdf-29-5Bgnso.icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwl
> l3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2
> EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=X9VgJIlB9HG4RpWIUl
> JMRA7IYVVjNPodJy6B3m5asec&e=
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_drafts_review-2Dimplementation-2Drecommendations-2Ddiscussion-2Dpaper-2D20jun16-2Den.pdf-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=-BQXfybyFmWWf2VaEaCnu_icX4XAK5qlPMNgS5XqYwQ&e=>.
> On 21 July 2016 the GNSO Council chartered[gnso.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_e
> n_drafts_gnso-2Dreview-2Dcharter-2D21jul16-2Den.pdf&d=DgMFAw&c=FmY1u3P
> Jp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=mpNCVIYX665jhJ17rntBgHS9zzHgGGig8huBDIrwa2Y&e=>
> the GNSO Review Working Group and directed it to submit a proposed
> implementation plan to the Council for approval by the ICANN57 meeting.
>
>
>
> The GNSO Review Working Group circulated its proposed implementation
> plan to the Council on 21 November.
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en
> _drafts_review-2Dimplementation-2Drecommendations-2Dplan-2D21nov16-2De
> n.pdf-5Bgnso.icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJm
> s7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKl
> rSvz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=jXx4krMhYgSWb3H-LjGtwVRXplae3XjQJyR
> 9Z43Ud5k&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_e
> n_drafts_review-2Dimplementation-2Drecommendations-2Dplan-2D21nov16-2D
> en.pdf&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX
> 3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=Fm1pKTEN6
> VRmMYjEm2YXhbMroDrX19hx2uiqPqHAex8&s=Oo1S2OT2brknp3ieQ19DSDPuoVP3Cl8PZ
> oSkWpdVYGw&e=> Here the Council will consider whether or not to
> approve the plan for transmission to the ICANN Board.
>
> 7.1 - Presentation of the motion[community.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.
> org_display_gnsocouncilmeetings_Motions-26-2343-3B1-26-2343-3BDecember
> -26-2343-3B2016&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM
> &r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09H
> kFgPZ8rQYMg1u-6Fisv8RY&s=0kK5l26dGz6hzECC6KdEKVRFat-Dr99n1u8u2CEimS8&e
> => (Wolf-Ulrich
> Knoben)
>
> 7.2 - Council discussion
>
> 7.3 - Council vote (voting threshold: simple majority)
>
> * *
>
> *Item 8. COUNCIL DISCUSSION - GNSO Council Response to Proposed Scope
> of the Forthcoming Registration Directory Services (RDS) Review
> (formerly the Whois Review) (10 minutes)*
>
> On 4 November 2016 ICANN staff circulated a document to all Supporting
> Organizations and Advisory Committee (SO/AC) leaders that described a
> proposed limited scope for the forthcoming RDS (formerly Whois) Review
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_ma
> iling-2Dlists_archives_council_msg19381.html-29-5Bgnso.icann.org-5D&d=
> DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgm
> kXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3kmt
> njDM&s=qMzopgu29uR635MD5a3RIXP1CAzOZRWT__iKkk_mBA4&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_mailing-2Dlists_archives_council_msg19381.html-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=ntM0ZZdwVBRVtw1bclE23GgsWtwLZIF4GEISrT6LAO0&e=>.
> This topic was also discussed as part of a High Interest Topics
> Session at ICANN57 in Hyderabad, and certain concerns with the
> proposal noted by the GNSO Council during its Wrap Up Session. Here
> the Council will discuss and confirm its feedback (if any) concerning
> the proposed limited scope of the RDS Review.
>
> 8.1 - Summary and update (James Bladel / Susan Kawaguchi)
>
> 8.2 - Council discussion
>
> 8.3 - Next steps
>
> * *
>
> *Item 9. COUNCIL DISCUSSION - GNSO Council Response to Questions from
> the CCWG-Accountability Co-Chairs concerning Work Stream 2 (10
> minutes)*
>
> *On 4 November 2016, the co-chairs of the Cross Community Working
> Group on ICANN Accountability (CCWG-Accountability) wrote to all SO/AC
> leaders seeking input by early December on the r*esources and
> documents used by each SO/AC to maintain accountability to its
> respective designated community, taking into account the particular or
> specific working modalities of each SO/AC (and any subgroups)
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_m
> ailing-2Dlists_archives_council_msg19440.html-29-5Bgnso.icann.org-5D&d
> =DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIg
> mkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3km
> tnjDM&s=twVF81K2oQjNOa8ko_mDonac9Unc29FhcCiOeMyKOq8&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_mailing-2Dlists_archives_council_msg19440.html-29&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=p0RyYW1li1be3pwfT0IEnfsYU4cpZmoDk4Tz8sYIPTw&e=>.
> The GNSO Council leadership is working on a possible response from the
> Council, and has requested feedback from each Stakeholder Group and
> Constituency on the topic. Here the Council will discuss whether or
> not to send a response to the CCWG-Accountability co-chairs.
>
> 9.1 - Status summary (GNSO Council leadership)
>
> 9.2 - Council discussion
>
> 9.3 - Next steps
>
> * ***
>
> *Item 10: COUNCIL DISCUSSION - Selection of GNSO Representatives to
> the Security, Stability & Resiliency Review Team (10 minutes)*
>
> At ICANN57 in Hyderabad, SO/AC leaders (including the chairs of
> several GNSO Stakeholder Groups and Constituencies) met with ICANN
> staff to discuss the selection process for appointments to the
> forthcoming Security, Stability & Resiliency (SSR) Review Team. It was
> agreed that selection of the final slate of Review Team members should
> be a collective effort by all SO/AC leaders, and that each SO/AC would
> develop its own internal guidelines for selecting its representatives
> for consideration (up to a maximum of 3 per SO/AC). The group also
> discussed how independent experts should be appointed to the Review
> Team. The current slate of applicants can be viewed at
> https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.o
> rg_x_xRqsAw-5Bcommunity.icann.org-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVz
> gfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=
> oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=GvfPWaLSPs0y_xQOZmeNIQz2
> RPYuz-OpD14N7kDY1ks&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_xRqsAw&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=YX94XSbkxuASK4IIXMQh6w587gSVqXzudayzpkt8YE4&e=>.
> Here the Council will discuss the GNSO's selection process, with a
> view toward developing a standard mechanism for all future Review Teams.
>
> *10.1 - Status summary (James Bladel)***
>
> *10.2 - Council discussion***
>
> *10.3 - Next steps***
>
> * *
>
> *Item 11: **COUNCIL DISCUSSION - Planning for ICANN58 (10 minutes)*
>
> At its Wrap Up Session at ICANN57 in Hyderabad, the Council discussed
> the need to start planning early for ICANN58. It also agreed that
> confirming certain sessions (including joint meetings with other
> SO/ACs and the ICANN Board) as fixed in the overall meeting schedule
> would be helpful for scheduling purposes, as would facilitating better
> coordination between and with individual Stakeholder Groups and
> Constituencies, and ensuring that sufficient time is given over to
> policy development work. Here the Council will discuss initial
> suggestions for the ICANN58 meeting schedule and consider next steps.
> GNSO Council input on ICANN58 Council Planning
> Survey:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en
> _drafts_icann58-2Dcouncil-2Dplanning-2Dsurvey-2D30nov16-2Den.pdf&d=DgI
> D-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh
> FzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3kmtnjD
> M&s=L9zCAUofUwlMOhg3MpoIT8G_K5bVaMBOeSSHarltMNI&e=
>
> *11.1 - Status summary (GNSO Council leadership)***
>
> *11.2 - Council discussion***
>
> *11.3 - Next steps***
>
> * *
>
> *Item 12: ANY OTHER BUSINESS (5 minutes)*
>
> *12.1 - Confirmation of GNSO Council meeting
> **calendar[gnso.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_m
> ailing-2Dlists_archives_council_msg19445.html&d=DgMFAw&c=FmY1u3PJp6wrc
> rwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ
> 64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u-6Fisv8RY&s=_FpjCoJvauMgPfK
> 0-9y4Ksup6VnkAzgaMDt1cWmclUQ&e=>** for
> 2017***
>
> * *
>
> *Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X,
> Section 3)*
>
> 9. Except as otherwise specified in these Bylaws, Annex A hereto, or
> the GNSO Operating Procedures, the default threshold to pass a GNSO
> Council motion or other voting action requires a simple majority vote
> of each House. The voting thresholds described below shall apply to
> the following GNSO actions:
>
> a. Create an Issues Report: requires an affirmative vote of more than
> one-fourth (1/4) vote of each House or majority of one House.
>
> b. Initiate a Policy Development Process ("PDP") Within Scope (as
> described in Annex A[icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_about_governance_bylaws-23AnnexA&d=DQMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=55oYi9y1UeIL5juaxAkqpioz33PyWqjoetRz4HfuZU0&s=6qYeakEV77hP5ukN3QtuJnVBlWJAK4tFqiH0uErMfvE&e=>):
> requires an affirmative vote of more than one-third (1/3) of each
> House or more than two-thirds (2/3) of one House.
>
> c. Initiate a PDP Not Within Scope: requires an affirmative vote of
> GNSO Supermajority.
>
> d. Approve a PDP Team Charter for a PDP Within Scope: requires an
> affirmative vote of more than one-third (1/3) of each House or more
> than two-thirds (2/3) of one House.
>
> e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an
> affirmative vote of a GNSO Supermajority.
>
> f. Changes to an Approved PDP Team Charter: For any PDP Team Charter
> approved under d. or e. above, the GNSO Council may approve an
> amendment to the Charter through a simple majority vote of each House.
>
> g. Terminate a PDP: Once initiated, and prior to the publication of a
> Final Report, the GNSO Council may terminate a PDP only for
> significant cause, upon a motion that passes with a GNSO Supermajority
> Vote in favor of termination.
>
> h. Approve a PDP Recommendation Without a GNSO Supermajority: requires
> an affirmative vote of a majority of each House and further requires
> that one GNSO Council member representative of at least 3 of the 4
> Stakeholder Groups supports the Recommendation.
>
> i. Approve a PDP Recommendation With a GNSO Supermajority: requires an
> affirmative vote of a GNSO Supermajority,
>
> j. Approve a PDP Recommendation Imposing New Obligations on Certain
> Contracting Parties: where an ICANN contract provision specifies that
> "a two-thirds vote of the council" demonstrates the presence of a
> consensus, the GNSO Supermajority vote threshold will have to be met
> or exceeded.
>
> k. Modification of Approved PDP Recommendation: Prior to Final
> Approval by the ICANN Board, an Approved PDP Recommendation may be
> modified or amended by the GNSO Council with a GNSO Supermajority vote.
>
> l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the
> Council members of each House, or (b) three-fourths (3/4) of one House
> and a majority of the other House."
>
> * *
>
> *Appendix 2: Absentee Voting Procedures (**GNSO Operating Procedures
> 4.4*[gnso.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_co
> uncil_gnso-2Doperating-2Dprocedures-2D22sep11-2Den.pdf&d=DQMFaQ&c=FmY1
> u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVE
> R-_lK-PAQ64rKHs&m=55oYi9y1UeIL5juaxAkqpioz33PyWqjoetRz4HfuZU0&s=jAo-z5
> qhcfq-MJtldm4uEeMDsiYMIiA06sgcu-FMbr8&e=>*)*
>
> 4.4.1 Applicability
> Absentee voting is permitted for the following limited number of
> Council motions or measures.
> a. Initiate a Policy Development Process (PDP); b. Approve a PDP
> recommendation; c. Recommend amendments to the GNSO Operating
> Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for
> election.
>
> 4.4.2 Absentee ballots, when permitted, must be submitted within the
> announced time limit, which shall be 72 hours from the meeting's
> adjournment. In exceptional circumstances, announced at the time of
> the vote, the Chair may reduce this time to 24 hours or extend the
> time to 7 calendar days, provided such amendment is verbally confirmed
> by all Vice-Chairs present.
>
> 4.4.3 The GNSO Secretariat will administer, record, and tabulate
> absentee votes according to these procedures and will provide
> reasonable means for transmitting and authenticating absentee ballots,
> which could include voting by telephone, e- mail, web-based interface,
> or other technologies as may become available.
> 4.4.4 Absentee balloting does not affect quorum requirements. (There
> must be a quorum for the meeting in which the vote is initiated.)
>
> Reference (Coordinated Universal Time) 21:00 UTC Local time between
> October and March Winter in the NORTHERN hemisphere
> ----------------------------------------------------------------------
> ------ California, USA (_PDT) _UTC-8 +0DST 13:00 San José, Costa Rica
> UTC--6 +0DST 15:00 Iowa City, USA (CDT
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__fr.wikipedia.org_
> wiki_UTC-25E2-2588-259206-3A00&d=DQMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPS
> S6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=55oYi9
> y1UeIL5juaxAkqpioz33PyWqjoetRz4HfuZU0&s=lpAnNGMFiP39IIgLn917cyE6YPY12D
> Fo3Xq8yCt3U6E&e=>)
> UTC--6 +0DST 15:00
> New York/Washington DC, USA (EST) UTC-5 +0DST 16:00 Buenos Aires,
> Argentina (_ART_) UTC-3+0DST 18:00 Rio de Janiero, Brazil (BRST) UTC-2
> +0DST 17:00 London, United Kingdom (GMT) UTC+0DST 21:00 Bonn, Germany
> (CET) UTC+1+0DST 22:00 Cairo, Egypt, (EET) UTC+2 +0DST 23:00 Istanbul,
> Turkey (TRT) UTC+3+0DST 00:00 (2^nd December 2016) Singapore (SGT)
> UTC +8 +0DST 05:00 (2^nd December 2016) Tokyo, Japan (JST) UTC+9+0DST
> 06:00 (2^nd December 2016) Sydney/Hobart, Australia (AEDT)
> UTC+11+0DST 08:00 (2^ND December 2016)
> ----------------------------------------------------------------------
> ------ DST starts/ends on last Sunday of March 2017, 2:00 or 3:00
> local time (with exceptions)
> ----------------------------------------------------------------------
> For other places see
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.co
> m-5Btimeanddate.com-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7x
> cl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSv
> z5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=3VDlD7et-T53-mx7KcjlCHW3sidUxLpVuH2RdE
> IKX0k&e=
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.c
> om&d=DQMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko
> 8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=tCBSvLOuNpTkJ9SsdRLACXivZ-3cGt_UI8
> J6Vgmi7AU&s=Pi6sQfC8Whv0u4vxYv08Ac0jaJMZBTzgmpxb4_387WA&e=>_
> _https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_zqkas
> 4h-5Btinyurl.com-5D&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4
> I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5u
> kTPKhkKh8-cBX7KOQW3kmtnjDM&s=LDKZD89yu5n7-RtfrKbHZXKpboztO38jBMAiBMjTt
> 5U&e=
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_zqkas
> 4h&d=DgMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko
> 8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=-y8r7d6ely2-auB71o09HkFgPZ8rQYMg1u
> -6Fisv8RY&s=GQrrb-5wfVwExPeuYPyTdP-lCTA795_FUFaUNe77cYs&e=>
>
> Please let me know if you have any questions.
>
> Thank you very much
> Kind regards,
>
>
>
> Nathalie
>
>
> --
>
> Nathalie Peregrine
> Specialist, SOAC Support (GNSO)
> Internet Corporation for Assigned Names and Numbers (ICANN)
> Email: nathalie.peregrine@xxxxxxxxx <nathalie.peregrine@xxxxxxxxx >
> Skype: nathalie.peregrine.icann
>
> Find out more about the GNSO by taking our interactive courses
> <learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_si
> tes_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=oVvfyej1KKlrSvz5ukTPKhkKh8-cBX7KOQW3kmtnjDM&s=14O7ybuMQkeGYLZUZLnDWXePmxqGE6tflYvnr9Jlob8&e=
> >
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|