RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)
0 sources
RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)
Summary
RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP) is a Request for Comments[1].
Key Facts
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP) authored Referring to Multiple Resources in the Session Initiation Protocol (SIP) — author (P50): Gonzalo Camarillo[2].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s instance of is recorded as Referring to Multiple Resources in the Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[3].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s publisher is recorded as Referring to Multiple Resources in the Session Initiation Protocol (SIP) — publisher (P123): Internet Engineering Task Force[4].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s DOI is recorded as 10.17487/RFC5368[5].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s language of work or name is recorded as Referring to Multiple Resources in the Session Initiation Protocol (SIP) — language of work or name (P407): English[6].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s publication date is recorded as +2008-10-01T00:00:00Z[7].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s RfC ID is recorded as 5368[8].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s main subject is recorded as Referring to Multiple Resources in the Session Initiation Protocol (SIP) — main subject (P921): Session Initiation Protocol[9].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc5368[10].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc5368.txt[11].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5368.txt[12].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5368.txt.pdf[13].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s number of pages is recorded as {'unit': '1', 'amount': '+13'}[14].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s title is recorded as Referring to Multiple Resources in the Session Initiation Protocol (SIP)[15].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s author name string is recorded as A. Niemi[16].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s author name string is recorded as M. Isomaki[17].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s author name string is recorded as M. Garcia-Martin[18].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s author name string is recorded as H. Khartabil[19].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s amended by is recorded as Referring to Multiple Resources in the Session Initiation Protocol (SIP) — amended by (P2567): RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)[20].
- RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s DBLP publication ID is recorded as journals/rfc/rfc5368[21].
Body
Designation and Status
RFC 5368: Referring to Multiple Resources in the Session Initiation Protocol (SIP)'s instance of is recorded as Referring to Multiple Resources in the Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[3].