Shared Use of Experimental TCP Options
draft-ietf-tcpm-experimental-options-02

The information below is for an old version of the document
Document Type Active Internet-Draft (tcpm WG)
Last updated 2012-11-08 (latest revision 2012-10-05)
Replaces draft-touch-tcpm-experimental-options
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state AD Evaluation
Telechat date
Responsible AD Wesley Eddy
IESG note Michael Scharf (michael.scharf@alcatel-lucent.com) is the document shepherd.
Send notices to tcpm-chairs@tools.ietf.org, draft-ietf-tcpm-experimental-options@tools.ietf.org
TCPM Working Group                                             J. Touch
Internet Draft                                                 USC/ISI
Intended status: Proposed Standard                      October 5, 2012
Expires: April 2013

                  Shared Use of Experimental TCP Options
                draft-ietf-tcpm-experimental-options-02.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 April 5, 2013.

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

Touch                   Expires April 5, 2013                  [Page 1]
Internet-Draft  Shared Use of Experimental TCP Options     October 2012

   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.

Abstract

   This document describes how TCP option codepoints can support
   concurrent experiments using a magic number field. This mechanism
   avoids the need for a coordinated registry, and is backward-
   compatible with currently known uses. It is recommended for all new
   experimental RFCs that require TCP option codepoints.

Table of Contents

   1. Introduction...................................................2
   2. Conventions used in this document..............................3
   3. TCP Experimental Option Structure..............................4
      3.1. Reducing the Impact of False Positives....................6
      3.2. Migration to Assigned Options.............................6
   4. Security Considerations........................................7
   5. IANA Considerations............................................7
   6. References.....................................................7
      6.1. Normative References......................................7
      6.2. Informative References....................................7
   7. Acknowledgments................................................8

1. Introduction

   TCP includes options to enable new protocol capabilities that can be
   activated only where needed and supported [RFC793]. The space for
   identifying such options is small - 256 values, of which 30 are
   assigned at the time this document was published [IANA]. Two of
   these codepoints are allocated to support experiments (253, 254)
   [RFC4727]. These numbers are intended for testing purposes, and
   implementations need to assume they can be used for other purposes,
   but this is often not the case.

   There is no mechanism to support shared use of the experimental
   option codepoints. Experimental options 253 and 254 are deployed in
   operational code to support an early version of TCP authentication.
   Option 253 is also documented for the experimental TCP Cookie
   Transaction option [RFC6013]. This shared use results in collisions
   in which a single codepoint can appear multiple times in a single
   TCP segment and each use is ambiguous.

Touch, (TBD)            Expires April 5, 2013                  [Page 2]
Internet-Draft  Shared Use of Experimental TCP Options     October 2012

   Other codepoints have been used without assignment, notably 31-32
   (TCP cookie transactions, as originally distributed and in its API
   doc) and 76-78 (tcpcrypt) [Bi11][Si11]. Commercial products
   reportedly also use unassigned options 33, 69-70, and 76-78 as well.
   Even though these uses are unauthorized, they can impact legitimate
   assignees.

   There are a variety of proposed approaches to address this issue.
Show full document text