Re: [tcpm] IANA TCP options registry
Christian Huitema <huitema@microsoft.com> Sat, 06 March 2010 01:12 UTC
Return-Path: <huitema@microsoft.com>
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 0E6C93A7870 for <tcpm@core3.amsl.com>; Fri, 5 Mar 2010 17:12:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 PqrqivvyzbKN for <tcpm@core3.amsl.com>; Fri, 5 Mar 2010 17:12:05 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 76DFC3A905B for <tcpm@ietf.org>; Fri, 5 Mar 2010 17:12:04 -0800 (PST)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 5 Mar 2010 17:12:07 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.0.639.21; Fri, 5 Mar 2010 17:11:48 -0800
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.84]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Fri, 5 Mar 2010 17:11:49 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fernando@gont.com.ar>, Joe Touch <touch@ISI.EDU>
Thread-Topic: [tcpm] IANA TCP options registry
Thread-Index: AQHKvK5fOZjK3jmy1kaQ625kwWKmnJHkbpEAgAAK9gD//5/3EA==
Date: Sat, 06 Mar 2010 01:11:46 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA685E80A4@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <4B917D5B.3060804@gont.com.ar> <4B9181BE.3050908@isi.edu> <4B918AF0.5090605@gont.com.ar>
In-Reply-To: <4B918AF0.5090605@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sat, 06 Mar 2010 01:12:09 -0000
The bubba and skeeter options were reserved by Stev Knowles, then working at FTP Software. The options are parts of an encryption system. The documentation for that system was not made publicly available. According to Stev, the options were actually deployed and used, certainly until 2000, and possibly later. -----Original Message----- From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On Behalf Of Fernando Gont Sent: Friday, March 05, 2010 2:51 PM To: Joe Touch Cc: tcpm-chairs@tools.ietf.org; Alfred Hönes; tcpm@ietf.org Subject: Re: [tcpm] IANA TCP options registry Hi, Joe, >> 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 ;-) Yes, but other than that, one should be able to know if the option was ever deployed, whether it's obsolete, etc. e.g., if I wanted to design a firewall policy, I might need that information. >> 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. Ok. I've just e-mailed them. Let's see what happens. 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 _______________________________________________ tcpm mailing list tcpm@ietf.org https://www.ietf.org/mailman/listinfo/tcpm
- [tcpm] IANA TCP options registry Fernando Gont
- Re: [tcpm] IANA TCP options registry Joe Touch
- Re: [tcpm] IANA TCP options registry Fernando Gont
- Re: [tcpm] IANA TCP options registry Christian Huitema
- Re: [tcpm] IANA TCP options registry Lars Eggert
- Re: [tcpm] IANA TCP options registry Joe Touch
- Re: [tcpm] IANA TCP options registry Fernando Gont
- Re: [tcpm] IANA TCP options registry Joe Touch
- Re: [tcpm] IANA TCP options registry Fernando Gont
- Re: [tcpm] IANA TCP options registry Joe Touch
- Re: [tcpm] IANA TCP options registry Fernando Gont
- Re: [tcpm] IANA TCP options registry Joe Touch
- Re: [tcpm] IANA TCP options registry Fernando Gont