[Gac-gnso-cg] FW: For your review - notes from today's meeting

[Manal Ismail]

Many thanks Marika for the detailed notes .. Very helpful ..

The counterpart issue has already been conveyed by Olof .. 

I do not have any known conflicts with schedule as suggested ..

Will try to trigger the discussion on the substance in a separate thread
.. 

Kind regards

--Manal

 

From: gac-gnso-cg-bounces at icann.org
[mailto:gac-gnso-cg-bounces at icann.org] On Behalf Of Marika Konings
Sent: Wednesday, November 05, 2014 11:20 AM
To: gac-gnso-cg at icann.org
Subject: [Gac-gnso-cg] FW: For your review - notes from today's meeting

 

Resending as I don't think my message went through yesterday.

 

Best regards,

 

Marika

 

From: Marika Konings <marika.konings at icann.org>
Date: Tuesday 4 November 2014 16:19
To: "gac-gnso-cg at icann.org" <gac-gnso-cg-bounces at icann.org>
Subject: For your review - notes from today's meeting

 

Dear All, 

 

Please find below the notes from today's meeting. For those that were
able to join, please review and let me know if I've missed anything. For
those that were not able to join, please review and share with the list
if you have any additional views or comments.

 

The next meeting will be scheduled for Tuesday 18 November at 15.00 UTC.
>From there, we'll continue with our meetings every two weeks - please
let us know ahead of time if there are any meetings that you cannot make
so we can plan accordingly should there be more members unavailable for
certain dates.

 

Best regards,

 

Marika

 

Notes 4 November 2014:

 

Taking stock of LA meeting:

*	Session with full committee was very timely - opening of
dialogue between GAC-GNSO very useful
*	Hope for more GAC engagement over coming months as modalities
are defined
*	New GAC Chair also recognises the importance of this initiative
*	Hopefully this will result in additional participants in this
effort

 

Update on Work Tracks

*	Reminder on deliverables of charter which have resulted in the
two work tracks (1) A documented process (table, flow chart, ...etc.)
for ongoing smooth and timely information exchange between the GAC and
the GNSO organizations (GNSO Liaison to the GAC , permanent
liaison/consultative group, ... etc.) 2) An agreed documented process
(table, flow chart, ... etc.) for ongoing smooth early engagement of GAC
in GNSO PDP projects; along with an agreed documented procedure to be
followed where GAC early input is in conflict with a GNSO proposal and a
mutual agreement could not be reached
*	PDP Work Track: little progress has been made, but also noting
the link between the other track. Some work has been done on possible
early engagement opportunities in the PDP, but further discussions /
input are needed. Commitment would be needed from both sides to make
possible changes work, but would ideally be light touches to the
process. May be time to put to the GAC the quick look mechanism approach
- the earlier the GAC has an opportunity to express its view or indicate
its interest to be engaged, the better. Suggestion for GAC members to
consider putting together proposal for Quick Look Mechanism for GAC
consideration - timing will be crucial as information would need to be
provided prior to GAC meetings so that quick look mechanism could be
employed and feedback could possibly be provided via GNSO liaison.
Outcome of quick look mechanism could also be recorded as part of the
GAC communique. What happens if PDP work advances to next stage before
GAC is able to provide input - is that an issue or can it be taken into
account as part of a next phase? Initial idea of quick look mechanism is
to provide an indication during the Issue Report phase of whether there
are public policy implications, not necessarily substantive input which
will be more important when the GNSO PDP WG commences its deliberations
and as such may not take as much time as the preparation of substantive
input which ideally would contain detail as well as rationale.
Alternatively, if more time is needed, GAC could already be informed
immediately following the request for an Issue Report, instead of once
the Preliminary Issue Report is posted for public comment. Quick look
mechanism could potentially be developed intersessional but without
being binding but providing important guidance to both the GNSO and the
GAC. Decision on outcome of a quick look mechanism check probably will
need to be made during an ICANN meeting, may not be possible
intersessionally. If the decision is that there are likely public policy
implications, this could trigger the formation of a GAC committee to
develop substantive input to provide input by the time the PDP WG is
formed. Preliminary Issue Report may not be necessary for trigger quick
look mechanism, possibly a short description (1-2 pages) of the issue
could be sufficient for the GAC to consider the issue (noted that GAC
could always revise its view based on additional information coming
available). 

 

Counterpart inside the GAC for day-to-day contact

*	Would be helpful to have a day-to-day co-ordination point for
Mason - peer to peer relationship with GAC member(s) 
*	If this relates to forwarding / sharing information, this could
be done via Olof
*	One of the five vice-chairs could be awarded this
responsibility? Consider suggesting this to Thomas. 

 

Day-to-day Co-ordination

*	See latest version of day-to-day co-ordination document as well
as suggestion during F2F meeting for a possible joint WG. 
*	Continue discussion on the list

 

Agree on call schedule

*	Proposal to continue with meetings every two weeks - next
meeting to be scheduled for 18 November at 14.00 UTC. 
*	All encouraged to indicate ahead of meetings if not available

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gac-gnso-cg/attachments/20141110/d7175378/attachment.html>