draft-ietf-sipping-nat-scenarios-14.txt   draft-ietf-sipping-nat-scenarios-15.txt 
SIPPING Working Group C. Boulton SIPPING Working Group C. Boulton
Internet-Draft NS-Technologies Internet-Draft NS-Technologies
Intended status: BCP J. Rosenberg Intended status: Informational J. Rosenberg
Expires: July 23, 2011 Skype Expires: August 6, 2011 Skype
G. Camarillo G. Camarillo
Ericsson Ericsson
F. Audet F. Audet
Skype Skype
January 19, 2011 February 2, 2011
Best Current Practices for NAT Traversal for Client-Server SIP Best Current Practices for NAT Traversal for Client-Server SIP
draft-ietf-sipping-nat-scenarios-14 draft-ietf-sipping-nat-scenarios-15
Abstract Abstract
Traversal of the Session Initiation Protocol (SIP) and the sessions Traversal of the Session Initiation Protocol (SIP) and the sessions
it establishes through Network Address Translators (NATs) is a it establishes through Network Address Translators (NATs) is a
complex problem. Currently there are many deployment scenarios and complex problem. Currently there are many deployment scenarios and
traversal mechanisms for media traffic. This document provides traversal mechanisms for media traffic. This document provides
concrete recommendations and a unified method for NAT traversal as concrete recommendations and a unified method for NAT traversal as
well as documenting corresponding flows. well as documenting corresponding flows.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 July 23, 2011. This Internet-Draft will expire on August 6, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 3, line 24 skipping to change at page 3, line 24
Unicast UDP' [RFC4787]. Unicast UDP' [RFC4787].
The IETF has been active on many specifications for the traversal of The IETF has been active on many specifications for the traversal of
NATs, including STUN[RFC5389], ICE[RFC5245], symmetric NATs, including STUN[RFC5389], ICE[RFC5245], symmetric
response[RFC3581], symmetric RTP[RFC4961], TURN[RFC5766], SIP response[RFC3581], symmetric RTP[RFC4961], TURN[RFC5766], SIP
Outbound[RFC5626], SDP attribute for RTCP[RFC3605], Multiplexing RTP Outbound[RFC5626], SDP attribute for RTCP[RFC3605], Multiplexing RTP
Data and Control Packets on a Single Port[RFC5761] and others. These Data and Control Packets on a Single Port[RFC5761] and others. These
each represent a part of the solution, but none of them gives the each represent a part of the solution, but none of them gives the
overall context for how the NATs traversal problem is decomposed and overall context for how the NATs traversal problem is decomposed and
solved through this collection of specifications. This document solved through this collection of specifications. This document
serves to meet that need. serves to meet that need. It should be noted that this document
intentionally does not invoke Best Common Practice machinery as
defined in RFC 2026 [RFC2026].
The draft is split into two distinct sections as follows: The draft is split into two distinct sections as follows:
o Section 4 provides a definitive set of 'Best Common Practices' to o Section 4 provides a definitive set of 'Best Common Practices' to
demonstrate the traversal of SIP and its associated media through demonstrate the traversal of SIP and its associated media through
NAT devices. NAT devices.
o Section 5 provides non-normative examples representing o Section 5 provides non-normative examples representing
interactions of SIP using various NAT type deployments. interactions of SIP using various NAT type deployments.
skipping to change at page 65, line 44 skipping to change at page 65, line 44
Interactions for Signaling Protocol Communication along Interactions for Signaling Protocol Communication along
the Media Path", the Media Path",
draft-ietf-mmusic-media-path-middleboxes-03 (work in draft-ietf-mmusic-media-path-middleboxes-03 (work in
progress), July 2010. progress), July 2010.
[I-D.ietf-sipping-v6-transition] [I-D.ietf-sipping-v6-transition]
Camarillo, G., "IPv6 Transition in the Session Initiation Camarillo, G., "IPv6 Transition in the Session Initiation
Protocol (SIP)", draft-ietf-sipping-v6-transition-07 (work Protocol (SIP)", draft-ietf-sipping-v6-transition-07 (work
in progress), August 2007. in progress), August 2007.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996.
[RFC3424] Daigle, L. and IAB, "IAB Considerations for UNilateral [RFC3424] Daigle, L. and IAB, "IAB Considerations for UNilateral
Self-Address Fixing (UNSAF) Across Network Address Self-Address Fixing (UNSAF) Across Network Address
Translation", RFC 3424, November 2002. Translation", RFC 3424, November 2002.
[RFC5780] MacDonald, D. and B. Lowekamp, "NAT Behavior Discovery [RFC5780] MacDonald, D. and B. Lowekamp, "NAT Behavior Discovery
Using Session Traversal Utilities for NAT (STUN)", Using Session Traversal Utilities for NAT (STUN)",
RFC 5780, May 2010. RFC 5780, May 2010.
[RFC5853] Hautakorpi, J., Camarillo, G., Penfield, R., Hawrylyshen, [RFC5853] Hautakorpi, J., Camarillo, G., Penfield, R., Hawrylyshen,
A., and M. Bhatia, "Requirements from Session Initiation A., and M. Bhatia, "Requirements from Session Initiation
 End of changes. 6 change blocks. 
6 lines changed or deleted 11 lines changed or added

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