My idea was to make the IP protocol a superset of existing musical protocols.
 The basic format would have:

a timestamp
a packet size
a data identifier
a data area

	If the data identifier were MIDI, the a complete MIDI message would be
contained inside the data area.  If it is ZIPI, a ZIPI message would be
contained.  The receiveing app (like csound) could just send the data to the
appropriate place.  When it got a MIDI packet, it would write it directly into
the MIDI input code, as if it had come in from the MIDI interface.
	This way an app can use packets in whatever protocols it supports and discard
the rest.  So in a sense, this defers the format debate.  But is also could
lead to a single hardware interface (your TCP/IP hardware) which could act to
receive all of the possible data formats.
	All of this discussion is of course predicated on real-time control, of which
csound is only beginning to be capable.  But eventually, it could result in a
server/client relationship, which is my reason for doing this with GrainWave.
-- 
Mike Berry
mikeb@nmol.com
http://www.nmol.com/users/mikeb