RFC 8955 on Dissemination of Flow Specification Rules

rfc-editor@rfc-editor.org Thu, 31 December 2020 21:54 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 910873A0C0F; Thu, 31 Dec 2020 13:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7J49FuttNuoE; Thu, 31 Dec 2020 13:54:11 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47F7A3A0C0E; Thu, 31 Dec 2020 13:54:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B5192F40741; Thu, 31 Dec 2020 13:53:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8955 on Dissemination of Flow Specification Rules
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, idr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201231215338.B5192F40741@rfc-editor.org>
Date: Thu, 31 Dec 2020 13:53:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/SIIS2KRk8CRyQxcrTMMN4v31CJs>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 31 Dec 2020 21:54:13 -0000

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

        RFC 8955

        Title:      Dissemination of Flow Specification Rules 
        Author:     C. Loibl,
                    S. Hares,
                    R. Raszuk,
                    D. McPherson,
                    M. Bacher
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2020
        Mailbox:    cl@tix.at, 
        Pages:      36
        Obsoletes:  RFC 5575, RFC 7674

        I-D Tag:    draft-ietf-idr-rfc5575bis-27.txt

        URL:        https://www.rfc-editor.org/info/rfc8955

        DOI:        10.17487/RFC8955

This document defines a Border Gateway Protocol Network Layer
Reachability Information (BGP NLRI) encoding format that can be used
to distribute (intra-domain and inter-domain) traffic Flow
Specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services. This
allows the routing system to propagate information regarding more
specific components of the traffic aggregate defined by an IP
destination prefix. 

It also specifies BGP Extended Community encoding formats, which can
be used to propagate Traffic Filtering Actions along with the Flow
Specification NLRI.  Those Traffic Filtering Actions encode actions a
routing system can take if the packet matches the Flow Specification.

This document obsoletes both RFC 5575 and RFC 7674.

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

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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