search

tlswg / dtls13-spec

Repo for DTLS 1.3
32 stars 25 forks source link

Should the protocol specify a mechanism to ensure that the link is disconnected if the peer is restarted or some reason? #248

Closed yangyangtiantianlonglong closed 3 years ago

yangyangtiantianlonglong commented 3 years ago

Since there are various versions of dtls implementations, should the protocol specify a common mechanism for disconnects? When the status of the peer end is unknown.

ekr commented 3 years ago

Generally, I think that's out of scope at this time. We could graft something like QUIC's stateless reset on later if needed, but DTLS has gotten along pretty well without it so far

On Tue, Jun 8, 2021 at 1:31 AM TiaLo @.***> wrote:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tlswg/dtls13-spec/issues/248, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIPLIM6FXUX7P3QBXXAUDDTRXIMHANCNFSM46JME4XQ .

yangyangtiantianlonglong commented 3 years ago

DTLS has gotten along pretty well without it so far When disconnecting a dtls link with a third-party device, there is no common disconnection mechanism and we are always speculating on the behavior of the third-party device. Most dtls users disconnect the link by timeout, and setting different times will cause confusion. And timeout disconnection makes app user experience poor. It would make things easier to suggest a common mechanism to solve the problem.

ekr commented 3 years ago

I'm not saying this wouldn't be helpful. I'm saying that at this point in the process it would be disruptive to hold the document to add it. Moreover, we would probably add something like QUIC's stateless reset, which would end up being an extension anyway. So I think the right thing to do is to write an extension document.

On Tue, Jun 8, 2021 at 6:39 PM TiaLo @.***> wrote:

DTLS has gotten along pretty well without it so far When disconnecting a dtls link with a third-party device, there is no common disconnection mechanism and we are always speculating on the behavior of the third-party device. Most dtls users disconnect the link by timeout, and setting different times will cause confusion. And timeout disconnection makes app user experience poor. It would make things easier to suggest a common mechanism to solve the problem.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/tlswg/dtls13-spec/issues/248#issuecomment-857305080, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIPLILQLQFIQVFQ35E3FELTR3A4XANCNFSM46JME4XQ .

yangyangtiantianlonglong commented 3 years ago

I see. Thank you for your reply.

seanturner commented 3 years ago

@ekr should this be closed?

ekr commented 3 years ago

yes imo

On Thu, Jul 15, 2021 at 11:39 AM Sean Turner @.***> wrote:

@ekr https://github.com/ekr should this be closed?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tlswg/dtls13-spec/issues/248#issuecomment-880926436, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIPLIJ7UZIPPW5YZ6AJCWDTX4TMJANCNFSM46JME4XQ .