ICANN/GNSO GNSO Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] Action Item - GNSO/SSAC Liaison(s)

  • To: GNSO Council List <council@xxxxxxxxxxxxxx>
  • Subject: Re: [council] Action Item - GNSO/SSAC Liaison(s)
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Sat, 7 May 2016 14:38:14 +0000
  • Accept-language: en-US
  • Authentication-results: gnso.icann.org; dkim=none (message not signed) header.d=none;gnso.icann.org; dmarc=none action=none header.from=godaddy.com;
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector1-godaddy-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=sfgKgNYOI6kFgPk74+79DErdYZyOwjUjebFqes0Xnbk=; b=Bj7xa2Ewlhn7AwWnZNh1GeMTwRlh/qDec8fIV/JqQPpNaO9Qeo7V5cOIGwTVdTxGiO5uzKPiXt3sp21MR/DXtNb+A9zbL54RxXzGjiqzLmn82rtegBlOSkVbukTihHZVlc8IQYi9CwFrM5Iy0dKdldlCIfqUwJt2IAOYt7OB/ts=
  • In-reply-to: <2B142D29BAFF4F2D94FF8C0046789993@WUKPC>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <D33FF961.BBF6E%jbladel@godaddy.com> <571B5E89.1080001@mail.utoronto.ca> <2B142D29BAFF4F2D94FF8C0046789993@WUKPC>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23
  • Thread-index: AQHRnNj8YPihc9hgkEWGalEFDc2U1p+Xb2mAgAFT0ICAFItYgA==
  • Thread-topic: [council] Action Item - GNSO/SSAC Liaison(s)
  • User-agent: Microsoft-MacOutlook/

Thanks, Wolf-Ulrich, Stephanie, Julf, David, and Carlos for contributing your 
thoughts.  In order to bring this topic to a close for our next meeting, here’s 
what I’m hearing from the group:

  *   Change the format of the GNSO/SSAC interactions, post topics in advance 
and promote a more free flowing discussion.  Come prepared with questions, and 
encourage SSAC to tailor their materials & updates to active GNSO work.
  *   Leverage the overlap – encourage members who participate in both 
communities, and ICANN Staff, to highlight mutual areas of interest and flag 
for discussion by GNSO/SSAC.  For example,some SSAC resources are public, which 
would allow one or two Councilors to volunteer as informal liaisons (e.g. 
keeping up with the lists & new publications, and reporting back to Council 
with any material topics).
  *   Create an “SSAC Consultation” step as part of the start up activities of 
new PDPs.  Perhaps this could be merged with the existing SG/C 
comment/consultation steps?
  *   No strong consensus to establish a formal liaison at this time, but keep 
this path open if future circumstances warrant the position.

I hope this reflects our discussion.  If there are no further comments by 
Monday, I’ll report back to Patrik.

Thank you -


From: WUKnoben 
Reply-To: WUKnoben 
Date: Sunday, April 24, 2016 at 2:53
To: Stephanie Perrin 
James Bladel <jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>>, GNSO Council 
List <council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: Re: [council] Action Item - GNSO/SSAC Liaison(s)

I definitely agree with Stephanie, in particular No. 3. This exchange is of 
value if prepared with more detailed questions related to the impact of SSAC to 
GNSO work. As we do in relation to other ACs (e.g. GAC).
If this exchange could be improved then I see the formalization as 
consequential step.

Best regards


From: Stephanie Perrin<mailto:stephanie.perrin@xxxxxxxxxxxxxxxx>
Sent: Saturday, April 23, 2016 1:37 PM
To: James M. Bladel<mailto:jbladel@xxxxxxxxxxx> ; GNSO Council 
Subject: Re: [council] Action Item - GNSO/SSAC Liaison(s)

1.  I think this discussion is very valuable.  When Patrik has said, "we have 
this document, go read it", I have done so and found them to be excellent 
resources.  We should explore ways to support greater use of and understanding 
of their work, certainly.
2.  A formal liaison would be useful to keep their workplans and priorities on 
our radar, and vice verse.
3.  Advance planning for SSAC briefings, including suggested reading on their 
side,  and a list of questions on our side would make the briefings more 
relevant.  Then we could have a richer discussion.
4.  I think we should formalize a kind of SSAC review when we develop the PDP 
charters.  Consultation at that stage would ensure that relevant SSAC existing 
work. or future security concerns, could be flagged.  For instance, in the RDS 
PDP David mentioned, in my view the EWG report should be read with the SSAC 
comments on the EWG draft in hand.  Certainly we have several members of SSAC 
on the RDS pdp, but sometimes these things are hit and miss, a formal review 
could be helpful to ensure coverage, and a liaison would also be useful to help 
SSAC anticipate new work we are needing help on.
In short, all four of your bullets are great in my view.
Stephanie Perrin

On 2016-04-22 16:53, James M. Bladel wrote:
Council Colleagues -

Continuing with the “spring cleaning” of our Action Item list,  here’s another 
item that has been in a pending state for quite some time.

Yesterday I was able to meet with Patrik  (Chairs, SSAC) to discuss ideas to 
strengthen coordination between our two organizations, up to and including a 
formal exchange of liaisons.  As we’ve noted previously, the SSAC’s rules 
require that any of its members (including a potential liaison) would need to 
meet the general membership requirements, which include a non-disclosure 
agreement (NDA).

Patrik and I also discussed alternatives to a formal liaison that would keep 
the two groups mutually informed. We both agreed that the standard SSAC 
presentation/Q&A sessions at ICANN meetings had limited value, and we should 
revise the format to specifically address topics where either or both sides had 
specific questions or asks.

Furthermore, Patrik noted that some PDPs could benefit from existing or planned 
SSAC research, and we should reinforce the availability of the SSAC as a 
resource for new PDPs.  We also observed that there is significant membership 
overlap between some individuals and groups, and that this should be leveraged 
to enhance cooperation.  Finally, ICANN Staff can help facilitate communication 
between the GNSO (Council & PDPs) and SSAC, if they flag topics that have 
potentially shared interests, and raise this with leadership of all groups.

Possible action items / paths forward:

  1.  Continue to pursue formal exchange of liaisons between the GNSO & SSAC, 
noting the constraints listed above.
  2.  Modify the SSAC/GNSO sessions at ICANN meetings to be a more free-flowing 
conversation about topics that share mutual interests.
  3.  Encourage PDPs and other GNSO groups to consider the utility & 
applicability of SSAC research in their work.
  4.  Ask Staff to help facilitate information exchange between the two groups.

I look forward to your thoughts & comments on this subject.



<<< Chronological Index >>>    <<< Thread Index >>>