[Int-area] Last Call: <draft-ietf-intarea-router-alert-considerations-05.txt> (IP Router Alert Considerations and Usage) to BCP

The IESG <iesg-secretary@ietf.org> Wed, 29 June 2011 14:07 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34DA011E808E; Wed, 29 Jun 2011 07:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level:
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.236, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kxSVnNb3u81C; Wed, 29 Jun 2011 07:07:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDBE111E8076; Wed, 29 Jun 2011 07:07:58 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <20110629140758.14503.57842.idtracker@ietfa.amsl.com>
Date: Wed, 29 Jun 2011 07:07:58 -0700
Cc: int-area@ietf.org
Subject: [Int-area] Last Call: <draft-ietf-intarea-router-alert-considerations-05.txt> (IP Router Alert Considerations and Usage) to BCP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2011 14:07:59 -0000

The IESG has received a request from the Internet Area Working Group WG
(intarea) to consider the following document:
- 'IP Router Alert Considerations and Usage'
  <draft-ietf-intarea-router-alert-considerations-05.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-07-13. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The IP Router Alert Option is an IP option that alerts transit
   routers to more closely examine the contents of an IP packet.
   Resource reSerVation Protocol (RSVP), Pragmatic General Multicast
   (PGM), Internet Group Management Protocol (IGMP), Multicast Listener
   Discovery (MLD), Multicast Router Discovery (MRD) and General
   Internet Signalling Transport (GIST) are some of the protocols that
   make use of the IP Router Alert option.  This document discusses
   security aspects and usage guidelines around the use of the current
   IP Router Alert option.  Specifically, it provides recommendation
   against using the Router Alert in the end-to-end open Internet as
   well as identify controlled environments where protocols depending on
   Router Alert can be used safely.  It also provides recommendation
   about protection approaches for Service Providers.  Finally it
   provides brief guidelines for Router Alert implementation on routers.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-intarea-router-alert-considerations/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-intarea-router-alert-considerations/


No IPR declarations have been submitted directly on this I-D.