Session Initiation Protocol Authenticated Identity Body Format
RFC 3893, “Session Initiation Protocol Authenticated Identity Body Format”, is a Proposed Standard document published in September 2004 by J. Peterson. The canonical text is published by the RFC Editor.
Abstract
RFC 3261 introduces the concept of adding an S/MIME body to a Session Initiation Protocol (SIP) request or response in order to provide reference integrity over its headers. This document provides a more specific mechanism to derive integrity and authentication properties from an 'authenticated identity body', a digitally-signed SIP message, or message fragment. A standard format for such bodies (known as Authenticated Identity Bodies, or AIBs) is given in this document. Some considerations for the processing of AIBs by recipients of SIP messages with such bodies are also given. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3893 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3892 The Session Initiation Protocol Referred-By Mechanism
- RFC 3894 Sieve Extension: Copying Without Side Effects
- RFC 3891 The Session Initiation Protocol "Replaces" Header
- RFC 3895 Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types
- RFC 3890 A Transport Independent Bandwidth Modifier for the Session Description Protocol
- RFC 3896 Definitions of Managed Objects for the DS3/E3 Interface Type
- RFC 3897 Open Pluggable Edge Services Entities and End Points Communication
- RFC 3888 Message Tracking Model and Requirements