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

I think that the encoding-comparison draft is sufficient and that they don't need to be published as historical rfcs. Mainly because of the extra effort involved with no benefit in my view. 

If it is decided there is consensus and effort to progress these 2 docs as historical, I suggest:

- waiting for 3-in-1 to get to RFC status or at least into rfc editor, in case issues emerge during that approval which need to be reflected back into these two docs. (For instance, Bob recently sent an email - not sure if that would imply changes to these two docs as well.) 
- please make sure key parts (abstract, intro, conclusion) make it clear that this is a document for archive purposes and the actual encoding to use is in rfcxxxx potential confusion

Re:
> I was suggesting that having a normative reference to an expired draft
> could be problematic.
I think this can be skirted round. In the encoding comparison, say something like "PSDN encoding was proposed in [ref]"
Then it can be an Informational reference - since it's informing the reader where it was proposed, whereas the actual definition is in the encoding comparison doc.

-----Original Message-----
From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Steven Blake
Sent: 13 March 2012 04:38
To: David Harrington
Cc: <pcn@ietf.org>; <toby.moncaster@cl.cam.ac.uk>
Subject: Re: [PCN] IESG feedback from 3-in-1 encoding/ encoding comparison

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

_______________________________________________
PCN mailing list
PCN@ietf.org
https://www.ietf.org/mailman/listinfo/pcn