All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wouter Verhelst <w@uter.be>
To: Alex Bligh <alex@alex.org.uk>
Cc: Eric Blake <eblake@redhat.com>,
	"nbd-general@lists.sourceforge.net"
	<nbd-general@lists.sourceforge.net>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Nbd] [PATCHv8] Improve documentation for TLS
Date: Mon, 11 Apr 2016 08:10:13 +0200	[thread overview]
Message-ID: <20160411061013.GE28660@grep.be> (raw)
In-Reply-To: <1460292452-1348-1-git-send-email-alex@alex.org.uk>

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

  reply	other threads:[~2016-04-11  6:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10 12:47 [Qemu-devel] [PATCHv8] Improve documentation for TLS Alex Bligh
2016-04-11  6:10 ` Wouter Verhelst [this message]
2016-04-11  7:27   ` [Qemu-devel] [Nbd] " Alex Bligh
2016-04-11 20:14     ` Eric Blake
2016-04-11 20:34       ` Alex Bligh
2016-04-12  6:01         ` Wouter Verhelst
2016-04-12  7:47           ` Alex Bligh
2016-04-12  9:20             ` Wouter Verhelst
2016-04-12  9:53               ` Alex Bligh
2016-04-12 12:40                 ` Wouter Verhelst
2016-04-12 12:57                   ` Alex Bligh
2016-04-12 13:01                     ` Wouter Verhelst
2016-04-12 13:29                       ` Alex Bligh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160411061013.GE28660@grep.be \
    --to=w@uter.be \
    --cc=alex@alex.org.uk \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=nbd-general@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.