From: bfields@fieldses.org (J. Bruce Fields)
To: Martin Houry <martinhoury@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Question : Session trunking fail-over
Date: Fri, 17 Jun 2016 11:50:44 -0400 [thread overview]
Message-ID: <20160617155044.GC29438@fieldses.org> (raw)
In-Reply-To: <CAEUt8VKFwMMkUCnbjy1m5Zht3yH83HMOo2T12oCVLwfzEP6D1Q@mail.gmail.com>
On Fri, Jun 17, 2016 at 09:08:45AM +0200, Martin Houry wrote:
> Hello, I have a question about Session trunking.
> In the RFC 5661 the "2.10.13.1.2.Connection Loss" specify how to do
> if the LAST connection of the session is lost. There no specification
> when the lost connection is not the last connection of the session. Is
> there a fail-over mecanism for the session trunking connection loss?
I believe the RFC provides all the necessary protocol which a client
would need to implement such a failover mechanism. The Linux client
doesn't currently attempt to do that.
--b.
prev parent reply other threads:[~2016-06-17 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 7:08 Question : Session trunking fail-over Martin Houry
2016-06-17 15:50 ` J. Bruce Fields [this message]
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=20160617155044.GC29438@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=martinhoury@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).