Tags API (3) , Conference (8) , Dispatcher (2) , Geneva (1) , Go (6) , Guardian (1) , I2P (1) , IETF (7) , IPC (3) , Localization (1) , MASQUE (1) , Minecruft (1) , Multipath (1) , Obfs4 (1) , Obfuscation (2) , Operator (3) , PTIM (2) , PTIM2020 (7) , PTSpec (2) , Rhizome (1) , Shapeshifter (1) , Spec (2) , Specification (3) , Swift (1) , TCP (1) , UMD (1) , Virtual (8) , conference (1) , create (2) , developer (41) , grants (12) , implement (32) , implementation (9) , library (2) , marionette (1) , meeting (18) , minecruft (1) , repository (1) , research (3) , shapeshifter (1) , software (1) , specification (1) , transport (14) , video (1) , virtual (19) , Archives by Date
September 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
August 2021
July 2021
March 2021
December 2020
October 2020
September 2020
January 2020
December 2019
March 2019
February 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
July 2017
June 2017
May 2017

subscribe via RSS

Pluggable Transports Specification v2.2 released

Updated:

The latest version of the Pluggable Transports community specification has been uploaded to the github repository. The latest completed specification can be found in the releases folder, along with all numbered versions. The latest update was to the Dispatcher module, which is updated to V2.2. All other modules remain as V2.1. Changes made in PT V2.2 are backwards-compatible with V2.1 and V2.0.

Changes to this version of the spec are:

  1. Reduced Use of Microformats in IPC parameters New parameters will be introduced which have simplified values. The old parameters will be kept for backwards compatibility.

  2. User Settable Proxy Listen Address A new command line flag will be added that allows the user to specify the proxy listener address.

  3. Reduced Number of Required IPC Parameters All IPC parameters will be marked in the specification as optional except for those which are actually required because no good default parameter value can be chosen.

  4. Improved Logging in IPC A new IPC protocol message will be introduced to carry logging information. Additionally, a new command line option will be introduced to control IPC logging, as opposed to other logging that the transports might do either internally or using the dispatcher’s logging facilities.

Do you want to contribute to future iterations and revisions of the specification? Set yourself up as a “watcher” in the repository, and feel free to add issues and ideas.