On 7/31/08 2:56 PM, Dan Wing wrote:
Sorry, I was a bit unclear. When I talk about this "chain of
custody," I
mean everything that has performed an action that would invalidate a
4474 signature; everything that has had to re-sign something.
Those are
the actions that require a level of trust. As long as the ITSP you
mention doesn't change 4474-protected fields, I don't care
who they are.
Oh, so something like: "The original list of codecs was G.729,G.711" and to
convey it in such a way that I could re-insert G.729 and validate the original
4474 signature? And something like "The original m/c line was 1.2.3.4/5678"?
Yes, that has the right property -- enough information to reconstruct
which changes were made, and by whom.
/a
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
