While it would be good to be compatible with IETF standards I'm not sure how applicable they are: OSC doesnt have sessions or streams per se and it has almost no semantics.
Also it would be a great advantage if service discovery could be done only using the OSC protocol - for compatability with existing implmentations. The offer/answer stuff might be relevant, if we can come up with an equivalent encoding in OSC messages. - Steve On Mon, Jan 26, 2004 at 02:58:30 -0800, John Lazzaro wrote: > Hi everyone, > > Just wanted to put in a plug for IETF-based solutions > to doing service discovery for OSC -- basically, this would > entail using SIP: > > http://www.ietf.org/rfc/rfc3261.txt > > for session management, and SDP: > > http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-15.txt > > to describe the sessions themselves. To specify OSC > in SDP, you'd use UDP or TCP as a transport specifier on > the media line, and make up (and eventually, register) a "fmt" > parameter for OSC. > > One of the things I'm planning to do now that RTP MIDI > is finally nearing Last Call is to look at session management > frameworks for RTP MIDI that would use SIP + SDP. If OSC > went this route too, applications could use the Offer/Answer > protocol: > > http://www.ietf.org/rfc/rfc3264.txt > > to negotiate to use MIDI (for baseline support) or OSC > (to do more sophisticated things). This was one of the > motivations behind RTP MIDI -- to offer a migration path > from MIDI, without requiring backward-compatibility between > control languages ... > > --- > John Lazzaro > http://www.cs.berkeley.edu/~lazzaro > lazzaro [at] cs [dot] berkeley [dot] edu > ---
