{"action":"created","issue":{"url":"https://api.github.com/repos/Tribler/tribler/issues/2087","repository_url":"https://api.github.com/repos/Tribler/tribler","labels_url":"https://api.github.com/repos/Tribler/tribler/issues/2087/labels{/name}","comments_url":"https://api.github.com/repos/Tribler/tribler/issues/2087/comments","events_url":"https://api.github.com/repos/Tribler/tribler/issues/2087/events","html_url":"https://github.com/Tribler/tribler/issues/2087","id":148031425,"number":2087,"title":"IETF RFC writeup of Trustchain","user":{"login":"synctext","id":325224,"avatar_url":"https://avatars0.githubusercontent.com/u/325224?v=4","gravatar_id":"","url":"https://api.github.com/users/synctext","html_url":"https://github.com/synctext","followers_url":"https://api.github.com/users/synctext/followers","following_url":"https://api.github.com/users/synctext/following{/other_user}","gists_url":"https://api.github.com/users/synctext/gists{/gist_id}","starred_url":"https://api.github.com/users/synctext/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/synctext/subscriptions","organizations_url":"https://api.github.com/users/synctext/orgs","repos_url":"https://api.github.com/users/synctext/repos","events_url":"https://api.github.com/users/synctext/events{/privacy}","received_events_url":"https://api.github.com/users/synctext/received_events","type":"User","site_admin":false},"labels":[{"id":291602554,"url":"https://api.github.com/repos/Tribler/tribler/labels/MSc-Thesis-Work","name":"MSc-Thesis-Work","color":"ed2cd6","default":false}],"state":"open","locked":false,"assignee":{"login":"svanschooten","id":3600842,"avatar_url":"https://avatars0.githubusercontent.com/u/3600842?v=4","gravatar_id":"","url":"https://api.github.com/users/svanschooten","html_url":"https://github.com/svanschooten","followers_url":"https://api.github.com/users/svanschooten/followers","following_url":"https://api.github.com/users/svanschooten/following{/other_user}","gists_url":"https://api.github.com/users/svanschooten/gists{/gist_id}","starred_url":"https://api.github.com/users/svanschooten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/svanschooten/subscriptions","organizations_url":"https://api.github.com/users/svanschooten/orgs","repos_url":"https://api.github.com/users/svanschooten/repos","events_url":"https://api.github.com/users/svanschooten/events{/privacy}","received_events_url":"https://api.github.com/users/svanschooten/received_events","type":"User","site_admin":false},"assignees":[{"login":"svanschooten","id":3600842,"avatar_url":"https://avatars0.githubusercontent.com/u/3600842?v=4","gravatar_id":"","url":"https://api.github.com/users/svanschooten","html_url":"https://github.com/svanschooten","followers_url":"https://api.github.com/users/svanschooten/followers","following_url":"https://api.github.com/users/svanschooten/following{/other_user}","gists_url":"https://api.github.com/users/svanschooten/gists{/gist_id}","starred_url":"https://api.github.com/users/svanschooten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/svanschooten/subscriptions","organizations_url":"https://api.github.com/users/svanschooten/orgs","repos_url":"https://api.github.com/users/svanschooten/repos","events_url":"https://api.github.com/users/svanschooten/events{/privacy}","received_events_url":"https://api.github.com/users/svanschooten/received_events","type":"User","site_admin":false}],"milestone":{"url":"https://api.github.com/repos/Tribler/tribler/milestones/19","html_url":"https://github.com/Tribler/tribler/milestone/19","labels_url":"https://api.github.com/repos/Tribler/tribler/milestones/19/labels","id":951197,"number":19,"title":"Backlog","description":"","creator":{"login":"whirm","id":529494,"avatar_url":"https://avatars1.githubusercontent.com/u/529494?v=4","gravatar_id":"","url":"https://api.github.com/users/whirm","html_url":"https://github.com/whirm","followers_url":"https://api.github.com/users/whirm/followers","following_url":"https://api.github.com/users/whirm/following{/other_user}","gists_url":"https://api.github.com/users/whirm/gists{/gist_id}","starred_url":"https://api.github.com/users/whirm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whirm/subscriptions","organizations_url":"https://api.github.com/users/whirm/orgs","repos_url":"https://api.github.com/users/whirm/repos","events_url":"https://api.github.com/users/whirm/events{/privacy}","received_events_url":"https://api.github.com/users/whirm/received_events","type":"User","site_admin":false},"open_issues":184,"closed_issues":122,"state":"open","created_at":"2015-01-26T12:02:36Z","updated_at":"2017-10-01T06:38:04Z","due_on":null,"closed_at":null},"comments":13,"created_at":"2016-04-13T11:36:09Z","updated_at":"2017-10-12T15:47:50Z","closed_at":null,"author_association":"OWNER","body":"Goal: facilitate broader uptake of Multi-Chain\n\nApproach: have a detailed, complete and accurate protocol description of Multi-Chain in IETF RFC format\n\nTribler team at Delft created before: https://datatracker.ietf.org/doc/rfc7574/\nExample RFCs which mention currency, credit or gossip : \n- https://datatracker.ietf.org/doc/draft-ietf-trans-gossip/ \n- [4 reputation RFCs](https://datatracker.ietf.org/doc/search/?name=reputation&sort=&rfcs=on&activedrafts=on)\n- https://datatracker.ietf.org/doc/rfc1898/ \n- https://datatracker.ietf.org/doc/rfc5578/?include_text=1 \n- https://datatracker.ietf.org/doc/draft-ietf-manet-credit-window/\n\nTeam Multi-chain: @pimveldhuisen @pimotte @Captain-Coder \nSide-affect: a nice thesis chapter.\n"},"comment":{"url":"https://api.github.com/repos/Tribler/tribler/issues/comments/336179641","html_url":"https://github.com/Tribler/tribler/issues/2087#issuecomment-336179641","issue_url":"https://api.github.com/repos/Tribler/tribler/issues/2087","id":336179641,"user":{"login":"synctext","id":325224,"avatar_url":"https://avatars0.githubusercontent.com/u/325224?v=4","gravatar_id":"","url":"https://api.github.com/users/synctext","html_url":"https://github.com/synctext","followers_url":"https://api.github.com/users/synctext/followers","following_url":"https://api.github.com/users/synctext/following{/other_user}","gists_url":"https://api.github.com/users/synctext/gists{/gist_id}","starred_url":"https://api.github.com/users/synctext/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/synctext/subscriptions","organizations_url":"https://api.github.com/users/synctext/orgs","repos_url":"https://api.github.com/users/synctext/repos","events_url":"https://api.github.com/users/synctext/events{/privacy}","received_events_url":"https://api.github.com/users/synctext/received_events","type":"User","site_admin":false},"created_at":"2017-10-12T15:47:50Z","updated_at":"2017-10-12T15:47:50Z","author_association":"OWNER","body":"First create several pieces of highly focused text, before integrating them.\r\n\r\n- Introduction section is based on existing clean-slate work. Framing of our IPv8 and Trustchain plus CHECO approach is a new networking architecture. [Like this Content-Centric Networking](https://tools.ietf.org/html/draft-irtf-icnrg-ccnxsemantics-05) using PARC Research Fellow Van Jacobson 2006 ideas.\r\n```\r\n   This document describes the principles of the CCNx architecture.  It\r\n   describes the network protocol based on two message types: Interests\r\n   and Content Objects.  The description is not dependent on a specific\r\n   wire format or particular encodings.  This section introduces the\r\n   main concepts of CCNx, which are further elaborated in the remainder\r\n   of the document.\r\n[...]\r\n   Protocol Overview\r\n   CCNx is a request and response protocol to fetch chunks of data using\r\n   a name.  The integrity of each chunk may be directly asserted through\r\n   a digital signature or message authentication code (MAC), or,\r\n   alternatively, indirectly via hash chains. \r\n```\r\n- direction of storyline: protocol stacks are evolving for the past decades towards the business layers. Protocols such as {name non-blockchain protocols}, R3 Corda, and IOTA. This architecture covers the complete range of long-lived private identity, throw away personas, NAT traversal, onion routing, reputation tracking and decentralised bid/ask orderbooks. In short, creating new datagram delivery protocol up to open alternatives for eBay, Uber, and Airbnb rating and reputation.\r\n- persistent directory service and reputation tracking without platform-lockin. Result, spoofing, MITM protection when communicating. Plus end-point uncertainty using onion routing ability.\r\n- Tamper-proof identity traffic graph. Count bytes exchanged or other metric to build a ledger of identity-to-identity traffic. Use this to calculate reputations and estimate reliability using transitive trust.\r\n- A (single page?) description of active relevant working groups. Including both their maturity (HIP WG is 10 years old) in terms of documentation and code, possible openness to blockchain and our IPv8 code. \r\n\r\n[Copied from Padma IETF draft:](https://tools.ietf.org/html/draft-padma-ideas-problem-statement-03#section-5.1)\r\nSome initiatives do not focus on re-architecting the Internet, but merely a DNS 2.0 service, as seen in this problem statement: ```support identity services in addition to enhancing existing identifier/location mapping and resolution services.``` However, [this workgroup seems in severe trouble and will not be formed](https://datatracker.ietf.org/doc/charter-ietf-ideas/ballot/).\r\n\r\n```\r\n5.1.  LISP WG\r\n\r\n   The LISP WG has been working on multiple mapping systems (ALT, DDT)\r\n   for the LISP control plane and the primary function of this mapping\r\n   system is to map and resolve the IDf to IP addresses (EID/RLOC\r\n   mapping).  LISP WG is also looking at Casssandra and blockchain.\r\n   Though some requirements are common,GRIDS has new specific\r\n   requirements described in [IDEAS-REQ].\r\n\r\n5.2.  HIP WG\r\n\r\n   The HIP WG has based its IDy to IDf resolution service on DNS.\r\n   Operational IDf to Loc for fast mobility with low latency is handled\r\n   by HIP-RVS [RFC8005] and specific HIP Mobility Notification messaging\r\n   [RFC8046].\r\n\r\n5.3.  NVO3 WG\r\n\r\n   The NV03 WG has been working on a mapping of VN names to VN IDs in\r\n   the network virtualization space and their requirements differ from\r\n   the wireless broadband requirements and cross-silo communications\r\n   that have been mentioned in this document.\r\n```\r\n- Understanding and processing the comments of well known experts. For instance, this [strong opposition against  the fundamentals ](https://www.spinics.net/lists/ietf/msg84843.html) which will require documenting the \"throw-away persona\" approach and Tor-like onion routing integration.\r\n```I oppose creation of this working\r\ngroup on the basis that it enables and seemingly encourages\r\nembedding identifiers for humans as addresses. Doing so\r\nwould have significant privacy downsides, would enable\r\nnew methods for censorship and discrimination```\r\n\r\n"}}
{"actor":{"display_login":"synctext"}}