[rfc-dist] RFC 5360 on A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Oct 30 11:24:52 PDT 2008

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

        RFC 5360

        Title:      A Framework for Consent-Based Communications 
                    in the Session Initiation Protocol (SIP) 
        Author:     J. Rosenberg, G. Camarillo,
                    Ed., D. Willis
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    jdrosen at cisco.com, 
                    Gonzalo.Camarillo at ericsson.com, 
                    dean.willis at softarmor.com
        Pages:      31
        Characters: 70658
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-consent-framework-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5360.txt

SIP supports communications for several services, including real-time
audio, video, text, instant messaging, and presence.  In its current
form, it allows session invitations, instant messages, and other
requests to be delivered from one party to another without requiring
explicit consent of the recipient.  Without such consent, it is
possible for SIP to be used for malicious purposes, including
amplification and DoS (Denial of Service) attacks.  This document
identifies a framework for consent-based communications in SIP. 

This document is a product of the Session Initiation Protocol Working 
Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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

The RFC Editor Team
USC/Information Sciences Institute

More information about the rfc-dist mailing list