Re: draft-manning-dnssvr-criteria-01.txt

Randy Bush <randy@psg.com> Sun, 05 May 1996 17:25 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14514; 5 May 96 13:25 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14509; 5 May 96 13:25 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09866; 5 May 96 13:25 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14490; 5 May 96 13:24 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14439; 5 May 96 13:22 EDT
Received: from rip.psg.com by CNRI.Reston.VA.US id aa09835; 5 May 96 13:22 EDT
Received: by rip.psg.com (Smail3.1.29.1 #1) id m0uG7VM-00083RC; Sun, 5 May 96 10:21 PDT
Message-Id: <m0uG7VM-00083RC@rip.psg.com>
Date: Sun, 05 May 1996 10:21:00 -0700
X-Orig-Sender: ietf-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Randy Bush <randy@psg.com>
To: John Curran <jcurran@bbnplanet.com>
Cc: John C Klensin <klensin@mail1.reston.mci.net>, ietf <ietf@CNRI.Reston.VA.US>
Subject: Re: draft-manning-dnssvr-criteria-01.txt
References: <v02130507adb2813ecbf0@[192.52.71.147]>
Source-Info: From (or Sender) name not authenticated.

> prevent publication as an informational RFC because some random soul might
> misconstrue the categorizing is unreasonable.

We can not prevent it, ab definito. nor am I suggesting that we do so, nor
do I think we should be able to prevent it.  Ref much discussion of role of
RFC Editor.

But I do think we can request that its serious problems be addressed before
giving the implicit IETF stamp of approval.

> Unless the IETF has a working group underway working on the same topic,
> I'd advise against ad-hoc censorship of new informational RFCs.

Even if there were such a WG, I would strongly stand against any censorship,
ad-hoc or organized, of new informational RFCs.  Ref much discussion of role
of RFC Editor.

But, as no one is doing so, this herring has a pinkish tinge.

All that is happening is that folk are suggesting that some very serious
weaknesses in the draft be corrected before the IETF allows its tacit stamp
of approval to be placed on an informational RFC.  I would think that this
is not an unusual or egregious process.

randy