[tcpm] IANA TCP options registry

Fernando Gont <fernando@gont.com.ar> Fri, 05 March 2010 21:53 UTC

Return-Path: <fernando@gont.com.ar>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8003C28C374 for <tcpm@core3.amsl.com>; Fri, 5 Mar 2010 13:53:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level:
X-Spam-Status: No, score=-3.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J88y-DOe6rtJ for <tcpm@core3.amsl.com>; Fri, 5 Mar 2010 13:53:33 -0800 (PST)
Received: from smtp1.xmundo.net (smtp1.xmundo.net [201.216.232.80]) by core3.amsl.com (Postfix) with ESMTP id 8936628C368 for <tcpm@ietf.org>; Fri, 5 Mar 2010 13:53:32 -0800 (PST)
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56]) by smtp1.xmundo.net (Postfix) with ESMTP id 2B0076B6773; Fri, 5 Mar 2010 18:53:38 -0300 (ART)
Received: from [192.168.0.100] (129-130-17-190.fibertel.com.ar [190.17.130.129]) (authenticated bits=0) by venus.xmundo.net (8.13.8/8.13.8) with ESMTP id o25LrU6m010425; Fri, 5 Mar 2010 18:53:31 -0300
Message-ID: <4B917D5B.3060804@gont.com.ar>
Date: Fri, 05 Mar 2010 18:53:31 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "tcpm@ietf.org" <tcpm@ietf.org>
X-Enigmail-Version: 0.96.0
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (venus.xmundo.net [201.216.232.56]); Fri, 05 Mar 2010 18:53:37 -0300 (ART)
Cc: "tcpm-chairs@tools.ietf.org" <tcpm-chairs@tools.ietf.org>, Alfred Hönes <ah@tr-sys.de>, Joe Touch <touch@ISI.EDU>
Subject: [tcpm] IANA TCP options registry
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2010 21:53:34 -0000

(note: this post has nothing to do with the recent poll on whether the
TCP MD5 option should be obsoleted)

Folks,

The IANA TCP options registry
(http://www.iana.org/assignments/tcp-parameters/) lacks of valuable
information. e.g., you need to figure out by yourself what the "Bubba"
option is (or what it is used for), and missing references (e.g., for
options #20 through #23 are missing).

Al this was particularly painful when working on the CPNI TCP security
document. I ended up using an unofficial revised registry posted by
Alfred (http://www.ietf.org/mail-archive/web/tcpm/current/msg03199.html)
which is, IMO, far better than the current IANA registry.

What'd be the procedure to have Alfred's registry replace the current
one? (i.e., have most/all of the information there make it into the
"official" IANA registry).

Thanks!

Kind regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1