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

Responses inline below [MB].

On Thu, Nov 11, 2010 at 1:59 AM, Worley, Dale R (Dale) <dworley@avaya.com>wrote:

> ________________________________________
> 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.
>
[MB] Hadriel - There is text that describes that applications must be able
to handle gaps and thus not break. We can't police the protocol, but
removing the entries would not be normative behavior since it could impact
an end application that wants to make use of the information. This is the
usual be generous in what you receive...[/MB]

> _______________________________________________
>
> 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)
>
[MB] Dale - I don't see that Issue 34 is related to this specific issue.
Please see my response to issue 34 on the mailing list. [/MB]

> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>