IETF Logo Mail Archive

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

Steven Blake <slblake@petri-meat.com> Tue, 13 March 2012 04:38 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 0549911E8083 for <pcn@ietfa.amsl.com>; Mon, 12 Mar 2012 21:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.093
X-Spam-Level:
X-Spam-Status: No, score=-102.093 tagged_above=-999 required=5 tests=[AWL=0.506, BAYES_00=-2.599, 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 dXoSSY4bwlSV for <pcn@ietfa.amsl.com>; Mon, 12 Mar 2012 21:38:29 -0700 (PDT)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198]) by ietfa.amsl.com (Postfix) with ESMTP id CB0EF11E8072 for <pcn@ietf.org>; Mon, 12 Mar 2012 21:38:28 -0700 (PDT)
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=MYIjBas873GUhfY7srMBEy0CNVjPIojqU4EKl2OBs2PpLJrvpZuj4sVm3Or65GkAm4Y8iGfK6yeigLcQSC6iEgRvsREppwXmTWruQBTS/cwijzaIXPNggbYIUVtC35o7;
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 1S7JVC-0003u1-C5; Tue, 13 Mar 2012 00:38:26 -0400
From: Steven Blake <slblake@petri-meat.com>
To: David Harrington <ietfdbh@comcast.net>
Date: Tue, 13 Mar 2012 00:38:26 -0400
In-Reply-To: <CB840802.1F0F8%ietfdbh@comcast.net>
References: <CB840802.1F0F8%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: <1331613507.23822.6.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>" <pcn@ietf.org>, "<toby.moncaster@cl.cam.ac.uk>" <toby.moncaster@cl.cam.ac.uk>
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: Tue, 13 Mar 2012 04:38:30 -0000

On Mon, 2012-03-12 at 20:10 -0400, David Harrington wrote:

> Hi,
> 
> I hope I parsed your  double negatives appropriately.
> I was suggesting that having a normative reference to an expired draft
> could be problematic.
> 
> I see that one of the drafts was revised as Historic .
> Is the WG decision to publish these as Historic or let them disappear?
> The IESG needs to know.

I thought RFCs were re-categorized as Historic?  I didn't realize that
an RFC could be published as Historic right off the bat.

I'm initiating a 3-day WGLC to determine whether to publish
draft-ietf-pcn-psdm-encoding-02.txt and
draft-ietf-pcn-3-state-encoding-02.txt
as Informational/Historic RFCs (terminating EOB Thursday 3/15).
  
Please send comments to the list ASAP.


Regards,

// Steve

v2.23.0 | Report a Bug | By Email