p2psp team mailing list archive
-
p2psp team
-
Mailing list archive
-
Message #00262
Re: NAT Traversal Set of rules implementation
On Fri, Jul 17, 2015 at 6:05 PM Max Mertens <max.mail@xxxxxxxxxx> wrote:
> Hi Vicente,
>
> just a quick status update: This week I implemented generating, sending
> and receiving peer IDs to the NTS classes (diff: [1]).
> The next step will be sending the keepalive packets in a timer and
> keeping a list of currently connecting peers.
>
> This weekend I will pause development, as I have exams tomorrow and on
> Monday.
> From monday on I will continue work, with more time per week as classes
> have finished today.
>
> On 13.07.2015 15:46, Max Mertens wrote:
> > On 13.07.2015 13:22, Vicente Gonzalez wrote:
> >> The minimization of the protocol overhead is essential, so, if we can
> >> live without extra fields in the headers, perfect. However, it is
> >> quite likely that at the end, when the complexity of the protocol
> >> grows, we will use this technique. So, if you see the thing more
> >> clear using message type prefixes, go ahead.
> > Ok, thanks for the explanation. Currently the different message types
> > are overseeable, so I'll stick to the current solution.
> It appears more and more that some message typing (just a 1 byte prefix,
> maybe later 2 bytes) would help in differentiating the packets. IIRC,
> currently the biggest packet size is 1026 bytes, so adding 1-2 bytes
> would not exceed the MTU of ~1500 bytes. Maybe this is something to
> implement towards the end of the project this summer. What do you think?
>
Hi,
apologies by the delayed reply ...
Of course, this is a small overhead. Implement this idea when you need it.
Regards,
Vi.
> Thanks and have a nice weekend,
> Max
>
> [1] https://github.com/P2PSP/p2psp/compare/f7ab7d0...a4f1592
>
>
> --
--
Vicente González Ruiz
Depto de Informática
Escuela Técnica Superior de Ingeniería
Universidad de Almería
Carretera Sacramento S/N
04120, La Cañada de San Urbano
Almería, España
e-mail: vruiz@xxxxxx
http://www.ual.es/~vruiz
tel: +34 950 015711
fax: +34 950 015486
References
-
NAT Traversal Set of rules implementation
From: Max Mertens, 2015-06-06
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-06-12
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-06-14
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-06-15
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-06-21
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-06-22
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-06-24
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-06-25
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-06-25
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-06-28
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-06-29
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-07-01
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-07-02
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-07-03
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-07-03
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-07-08
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-07-09
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-07-11
-
Re: NAT Traversal Set of rules implementation
From: Vicente Gonzalez, 2015-07-13
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-07-13
-
Re: NAT Traversal Set of rules implementation
From: Max Mertens, 2015-07-17