Re: Going about requesting new TELOPT Options

Theodore Ts'o <tytso@mit.edu> Thu, 08 February 1996 22:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24051; 8 Feb 96 17:19 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa24047; 8 Feb 96 17:19 EST
Received: from timbuk.cray.com by CNRI.Reston.VA.US id aa13968; 8 Feb 96 17:19 EST
Received: from ironwood.cray.com (daemon@ironwood-fddi.cray.com [128.162.21.36]) by timbuk.cray.com (8.6.12/CRI-gate-8-2.11) with ESMTP id QAA00220; Thu, 8 Feb 1996 16:11:47 -0600
Received: (from daemon@localhost) by ironwood.cray.com (8.6.12/CRI-ccm_serv-8-2.8) id QAA08204 for telnet-ietf_list@sdiv; Thu, 8 Feb 1996 16:09:49 -0600
Received: from t2.cray.com (root@t2 [128.162.19.5]) by ironwood.cray.com (8.6.12/CRI-ccm_serv-8-2.8) with ESMTP id QAA08198 for <telnet-ietf@ironwood.cray.com>; Thu, 8 Feb 1996 16:09:48 -0600
Received: from timbuk.cray.com (root@timbuk.cray.com [128.162.19.7]) by t2.cray.com (8.6.12/craymail-smart) with ESMTP id QAA06072 for <telnet-ietf@cray.com>; Thu, 8 Feb 1996 16:09:47 -0600
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by timbuk.cray.com (8.6.12/CRI-gate-8-2.11) with SMTP id QAA29966 for <telnet-ietf@cray.com>; Thu, 8 Feb 1996 16:09:46 -0600
Received: from DCL.MIT.EDU by MIT.EDU with SMTP id AA01705; Thu, 8 Feb 96 17:09:23 EST
Received: by dcl.MIT.EDU (5.0/4.7) id AA28351; Thu, 8 Feb 1996 17:09:45 -0500
Date: Thu, 8 Feb 1996 17:09:45 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Theodore Ts'o <tytso@mit.edu>
Message-Id: <9602082209.AA28351@dcl.MIT.EDU>
To: Joe Croft <jcroft@unicomp.net>
Cc: telnet-ietf@cray.com
In-Reply-To: Joe Croft's message of Tue, 6 Feb 1996 12:04:02 -0600 (CST), <Pine.LNX.3.91.960206115701.552A-100000@croftj.reliance.com>
Subject: Re: Going about requesting new TELOPT Options
Address: 1 Amherst St., Cambridge, MA 02139
Phone: (617) 253-8091
Content-Length: 1053

   Date: Tue, 6 Feb 1996 12:04:02 -0600 (CST)
   From: Joe Croft <jcroft@unicomp.net>

   this, I found the need for 3 new options, at this time, I'm using unused 
   TELOPT equates, but I'm sure that this will bite me sooner or later as 
   Yall come up w/ new options. 

    What I would like to know is, How do I propose these new options to Yall 
   to take them into consideration to be added to the standard? 

Sending mail to this list for discussion is a general good step.
There's a specific procedure for elevating new IETF standards; if you
are interested in the mechanics of such a scheme, I can send you a list
of good starting points as far as documents describing the
standardization process.

However, usually the first thing to do is to ask other technical experts
to take a look at the proposed new options and make sure that there
isn't another, already existing, standard method of trying to accomplish
what you are trying to do.  This mailing list is probably a good a
mailing list as any for that purpose.

Good luck!

						- Ted