Network Address Translation (NAT) Behavioral Requirements Updates
draft-ietf-tsvwg-behave-requirements-update-07

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2016-02-23 (latest revision 2016-02-16)
Replaces draft-penno-behave-rfc4787-5382-5508-bis, draft-ietf-behave-requirements-update
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd David Black
Shepherd write-up Show (last changed 2016-01-27)
IESG IESG state IESG Evaluation
Consensus Boilerplate Unknown
Telechat date
Needs a YES. Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Spencer Dawkins
Send notices to "David L. Black" <david.black@emc.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
TSVWG                                                           R. Penno
Internet-Draft                                                     Cisco
Updates: 4787, 5382, 5508  (if approved)                    S. Perreault
Intended status: Best Current Practice               Jive Communications
Expires: August 19, 2016                               M. Boucadair, Ed.
                                                                  Orange
                                                            S. Sivakumar
                                                                   Cisco
                                                                K. Naito
                                                                     NTT
                                                       February 16, 2016

   Network Address Translation (NAT) Behavioral Requirements Updates
             draft-ietf-tsvwg-behave-requirements-update-07

Abstract

   This document clarifies and updates several requirements of RFC4787,
   RFC5382, and RFC5508 based on operational and development experience.
   The focus of this document is NAT44.

   This document updates RFCs 4787, 5382, and 5508.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 19, 2016.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Penno, et al.            Expires August 19, 2016                [Page 1]
Internet-Draft draft-ietf-tsvwg-behave-requirements-update February 2016

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  TCP Session Tracking  . . . . . . . . . . . . . . . . . . . .   3
     2.1.  TCP Transitory Connection Idle-Timeout  . . . . . . . . .   5
     2.2.  TCP RST . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Port Overlapping Behavior . . . . . . . . . . . . . . . . . .   5
   4.  Address Pooling Paired (APP)  . . . . . . . . . . . . . . . .   6
   5.  Endpoint-Independent Mapping (EIM) Protocol Independence  . .   7
   6.  Endpoint-Independent Filtering (EIF) Protocol Independence  .   7
   7.  Endpoint-Independent Filtering (EIF) Mapping Refresh  . . . .   7
     7.1.  Outbound Mapping Refresh and Error Packets  . . . . . . .   8
   8.  Port Parity . . . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Port Randomization  . . . . . . . . . . . . . . . . . . . . .   8
   10. IP Identification (IP ID) . . . . . . . . . . . . . . . . . .   9
   11. ICMP Query Mappings Timeout . . . . . . . . . . . . . . . . .   9
   12. Hairpinning Support for ICMP Packets  . . . . . . . . . . . .   9
   13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   14. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   15. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     15.1.  Normative References . . . . . . . . . . . . . . . . . .  11
Show full document text