Re: [tcpm] IANA TCP options registry

Joe Touch <touch@ISI.EDU> Fri, 05 March 2010 22:14 UTC

Return-Path: <touch@ISI.EDU>
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 1FA1328C38D for <tcpm@core3.amsl.com>; Fri, 5 Mar 2010 14:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 zXLJXXIFFszz for <tcpm@core3.amsl.com>; Fri, 5 Mar 2010 14:14:02 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id BFC5428B23E for <tcpm@ietf.org>; Fri, 5 Mar 2010 14:14:02 -0800 (PST)
Received: from [75.215.248.70] (70.sub-75-215-248.myvzw.com [75.215.248.70]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id o25MCFHG024842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 5 Mar 2010 14:12:17 -0800 (PST)
Message-ID: <4B9181BE.3050908@isi.edu>
Date: Fri, 05 Mar 2010 14:12:14 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
References: <4B917D5B.3060804@gont.com.ar>
In-Reply-To: <4B917D5B.3060804@gont.com.ar>
X-Enigmail-Version: 0.96.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enigBC6A922F05AFA2A7F03B54CA"
X-MailScanner-ID: o25MCFHG024842
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tcpm-chairs@tools.ietf.org" <tcpm-chairs@tools.ietf.org>, Alfred Hönes <ah@tr-sys.de>, "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [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 22:14:04 -0000

Hi, Fernando,

Fernando Gont wrote:
> (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).

Some of that information might be solicited found elsewhere, e.g.,
internet-history@postel.org ;-)

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

Ask IANA (iana@iana.org). I don't think this really requires any
particular policy stuff - some of that info isn't there because it just
wasn't known when the page was created.

Joe