RFC 6072: Certificate Management Service for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document defines a credential service that allows Session Initiation Protocol (SIP) User Agents (UAs) to use a SIP event package to discover the certificates of other users. This mechanism allows User Agents that want to contact a given Address-of-Record (AOR) to retrieve that AOR's certificate by subscribing to the credential service, which returns an authenticated response containing that certificate. The credential service also allows users to store and retrieve their own certificates and private keys. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6072
- Published
- February 2011
- Authors
- C. Jennings; J. Fischl
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3764enumservice registration for Session Initiation Protocol (SIP) Addresses-of-RecordUpdated
April 2004
- RFC 6080A Framework for Session Initiation Protocol User Agent Profile DeliveryCurrent
March 2011
- RFC 6051Rapid Synchronisation of RTP FlowsCurrent
November 2010
- RFC 6035Session Initiation Protocol Event Package for Voice Quality ReportingCurrent
November 2010
- RFC 6116The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Current
March 2011
- RFC 6117IANA Registration of Enumservices: Guide, Template, and IANA ConsiderationsCurrent
March 2011
- RFC 6118Update of Legacy IANA Registrations of EnumservicesCurrent
March 2011
- RFC 6128RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) SessionsCurrent
February 2011
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?