RFC 3329 on Security Mechanism Agreement for the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Tue, 07 January 2003 11:14 UTC

Message-Id: <200301062346.h06NkpD27924@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3329 on Security Mechanism Agreement for the Session Initiation Protocol (SIP)
Cc: rfc-editor@rfc-editor.org, sip@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 06 Jan 2003 15:46:51 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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


        RFC 3329

        Title:      Security Mechanism Agreement for the Session
                    Initiation Protocol (SIP)
        Author(s):  J. Arkko, V. Torvinen, G. Camarillo, A. Niemi,
                    T. Haukka
        Status:     Standards Track
        Date:       January 2003
        Mailbox:    jari.arkko@ericsson.com,
                    vesa.torvinen@ericsson.fi,
                    Gonzalo.Camarillo@ericsson.com,
                    aki.niemi@nokia.com, tao.haukka@nokia.com
        Pages:      24
        Characters: 51503
        Updates/Obsoletes/See Also:   None

        I-D Tag:    draft-ietf-sip-sec-agree-05.txt

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


This document defines new functionality for negotiating the security
mechanisms used between a Session Initiation Protocol (SIP) user
agent and its next-hop SIP entity.  This new functionality
supplements the existing methods of choosing security mechanisms
between SIP entities.

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@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.

ftp://ftp.isi.edu/in-notes/rfc3329.txt"><ftp://ftp.isi.edu/in-notes/rfc3329.txt>

RFC 3329 on Security Mechanism Agreement for the … rfc-editor