draft-ietf-v6ops-ipv4survey-routing-02.txt   draft-ietf-v6ops-ipv4survey-routing-03.txt 
Network Working Group C. Olvera Network Working Group C. Olvera
draft-ietf-v6ops-ipv4survey-routing-02.txt Consulintel draft-ietf-v6ops-ipv4survey-routing-03.txt Consulintel
Internet Draft P. J. Nesser II Internet Draft P. J. Nesser II
Expires April 2004 Nesser & Nesser Consulting Expires April 2004 Nesser & Nesser Consulting
October 2003 December 2003
Survey of IPv4 Addresses in Currently Deployed Survey of IPv4 Addresses in Currently Deployed
IETF Routing Area Standards IETF Routing Area Standards
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 46 skipping to change at page 1, line 46
in currently deployed IETF Routing Area documented standards. In in currently deployed IETF Routing Area documented standards. In
order to successfully transition from an all IPv4 Internet to an all order to successfully transition from an all IPv4 Internet to an all
IPv6 Internet, many interim steps will be taken. One of these steps IPv6 Internet, many interim steps will be taken. One of these steps
is the evolution of current protocols that have IPv4 dependencies. is the evolution of current protocols that have IPv4 dependencies.
It is hoped that these protocols (and their implementations) will be It is hoped that these protocols (and their implementations) will be
redesigned to be network address independent, but failing that will redesigned to be network address independent, but failing that will
at least dually support IPv4 and IPv6. To this end, all Standards at least dually support IPv4 and IPv6. To this end, all Standards
(Full, Draft, and Proposed) as well as Experimental RFCs will be (Full, Draft, and Proposed) as well as Experimental RFCs will be
surveyed and any dependencies will be documented. surveyed and any dependencies will be documented.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Document Organization..........................................3 2. Document Organization..........................................3
3. Full Standards.................................................4 3. Full Standards.................................................4
skipping to change at page 2, line 35 skipping to change at page 2, line 35
9. Acknowledgements..............................................15 9. Acknowledgements..............................................15
10. References...................................................15 10. References...................................................15
11. Authors' Addresses...........................................16 11. Authors' Addresses...........................................16
Copyright........................................................16 Copyright........................................................16
Intellectual Property............................................17 Intellectual Property............................................17
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
1. Introduction 1. Introduction
This work aims to document all usage of IPv4 addresses in currently This work aims to document all usage of IPv4 addresses in currently
deployed IETF Routing Area documented standards. Also, throughout deployed IETF Routing Area documented standards. Also, throughout
this document there are discussions on how routing protocols might be this document there are discussions on how routing protocols might be
updated to support IPv6 addresses. updated to support IPv6 addresses.
skipping to change at page 3, line 48 skipping to change at page 3, line 48
discussed in its turn starting with RFC 1 and ending (around) RFC 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 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 RFC is discussed in a vacuum and problems or issues discussed do not
"look ahead" to see if the problems have already been fixed. "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, 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 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 and the problems that have been resolved in later RFCs are
correlated. correlated.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
3. Full Standards 3. Full Standards
Full Internet Standards (most commonly simply referred to as Full Internet Standards (most commonly simply referred to as
"Standards") are fully mature protocol specification that are widely "Standards") are fully mature protocol specification that are widely
implemented and used throughout the Internet. implemented and used throughout the Internet.
3.1 RFC 1722 (STD 57) RIP Version 2 Protocol Applicability Statement 3.1 RFC 1722 (STD 57) RIP Version 2 Protocol Applicability Statement
skipping to change at page 4, line 42 skipping to change at page 4, line 42
4.1 RFC 1771 A Border Gateway Protocol 4 (BGP-4) 4.1 RFC 1771 A Border Gateway Protocol 4 (BGP-4)
This RFC defines a protocol used for exchange of IPv4 routing This RFC defines a protocol used for exchange of IPv4 routing
information and does not support IPv6 as is defined. information and does not support IPv6 as is defined.
4.2 RFC 1772 Application of the Border Gateway Protocol in the Internet 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. 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 5. Proposed Standards
Proposed Standards are introductory level documents. There are no Proposed Standards are introductory level documents. There are no
requirements for even a single implementation. In many cases requirements for even a single implementation. In many cases
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
Proposed are never implemented or advanced in the IETF standards Proposed are never implemented or advanced in the IETF standards
process. They therefore are often just proposed ideas that are process. They therefore are often just proposed ideas that are
presented to the Internet community. Sometimes flaws are exposed or presented to the Internet community. Sometimes flaws are exposed or
they are one of many competing solutions to problems. In these later they are one of many competing solutions to problems. In these later
cases, no discussion is presented as it would not serve the purpose cases, no discussion is presented as it would not serve the purpose
of this discussion. of this discussion.
skipping to change at page 5, line 46 skipping to change at page 5, line 46
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.6 RFC 1517 Applicability Statement for the Implementation of Classless 5.6 RFC 1517 Applicability Statement for the Implementation of Classless
Inter-Domain Routing (CIDR) Inter-Domain Routing (CIDR)
This document deals exclusively with IPv4 addressing issue. This document deals exclusively with IPv4 addressing issue.
5.7 RFC 1518 An Architecture for IP Address Allocation with CIDR 5.7 RFC 1518 An Architecture for IP Address Allocation with CIDR
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
This document deals exclusively with IPv4 addressing issue. This document deals exclusively with IPv4 addressing issue.
5.8 RFC 1519 Classless Inter-Domain Routing (CIDR): an Address 5.8 RFC 1519 Classless Inter-Domain Routing (CIDR): an Address
Assignment and Aggregation Strategy Assignment and Aggregation Strategy
This document deals exclusively with IPv4 addressing issue. This document deals exclusively with IPv4 addressing issue.
skipping to change at page 6, line 45 skipping to change at page 6, line 45
5.13 RFC 2080 RIPng for IPv6 5.13 RFC 2080 RIPng for IPv6
This RFC documents a protocol for exchanging IPv6 routing information This RFC documents a protocol for exchanging IPv6 routing information
and is not discussed in this document. and is not discussed in this document.
5.14 RFC 2091 Triggered Extensions to RIP to Support Demand Circuits 5.14 RFC 2091 Triggered Extensions to RIP to Support Demand Circuits
This RFC defines an enhancement for an IPv4 routing protocol and This RFC defines an enhancement for an IPv4 routing protocol and
while it has no IPv4 dependencies it is inherently limited to IPv4. while it has no IPv4 dependencies it is inherently limited to IPv4.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
5.15 RFC 2338 Virtual Router Redundancy Protocol (VRRP) 5.15 RFC 2338 Virtual Router Redundancy Protocol (VRRP)
This protocol is IPv4 specific, there are numerous references to 32- This protocol is IPv4 specific, there are numerous references to 32-
bit IP addresses. bit IP addresses.
5.16 RFC 2370 The OSPF Opaque LSA Option 5.16 RFC 2370 The OSPF Opaque LSA Option
There are no IPv4 dependencies in this protocol other than the fact There are no IPv4 dependencies in this protocol other than the fact
that it is a new functionality for a routing protocol that only that it is a new functionality for a routing protocol that only
supports IPv4 networks. supports IPv4 networks.
5.17 RFC 2439 BGP Route Flap Damping 5.17 RFC 2439 BGP Route Flap Damping
This protocol enhancements have no IPv4 dependencies, even though the The protocol enhancements have no IPv4 dependencies, even though the
base protocol, BGP-4, is IPv4 only routing protocol. base protocol, BGP-4, is IPv4 only routing protocol.
5.18 RFC 2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter- 5.18 RFC 2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-
Domain Routing Domain Routing
This RFC documents IPv6 routing methods and is not discussed in this This RFC documents IPv6 routing methods and is not discussed in this
document. document.
5.19 RFC 2740 OSPF for IPv6 5.19 RFC 2740 OSPF for IPv6
skipping to change at page 7, line 47 skipping to change at page 7, line 47
Appendix: Appendix:
o IPv6 as Delivery and/or Payload Protocol o IPv6 as Delivery and/or Payload Protocol
This specification describes the intersection of GRE currently This specification describes the intersection of GRE currently
deployed by multiple vendors. IPv6 as delivery and/or payload deployed by multiple vendors. IPv6 as delivery and/or payload
protocol is not included. protocol is not included.
5.21 RFC 2796 BGP Route Reflection - An Alternative to Full Mesh IBGP 5.21 RFC 2796 BGP Route Reflection - An Alternative to Full Mesh IBGP
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
Although the protocol enhancements have no IPv4 dependencies, the Although the protocol enhancements have no IPv4 dependencies, the
base protocol, BGP-4, is IPv4 only routing protocol. This base protocol, BGP-4, is IPv4 only routing protocol. This
specification updates but does not obsolete RFC 1966. specification updates but does not obsolete RFC 1966.
5.22 RFC 2858 Multiprotocol Extensions for BGP-4 5.22 RFC 2858 Multiprotocol Extensions for BGP-4
In the Abstract: In the Abstract:
skipping to change at page 8, line 47 skipping to change at page 8, line 47
5.26 RFC 3065 Autonomous System Confederations for BGP 5.26 RFC 3065 Autonomous System Confederations for BGP
Although the protocol enhancements have no IPv4 dependencies, the Although the protocol enhancements have no IPv4 dependencies, the
base protocol, BGP-4, is IPv4 only routing protocol. base protocol, BGP-4, is IPv4 only routing protocol.
5.27 RFC 3101 The OSPF Not-So-Stubby Area (NSSA) Option 5.27 RFC 3101 The OSPF Not-So-Stubby Area (NSSA) Option
This document defines an extension to an IPv4 routing protocol. This document defines an extension to an IPv4 routing protocol.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
5.28 RFC 3107 Carrying Label Information in BGP-4 5.28 RFC 3107 Carrying Label Information in BGP-4
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.29 RFC 3122 Extensions to IPv6 Neighbor Discovery for Inverse 5.29 RFC 3122 Extensions to IPv6 Neighbor Discovery for Inverse
Discovery Specification Discovery Specification
skipping to change at page 9, line 48 skipping to change at page 9, line 48
address. address.
The three strings will be separated by a single comma. An example of The three strings will be separated by a single comma. An example of
record would thus be: record would thus be:
___________________________________________________________________ ___________________________________________________________________
| domain | type | record | value | | domain | type | record | value |
| - | | | | | - | | | |
|*.27.32.192.in-addr.arpa | IP | TXT | RX, 10, 10.0.0.7| |*.27.32.192.in-addr.arpa | IP | TXT | RX, 10, 10.0.0.7|
|_________________________|________|__________|___________________| |_________________________|________|__________|___________________|
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
which means that for all hosts whose IP address starts by the three which means that for all hosts whose IP address starts by the three
octets "192.32.27" the IP host "10.0.0.7" can be used as a gateway, octets "192.32.27" the IP host "10.0.0.7" can be used as a gateway,
and that the preference value is 10. and that the preference value is 10.
6.3 RFC 1476 RAP: Internet Route Access Protocol 6.3 RFC 1476 RAP: Internet Route Access Protocol
This document defines an IPv7 routing protocol and has been abandoned This document defines an IPv7 routing protocol and has been abandoned
skipping to change at page 10, line 47 skipping to change at page 10, line 47
6.8 RFC 2201 Core Based Trees (CBT) Multicast Routing Architecture 6.8 RFC 2201 Core Based Trees (CBT) Multicast Routing Architecture
See previous Section for the IPv4 limitation in this protocol. See previous Section for the IPv4 limitation in this protocol.
6.9 RFC 2337 Intra-LIS IP multicast among routers over ATM using Sparse 6.9 RFC 2337 Intra-LIS IP multicast among routers over ATM using Sparse
Mode PIM Mode PIM
This protocol is designed for IPv4 multicast. This protocol is designed for IPv4 multicast.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
6.10 RFC 2362 Protocol Independent Multicast-Sparse Mode (PIM-SM): 6.10 RFC 2362 Protocol Independent Multicast-Sparse Mode (PIM-SM):
Protocol Specification Protocol Specification
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
6.11 RFC 2676 QoS Routing Mechanisms and OSPF Extensions 6.11 RFC 2676 QoS Routing Mechanisms and OSPF Extensions
There are IPv4 dependencies in this protocol. It requires the use of There are IPv4 dependencies in this protocol. It requires the use of
the IPv4 TOS header field. the IPv4 TOS header field.
7. Summary of Results 7. Summary of Results
In the initial survey of RFCs, 22 positives were identified out of a In the initial survey of RFCs, 22 positives were identified out of a
total of 44, broken down as follows: total of 45, broken down as follows:
Standards 3 of 3 or 100% Standards 3 of 3 or 100%
Draft Standards 1 of 2 or 50.00% Draft Standards 1 of 3 or 33.33%
Proposed Standards 13 of 29 or 44.83% Proposed Standards 13 of 29 or 44.83%
Experimental RFCs 6 of 11 or 54.54% Experimental RFCs 6 of 11 or 54.54%
Of those identified many require no action because they document Of those identified many require no action because they document
outdated and unused protocols, while others are document protocols outdated and unused protocols, while others are document protocols
that are actively being updated by the appropriate working groups. that are actively being updated by the appropriate working groups.
Additionally there are many instances of standards that should be Additionally there are many instances of standards that should be
updated but do not cause any operational impact if they are not updated but do not cause any operational impact if they are not
skipping to change at page 11, line 50 skipping to change at page 11, line 50
updates and should not be taken as an official statement. updates and should not be taken as an official statement.
7.1 Standards 7.1 Standards
7.1.1 STD 57 RIP Version 2 Protocol Applicability Statement (RFC 7.1.1 STD 57 RIP Version 2 Protocol Applicability Statement (RFC
1722) 1722)
This problem has been fixed by RFC 2081, RIPng Protocol Applicability This problem has been fixed by RFC 2081, RIPng Protocol Applicability
Statement. Statement.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
7.1.2 STD 54 OSPF Version 2 (RFC 2328) 7.1.2 STD 54 OSPF Version 2 (RFC 2328)
This problem has been fixed by RFC 2740, OSPF for IPv6. This problem has been fixed by RFC 2740, OSPF for IPv6.
7.1.3 STD 56 RIP Version 2 (RFC 2453) 7.1.3 STD 56 RIP Version 2 (RFC 2453)
This problem has been fixed by RFC 2080, RIPng for IPv6. This problem has been fixed by RFC 2080, RIPng for IPv6.
skipping to change at page 12, line 51 skipping to change at page 12, line 51
7.3.2 Applicability Statement for OSPFv2 (RFC 1370) 7.3.2 Applicability Statement for OSPFv2 (RFC 1370)
This problem has been resolved in RFC 2740, OSPF for IPv6. This problem has been resolved in RFC 2740, OSPF for IPv6.
7.3.3 Applicability of CIDR (RFC 1517) 7.3.3 Applicability of CIDR (RFC 1517)
The contents of this specification has been treated in various IPv6 The contents of this specification has been treated in various IPv6
addressing architecture RFCs, see RFC 3513 & 3587. addressing architecture RFCs, see RFC 3513 & 3587.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
7.3.4 CIDR Architecture (RFC 1518) 7.3.4 CIDR Architecture (RFC 1518)
The contents of this specification has been treated in various IPv6 The contents of this specification has been treated in various IPv6
addressing architecture RFCs, see RFC 3513 & 3587. addressing architecture RFCs, see RFC 3513 & 3587.
7.3.5 Classless Inter-Domain Routing (CIDR): an Address Assignment 7.3.5 Classless Inter-Domain Routing (CIDR): an Address Assignment
and Aggregation Strategy (RFC 1519) and Aggregation Strategy (RFC 1519)
skipping to change at page 13, line 53 skipping to change at page 13, line 53
7.3.12 Generic Routing Encapsulation (GRE)(RFC 2784) 7.3.12 Generic Routing Encapsulation (GRE)(RFC 2784)
Even trough GRE tunneling over IPv6 has been implemented and used, Even trough GRE tunneling over IPv6 has been implemented and used,
its use has not been formally specified. Clarifications are required. its use has not been formally specified. Clarifications are required.
7.3.13 OSPF NSSA Option (RFC 3101) 7.3.13 OSPF NSSA Option (RFC 3101)
This functionality has been covered in RFC 2740, OSPF for IPv6. This functionality has been covered in RFC 2740, OSPF for IPv6.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
7.4 Experimental RFCs 7.4 Experimental RFCs
7.4.1 Distance Vector Multicast Routing Protocol (RFC 1075) 7.4.1 Distance Vector Multicast Routing Protocol (RFC 1075)
This protocol is a routing protocol for IPv4 multicast routing. It This protocol is a routing protocol for IPv4 multicast routing. It
is no longer in use and need not be redefined. is no longer in use and need not be redefined.
skipping to change at page 14, line 52 skipping to change at page 14, line 52
However, if necessary, an update to this document could simply define However, if necessary, an update to this document could simply define
the use of the IPv6 Traffic Class field since it is defined to be the use of the IPv6 Traffic Class field since it is defined to be
exactly the same as the IPv4 TOS field. exactly the same as the IPv4 TOS field.
8. Security Considerations 8. Security Considerations
This document examines the IPv6-readiness of routing specification; This document examines the IPv6-readiness of routing specification;
this does not have security considerations in itself. this does not have security considerations in itself.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
9. Acknowledgements 9. Acknowledgements
The original author, Philip J. Nesser II, would like to acknowledge The original author, Philip J. Nesser II, would like to acknowledge
the support of the Internet Society in the research and production of the support of the Internet Society in the research and production of
this document. this document.
He also would like to thanks his partner in all ways, Wendy M. He also would like to thanks his partner in all ways, Wendy M.
skipping to change at page 15, line 51 skipping to change at page 15, line 51
[4] Philip J. Nesser II, Andreas Bergstrom. "Survey of IPv4 [4] Philip J. Nesser II, Andreas Bergstrom. "Survey of IPv4
addresses in Currently Deployed IETF Operations & Management Area addresses in Currently Deployed IETF Operations & Management Area
Standards", draft-ietf-v6ops-ipv4survey-ops-03.txt IETF work in Standards", draft-ietf-v6ops-ipv4survey-ops-03.txt IETF work in
progress, September 2003. progress, September 2003.
[5] Philip J. Nesser II, Andreas Bergstrom. "Survey of IPv4 [5] Philip J. Nesser II, Andreas Bergstrom. "Survey of IPv4
Addresses in Currently Deployed IETF Security Area Standards", draft- Addresses in Currently Deployed IETF Security Area Standards", draft-
ietf-v6ops-ipv4survey-sec-02.txt, IETF work in progress, September ietf-v6ops-ipv4survey-sec-02.txt, IETF work in progress, September
2003. 2003.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
[6] Philip J. Nesser II, Andreas Bergstrom. "Survey of IPv4 [6] Philip J. Nesser II, Andreas Bergstrom. "Survey of IPv4
Addresses in Currently Deployed IETF Sub-IP Area Standards", draft- Addresses in Currently Deployed IETF Sub-IP Area Standards", draft-
ietf-v6ops-ipv4survey-subip-02.txt, IETF work in progress, August ietf-v6ops-ipv4survey-subip-02.txt, IETF work in progress, August
2003. 2003.
[7] Philip J. Nesser II, Andreas Bergstrom "Survey of IPv4 [7] Philip J. Nesser II, Andreas Bergstrom "Survey of IPv4
Addresses in Currently Deployed IETF Transport Area Standards", Addresses in Currently Deployed IETF Transport Area Standards",
skipping to change at page 16, line 52 skipping to change at page 16, line 52
The following Full Copyright Statement from RFC 2026, Section 10.4, The following Full Copyright Statement from RFC 2026, Section 10.4,
describes the applicable copyright for this document. describes the applicable copyright for this document.
Copyright (C) The Internet Society June, 2003. All Rights Reserved. Copyright (C) The Internet Society June, 2003. All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
Survey of IPv4 Addresses in Currently Survey of IPv4 Addresses in Currently
Deployed IETF Routing Area Standards Deployed IETF Routing Area Standards
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
skipping to change at page 17, line 53 skipping to change at page 17, line 53
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
draft-ietf-v6ops-ipv4survey-routing-02.txt draft-ietf-v6ops-ipv4survey-routing-03.txt
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/