RFC 5128 on State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)
rfc-editor@rfc-editor.org Fri, 28 March 2008 21:12 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A763E28CA80; Fri, 28 Mar 2008 14:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.592
X-Spam-Level:
X-Spam-Status: No, score=-100.592 tagged_above=-999 required=5 tests=[AWL=-0.155, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GyQjk5H1KNqs; Fri, 28 Mar 2008 14:12:27 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 401FA28C9E2; Fri, 28 Mar 2008 14:11:21 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E5DA3A6AD8; Fri, 28 Mar 2008 14:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wypkeYotsixl; Fri, 28 Mar 2008 14:11:16 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 729DD28C3E2; Fri, 28 Mar 2008 14:10:43 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 04480121729; Fri, 28 Mar 2008 14:10:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5128 on State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)
From: rfc-editor@rfc-editor.org
Message-Id: <20080328211043.04480121729@bosco.isi.edu>
Date: Fri, 28 Mar 2008 14:10:43 -0700
Cc: behave@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5128
Title: State of Peer-to-Peer (P2P) Communication
across Network Address Translators (NATs)
Author: P. Srisuresh, B. Ford, D. Kegel
Status: Informational
Date: March 2008
Mailbox: srisuresh@yahoo.com,
baford@mit.edu,
dank06@kegel.com
Pages: 32
Characters: 81008
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-behave-p2p-state-06.txt
URL: http://www.rfc-editor.org/rfc/rfc5128.txt
This memo documents the various methods known to be in use by
applications to establish direct communication in the presence
of Network Address Translators (NATs) at the current time. Although
this memo is intended to be mainly descriptive, the Security
Considerations section makes some purely advisory recommendations
about how to deal with security vulnerabilities the applications
could inadvertently create when using the methods described. This
memo covers NAT traversal approaches used by both TCP- and UDP-based
applications. This memo is not an endorsement of the methods
described, but merely an attempt to capture them in a document.
This memo provides information for the Internet community.
This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce