[NCUC-DISCUSS] Spec 11 Drafting Team
Mueller, Milton L
milton.mueller at pubpolicy.gatech.edu
Tue Sep 1 23:35:43 CEST 2015
Interesting - and objectionable - that governments (who are not registries) are included and members of the public are not.
From: ncuc-discuss-bounces at lists.ncuc.org [mailto:ncuc-discuss-bounces at lists.ncuc.org] On Behalf Of James Gannon
Sent: Tuesday, September 1, 2015 2:44 PM
To: NCUC-discuss
Subject: [NCUC-DISCUSS] Fwd: Spec 11 Drafting Team
Hi All,
I thought it might be useful to those of us who are security minded to note that the drafting team for a security framework around Specification 11 of the newGTLD registry agreement has kicked off its work.
I asked if there was the opportunity to join the group as an observer but unfortunately at this stage of their work (Early drafting) they are keeping the group quite small (As seen below) I believe that this may be pretty normal practise for initial workgroups that are focussed on issues related to the contracted parties but I had figured it was worth asking, I will try and keep an eye on the work as they progress and keep everyone here updated as I can.
I noticed that we have a member of the NCUC EC Zuan Zhang (Peter Green) participating in the group however on behalf of the registries, so we might be able to get some updates from Peter as the work begins to produce some deliverables and documents.
As security issues are at the forefront of a lot of work these days and as more focus is placed on cybersecurity issues within ICANN I think that this is an important group to follow the work on closely as it will likely set a baseline for a lot of work to come on whats expected of the contracted parties when it comes to being responsive to security threats and the suggestion that they should have an active program in place to detect and respond in real time. Its important to note that for the moment this drafting team is only concerned with coming up with an initial best-practices framework around this issue and will not result in binding changes on the registries and won't be incorporated in the registry agreement yet, but I would think that if the initial work is found to be fruitful it might be something that would be looked at in the future.
Hope people find this useful to know,
-James Gannon
Begin forwarded message:
From: Fabien Betremieux <fabien.betremieux at icann.org<mailto:fabien.betremieux at icann.org>>
To: James Gannon <james at cyberinvasion.net<mailto:james at cyberinvasion.net>>
Subject: Re: Spec 11 Drafting Team
Date: 1 September 2015 17:07:32 IST
Hello James,
Members of the Framework Drafting Team are either representatives of
Registry Operator, Registrars or Governments (GAC/PSWG). We don¹t have a
specific observer status for other members of the community at this point
of our developments (which started only recently).
However, all developments of the Drafting Team are public. You will find
all available information on this workspace:
https://community.icann.org/display/S1SF/Spec+11+Security+Framework+Home
Let me know if you need any additional information.
Best Regards
--
Fabien Betremieux
Sr. Registry Services & Engagement Manager
Global Domains Division, ICANN
US: +1 310 463 5334 | FR: +33 7 60 09 09 40 | Skype: fabien.betremieux
-----Original Message-----
From: James Gannon <james at cyberinvasion.net<mailto:james at cyberinvasion.net>>
Date: Sunday, August 30, 2015 at 1:29 PM
To: Fabien Betremieux <fabien.betremieux at icann.org<mailto:fabien.betremieux at icann.org>>
Subject: Spec 11 Drafting Team
Hi Fabien,
I had a quick question for you, does the drafting team for Spec 11 allow
observers in their process, I¹m a security policy consultant and would be
very interested in following the Spec 11 work as it evolves as an
observer (Silent if necessary) given that I am not currently affiliated
with any of the identified stakeholders.
Thanks in advance.
-James Gannon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20150901/2c090fa1/attachment-0002.html>
More information about the Ncuc-discuss
mailing list