RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)
0 sources
RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)
Summary
RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP) is a Request for Comments[1].
Key Facts
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP) authored Security Mechanism Agreement for the Session Initiation Protocol (SIP) — author (P50): Gonzalo Camarillo[2].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP) authored Security Mechanism Agreement for the Session Initiation Protocol (SIP) — author (P50): Jari Arkko[3].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s instance of is recorded as Security Mechanism Agreement for the Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[4].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s publisher is recorded as Security Mechanism Agreement for the Session Initiation Protocol (SIP) — publisher (P123): Internet Engineering Task Force[5].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s DOI is recorded as 10.17487/RFC3329[6].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s language of work or name is recorded as Security Mechanism Agreement for the Session Initiation Protocol (SIP) — language of work or name (P407): English[7].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s publication date is recorded as +2003-01-01T00:00:00Z[8].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s RfC ID is recorded as 3329[9].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s main subject is recorded as Security Mechanism Agreement for the Session Initiation Protocol (SIP) — main subject (P921): Session Initiation Protocol[10].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc3329[11].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc3329.txt[12].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3329.txt[13].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3329.txt.pdf[14].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s number of pages is recorded as {'unit': '1', 'amount': '+24'}[15].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s title is recorded as Security Mechanism Agreement for the Session Initiation Protocol (SIP)[16].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s author name string is recorded as V. Torvinen[17].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s author name string is recorded as A. Niemi[18].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s author name string is recorded as T. Haukka[19].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s amended by is recorded as Security Mechanism Agreement for the Session Initiation Protocol (SIP) — amended by (P2567): RFC 8996: Deprecating TLS 1.0 and TLS 1.1[20].
- RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s DBLP publication ID is recorded as journals/rfc/rfc3329[21].
Body
Designation and Status
RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP)'s instance of is recorded as Security Mechanism Agreement for the Session Initiation Protocol (SIP) — instance of (P31): Request for Comments[4].