headers
Internet-Drafts | 5 Oct 2006 00:50
Picon
Favicon

I-D ACTION:draft-ietf-rddp-mpa-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Remote Direct Data Placement Working Group of the IETF.

	Title		: Marker PDU Aligned Framing for TCP Specification
	Author(s)	: P. Culley, et al.
	Filename	: draft-ietf-rddp-mpa-07.txt,.pdf
	Pages		: 75
	Date		: 2006-10-4
	
MPA (Marker Protocol data unit Aligned framing) is designed to work
   as an "adaptation layer" between TCP and the Direct Data Placement
   [DDP] protocol, preserving the reliable, in-order delivery of TCP,
   while adding the preservation of higher-level protocol record
   boundaries that DDP requires.  MPA is fully compliant with applicable
   TCP RFCs and can be utilized with existing TCP implementations.  MPA
   also supports integrated implementations that combine TCP, MPA and
   DDP to reduce buffering requirements in the implementation and
   improve performance at the system level.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rddp-mpa-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 9 Oct 2006 21:50
Picon
Favicon

I-D ACTION:draft-ietf-rddp-mpa-08.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Remote Direct Data Placement Working Group of the IETF.

	Title		: Marker PDU Aligned Framing for TCP Specification
	Author(s)	: P. Culley, et al.
	Filename	: draft-ietf-rddp-mpa-08.txt,.pdf
	Pages		: 75
	Date		: 2006-10-9
	
MPA (Marker Protocol data unit Aligned framing) is designed to work
   as an "adaptation layer" between TCP and the Direct Data Placement
   [DDP] protocol, preserving the reliable, in-order delivery of TCP,
   while adding the preservation of higher-level protocol record
   boundaries that DDP requires.  MPA is fully compliant with applicable
   TCP RFCs and can be utilized with existing TCP implementations.  MPA
   also supports integrated implementations that combine TCP, MPA and
   DDP to reduce buffering requirements in the implementation and
   improve performance at the system level.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rddp-mpa-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
(Continue reading)

Permalink | Reply | 8 comments |
headers
Black_David | 16 Oct 2006 16:31

Good news from the IESG

The IESG has approved three of the four remaining RDDP drafts
for RFC publication:
- The RDMAP and DDP drafts have been approved, announcements
	should appear in the near future.  Congratulations and
	thanks to all the authors and contributors!!
- The RDDP SCTP draft has been approved on a technical basis,
	after an RFC Editor note was added to say that use of
	IPsec with RDDP over SCTP requires IPsec support for SCTP
	(yes, it's obvious, but it does have to be stated ...).
	However, the SCTP draft is in a weird situation in that
	it allocates a codepoint from an IANA registry that does
	not exist yet, as the SCTP ADDIP draft that will create
	the registry has not yet made it to the IESG.  Hence,
	IANA has asked the IESG to hold the RDDP SCTP draft until
	IESG approval of the SCTP ADDIP draft.
- The MPA draft was deferred for two weeks.  This usually means
	that an AD simply ran out of time to review it.  There
	will be an RFC Editor Note coming to clarify and better
	explain when it's ok not to use the MPA CRC, including
	providing end-to-end IPsec as an example (should appear
	in the tracker this week, assuming my time permits).

We're getting close to done.  Many thanks to all who have
contributed,

--David (rddp WG chair)
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
(Continue reading)

Permalink | Reply | 0 comments |
headers
Black_David | 27 Oct 2006 00:53

MPA has been approved

Everyone,

It gives me great pleasure to announce that the IESG approved
the MPA draft for RFC publication earlier today - the actual
announcement of this approval will appear in the near future.

This completes the planned work of the RDDP Working Group - all
of our drafts are now approved and are (or shortly will be) in
the RFC Editor's Queue.  I want to thank all the authors, and
in particular recognize Paul Culley for his work on MPA - major
structural changes to the MPA draft were unexpectedly needed
after it left the WG, and Paul was diligent in getting them
done.

Authors should not tune out of RDDP entirely - authors will be
hearing from the RFC Editor and yours truly when the editing
is done, as approval by every author is required before an
RFC is published.  This may be a while in the future, as we have
a couple of normative references to drafts from other WGs that
will probably determine when the entire set of RFCs can be
published:
- The RDDP SCTP draft references draft-ietf-tsvwg-addip-sctp
- The RDDP RDMAP draft references draft-ietf-ips-iser

Congratulations and many thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
(Continue reading)

Permalink | Reply | 1 comment |
headers
Lars Eggert | 27 Oct 2006 09:24
Picon

Re: MPA has been approved

My congratulations to the RDDP WG as well! Start planning your  
victory party for San Diego.

We'll leave the WG in formal existence until the RFCs are appearing,  
in case any late changes require WG discussion (I don't expect it in  
this case). With the current level of RFC Editor activity, I expect  
publication to happen well before the Spring IETF.

Lars

On Oct 27, 2006, at 0:53, Black_David <at> emc.com wrote:
> This completes the planned work of the RDDP Working Group - all
> of our drafts are now approved and are (or shortly will be) in
> the RFC Editor's Queue.  I want to thank all the authors, and
> in particular recognize Paul Culley for his work on MPA - major
> structural changes to the MPA draft were unexpectedly needed
> after it left the WG, and Paul was diligent in getting them
> done.
>
> Authors should not tune out of RDDP entirely - authors will be
> hearing from the RFC Editor and yours truly when the editing
> is done, as approval by every author is required before an
> RFC is published.  This may be a while in the future, as we have
> a couple of normative references to drafts from other WGs that
> will probably determine when the entire set of RFCs can be
> published:
> - The RDDP SCTP draft references draft-ietf-tsvwg-addip-sctp
> - The RDDP RDMAP draft references draft-ietf-ips-iser

--

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane