RFC 6441: Time to Remove Filters for Previously Unallocated IPv4 /8s
In plain English — editorial summary, not part of the RFC
It has been common for network administrators to filter IP traffic from and BGP prefixes of unallocated IPv4 address space. Now that there are no longer any unallocated IPv4 /8s, this practise is more complicated, fragile, and expensive. Network administrators are advised to remove filters based on the registration status of the address space. This document explains why any remaining packet and BGP prefix filters for unallocated IPv4 /8s should now be removed on border routers and documents those IPv4 unicast prefixes that should not be routed across the public Internet. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6441
- Published
- November 2011
- Authors
- L. Vegoda
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- BCP171
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7755SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center EnvironmentsCurrent
February 2016
- RFC 7756Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation ModeCurrent
February 2016
- RFC 7757Explicit Address Mappings for Stateless IP/ICMP TranslationCurrent
February 2016
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 4942IPv6 Transition/Co-existence Security ConsiderationsCurrent
September 2007
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 4213Basic Transition Mechanisms for IPv6 Hosts and RoutersCurrent
October 2005
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?