[tcpm] TCP options - tcp-parameters IANA registry

Alfred Hönes <ah@tr-sys.de> Wed, 14 November 2007 22:58 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsRBq-000085-J5; Wed, 14 Nov 2007 17:58:34 -0500
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1IsRBp-000079-1r for tcpm-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 17:58:33 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsRBo-000061-No for tcpm@ietf.org; Wed, 14 Nov 2007 17:58:32 -0500
Received: from dsl.tr-sys.de ([] helo=WOTAN.TR-Sys.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsRBj-0003sz-H3 for tcpm@ietf.org; Wed, 14 Nov 2007 17:58:32 -0500
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: $/16.3) id AA202281064; Wed, 14 Nov 2007 23:57:44 +0100
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id XAA13402; Wed, 14 Nov 2007 23:57:43 +0100 (MEZ)
From: Alfred Hönes <ah@tr-sys.de>
Message-Id: <200711142257.XAA13402@TR-Sys.de>
To: tcpm@ietf.org
Date: Wed, 14 Nov 2007 23:57:42 +0100
X-Mailer: ELM [$Revision: $]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="ELM1195081062-13327-0_"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8aa7cbc518894eb04182283f0682f662
Subject: [tcpm] TCP options - tcp-parameters IANA registry
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Errors-To: tcpm-bounces@ietf.org

Hello all,
there are currently several proposals for new TCP options.

It has turned out onerous to get an overview of the TCP options
defined in the past, because the IANA 'tcp-parameters' registry
had not seen any additions until recently, for more than a decade,
and has not been maintained as carefully as might be desirable,
and because there are some apparently very obscure entries.

I have perceived the desire to build a more sound foundation
for my understanding of the issues related with those old and
proposed TCP options.  To this end, I have tried to perform a
survey of the non-RFC IANA-registered TCP options, by sending
out a questionnary to personal registrants last January, and I
have tried to collect and condense information contained in RFCs,
and from the distributed wisdom of the net.

I'd like to acknowledge the efforts of those individuals who have
assisted my attempts to get in contact with the owners of legacy
registrations, and who have taken the time to fill in the
questionnary and to supply additional information.

Due to lack of spare time and a rather small rate of feedback
I eventually arrived at for the survey, it took me until now to
prepare an updated, corrected, amended, and annotated version of
the latest IANA 'tcp-parameters' file.

I hope that sharing this information with the list will help to

o   complete the information, and

o   serve as a solid base of additional information for ongoing
    and starting discussions on various issues related to
    (existing and) newly proposed TCP options.

Furthermore, I'm interested to hear whether it might make sense
to start an 'authorized' effort to improve and update the
'tcp-parameters' IANA registry, incorporating some of the
changes I have performed on my local copy.

Currently, an update to the IANA Considerations for the 'protocols'
registry is submitted (from within and) to the IESG for publication
as an RFC, and a similar effort is being discussed for the
'port-numbers' registry as well.
This therefore might be a good opportunity for a cleanup of the
'tcp-parameters' registry as well, closing the gaps and facelifting
the file.

I have enclosed as an attachment my current working copy of that
registry file, including `==>` tagged lines pointing to specific
solicitations for additional information.
For informational purposes, I have also left therein a few traces
of the history of the file, as recovered from local backup media.

Please send comments to the list or in private communication,
as deemed useful.
I will honor requests for non-disclosure of information sources
and/or details received in personal communication, and will try
to update the working copy based on feedback received, in a neutral
and abstract way -- following the style you'll already find there

( see attached file: annotated_tcp-parameters.20070216 )

Kind regards,


| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |

tcpm mailing list