The TCP Service Number Option (SNO)
draft-touch-tcpm-sno-03

 
Document Type Active Internet-Draft (individual)
Last updated 2015-03-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

TCPM WG                                                        J. Touch
Internet Draft                                                  USC/ISI
Intended status: Experimental                             March 9, 2015
Expires: September 2015

                    The TCP Service Number Option (SNO)
                        draft-touch-tcpm-sno-03.txt

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79. This document may not be modified,
   and derivative works of it may not be created, except to publish it
   as an RFC and to translate it into languages other than English.

   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.

   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 September 9, 2015.

Touch                 Expires September 9, 2015                [Page 1]
Internet-Draft     TCP Service Number Option (SNO)           March 2015

Copyright Notice

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

Abstract

   This document specifies a TCP option for service numbers. The
   current SYN destination port is used both to indicate the desired
   service and as a connection demultiplexing field. This option
   separates those two functions, retaining the current destination
   port solely for demultiplexing and indicating the service separately
   in a service number option (SNO). By decoupling these two functions,
   SNO allows a larger number of concurrent connections for a single
   service, as might be useful between fixed addresses of proxies.

Table of Contents

   1. Introduction...................................................3
   2. Conventions used in this document..............................4
   3. Background.....................................................4
      3.1. IANA port numbers.........................................5
      3.2. DNS SRV records...........................................6
      3.3. RPC portmapper and RPCBIND................................7
      3.4. TCPMUX....................................................7
      3.5. Summary of alternatives and comparison to SNO.............8
   4. TCP Service Number Option......................................9
      4.1. Interaction between SNO and the TCP API..................11
         4.1.1. Active OPEN (Unix connect)..........................11
         4.1.2. Passive OPEN (Unix listen)..........................11
         4.1.3. Impact on the TCP OPEN API..........................11
      4.2. Error conditions.........................................12
      4.3. Backward compatibility...................................12
   5. Issues........................................................13
      5.1. Interaction with other protocols and features............13
      5.2. Potential use in other transport protocols...............14

Touch                 Expires September 9, 2015                [Page 2]
Show full document text