top | item 46453354 (no title) dontlaugh | 1 month ago For example, Cap'n Proto and QUIC are both little endian.TCP is becoming increasingly less relevant, although I don't know if it'll ever actually disappear. discuss order hn newest nineteen999|1 month ago Capn Proto and QUIC are are layer 6 and 7 (presentation and application protocols respectively). Quic is built on top of UDP.Layers 3-4 (network, transport) are both big-endian - IP packet headers and TCP/UDP headers use big-endian format.This means you can't have an IP stack (let alone TCP/UDP, Quic, Capn Proto) that's little-endian all the way through without breaking the internet.Outside the webdev bubble, it's pretty much QUIC that is irrelevant - it's just another UDP based application protocol. dontlaugh|1 month ago UDP is an implementation detail of QUIC, just a way to give IP-ish functionality to userspace. In practice, QUIC is a TCP alternative.The OSI layer model is not necessarily as relevant as it used to be. load replies (1) Veserv|1 month ago Foolishly, QUIC is not little-endian [1]. The headers are defined to be big-endian. Though, obviously, none of UDP, TCP, or QUIC define the endianness of their payload so you can at least kill it at that layer.[1] https://www.rfc-editor.org/rfc/rfc9000.html#name-notational-... dontlaugh|1 month ago Oh really? I must’ve misread.
nineteen999|1 month ago Capn Proto and QUIC are are layer 6 and 7 (presentation and application protocols respectively). Quic is built on top of UDP.Layers 3-4 (network, transport) are both big-endian - IP packet headers and TCP/UDP headers use big-endian format.This means you can't have an IP stack (let alone TCP/UDP, Quic, Capn Proto) that's little-endian all the way through without breaking the internet.Outside the webdev bubble, it's pretty much QUIC that is irrelevant - it's just another UDP based application protocol. dontlaugh|1 month ago UDP is an implementation detail of QUIC, just a way to give IP-ish functionality to userspace. In practice, QUIC is a TCP alternative.The OSI layer model is not necessarily as relevant as it used to be. load replies (1)
dontlaugh|1 month ago UDP is an implementation detail of QUIC, just a way to give IP-ish functionality to userspace. In practice, QUIC is a TCP alternative.The OSI layer model is not necessarily as relevant as it used to be. load replies (1)
Veserv|1 month ago Foolishly, QUIC is not little-endian [1]. The headers are defined to be big-endian. Though, obviously, none of UDP, TCP, or QUIC define the endianness of their payload so you can at least kill it at that layer.[1] https://www.rfc-editor.org/rfc/rfc9000.html#name-notational-... dontlaugh|1 month ago Oh really? I must’ve misread.
nineteen999|1 month ago
Layers 3-4 (network, transport) are both big-endian - IP packet headers and TCP/UDP headers use big-endian format.
This means you can't have an IP stack (let alone TCP/UDP, Quic, Capn Proto) that's little-endian all the way through without breaking the internet.
Outside the webdev bubble, it's pretty much QUIC that is irrelevant - it's just another UDP based application protocol.
dontlaugh|1 month ago
The OSI layer model is not necessarily as relevant as it used to be.
Veserv|1 month ago
[1] https://www.rfc-editor.org/rfc/rfc9000.html#name-notational-...
dontlaugh|1 month ago