GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Internet Engineering Task Force
  • System Status
  • Report a Bug
  • IRTF.org
  • IAB.org
  • Datatracker
  • Author Resources
  • RFC Editor
  • rfc-dist Info Page
  • rfc-interest Info Page

This view

  • Original page
  • New address

GeezerVison is showing www.rfc-editor.org — BCP 140 subseries contains 1 RFC | RFC Editor

BCP 140

Subscribe to BCP 140

Get notified when:

  • An RFC is added to or removed from this BCP
  • A RFC within the collection changes status, obsoleted by, updates, updated by, or subseries.

BCPs are stable identifiers for Best Current Practices. A BCP may consist of a single RFC or a group of RFCs related to a specific IETF process or recommended guidelines. The collection may become empty as the BCP evolves.

RFC 5358: BCP 140: Preventing Use of Recursive Nameservers in Reflector Attacks

Best Current Practice
  • J. Damas
  • F. Neves
  • October 2008
  • IETF publication
  • Operations and Management Area

Abstract

This document describes ways to prevent the use of default configured recursive nameservers as reflectors in Denial of Service (DoS) attacks. It provides recommended configuration as measures to mitigate the attack. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Abstract

This document describes ways to prevent the use of default configured recursive nameservers as reflectors in Denial of Service (DoS) attacks. It provides recommended configuration as measures to mitigate the attack. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.