HSTLD: Difference between revisions
Created page with "Image:UnderConstruction.png '''HSTLD''' refers to '''High Security Top Level Domains'''. They were basically established under a High Security Top Level Domain Program of th..." |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Image:UnderConstruction.png]] | [[Image:UnderConstruction.png]] | ||
'''HSTLD''' refers to '''High Security Top Level Domains'''. | '''HSTLD''' refers to '''High Security Top Level Domains'''. [[ICANN]] established HSTLDs under a High Security Top Level Domain Program in order to increase the security and trust for the top-level domain ([[TLD]]) registry operators who were interested in becoming a part of the program. Although [[ICANN]] started the program originally, it does not govern current HSTLD programs and is not liable for issues that come out from the use or non-use of HSTLD standards.<ref name="link3">[http://domainincite.com/icann-told-to-ban-bank-or-get-sued/ domainincite.com]</ref> | ||
== Who works towards HSTLD program? == | == Who works towards HSTLD program? == | ||
A community led High Security TLD Advisory (HSTLD AG) has been developed to look after the HSTLD program controls and criteria<ref name="link2">[http://www.icann.org/en/public-comment/comment-summary-analysis-hstld-draft-program-development-snapshot-12nov10-en.pdf icann.org]Public comments, retrieved March 20, 2011</ref> | A community-led High Security TLD Advisory Group (HSTLD AG) has been developed to look after the HSTLD program controls and criteria.<ref name="link2">[http://www.icann.org/en/public-comment/comment-summary-analysis-hstld-draft-program-development-snapshot-12nov10-en.pdf icann.org] Public comments, retrieved March 20, 2011</ref> The Advisory Group (AG) meets on a regular basis to build on the concept of a security verification program for the TLDs. This Advisory Group is comprised of members from the ICANN staff and members of the community who are keen on assisting in the development of the program as well as people who are experts in fields related to the program such as auditing, certification, security and programs.<ref name="link1">[http://www.tldnews.co.uk/2010/09/27/icann-seeks-input-on-new-high-security-programme-aimed-at-selected-tlds/ tldnews.co.uk]</ref> | ||
ICANN had also requested information from potential contractors and other parties interested in its High Security Top-Level Domains (HSTLD) Advisory Group in evaluation and shaping of the program.<ref name="link1">[http://www.tldnews.co.uk/2010/09/27/icann-seeks-input-on-new-high-security-programme-aimed-at-selected-tlds/ tldnews.co.uk]</ref> | ICANN had also requested information from potential contractors and other parties interested in its High Security Top-Level Domains (HSTLD) Advisory Group in the evaluation and shaping of the program.<ref name="link1">[http://www.tldnews.co.uk/2010/09/27/icann-seeks-input-on-new-high-security-programme-aimed-at-selected-tlds/ tldnews.co.uk]</ref> | ||
== Problems for ICANN == | == Problems for ICANN == | ||
In November | In November 2010, a major financial lobbyist group named BITS threatened to sue ICANN if it didn't put restrictions on [[.bank]] TLDs. BITS, a technology policy branch of the Financial Services Roundtable, was of the opinion that there was a need to ban financial TLDs from the first round of new Top Level Domains, at least until new rules concerning security were developed. In reaction to this, the HSTLD AG put more emphasis on creating technology policy specifications for the sake of registries responsible for HSTLDs. <ref name="link3">[http://domainincite.com/icann-told-to-ban-bank-or-get-sued/ domainincite.com]</ref> | ||
== Future of HSTLD == | == Future of HSTLD == | ||
ICANN | ICANN and the HSTLD AG mutually agreed that it was of value to conduct a Request for Information (RFI) on the program. ICANN is committed to to reducing the malicious conduct in the applications of the new GTLDs and provides its full support towards the development of the HSTLD as an independent and voluntarily operated program.<ref name="link2">[http://www.icann.org/en/public-comment/comment-summary-analysis-hstld-draft-program-development-snapshot-12nov10-en.pdf icann.org]Public comments, retrieved March 20, 2011</ref> | ||
== References == | == References == | ||
Revision as of 00:03, 2 April 2011
HSTLD refers to High Security Top Level Domains. ICANN established HSTLDs under a High Security Top Level Domain Program in order to increase the security and trust for the top-level domain (TLD) registry operators who were interested in becoming a part of the program. Although ICANN started the program originally, it does not govern current HSTLD programs and is not liable for issues that come out from the use or non-use of HSTLD standards.[1]
Who works towards HSTLD program?[edit | edit source]
A community-led High Security TLD Advisory Group (HSTLD AG) has been developed to look after the HSTLD program controls and criteria.[2] The Advisory Group (AG) meets on a regular basis to build on the concept of a security verification program for the TLDs. This Advisory Group is comprised of members from the ICANN staff and members of the community who are keen on assisting in the development of the program as well as people who are experts in fields related to the program such as auditing, certification, security and programs.[3]
ICANN had also requested information from potential contractors and other parties interested in its High Security Top-Level Domains (HSTLD) Advisory Group in the evaluation and shaping of the program.[3]
Problems for ICANN[edit | edit source]
In November 2010, a major financial lobbyist group named BITS threatened to sue ICANN if it didn't put restrictions on .bank TLDs. BITS, a technology policy branch of the Financial Services Roundtable, was of the opinion that there was a need to ban financial TLDs from the first round of new Top Level Domains, at least until new rules concerning security were developed. In reaction to this, the HSTLD AG put more emphasis on creating technology policy specifications for the sake of registries responsible for HSTLDs. [1]
Future of HSTLD[edit | edit source]
ICANN and the HSTLD AG mutually agreed that it was of value to conduct a Request for Information (RFI) on the program. ICANN is committed to to reducing the malicious conduct in the applications of the new GTLDs and provides its full support towards the development of the HSTLD as an independent and voluntarily operated program.[2]
References[edit | edit source]
- ↑ 1.0 1.1 domainincite.com
- ↑ 2.0 2.1 icann.org Public comments, retrieved March 20, 2011 Cite error: Invalid
<ref>tag; name "link2" defined multiple times with different content - ↑ 3.0 3.1 tldnews.co.uk