RFC 2267: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2827.
Current version: RFC 2827 — Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
In plain English — editorial summary, not part of the RFC
This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2267
- Published
- January 1998
- Authors
- P. Ferguson; D. Senie
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 2827
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2430A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)Current
October 1998
- RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent
October 2001
- RFC 2260Scalable Support for Multi-homed Multi-provider ConnectivityCurrent
January 1998
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 1788ICMP Domain Name MessagesObsoleted
April 1995
- RFC 2194Review of Roaming ImplementationsCurrent
September 1997
- RFC 2477Criteria for Evaluating Roaming ProtocolsCurrent
January 1999
- RFC 2286Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128Current
February 1998
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?