[Sip] draft-ietf-sip-history-info-01.txt

"Jesske, R" <R.Jesske@t-com.net> Fri, 16 January 2004 09:45 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06824 for <sip-archive@odin.ietf.org>; Fri, 16 Jan 2004 04:45:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AhQXG-00088P-M0 for sip-archive@odin.ietf.org; Fri, 16 Jan 2004 04:45:02 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G9j2Qo031199 for sip-archive@odin.ietf.org; Fri, 16 Jan 2004 04:45:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AhQWJ-000866-HA; Fri, 16 Jan 2004 04:44:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AhQVP-00084C-Gb for sip@optimus.ietf.org; Fri, 16 Jan 2004 04:43:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06780 for <sip@ietf.org>; Fri, 16 Jan 2004 04:43:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AhQVM-0006E3-00 for sip@ietf.org; Fri, 16 Jan 2004 04:43:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AhQUT-0006CQ-00 for sip@ietf.org; Fri, 16 Jan 2004 04:42:09 -0500
Received: from mail4.telekom.de ([195.243.210.197]) by ietf-mx with esmtp (Exim 4.12) id 1AhQU8-0006AO-00 for sip@ietf.org; Fri, 16 Jan 2004 04:41:48 -0500
Received: from g8pbr.blf01.telekom.de by mail2.dmz.telekom.de with ESMTP for sip@ietf.org; Fri, 16 Jan 2004 10:29:09 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19) id <CY59GR8V>; Fri, 16 Jan 2004 10:29:09 +0100
Message-Id: <953B9B08F98DD61183F8000347AE660102862DE6@G8PPV.blf01.telekom.de>
From: "Jesske, R" <R.Jesske@t-com.net>
To: sip@ietf.org
Cc: "Poetzl, Joachim" <Joachim.Poetzl@t-com.net>, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
Date: Fri, 16 Jan 2004 10:29:06 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [Sip] draft-ietf-sip-history-info-01.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>

Dear all,
in 1.3 Ensuring the Privacy of History_Info it is proposed to use a priv-value of Session or Header level privacy. I would like to propose a own privacy level for the history info, because the Information shows also information about the network. With regard to the provider operating a network some of the providers don't like to transmit information about call history. Or a redirecting party don't like to show the redirecting address.
Therefore it should be possible to delete the history info at domain boundaries based on the privacy-value.

I propose the priv-value   =   "history_info"  for the whole History-Info header.

In addition a option would be useful where only parts (e.g Indes1.1) of the history info are restricted. That could be done with a privacy statement within the History-Info .

Best Regards

Roland


Deutsche Telekom AG
T Com Zentrale
Roland Jesske, T332-2
Section T33; Signalling, Gateways and Switching Systems 
Am Kavalleriesand 3, 64295 Darmstadt, Germany
Phone:  +49 6151 83-5940 
Fax:      +49 6151 83-4577 
email:   r.jesske@t-com.net




_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip