Skip to content

experimental authenticated and encrypted unordered datagrams

Notifications You must be signed in to change notification settings

layer1capital/reprehensible

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Comparison to QUIC

Reprehensible does not use PKI like TLS. Reprehensible does not implement multiplexing. Reprehensible does not assume udp as the underlying transport. Reprehensible does not specify any handshake. Connections are semantically stateless like udp.

Why the name?

The name "reprehensible" was randomly selected.

Gotchas

Reprehensible does not provide forward secrecy.

Reprehensible does not protect against replay attacks.

Reprehensible does not deal with ip fragmentation.

Reprehensible does not protect against amplification attacks.

Reprehensible does not detect spoofed IPs. (IP is not in project scope)

Philosophy

  • Reprehensible is small, simple, and arrow in scope.
  • Aside from the stated goals, reprehnsible does not implement any feature, e.g. multiplexing, that can be implemented in a separate network layer.
  • Example implementations should be provided for ommitted features.

Goals

  • Provide end-to-end, authenticated encryption for unordered datagrams.

About

experimental authenticated and encrypted unordered datagrams

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages