One of the questions raised at the end of the SIP session today was the
following:
"Are there any useful steps for dealing with SDP modification by SBCs?"
SBCs modify SDP (and perhaps other signed information in SIP requests).
One of the reasons is NAT traversal (should not be applicable with ICE,
but I don't think we can always assume that ICE is used). Other reasons
are topology hiding, media shaping, etc.. Such modification breaks RFC
4474 signatures.
SBCs also sometimes change From URIs in SIP requests, as discussed in
draft-kaplan-sip-uris-change-00. We have taken this into account during
our various discussions (in the WG and off-line) on the telephone number
problem, so I want to keep that separate. For this thread, assume an
"email-style" (or non-phone-number-based) From URI that is not modified
by an SBC. Focus instead on modification of other signed information.
I would like to hear views on the following:
- The degree to which this is a problem.
- Existing solution proposals:
o draft-wing-sip-identity-media-02
o draft-fischer-sip-e2e-sec-media-00
- Other solution proposals.
John
_______________________________________________
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
