RFC 5041: Direct Data Placement over Reliable Transports
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 5041: Direct Data Placement over Reliable Transports
Summary
RFC 5041: Direct Data Placement over Reliable Transports is a Request for Comments[1].
Key Facts
- RFC 5041: Direct Data Placement over Reliable Transports's instance of is recorded as Direct Data Placement over Reliable Transports — instance of (P31): Request for Comments[2].
- RFC 5041: Direct Data Placement over Reliable Transports's publisher is recorded as Direct Data Placement over Reliable Transports — publisher (P123): Internet Engineering Task Force[3].
- RFC 5041: Direct Data Placement over Reliable Transports's DOI is recorded as 10.17487/RFC5041[4].
- RFC 5041: Direct Data Placement over Reliable Transports's language of work or name is recorded as Direct Data Placement over Reliable Transports — language of work or name (P407): English[5].
- RFC 5041: Direct Data Placement over Reliable Transports's publication date is recorded as +2007-10-01T00:00:00Z[6].
- RFC 5041: Direct Data Placement over Reliable Transports's RfC ID is recorded as 5041[7].
- RFC 5041: Direct Data Placement over Reliable Transports's work available at URL is recorded as https://tools.ietf.org/html/rfc5041[8].
- RFC 5041: Direct Data Placement over Reliable Transports's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5041.txt[9].
- RFC 5041: Direct Data Placement over Reliable Transports's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5041.txt[10].
- RFC 5041: Direct Data Placement over Reliable Transports's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5041.txt.pdf[11].
- RFC 5041: Direct Data Placement over Reliable Transports's number of pages is recorded as {'unit': '1', 'amount': '+38'}[12].
- RFC 5041: Direct Data Placement over Reliable Transports's title is recorded as Direct Data Placement over Reliable Transports[13].
- RFC 5041: Direct Data Placement over Reliable Transports's author name string is recorded as H. Shah[14].
- RFC 5041: Direct Data Placement over Reliable Transports's author name string is recorded as J. Pinkerton[15].
- RFC 5041: Direct Data Placement over Reliable Transports's author name string is recorded as R. Recio[16].
- RFC 5041: Direct Data Placement over Reliable Transports's author name string is recorded as P. Culley[17].
- RFC 5041: Direct Data Placement over Reliable Transports's amended by is recorded as Direct Data Placement over Reliable Transports — amended by (P2567): RFC 7146: Securing Block Storage Protocols over IP: RFC 3723 Requirements Update for IPsec v3[18].
- RFC 5041: Direct Data Placement over Reliable Transports's DBLP publication ID is recorded as journals/rfc/rfc5041[19].
Body
Designation and Status
RFC 5041: Direct Data Placement over Reliable Transports's instance of is recorded as Direct Data Placement over Reliable Transports — instance of (P31): Request for Comments[2].