BCP 168, RFC 6398 on IP Router Alert Considerations and Usage

rfc-editor@rfc-editor.org Wed, 26 October 2011 22:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 271AD11E80B4; Wed, 26 Oct 2011 15:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.381
X-Spam-Status: No, score=-102.381 tagged_above=-999 required=5 tests=[AWL=0.219, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id OMBNgNzgFdKA; Wed, 26 Oct 2011 15:53:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A909911E8083; Wed, 26 Oct 2011 15:53:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A58B698C291; Wed, 26 Oct 2011 15:53:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 168, RFC 6398 on IP Router Alert Considerations and Usage
From: rfc-editor@rfc-editor.org
Message-Id: <20111026225312.A58B698C291@rfc-editor.org>
Date: Wed, 26 Oct 2011 15:53:12 -0700
Cc: int-area@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Oct 2011 22:53:13 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 168        
        RFC 6398

        Title:      IP Router Alert Considerations and 
        Author:     F. Le Faucheur, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       October 2011
        Mailbox:    flefauch@cisco.com
        Pages:      19
        Characters: 44914
        Updates:    RFC2113, RFC2711
        See Also:   BCP0168

        I-D Tag:    draft-ietf-intarea-router-alert-considerations-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6398.txt

The IP Router Alert Option is an IP option that alerts transit
routers to more closely examine the contents of an IP packet.  The
Resource reSerVation Protocol (RSVP), Pragmatic General Multicast
(PGM), the Internet Group Management Protocol (IGMP), Multicast
Listener Discovery (MLD), Multicast Router Discovery (MRD), and
General Internet Signaling 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, thereby updating RFC 2113 and RFC 2711.
Specifically, it provides recommendations against using the Router
Alert in the end-to-end open Internet and identifies controlled
environments where protocols depending on Router Alert can be used
safely.  It also provides recommendations about protection approaches
for service providers.  Finally, it provides brief guidelines for
Router Alert implementation on routers.  This memo documents an Internet 
Best Current Practice.

This document is a product of the Internet Area Working Group Working Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC