A TCP Authentication Option NAT Extension
draft-touch-tcp-ao-nat-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-05-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
IETF conflict review conflict-review-touch-tcp-ao-nat
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
RFC Editor RFC Editor state ISR
TCPM WG                                                        J. Touch
Internet Draft                                                  USC/ISI
Intended status: Experimental                              May 30, 2012
Expires: November 2012

                 A TCP Authentication Option NAT Extension
                       draft-touch-tcp-ao-nat-03.txt

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on November 30, 2012.

Copyright Notice

   Copyright (c) 2012 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
   (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.

Touch                 Expires November 30, 2012                [Page 1]
Internet-Draft           TCP-AO NAT Extension                  May 2012

Abstract

   This document describes an extension to the TCP Authentication
   Option (TCP-AO) to support its use over connections that pass
   through network address and/or port translators (NATs/NAPTs). This
   extension changes the data used to compute traffic keys, but does
   not alter TCP-AO's packet processing or key generation algorithms.

Table of Contents

   1. Introduction...................................................2
   2. Conventions used in this document..............................2
   3. Background.....................................................3
   4. Extension to Allow NAT Use.....................................3
   5. Intended Use...................................................4
   6. Security Considerations........................................4
   7. IANA Considerations............................................5
   8. References.....................................................5
      8.1. Normative References......................................5
      8.2. Informative References....................................5
   9. Acknowledgments................................................5

1. Introduction

   This document describes an extension to the TCP Authentication
   Option (TCP-AO) [RFC5925] to support its use in the presence of
   network address and/or port translators (NAT/NAPT) [RFC2663]. These
   devices translate the source address and/or the source port number
   of a TCP connection. TCP-AO without these extensions would be
   sensitive to these modifications, and would discard authenticated
   segments.

   At least one potential application of this extension is to support
   the experimental multipath TCP protocol [Fo11], which uses multiple
   IP addresses to support a single TCP transfer.

   This document assumes detailed familiarity with TCP-AO [RFC5925]. As
   a preview, this document focuses on how TCP-AO generates traffic
   keys, and does not otherwise alter the TCP-AO mechanism or that of
   its key generation [RFC5926].

2. Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC-2119 [RFC2119].

Touch                 Expires November 30, 2012                [Page 2]
Internet-Draft           TCP-AO NAT Extension                  May 2012

   When used in lower case, these words have their conventional meaning
   and do not convey the interpretations in RFC-2119.

3. Background

   TCP-AO generates traffic keys that are specific to a socket pair
   [RFC5925]. Using the TCP-AO convention (local = source for outgoing
   segments, destination for incoming segments), the following
   information is used to create a connection's traffic keys:

   o  IP local address

   o  IP remote address

   o  TCP local port

   o  TCP remote port
Show full document text