RFC 3702: Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
As Session Initiation Protocol (SIP) services are deployed on the Internet, there is a need for authentication, authorization, and accounting of SIP sessions. This document sets out the basic requirements for this work. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3702
- Published
- February 2004
- Authors
- J. Loughney; G. Camarillo
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3694Threat Analysis of the Geopriv ProtocolUpdated
February 2004
- RFC 3693Geopriv RequirementsUpdated
February 2004
- RFC 3711The Secure Real-time Transport Protocol (SRTP)Updated
March 2004
- RFC 3690IP Telephony Requirements for Emergency Telecommunication Service (ETS)Current
February 2004
- RFC 3689General Requirements for Emergency Telecommunication Service (ETS)Current
February 2004
- RFC 3680A Session Initiation Protocol (SIP) Event Package for RegistrationsUpdated
March 2004
- RFC 3725Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)Current
April 2004
- RFC 3666Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call FlowsCurrent
January 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?