blob: dda088173750fc49ab5ba8c085ea87896e26b8a7 (plain
GNUnet Assigned Numbers Authority (GANA)
This Git repository contains various registries we maintain, for
GNUnet other projects that need names and numbers for use in network
protocols. If you need to open a new registry, please feel free
to contact us at firstname.lastname@example.org.
If you have Git access to GANA, you are generally authorized to add
new entries to the registries. Most registries are under a simple
first-come first-use policy. If you are unsure about the registration
policy of a particular registry, do ask email@example.com before making
Deleting or modifying existing entries (except improving comments)
should be done particularly carefully, so if unsure you might want to
double-check with firstname.lastname@example.org before changing or deleting
Barry Leiba wrote on April 4th 2020 that "Neither IANA nor
participants in the IETF will have any necessary expertise to evaluate
registration requests in the sort of registry described, and no one
will be well served by the creation of such a registry at IANA. It
would be far better to have a registration process be described in
this document involving experts from the industry as reviewers and
maintenance of the registrations by an industry organization, rather
than by IANA."
So here we are. As IETF/IANA "lack the necessary expertise to operate
a registry" for names and numbers used in network protocols, the
GNUnet project is happy to step up.
The GANA database is licensed under the GPL. See COPYING.
Each registry must have a unique name and all associated information
lives in a directory under that unique name in this Git repository.
Each registry must include at least the following files:
document describing the purpose of the registry in English
registration policy, explaining required fields and
the procedure for adding, updating and deleting entries
GNU recutils data file with all of the current entries in
GNU make makefile with a 'make check' target to run the validation logic.
Ideally, the registry.rec should be written such that the 'check' target
is simply invoking "recfix --check registry.rec".
Additional targets to convert data.rec to various formats may be defined.
In particular, see format.sh in this directory (try --help).