RE: I-D ACTION:draft-ietf-rddp-security-03.txt

This draft is intended to resolve all of the outstanding issues that
were identified either on the reflector or at the IETF work group
meeting last week, except:

	- The TBDs I left in the reply to Tom Talpey's feedback (4 of
'em)
	- Cleanup of the appendix focused on client/server
implementations 
		and how the normative statements in the documents 
		are interpreted in a client/server environment.

Specifically the text changed the document to be standards track, and
changes what used to be RECOMMENDations (i.e. SHOULDs) into MUST,
SHOULD, MAY, recommended (i.e. lower case recommends that are not
implementation requirements), etc.

As we discussed in the work group meeting, I'll send out a note in about
a week to try to work out a conference call time that anyone interested
can attend to specifically review the MUST/SHOULD/MAY statements, in the
hopes that we can more quickly converge on consensus this way. Note that
as David Black mentioned at the workgroup meeting, not being able to
attend the meeting in no way restricts your ability to give feedback
either directly to the authors or to this reflector.

To aid in review, I've got the original MS word document with changebars
turned on. Unfortunately I am not able to output a pdf document and
preserve the changebars though. If you would like the changebar version,
please send me mail directly.


Jim Pinkerton






> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
Of
> [email protected]
> Sent: Monday, August 09, 2004 12:27 PM
> To: [email protected]
> Cc: [email protected]
> Subject: [rddp] I-D ACTION:draft-ietf-rddp-security-03.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		: DDP/RDMAP Security
> 	Author(s)	: J. Pinkerton, et al.
> 	Filename	: draft-ietf-rddp-security-03.txt,.pdf
> 	Pages		: 52
> 	Date		: 2004-8-9
> 
> This document analyzes security issues around implementation and
>    use of the Direct Data Placement Protocol(DDP) and Remote Direct
>    Memory Access Protocol (RDMAP). It first defines an architectural
>    model for an RDMA Network Interface Card (RNIC), which can
>    implement DDP or RDMAP and DDP. The document reviews various
>    attacks against the resources defined in the architectural model
>    and the countermeasures that can be used to protect the system.
>    Attacks are grouped into spoofing, tampering, information
>    disclosure, denial of service, and elevation of privilege.
>    Finally, the document concludes with a summary of security
>    services for RDDP, such as IPSec.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-03.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> [email protected] 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
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-rddp-security-03.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	[email protected].
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-rddp-security-03.txt".
> 
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.