1. Discussion for Compatibility

2. Common Recognition Data transport protocol in e-VLBI is ONLY important for realtime e-vlbi. Data (FILE) format is important generally. –Protocol and Data format may be discussed separately. IP(L3) will be the base of common protocol rather than L2(Ethernet,SDH(ATM)). UDP will be suitable than TCP for the requirement of VLBI. VLBI data stream is not appropriate for dynamical rate control, basically.

3. Compatibility Issues Data protocol –Packet header format –Transaction (UDP or UDP/TCP tandem) Data format –Mark5B, just raw data, or any other Common available Observation modes

4. Data transport protocol direction Independent from the particular format of DAS. It should covers possible usage as much as possible. Simplest way as possible. We may upgrade its version in future if some missing functions were found.

5. Data protocol EVN/JIVE, ATNF Sequential Nmber 132 Data frame Mark5C

6. A tentative proposal for consensus. Data transport protocol Sequential Number 132 Data frame(Mark5B,raw data) Time tag (sec. since 1990) Format –Header part will be in network byte order. Transaction –Just sending UDP packet with UDP –Data length or packet size may be informed to receiver by other way. Ver.Stream ID

7. Publication of the standard format Writing specification description. On the Webpage of a institute? IVS? EVN? Simple sample software (receiver/sender) on the web as example? Ad hoc small group to do that?