Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct Data Placement (DDP)
draft-ietf-rddp-applicability-08

[Ballot comment]
draft-ietf-rddp-applicability-07:

  Section 6.6 says:
  >
  > A ULP that requires a greater degree of protection may add it own.
  >
  s/own/own integrity check/

  Section 9.3 contains sentence fragments.  I would prefer a slight
  reorganization, so that TLS, DTLS, and IPsec are each discussed in
  their own paragraphs.

[Ballot discuss]
draft-ietf-rddp-security-09:

  The discussion in section 5.4.2 should consider DTLS (RFC 4347).
  It might be best handled as a separate section.

  draft-ietf-rddp-applicability-07:

  The discussion in section 9.3 should consider DTLS (RFC 4347).

[Ballot comment]
draft-ietf-rddp-applicability-07:

  Section 6.6 says:
  >
  > A ULP that requires a greater degree of protection may add it own.
  >
  s/own/own integrity check/

PROTO writeup:

Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct
                          Data Placement (DDP)
                  draft-ietf-rddp-applicability-04.txt

Requested Publication Status: Informational
PROTO shepherd: David L. Black (RDDP WG Chair)
------------------------------------------------------------------------

  1.a) Have the chairs personally reviewed this version of the Internet
        Draft (ID), and in particular, do they believe this ID is ready
        to forward to the IESG for publication?

Yes.  There are a few editing issues that the RFC Editor can address.

  1.b) Has the document had adequate review from both key WG members
        and key non-WG members?

Yes, primarily from WG members.

        Do you have any concerns about the
        depth or breadth of the reviews that have been performed?

The draft has had limited review outside the WG.

  1.c) Do you have concerns that the document needs more review from a
        particular (broader) perspective (e.g., security, operational
        complexity, someone familiar with AAA, etc.)?

No.

  1.d) Do you have any specific concerns/issues with this document that
        you believe the ADs and/or IESG should be aware of?  For
        example, perhaps you are uncomfortable with certain parts of the
        document, or have concerns whether there really is a need for
        it.  In any event, if your issues have been discussed in the WG
        and the WG has indicated it that it still wishes to advance the
        document, detail those concerns in the write-up.

No.

  1.e) How solid is the WG consensus behind this document? Does it
        represent the strong concurrence of a few individuals, with
        others being silent, or does the WG as a whole understand and
        agree with it?

Most of the WG is interested in rddp over TCP.  There is limited interest
in SCTP, or in a draft like this that includes guidance on choosing
between TCP and SCTP.  The portion of the WG that is interested in SCTP
understands and agrees with this document.

  1.f) Has anyone threatened an appeal or otherwise indicated extreme
        discontent?  If so, please summarise the areas of conflict in
        separate email to the Responsible Area Director.

No.

  1.g) Have the chairs verified that the document adheres to all of the
        ID nits? (see http://www.ietf.org/ID-Checklist.html).

Yes.

  1.h) Is the document split into normative and informative references?

Yes.  All references are normative.

        Are there normative references to IDs, where the IDs are not
        also ready for advancement or are otherwise in an unclear state?
        (note here that the RFC editor will not publish an RFC with
        normative references to IDs, it will delay publication until all
        such IDs are also ready for publication as RFCs.)

There are four normative references to Internet-Drafts:

o draft-ietf-rddp-rdmap, draft-ietf-rddp-ddp - publication has already
been requested.
o draft-ietf-rddp-mpa, draft-ietf-rddp-sctp - publication has already
been requested.

  1.i) For Standards Track and BCP documents, the IESG approval
        announcement includes a write-up section

N/A - this is an Informational document.