HTTP Ideas
- Transport
- Path to application / application path metadata
- FEC
- UDP
- Taking advantage of multipath
- Out of order delivery
- Unreliable (as a feature)
- Taking advantage of multicast
- Peer-to-peer / distributed HTTP / content-centric networking / NDN
- Mobility
- Up-front routing information
- Web browsing focus? Other use cases? E.g., IoT?
- Browser Profile for HTTP
- Other profiles? E.g., IoT, app
- Multiple metadata buckets / labels
- Data-aware header encoding
- Firm limits on protocol elements (sizes, etc.)
- Energy efficiency
- Clear layering / modularity - esp. relation to transport
- Semantic backwards compatibility - how much can we break?
- Security / encryption requirements
- Resistance to traffic analysis
- Built-in onion routing (lite?)
- Notification / store-and-forward / pub/sub
- Selective encryption
- DoS resistance
- Explore large latency optimisation
- Recommended standards / usage for H2 over TCP
- IW
- TFO (including impact on specs/apps/apis)
- Congestion control algorithms
- Pacing
- Connection timeout improvements
- Congestion control tweaks for fairness relative to h1
- Dynamic TLS record sizes
- Explore / advise on use of multiple connections
- Connection coalescing
- Path to application / application to path?
- ORIGIN Frame
- Client certs
- Priority improvements / modifications
- websockets
- PUSH for pub/sub and store-forward
- Pushing DNS / certs
- BLOCKED frame
- PUSH hints?
- Blind Caching
- Conditional-on-hash
- replacement for content-md5 (use cases?)
- encryption encoding
- Multipart-range response media type replacement
- zero knowledge proof
- key
- prioritisation hints - visibility, controls
- partial upload
- "delayed" requests - how long has been stored/in transit - including error responce semantics
- High precision timestamps (in caching)
- first party cookies
- origin cookies
- JSON header convention
- Health check convention / practices
- New DNS records - available protocols, etc.)
