Behavior Engineering for Hindrance Avoidance (behave)
-----------------------------------------------------

 Charter
 Last Modified: 2008-12-16

 Current Status: Active Working Group

 Chair(s):
     Dan Wing  <dwing@cisco.com>
     Dave Thaler  <dthaler@microsoft.com>

 Transport Area Director(s):
     Magnus Westerlund  <magnus.westerlund@ericsson.com>
     Lars Eggert  <lars.eggert@nokia.com>

 Transport Area Advisor:
     Magnus Westerlund  <magnus.westerlund@ericsson.com>

 Mailing Lists: 
     General Discussion:behave@ietf.org
     To Subscribe:      behave-request@ietf.org
         In Body:       In Body: subscribe
     Archive:           http://www.ietf.org/mail-archive/web/behave

Description of Working Group:

No description available


 Goals and Milestones:

   Done         Submit BCP that defines unicast UDP behavioral requirements for 
                NATs to IESG 

   Done         Submit a BCP that defines TCP behavioral requireents for NATs 
                to IESG 

   Done         Submit a BCP that defines ICMP behavioral requirements for NATs 
                to IESG 

   Done         Submit informational that discusses current NAT traversal 
                techniques used by applications 

   Done         Submit BCP that defines multicast UDP 

   Done         Submit revision of RFC 3489 to IESG behavioral requirements for 
                NATs to IESG 

   Done         Submit informational document for rfc3489bis test vectors 

   Done         Submit experimental document that describes how an application 
                can determine the type of NAT it is behind 

   Done         Submit BCP document for DCCP NAT behavior 

   Dec 2008       Submit BCP document for SCTP NAT behavior 

   Dec 2008       Submit standards-track relay protocol 

   Jan 2009       Determine relative prioritization of the four translation 
                cases. 

   Mar 2009       Submit standards-track document for relaying of a TCP 
                bytestream 

   Mar 2009       Submit standard-track document of an IPv6 relay protocol to 
                IESG 

   Mar 2009       Determine what solutions(s) and components are needed to solve 
                each of the four cases. Create new milestones for the 
                solution(s) and the components. 

   Sep 2009       Target for first solution to be submitted to IESG for 
                publication as standards track RFC. 


 Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Mar 2006 Jul 2009   <draft-ietf-behave-turn-16.txt>
                Traversal Using Relays around NAT (TURN): Relay Extensions to 
                Session Traversal Utilities for NAT (STUN) 

Feb 2007 Sep 2009   <draft-ietf-behave-nat-behavior-discovery-08.txt>
                NAT Behavior Discovery Using STUN 

Nov 2007 Jul 2009   <draft-ietf-behave-turn-tcp-04.txt>
                Traversal Using Relays around NAT (TURN) Extensions for TCP 
                Allocations 

Dec 2007 Nov 2008   <draft-ietf-behave-stun-test-vectors-04.txt>
                Test vectors for STUN 

Dec 2008 Aug 2009   <draft-ietf-behave-turn-uri-03.txt>
                Traversal Using Relays around NAT (TURN) Uniform Resource 
                Identifiers 

Jun 2009 Sep 2009   <draft-ietf-behave-v6v4-xlate-01.txt>
                IP/ICMP Translation Algorithm 

Jul 2009 Jul 2009   <draft-ietf-behave-dns64-00.txt>
                DNS64: DNS extensions for Network Address Translation from IPv6 
                Clients to IPv4 Servers 

Jul 2009 Jul 2009   <draft-ietf-behave-v6v4-xlate-stateful-01.txt>
                NAT64: Network Address and Protocol Translation from IPv6 
                Clients to IPv4 Servers 

Jul 2009 Sep 2009   <draft-ietf-behave-v6v4-framework-01.txt>
                Framework for IPv4/IPv6 Translation 

Aug 2009 Aug 2009   <draft-ietf-behave-address-format-00.txt>
                IPv6 Addressing of IPv4/IPv6 Translators 

 Request For Comments:

  RFC   Stat Published     Title
------- -- ----------- ------------------------------------
RFC4787BCP  Jan 2007    Network Address Translation (NAT) Behavioral 
                       Requirements for Unicast UDP 

RFC5135BCP  Feb 2008    IP Multicast Requirements for a Network Address 
                       Translator (NAT) and a Network Address Port Translator 
                       (NAPT) 

RFC5128 I    Mar 2008    State of Peer-to-Peer(P2P) Communication Across Network 
                       Address Translators(NATs) 

RFC5382BCP  Oct 2008    NAT Behavioral Requirements for TCP 

RFC5389 PS   Oct 2008    Session Traversal Utilities for NAT (STUN) 

RFC5508BCP  Apr 2009    NAT Behavioral Requirements for ICMP 

RFC5597BCP  Sep 2009    Network Address Translation (NAT) Behavioral 
                       Requirements for the Datagram Congestion Control 
                       Protocol