[JDEV] IETF Progress

[Thomas D. Charron]

  There are many people who have hashed out protocols that meet the specs for the 'standards', but what will win out is the question..  There are also many, MANY ways to implement the RFC that currently is in place, but the one that I wonder about the most is the ability to have an 'independent namespace'..  So far, as far as I've seen, Jabber is the only protocol that meets this requirment..

---
Thomas Charron

On Fri, 6 Aug 1999 13:55:15    Benjamin Kahn wrote:
>
>	Actually, from what I understand of IETF processes, they are quite
>close to a standard protocol.  A lot of time is spent on the model and the
>requirements.  But then people go off and produce sample implimentations.
>Like Jabber!  
>
>	Of course, I could be wrong.  I knew that several people are
>producing sample implimentations. based on the spec fso far.
>
>
>On Fri, 6 Aug 1999, Thomas D. Charron wrote:
>
>> Date: Fri, 06 Aug 1999 10:35:49 -0700
>> From: Thomas D. Charron <tcharron at my-deja.com>
>> Reply-To: jdev at jabber.org
>> To: jdev at jabber.org
>> Subject: Re: [JDEV] My evil plans for a client.
>> 
>>   As said before, the IETF IMPP HAS NO PROTOCOL as of yet..  I'm putting money on Microsoft getting theirs in as standard, and I wouldn;t count on that for about a year or so..  Technically speaking, the current Jabbe rprotocol could be implemented to meet all IMPP requirements, and be called a 'standard protocol'..
>> ---
>> Thomas Charron
>> 
>> On Fri, 6 Aug 1999 12:15:59    arh14 wrote:
>> >
>> >
>> >On Fri, 6 Aug 1999, Tim Lesher wrote:
>> >
>> >> Scott Robinson <scott at tranzoa.com> said:
>> >> 
>> >> > But back into reality, I'd love to make another suggestion for client fun.
>> >> > MIME support! Messages encoded in MIME (and the clients have a rudimentery
>> >> > (sp?) mailcap) could allow for a whole new world of kick-ass messenging.
>> >> 
>> >> The IETF proposal for instant messaging already calls for MIME support.
>> >> 
>> >> Which brings up an interesting question:  Are any Jabberites tracking the
>> >> IETF efforts?
>> >
>> >That is my question too.  The purpose of Jabber was so that we could stop 
>> >being shot in the foot by proprietary lock-out.  We should, if not adopt, 
>> >at least enable simply integration with the IETF protocol.  MIME is also 
>> >good...it has already done all the encoding and transfer work...we can 
>> >just fill <message>s with MIME and not care.
>> >
>> >Aaron
>> >
>> >> 
>> >> > As for my 3l1t3 soon be started client... keep looking for it.
>> >> 
>> >> Evil?  Scott, you're quasi-evil... ( :-)
>> >> 
>> >> --
>> >> Tim Lesher
>> >> mailto:timl at epix.net
>> >
>> >_______________________________________________
>> >jdev mailing list
>> >jdev at jabber.org
>> >http://mailman.jabber.org/listinfo/jdev
>> >
>> 
>> 
>> --== Sent via Deja.com http://www.deja.com/ ==--
>> Share what you know. Learn what you don't.
>> 
>> _______________________________________________
>> jdev mailing list
>> jdev at jabber.org
>> http://mailman.jabber.org/listinfo/jdev
>> 
>
>						-Ben
>
>------------------------------------ |\      _,,,--,,_  ,) ----------
>Benjamin Kahn                        /,`.-'`'   -,  ;-;;'
>(212) 924 - 2220 ext 201            |,4-  ) )-,_ ) /\
>ben at cybersites.com --------------- '---''(_/--' (_/-' ---------------
>     If at first you don't succeed, skydiving may not be for you.
>
>
>
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mailman.jabber.org/listinfo/jdev
>


--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.