Re: draft-johnston-sipping-cc-uui-05

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: sipping-bounces@xxxxxxxx [mailto:sipping-bounces@xxxxxxxx] On Behalf
> Of Cullen Jennings
>
> I can easily imagine cases where customer sensitize information was
> transfered over this and it was going to an remote agent phone that
> went through another trust domain to route the call to the agent. In
> these cases, I think an important requirement would be to  protect the
> draft from authorized access by intermediaries.

Do you mean protect it from unauthorized access?  Or allow for authorized access? (and I assume you mean the UUI data, not protect the "draft" ;)

I don't think there's anything you can do to stop tampering or reading it, without pre-shared keys or certs of course.  And middleboxes can already read and modify ISUP mime bodies so it's not any worse really.

-hadriel
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP

[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux