gnunet-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-developers] GNUnet dev mumble: TNG


From: t3sserakt
Subject: [GNUnet-developers] GNUnet dev mumble: TNG
Date: Wed, 24 Apr 2019 08:11:18 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1

To all who like to help advance GNUnet,

there will be a GNUnet dev mumble at 21:00 CEST on the 1st of May.

We will talk about transport next generation (TNG).

Prior to the mumble you might have a look into the transport section of
READMe.1st,  https://datatracker.ietf.org/doc/draft-ietf-quic-transport/
and maybe https://datatracker.ietf.org/doc/draft-ietf-quic-recovery/.
There is already some code in ./src/transport/gnunet-service-tng.c.

Happy hacking!

t3ss

On 20.04.19 18:43, Christian Grothoff wrote:

> On 4/20/19 4:03 PM, t3sserakt wrote:
>>>> I am especially interested in the work regarding TNG. I also would like
>>>> to hear more about TNG before the GNUnet Hacker Meeting. In the past
>>>> there was a more or less regular GNUnet dev mumble meeting. Maybe we
>>>> could have one where we get an introduction into TNG. As preparation for
>>>> such a mumble meeting I would start to look into the actual transport code.
>>> That's a good idea, a good day for me for such a Mumble would be May 1st.
>> On bank holiday I am usually spending time with my family. If it is at
>> the beginning or end of the day I can make it, but not during the day.
> We can certainly do it late, say 9pm?
Perfect!
>>> Best preparation would probably reading up on NAT traversal and
>>> fingerprinting attacks on TLS. The IETF QUIC draft also seems like it
>>> has quite a few interesting ideas in it, I haven't fully digested it
>>> myself, but for someone looking to contribute on topics like traffic
>>> amplification and congestion control, that draft likely has some ideas
>>> we'll want to eventually take into consideration.
>> All documents in here
>>
>> https://datatracker.ietf.org/wg/quic/documents/
>>
>> or specific ones?
> Specific ones:
>
> https://datatracker.ietf.org/doc/draft-ietf-quic-transport/ and maybe
> https://datatracker.ietf.org/doc/draft-ietf-quic-recovery/
>
>

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]