From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apV3T-0000ov-1D for qemu-devel@nongnu.org; Mon, 11 Apr 2016 02:10:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1apV3P-0001Oq-Ol for qemu-devel@nongnu.org; Mon, 11 Apr 2016 02:10:34 -0400 Received: from barbershop.grep.be ([89.106.240.122]:52590) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apV3P-0001OE-FU for qemu-devel@nongnu.org; Mon, 11 Apr 2016 02:10:31 -0400 Date: Mon, 11 Apr 2016 08:10:13 +0200 From: Wouter Verhelst Message-ID: <20160411061013.GE28660@grep.be> References: <1460292452-1348-1-git-send-email-alex@alex.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1460292452-1348-1-git-send-email-alex@alex.org.uk> Subject: Re: [Qemu-devel] [Nbd] [PATCHv8] Improve documentation for TLS List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Bligh Cc: Eric Blake , "nbd-general@lists.sourceforge.net" , "Daniel P. Berrange" , "qemu-devel@nongnu.org" Mostly there. Final note: On Sun, Apr 10, 2016 at 01:47:32PM +0100, Alex Bligh wrote: > diff --git a/doc/proto.md b/doc/proto.md > index f117394..5005552 100644 > --- a/doc/proto.md > +++ b/doc/proto.md > @@ -195,6 +195,13 @@ request before sending the next one of the same type. The server MAY > send replies in the order that the requests were received, but is not > required to. > > +There is no requirement for the client or server to complete a negotiation > +if it does not wish to do so. If the client does not find an export it > +is looking for (for instance) it may simply close the TCP connection. > +Under certain circumstances either the client or the server may be required > +by this document to close the TCP connection. In each case, this is > +referred to as 'terminate the session'. > + > ### Transmission NAK. If we have disconnect messages (NBD_OPT_ABORT and NBD_CMD_DISC), it makes sense to say that clients should use them. Protocol violations by peers are a different matter; but in the general case you should drop a connection properly, i.e., by using the relevant "close the connection" command. (I realize I didn't comment on this earlier, but I changed my mind during the discussion about DISC). -- < ron> I mean, the main *practical* problem with C++, is there's like a dozen people in the world who think they really understand all of its rules, and pretty much all of them are just lying to themselves too. -- #debian-devel, OFTC, 2016-02-12