idnits 2.17.1 draft-ietf-sip-symmetric-response-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3581 5 Title: An Extension to the Session Initiation Protocol 6 (SIP) for Symmetric Response Routing 7 Author(s): J. Rosenberg, H. Schulzrinne 8 Status: Standards Track 9 Date: August 2003 10 Mailbox: jdrosen@dynamicsoft.com, 11 schulzrinne@cs.columbia.edu 12 Pages: 13 13 Characters: 66133 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-sip-symmetric-response-01.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3581.txt 20 The Session Initiation Protocol (SIP) operates over UDP and TCP, among 21 others. When used with UDP, responses to requests are returned to the 22 source address the request came from, and to the port written into the 23 topmost Via header field value of the request. This behavior is not 24 desirable in many cases, most notably, when the client is behind a 25 Network Address Translator (NAT). This extension defines a new 26 parameter for the Via header field, called "rport", that allows a 27 client to request that the server send the response back to the 28 source IP address and port from which the request originated. 30 This document is a product of the Session Initiation Protocol Working 31 Group of the IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.