State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)
draft-ietf-behave-p2p-state-06

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    behave mailing list <behave@ietf.org>, 
    behave chair <behave-chairs@tools.ietf.org>
Subject: Document Action: 'State of Peer-to-Peer(P2P) 
         Communication Across Network Address Translators(NATs)' to 
         Informational RFC 

The IESG has approved the following document:

- 'State of Peer-to-Peer(P2P) Communication Across Network Address 
   Translators(NATs) '
   <draft-ietf-behave-p2p-state-07.txt> as an Informational RFC

This document is the product of the Behavior Engineering for Hindrance 
Avoidance Working Group. 

The IESG contact persons are Magnus Westerlund and Lars Eggert.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-p2p-state-07.txt

Ballot Text

Technical Summary

This memo documents the various methods known to be in use by
applications to establish direct UDP or TCP communication in the
presence of Network Address Translators (NATs).


Working Group Summary

Agreeing on RFC3489 terminology (which is well known) versus
RFC4787 terminology (which is more accurate but longer) involved some
controversy. Consensus was to use RFC4787 terminology.


Document Quality

This document have had descent review in the WG. The techniques in this
document are implemented in various software that traverses NATs. 

Personnel

Document shepherd: Dan Wing, dwing@cisco.com
Responsible AD: Magnus Westerlund, magnus.westerlund@ericsson.com

Note to RFC Editor
 
Please update the reference to RFC 3041 to RFC 4941.

RFC Editor Note