Re: FW: Last Call: draft-heard-rfc4181-update (RFC 4181 Update to Recognize the IETF Trust) to BCP

"C. M. Heard" <heard@pobox.com> Sat, 27 January 2007 23:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAxMn-0000rF-Sr; Sat, 27 Jan 2007 18:53:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAxMl-0000r5-6F for ietf@ietf.org; Sat, 27 Jan 2007 18:53:51 -0500
Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAxMj-0007Kd-QQ for ietf@ietf.org; Sat, 27 Jan 2007 18:53:51 -0500
Received: (qmail 28973 invoked from network); 27 Jan 2007 15:53:44 -0800
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Jan 2007 15:53:44 -0800
Date: Sat, 27 Jan 2007 15:53:43 -0800
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: ietf@ietf.org
In-Reply-To: <45BBAF5A.5BC0@xyzzy.claranet.de>
Message-ID: <Pine.LNX.4.64.0701271522400.5025@shell4.bayarea.net>
References: <Pine.LNX.4.64.0701261712340.9792@shell4.bayarea.net> <45BBAF5A.5BC0@xyzzy.claranet.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: Re: FW: Last Call: draft-heard-rfc4181-update (RFC 4181 Update to Recognize the IETF Trust) to BCP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Sat, 27 Jan 2007, Frank Ellermann wrote:
> C. M. Heard wrote:
>> The draft is intended to do the same thing for RFC 4181
>> that RFC 4748 did for RFC 3978.  Comments, if any, should
>> be directed to <ietf@ietf.org>.
>
> Now that you ask, your patches are straight forward, so why
> not simply apply them and publish a complete new 4181bis ?
>
> Patchwork RFCs are IMO ugly.  RFC 4748 was a special case,
> it was urgent, there was a competing 3978bis draft, and the
> IPR WG intends to update RFC 3978 anyway, soon.
>
> A somewhat radical proposal:  If your patch is approved you
> could transform it into a complete 4181bis in AUTH48, and
> let that obsolete 4181.  Or is the 4181 situation exacly as
> for 4748 + 3978 ?

The situation for RFC 4181 is like this:  new copyright language 
will be required in IETF MIB documents as of the beginning of
next month, so we need to get an update out ASAP.  The original
plan was to issue a complete 4181bis, but the person who has
volunteered to take over the editing duties is busy with other
things, so I proposed the patch as an interim solution.  (Note
that we don't have xml source for this document, so the first
job for the new editor is creating it ... not a trivial task.)
My hope and expectation is that there will be a complete 4181bis
in the not too distant future.

> Your patch might be incomplete, chapter 3.7, appendix A, and
> the normative references mention 3978 instead of 3978 + 4748.
> Especially appendix A point 7 should now point to RFC 4748.

That's something that I hoped could wait for a complete 4181bis.

//cmh

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf