[31053] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: bring sense to the ietf - volunteer for nomcom

daemon@ATHENA.MIT.EDU (Michael Shields)
Thu Sep 7 17:32:46 2000

To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: Randy Bush <randy@psg.com>, Yakov Rekhter <yakov@cisco.com>,
	nanog@merit.edu
From: Michael Shields <shields@msrl.com>
Date: 07 Sep 2000 21:29:49 +0000
In-Reply-To: Masataka Ohta's message of "Thu, 7 Sep 2000 22:54:22 +0859 ()"
Message-ID: <87k8cnx54i.fsf@challah.msrl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Errors-To: owner-nanog-outgoing@merit.edu


In article <200009071354.WAA27086@necom830.hpcl.titech.ac.jp>,
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:
> Note that BCP9, RFC2026, says:
> 
>    publication for comments before proceeding further.  The RFC Editor
>    is expected to exercise his or her judgment concerning the editorial
>    suitability of a document for publication with Experimental or
>    Informational status, and may refuse to publish a document which, in
>    the expert opinion of the RFC Editor, is unrelated to Internet
>                                             ^^^^^^^^^^^^^^^^^^^^^
>    activity or falls below the technical and/or editorial standard for
>    ^^^^^^^^
>    RFCs.
> 
> I should accept a fact that Jon Postel is really dead.

Yes, the RFC Editor "may refuse".  From BCP 14 / RFC 2119: "This word,
or the adjective OPTIONAL, mean that an item is truly optional."
-- 
Shields.


home help back first fref pref prev next nref lref last post