Create statuscodes.md

Initial draft of the doc describing the acses where different statuses are returned.

doc/statuscodes.md

+# Status codes and their use in gRPC
+
+gRPC uses a set of well defined status codes as part of the RPC API. All RPCs started at a client return  a `status` object composed of an integer `code` and a string `message`. The server-side can choose the status it returns for a given RPC.
+
+The gRPC client and server-side implementations may also generate and return `status` on their own when errors happen.  
+Only a subset of the pre-defined status codes are generated by the gRPC libraries. The following table lists these codes and summarizes the situations in which they are generated, either by the client or the server-side library implementation.
+
+| Case        | Code           | Generated at Client or server  |
+| ------------- |:-------------| :-----:|
+| Client Application cancelled the request	| GRPC_STATUS_CANCELLED | Both |
+| Deadline expires before server returns status	| GRPC_STATUS_DEADLINE_EXCEEDED | Both |
+| Method not found at server	| GRPC_STATUS_UNIMPLEMENTED | Server|
+| Server shutting down	| GRPC_STATUS_UNAVAILABLE | Server|
+| Server side application throws an exception (or does something other than returning a Status code to terminate an RPC) |	GRPC_STATUS_UNKNOWN | Server|
+| No response received before Deadline expires. This may occur either when the client is unable to send the request to the server or when the server fails to respond in time. |	GRPC_STATUS_DEADLINE_EXCEEDED | Both|
+| Some data transmitted (e.g., request metadata written to TCP connection) before connection breaks |	GRPC_STATUS_UNAVAILABLE | Client |
+| Could not decompress, but compression algorithm supported (Client -> Server)	| GRPC_STATUS_INTERNAL | Server |
+| Could not decompress, but compression algorithm supported (Server -> Client)	| GRPC_STATUS_INTERNAL | Client |
+| Compression mechanism used by client not supported at server	| GRPC_STATUS_UNIMPLEMENTED | Server |
+| Server temporarily out of resources (e.g., Flow-control resource limits reached) |	GRPC_STATUS_RESOURCE_EXHAUSTED | Server|
+| Flow-control protocol violation |	GRPC_STATUS_INTERNAL | Both |
+| Error parsing returned status	| GRPC_STATUS_UNKNOWN | Client |
+| Incorrect Auth metadata ( Credentials failed to get metadata, Incompatible credentials set on channel and call, Invalid host set in `:authority` metadata, etc.) | GRPC_STATUS_UNAUTHENTICATED | Both |
+| Error parsing response proto	| GRPC_STATUS_INTERNAL | Client|
+| Error parsing request proto	| GRPC_STATUS_INTERNAL | Server|
+
+
+The following status codes are never generated by the library:
+- GRPC_STATUS_INVALID_ARGUMENT
+- GRPC_STATUS_NOT_FOUND
+- GRPC_STATUS_ALREADY_EXISTS
+- GRPC_STATUS_FAILED_PRECONDITION
+- GRPC_STATUS_ABORTED
+- GRPC_STATUS_OUT_OF_RANGE
+- GRPC_STATUS_DATA_LOSS