RFC 7434 on Interworking ISDN Call Control User Information with 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 BACBF1A9030; Thu, 22 Jan 2015 20:38:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 VutGSaXekCHf; Thu, 22 Jan 2015 20:38:39 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 227231A9009; Thu, 22 Jan 2015 20:38:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 780F6187E27; Thu, 22 Jan 2015 20:38:14 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7434 on Interworking ISDN Call Control User Information with SIP
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150123043814.780F6187E27@rfc-editor.org>
Date: Thu, 22 Jan 2015 20:38:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/fyaKuCGFL9SfSnwJPyxsCKmEMPw>
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:44 -0000

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

        RFC 7434

        Title:      Interworking ISDN Call Control User 
                    Information with SIP 
        Author:     K. Drage, Ed.,
                    A. Johnston
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2015
        Mailbox:    keith.drage@alcatel-lucent.com, 
        Pages:      17
        Characters: 39276
        Updates/Obsoletes/SeeAlso:   None

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

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

The motivation and use cases for interworking and transporting User-
to-User Information (UUI) from the ITU-T Digital Subscriber
Signalling System No. 1 (DSS1) User-user information element within
SIP are described in RFC 6567.  As networks move to SIP, it is
important that applications requiring this data can continue to
function in SIP networks as well as have the ability to interwork
with this ISDN service for end-to-end transparency.  This document
defines a usage (a new package called the ISDN UUI package) of the
User-to-User header field to enable interworking with this ISDN

This document covers interworking with both public ISDN and private
ISDN capabilities, so the potential interworking with QSIG will also
be addressed.

The package is identified by the new value "isdn-uui" of the
"purpose" header field parameter.

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