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

Toby Moncaster <toby.moncaster@cl.cam.ac.uk> Fri, 02 March 2012 09:45 UTC

Return-Path: <tm444@hermes.cam.ac.uk>
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 5966021F8B3C for <pcn@ietfa.amsl.com>; Fri, 2 Mar 2012 01:45:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 FtnzVCw8Xfmx for <pcn@ietfa.amsl.com>; Fri, 2 Mar 2012 01:45:20 -0800 (PST)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 99C5D21F8AB7 for <pcn@ietf.org>; Fri, 2 Mar 2012 01:45:20 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from ravage.cl.cam.ac.uk ([128.232.1.17]:63381) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpsa (PLAIN:tm444) (TLSv1:AES128-SHA:128) id 1S3P38-0007GO-rh (Exim 4.72) for pcn@ietf.org (return-path <tm444@hermes.cam.ac.uk>); Fri, 02 Mar 2012 09:45:18 +0000
From: Toby Moncaster <toby.moncaster@cl.cam.ac.uk>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 02 Mar 2012 09:45:17 +0000
Message-Id: <9C874ADA-1419-4AF4-B075-47FEDA98E999@cl.cam.ac.uk>
To: pcn <pcn@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Sender: "T. Moncaster" <tm444@hermes.cam.ac.uk>
Subject: [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: Fri, 02 Mar 2012 09:45:21 -0000

Adrian Farrel is keen to find out what the WG intentions are regarding the "other" WG encoding drafts. Just to remind everyone, the original idea was to have the baseline encoding and a set of 3 experimental encodings that built on it. Then Bob got RFC6040 published and we decided to push 3-in-1 encoding as the main standard. This left the other experimental encodings in limbo. They are:

draft-ietf-pcn-psdm-encoding-01 <http://tools.ietf.org/html/draft-ietf-pcn-psdm-encoding-01>

draft-ietf-pcn-3-state-encoding-01 <http://tools.ietf.org/html/draft-ietf-pcn-3-state-encoding-01>

These are both cited in the encoding comparison draft which poses some potential problems. Firstly we are not meant to refer to IDs in RFCs, secondly these have both long expired so will eventually disappear from any archives, thirdly I believe Michael may still want to use PSDM experimentally?

There would seem to be 3 possible courses of action:

1) We ask for these to be published as historical RFCs so they can be referenced from encoding comparison
2) we ask for these to be published as experimental schemes so they can be referenced and can be used
3) we remove all reference from the encoding comparison

OPtion 1 is probably the easiest as (hopefully) they would not need too much updating. Option 2 requires more work on the drafts (in light of the fact we are obsolete RFC5696 which they both depend on), but would at least hold the door open to future work. Option 3 partially defeats the point of the encoding comparison document. 

I have a very slight preference for option 1, but what do other people think? 

Toby