Internet DRAFT - draft-boucadair-ip-version-5-8-9-historic
draft-boucadair-ip-version-5-8-9-historic
Network Working Group M. Boucadair
Internet-Draft C. Jacquenet
Intended status: Standards Track Orange
Expires: September 17, 2016 March 16, 2016
Reclassification of ST (IP version 5), PIP (IP version 8) and TUBA (IP
version 9) to Historic
draft-boucadair-ip-version-5-8-9-historic-00
Abstract
This document reclassifies ST (IP version 5), PIP (IP version 8) and
TUBA (IP version 9) to Historic status.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 17, 2016.
Copyright Notice
Copyright (c) 2016 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
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.
Boucadair & Jacquenet Expires September 17, 2016 [Page 1]
Internet-DrafReclassification ST, PIP and TUBA to Historic March 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Security Considerations . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Normative references . . . . . . . . . . . . . . . . . . 3
5.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The Internet community has been mobilized in the past to agree on a
strategy for the evolution of the Internet and its associated IP
model (e.g., [RFC6250]). An effort, called Internet "Architecture
Retreat", has been initiated in the early 90's by the IAB (Internet
Architecture Board) and IESG (Internet Engineering Steering Group) to
investigate issues met by the Internet. A set of recommendations
"towards the future Internet architecture" have been drawn [RFC1287].
At that time (although it may be seen as nonsense in 2016), the
Internet community faced a dilemma: either choose to deliberately
limit the growth of the Internet or take the risk of disrupting the
network and introduce new techniques for the sake of Internet growth.
In addition to the need to support real-time services, [RFC1287]
acknowledged that routing information explosion and address space
consumption were the most urgent problems to solve. Given small
changes may require a long time to be effective, [RFC1287] advocated
for a long term action plan to preserve the architectural principles
of the Internet instead of implementing small changes.
Then, a group called ROAD [RFC1380] has been formed to structure the
problem space and to propose some directions for future Internet.
ROAD and [RFC1287] have inspired IAB to propose an action plan to
overcome the alarming decrease of IP address pools and the growth of
routing tables [I-D.iab-ipversion7]. Concretely, IAB recommended to
deprecate the Class "A"/"B"/"C" address taxonomy, to enforce CIDR
(Classless Inter-domain Routing, [RFC4632]) as a short term solution,
and to get ready for the introduction of "IP version 7" (not to
confuse with [RFC1475]) in a mid and long term. Once the address
shortage is solved, design a routing architecture which does not
assume any dependency between addresses and the underlying routing
topology.
Later, the IETF (Internet Engineering Task Force) has adopted the
strategy proposed by the IAB but objected to some technical choices.
Particularly, the IETF rejected the recommendation on IPv7 in favour
Boucadair & Jacquenet Expires September 17, 2016 [Page 2]
Internet-DrafReclassification ST, PIP and TUBA to Historic March 2016
of IPv6 [RFC2460]; the reader may refer to [RFC1752] for more
details. As an input to its decision-making process, the IETF formed
a working group called Address Lifetime Estimation (ALE) to estimate
the IPv4 address depletion date and to implicitly qualify the level
of urgency to specify an alternative scheme to IPv4 addressing. For
the record, ALE estimated the IPv4 address depletion date between
2005 and 2011 [RFC1752]; this projection has been confirmed by recent
announcements of IANA about the depletion of global IPv4 addresses.
Various proposals have been RFCed to solve some of the problems
encountered by the Internet architecture. IP version numbers have
been assigned to some of them:
Decimal Keyword Version
======= ======= ========================
5 ST ST Datagram Mode
7 TP/IX TP/IX: The Next Internet
8 PIP The P Internet Protocol
9 TUBA TUBA
Given that IPv6 is a deployment reality and there are no proven
deployments of the aforementioned IP versions, this document
reclassifies ST ([RFC1347]), PIP ([RFC1819]) and TUBA ([RFC1621]) to
Historic status.
Note that [RFC1475] is already obsoleted.
2. Security Considerations
This document does not introduce any security issues.
3. IANA Considerations
IANA is requested to deallocate the version numbers
(http://www.iana.org/assignments/version-numbers/version-
numbers.xhtml): 5, 7, 8, and 9.
4. Acknowledgments
TBC.
5. References
5.1. Normative references
Boucadair & Jacquenet Expires September 17, 2016 [Page 3]
Internet-DrafReclassification ST, PIP and TUBA to Historic March 2016
[RFC1347] Callon, R., "TCP and UDP with Bigger Addresses (TUBA), A
Simple Proposal for Internet Addressing and Routing",
RFC 1347, DOI 10.17487/RFC1347, June 1992,
<http://www.rfc-editor.org/info/rfc1347>.
[RFC1621] Francis, P., "Pip Near-term Architecture", RFC 1621,
DOI 10.17487/RFC1621, May 1994,
<http://www.rfc-editor.org/info/rfc1621>.
[RFC1819] Delgrossi, L., Ed. and L. Berger, Ed., "Internet Stream
Protocol Version 2 (ST2) Protocol Specification - Version
ST2+", RFC 1819, DOI 10.17487/RFC1819, August 1995,
<http://www.rfc-editor.org/info/rfc1819>.
5.2. Informative References
[I-D.iab-ipversion7]
Internet Architecture Board, "IP Version 7", July 1992.
[RFC1287] Clark, D., Chapin, L., Cerf, V., Braden, R., and R. Hobby,
"Towards the Future Internet Architecture", RFC 1287,
DOI 10.17487/RFC1287, December 1991,
<http://www.rfc-editor.org/info/rfc1287>.
[RFC1380] Gross, P. and P. Almquist, "IESG Deliberations on Routing
and Addressing", RFC 1380, DOI 10.17487/RFC1380, November
1992, <http://www.rfc-editor.org/info/rfc1380>.
[RFC1475] Ullmann, R., "TP/IX: The Next Internet", RFC 1475,
DOI 10.17487/RFC1475, June 1993,
<http://www.rfc-editor.org/info/rfc1475>.
[RFC1752] Bradner, S. and A. Mankin, "The Recommendation for the IP
Next Generation Protocol", RFC 1752, DOI 10.17487/RFC1752,
January 1995, <http://www.rfc-editor.org/info/rfc1752>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/rfc2460>.
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing
(CIDR): The Internet Address Assignment and Aggregation
Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August
2006, <http://www.rfc-editor.org/info/rfc4632>.
[RFC6250] Thaler, D., "Evolution of the IP Model", RFC 6250,
DOI 10.17487/RFC6250, May 2011,
<http://www.rfc-editor.org/info/rfc6250>.
Boucadair & Jacquenet Expires September 17, 2016 [Page 4]
Internet-DrafReclassification ST, PIP and TUBA to Historic March 2016
Authors' Addresses
Mohamed Boucadair
Orange
Rennes 35000
France
EMail: mohamed.boucadair@orange.com
Christian Jacquenet
Orange
Rennes 35000
France
EMail: christian.jacquenet@orange.com
Boucadair & Jacquenet Expires September 17, 2016 [Page 5]
