Discuss mailing list

[Jonah Aragon <jonah AT triplebit.net>]

Does anyone have anything else to add or comment on? If not, I’m hoping to start a voting thread tomorrow on this proposal. 

I would just like to add that this is not any kind of charter intended to be the forming policies of a new organization or nonprofit. It isn’t even a complete set of policies, just a small set pertaining to voting and some small infrastructure requirements. It mainly exists for clarification of what the community here expects for new members. 

There were some mentions of having a procedure to remove people who aren’t contributing or are spamming the mailing list, but I’m hesitant to add any policies regarding that at the moment. I don’t want to carelessly add something that could be misconstrued (possibly maliciously) in a way that’d lead to the removal of actual members. It’s somewhat difficult to differentiate clearly between active trolls and people with opinions that conflict with your own. If we do decide to add policies regarding that, I think that should be done on a separate discussion and proposal.

Thanks!

Jonah

On Oct 21, 2017, at 4:47 PM, Jonah Aragon <jonah AT triplebit.net> wrote:

ADDITION — Please consider the following as part of this discussion:

Section VI: Peered Network Guidelines

This section only applies to peered networks added to the OpenNIC root zone after this proposal has passed a vote of the community; networks peered prior to that date SHOULD consider this document a good guideline to follow. This section does not apply to any TLDs operated by OpenNIC. 

Peering with another alternative DNS root SHOULD represent a mutual two-way relationship.

The peered network:

- MUST provide access to OpenNIC’s TLD namespaces, without exception.

- MUST be willing to make every attempt to operate their network and the peering relationship in the long-term, to maintain stability.

- MUST provide a proxy Tier 1 server dedicated to peering with OpenNIC, that will be used as the authority for their namespaces by other OpenNIC servers. This server should follow all Tier 1 server guidelines.

- MUST provide a representative, to be available at a certain email contact and on the OpenNIC Mailing List.

- SHOULD be in operation for at least one (1) year.

- SHOULD have an abuse process in place to prevent malware on their namespaces.

- SHOULD be held accountable to OpenNIC abuse policies, especially in regard to malware.

- SHOULD provide registrations available to any user on all namespaces.

- SHOULD NOT be held accountable to OpenNIC organizational policies.

- Will OPTIONALLY provide a representative to be available on the #opennic IRC channel on Freenode, for immediate communication for time-sensitive issues.

OpenNIC:

- SHALL provide access to the peered network’s namespaces.

- SHOULD provide access to every namespace the peered network hosts.

- SHOULD NOT be required to host a Tier 1 server acting as a bridge between the two networks.

- SHOULD NOT blacklist access to any domains on the peered network from the Tier 1 network. 

Failure to meet these requirements may result in the disintegration of OpenNIC and the peered network’s agreement.

Jonah