[31065] in North American Network Operators' Group
Re: bring sense to the ietf - volunteer for nomcom
daemon@ATHENA.MIT.EDU (Masataka Ohta)
Fri Sep 8 00:14:56 2000
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200009080356.MAA28836@necom830.hpcl.titech.ac.jp>
In-Reply-To: <87k8cnx54i.fsf@challah.msrl.com> from Michael Shields at "Sep 7,
2000 09:29:49 pm"
To: Michael Shields <shields@msrl.com>
Date: Fri, 8 Sep 2000 12:56:20 +0859 ()
Cc: Randy Bush <randy@psg.com>, Yakov Rekhter <yakov@cisco.com>,
nanog@merit.edu
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."
Yes, it may but can not. Jon could.
Masataka Ohta