Content Comparison

Notes/ Action Items

Action Items:

1. Recommendation 30: Staff will finalize the charter and send it out for a two-week consensus call;
2. Recommendation 31: Staff will incorporate suggested changes based on the discussion on the 17 August call and send the revised version out for further review and discussion;
3. Recommendations 26/27/28/29: Staff will prepare a draft charter;
4. Recommendation 6: Staff will prepare a draft charter;
5. Timeline: Staff will update the timeline for discussion at the call on 31 August;
6. Meeting/Update at ICANN60: Staff will send a note to the list indicating that there will be a regularly scheduled meeting the week before ICANN60 so unless there are objections the suggestion is to not meet in person at ICANN60 as there will likely be conflicts; staff will request a slot in the GNSO Council schedule for an update from the WG on its progress.

Notes:

1. Recommendation 30:

-- Determined that the first part has been done -- the so-called “policy.” 

-- There is a process available in order where the different groups can rely on.

-- Community budget requests can be found here: https://icann-community.atlassian.net/wiki/x/vgRbBg for those interested.

-- Decisions for FY2017 are posted here: https://icann-community.atlassian.net/wiki/x/rQlbBg

2. Recommendation 31:

-- Either we say this will not be possible or suggest an alternative approach.

-- It is really important to find some negotiated way to have GAC involvement, even if an informal role.  Need to re-write this recommendation to allow informal involvement.  Might agree to observer status.

-- The Consultation Group included the GNSO and the GAC.  What are we trying to accomplish?  A GAC representative cannot represent the whole view of the GAC.

--  Action: Revise the charter to note that the GNSO-GAC Consultation Group has completed its work, note its recommendations and that GAC members cannot act as even informal liaisons, and offer ways that the GAC can become involved (Work Track 5).  Include justification for revising the recommendation.

From the chat:

Marika Konings: Do note that this is an issue that was also considered by the GAC-GNSO Consultation Group. The GAC is of the view that no one, apart from the GAC Chair, can represent the GAC and as such they are not willing to appoint liaisons to other SO/ACs or WGs.

Marika Konings: it may be worth asking the question again to meet this recommendation, but the response will likely be along similar lines, unless perspectives have changed in the meantime....

Marika Konings: Maybe it is a question for the GAC to see what they would consider feasible and practical as they do seem to want to be more actively engaged in PDPs?

Krishna Seeburn (Kris): We can still recommend  for informal....

Rafik: @marika a question already asked several times to GAC I think :)

Krishna Seeburn (Kris): i thnink observer status could work

Pascal Bekono: Could you define 4.  "Options" ???

Marika Konings: @Rafik - yes, but maybe one day the response is different, and in any case, I don't think this group can decide on what the GAC should be doing or providing, without their agreement ;-)

3. Meeting Slot at ICANN60/GNSO Update:

-- How does that fit with our usual schedule?

-- We do need to deliver a report to the GNSO.  Staff will request a slot.

-- Action: Staff will determine where we are in the schedule and if it is an off week suggest not holding a F2F meeting.  Staff will request a slot for an update to the GNSO.