draft-ietf-mmusic-rtsp-nat-evaluation-08.txt   draft-ietf-mmusic-rtsp-nat-evaluation-09.txt 
Network Working Group M. Westerlund Network Working Group M. Westerlund
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational T. Zeng Intended status: Informational T. Zeng
Expires: November 28, 2013 May 27, 2013 Expires: November 30, 2013 May 29, 2013
The Evaluation of Different Network Address Translator (NAT) Traversal The Evaluation of Different Network Address Translator (NAT) Traversal
Techniques for Media Controlled by Real-time Streaming Protocol (RTSP) Techniques for Media Controlled by Real-time Streaming Protocol (RTSP)
draft-ietf-mmusic-rtsp-nat-evaluation-08 draft-ietf-mmusic-rtsp-nat-evaluation-09
Abstract Abstract
This document describes several Network Address Translator (NAT) This document describes several Network Address Translator (NAT)
traversal techniques that were considered to be used for establishing traversal techniques that were considered to be used for establishing
the RTP media flows controlled by the Real-time Streaming Protocol the RTP media flows controlled by the Real-time Streaming Protocol
(RTSP). Each technique includes a description on how it would be (RTSP). Each technique includes a description on how it would be
used, the security implications of using it and any other deployment used, the security implications of using it and any other deployment
considerations it has. There are also discussions on how NAT considerations it has. There are also discussions on how NAT
traversal techniques relates to firewalls and how each technique can traversal techniques relates to firewalls and how each technique can
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 28, 2013. This Internet-Draft will expire on November 30, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 32, line 27 skipping to change at page 32, line 27
3. The RTSP client uses the acquired address and port allocations in 3. The RTSP client uses the acquired address and port allocations in
the RTSP SETUP request using the destination header. the RTSP SETUP request using the destination header.
4. The RTSP Server sends the SETUP reply, which must include the 4. The RTSP Server sends the SETUP reply, which must include the
transport headers src_addr parameter (source and port in RTSP transport headers src_addr parameter (source and port in RTSP
1.0). Note that the server is required to have a mechanism to 1.0). Note that the server is required to have a mechanism to
verify that it is allowed to send media traffic to the given verify that it is allowed to send media traffic to the given
address. address.
5. The RTSP Client uses the RTSP Servers response to create TURN 5. The RTSP Client uses the RTSP Server's response to create TURN
permissions for the server's media traffic. permissions for the server's media traffic.
6. The client requests that the server starts playing. The server 6. The client requests that the server starts playing. The server
starts sending media packets to the given destination address and starts sending media packets to the given destination address and
ports. ports.
7. The first media packet to arrive at the TURN server on the 7. The first media packet arrive at the TURN server on the external
external port; If matching established permissions the TURN port; If the packet matches an established permission the TURN
server forwards the media packets to the RTSP client. server forwards the media packet to the RTSP client.
8. If the client pauses and media is not sent for about 75% of the 8. If the client pauses and media is not sent for about 75% of the
mapping timeout the client should use TURN to refresh the mapping timeout the client should use TURN to refresh the
bindings. bindings.
4.9.3. Deployment Considerations 4.9.3. Deployment Considerations
Advantages: Advantages:
o Does not require any server modifications given that the server o Does not require any server modifications given that the server
skipping to change at page 38, line 11 skipping to change at page 38, line 11
[I-D.ietf-mmusic-rfc2326bis] [I-D.ietf-mmusic-rfc2326bis]
Schulzrinne, H., Rao, A., Lanphier, R., Westerlund, M., Schulzrinne, H., Rao, A., Lanphier, R., Westerlund, M.,
and M. Stiemerling, "Real Time Streaming Protocol 2.0 and M. Stiemerling, "Real Time Streaming Protocol 2.0
(RTSP)", draft-ietf-mmusic-rfc2326bis-34 (work in (RTSP)", draft-ietf-mmusic-rfc2326bis-34 (work in
progress), April 2013. progress), April 2013.
[I-D.ietf-mmusic-rtsp-nat] [I-D.ietf-mmusic-rtsp-nat]
Goldberg, J., Westerlund, M., and T. Zeng, "A Network Goldberg, J., Westerlund, M., and T. Zeng, "A Network
Address Translator (NAT) Traversal mechanism for media Address Translator (NAT) Traversal mechanism for media
controlled by Real-Time Streaming Protocol (RTSP)", draft- controlled by Real-Time Streaming Protocol (RTSP)", draft-
ietf-mmusic-rtsp-nat-15 (work in progress), May 2013. ietf-mmusic-rtsp-nat-16 (work in progress), May 2013.
[NICE] , "Libnice - The GLib ICE implementation, [NICE] , "Libnice - The GLib ICE implementation,
http://nice.freedesktop.org/wiki/", May 2013. http://nice.freedesktop.org/wiki/", May 2013.
[PJNATH] , "PJNATH - Open Source ICE, STUN, and TURN Library, [PJNATH] , "PJNATH - Open Source ICE, STUN, and TURN Library,
http://www.pjsip.org/pjnath/docs/html/", May 2013. http://www.pjsip.org/pjnath/docs/html/", May 2013.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
 End of changes. 6 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/