Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] peering with FreeNIC

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] peering with FreeNIC


Chronological Thread 
  • From: vv AT cgs.pw
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] peering with FreeNIC
  • Date: Tue, 7 Mar 2017 23:26:24 -0800
  • Importance: Normal


I'm not sure who would get confused. In any case
second level registration would serve no practical
purpose for us. Why would I "register" something
with myself?

~ Ole


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Dan, OpenNIC does "not support self-named or private Top-Level
> Domains". (http://wiki.opennicproject.org/AlternateNICs)
>
> I vote no on your proposal, Angélica. The filter is a good idea, but
> people could get confused as they might think that our roots are fully
> compatible with each other. However, behavior is not well-defined and
> we might slide into chaos. Also, I think second-level registration
> should be required.
>
>
> On 08.03.2017 01:02, Daniel Quintiliani wrote:
>> [...] I would however support peering if it was handled like
>> .radio.freenic or .smart.freenic.
>
>
> On 06.03.2017 20:36, Angélica Luna wrote:
>> Hello all,
>>
>> I'm one of the founding members of FreeNIC http://freenic.org/ a
>> totally free and open root that resolves all OpenNIC TLDs and most
>> ICANN ones in addition to TLDs chosen without rules or regulations
>> by anyone who wishes to join. Our TLDs are mainly for personal use;
>> we don't require second-level registration to be available. All
>> members have equal status as we have no leadership. I'm proposing a
>> partial peering agreement, as explained below.
>>
>> Because we have no rules, there's nothing stopping conflicting TLDs
>> from being registered. We currently have .radio and .smart, which
>> have been registered in the ICANN root. The ICANN .radio and .smart
>> have been deleted from our root zone. Shdwdrgn is in the process of
>> designing a filter that would prevent OpenNIC from resolving
>> FreeNIC TLDs that conflict with OpenNIC or ICANN should this
>> peering agreement be accepted. Peering wouldn't take place until
>> the filter has been implemented.
>>
>> Please discuss and vote.
> -----BEGIN PGP SIGNATURE-----
>
> iQIcBAEBCAAGBQJYv5oxAAoJEG4G1Hi2cA/ZoqgP/0cbAgBBisuEZW3NbHTtUtgz
> h3zYu+UGN/wiGVyKmJX26EwpyErMyFsbQLSK6pIvpW5GjEspuJG2dhjhilxqJrQp
> QSy5HOKjmQChJkU+YMykWvr76xF/SXlQqFrVPu5oO2QswlsVbbIjAFAPPQ+7KD3Y
> 6+FStATC8KUHebBBcCv1TYEw77pTR3qeIPCNyp1grgiwTV03VCTtGFF2ZV5WEcev
> LChO/z7gcu/GJN0VRb48gVsDGXkqUyrW0jxRQYlg0gT0hyIgINs0Kk8NCpxpjES8
> xx2JMYlrD8Ulk7IcQixVvtFQEYDz4dRAv9qdy98V89eywa0Q79UragNLSuxWfhZu
> iQzWCsJjSsohyxlN8LB0qlNFu0j7obe0q9SOrbU1gPGxSKZrj97XAxeqsCR9dHV2
> bbp/6WKrHfbuw3dQgmcQvVKf7iIPSts4VcQ+fWVvE/8NdxIXcHTSBSD0TFGWR0oM
> PBlBeTovOjVyYJ6TwB4Te9mg9cHA+5LDq1YMGH0PujK13L4tLu9GPDxobJ/3kh4e
> AHO6+Y/GhAc0buNtx01PcUAld+wD6t0fQzs33tJJOhksIfY3+E0B85oMAegihMsk
> fPxSYZuljjl2uU6U1NBi5GCoNHT6LmWAwjnxGTMSMCTK6bkggpxNBnzS9d217pl3
> 6sDz1UCUdytMgbrgu3Jc
> =JFNW
> -----END PGP SIGNATURE-----
>
>
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing
> discuss-unsubscribe AT lists.opennicproject.org
>




Archive powered by MHonArc 2.6.19.

Top of Page