[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Request to advance rfc4214(bis) to standards-track through ADsponsorship
- To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
- Subject: RE: Request to advance rfc4214(bis) to standards-track through ADsponsorship
- From: Pekka Savola <pekkas@netcore.fi>
- Date: Fri, 30 Mar 2007 07:54:33 +0300 (EEST)
- Cc: Mark Townsley <townsley@cisco.com>, Ron Bonica <rbonica@juniper.net>, dromasca@avaya.com, Jari Arkko <jari.arkko@piuha.net>, Lindqvist Erik Kurt <kurtis@kurtis.pp.se>, Fred Baker <fred@cisco.com>, David Ward <dward@cisco.com>, "Durand, Alain" <Alain_Durand@cable.comcast.com>, Bob Hinden <bob.hinden@nokia.com>, brian@innovationslab.net, tgleeson@cisco.com, dthaler@microsoft.com, mohitt@microsoft.com, v6ops@ops.ietf.org
- In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A101774853@XCH-NW-7V2.nw.nos.boeing.com>
- References: <69BD6B46-47FD-4E13-93E1-6CBB6C57F5C5@cisco.com> <EF2F0EC839870F43A6637360BC12ABD4018E3765@PACDCEXCMB05.cable.comcast.com> <39C363776A4E8C4A94691D2BD9D1C9A10177484C@XCH-NW-7V2.nw.nos.boeing.com> <460BFB6D.2000309@juniper.net> <39C363776A4E8C4A94691D2BD9D1C9A101774850@XCH-NW-7V2.nw.nos.boeing.com> <460C0215.7050002@cisco.com> <39C363776A4E8C4A94691D2BD9D1C9A101774853@XCH-NW-7V2.nw.nos.boeing.com>
On Thu, 29 Mar 2007, Templin, Fred L wrote:
If Mark is also busy we could ask the other ADs, but I
suppose another option would be to just put it as an
independent submission to the RFC editor?
That's always an option.
Process question - is it possible to publish as standards-track
through independent submission to the RFC editor, or is that
method only good for Informational/Experimental? (Please cite
references if possible.)
No. RFC editor cannot publish standards track RFCs, those must come
from the IETF (either from a WG or through an AD).
From http://www.rfc-editor.org/indsubs.html :
"Independent submissions are submitted directly to the RFC Editor as
Internet Drafts. Once such a Draft has been published, the author
should then email its file name to rfc-editor@rfc-editor.org,
requesting that the independent submission be considered for
publication as an RFC in the Informational or Experimental category
(please specify)."
FWIW I personally haven't seen sufficient justification (e.g., the
amount and the kind of deployments; the number of implementations that
currently ship ISATAP as specified by the RFC; the amount of required
revisions to the specification) to move ISATAP to the standards track.
Even if there was a high-level decision to do so, the process should
take a number of months at the very least to ensure proper review has
been done.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings