AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
...
- TLD-OPS status - membership of the list has grown from 29 to 77 since the last conference call on Feb 24. Invitations to attend the WG sessions by the ccNSO Secretariat are reliant on all IANA Admin Contact email addresses are up to date
- Rules of Engagement - feedback on the two webinars on TLD-OPS "rules of engagement" have been discussed. The needs need for more clarity has resulted in the group refining their drafts draft set of rules over the next weeks, for instance, adding an example for each of the TLD-OPS colour levels. More information about the WG on http://ccnso.icann.org/workinggroups/secir-tld-ops-overview-02mar15-en.pdf
- Sharing of incident information - while the purpose of the group is to act as a contact repository for ccTLDs the group decided that they may share incident information which may be useful and relevant to a large number of subscribed ccTLDs.
Summary SECIR Conference Call #12
...
(1) TLD-OPS status. The number of ccTLDs that have subscribed to the TLD-OPS list has grown to 77 from 29 since our last conference call on Feb 24. As before, the ccNSO Secretariat will continue to invite ccTLDs and the WG therefore again requests all IANA Admin Contacts to regularly check their admin email address.
(2) Rules of engagement. We first discussed the feedback we received during and after our two webinars of Wed Mar 11on the TLD-OPS “rules of engagement”, which the community thought could be improved in terms of clarity. We decided to refine the draft set of rules in the coming weeks, for instance by adding an example for each of the TLD-OPS color levels.
(3) Sharing of incident information. During the webinars, several members of the community indicated they would like to share incident information on the list, for instance pertaining to botnets. While the main purpose of the TLD-OPS list is to act as a contact repository for ccTLDs, we decided that sharing incident information on the list would likely to be useful if the information is relevant for a relatively large number of subscribed ccTLDs. An example we discussed was a ccTLD wanting to notify its peers of an ongoing dictionary attack on the ccTLD’s name servers because the attack might soon “hop” to another ccTLD. If a ccTLD wants to share incident information with one or a few ccTLDs, then that ccTLD should use a different channel and not use the TLD-OPS list. We will incorporate these guidelines in the in the TLD-OPS overview document and in the TLD-OPS rules of engagement.
Our next conference call will take place in the week of Apr 8.
- The
...
- group's guidelines will stipulate the use of the main list for sharing but one example could be one ccTLD wanting to notify its peers of an ongoing dictionary attack on the ccTLD's name server because the attack might soon hop to another ccTLD.
- The next conference meeting will be during the week of April 8.
- SECIR members: Erwin Lansing (.dk), Jacques Latour (.ca), Frederico Neves (.br), Abibu Ntahigiye (.tz), Geng-Da Tsai (.tw), and Cristian Hesselman (.nl, chair)
- TLD-OPS homepage: http://ccnso.icann.org/resources/tld-ops-secure-communication.htm
SECIR homepage: http://ccnso.icann.org/workinggroups/secir.htm
SECIR members: Erwin Lansing (.dk), Jacques Latour (.ca), Frederico Neves (.br), Abibu Ntahigiye (.tz), Geng-Da Tsai (.tw), and Cristian Hesselman (.nl, chair)
- I have recommended subscribing to this list to the managers of my local ccTLD .ck and to other ccTLD managers on the PICISOC mailing list.
Informal Report on the ccNSO Council meeting 19 March 1200UTC
...
