Re: [tcpm] I-D Action:draft-eggert-tcpm-historicize-01.txt

[Lars Eggert <[e-mail]>]

ACK.

I'll leave it to David as the responsible AD to make a call here. As I said, I have no issue removing 1263 from this doc if this is the consensus.

Lars

On 2011-2-17, at 19:35, Christian Huitema wrote:

> I would suggest to leave 1623 alone for now. There may be a  rationale to downgrade it later -- or maybe not. In any case, that rationale is not that it defines unused TCP extensions, and thus it does not belong to the same batch.
> 
> -----Original Message-----
> From: Lars Eggert [mailto:[e-mail]] 
> Sent: Thursday, February 17, 2011 12:57 AM
> To: Christian Huitema
> Cc: [e-mail] Extensions; [e-mail]; Scott O. Bradner
> Subject: Re: [tcpm] I-D Action:draft-eggert-tcpm-historicize-01.txt
> 
> Hi,
> 
> On 2011-2-17, at 9:00, Christian Huitema wrote:
>> I note that the list of RFC includes RFC 1263, "TCP Extensions Considered Harmful." The purpose of the draft is to make some extensions historic. Since RFC 1263 does not define any particular extension, I don't see the point of including it. RFC 1263 is an informational RFC. It provides advice on protocol design, and that advice appears to be just as informational now as it was then. I don't see why we should reclassify it.
> 
> it provides advice on *TCP* protocol design going forward, but the community went the other way. I don't feel strongly about moving it to Historic or not, but someone suggested it (see below).
> 
> Scott Bradner brought this up during his ops-dir review as well:
> 
>> On 2011-2-11, at 4:24, Scott O. Bradner wrote:
>>> I'm not sure why RFC 1263  "TCP Extensions Considered Harmful" should
>>> be included in the list since it seems to me that message of the RFC
>>> is still valid.  But if it is to be included it seems like the
>>> "it is not used" general description does not apply to this RFC and some
>>> specific text should be added to say why it should be made historic
>> 
>> good point. Someone (I can't remember who, might have been Craig Partridge) suggested to include RFC1263 in this list because it argues for an architectural approach which the subsequent TCP evolution with its myriad of options did not follow. (RFC4614 also contains text along those lines.)
>> 
>> I'm adding this text to my working copy:
>> 
>> <xref target="RFC1263"/> ("TCP Extensions Considered Harmful") is somewhat of a special case. Unlike the other RFCs made Historic by this memo, it does not specify a TCP option that failed to see deployment, but argued for a way to evolve TCP forward that the community did not choose to follow.
> 
> Lars