| draft-ietf-grow-no-more-unallocated-slash8s-02.txt | draft-ietf-grow-no-more-unallocated-slash8s-03.txt | |||
|---|---|---|---|---|
| Network Working Group L. Vegoda | Network Working Group L. Vegoda | |||
| Internet-Draft ICANN | Internet-Draft ICANN | |||
| Intended status: BCP August 2, 2011 | Intended status: BCP September 28, 2011 | |||
| Expires: February 3, 2012 | Expires: March 31, 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-02 | draft-ietf-grow-no-more-unallocated-slash8s-03 | |||
| 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 February 3, 2012. | This Internet-Draft will expire on March 31, 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 3, line 28 | skipping to change at page 3, line 28 | |||
| 2. Terminology | 2. Terminology | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| document are to be interpreted as described in BCP 14, RFC 2119 | document are to be interpreted as described in BCP 14, RFC 2119 | |||
| [RFC2119]. | [RFC2119]. | |||
| Bogons are packets sourced from addresses that have not yet been | Bogons are packets sourced from addresses that have not yet been | |||
| allocated by IANA or the Regional Internet Registries (RIRs), or | allocated by IANA or the Regional Internet Registries (RIRs), or | |||
| addresses reserved for private or special use by RFCs [RFC3871]. | addresses reserved for private or special use by RFCs [RFC5735]. | |||
| Martians are packets with an altogether bogus (non-registered or ill- | Martians are packets with an altogether bogus (non-registered or ill- | |||
| formed) Internet address [RFC1208]. Bogons are referred to as "Dark | formed) Internet address [RFC1208]. Bogons are referred to as "Dark | |||
| IP" in some circles. | IP" in some circles. | |||
| 3. Traffic Filtering Options | 3. Traffic Filtering Options | |||
| 3.1. No Longer Filtering Based on Address Registration Status | 3.1. No Longer Filtering Based on Address Registration Status | |||
| Network administrators who implemented filters for unallocated IPv4 | Network administrators who implemented filters for unallocated IPv4 | |||
| /8s did so in the knowledge that those /8s were not a legitimate | /8s did so in the knowledge that those /8s were not a legitimate | |||
| skipping to change at page 6, line 6 | skipping to change at page 6, line 6 | |||
| March 2010. | March 2010. | |||
| 7.2. Informative References | 7.2. Informative References | |||
| [RFC1208] Jacobsen, O. and D. Lynch, "Glossary of networking terms", | [RFC1208] Jacobsen, O. and D. Lynch, "Glossary of networking terms", | |||
| RFC 1208, March 1991. | RFC 1208, March 1991. | |||
| [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for | [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for | |||
| Network Interconnect Devices", RFC 2544, March 1999. | 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 | [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks | |||
| Reserved for Documentation", RFC 5737, January 2010. | 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. | |||
| End of changes. 5 change blocks. | ||||
| 9 lines changed or deleted | 5 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/ | ||||