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

rfc-editor@rfc-editor.org Thu, 30 October 2008 18:24 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F07CD3A6A3F; Thu, 30 Oct 2008 11:24:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B455D3A6A3F; Thu, 30 Oct 2008 11:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.299
X-Spam-Level:
X-Spam-Status: No, score=-18.299 tagged_above=-999 required=5 tests=[AWL=0.700, BAYES_00=-2.599, GB_I_INVITATION=-2, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcYjZ1Ee3mgN; Thu, 30 Oct 2008 11:24:52 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id E61FD3A693E; Thu, 30 Oct 2008 11:24:52 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 1403C16CBA6; Thu, 30 Oct 2008 11:24:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182452.1403C16CBA6@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:24:52 -0700
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5360 on A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

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@cisco.com, 
                    Gonzalo.Camarillo@ericsson.com, 
                    dean.willis@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. 
[STANDARDS TRACK]

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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@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


_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip