RE: [Sip] B2BUA

Thanks, Christian.

Assuming IPv4 addresses and without delving into the draft RFC on STUN:
The SDP contains the RTP/RTCP port numbers that are private and these are
also required to be NAT'd. Now, if the SDP, which forms part of the SIP
body, is encrypted, how will RTP/RTCP ports be translated?

regards,
- sonit

> -----Original Message-----
> From: Christian Huitema [mailto:huitema@windows.microsoft.com]
> Sent: Thursday, December 05, 2002 12:54 PM
> To: Mahey, Sonit; Jonathan Rosenberg; Pete Cordell
> Cc: sip@ietf.org
> Subject: RE: [Sip] B2BUA - Security
> 
> 
> > From: Mahey, Sonit [mailto:Sonit.Mahey@icn.siemens.com]
> > Sent: Thursday, December 05, 2002 9:14 AM
> >
> > I agree with Jonathan.
> > 
> > That brings up the question:
> > Is NAT traversal for encrypted SIP traffic addressed anywhere?
> 
> There are two possibilities. If your application only uses UDP, it is
> possible to use IPv4 and STUN to find out the "outside ports" for your
> UDP traffic (check draft-ietf-midcom-stun-03.txt); you may need to use
> the "a:rtcp" convention to encode port numbers in SDP (check
> draft-ietf-mmusic-sdp4nat-03.txt). If you need to also support TCP, or
> use IPSEC, or generally do away with the complications of 
> NAT, the best
> solution is to just move to IPv6; see Teredo
> (draft-ietf-ngtrans-shipworm-08.txt) for one possible way to 
> carry IPv6
> across NAT, and 6to4 (RFC 3056 & 3068) for a possible way to 
> upgrade the
> NAT and make it an IPv6 router.
> 
> -- Christian Huitema
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip