draft-ietf-v6ops-ipv4survey-ops-04.txt   draft-ietf-v6ops-ipv4survey-ops-05.txt 
Network Working Group Philip J. Nesser II Network Working Group Philip J. Nesser II
draft-ietf-v6ops-ipv4survey-ops-04.txt Nesser & Nesser Consulting draft-ietf-v6ops-ipv4survey-ops-05.txt Nesser & Nesser Consulting
Internet Draft Andreas Bergstrom (Ed.) Internet Draft Andreas Bergstrom (Ed.)
Ostfold University College Ostfold University College
November 2003 December 2003
Expires April 2004 Expires May 2004
Survey of IPv4 Addresses in Currently Deployed Survey of IPv4 Addresses in Currently Deployed
IETF Operations & Management Area Standards IETF Operations & Management Area Standards
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.
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at line 56 skipping to change at line 55
1. Introduction 1. Introduction
2. Document Organisation 2. Document Organisation
3. Full Standards 3. Full Standards
4. Draft Standards 4. Draft Standards
5. Proposed Standards 5. Proposed Standards
6. Experimental RFCs 6. Experimental RFCs
7. Summary of Results 7. Summary of Results
7.1 Standards 7.1 Standards
7.2 Draft Standards 7.2 Draft Standards
7.3 Proposed Standards 7.3 Proposed Standards 7.4 Experimental RFCs
7.4 Experimental RFCs
8. Security Consideration 8. Security Consideration
9. Acknowledgements 9. Acknowledgements
10. References 10. References
11. Authors' Addresses 11. Authors' Addresses
12. Intellectual Property Statement 12. Intellectual Property Statement
13. Full Copyright Statement 13. Full Copyright Statement
1.0 Introduction 1.0 Introduction
This document is part of a document set aiming to document all usage of This document is part of a document set aiming to document all usage of
skipping to change at line 1544 skipping to change at line 1542
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.106 RFC 3060 Policy Core Information Model -- Version 1 5.106 RFC 3060 Policy Core Information Model -- Version 1
Specification (CIM) Specification (CIM)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.107 RFC 3084 COPS Usage for Policy Provisioning (COPS-PR) 5.107 RFC 3084 COPS Usage for Policy Provisioning (COPS-PR)
This is an IPv4 only protocol. A version for IPv6 may need to be This specification builds on RFC 2748, and is both IPv4
defined. and IPv6 capable. The specification defines a sample filter in
section 4.3, which has "ipv4" in it; however, it's just an example,
and available to IPv6 as well with a simple replacement of "ipv4"
with "ipv6".
5.108 RFC 3165 Definitions of Managed Objects for the Delegation of 5.108 RFC 3165 Definitions of Managed Objects for the Delegation of
Management Scripts. Management Scripts.
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.109 RFC 3231 Definitions of Managed Objects for Scheduling Management 5.109 RFC 3231 Definitions of Managed Objects for Scheduling Management
Operations. Operations.
There are no IPv4 dependecies in this specification. There are no IPv4 dependecies in this specification.
skipping to change at line 1658 skipping to change at line 1659
7.1.1 STD 16, Structure of Management Information (RFCs 1155 and 1212) 7.1.1 STD 16, Structure of Management Information (RFCs 1155 and 1212)
RFCs 1155 and RFCs 1212 (along with the informational document RFC RFCs 1155 and RFCs 1212 (along with the informational document RFC
1215) define SMIv1. These documents have been superseded by RFCs 1215) define SMIv1. These documents have been superseded by RFCs
2578, 2579, and 2580 which define SMIv2. Since SMIv1 is no longer 2578, 2579, and 2580 which define SMIv2. Since SMIv1 is no longer
being used as the basis for new IETF MIB modules, the limitations being used as the basis for new IETF MIB modules, the limitations
identified in this Internet Standard do not require any action. identified in this Internet Standard do not require any action.
7.1.2 STD 17 Simple Network Management Protocol (RFC 1213) 7.1.2 STD 17 Simple Network Management Protocol (RFC 1213)
The limitations identified have been addressed, RFC1213 has been The limitations identified have been addressed, because RFC 1213
split into multiple modules which have been seen to. has been split into multiple modules which are all IPv6 capable.
7.2 Draft Standards 7.2 Draft Standards
7.2.1 BGP4 MIB (RFC 1657) 7.2.1 BGP4 MIB (RFC 1657)
This problem is currently being addressed by the Inter Domain Routing This problem is currently being addressed by the Inter Domain Routing
(IDR) WG and an ID exists (draft-ietf-idr-bgp4-mib-11.txt). (IDR) WG and an ID exists (draft-ietf-idr-bgp4-mib-11.txt).
7.2.2 SMDS MIB (RFC 1694) 7.2.2 SMDS MIB (RFC 1694)
 End of changes. 

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