Update File transfer

tutorials/File-transfer.md

@@ -38,11 +38,17 @@ you will see 'awaiting peer':
 
 ![Android_awaiting_peer](/uploads/56f0316c945ca243448668ae9091b1de/Android_awaiting_peer.png)
 
-How it works (technical)?
+How it works? (technical)
 -------------------------
 
 ### How it works
 
+**TODO: doc new design for p2p file transfer**
+1. Short description
+2. Explain class by class the role + schema
+3. Explain the whole process for sending and receiving
+4. PJSIP part
+
 #### Sending files
 
 The following method is used:
@@ -162,10 +168,6 @@ For now, if a file transfer fails when ongoing, the sender can't resume
 the transfer and must relaunch the whole transfer. In the future, there
 will be a retry button for resuming the transfer.
 
-Moreover, the current implementation must pass through a TURN server.
-Ring should supports in a distant future a true peer-to-peer
-implementation with TURN fallback. Ideas and PR welcome.
-
 Finally, because Ring do not support text conferences (just video
 conferences, where there is one master merging slaves SIP calls), there
 is no real file transfer in conferences. For now, when you are in a
@@ -177,5 +179,4 @@ send a file to B or to C (just have to select the correct conversation).
 
 1. Add unit-tests (https://gerrit-ring.savoirfairelinux.com/\#/c/9365/)
 2. Show subtransfers status for outgoing files
-3. Still some unjoinable peer error to fix
-4. Offset resume (for failed transfer)
+3. Offset resume (for failed transfer)