Network Working Group C. Olvera draft-ietf-v6ops-ipv4survey-routing-03.txt Consulintel Internet Draft P. J. Nesser II Expires April 2004 Nesser & Nesser Consulting December 2003 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed athttp://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This investigation work seeks to document all usage of IPv4 addresses in currently deployed IETF Routing Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. draft-ietf-v6ops-ipv4survey-routing-03.txt Expires April 2004 [Page 1] Internet Draft December 2003 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Table of Contents 1. Introduction...................................................3 2. Document Organization..........................................3 3. Full Standards.................................................4 4. Draft Standards................................................4 5. Proposed Standards.............................................4 6. Experimental RFCs..............................................9 7. Summary of Results............................................11 8. Security Considerations.......................................14 9. Acknowledgements..............................................15 10. References...................................................15 11. Authors' Addresses...........................................16 Copyright........................................................16 Intellectual Property............................................17 draft-ietf-v6ops-ipv4survey-routing-03.txt Expires April 2004 [Page 2] Internet Draft December 2003 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards 1. Introduction This work aims to document all usage of IPv4 addresses in currently deployed IETF Routing Area documented standards. Also, throughout this document there are discussions on how routing protocols might be updated to support IPv6 addresses. This material was originally presented within a single document, but in an effort to have the information in a manageable form, it has subsequently been split into 7 documents conforming to the current IETF main areas (Application[2], Internet[3], Operations & Management [4], Routing[this document], Security[5], Sub-IP[6] and Transport[7]). The general overview, methodology used during documentation and scope of the investigation for the whole 7 documents can be found in the introduction of this set of documents[1]. It is important to mention that to perform this study the following classes of IETF standards are investigated: Full, Draft, and Proposed, as well as Experimental. Informational, BCP and Historic RFCs are not addressed. RFCs that have been obsoleted by either newer versions or as they have transitioned through the standards process are also not covered. 2. Document Organization The main Sections of this document are described below. Sections 3, 4, 5, and 6 each describe the raw analysis of Full, Draft, Proposed Standards and Experimental RFCs. Each RFC is discussed in its turn starting with RFC 1 and ending (around) RFC 3100. The comments for each RFC are "raw" in nature. That is, each RFC is discussed in a vacuum and problems or issues discussed do not "look ahead" to see if the problems have already been fixed. Section 7 is an analysis of the data presented in Sections 3, 4, 5, and 6. It is here that all of the results are considered as a whole and the problems that have been resolved in later RFCs are correlated. draft-ietf-v6ops-ipv4survey-routing-03.txt Expires April 2004 [Page 3] Internet Draft December 2003 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards 3. Full Standards Full Internet Standards (most commonly simply referred to as "Standards") are fully mature protocol specification that are widely implemented and used throughout the Internet. 3.1 RFC 1722 (STD 57) RIP Version 2 Protocol Applicability Statement RIPv2 is only intended for IPv4 networks. 3.2 RFC 2328 (STD 54) OSPF Version 2 This RFC defines a protocol for IPv4 routing. It is highly assumptive about address formats being IPv4 in nature. 3.3 RFC 2453 (STD 56) RIP Version 2 RIPv2 is only intended for IPv4 networks. 4. Draft Standards Draft Standards represent the penultimate standard level in the IETF. A protocol can only achieve draft standard when there are multiple, independent, interoperable implementations. Draft Standards are usually quite mature and widely used. 4.1 RFC 1771 A Border Gateway Protocol 4 (BGP-4) This RFC defines a protocol used for exchange of IPv4 routing information and does not support IPv6 as is defined. 4.2 RFC 1772 Application of the Border Gateway Protocol in the Internet This RFC is a discussion of the use of BGP-4 on the Internet. 4.3 RFC 3392 Capabilities Advertisement with BGP-4 Although the protocol enhancements have no IPv4 dependencies, the base protocol, BGP-4, is IPv4 only. 5. Proposed Standards Proposed Standards are introductory level documents. There are no requirements for even a single implementation. In many cases draft-ietf-v6ops-ipv4survey-routing-03.txt Expires April 2004 [Page 4] Internet Draft December 2003 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Proposed are never implemented or advanced in the IETF standards process. They therefore are often just proposed ideas that are presented to the Internet community. Sometimes flaws are exposed or they are one of many competing solutions to problems. In these later cases, no discussion is presented as it would not serve the purpose of this discussion. 5.1 RFC 1195 Use of OSI IS-IS for routing in TCP/IP and dual environments This document specifies a protocol for the exchange of IPv4 routing information. 5.2 RFC 1370 Applicability Statement for OSPF This document discusses a version of OSPF that is limited to IPv4. 5.3 RFC 1397 Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol BGP2 and BGP3 are both deprecated and therefore are not discussed in this document. 5.4 RFC 1478 An Architecture for Inter-Domain Policy Routing The architecture described in this document has no IPv4 dependencies. 5.5 RFC 1479 Inter-Domain Policy Routing Protocol Specification: Version 1 (IDPR) There are no IPv4 dependencies in this protocol. 5.6 RFC 1517 Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR) This document deals exclusively with IPv4 addressing issue. 5.7 RFC 1518 An Architecture for IP Address Allocation with CIDR draft-ietf-v6ops-ipv4survey-routing-03.txt Expires April 2004 [Page 5] Internet Draft December 2003 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards This document deals exclusively with IPv4 addressing issue. 5.8 RFC 1519 Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy This document deals exclusively with IPv4 addressing issue. 5.9 RFC 1582 Extensions to RIP to Support Demand Circuits This protocol is an extension to a protocol for exchanging IPv4 routing information. 5.10 RFC 1584 Multicast Extensions to OSPF This document defines the use of IPv4 multicast to an IPv4 only routing protocol. 5.11 RFC 1793 Extending OSPF to Support Demand Circuits There are no IPv4 dependencies in this protocol other than the fact that it is a new functionality for a routing protocol that only supports IPv4 networks. 5.12 RFC 1997 BGP Communities Attribute Although the protocol enhancements have no IPv4 dependencies, the base protocol, BGP-4, is IPv4 only. 5.13 RFC 2080 RIPng for IPv6 This RFC documents a protocol for exchanging IPv6 routing information and is not discussed in this document. 5.14 RFC 2091 Triggered Extensions to RIP to Support Demand Circuits This RFC defines an enhancement for an IPv4 routing protocol and while it has no IPv4 dependencies it is inherently limited to IPv4. draft-ietf-v6ops-ipv4survey-routing-03.txt Expires April 2004 [Page 6] Internet Draft December 2003 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards 5.15 RFC 2338 Virtual Router Redundancy Protocol (VRRP) This protocol is IPv4 specific, there are numerous references to 32- bit IP addresses. 5.16 RFC 2370 The OSPF Opaque LSA Option There are no IPv4 dependencies in this protocol other than the fact that it is a new functionality for a