RFC 5812 on Forwarding and Control Element Separation (ForCES) Forwarding Element Model

rfc-editor@rfc-editor.org Fri, 19 March 2010 02:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id D35E73A6C8F; Thu, 18 Mar 2010 19:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=-0.521, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id ZUb+6PsLvVe0; Thu, 18 Mar 2010 19:18:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 301233A6C91; Thu, 18 Mar 2010 19:18:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8DF7FE0764; Thu, 18 Mar 2010 19:18:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5812 on Forwarding and Control Element Separation (ForCES) Forwarding Element Model
From: rfc-editor@rfc-editor.org
Message-Id: <20100319021814.8DF7FE0764@rfc-editor.org>
Date: Thu, 18 Mar 2010 19:18:14 -0700 (PDT)
Cc: forces@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 19 Mar 2010 02:18:05 -0000

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

        RFC 5812

        Title:      Forwarding and Control Element Separation 
                    (ForCES) Forwarding Element Model 
        Author:     J. Halpern, J. Hadi Salim
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    jmh@joelhalpern.com, 
        Pages:      134
        Characters: 301491
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-forces-model-16.txt

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

This document defines the forwarding element (FE) model used in the
Forwarding and Control Element Separation (ForCES) protocol.  The
model represents the capabilities, state, and configuration of
forwarding elements within the context of the ForCES protocol, so
that control elements (CEs) can control the FEs accordingly.  More
specifically, the model describes the logical functions that are
present in an FE, what capabilities these functions support, and how
these functions are or can be interconnected.  This FE model is
intended to satisfy the model requirements specified in RFC 3654. 

This document is a product of the Forwarding and Control Element Separation 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

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