> I feel that what's needed is an internet > protocol that isn't mean't to share data > between programs, but is the protocol with > which data is shared. To my knowledge, those > protocols have have made no effort to include > location scheduling, groups, etc.
One of the key aspects of the IETF process is that anyone can participate. If you have concerns about the direction of the calendaring work and feel you have ideas and maybe even elbow grease to contribute, you should sign up on the appropriate mailing list(s) and participate.
If the current calendaring work looks like only entrenched vendors are designing it, that may be essentially what is happening (I personally don't know). It takes the participation of different folks with different perspectives in order to balance out a workng group's direction(s).
The IETF has built a robust infrastructure for open development of Internet protocols -- I strongly encourage anyone who is entertaining development of a multi-vendor IP-based protocol to carry it forward within the IETF framework so that we all can beneit from it.
Jeff http://www.stanford.edu/~hodges/ http://www.KingsMountain.com/
Before you run off and start doing any of your own things, I urge you to carefully review the current internet-drafts and RFCs produced by this group as well as review the working group's mailing list archive (which is available via the IMC-hosted page pointed-to above).
~Anyone~ is welcome to participate in the IETF. If you have ideas and cycles to contribute to this avenue, then you're definitely encouraged to get involved.
Note that by definition, IETF protocol standards are OPEN. Implementations are often open-source. For any protocol standard to progress beyond the "proposed standard" maturity level, there must be > 1 ~interoperable~ implementations. See this page..
Slashdot Mirror
> I feel that what's needed is an internet
> protocol that isn't mean't to share data
> between programs, but is the protocol with
> which data is shared. To my knowledge, those
> protocols have have made no effort to include
> location scheduling, groups, etc.
One of the key aspects of the IETF process is that anyone can participate. If you have concerns about the direction of the calendaring work and feel you have ideas and maybe even elbow grease to contribute, you should sign up on the appropriate mailing list(s) and participate.
If the current calendaring work looks like only entrenched vendors are designing it, that may be essentially what is happening (I personally don't know). It takes the participation of different folks with different perspectives in order to balance out a workng group's direction(s).
The IETF has built a robust infrastructure for open development of Internet protocols -- I strongly encourage anyone who is entertaining development of a multi-vendor IP-based protocol to carry it forward within the IETF framework so that we all can beneit from it.
Jeff
http://www.stanford.edu/~hodges/
http://www.KingsMountain.com/
There is definitely on-going work in the IETF (www.ietf.org) on Calendaring and scheduling. This page..
r .html
a ndardsProcess.html
http://www.imc.org/ietf-calendar/
..is indeed the key resource. Closely following that is the "calsch" working group's "charter page"..
http://www.ietf.org/html.charters/calsch-charte
Before you run off and start doing any of your own things, I urge you to carefully review the current internet-drafts and RFCs produced by this group as well as review the working group's mailing list archive (which is available via the IMC-hosted page pointed-to above).
~Anyone~ is welcome to participate in the IETF. If you have ideas and cycles to contribute to this avenue, then you're definitely encouraged to get involved.
Note that by definition, IETF protocol standards are OPEN. Implementations are often open-source. For any protocol standard to progress beyond the "proposed standard" maturity level, there must be > 1 ~interoperable~ implementations. See this page..
http://www.KingsMountain.com/LDAPRoadmap/IETFSt
..for info about "IETF Document Series and How Standing is Denoted".
If you've never participated in the IETF and are curious about how to get started, take a look at..
http://www.ietf.org/join.html
http://www.ietf.org/newcomer/index.htm
http://www.ietf.org/tao.html
Jeff
http://www.stanford.edu/~hodges/