RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications
0 sources
RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications
Summary
RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications is a Request for Comments[1].
Key Facts
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's instance of is recorded as Signaling Compression (SigComp) Corrections and Clarifications — instance of (P31): Request for Comments[2].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's publisher is recorded as Signaling Compression (SigComp) Corrections and Clarifications — publisher (P123): Internet Engineering Task Force[3].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's based on is recorded as Signaling Compression (SigComp) Corrections and Clarifications — based on (P144): RFC 3320: Signaling Compression (SigComp)[4].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's based on is recorded as Signaling Compression (SigComp) Corrections and Clarifications — based on (P144): RFC 3321: Signaling Compression (SigComp) - Extended Operations[5].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's based on is recorded as Signaling Compression (SigComp) Corrections and Clarifications — based on (P144): RFC 3485: The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)[6].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's DOI is recorded as 10.17487/RFC4896[7].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's language of work or name is recorded as Signaling Compression (SigComp) Corrections and Clarifications — language of work or name (P407): English[8].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's publication date is recorded as +2007-06-01T00:00:00Z[9].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's RfC ID is recorded as 4896[10].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's work available at URL is recorded as https://tools.ietf.org/html/rfc4896[11].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4896.txt[12].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4896.txt[13].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4896.txt.pdf[14].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's number of pages is recorded as {'unit': '1', 'amount': '+28'}[15].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's title is recorded as Signaling Compression (SigComp) Corrections and Clarifications[16].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's author name string is recorded as A. Surtees[17].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's author name string is recorded as M. West[18].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's author name string is recorded as A.B. Roach[19].
- RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's DBLP publication ID is recorded as journals/rfc/rfc4896[20].
Body
Designation and Status
RFC 4896: Signaling Compression (SigComp) Corrections and Clarifications's instance of is recorded as Signaling Compression (SigComp) Corrections and Clarifications — instance of (P31): Request for Comments[2].