Protocol Action: IP Router Alert Option to Proposed Standard

The IESG <iesg-secretary@CNRI.Reston.VA.US> Wed, 29 January 1997 18:54 UTC

Received: from ietf.org by ietf.org id aa25484; 29 Jan 97 13:54 EST
Received: from ietf.ietf.org by ietf.org id aa25356; 29 Jan 97 13:51 EST
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Sender: ietf-announce-request@ietf.org
From: The IESG <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: IP Router Alert Option to Proposed Standard
Date: Wed, 29 Jan 1997 13:51:10 -0500
X-Orig-Sender: scoya@ietf.org
Message-ID: <9701291351.aa25356@ietf.org>


  The IESG has approved the Internet-Draft "IP Router Alert Option"
  <draft-katz-router-alert-04.txt> as a Proposed Standard. This
  document is the not the product of a working group, but has been
  reviewed by the Resource Reservation Setup Protocol Working Group.
  The IESG contact persons are Allison Mankin and Allyn Romanow.


Technical Summary

  This document describes a new IP option type, router alert, which
  tells transit routers to examine the IP packet. This is especially
  useful for new protocols that require special treatment from routers
  and cannot be handled in a router's mainline forwarding path. Two
  such currently existing protocols are IGMP and RSVP.  This mechanism
  makes it possible for routers to intercept packets not addressed to
  them without incurring a significant performance penalty on the
  forwarding of normal data packets.

Working Group Summary

  This is not a product of an IETF working group. However, it was
  reviewed by the RSVP working group, which adopted it as a recommended
  mechanism and requested that it be submitted for standards track
  publication. Since router alert is a general router mechanism, it is
  important that there be more than a single protocol as constituency
  for it. The inclusion of router alert in IGMP version 2 constitutes
  sufficient generality from the point of view of the several working
  group chairs and the Area Directors.

  A similar draft is in Last Call for Router Alert for IPv6.

  No problems surfaced during the four week IETF Last Call.

Protocol Quality

  The protocol was reviewed for the IETF by Allyn Romanow