Adding close_notify to the spec ?

On Sat, 7 Nov 2020 19:20:21 -0600
Scot <gmi1 at scotdoyle.com> wrote:

> Does anyone have any concerns about amending the spec to state that a TLS
> close_notify message should be sent before closing the TCP connection?
> While TLS guarantees the integrity of the data from the server, it does
> not guarantee completeness until a close_notify is received by the client.
> Interested and able clients could then determine that they received a
> complete response.

A close_notify alert "MUST" be sent prior to closing the write side
of the connection in both TLS 1.2 and 1.3. I should think it's
redundant to mention this in the Gemini spec since it's already
required by the TLS specs, but the number of servers that don't
implement TLS properly is alarmingly high, so maybe a reminder is
necessary.

-- 
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201108/01dd
d6da/attachment-0001.sig>

---

Previous in thread (1 of 6): 🗣️ Scot (gmi1 (a) scotdoyle.com)

Next in thread (3 of 6): 🗣️ Michael Lazar (lazar.michael22 (a) gmail.com)

View entire thread.