Re: Publishing the Tao as a web page

John C Klensin <> Fri, 15 June 2012 18:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 149A421F84AC for <>; Fri, 15 Jun 2012 11:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fFtaKzlKwVcA for <>; Fri, 15 Jun 2012 11:17:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7C84B21F8484 for <>; Fri, 15 Jun 2012 11:17:28 -0700 (PDT)
Received: from [] ( by with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <>) id 1Sfaz5-000NjR-91; Fri, 15 Jun 2012 14:10:59 -0400
Date: Fri, 15 Jun 2012 14:17:20 -0400
From: John C Klensin <>
To: Paul Hoffman <>, IETF discussion list <>
Subject: Re: Publishing the Tao as a web page
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Jun 2012 18:17:29 -0000

--On Wednesday, June 13, 2012 13:44 -0700 Paul Hoffman
<> wrote:

>> but I can see the advantages if
>> others disagree.  On the other hand, publishing
>> draft-hoffman-tao4677bis in the RFC series seems to me to have
>> no value at all.  There should be an RFC 4677bis but it should
>> probably say little more than "Tao is now a web page at ....
>> and it is not being maintained in the RFC Series".
> That's the purpose of this document.


Having taken a quick look at -02 in the above context, let me
make an observation and small procedural suggestion:

The information in this I-D is exactly what the title and
abstract suggest (A Good Thing), namely an explanation of the
change from RFC publication and the new procedure.  But that
sets a bit of a trap because, if the procedural model changes
--as it inevitably will over time-- the RFC will need to be

So, I suggest that, after sufficient agreement on this document
and procedure are reached, you take the bulk of this document
and simply make it an appendix to the Tao.  Since the IESG has
to approve any changes to the Tao anyway, no control is lost,
but we avoid having to obsolete 4677bis, a document whose
purpose was the get the Tao out of the RFC Series.  Then we
produce a very short and focused 4677bis for the RFC Series that
says as little more than "out of the RFC Series, 4677 is
obsolete, doc is located at stable URI ..."