RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
0 sources
RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
Summary
RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) is a Request for Comments[1].
Key Facts
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) authored Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) — author (P50): Christer Holmberg[2].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s instance of is recorded as Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[3].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s publisher is recorded as Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) — publisher (P123): Internet Engineering Task Force[4].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s based on is recorded as Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) — based on (P144): RFC 3261: SIP: Session Initiation Protocol[5].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s DOI is recorded as 10.17487/RFC8898[6].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s language of work or name is recorded as Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) — language of work or name (P407): English[7].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s publication date is recorded as +2020-09-01T00:00:00Z[8].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s RfC ID is recorded as 8898[9].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc8898[10].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s title is recorded as Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)[11].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s author name string is recorded as R. Shekh-Yusef[12].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s author name string is recorded as V. Pascual[13].
- RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s DBLP publication ID is recorded as journals/rfc/rfc8898[14].
Body
Designation and Status
RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)'s instance of is recorded as Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[3].