http2 explained – This document describes http2 at a technical and protocol level. Background, the protocol, the implementations and the future.
- The http2 spec is expected to ship in June 2014 (a month or two away!)
- http2 is heavily based on Google’s SPDY
- http2 is binary
- http2 fixes a lot of issues with HTTP 1.1 (pipelining, head of line blocking, etc)
- http2 brings new features (server push, block, reset)
- http2 will keep the URL schemes (http and https)
- http2 will mostly be implemented for https (via protocol negotiations in TLS)
- http2 already has a variety of implementations: Firefox and Google Chrome (MSIE coming), cURL, Goolge, Twitter, Facebook. Apache and Nginx expected.
I’ve always relied on my mail servers having a complete and correct /etc/aliases file with all the necessary aliases. I never even thought about who puts them there and why. It was just one of those many things that just work. Today I discovered that there is actually an RFC 2142, which describes standard mailbox names for common services, roles, and functions. Here is the abstract:
This specification enumerates and describes Internet mail addresses (mailbox name @ host reference) to be used when contacting personnel at an organization. Mailbox names are provided for both operations and business functions. Additional mailbox names and aliases are not prohibited, but organizations which support email exchanges with the Internet are encouraged to support AT LEAST each mailbox name for which the associated function exists within the organization.