Browse Prior Art Database

Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format (RFC3893)

IP.com Disclosure Number: IPCOM000031627D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2004-Oct-01
Document File: 14 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Peterson: AUTHOR

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group                                        J. Peterson

Request for Comments: 3893                                       NeuStar

Category: Standards Track                                 September 2004

                   Session Initiation Protocol (SIP)

                Authenticated Identity Body (AIB) Format

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

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.

Peterson                    Standards Track                     [Page 1]

RFC 3893      SIP Authenticated Identity Body (AIB) FormatSeptember 2004

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2

       1.1.  Requirements Notation. . . . . . . . . . . . . . . . . .  3

   2.  AIB Format . . . . . . . . . . . . . . . . . . . . . . . . . .  4

   3.  Example of a Request with AIB  . . . . . . . . . . . . . . . .  5

   4.  AIBs for Identifying Third-Parties . . . . . . . . . . . . . .  6

   5.  Identity in non-INVITE Requests  . . . . . . . . . . . . . . .  7

   6.  Identity in Responses  . . . . . . . . . . . . . . . . . . . .  7

   7.  Receiving an AIB . . . . . . . . . . . . . . . . . . . . . . .  7

   8.  Encryption of Identity . . . . . . . . . . . . . . . . . . . .  8

   9.  Example of Encryption  . . . . . . . . . . . . . . . . . . . .  8

   10. Security Considerations  . . . . . . . . . . . . . . . . . . .  9

   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11

   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11

       12.1. Normative References . . . . . . . . . . . . . . . . . . 11

       12.2. Informative References . . . . . . . . . . . . . . . . . 11

   13. Acknowledgements . . . . . . . . . . . . . . . ....