Re: [sipcore] Understanding Privacy: history invoked by UAS

<R.Jesske@telekom.de> Thu, 11 November 2010 08:23 UTC

Return-Path: <R.Jesske@telekom.de>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B58A33A69B3 for <sipcore@core3.amsl.com>; Thu, 11 Nov 2010 00:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level:
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.725, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id By+svMvHcFSm for <sipcore@core3.amsl.com>; Thu, 11 Nov 2010 00:23:03 -0800 (PST)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id 6622B3A69AC for <sipcore@ietf.org>; Thu, 11 Nov 2010 00:23:03 -0800 (PST)
Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 11 Nov 2010 09:23:02 +0100
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.118]) by he110890 ([10.134.92.131]) with mapi; Thu, 11 Nov 2010 09:22:58 +0100
From: <R.Jesske@telekom.de>
To: <dworley@avaya.com>, <HKaplan@acmepacket.com>, <shida@ntt-at.com>
Date: Thu, 11 Nov 2010 09:22:55 +0100
Thread-Topic: [sipcore] Understanding Privacy: history invoked by UAS
Thread-Index: AcuAkx168p1bfSMAT9G6L6ZMOBxfCwA40ZL7AAB4J3A=
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D0146FC0E@HE111648.emea1.cds.t-internal.com>
References: <A444A0F8084434499206E78C106220CA02357ADA69@MCHP058A.global-ad.net> <A78B9020-EB78-477E-8B2A-22F8F27B1032@ntt-at.com> <A444A0F8084434499206E78C106220CA023587F123@MCHP058A.global-ad.net> <1A3940A5-123E-4FF1-8B94-76B6C5B49596@ntt-at.com>, <7B01FB93-0DD5-47B5-BB01-B2E6FAED3DDA@acmepacket.com> <CD5674C3CD99574EBA7432465FC13C1B2202288A05@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288A05@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Understanding Privacy: history invoked by UAS
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Nov 2010 08:23:04 -0000

For call forwarding the entries will be counted when a "mp" is included. This is due to avoid to many Call forwardings.
3GPP has defined their service in counting the entries where a "cause" regarding RFC4458 is included.

So if such entries will be deleted then the counter number of diversions is not correct, which is also needed for the interworking with the PSTN.

Roland

> -----Ursprüngliche Nachricht-----
> Von: sipcore-bounces@ietf.org
> [mailto:sipcore-bounces@ietf.org] Im Auftrag von Worley, Dale R (Dale)
> Gesendet: Donnerstag, 11. November 2010 09:00
> An: Hadriel Kaplan; Shida Schubert
> Cc: sipcore@ietf.org
> Betreff: Re: [sipcore] Understanding Privacy: history invoked by UAS
>
> ________________________________________
> From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On
> Behalf Of Hadriel Kaplan [HKaplan@acmepacket.com]
>
> Out of curiosity, will anything "break" if the anonymized H-I
> entries are simply removed?  I'm not suggesting we document
> doing that in the draft, just asking if any
> apps/use-cases/whatever will break if it happens.  Because my
> guess is some of us will just remove them, and I'd like to
> know if there's any real reason I shouldn't.
> _______________________________________________
>
> Hmmm...  Another reason that we need to definitively define
> what constitutes a valid H-I value and what does not.  (This
> is tracker issue 34: http://tools.ietf.org/wg/sipcore/trac/ticket/34)
>
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>