idnits 2.17.1 draft-iab-unsaf-considerations-02.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 3424 5 Title: IAB Considerations for UNilateral Self-Address 6 Fixing (UNSAF) Across Network Address Translation 7 Author(s): L. Daigle, Ed., IAB 8 Status: Informational 9 Date: November 2002 10 Mailbox: iab@iab.org 11 Pages: 9 12 Characters: 18165 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-iab-unsaf-considerations-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3424.txt 19 As a result of the nature of Network Address Translation (NAT) 20 Middleboxes, communicating endpoints that are separated by one or more 21 NATs do not know how to refer to themselves using addresses that are 22 valid in the addressing realms of their (current and future) peers. 23 Various proposals have been made for "UNilateral Self-Address Fixing 24 (UNSAF)" processes. These are processes whereby some originating 25 endpoint attempts to determine or fix the address (and port) by 26 which it is known to another endpoint - e.g. to be able to use 27 address data in the protocol exchange, or to advertise a public 28 address from which it will receive connections. 30 This document outlines the reasons for which these proposals can be 31 considered at best as short term fixes to specific problems and the 32 specific issues to be carefully evaluated before creating an UNSAF 33 proposal. 35 This document is a product of the Internet Architecture Board. 37 This memo provides information for the Internet community. It does 38 not specify an Internet standard of any kind. Distribution of this 39 memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.