RFC 7408 on Forwarding and Control Element Separation (ForCES) Model Extension
rfc-editor@rfc-editor.org Mon, 01 December 2014 02:31 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 3C0D91A014A; Sun, 30 Nov 2014 18:31:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.788
X-Spam-Level:
X-Spam-Status: No, score=0.788 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 BRdRfEMMYTBs; Sun, 30 Nov 2014 18:31:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 23A481A00FC; Sun, 30 Nov 2014 18:31:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C4F5718008D; Sun, 30 Nov 2014 18:31:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7408 on Forwarding and Control Element Separation (ForCES) Model Extension
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141201023120.C4F5718008D@rfc-editor.org>
Date: Sun, 30 Nov 2014 18:31:20 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/qjJglsaPAup2KHjdsB9U4yiXi-M
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:31:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7408
Title: Forwarding and Control Element Separation
(ForCES) Model Extension
Author: E. Haleplidis
Status: Standards Track
Stream: IETF
Date: November 2014
Mailbox: ehalep@ece.upatras.gr
Pages: 31
Characters: 62348
Updates: RFC5812
I-D Tag: draft-ietf-forces-model-extension-05.txt
URL: https://www.rfc-editor.org/rfc/rfc7408.txt
This memo extends the Forwarding and Control Element Separation
(ForCES) model defined in RFC 5812 and updates that RFC to allow
complex data types for metadata, optional default values for data
types, and optional access types for structures. It also fixes an
issue with Logical Functional Block (LFB) inheritance and introduces
two new features: a new event condition called eventBecomesEqualTo
and LFB properties. The changes introduced in this memo do not alter
the protocol and retain backward compatibility with older LFB models.
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