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

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
>