ICMP Blocked Notification
draft-lear-icmp-blocked-00

Document Type Expired Internet-Draft (individual)
Last updated 2000-08-21
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-lear-icmp-blocked-00.txt

Abstract

Since the introduction of private addresses[1] the use of NATs and firewalls has introduced not only inability to communicate using certain mechanisms, such as AH[2], ESP[3], and H.323[4], but also difficulty in determining the reason for the failed communication. This document specifies methods an intermediate device such as a router, a firewall, or a NAT may use to inform end hosts that a particular type of communication is not possible. It also recommends practices for both the frequency of transmission of such error notices, and their consumption by the end hosts. This document is an outgrowth of the 'foglamps' discussion that occurred within the IETF between late 1999 and 2000, and is not the product of a working group.

Authors

Eliot Lear (lear@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)