idnits 2.16.02
/tmp/draft-ietf-nat-app-guide-07.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 3235
5 Title: Network Address Translator (NAT)-Friendly
6 Application Design Guidelines
7 Author(s): D. Senie
8 Status: Informational
9 Date: January 2002
10 Mailbox: dts@senie.com
11 Pages: 13
12 Characters: 29588
13 Updates/Obsoletes/SeeAlso: NONE
15 I-D Tag: draft-ietf-nat-app-guide-07.txt
17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3235.txt
19 This document discusses those things that application designers might
20 wish to consider when designing new protocols. While many common
21 Internet applications will operate cleanly in the presence of Network
22 Address Translators, others suffer from a variety of problems when
23 crossing these devices. Guidelines are presented herein to help
24 ensure new protocols and applications will, to the extent possible, be
25 compatible with NAT (Network Address Translation).
27 This document is a product of the Network Address Translators Working
28 Group of the IETF.
30 This memo provides information for the Internet community. It does
31 not specify an Internet standard of any kind. Distribution of this
32 memo is unlimited.
34 This announcement is sent to the IETF list and the RFC-DIST list.
35 Requests to be added to or deleted from the IETF distribution list
36 should be sent to IETF-REQUEST@IETF.ORG. Requests to be
37 added to or deleted from the RFC-DIST distribution list should
38 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
40 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
41 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
42 help: ways_to_get_rfcs. For example:
44 To: rfc-info@RFC-EDITOR.ORG
45 Subject: getting rfcs
47 help: ways_to_get_rfcs
49 Requests for special distribution should be addressed to either the
50 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
51 specifically noted otherwise on the RFC itself, all RFCs are for
52 unlimited distribution.echo
53 Submissions for Requests for Comments should be sent to
54 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
55 Authors, for further information.