47 lines
1.2 KiB
ReStructuredText
47 lines
1.2 KiB
ReStructuredText
============
|
|
PT Transport
|
|
============
|
|
.. meta::
|
|
:author: zzz
|
|
:created: 2014-01-09
|
|
:thread: http://zzz.i2p/topics/1551
|
|
:lastupdated: 2014-09-28
|
|
:status: Open
|
|
|
|
.. contents::
|
|
|
|
|
|
Overview
|
|
========
|
|
|
|
This proposal is for creating an I2P transport that connects to other routers
|
|
through Pluggable Transports.
|
|
|
|
|
|
Motivation
|
|
==========
|
|
|
|
Pluggable Transports (PTs) were developed by Tor as a way to add obfuscation
|
|
transports to Tor bridges in a modular way.
|
|
|
|
I2P already has a modular transport system that decreases the barrier to adding
|
|
alternative transports. Adding support for PTs would provide I2P with an easy
|
|
way to experiment with alternative protocols, and get ready for blocking
|
|
resistance.
|
|
|
|
|
|
Design
|
|
======
|
|
|
|
There are a few potential layers of implementation:
|
|
|
|
1. A generic PT that implements SOCKS and ExtORPort and configures and forks the
|
|
in and out processes, and registers with the comm system. This layer knows
|
|
nothing about NTCP, and it may or may not use NTCP. Good for testing.
|
|
|
|
2. Building on 1), a generic NTCP PT that builds on the NTCP code and funnels
|
|
NTCP to 1).
|
|
|
|
3. Building on 2), a specific NTCP-xxxx PT configured to run a given external in
|
|
and out process.
|