.frogans: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 8: | Line 8: | ||
|registryprovider = [[AFNIC]] | |registryprovider = [[AFNIC]] | ||
|registrations = | |registrations = | ||
|date = | |date = 19 April 2014 | ||
|type = [[Brand TLD]] | |type = [[Brand TLD]] | ||
|category = | |category = | ||
| Line 16: | Line 16: | ||
}} | }} | ||
'''.frogans''' is a [[Brand TLD]] | '''.frogans''' is a [[Brand TLD]] delegated in [[ICANN]]'s [[New gTLD Program]]. The applicant and now Registry Operator is [[OP3FT]].<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref> The proposed application succeeded and was delegated to the [[Root Zone]] on 19 April 2014.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated Strings, ICANN.org] Retrieved 30 May 2014</ref> | ||
==Application Details== | ==Application Details== | ||
| Line 64: | Line 64: | ||
==Delegation and Availability== | ==Delegation and Availability== | ||
.frogans was delegated to the [[Root Zone]] of the [[DNS]] on 19 April, 2014, completing the successful application for the string.<ref name="delegation"></ref> | .frogans was delegated to the [[Root Zone]] of the [[DNS]] on 19 April, 2014, completing the successful application for the string.<ref name="delegation"></ref> | ||
==Links== | |||
Official Web site of the Frogans technology: https://www.frogans.org/en/main.html | |||
==References== | ==References== | ||
Latest revision as of 12:14, 12 May 2015
| Status: | Delegated |
| Registry Provider: | AFNIC |
| Date Implemented: | 19 April 2014 |
| Type: | Brand TLD |
| Priority #: | 1209 - OP3FT |
More information: 
| |
.frogans is a Brand TLD delegated in ICANN's New gTLD Program. The applicant and now Registry Operator is OP3FT.[1] The proposed application succeeded and was delegated to the Root Zone on 19 April 2014.[2]
Application Details[edit | edit source]
The following is an excerpt from the applicant's response to question #18:
"The OP3FT (Organization for the Promotion, Protection and Progress of Frogans Technology) is a French non-profit organization established on March 17, 2012 for ensuring that, in the public interest, the development of Frogans technology, begun in 1999, be carried out irrevocably in a neutral, open and transparent manner and that its access be guaranteed to all Internet users.
As a non-profit organization acting in the public interest, the object of the OP3FT is to hold, promote, protect and progress Frogans technology in the form of an open standard for the Internet that is free to use by all.
More generally, the object of the OP3FT is to contribute to the development of a secure and stable Internet that is open to innovations, and to support and finance public-interest initiatives or innovative actions of a social, educational or cultural nature in the area of information and communication technologies.
The support and financing of these actions, programs and⁄or initiatives take place in compliance with the principles of openness and transparency that contribute to the spread of progress made in the area of information and communication technologies to the greatest number of people.
The works that the OP3FT must accomplish to fulfill its mission are detailed in its Bylaws which are available to the public.
1. Frogans technology[edit | edit source]
Frogans technology allows the implementation of a new application layer on the Internet, called the “Frogans layer,” alongside the other Internet application layers such as Email or the World Wide Web.
Frogans technology, which is secure and simple, allows for the publication of Frogans sites. A Frogans site is a set of Frogans pages, hyperlinked between each other, which is put on line on the Internet, or on an intranet, at a Frogans address. Frogans sites can be published by anyone.
Frogans technology uses standards that are open and free, such as the DNS, Unicode, the XML format, the HTTP protocol and the TLS (SSL) protocol.
The Frogans layer will be introduced on the Internet in the near future.
2. Use of the .frogans gTLD[edit | edit source]
The OP3FT will use the .frogans gTLD with the aim of ensuring the security, stability and reliability of the Frogans layer for the benefit of all Internet users.
The OP3FT will use .frogans gTLD domain names for addressing the computers that are dedicated to the functioning of the Frogans layer on the Internet.
These computers are to be used, for example:
- for the distribution of the free software application that allows all Internet users to navigate Frogans sites (Frogans Player);
- for the resolution of Frogans addresses from anywhere on the Internet.
This use of the .frogans gTLD is inspired by the use of the .net gTLD, as specified by Jon Postel in RFC 1591 (March 1994).
The OP3FT will not use .frogans gTLD domain names for naming Frogans sites. Indeed, the global addressing system of the Frogans layer (Frogans Network System) relies on Frogans addresses, whose specific and simple pattern (network*site) is not related to the Uniform Resource Identifier (URI) scheme.
The use of the .frogans gTLD adheres to ICANNʹs principles for keeping the Internet secure, stable and interoperable, while encouraging more innovation on the Internet."[3]
Contract Signed[edit | edit source]
On 19 December 2013 OP3FT received a Registry Agreement signed by ICANN for .frogans after passing all the required processes needed to become a Registry Operator for the string.[4]
Delegation and Availability[edit | edit source]
.frogans was delegated to the Root Zone of the DNS on 19 April, 2014, completing the successful application for the string.[2]
Links[edit | edit source]
Official Web site of the Frogans technology: https://www.frogans.org/en/main.html
References[edit | edit source]
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ 2.0 2.1 Delegated Strings, ICANN.org Retrieved 30 May 2014
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 28 Feb 2013
- ↑ Registry Agreements, ICANN.org Retrieved 30 Dec 2013