RFC 4960: Stream Control Transmission Protocol
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 4960: Stream Control Transmission Protocol
Summary
RFC 4960: Stream Control Transmission Protocol is a Request for Comments[1].
Key Facts
- RFC 4960: Stream Control Transmission Protocol authored Stream Control Transmission Protocol — author (P50): Randall R. Stewart[2].
- RFC 4960: Stream Control Transmission Protocol's instance of is recorded as Stream Control Transmission Protocol — instance of (P31): Request for Comments[3].
- RFC 4960: Stream Control Transmission Protocol's publisher is recorded as Stream Control Transmission Protocol — publisher (P123): Internet Engineering Task Force[4].
- RFC 4960: Stream Control Transmission Protocol's DOI is recorded as 10.17487/RFC4960[5].
- RFC 4960: Stream Control Transmission Protocol's language of work or name is recorded as Stream Control Transmission Protocol — language of work or name (P407): English[6].
- RFC 4960: Stream Control Transmission Protocol's publication date is recorded as +2007-09-01T00:00:00Z[7].
- RFC 4960: Stream Control Transmission Protocol's RfC ID is recorded as 4960[8].
- RFC 4960: Stream Control Transmission Protocol's main subject is recorded as Stream Control Transmission Protocol — main subject (P921): Stream Control Transmission Protocol[9].
- RFC 4960: Stream Control Transmission Protocol's work available at URL is recorded as https://tools.ietf.org/html/rfc4960[10].
- RFC 4960: Stream Control Transmission Protocol's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4960.txt[11].
- RFC 4960: Stream Control Transmission Protocol's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4960.txt[12].
- RFC 4960: Stream Control Transmission Protocol's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4960.txt.pdf[13].
- RFC 4960: Stream Control Transmission Protocol's number of pages is recorded as {'unit': '1', 'amount': '+152'}[14].
- RFC 4960: Stream Control Transmission Protocol's replaces is recorded as Stream Control Transmission Protocol — replaces (P1365): RFC 2960: Stream Control Transmission Protocol[15].
- RFC 4960: Stream Control Transmission Protocol's replaces is recorded as Stream Control Transmission Protocol — replaces (P1365): RFC 3309: Stream Control Transmission Protocol (SCTP) Checksum Change[16].
- RFC 4960: Stream Control Transmission Protocol's replaced by is recorded as Stream Control Transmission Protocol — replaced by (P1366): RFC 9260: Stream Control Transmission Protocol[17].
- RFC 4960: Stream Control Transmission Protocol's title is recorded as Stream Control Transmission Protocol[18].
- RFC 4960: Stream Control Transmission Protocol's amended by is recorded as Stream Control Transmission Protocol — amended by (P2567): RFC 6096: Stream Control Transmission Protocol (SCTP) Chunk Flags Registration[19].
- RFC 4960: Stream Control Transmission Protocol's amended by is recorded as Stream Control Transmission Protocol — amended by (P2567): RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry[20].
- RFC 4960: Stream Control Transmission Protocol's amended by is recorded as Stream Control Transmission Protocol — amended by (P2567): RFC 7053: SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol[21].
- RFC 4960: Stream Control Transmission Protocol's amended by is recorded as Stream Control Transmission Protocol — amended by (P2567): RFC 8899: Packetization Layer Path MTU Discovery for Datagram Transports[22].
- RFC 4960: Stream Control Transmission Protocol's DBLP publication ID is recorded as journals/rfc/rfc4960[23].
Body
Designation and Status
RFC 4960: Stream Control Transmission Protocol's instance of is recorded as Stream Control Transmission Protocol — instance of (P31): Request for Comments[3].