RE: (#317) Re: protocol documentation project (Re: Speak Free

"Wm. Burke \(HQ\)" <[email protected]>
Newsgroups gmane.comp.audio.speak-freely.general
Message-ID <[email protected]>
John.

Could you reply to me off-list, when you have a moment?

[email protected]



-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Speak Freely
Forum
Sent: August 01, 2003 9:31 AM
To: [email protected]
Subject: [speak-freely] (#317) Re: protocol documentation project
(Re:
Speak Free


Message posted to the Speak Freely Forum
  by John Walker on Fri, 1 Aug 2003 15:30:53 +0200 (MEST).
  http://www.fourmilab.ch/wb/speak-freely.pl?rev=317

  Reply To: (#315) protocol documentation project (Re: Speak
Freely E
  Author:   Johannes Po....
  Date:     2003-08-01 15:11

: Forwarded from the [email protected]
: mailing list: I would ask other interested
: developers to start a "reverse
: engineering"
: project of Speak freely producing a protocol
: documentation.

I would be happy to review a protocol document. In fact, I will
agree to write
such a protocol document and post it on SourceForge before January
15th, 2004
if nobody else does. I don't think there is any reason to document
the RTP
support, as that is thoroughly documented in RFCs 1889 and
1890--simply
stating which transport encodings Speak Freely supports is
sufficient. The
actual
Speak Freely protocol is very simple--the only tricky part is how
the various
compression modes are stuffed into the packets and how packets are
padded when
encryption is used. The control packets and information sent to
the LWL server
are RTP-compliant regardless of which protocol is used.


                      * * *

To unsubscribe from this mailing list, send E-mail containing
the word "unsubscribe" in the message body (*not* as the
Subject) to [email protected]


                      * * *

To unsubscribe from this mailing list, send E-mail containing
the word "unsubscribe" in the message body (*not* as the
Subject) to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.