public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed
From: John Goerzen <jgoerzen@complete•org>
To: Sergey Matveev <stargrave@stargrave•org>
Cc: nncp-devel@lists.cypherpunks.ru
Subject: Re: [EN] NNCP 8.6.0 release announcement
Date: Wed, 02 Mar 2022 10:22:55 -0600	[thread overview]
Message-ID: <87h78g9vds.fsf@complete.org> (raw)
In-Reply-To: <87k0dc9vlg.fsf@complete.org>


On Wed, Mar 02 2022, John Goerzen wrote:

> I think option #1 is preferable.  If an ACK is lost, there's no harm
> (particularly if -seen is in use, which it should be in this cast [might
> want to mention that hint on the nncp-ack documentation page]).  The
> sender will simply retransmit, the recipient will re-ACK and then toss
> will ignore it as it's been seen.

Hmm, now I see that nncp-xfer -rx will ignore packets that have been
seen.  That would mean that if an ACK is lost, the sender will keep
retransmitting the packet forever, right?  I'm not quite sure what to do
about this yet, hmm.

  reply	other threads:[~2022-03-02 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 14:57 [EN] NNCP 8.6.0 release announcement Sergey Matveev
2022-03-02 16:18 ` John Goerzen
2022-03-02 16:22   ` John Goerzen [this message]
2022-03-02 18:55     ` Sergey Matveev
2022-03-02 18:47   ` Sergey Matveev
2022-03-02 18:59     ` John Goerzen
2022-03-02 19:26       ` Sergey Matveev
2022-03-03  3:10         ` John Goerzen