[Home] [Charter] [Drafts] [Morgue] [Last Call Info] [Meetings] [Design Teams] [Issues] [Mailing List]
[Closed Discussion Topics | Expired Drafts | Old News]
Framework Handling of
Multicast
There have been several comments on the list about a unicast focus in draft-forces-framework-07.txt. The authors have been asked to revise the framework in order to speak to unicast and multicast protocol solutions to ForCES equally well. After some revisions the Framework has been updated to cover multicast and unicast more completely.
Status: Closed.
CE/FE Closeness
The issue of CE/FE closeness and whether ForCES would focus on
"close" scenarios or "very close" scenarios has been
discussed on the list and the consensus was around a focus on "very
close" scenarios. For more information see the
issue summary.
High Availability
draft-ietf-forces-requirements-02.txt
contained wording specifying a requirement for support of "high
availability." This wording was criticized as too vague and open to
interpretation. Section 5 item 7 and section 7 where reworded in draft-ietf-forces-requirements-03.txt
to instead mention a requirement for CE redundancy and failover support. For
more information see the
issue summary.
Related discussion threads: 1
2
The following table lists drafts previously presented in the ForCES working group that have expired. Current drafts can be found in the drafts repository.
|
# |
Draft Title |
Token |
Status |
Pub |
Exp |
Propose |
Submit |
Charter |
Charter |
Design |
Track |
Type |
|
1 |
Authors |
expired |
Jul01 |
Jan02 |
|
|
|
requirements |
|
info |
requirements |
|
|
2 |
Authors |
Proceed as individual. |
Feb02 |
Aug02 |
|
|
|
model |
|
info |
spec |
|
|
3 |
Authors |
expired |
Nov01 |
Apr02 |
|
|
|
model |
|
info |
model |
|
|
4 |
Authors |
Reviewed by WG. To be
considered as work item in the future after protocol and model progress
further. |
Jun03 |
Dec03 |
|
|
|
not yet charter work item |
|
info |
req |
|
|
5 |
Authors |
Presented to WG. Authors
asked to collaborate with model team. |
Jun03 |
Dec03 |
|
|
|
model |
|
info |
req |
|
|
6 |
Authors |
Presented to WG. Incorporated
concepts into framework & model documents. |
Aug03 |
Dec03 |
|
|
|
model |
|
info |
req |
|
|
7 |
WG |
Incorporated into model. |
Oct03 |
Mar04 |
|
|
|
model |
|
info |
req |
|
|
8 |
WG |
Reviewed, WG decided to
propose a merged draft. |
Dec03 |
Jun04 |
|
|
|
protocol |
|
info |
eval |
|
|
9 |
WG |
Reviewed, WG decided to
make alternate draft a WG item. |
Jun04 |
Dec04 |
|
|
Mar03 |
Protocol |
|
std |
spec |
|
|
10 |
WG |
Merged with draft that
became ForCES protocol working group draft. |
Jul04 |
Jan05 |
|
|
Mar03 |
Protocol |
|
std |
spec |
|
|
11 |
WG |
Merged with draft that
became ForCES protocol working group draft. |
Nov03 |
May04 |
|
|
Mar03 |
protocol |
|
std |
spec |
|
|
12 |
WG |
Merged with draft that
became ForCES protocol working group draft. |
Oct03 |
Apr04 |
|
|
Mar03 |
protocol |
|
std |
spec |
|
|
13 |
WG |
Merged with draft that
became ForCES protocol working group draft. |
May04 |
Sep04 |
|
|
Mar03 |
protocol |
|
std |
spec |
02/17/2004 The ForCES Model has received numerous updates. 1
02/09/2004 The ForCES Framework has been approved for publication as an RFC. 1
02/04/2004 A call for agenda items has been sent out for the ForCES meeting at IETF 59.
01/23/2004 The working group chairs have suggested that a merger protocol proposal be put forward, and are considering an interim meeting to facilitate this. 1
01/21/2004 The ForCES Framework has been forwarded to the IESG for review. 1
01/19/2004 A new transport protocol proposal for ForCES, draft-maloy-tipc-00.txt, has been uploaded to the IETF. 1
01/16/2004 An early preview of the FE capabilities and attributes section of the upcoming revision to the ForCES model draft has been sent to the list for review. 1
01/14/2004 A new revision of the ForCES Framework has been uploaded in response to comments received during the previous last call. This is the last chance for final review before this document is requested for publication as an RFC. Please comment by January 20 if any further changes are necessary. 1 2
01/05/2004 The last call for the ForCES Framework received several comments which are being addressed through a new revision of the ForCES framework which will be uploaded soon.
12/17/2003 A new revision of the ForCES Framework has been uploaded in response to IESG comments. A last call has been initiated to review these and all other changes made over the last few revisions – please comment by January 5. 1 2
12/16/2003 The configuration of the ForCES mailing list has been changed to default to replying to the sender. Reply-To-All should be used if one wants to reply to the ForCES list as well. 1
12/11/2003 The ForCES protocol evaluation draft has been revised with new material from Netlink2 and updated material from GRMP and FACT. Please review this document as the WG is now in the process of protocol selection. 1
10/28/2003 The ForCES Protocol Evaluation has been revised with new information provided by the protocol proposal teams. 1
10/24/2003 The ForCES Framework has been revised in response to IESG feedback.
10/14/2003 Protocol authors may choose to provide text for the protocol evaluation draft in anticipation of presenting at the upcoming (Minneapolis) IETF, but must do so by October 23. 1
Updated October 21, 2004.