Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status.

Similar documents
Internet Engineering Task Force (IETF) Request for Comments: 7805 Obsoletes: MTI Systems

Internet Engineering Task Force (IETF) October This document establishes an IETF URN Sub-namespace for use with OAuth-related specifications.

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track. Cisco May 2012

Internet Engineering Task Force (IETF) Request for Comments: ISSN: January 2010

Internet Engineering Task Force (IETF) Request for Comments: 6379 Obsoletes: 4869 Category: Informational October 2011 ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track April 2013 ISSN: Formally Deprecating Some ICMPv4 Message Types

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track May 2011 ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: January 2011

Internet Engineering Task Force (IETF) Updates: 5451 March 2012 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7725 Category: Standards Track February 2016 ISSN:

Internet Engineering Task Force (IETF) Category: Informational. May IEEE Information Element for the IETF

Internet Engineering Task Force (IETF) Updates: 4326 June 2014 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7125 Category: Informational. February 2014

Internet Engineering Task Force (IETF) Request for Comments: 7319 BCP: 191 July 2014 Category: Best Current Practice ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6160 Category: Standards Track April 2011 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8142 Category: Standards Track April 2017 ISSN:

Internet Engineering Task Force (IETF) Cisco Systems, Inc. April 2015

Internet Engineering Task Force (IETF) Request for Comments: ISSN: October 2011

Internet Engineering Task Force (IETF) Request for Comments: 6441 BCP: 171 November 2011 Category: Best Current Practice ISSN:

Internet Engineering Task Force (IETF) Category: Informational March 2016 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7237 Category: Informational June 2014 ISSN:

Internet Engineering Task Force (IETF) Updates: 6376 January 2018 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6061 Category: Informational January 2011 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6309

Internet Engineering Task Force (IETF) Request for Comments: 8069 Category: Informational February 2017 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: ISSN: March 2016

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track ISSN: September 2015

Internet Engineering Task Force (IETF) Category: Informational. July Reclassification of Suite B Documents to Historic Status

Internet Engineering Task Force (IETF) Request for Comments: ISSN: August 2010

Internet Engineering Task Force (IETF) Category: Informational. June A Uniform Resource Name (URN) Namespace for CableLabs

Internet Engineering Task Force (IETF) Obsoletes: 2831 July 2011 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6028 Category: Experimental ISSN: October 2010

Internet Engineering Task Force (IETF) Request for Comments: 6034 Category: Standards Track October 2010 ISSN:

Internet Engineering Task Force (IETF) Category: Informational October 2013 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track. July 2014

Internet Engineering Task Force (IETF) Category: Informational. August IANA Registration for the Cryptographic Algorithm Object Identifier Range

Internet Engineering Task Force (IETF) Request for Comments: 8186 Category: Standards Track. June 2017

Internet Engineering Task Force (IETF) Request for Comments: 7504 June 2015 Updates: 1846, 5321 Category: Standards Track ISSN:

Request for Comments: 7314 Category: Experimental July 2014 ISSN: Extension Mechanisms for DNS (EDNS) EXPIRE Option.

Internet Engineering Task Force (IETF) Category: Standards Track March 2015 ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track. March 2017

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track ISSN: July 2014

Clarifications for When to Use the name-addr Production in SIP Messages

Internet Engineering Task Force (IETF) Request for Comments: 6725 Category: Standards Track August 2012 ISSN:

Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation Status

Internet Engineering Task Force (IETF) Request for Comments: 7192 Category: Standards Track April 2014 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6522 STD: 73 January 2012 Obsoletes: 3462 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track December 2011 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6440 Category: Standards Track. Huawei December 2011

Internet Engineering Task Force (IETF) Request for Comments: T. Chown University of Southampton M. Eubanks Iformata Communications August 2012

Internet Engineering Task Force (IETF) Category: Standards Track. Enterprise Architects February 2012

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track. January 2010

Internet Engineering Task Force (IETF) Request for Comments: 8035 Updates: 5761 November 2016 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7189 Category: Standards Track March 2014 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7973 Category: Informational ISSN: November 2016

Internet Engineering Task Force (IETF) Request for Comments: 7537 Updates: 4379, L. Andersson S. Aldrin Huawei Technologies May 2015

Internet Engineering Task Force (IETF) Request for Comments: 5736 Category: Informational. ICANN January 2010

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: July 2012

Internet Engineering Task Force (IETF) Request for Comments: 6470 Category: Standards Track February 2012 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: November 2015

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track ISSN: February 2016

Internet Engineering Task Force (IETF) Request for Comments: 8440 Category: Standards Track ISSN: August 2018

Internet Engineering Task Force (IETF) Updates: 2474 August 2018 Category: Standards Track ISSN:

Request for Comments: 5402 Category: Informational February 2010 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6694 August 2012 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Updates: 5322 March 2013 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8516 Category: Standards Track January 2019 ISSN:

Internet Engineering Task Force (IETF) Obsoletes: 7302 September 2016 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7660 Category: Standards Track. October 2015

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: March 2010

Internet Engineering Task Force (IETF) Request for Comments: ISSN: March 2018

Internet Engineering Task Force (IETF) Request for Comments: 8441 Updates: 6455 September 2018 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: ISSN: July 2011

Internet Engineering Task Force (IETF) Updates: 792, 1122, 1812 May 2012 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6594 Category: Standards Track April 2012 ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track March 2011 ISSN:

Internet Engineering Task Force (IETF) Updates: 6811 September 2018 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Updates: 5066 February 2014 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: Q. Wu, Ed. R. Huang Huawei November 2014

Internet Research Task Force (IRTF) Request for Comments: 6255 Category: Informational May 2011 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: Google K. Patel Cisco Systems August 2015

Internet Engineering Task Force (IETF) Request for Comments: ISSN: Y. Umaoka IBM December 2010

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: October Host Identity Protocol (HIP) Rendezvous Extension

Internet Engineering Task Force (IETF) Category: Standards Track January 2019 ISSN:

Internet Engineering Task Force (IETF) June Network Time Protocol (NTP) Server Option for DHCPv6

Internet Engineering Task Force (IETF) RTFM, Inc. January 2011

Internet Engineering Task Force (IETF) Request for Comments: 8050 Category: Standards Track ISSN: May 2017

Category: Informational January 2010 ISSN:

Internet Engineering Task Force (IETF) ISSN: April 2014

Internet Engineering Task Force (IETF) Nokia P. Pillay-Esnault Huawei USA January 2019

Internet Engineering Task Force (IETF) Request for Comments: 7043 Category: Informational October 2013 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: November 2010

Internet Engineering Task Force (IETF) Request for Comments: ISSN: July 2014

Internet Engineering Task Force (IETF) Request for Comments: 5959 Category: Standards Track August 2010 ISSN:

Internet Engineering Task Force (IETF) Updates: 5614 October 2013 Category: Experimental ISSN:

Internet Research Task Force (IRTF) Category: Experimental. S. Ostermann. Ohio University. March 2014

Internet Engineering Task Force (IETF) Request for Comments: 6939 Category: Standards Track. May 2013

Internet Engineering Task Force (IETF) Category: Standards Track. February 2012

DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 Prefixes

Internet Engineering Task Force (IETF) BCP: 183 May 2013 Category: Best Current Practice ISSN:

Transcription:

Internet Engineering Task Force (IETF) L. Eggert Request for Comments: 6247 Nokia Obsoletes: 1072, 1106, 1110, 1145, May 2011 1146, 1379, 1644, 1693 Updates: 4614 Category: Informational ISSN: 2070-1721 Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status Abstract This document reclassifies several TCP extensions that have never seen widespread use to Historic status. The affected RFCs are RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6247. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust s Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must Eggert Informational [Page 1]

include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 1. Introduction TCP has a long history, and several proposed TCP extensions have never seen widespread deployment. Section 5 of the TCP "roadmap" document [RFC4614] already classifies a number of TCP extensions as Historic and describes the reasons for doing so, but it does not instruct the RFC Editor and IANA to change the status of these RFCs in the RFC database and the relevant IANA registries. The sole purpose of this document is to do just that. Please refer to Section 5 of [RFC4614] for justification. 2. RFC Editor Considerations Per this document, the RFC Editor has changed the status of the following RFCs to Historic [RFC2026]: o [RFC1072] on "TCP Extensions for Long-Delay Paths" o [RFC1106] and [RFC1110] related to the "TCP Big Window and Nak Options" o [RFC1145] and [RFC1146] related to the "TCP Alternate Checksum Options" o [RFC1379] and [RFC1644] on "T/TCP -- Extensions for Transactions Functional Specification" o [RFC1693] on "An Extension to TCP : Partial Order Service" 3. IANA Considerations IANA has marked the TCP options 6, 7, 9, 10, 11, 12, 13, 14, and 15 documented in [RFC1072], [RFC1146], [RFC1644], and [RFC1693] as "obsolete" in the "TCP Option Kind Numbers" registry [TCPOPTREG], with a reference to this RFC. 4. Security Considerations As mentioned in [RFC4614], the TCP Extensions for Transactions (T/TCP) [RFC1379][RFC1644] are reported to have security issues [DEVIVO]. Eggert Informational [Page 2]

5. Acknowledgments Lars Eggert is partly funded by [TRILOGY], a research project supported by the European Commission under its Seventh Framework Program. 6. References 6.1. Normative References [RFC1072] Jacobson, V. and R. Braden, "TCP extensions for longdelay paths", RFC 1072, October 1988. [RFC1106] Fox, R., "TCP big window and NAK options", RFC 1106, June 1989. [RFC1110] [RFC1145] [RFC1146] McKenzie, A., "Problem with the TCP big window option", RFC 1110, August 1989. Zweig, J. and C. Partridge, "TCP alternate checksum options", RFC 1145, February 1990. Zweig, J. and C. Partridge, "TCP alternate checksum options", RFC 1146, March 1990. [RFC1379] Braden, B., "Extending TCP for Transactions -- Concepts", RFC 1379, November 1992. [RFC1644] [RFC1693] Braden, B., "T/TCP -- TCP Extensions for Transactions Functional Specification", RFC 1644, July 1994. Connolly, T., Amer, P., and P. Conrad, "An Extension to TCP : Partial Order Service", RFC 1693, November 1994. [RFC4614] Duke, M., Braden, R., Eddy, W., and E. Blanton, "A Roadmap for Transmission Control Protocol (TCP) Specification Documents", RFC 4614, September 2006. 6.2. Informative References [DEVIVO] [RFC2026] de Vivo, M., de Vivo, G., Koeneke, R., and G. Isern, "Internet Vulnerabilities Related to TCP/IP and T/TCP", ACM SIGCOMM Computer Communications Review (CCR), Vol. 29, No. 1, January 1999. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. Eggert Informational [Page 3]

[TCPOPTREG] Internet Assigned Numbers Authority (IANA), "TCP Option Kind Numbers", <http://www.iana.org>. [TRILOGY] "Trilogy Project", <http://www.trilogy-project.org/>. Author s Address Lars Eggert Nokia Research Center P.O. Box 407 Nokia Group 00045 Finland Phone: +358 50 48 24461 EMail: lars.eggert@nokia.com URI: http://research.nokia.com/people/lars_eggert Eggert Informational [Page 4]