[Ssr2-review] rec 23 and 24: who is interested in hashing out thoughts?
Russ Housley
housley at vigilsec.com
Wed Dec 19 18:49:12 UTC 2018
I am interested in discussing follow-on recommendations, but I personally do not have time before the call on Thursday. The past two calls have gone more swiftly than I expected. Maybe we can talk about this under AOB if that happens again.
Russ
> On Dec 17, 2018, at 5:20 PM, k claffy <kc at caida.org> wrote:
>
>
>
>
> follow-on rec.
>
> i think rec 23 is focal to many other problems.
>
> k
>
> On Mon, Dec 17, 2018 at 03:28:22PM -0500, Russ Housley wrote:
>> KC:
>>
>> I think that the basic findings are already in the Google Doc. Are you looking for a brainstorm session on the final document wording or follow-on recommendations?
>>
>> Russ
>>
>>
>>> On Dec 15, 2018, at 8:21 PM, k claffy <kc at caida.org> wrote:
>>>
>>>
>>>
>>> i'm especially interested in who would like to donate an
>>> hour to discuss ideas to replace recommendation 23 with
>>> something that reflects all the comments i put in the doc,
>>> which will require you read them first. if you read them
>>> and want to join a call this month, please let me know by
>>> wed 19 dec. tnx -k.
>>>
>>>
>>>
>>>
>>> RECOMMENDATION 23: ICANN must provide appropriate resources for SSR-related
>>> Working Groups and Advisory Committees, consistent with the demands
>>> placed upon them. ICANN also must ensure decisions reached by Working
>>> Groups and Advisory Committees are reached in an objective manner that
>>> is free from external or internal pressure.
>>>
>>> RECOMMENDATION 24: ICANN must clearly define the charter, roles and
>>> responsibilities of the Chief Security Office Team.
>>
More information about the Ssr2-review
mailing list