kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update all proposals to conform to the proposal process

Browse Source
This commit is contained in:
str4d
2016-04-25 06:09:22 +00:00
parent 63fa249f54
commit 4d1c50af7a
27 changed files with 317 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
i2p2www/spec/proposals/109-pt-transport.rst
View File

@@ -6,22 +6,33 @@ PT Transport
:created: 2014-01-09
:thread: http://zzz.i2p/topics/1551
:lastupdated: 2014-09-28
:status: Draft
:status: Open
.. contents::
Introduction
============
The general idea is to use Pluggable Transports (PTs) as an I2P transport for
communication between routers. It would be an easy way to experiment with
alternative protocols, and get ready for I2P blocking resistance.
Thoughts
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