forked from I2P_Developers/i2p.www
490 lines
18 KiB
HTML
490 lines
18 KiB
HTML
{% extends "global/layout.html" %}
|
|
{% block title %}{% trans %}Naming and Addressbook{% endtrans %}{% endblock %}
|
|
{% block lastupdated %}{% trans %}June 2018{% endtrans %}{% endblock %}
|
|
{% block accuratefor %}0.9.34{% endblock %}
|
|
{% block content %}
|
|
<h2 id="overview">{% trans %}Overview{% endtrans %}</h2>
|
|
|
|
<p>{% trans -%}
|
|
I2P ships with a generic naming library and a base implementation
|
|
designed to work off a local name to destination mapping, as well as an
|
|
add-on application called the <a href="#addressbook">addressbook</a>.
|
|
I2P also supports <a href="#base32">Base32 hostnames</a> similar to Tor's .onion addresses.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
The addressbook is a web-of-trust
|
|
driven secure, distributed, and human readable naming system, sacrificing only
|
|
the call for all human readable names to be globally unique by mandating only
|
|
local uniqueness. While all messages in I2P are cryptographically addressed
|
|
by their destination, different people can have local addressbook entries for
|
|
"Alice" which refer to different destinations. People can still discover new
|
|
names by importing published addressbooks of peers specified in their web of trust,
|
|
by adding in the entries provided through a third party, or (if some people organize
|
|
a series of published addressbooks using a first come first serve registration
|
|
system) people can choose to treat these addressbooks as name servers, emulating
|
|
traditional DNS.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans namingdiscussion=site_url('docs/discussions/naming') -%}
|
|
NOTE: For the reasoning behind the I2P naming system, common arguments against it
|
|
and possible alternatives see the <a href="{{ namingdiscussion }}">naming discussion</a>
|
|
page.
|
|
{%- endtrans %}</p>
|
|
|
|
|
|
<h2 id="components">{% trans %}Naming System Components{% endtrans %}</h2>
|
|
|
|
<p>{% trans -%}
|
|
There is no central naming authority in I2P.
|
|
All hostnames are local.
|
|
{%- endtrans %}</p>
|
|
|
|
<p>{% trans -%}
|
|
The naming system is quite simple and most of it is implemented
|
|
in applications external to the router, but bundled with
|
|
the I2P distribution.
|
|
The components are:
|
|
{%- endtrans %}</p>
|
|
|
|
<ol>
|
|
<li>{% trans -%}
|
|
The local <a href="#lookup">naming service</a> which does lookups
|
|
and also handles <a href="#base32">Base32 hostnames</a>.
|
|
{%- endtrans %}</li>
|
|
<li>{% trans -%}
|
|
The <a href="#httpproxy">HTTP proxy</a> which asks the router for lookups and points
|
|
the user to remote jump services to assist with failed lookups.
|
|
{%- endtrans %}</li>
|
|
<li>{% trans -%}
|
|
HTTP <a href="#add-services">host-add forms</a> which allow users to add hosts to their local hosts.txt
|
|
{%- endtrans %}</li>
|
|
<< |