[Sipping] Document Action: 'Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)' to Informational RFC
The IESG <iesg-secretary@ietf.org> Wed, 25 January 2006 18:08 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1p4D-0002cg-O4; Wed, 25 Jan 2006 13:08:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1p48-0002bP-9M; Wed, 25 Jan 2006 13:08:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07237; Wed, 25 Jan 2006 13:06:49 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1pDw-0002xo-1I; Wed, 25 Jan 2006 13:18:28 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1F1p47-00025o-80; Wed, 25 Jan 2006 13:08:19 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1F1p47-00025o-80@newodin.ietf.org>
Date: Wed, 25 Jan 2006 13:08:19 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: sipping chair <rohan@ekabal.com>, Internet Architecture Board <iab@iab.org>, sipping chair <dean.willis@softarmor.com>, sipping mailing list <sipping@ietf.org>, sipping chair <gonzalo.camarillo@ericsson.com>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Sipping] Document Action: 'Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)' to Informational RFC
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
The IESG has approved the following document: - 'Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP) ' <draft-ietf-sipping-consent-reqs-04.txt> as an Informational RFC This document is the product of the Session Initiation Proposal Investigation Working Group. The IESG contact person is Allison Mankin. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sipping-consent-reqs-04.txt Technical Summary This document describes requirements for an explicit-consent forwarding system for the Session Initiation Protocol (SIP). SIP is an Internet application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. SIP sessions are separate from the media flows they establish. These sessions include, in particular, telephone calls and sessions of instant messages. By nature these services are intentionally intrusive and therefore sensitive to undesirable communications. SIP is designed according to the end-to-end principle and therefore allows and expects delivery from any SIP node to any other SIP node with no prior relationship. The requirements in this document are designed to prevent undesirable communications in several forms, by allowing explicit authorization and revocation to forward SIP requests. These requirements are particularly important in the context of URIs which represent lists or multiple users. Working Group Summary The document is a product of the SIPPING working group and was developed over the course of about one year. The SIP community (including participants of the SIMPLE, SIP, and SIPPING working groups) and portions of the XCON working group jointly discussed and developed new mechanisms to forward a single SIP request to a list of participants (similar to an email mailing list) in support of applications such as push-to-talk, dial-out conferencing, and group paging style instant messages. The groups realized that such a mechanism is a potential amplifier for unsolicited communications and denial-of-service attacks. This document describes requirements for an explicit-consent authorization and revocation system to mitigate this and related attacks. The working group demonstrated strong consensus to deliver a standard solution to this problem, and support for, or no objection to the specific requirements. The working group is energetically developing mechanisms from these requirements. It considered its consensus on this document to significance as a milestone. Protocol Quality This document was shepherded under the PROTO process by Rohan Mahy, co-chair of the SIP and SIPPING working groups. Note to RFC Editor Please expand the first use of URI to Uniform Resource Identifier. _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP