RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)
0 sources
RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)
Summary
RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP) is a Request for Comments[1].
Key Facts
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP) authored Content-ID Header Field in the Session Initiation Protocol (SIP) — author (P50): Christer Holmberg[2].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s instance of is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[3].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s publisher is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — publisher (P123): Internet Engineering Task Force[4].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s based on is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — based on (P144): RFC 5621: Message Body Handling in the Session Initiation Protocol (SIP)[5].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s based on is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — based on (P144): RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)[6].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s based on is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — based on (P144): RFC 6442: Location Conveyance for the Session Initiation Protocol[7].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s DOI is recorded as 10.17487/RFC8262[8].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s language of work or name is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — language of work or name (P407): English[9].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s publication date is recorded as +2017-10-01T00:00:00Z[10].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s RfC ID is recorded as 8262[11].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s main subject is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — main subject (P921): Session Initiation Protocol[12].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc8262[13].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc8262.txt[14].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc8262.txt[15].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc8262.txt.pdf[16].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s number of pages is recorded as {'unit': '1', 'amount': '+14'}[17].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s title is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP)[18].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s author name string is recorded as I. Sedlacek[19].
- RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s DBLP publication ID is recorded as journals/rfc/rfc8262[20].
Body
Designation and Status
RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)'s instance of is recorded as Content-ID Header Field in the Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[3].