RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)
0 sources
RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)
Summary
RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP) is a Request for Comments[1].
Key Facts
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP) authored Problem Statement for the Datagram Congestion Control Protocol (DCCP) — author (P50): Mark Handley[2].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP) authored Problem Statement for the Datagram Congestion Control Protocol (DCCP) — author (P50): Sally Floyd[3].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP) authored Problem Statement for the Datagram Congestion Control Protocol (DCCP) — author (P50): Eddie Kohler[4].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s instance of is recorded as Problem Statement for the Datagram Congestion Control Protocol (DCCP) — instance of (P31): Request for Comments[5].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s publisher is recorded as Problem Statement for the Datagram Congestion Control Protocol (DCCP) — publisher (P123): Internet Engineering Task Force[6].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s DOI is recorded as 10.17487/RFC4336[7].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s language of work or name is recorded as Problem Statement for the Datagram Congestion Control Protocol (DCCP) — language of work or name (P407): English[8].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s publication date is recorded as +2006-03-01T00:00:00Z[9].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s RfC ID is recorded as 4336[10].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s main subject is recorded as Problem Statement for the Datagram Congestion Control Protocol (DCCP) — main subject (P921): Datagram Congestion Control Protocol[11].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc4336[12].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc4336.txt[13].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4336.txt[14].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4336.txt.pdf[15].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s number of pages is recorded as {'unit': '1', 'amount': '+22'}[16].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s title is recorded as Problem Statement for the Datagram Congestion Control Protocol (DCCP)[17].
- RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s DBLP publication ID is recorded as journals/rfc/rfc4336[18].
Body
Designation and Status
RFC 4336: Problem Statement for the Datagram Congestion Control Protocol (DCCP)'s instance of is recorded as Problem Statement for the Datagram Congestion Control Protocol (DCCP) — instance of (P31): Request for Comments[5].