Enhanced Remote Direct Memory Access (RDMA) Connection Establishment
RFC 6581

Note: This ballot was opened for revision 09 and is now closed.

(David Harrington) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

Comment (2011-10-05 for -)
No email
send info
Readable document, thank you.

RDMA is not a "well known" acronym at
http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

You should expand it in the Abstract and Introduction.

(You might also want to lobby the RFC Editor to get it made "well known"

MPA will also need expansion in the Abstract.

---

FULPDU:  Framed Upper Layer Protocol PDU

How many letter Ps?

(Stephen Farrell) No Objection

Comment (2011-10-04 for -)
No email
send info
- The abstract uses the asconyms MPA and RDMA without expansion,
it'd be better not to do that and generally many acronyms are
used before being expanded - a pass to fix that would be useful

- The security considerations section says that this changes
nothing compared to RFC 5044, however, I guess that a peer 
could try a DoS against another peer by setting large xRD
values, but I don't know if that's significant enough to
warrant a mention or not. Is it? If it were, then I guess
just a warning that implementations ought to have some kind of
sanity checking on those inputs would suffice.

- Just out of curiosity - RFCs 5043 and 5044 seem to say: "if
you want security, do IPsec" - is that how things are actually
deployed?

(Russ Housley) (was Discuss) No Objection

(Pete Resnick) No Objection

(Dan Romascanu) No Objection

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection