RFC 8119 on SIP "cause" URI Parameter for Service Number Translation
rfc-editor@rfc-editor.org Thu, 16 March 2017 00:09 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 350D61300E7 for <ietf-announce@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blXKxvGOeA_D for <ietf-announce@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D01513012B for <ietf-announce@ietf.org>; Wed, 15 Mar 2017 17:08:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C46AFB81533; Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8119 on SIP "cause" URI Parameter for Service Number Translation
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170316000808.C46AFB81533@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:08:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lR4sDvs0f5NHP6OQnoVfMDxKwro>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 16 Mar 2017 00:09:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8119
Title: SIP "cause" URI Parameter for
Service Number Translation
Author: M. Mohali, M. Barnes
Status: Informational
Stream: IETF
Date: March 2017
Mailbox: marianne.mohali@orange.com,
mary.ietf.barnes@gmail.com
Pages: 12
Characters: 24142
Updates: RFC 4458
I-D Tag: draft-mohali-dispatch-cause-for-service-number-14.txt
URL: https://www.rfc-editor.org/info/rfc8119
DOI: 10.17487/RFC8119
RFC 4458 (regarding SIP URIs for applications) defines a "cause" URI
parameter, which may appear in the Request-URI of a SIP request, that
is used to indicate a reason why the request arrived to the User
Agent Server (UAS) receiving the message. This document updates RFC
4458 by creating a new predefined value for the "cause" URI parameter
to cover service number translation for cases of retargeting due to
specific service action leading to the translation of a called
service access number. This document also provides guidance, which
was missing in RFC 4458, for using the "cause" URI parameter within
the History-Info header field, since this use is mandatory in some IP
networks' implementations.
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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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