[forces] RFC 7391 on Forwarding and Control Element Separation (ForCES) Protocol Extensions

rfc-editor@rfc-editor.org Fri, 31 October 2014 23:31 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F131A874D; Fri, 31 Oct 2014 16:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.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, USER_IN_WHITELIST=-100] 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 PYxAKE7SXa4H; Fri, 31 Oct 2014 16:31:48 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id C7F401A874A; Fri, 31 Oct 2014 16:31:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 66133181C91; Fri, 31 Oct 2014 16:30:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141031233056.66133181C91@rfc-editor.org>
Date: Fri, 31 Oct 2014 16:30:56 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/forces/ocnDFjLUmphJlWgBf-K254D3alE
Cc: forces@ietf.org, rfc-editor@rfc-editor.org
Subject: [forces] RFC 7391 on Forwarding and Control Element Separation (ForCES) Protocol Extensions
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces/>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2014 23:31:51 -0000

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

        
        RFC 7391

        Title:      Forwarding and Control Element Separation 
                    (ForCES) Protocol Extensions 
        Author:     J. Hadi Salim
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2014
        Mailbox:    hadi@mojatatu.com
        Pages:      23
        Characters: 49481
        Updates:    RFC 5810, RFC 7121

        I-D Tag:    draft-ietf-forces-protoextension-06.txt

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

Experience in implementing and deploying the Forwarding and Control
Element Separation (ForCES) architecture has demonstrated the need
for a few small extensions both to ease programmability and to
improve wire efficiency of some transactions.  The ForCES protocol is
extended with a table range operation and a new extension for error
handling.  This document updates the semantics in RFCs 5810 and 7121
to achieve that end goal.

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