BCP 142, RFC 5382 on NAT Behavioral Requirements for TCP
rfc-editor@rfc-editor.org Thu, 16 October 2008 22:07 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12AF33A68BE; Thu, 16 Oct 2008 15:07:18 -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 8D0E93A68BE; Thu, 16 Oct 2008 15:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.4
X-Spam-Level:
X-Spam-Status: No, score=-17.4 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 gT3gAhl6TZPZ; Thu, 16 Oct 2008 15:07:15 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id A79093A68AA; Thu, 16 Oct 2008 15:07:15 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 177D3168619; Thu, 16 Oct 2008 15:08:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 142, RFC 5382 on NAT Behavioral Requirements for TCP
From: rfc-editor@rfc-editor.org
Message-Id: <20081016220817.177D3168619@bosco.isi.edu>
Date: Thu, 16 Oct 2008 15:08:17 -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 announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf-announce>
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.
BCP 142
RFC 5382
Title: NAT Behavioral Requirements for TCP
Author: S. Guha, Ed.,
K. Biswas, B. Ford,
S. Sivakumar, P. Srisuresh
Status: Best Current Practice
Date: October 2008
Mailbox: saikat@cs.cornell.edu,
kbiswas@cisco.com,
baford@mpi-sws.org,
ssenthil@cisco.com,
srisuresh@yahoo.com
Pages: 31
Characters: 50306
See Also: BCP0142
I-D Tag: draft-ietf-behave-tcp-08.txt
URL: http://www.rfc-editor.org/rfc/rfc5382.txt
This document defines a set of requirements for NATs that handle TCP
that would allow many applications, such as peer-to-peer applications
and online games to work consistently. Developing NATs that meet
this set of requirements will greatly increase the likelihood that
these applications will function properly. This document specifies
an Internet Best Current Practices for the Internet Community,
and requests discussion and suggestions for improvements.
This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce