RFC 7409 on Forwarding and Control Element Separation (ForCES) Packet Parallelization

rfc-editor@rfc-editor.org Mon, 01 December 2014 02:32 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A96A1A014E; Sun, 30 Nov 2014 18:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7gZDpJMAFExt; Sun, 30 Nov 2014 18:32:14 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECAE1A016F; Sun, 30 Nov 2014 18:32:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5CCF2181CE3; Sun, 30 Nov 2014 18:31:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7409 on Forwarding and Control Element Separation (ForCES) Packet Parallelization
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141201023144.5CCF2181CE3@rfc-editor.org>
Date: Sun, 30 Nov 2014 18:31:44 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/9dhD9B9DYA2xPu5IHFbRZGzYdVw
Cc: drafts-update-ref@iana.org, forces@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: Mon, 01 Dec 2014 02:32:16 -0000

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

        
        RFC 7409

        Title:      Forwarding and Control Element Separation 
                    (ForCES) Packet Parallelization 
        Author:     E. Haleplidis, J. Halpern
        Status:     Experimental
        Stream:     IETF
        Date:       November 2014
        Mailbox:    ehalep@ece.upatras.gr, 
                    joel.halpern@ericsson.com
        Pages:      27
        Characters: 53906
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-forces-packet-parallelization-03.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7409.txt

Many network devices support parallel packet processing.  This
document describes how Forwarding and Control Element Separation
(ForCES) can model a network device's parallelization datapath using
constructs defined by the ForCES model (RFC 5812) and controlled via
the ForCES protocol (RFC 5810).

This document is a product of the Forwarding and Control Element Separation Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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