[rfc-dist] RFC 3893 on Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format

[rfc-editor at rfc-editor.org]

A new Request for Comments is now available in online RFC libraries.


        RFC 3893

        Title:      Session Initiation Protocol (SIP)
                    Authenticated Identity Body (AIB) Format
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    jon.peterson at neustar.biz
        Pages:      13
        Characters: 28500
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-authid-body-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3893.txt


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 document is a product of the Session Initiation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative