RFC 7044 on An Extension to the Session Initiation Protocol (SIP) for Request History Information

rfc-editor@rfc-editor.org Tue, 04 February 2014 19:16 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 474141A01E0; Tue, 4 Feb 2014 11:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id uffEpG4JiOgG; Tue, 4 Feb 2014 11:15:58 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id D80631A01DF; Tue, 4 Feb 2014 11:15:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7CAF67FC159; Tue, 4 Feb 2014 11:15:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7044 on An Extension to the Session Initiation Protocol (SIP) for Request History Information
From: rfc-editor@rfc-editor.org
Message-Id: <20140204191557.7CAF67FC159@rfc-editor.org>
Date: Tue, 4 Feb 2014 11:15:57 -0800 (PST)
Cc: drafts-update-ref@iana.org, sipcore@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: Tue, 04 Feb 2014 19:16:00 -0000

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

        RFC 7044

        Title:      An Extension to the Session 
                    Initiation Protocol (SIP) for 
                    Request History Information 
        Author:     M. Barnes, F. Audet,
                    S. Schubert, J. van Elburg,
                    C. Holmberg
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2014
        Mailbox:    mary.ietf.barnes@gmail.com, 
        Pages:      36
        Characters: 85068
        Obsoletes:  RFC 4244

        I-D Tag:    draft-ietf-sipcore-rfc4244bis-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7044.txt

This document defines a standard mechanism for capturing the history
information associated with a Session Initiation Protocol (SIP)
request.  This capability enables many enhanced services by providing
the information as to how and why a SIP request arrives at a specific
application or user.  This document defines an optional SIP header
field, History-Info, for capturing the history information in
requests.  The document also defines SIP header field parameters for
the History-Info and Contact header fields to tag the method by which
the target of a request is determined.  In addition, this
specification defines a value for the Privacy header field that
directs the anonymization of values in the History-Info header field.
This document obsoletes RFC 4244.

This document is a product of the Session Initiation Protocol Core 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 Internet
Official Protocol Standards (STD 1) 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 http://www.rfc-editor.org/search/rfc_search.php
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