From: Arkady Kanevsky <arkady-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
To: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: FW: New Version Notification for draft-ietf-storm-mpa-peer-connect-03
Date: Mon, 14 Mar 2011 08:08:13 -0700 [thread overview]
Message-ID: <C9A3A74B.10141%arkady@vmware.com> (raw)
In-Reply-To: <20110314125155.52C883A6D24-L/zGUk07lBdxiNq7VP1ztA@public.gmane.org>
Please, provide your feedback on IETF iWARP connection management
extensions.
Thanks,
Arkady
Arkady Kanevsky PhD. Sr. Academic Program Manager
5 Cambridge Center arkady-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org
Cambridge, MA 02142 617-528-7721
On 3/14/11 8:51 AM, "IETF I-D Submission Tool" <idsubmission-EgrivxUAwEY@public.gmane.org>
wrote:
>
>A new version of I-D, draft-ietf-storm-mpa-peer-connect-03.txt has been
>successfully submitted by Arkady Kanevsky and posted to the IETF
>repository.
>
>Filename: draft-ietf-storm-mpa-peer-connect
>Revision: 03
>Title: Enhanced RDMA Connection Establishment
>Creation_date: 2011-03-14
>WG ID: storm
>Number_of_pages: 18
>
>Abstract:
>This document updates [RFC5043] and [RFC5044] by extending MPA
>negotiation for RDMA Connection establishment. The first extension
>extends [RFC5043], enabling peer-to-peer connection establishment
>over MPA/TCP. The second extension extends both [RFC5043] and
>[RFC5044], by providing an option for standardized exchange of RDMA-
>layer connection configuration.
>
>
>
>
>The IETF Secretariat.
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2011-03-14 15:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20110314125155.52C883A6D24-L/zGUk07lBdxiNq7VP1ztA@public.gmane.org>]
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=C9A3A74B.10141%arkady@vmware.com \
--to=arkady-pghwnbhtmq7qt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox