[Idr] RFC 5575 on Dissemination of Flow Specification Rules

rfc-editor@rfc-editor.org Fri, 21 August 2009 23:55 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C1683A683B; Fri, 21 Aug 2009 16:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.761
X-Spam-Level:
X-Spam-Status: No, score=-16.761 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 872Pxg7YAtEr; Fri, 21 Aug 2009 16:55:42 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 44A463A6879; Fri, 21 Aug 2009 16:55:42 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 512E930D789; Fri, 21 Aug 2009 16:55:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090821235533.512E930D789@bosco.isi.edu>
Date: Fri, 21 Aug 2009 16:55:33 -0700
Cc: idr@ietf.org, rfc-editor@rfc-editor.org
Subject: [Idr] RFC 5575 on Dissemination of Flow Specification Rules
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2009 23:55:43 -0000

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

        
        RFC 5575

        Title:      Dissemination of Flow Specification Rules 
        Author:     P. Marques, N. Sheth,
                    R. Raszuk, B. Greene,
                    J. Mauch, D. McPherson
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    roque@cisco.com, 
                    nsheth@juniper.net, 
                    raszuk@cisco.com,
                    bgreene@juniper.net, 
                    jmauch@us.ntt.net,
                    danny@arbor.net
        Pages:      22
        Characters: 46473
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-idr-flow-spec-09.txt

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

This document defines a new Border Gateway Protocol Network Layer
Reachability Information (BGP NLRI) encoding format that can be used
to distribute traffic flow specifications.  This allows the routing
system to propagate information regarding more specific components of
the traffic aggregate defined by an IP destination prefix.

Additionally, it defines two applications of that encoding format:
one that can be used to automate inter-domain coordination of traffic
filtering, such as what is required in order to mitigate
(distributed) denial-of-service attacks, and a second application to
provide traffic filtering in the context of a BGP/MPLS VPN service.

The information is carried via the BGP, thereby reusing protocol
algorithms, operational experience, and administrative processes such
as inter-provider peering agreements.  [STANDARDS TRACK]

This document is a product of the Inter-Domain Routing Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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
USC/Information Sciences Institute