RFC 6567 on Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP
rfc-editor@rfc-editor.org Fri, 06 April 2012 21:25 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD3711E80AE; Fri, 6 Apr 2012 14:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.375
X-Spam-Level:
X-Spam-Status: No, score=-102.375 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJxvdHfT0Q8m; Fri, 6 Apr 2012 14:25:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E005E11E80A4; Fri, 6 Apr 2012 14:25:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C57DDB1E005; Fri, 6 Apr 2012 14:12:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6567 on Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP
From: rfc-editor@rfc-editor.org
Message-Id: <20120406211224.C57DDB1E005@rfc-editor.org>
Date: Fri, 06 Apr 2012 14:12:24 -0700
Cc: cuss@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 06 Apr 2012 21:25:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6567
Title: Problem Statement and Requirements for
Transporting User-to-User Call Control Information in
SIP
Author: A. Johnston, L. Liess
Status: Informational
Stream: IETF
Date: April 2012
Mailbox: alan.b.johnston@gmail.com,
laura.liess.dt@gmail.com
Pages: 11
Characters: 25981
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-cuss-sip-uui-reqs-09.txt
URL: http://www.rfc-editor.org/rfc/rfc6567.txt
This document introduces the transport of call control User-to-User
Information (UUI) using the Session Initiation Protocol (SIP) and
develops several requirements for a new SIP mechanism. Some SIP
sessions are established by or related to a non-SIP application.
This application may have information that needs to be transported
between the SIP User Agents during session establishment. In
addition to interworking with the Integrated Services Digital Network
(ISDN) UUI Service, this extension will also be used for native SIP
endpoints requiring application UUI. This document is not an Internet
Standards Track specification; it is published for informational purposes.
This document is a product of the Call Control UUI Service for SIP Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
Association Management Solutions, LLC