RFC 7433 on A Mechanism for Transporting User-to-User Call Control Information in SIP

rfc-editor@rfc-editor.org Fri, 23 January 2015 04:38 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 964A41A1AA1; Thu, 22 Jan 2015 20:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id fTPRkyZ4cNzQ; Thu, 22 Jan 2015 20:38:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id D26881A0169; Thu, 22 Jan 2015 20:38:24 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 33897187E26; Thu, 22 Jan 2015 20:38:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7433 on A Mechanism for Transporting User-to-User Call Control Information in SIP
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150123043800.33897187E26@rfc-editor.org>
Date: Thu, 22 Jan 2015 20:38:00 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/hTTq8HknH8BSQ5LMfgWWWXHsuq8>
Cc: drafts-update-ref@iana.org, cuss@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 04:38:26 -0000

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

        RFC 7433

        Title:      A Mechanism for Transporting User-to-User 
                    Call Control Information in SIP 
        Author:     A. Johnston, J. Rafferty
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2015
        Mailbox:    alan.b.johnston@gmail.com, 
        Pages:      19
        Characters: 45687
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cuss-sip-uui-17.txt

        URL:        https://www.rfc-editor.org/info/rfc7433

There is a class of applications that benefit from using SIP to
exchange User-to-User Information (UUI) data during session
establishment.  This information, known as call control UUI data, is
a small piece of data inserted by an application initiating the
session and utilized by an application accepting the session.  The
syntax and semantics for the UUI data used by a specific application
are defined by a UUI package.  This UUI data is opaque to SIP and its
function is unrelated to any basic SIP function.  This document
defines a new SIP header field, User-to-User, to transport UUI data,
along with an extension mechanism.

This document is a product of the Call Control UUI Service for SIP Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.rfc-editor.org/search
For downloading RFCs, see https://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
Association Management Solutions, LLC