Re: [PCN] IESG feedback from 3-in-1 encoding/ encoding comparison

Steven Blake <slblake@petri-meat.com> Thu, 08 March 2012 05:01 UTC

Return-Path: <slblake@petri-meat.com>
X-Original-To: pcn@ietfa.amsl.com
Delivered-To: pcn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF1A021F85A5 for <pcn@ietfa.amsl.com>; Wed, 7 Mar 2012 21:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.136
X-Spam-Level:
X-Spam-Status: No, score=-101.136 tagged_above=-999 required=5 tests=[AWL=-0.396, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5mJnncwQ58d for <pcn@ietfa.amsl.com>; Wed, 7 Mar 2012 21:01:17 -0800 (PST)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198]) by ietfa.amsl.com (Postfix) with ESMTP id BD11921F85A3 for <pcn@ietf.org>; Wed, 7 Mar 2012 21:01:14 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=petri-meat.com; h=Received:Subject:From:To:Cc:Date:In-Reply-To:References:Content-Type:X-Mailer:Content-Transfer-Encoding:Message-ID:Mime-Version; b=BG5zjk8C/cqivNtmkKXUreg5akvE9VUGfRw5bvZAwlm6cA3oyXU0J12vvgleWHJpS/mShFSYqxgIlCNKdD8kywrxXGv1QSlA2iiq+2FfFW7aAEuabXHNsfHhEXJiFJmC;
Received: from cpe-071-065-228-004.nc.res.rr.com ([71.65.228.4]) by elom.tchmachines.com with esmtpa (Exim 4.69) (envelope-from <slblake@petri-meat.com>) id 1S5VTU-0002YZ-Sg; Thu, 08 Mar 2012 00:01:12 -0500
From: Steven Blake <slblake@petri-meat.com>
To: David Harrington <ietfdbh@comcast.net>
Date: Thu, 08 Mar 2012 00:01:13 -0500
In-Reply-To: <CB7BBCE1.1D69F%ietfdbh@comcast.net>
References: <CB7BBCE1.1D69F%ietfdbh@comcast.net>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.0.3 (3.0.3-1.fc15)
Content-Transfer-Encoding: 7bit
Message-ID: <1331182874.6028.14.camel@tachyon>
Mime-Version: 1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - elom.tchmachines.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
Cc: pcn@ietf.org
Subject: Re: [PCN] IESG feedback from 3-in-1 encoding/ encoding comparison
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 05:01:17 -0000

On Tue, 2012-03-06 at 13:23 -0500, David Harrington wrote:

> Hi,
> 
> It appears to me the drafts have already expired.
> You can refer to expired drafts in an Informational document, using an
> approach similar to this:
> 
>    The XYZ encoding was proposed in a draft document submitted to the PCN
> WG in <October
>    2006>. The PCN WG chose to not advance this draft.
> 
> 
> This way there is no reference to the expired draft, and the intentions to
> not carry the drafts forward is easy to see.
> 
> Now, as to whether publishing them as historical is the right way:
> How much more detail is in the drafts that will be lost if we just let
> them expire?
> Is it important to the industry to keep a record of that historical
> detail, or just a summary of the ideas in those drafts and why they didn't
> work.
> I can understand that academically, it might be nice to have these
> published as historical records, but I tend to agree that having them
> published as RFCs could confuse people who are not really knowledgeable
> about IETF practice and the difference in types of RFCs.
> If the summary seems adequate, then I recommend letting the drafts
> disappear.
> You should make sure all your documents do not contain any references to
> those drafts.

I think this last bit of advice applies even if the WG chooses to
publish the expired drafts.

Now, are there any volunteers to revise these drafts and get them in
shape for WG last call?


Regards,

// Steve