draft-ietf-grow-no-more-unallocated-slash8s-01.txt   draft-ietf-grow-no-more-unallocated-slash8s-02.txt 
Network Working Group L. Vegoda Network Working Group L. Vegoda
Internet-Draft ICANN Internet-Draft ICANN
Intended status: BCP May 13, 2011 Intended status: BCP August 2, 2011
Expires: November 14, 2011 Expires: February 3, 2012
Time to Remove Filters for Previously Unallocated IPv4 /8s Time to Remove Filters for Previously Unallocated IPv4 /8s
draft-ietf-grow-no-more-unallocated-slash8s-01 draft-ietf-grow-no-more-unallocated-slash8s-02
Abstract Abstract
It has been common for network administrators to filter IP traffic It has been common for network administrators to filter IP traffic
from and BGP prefixes of unallocated IPv4 address space. Now that from and BGP prefixes of unallocated IPv4 address space. Now that
there are no longer any unallocated IPv4 /8s, this practise is more there are no longer any unallocated IPv4 /8s, this practise is more
complicated, fragile and expensive. Network administrators are complicated, fragile and expensive. Network administrators are
advised to remove filters based on the registration status of the advised to remove filters based on the registration status of the
address space. address space.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 14, 2011. This Internet-Draft will expire on February 3, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Traffic Filtering Options . . . . . . . . . . . . . . . . . . . 3 3. Traffic Filtering Options . . . . . . . . . . . . . . . . . . . 3
3.1. No Longer Filtering Based on Address Registration 3.1. No Longer Filtering Based on Address Registration
Status . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Status . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Continuing to Filter Traffic from Unallocated IPv4 3.2. Continuing to Filter Traffic from Unallocated IPv4
Space . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Space . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Prefixes That Should Not be Routed Across the Internet . . . . 4 4. Prefixes That Should Not be Routed Across the Internet . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 6 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
It has been common for network administrators to filter IP traffic It has been common for network administrators to filter IP traffic
from and BGP prefixes of unallocated IPv4 address space. Now that from and BGP prefixes of unallocated IPv4 address space. Now that
there are no longer any unallocated IPv4 /8s, this practise is more there are no longer any unallocated IPv4 /8s, this practise is more
complicated, fragile and expensive. Network administrators are complicated, fragile and expensive. Network administrators are
advised to remove filters based on the registration status of the advised to remove filters based on the registration status of the
skipping to change at page 5, line 17 skipping to change at page 5, line 17
The cessation of filters based on unallocated IPv4 /8 allocations is The cessation of filters based on unallocated IPv4 /8 allocations is
an evolutionary step towards reasonable security filters. While an evolutionary step towards reasonable security filters. While
these filters are no longer necessary, and in fact harmful, this does these filters are no longer necessary, and in fact harmful, this does
not obviate the need to continue other security solutions. These not obviate the need to continue other security solutions. These
other solutions are as necessary today as they ever were. other solutions are as necessary today as they ever were.
6. IANA Considerations 6. IANA Considerations
This document makes no request of IANA. This document makes no request of IANA.
7. Normative References 7. References
7.1. Normative References
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, August 1989. RFC 1112, August 1989.
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122, October 1989.
[RFC1208] Jacobsen, O. and D. Lynch, "Glossary of networking terms",
RFC 1208, March 1991.
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets", E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996. BCP 5, RFC 1918, February 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, March 1999.
[RFC3871] Jones, G., "Operational Security Requirements for Large
Internet Service Provider (ISP) IP Network
Infrastructure", RFC 3871, September 2004.
[RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic
Configuration of IPv4 Link-Local Addresses", RFC 3927, Configuration of IPv4 Link-Local Addresses", RFC 3927,
May 2005. May 2005.
[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
BCP 153, RFC 5735, January 2010. BCP 153, RFC 5735, January 2010.
[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
Reserved for Documentation", RFC 5737, January 2010.
[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for [RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for
IPv4 Multicast Address Assignments", BCP 51, RFC 5771, IPv4 Multicast Address Assignments", BCP 51, RFC 5771,
March 2010. March 2010.
7.2. Informative References
[RFC1208] Jacobsen, O. and D. Lynch, "Glossary of networking terms",
RFC 1208, March 1991.
[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, March 1999.
[RFC3871] Jones, G., "Operational Security Requirements for Large
Internet Service Provider (ISP) IP Network
Infrastructure", RFC 3871, September 2004.
[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
Reserved for Documentation", RFC 5737, January 2010.
Appendix A. Acknowledgments Appendix A. Acknowledgments
Thanks are owed to Kim Davies, Terry Manderson, Dave Piscitello and Thanks are owed to Kim Davies, Terry Manderson, Dave Piscitello and
Joe Abley for helpful advice on how to focus this document. Thanks Joe Abley for helpful advice on how to focus this document. Thanks
also go to Andy Davidson, Philip Smith and Rob Thomas for early also go to Andy Davidson, Philip Smith and Rob Thomas for early
reviews and suggestions for improvements to the text and Carlos reviews and suggestions for improvements to the text and Carlos
Pignataro for his support and comments. Pignataro for his support and comments.
Author's Address Author's Address
 End of changes. 9 change blocks. 
19 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/