ForCES Drafts and RFCs

[Home] [Charter] [Drafts & RFCs] [Morgue] [Last Call Info] [Meetings] [Design Teams] [Issues] [Mailing List]

 

The following table lists the current drafts within the ForCES working group, with working group drafts listed first, followed by individual contributions. Dead drafts can be found in the morgue. ForCES RFCs appear at the bottom of this page.

 

#

Draft Title

Token

Status

Pub
date

Exp
date

Propose
WGLC

Submit
to
IESG

Charter
Goal

Charter
Task

Design
Team

Track

Type

1

draft-ietf-forces-applicability-02.txt

WG
(hold)

Document on backburner until protocol selected & model reaches maturity.

Jun02

Dec03

 

 

Jun03

applicability

 

info

usage

2

draft-ietf-forces-model-04.txt

WG
(review)

Authors working on new revision -02 for IETF 59.

Feb05

Aug05

 

 

 Nov02

model

 

info

req

3

draft-ietf-forces-protocol-02.txt

WG
(review)

WG needs to review. Last call expected soon.

Feb05

Aug05

 

 

Mar03

protocol

 

std

spec

3

draft-ansari-forces-discovery-01.txt

WG
(review)

Discovery protocol proposal for ForCES CE and FE binding and discovery.

Oct04

Apr05

 

 

 

 

 

std

spec

4

draft-audu-forces-iptml-00.txt

WG
(review)

ForCES TML Protocol proposal. Needs WG review to determine if acceptable as a WG document.

Oct04

Apr05

 

 

Mar03

Protocol

 

std

spec

5

draft-blake-forces-attrib-00.txt

WG
(review)

Proposed changes to ForCES model. Needs WG feedback as to whether to adopt changes.

Jul04

Jan05

 

 

Mar03

Model

 

info

spec

6

draft-khosravi-forces-tcptml-01.txt

WG
(review)

ForCES TML Protocol proposal. Needs WG review to determine if acceptable as a WG document.

Feb05

Aug05

 

 

Mar03

protocol

 

std

spec

7

draft-maloy-tipc-01.txt

WG
(review)

New proposal for transport protocol to use for ForCES in clusters.

Oct04

Apr05

 

 

 

protocol

 

std

spec

 

The follow table lists RFCs by the ForCES working group.

#

RFC Title

Status

Pub
date

Track

Type

1

RFC 3549 – Linux Netlink as an IP Services Protocol

Informational draft documenting relevant prior art.

July 2003

informational

Prior art

2

RFC 3654 – Requirements for Separation of IP Control and Forwarding

Informational draft specifying requirements for ForCES framework, model, and protocols.

November 2003

informational

Requirements

3

RFC 3746 – Forwarding and Control Element Separation (ForCES) Framework

Informational draft specifying architecture and entities that comprise a ForCES network element

April 2004

informational

Framework

 

Updated February 23, 2005.