Distributed Scheduling Protocol (chronos) Concluded WG
Note: The data for concluded WGs is occasionally incorrect.
|WG||Name||Distributed Scheduling Protocol|
|Area||Applications Area (app)|
|Dependencies||Document dependency graph (SVG)|
Charter for Working Group
The Chronos protocol Working Group is chartered to define a
protocol for the management of calendars, appointments and schedules
over the Internet. In defining this protocol, several questions must
be addressed. The role of the calendar administrator must be defined.
Differing levels of security need to be specified to allow maximum
functionality yet still allow privacy and flexibility. The scope of
the protocol should also be evaluated; how much burden should we put
on the server, on the client? Additionally the behavior of multiple
chronos servers must be analyzed.
This protocol should be able to be developed and stabilized
within 6-8 months, since there is already a draft specification to work
from. The process is subject to extension if many new features are
added, or more revision is needed.
|Jul 1991||Revise document based on implementations. Ask IESG to make the revision a Draft Standard.|
|Mar 1991||Spring IETF meeting. Review final draft and if OK, give to IESG for publication as RFC. Begin implementations.|
|Feb 1991||Make document an Internet Draft. Continue revisions based on comments received over e-mail.|
|Jan 1991||Review first draft document, determine necessary revisions. Follow up discussion will occur on mailing list. Prototype implementations.|