datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) Library
draft-ietf-forces-lfb-lib-12

Approval Announcement

Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    forces mailing list <forces@ietf.org>,
    forces chair <forces-chairs@tools.ietf.org>
Subject: Protocol Action: 'ForCES Logical Function Block (LFB) Library' to Proposed Standard (draft-ietf-forces-lfb-lib-12.txt)

The IESG has approved the following document:
- 'ForCES Logical Function Block (LFB) Library'
  (draft-ietf-forces-lfb-lib-12.txt) as Proposed Standard

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

The IESG contact persons are Adrian Farrel and Stewart Bryant.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-forces-lfb-lib/



Technical Summary

   This document defines basic classes of Logical Function Blocks (LFBs)
   used in the Forwarding and Control Element Separation (ForCES).  The
   basic LFB classes are defined according to ForCES FE model and ForCES
   protocol specifications, and are scoped to meet requirements of
   typical router functions and considered as the basic LFB library for
   ForCES.  The library includes the descriptions of the LFBs and the
   XML definitions.

Working Group Summary: 

  Standard WG discussions, nothing controversial. 
  The document was returned to the authors after AD review. The issues
  were addressed in public on the WG mailing list.

Document Quality: 

  There are known implementations of this document. 

  Version 00 of this document was published in 2009 and has
  undergone feedback based on implementation and architecture
  discussion. 

Personnel: 

  Jamal Hadi Salim (hadi@mojatatu.com) is the Document Shepherd
  Adrian Farrel (adrian@olddog.co.uk) is the Responsible AD

RFC Editor Note

  The three unused references may be safely removed.

  Please make RFC 2119 a Normative Reference