RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)
0 sources
RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)
Summary
RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) is a Request for Comments[1].
Key Facts
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) authored The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) — author (P50): Gonzalo Camarillo[2].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s instance of is recorded as The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) — instance of (P31): Request for Comments[3].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s publisher is recorded as The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) — publisher (P123): Internet Engineering Task Force[4].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s DOI is recorded as 10.17487/RFC5002[5].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s language of work or name is recorded as The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) — language of work or name (P407): English[6].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s publication date is recorded as +2007-08-01T00:00:00Z[7].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s RfC ID is recorded as 5002[8].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s main subject is recorded as The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) — main subject (P921): Session Initiation Protocol[9].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s work available at URL is recorded as https://tools.ietf.org/html/rfc5002[10].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc5002.txt[11].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5002.txt[12].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5002.txt.pdf[13].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s number of pages is recorded as {'unit': '1', 'amount': '+7'}[14].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s title is recorded as The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)[15].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s author name string is recorded as G. Blanco[16].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s amended by is recorded as The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) — amended by (P2567): RFC 8217: Clarifications for When to Use the name-addr Production in SIP Messages[17].
- RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s DBLP publication ID is recorded as journals/rfc/rfc5002[18].
Body
Designation and Status
RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)'s instance of is recorded as The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) — instance of (P31): Request for Comments[3].