From rem-conf-request@es.net Mon Nov 01 11:33:49 1993 Received: from hplb.hpl.hp.com by osi-east.es.net via ESnet SMTP service id <12255-0@osi-east.es.net>; Mon, 1 Nov 1993 08:20:23 +0000 Received: from morse.hpl.hp.com by hplb.hpl.hp.com; Mon, 1 Nov 93 16:08:13 GMT Message-Id: <9311011608.AA11334@hplb.hpl.hp.com> To: rem-conf@es.net Cc: pink@hplb.hpl.hp.com Subject: no SD advertisements of IETF sessions Date: Mon, 01 Nov 93 16:17:37 GMT From: Stephen Pink I have lost the sd session advertisements for both IETF channels and can't get them back. Everyone at my site is having this problem. We got them before 1500 GMT and lost them shortly afterwards. Anyone know what the problem is? Steve Pink From rem-conf-request@es.net Mon Nov 01 13:03:36 1993 Received: from brazos.is.rice.edu by osi-east.es.net via ESnet SMTP service id <13473-0@osi-east.es.net>; Mon, 1 Nov 1993 09:52:45 +0000 Received: by brazos.is.rice.edu (AA23289); Mon, 1 Nov 93 11:52:19 CST From: bmanning@is.rice.edu (William Manning) Message-Id: <9311011752.AA23289@brazos.is.rice.edu> Subject: Re: no SD advertisements of IETF sessions To: pink@hplb.hpl.hp.com (Stephen Pink) Date: Mon, 1 Nov 1993 11:52:19 -0600 (CST) Cc: rem-conf@es.net, pink@hplb.hpl.hp.com In-Reply-To: <9311011608.AA11334@hplb.hpl.hp.com> from "Stephen Pink" at Nov 1, 93 04:17:37 pm X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 376 We had not put up the lable on the ietf28 tunnel machine and a friendly attendee logged the machine out & in.. The sign is up now. Reception is minimal for the nonce, since we are in Lunch break. -- Regards, Bill Manning bmanning@rice.edu PO Box 1892 713-285-5415 713-527-6099 Houston, Texas R.U. (o-kome) 77251-1892 From rem-conf-request@es.net Mon Nov 01 13:48:30 1993 Received: from is.rice.edu by osi-east.es.net via ESnet SMTP service id <13854-0@osi-east.es.net>; Mon, 1 Nov 1993 10:39:03 +0000 Received: by is.rice.edu (AA15599); Mon, 1 Nov 93 12:39:02 CST From: soren@is.rice.edu (William Soren Deigaard) Message-Id: <9311011839.AA15599@is.rice.edu> Subject: Re: no SD advertisements of IETF sessions To: pink@hplb.hpl.hp.com (Stephen Pink) Date: Mon, 1 Nov 1993 12:35:54 -0600 (CST) Cc: rem-conf@isi.edu In-Reply-To: <9311011608.AA11334@hplb.hpl.hp.com> from "Stephen Pink" at Nov 1, 93 04:17:37 pm X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 622 Sender: soren@is.rice.edu We had a little problem where ietf28 was logged out of the tunnel machine where the sessions were created. We took care of it, so you should be seeing the sessions now. Sorry for the interruption. > > > I have lost the sd session advertisements for both IETF channels and > can't get them back. Everyone at my site is having this problem. We > got them before 1500 GMT and lost them shortly afterwards. Anyone > know what the problem is? > > Steve Pink > > -- William Deigaard ^-^ (soren@rice.edu) (O O) Go Owls! ( v ) ---------------------m-m--- Owlnet System Programmer, Rice University From rem-conf-request@es.net Mon Nov 01 17:57:30 1993 Received: from venera.isi.edu by osi-east.es.net via ESnet SMTP service id <16960-0@osi-east.es.net>; Mon, 1 Nov 1993 14:49:12 +0000 Received: from xfr.isi.edu by venera.isi.edu (5.65c/5.61+local-13) id ; Mon, 1 Nov 1993 14:49:06 -0800 Posted-Date: Mon 1 Nov 93 14:48:22 PST Received: by xfr.isi.edu (4.1/4.0.3-4) id ; Mon, 1 Nov 93 14:48:23 PST Date: Mon 1 Nov 93 14:48:22 PST From: Stephen Casner Subject: How's the reception of IETF? To: rem-conf@es.net, MBONE@ISI.EDU Message-Id: <752194102.0.CASNER@XFR.ISI.EDU> Mail-System-Version: I have not seen any feedback about the quality and connectivity of the multicast from IETF. Let us know. -- Steve ------- From rem-conf-request@es.net Mon Nov 01 19:04:39 1993 Received: from Crazypete.AI.SRI.COM by osi-east.es.net via ESnet SMTP service id <17758-0@osi-east.es.net>; Mon, 1 Nov 1993 15:55:05 +0000 Received: by Crazypete.AI.SRI.COM (930416.SGI/SMI-4.1) id AA03047 for rem-conf@es.net; Mon, 1 Nov 93 15:54:59 -0800 Message-Id: <9311012354.AA03047@Crazypete.AI.SRI.COM> To: Stephen Casner Cc: rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-Reply-To: Your message of "Mon, 01 Nov 1993 14:48:22 PST." <752194102.0.CASNER@XFR.ISI.EDU> Date: Mon, 01 Nov 1993 15:54:59 -0800 From: Stephen Lau The overhead slides are difficult to read at times, especially when the speaker is writing. It appears as though Channel 1 is being broadcast in grayscale so the writing appears gray and is sometimes difficult to pick out from the background. Steve ------------------------------------------------------------------------------- Stephen Lau lau@ai.sri.com| "We take your bags and send them SRI International | in all directions." 333 Ravenswood Ave., Menlo Park, CA. 94025| - Sign in Copenhagen airline (415) 859-2925 (415) 326-6200| ticket office ------------------------------------------------------------------------------- From rem-conf-request@es.net Mon Nov 01 23:11:12 1993 Received: from mvs.oac.ucla.edu by osi-east.es.net via ESnet SMTP service id <19327-0@osi-east.es.net>; Mon, 1 Nov 1993 20:03:20 +0000 Received: from UCLAMVS.BITNET by MVS.OAC.UCLA.EDU (IBM MVS SMTP V2R2.1) with BSMTP id 1831; Mon, 01 Nov 93 20:03:11 PST Date: Mon, 01 Nov 93 20:02 PST To: rem-conf@ES.NET, MBONE@ISI.EDU From: Denis DeLaRoca (310) 825-4580 Subject: Re: How's the reception of IETF? It's been generally very good for me, most sound quality problems seem due to how mikes are set/used... the replay of the morning ple- nary featured a background hum... the live afternoon sessions all came very clear... the video seemed much better that last week's Xerox Park seminar but that may be due to the higher frame rate I am seeing. Two major problems. The slides are hard, if not impossible, to read on the video display... doubling image size makes this Sparc LX run cpu bound so I usually stay with normal image size. Perhaps a WhiteBoard session could get around the problem of the slides... The other problem that showed up this afternoon during the mmusic session was when an MBONE conference participant intervened, his audio would break in at an excruciatingly high level... later he had a conver- sation with another participant and had to adjust his gain to make that possible... I suppose VAT can't do much to deal with this situation, can't it? If somebody transmits at a high level they can literally blast your speaker and ear, does the AGC control help on this? -- Denis From rem-conf-request@es.net Tue Nov 02 00:43:30 1993 Received: from munin.fnal.gov by osi-east.es.net via ESnet SMTP service id <19659-0@osi-east.es.net>; Mon, 1 Nov 1993 21:38:25 +0000 Received: from LOCALHOST.fnal.gov by munin.fnal.gov with SMTP id AA06106 (5.65c+/IDA-1.4.4 for rem-conf@es.net); Mon, 1 Nov 1993 23:39:22 -0600 Message-Id: <199311020539.AA06106@munin.fnal.gov> To: Denis DeLaRoca 825-4580 (310) Cc: rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-Reply-To: Your message of Mon, 01 Nov 93 20:02:00 PST. <01H4TFRJ70C200GRH7@FNAL.FNAL.GOV> Date: Mon, 01 Nov 93 23:39:22 -0600 From: Matt Crawford > It's been generally very good for me, most sound quality problems > seem due to how mikes are set/used... the replay of the morning ple- > nary featured a background hum... The *room* had a background hum. It almost knocked me over as soon as I walked in. Matt From rem-conf-request@es.net Tue Nov 02 01:35:10 1993 Received: from noc.unt.edu by osi-east.es.net via ESnet SMTP service id <19930-0@osi-east.es.net>; Mon, 1 Nov 1993 22:28:16 +0000 Received: by noc.unt.edu (4.1/SMI-4.1) id AA07960; Tue, 2 Nov 93 00:28:01 CST Date: Tue, 2 Nov 1993 00:21:53 -0600 (CST) From: Darren Paul Loher Subject: Re: How's the reception of IETF? To: "Denis DeLaRoca (310) 825-4580" Cc: rem-conf@es.net, MBONE@ISI.EDU In-Reply-To: <199311020431.AA00749@mercury.unt.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 1 Nov 1993, Denis DeLaRoca (310) 825-4580 wrote: > Two major problems. The slides are hard, if not impossible, to read > on the video display... doubling image size makes this Sparc LX > run cpu bound so I usually stay with normal image size. Perhaps a > WhiteBoard session could get around the problem of the slides... Changing to gray scale can help this... but yes, I must agree. They were very hard to read. > The other problem that showed up this afternoon during the mmusic > session was when an MBONE conference participant intervened, his audio > would break in at an excruciatingly high level... later he had a conver- > sation with another participant and had to adjust his gain to make that > possible... I suppose VAT can't do much to deal with this situation, > can't it? If somebody transmits at a high level they can literally blast > your speaker and ear, does the AGC control help on this? > > -- Denis During the URI meeting, in the conference room it was nearly impossible to understand the man at CERN who was talking to us. I am not sure if the sound qaulity was bad due to his mike level or network level problems. -- Darren Loher University of North Texas darren@unt.edu Datacommunications 214-565-4168 From rem-conf-request@es.net Tue Nov 02 03:30:08 1993 Received: from gmdzi.gmd.de by osi-east.es.net via ESnet SMTP service id <20492-0@osi-east.es.net>; Tue, 2 Nov 1993 00:29:28 +0000 Received: from bagheera.gmd.de (bagheera) by gmdzi.gmd.de with SMTP id AA06952 (5.65c8/IDA-1.4.4 for ); Tue, 2 Nov 1993 09:27:40 +0100 Received: from localhost.gmd.de by bagheera.gmd.de with SMTP id AA00441 (5.65c/IDA-1.4.4); Tue, 2 Nov 1993 09:29:12 +0100 Message-Id: <199311020829.AA00441@bagheera.gmd.de> To: Stephen Casner Cc: rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-Reply-To: Your message of "Mon, 01 Nov 93 14:48:22 PST." <752194102.0.CASNER@XFR.ISI.EDU> Date: Tue, 02 Nov 93 09:29:10 +0100 From: Willi.Porten-Herzig@gmd.de > I have not seen any feedback about the quality and connectivity of > the multicast from IETF. Let us know. > -- Steve > ------- The speakers are good to understand. The real problem with speakers is that you only know who is speaking if you know the guys from other IETF meetings personally...... What really would help is if somebody would put the speakers name either into the vat line which now shows 'IETF 28 Channel x Audio' or into the NV top line which now shows 'IETF 28 Channel x Video' (best would be to put it into nv). The slides are hard to read. One problem with the todays broadcasted video (that I am currently getting about IPng) is that the camera does not get the text lines in total horizontal direction. Would be nice if this could be changed for more readibility. All in all the part of the MBONE that I am using today in a good shape in terms of quality (packet loss,...). Packet loss is normally <= 5% to my side in Germany which is acceptable for audio. Well this at the morning of my time. See what happens when the other non MBONE croud is using their internet....... -- Willi -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Willi Porten-Herzig GGGGG M M DDDDDD Email: porten-herzig@gmd.de GeNeRIC.DFNNOC G G MM MM D D Tel. + 49 2241/ 14 3190 GMD (German National G M M M M D D FAX + 49 2241/ 14 3002 Research Center for G GGGG M M M D D Computer Science) G G M M D D Anything regarding DFN-IP Rathausallee 10 G G M M D D email to 'dfn-noc@gmd.de' D-53757 Sankt Augustin GGGGG M M DDDDDD and never personally to me! From rem-conf-request@es.net Tue Nov 02 03:37:19 1993 Received: from bells.cs.ucl.ac.uk by osi-east.es.net via ESnet SMTP service id <20484-0@osi-east.es.net>; Tue, 2 Nov 1993 00:28:20 +0000 Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Tue, 2 Nov 1993 08:28:06 +0000 To: Stephen Casner , rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-reply-to: Your message of "Mon, 01 Nov 93 15:54:59 PST." <9311012354.AA03047@Crazypete.AI.SRI.COM> Date: Tue, 02 Nov 93 08:28:03 +0000 From: Jon Crowcroft reception in london was pretty good most of the plenary - had to leave then, though can't you arrange ietf's on GMT working days:-) jon i know, i know. GMT is no more. its utc... From rem-conf-request@es.net Tue Nov 02 03:49:06 1993 Received: from bells.cs.ucl.ac.uk by osi-east.es.net via ESnet SMTP service id <20532-0@osi-east.es.net>; Tue, 2 Nov 1993 00:39:06 +0000 Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Tue, 2 Nov 1993 08:38:44 +0000 To: Willi.Porten-Herzig@gmd.de cc: Stephen Casner , rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-reply-to: Your message of "Tue, 02 Nov 93 09:29:10 +0100." <199311020829.AA00441@bagheera.gmd.de> Date: Tue, 02 Nov 93 08:38:42 +0000 From: Jon Crowcroft >All in all the part of the MBONE that I am using today in a good shape >in terms of quality (packet loss,...). Packet loss is normally <= 5% >to my side in Germany which is acceptable for audio. Willi et al why not use this as an opportunity to check out the WOLHE Mbone if you administer an mrouted, get hold of the mrdebug program do a kill -USR1 on your mrouted, and then for ietf source, check out what it says currently the path is (the point of doing this at all sites rather than from one is tocheck if the mrouteds are actually carrying out the algorithms specified in DVMRP and also whether their are bugs in them or in mrdebug...and to see how many people are running pruning versions, and so on etc) if we could agree a time (e.g. UTC 15.15 - half way through the plenary today, tommorow etc, might bw a good time) we might learn a lot and there are not many opportunities to check out both the routing andfdebugging tools what do we say? jon From rem-conf-request@es.net Tue Nov 02 04:53:27 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <20913-0@osi-east.es.net>; Tue, 2 Nov 1993 01:50:49 +0000 Received: from hans.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA18483; Tue, 2 Nov 93 10:50:13 +0100 Message-Id: <9311020950.AA18483@sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 2 Nov 1993 10:50:15 +0100 To: Bob Braden , deering@parc.xerox.com, J.Crowcroft@cs.ucl.ac.uk From: hans@sics.se (Hans Eriksson) Subject: Re: What's missing from the PARC Forum multicasts Cc: rem-conf@es.net >No, No, you aren't taking this seriously enough. PARC needs its OWN >theme, something hummable, so that whenever people hear it, they >instantly associate it with PARC Forum. Like the William Tell >Overture and the Lone Ranger, for example. This gets more and more like radio DX-ing. The shortwave radio station all have a tune so that you know that it them that you tune in. Maybe we can start DX-hunts, where you dial the class-D and tries to find some "radio stations", maybe we can introduce disturbances such as on-the-fly varying ttls, packet losses at the source, remote dynamic mixing, etc... /hans From rem-conf-request@es.net Tue Nov 02 05:03:33 1993 Received: from venera.isi.edu by osi-east.es.net via ESnet SMTP service id <20987-0@osi-east.es.net>; Tue, 2 Nov 1993 02:02:48 +0000 Received: from xfr.isi.edu by venera.isi.edu (5.65c/5.61+local-14) id ; Tue, 2 Nov 1993 02:02:37 -0800 Posted-Date: Tue 2 Nov 93 02:01:53 PST Received: by xfr.isi.edu (4.1/4.0.3-4) id ; Tue, 2 Nov 93 02:01:54 PST Date: Tue 2 Nov 93 02:01:53 PST From: Stephen Casner Subject: Re: How's the reception of IETF? To: lau@ai.sri.com, CASNER@ISI.EDU Cc: rem-conf@es.net, MBONE@ISI.EDU Message-Id: <752234513.0.CASNER@XFR.ISI.EDU> In-Reply-To: <9311012354.AA03047@Crazypete.AI.SRI.COM> Mail-System-Version: Thanks to those of you who responded. The information is helpful. To Steve Lau, we decided to try sending the slides in grayscale because that will improve the displayed resolution on 8-bit displays that have to dither the color. I agree that the slides are often hard to read. We need people to use 24 point type, and landscape mode so we can zoom in tighter without cutting off the bottom. (matche s video aspect ratio better). -- Steve ------- From rem-conf-request@es.net Tue Nov 02 14:10:15 1993 Received: from nervm.nerdc.ufl.edu by osi-east.es.net via ESnet SMTP service id <24633-0@osi-east.es.net>; Tue, 2 Nov 1993 10:54:17 +0000 Received: from charon.cba.ufl.edu by nervm.nerdc.ufl.edu (IBM VM SMTP V2R2) with TCP; Tue, 02 Nov 93 13:54:13 EDT Received: From CHIP/WORKQUEUE by charon.cba.ufl.edu via Charon 3.4 with IPX id 100.931102135315.320; 02 Nov 93 13:53:28 -0500 Message-ID: To: rem-conf@es.net From: "RICHARD H. HUGHES" Date: Tue, 2 Nov 1993 13:53:12 EST Subject: How to unsubscribe Priority: normal X-mailer: WinPMail v1.0 (R2) How does one unsubscribe to this list. Messages to listserv@es.net bounce back. A message to the list itself did not work. Help!! ====================================================================== Richard H. Hughes Email: HUGHESRH@CHIP.CBA.UFL.EDU Director, CBA Media Center Phone: (904) 392-1426 Ext. 1261 University of Florida Fax: (904) 392-6250 237 Bryan Hall - P.O. Box 117150 Gainesville, FL 32611-1750 From rem-conf-request@es.net Tue Nov 02 15:34:06 1993 Received: from utrhcs.cs.utwente.nl by osi-east.es.net via ESnet SMTP service id <25532-0@osi-east.es.net>; Tue, 2 Nov 1993 12:25:09 +0000 Received: from utis179.cs.utwente.nl by utrhcs (4.1/RBCS-2.6mx) id AA29178; Tue, 2 Nov 93 21:24:59 +0100 Received: by utis179.cs.utwente.nl (4.1/RBCS-1.0.1) id AA01482; Tue, 2 Nov 93 21:24:58 +0100 Message-Id: <9311022024.AA01482@utis179.cs.utwente.nl> To: Stephen Casner Cc: rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-Reply-To: Your message of Tue, 02 Nov 93 02:01:53 -0800 From: Axel Belinfante Organisation: University of Twente, Dept of Informatics, Tele Informatics Group, PO Box 217, NL-7500 AE Enschede, The Netherlands Phone: +31 53 893774 Telefax: +31 53 333815 Date: Tue, 02 Nov 93 21:24:57 +0100 Sender: belinfan@cs.utwente.nl > To Steve Lau, we decided to try sending the slides in grayscale because > that will improve the displayed resolution on 8-bit displays that have > to dither the color. I agree that the slides are often hard to read. > We need people to use 24 point type, and landscape mode so we can zoom > in tighter without cutting off the bottom. (matches video aspect ratio > better). > -- Steve Wouldn't it be possible to use the shared whiteboard? If people would bring postscript versions of their slides.. and then give the presentation (partially?) via the wb program, and use an overhead displayer or so to project the picture in the session room? In the mice demo/lectures a second whiteboard was used for 'control' info (feedback etc). Maybe that might be helpful? Regards, Axel. tel. +31 53 893774 fax. +31 53 333815 University of Twente, Tele-Informatics & Open Systems Group P.O. Box 217 NL-7500 AE Enschede The Netherlands "ili ne sciis ke estas neebla do ili simple faris" -- Loesje From rem-conf-request@es.net Tue Nov 02 15:48:02 1993 Received: from Crazypete.AI.SRI.COM by osi-east.es.net via ESnet SMTP service id <25632-0@osi-east.es.net>; Tue, 2 Nov 1993 12:39:03 +0000 Received: by Crazypete.AI.SRI.COM (930416.SGI/SMI-4.1) id AA05853 for rem-conf@es.net; Tue, 2 Nov 93 12:38:46 -0800 Message-Id: <9311022038.AA05853@Crazypete.AI.SRI.COM> To: Stephen Casner Cc: lau@Sunset.ai.sri.com, rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-Reply-To: Your message of "Tue, 02 Nov 1993 02:01:53 PST." <752234513.0.CASNER@XFR.ISI.EDU> Date: Tue, 02 Nov 1993 12:38:46 -0800 From: Stephen Lau >To Steve Lau, we decided to try sending the slides in grayscale because >that will improve the displayed resolution on 8-bit displays that have >to dither the color. I agree that the slides are often hard to read. I thought that might be case. You might want to give the speakers pens that would show up with higher contrast in grayscale something like blue or black if they're not already using it. Hide the green and red ones. =:) Something else you might want to try is having a camera pointing directly down at the overhead projector instead of at the projection screen. But then we'll be starting to move into the area of making this into a full scale audio-video production with music and lights and mike booms etc. =:) ------------------------------------------------------------------------------- Stephen Lau lau@ai.sri.com| "We take your bags and send them SRI International | in all directions." 333 Ravenswood Ave., Menlo Park, CA. 94025| - Sign in Copenhagen airline (415) 859-2925 (415) 326-6200| ticket office ------------------------------------------------------------------------------- From rem-conf-request@es.net Wed Nov 03 04:08:27 1993 Received: from bells.cs.ucl.ac.uk by osi-east.es.net via ESnet SMTP service id <00707-0@osi-east.es.net>; Wed, 3 Nov 1993 00:58:04 +0000 Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Wed, 3 Nov 1993 08:57:45 +0000 To: Axel Belinfante cc: Stephen Casner , rem-conf@es.net, MBONE@ISI.EDU Subject: Re: How's the reception of IETF? In-reply-to: Your message of "Tue, 02 Nov 93 21:24:57 +0100." <9311022024.AA01482@utis179.cs.utwente.nl> Date: Wed, 03 Nov 93 08:57:43 +0000 From: Jon Crowcroft >Wouldn't it be possible to use the shared whiteboard? >If people would bring postscript versions of their slides.. Axel. right - i absolutely agree - even if people dont bring their postscript, many had printed slides which looked like they could login back home from ietf and ftp them, and some local person pull them in to wb, or at worst, get a scanner and scan them in - wbimport has that functionality... jon From rem-conf-request@es.net Wed Nov 03 06:55:36 1993 Received: from ncc.ripe.net by osi-east.es.net via ESnet SMTP service id <01233-0@osi-east.es.net>; Wed, 3 Nov 1993 03:54:56 +0000 Received: from reif.ripe.net by ncc.ripe.net with SMTP id AA01709 (5.65a/NCC-1.11); Wed, 3 Nov 1993 12:54:48 +0100 Message-Id: <9311031154.AA01709@ncc.ripe.net> Cc: rem-conf@es.net, MBONE@isi.edu Subject: Re: How's the reception of IETF? In-Reply-To: Your message of Wed, 03 Nov 1993 08:57:43 GMT. <199311030857.AA08662@venera.isi.edu> From: Daniel Karrenberg X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Wed, 03 Nov 1993 12:54:47 +0100 Sender: Daniel.Karrenberg@ripe.net Seconded. From rem-conf-request@es.net Wed Nov 03 08:49:17 1993 Received: from seismo.CSS.GOV by osi-east.es.net via ESnet SMTP service id <01564-0@osi-east.es.net>; Wed, 3 Nov 1993 05:32:07 +0000 Received: from beno.CSS.GOV by seismo.CSS.GOV (4.1/SMI-4.1) id AA26290; Wed, 3 Nov 93 08:32:03 EST Received: by beno.CSS.GOV (4.1/SMI-4.1) id AA00468; Wed, 3 Nov 93 08:32:02 EST Message-Id: <9311031332.AA00468@beno.CSS.GOV> To: mbone@isi.edu, rem-conf@es.net Subject: Re: How's the reception of IETF? In-Reply-To: Your message of "Tue, 02 Nov 1993 12:38:46 PST." <9311022038.AA05853@Crazypete.AI.SRI.COM> Date: Wed, 03 Nov 1993 08:32:01 -0500 From: David Comay > Something else you might want to try is having a camera pointing directly > down at the overhead projector instead of at the projection screen. But then also, perhaps the chairs could remind audience members attending ietf to use the microphones - although most of the folks there did seem to use them, sometimes it sounded like audience members were shouting, uh, speaking directly from their seats. the result being that mbone-land was hearing only one side of the talk. dsc From rem-conf-request@es.net Wed Nov 03 10:32:27 1993 Received: from garb5.bellcore.com by osi-east.es.net via ESnet SMTP service id <02367-0@osi-east.es.net>; Wed, 3 Nov 1993 07:17:48 +0000 Received: by garb5.bellcore.com (5.61/1.34) id AA01391; Wed, 3 Nov 93 10:17:46 -0500 Date: Wed, 3 Nov 93 10:17:46 -0500 From: bianchi@bellcore.com (Michael H Bianchi) Message-Id: <9311031517.AA01391@garb5.bellcore.com> To: rem-conf@es.net Subject: Recording help please. I'm trying to understand and use mbone recording and have gotten stumped right at the start. I'd appreciate any aid and assistance. A) If there is a document that describes the mbone architecture (how the IP addresses, port and id numbers interact between sender and recievers, etc.) I'll gladly go read and educate myself. (I've not found such a thing yet, but I feel it must be out there in ftp-land somewhere.) B) If there are detailed instructions in using vat_nv_record, beyond the README file, I'll read that before bothering anyone further. Finally, lacking parts A and B, I'd appreciate advice in how to get started. Here is what I've done so far: Yesterday, I picked up, the vat_nv_record.tar.Z file via ftp from sics.se, scattered the files on a Sparc 10, shouted make at it, and it built cleanly. Then, after reading the README, I created a test session which had Address 224.2.197.47 Audio: Port: 59236 ID: 8970 Video: Port: 57607 ID: 60602 In the test window, I set: input ->O (line) output O-> (line) nothing muted In the @test window, I set: Audio Tests: loopback Priority: med Output Mode: Line - Full duplex Push to talk Autoraise Network: Lecture PCM2 Name: bianchi@garb5.bellcore.com Key: (not encrypted) Title: test The other info showed as Dest: 224.2.197.47 Port: 59236 ID: 8970 TTL: 16 (I understand that for what follows, this shouldn't be relavent, but for completeness ...) The nv v3.2 window showed: Address: 224.2.197.47 Port: 57607 TTL: 16 Name: bianchi@garb5 I started play in video tape into my sparc, and could hear the output and see the input meter moving. I created an empty directory for the recording and, from that directory, issued the command: ../vat_record -i 224.2.197.47 -p 59236 -c 8970 Response: bind: Address already in use So, what don't I understand? Of course the address is in use, it's what is being sent. What address should I use? Mike Bianchi MRE 2D-394 (201) 829-5055 FAX (201) 829-5981 bellcore!bianchi bianchi@bellcore.com Bellcore Room 2D-394 445 South Street Morristown, NJ 07960-6438 From rem-conf-request@es.net Wed Nov 03 10:50:09 1993 Received: from tel.vtt.fi by osi-east.es.net via ESnet SMTP service id <02430-0@osi-east.es.net>; Wed, 3 Nov 1993 07:29:25 +0000 Received: by tel1.tel.vtt.fi id AA01373 (5.65c/IDA-1.4.4 for rem-conf@es.net); Wed, 3 Nov 1993 17:29:20 +0200 Date: Wed, 3 Nov 1993 17:29:20 +0200 From: Jarmo Molsa Message-Id: <199311031529.AA01373@tel1.tel.vtt.fi> To: rem-conf@es.net Subject: Bitfield & VTT/TEL in MCNC Packet Video Forum For those of you, who are interested in the MCNC Packet Video Forum: Bitfield Oy has reserved the stand number 1729 from the TeleCon XIII Conference at San Jose (November 8, 9 & 10, 1993). Jarmo Molsa from the Telecommunications Laboratory of the Technical Research Centre of Finland is demonstrating the current results and future plans of our Packet Video Project related to the MCNC Packet Video Forum. All these demonstrations are held at the Bitfield's stand 1729. Risto Helkio and Simo Poikola from Bitfield Oy are demonstrating their H.261-codec based products. Regards, Jarmo Molsa Email: jarmo.molsa@tel.vtt.fi From rem-conf-request@es.net Wed Nov 03 11:02:23 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <02562-0@osi-east.es.net>; Wed, 3 Nov 1993 07:45:50 +0000 Received: from bugs.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA15699; Wed, 3 Nov 93 16:45:38 +0100 Received: by bugs.sics.se (5.65+bind 1.7+ida 1.4.2/SICSclient-1.1) id AA26999 (for rem-conf@es.net); Wed, 3 Nov 93 16:45:37 +0100 Date: Wed, 3 Nov 93 16:45:37 +0100 From: klemets@sics.se Message-Id: <9311031545.AA26999@bugs.sics.se> To: bianchi@bellcore.com, rem-conf@es.net Subject: Re: Recording help please. The recording programs will not work if you run them on the same machine you use for transmitting. So you must run the programs from a different machine. Anders From rem-conf-request@es.net Wed Nov 03 11:42:05 1993 Received: from s1.msi.umn.edu by osi-east.es.net via ESnet SMTP service id <02929-0@osi-east.es.net>; Wed, 3 Nov 1993 08:12:00 +0000 Received: from i5.msi.umn.edu by s1.msi.umn.edu; Wed, 3 Nov 93 10:10:53 -0600 From: hughes@s1.msi.umn.edu Message-Id: <9311031610.AA02040@i5.msi.umn.edu> Received: by i5.msi.umn.edu; Wed, 3 Nov 93 10:10:53 -0600 Subject: Re: How's the reception of IETF? To: dsc@seismo.css.gov (David Comay) Date: Wed, 3 Nov 1993 10:10:52 -0600 (CST) Cc: mbone@isi.edu, rem-conf@es.net In-Reply-To: <9311031332.AA00468@beno.CSS.GOV> from "David Comay" at Nov 3, 93 08:32:01 am X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 690 According to David Comay: > > > Something else you might want to try is having a camera pointing directly > > down at the overhead projector instead of at the projection screen. But then > also, perhaps the chairs could remind audience members attending ietf to > use the microphones - although most of the folks there did seem to use them, > sometimes it sounded like audience members were shouting, uh, speaking directly > from their seats. the result being that mbone-land was hearing only one side > of the talk. I agree that this was a problem. One solution in some cases, where an audience just makes some simple comment is for the current speaker to repeat it. -- Matt Hughes From rem-conf-request@es.net Wed Nov 03 17:33:13 1993 Received: from garb5.bellcore.com by osi-east.es.net via ESnet SMTP service id <07447-0@osi-east.es.net>; Wed, 3 Nov 1993 14:32:37 +0000 Received: by garb5.bellcore.com (5.61/1.34) id AA02276; Wed, 3 Nov 93 17:32:24 -0500 Date: Wed, 3 Nov 93 17:32:24 -0500 From: bianchi@bellcore.com (Michael H Bianchi) Message-Id: <9311032232.AA02276@garb5.bellcore.com> To: markus@octavia.anu.edu.au, rem-conf@es.net Subject: mbone recording Markus, Thanks for the explanation. This is all getting me where I want to go in tiny steps. Maybe someone out there has the solution pre-packaged. The goal is to record video and audio, whether originating locally (like from my local vcr or from our local video network) or from mbone, and then be able to: <> Play it back via mbone as an event. (That's what vat/nv_record does.) <> Play it back on a workstation (video on demand, don't you know) <> Process it to determine properties of the recorded images and sounds. To do this, I have to understand how things are packaged (hence the request for documents and/or papers). At this point, I'm trying to decode the code. (At the moment, I'm suffering from lack of vat code. Can someone tell me it's whereabouts?) Has anyone already attacked any of those goals? Anders code is a start, but seems to address the problem only at the "record a broadcast" and "rebroadcast a recording" levels. Am I misunderstanding something? Mike Bianchi Bellcore Room 2D-394 445 South Street Morristown NJ 07960-6438 (201) 829-5055 FAX (201) 829-5981 bianchi@bellcore.com From rem-conf-request@es.net Thu Nov 04 05:32:40 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <09138-0@osi-east.es.net>; Wed, 3 Nov 1993 16:57:40 +0000 Received: from anhur.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA10554; Thu, 4 Nov 93 01:22:03 +0100 Message-Id: <9311040022.AA10554@sics.se> To: rem-conf@es.net Cc: Toerless , bianchi@bellcore.com, markus@octavia.anu.edu.au Subject: Re: Recording help please. Date: Thu, 04 Nov 1993 01:22:01 +0100 From: Anders Klemets It turns out that it is actually quite simple to make vat_record and nv_record work when a vat and/or nv is already running on the same machine. One just has to remove the #ifdef around two setsockopt() calls in nv_record.c and in vat_record.c. Since vat_record.c uses two sockets, in this file the calls to setsockopt() have to be repeated for the other socket as well. I have put a new version of archive/vat_nv_record.tar.Z up for anonymous ftp at sics.se. Thanks to Toerless Eckert for hinting me about this. I did not leave the #ifdef statements there on purpose. It was just a mistake. Anders From rem-conf-request@es.net Thu Nov 04 06:25:40 1993 Received: from anu.anu.edu.au by osi-east.es.net via ESnet SMTP service id <07141-0@osi-east.es.net>; Wed, 3 Nov 1993 14:12:58 +0000 Received: from octavia.anu.edu.au. by anu.anu.edu.au (4.1/SMI-4.1) id AA18543; Thu, 4 Nov 93 09:12:28 EST Received: by octavia.anu.edu.au. (4.1/SMI-4.1) id AA15514; Thu, 4 Nov 93 09:12:08 EST Date: Thu, 4 Nov 93 09:12:08 EST From: markus@octavia.anu.edu.au (Markus Buchhorn) Message-Id: <9311032212.AA15514@octavia.anu.edu.au.> To: bianchi@bellcore.com Subject: Re: Recording help please. Cc: rem-conf@es.net > (I understand that for what follows, this shouldn't be relavent, but for > completeness ...) > The nv v3.2 window showed: Actually - it is relevant.. > I created an empty directory for the recording and, from that directory, > issued the command: > ../vat_record -i 224.2.197.47 -p 59236 -c 8970 > Response: > bind: Address already in use > > So, what don't I understand? Of course the address is in use, it's what > is being sent. What address should I use? You are using the right address - but you can't have the nv/vat stuff running before you fire up the recorders. When I try to record (say NASA Select) I will write down all the numbers first, then turn off my vat/nv sessions for that multicast, then fire up vat/nv_record, and restart the vat/nv windows if I want to watch it while it is recording. If you don't then I get exactly the above error. So, why does nv (the player) bind the address firmly, but not nv_record ? Oh - Anders below isn't quite right, you don't *have* to use a different machine. I run the mrouted on my machine for our subnet and happily record as well - as long as they are started in the right order.. > > From: klemets@sics.se > The recording programs will not work if you run them on the same > machine you use for transmitting. So you must run the programs > from a different machine. Cheers, Markus Markus Buchhorn, Parallel Computing Research Facility email = markus@octavia.anu.edu.au snail = CISR, I Block, OAA, ANU Australian National University, Canberra, 0200 , Australia. [International = +61 6, Australia = 06] [Phone = 2492930, Fax = 2490747] From rem-conf-request@es.net Thu Nov 04 19:47:00 1993 Received: from picard.cmf.nrl.navy.mil by osi-east.es.net via ESnet SMTP service id <22554-0@osi-east.es.net>; Tue, 19 Oct 1993 10:32:34 +0000 Received: from herman.cmf.nrl.navy.mil by picard.cmf.nrl.navy.mil (4.1/SMI-4.1) id AA14992; Tue, 19 Oct 93 13:32:04 EDT Received: from localhost by herman.cmf.nrl.navy.mil (4.1/client-1.3) id AA02412; Tue, 19 Oct 93 13:32:04 EDT Message-Id: <9310191732.AA02412@herman.cmf.nrl.navy.mil> To: bianchi@bellcore.com (Michael H Bianchi) Cc: rem-conf@es.net Subject: Re: Sparc10 audio box In-Reply-To: Your message of "Mon, 18 Oct 93 17:11:49 EDT." <9310182111.AA01022@garb5.bellcore.com> Date: Tue, 19 Oct 1993 13:31:54 -0400 From: William C Fenner On Mon, 18 Oct 93 17:11:49 -0400 Michael H Bianchi wrote: > Using the line-level input and output would make sense > for mbone telecasts. Here's a program that I wrote to switch between mic and line in; with "man audio" and looking at the include files you can surely modify it to do the same with outputs. Bill /* * setinput.c * * Sets the audio device to mic or line in */ #include #include #include #include int main(argc,argv) int argc; char **argv; { audio_info_t info; int i; if (argc != 2) { printf("Usage: %s [m/l]\n",argv[0]); exit(1); } if ((i=open("/dev/audioctl",O_RDWR,0))<0) { perror("/dev/audioctl"); exit(1); } AUDIO_INITINFO(&info); info.record.balance = AUDIO_MID_BALANCE; if (*argv[1] == 'l') { printf("Switching to line in\n"); info.record.port = AUDIO_LINE_IN; } else { printf("Switching to microphone\n"); info.record.port = AUDIO_MICROPHONE; } if (ioctl(i,AUDIO_SETINFO,&info)<0) { perror("ioctl(SETINFO)"); exit(1); } close(i); exit(0); } From rem-conf-request@es.net Thu Nov 04 21:15:13 1993 Received: from Sun.COM by osi-east.es.net via ESnet SMTP service id <02416-0@osi-east.es.net>; Thu, 4 Nov 1993 18:14:35 +0000 Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (4.1/SMI-4.1) id AA07668; Thu, 4 Nov 93 18:14:33 PST Received: from kaos.Eng.Sun.COM (control) by Eng.Sun.COM (4.1/SMI-4.1) id AA19415; Thu, 4 Nov 93 18:14:08 PST Received: from gday.Eng.Sun.COM by kaos.Eng.Sun.COM (4.1/SMI-4.1) id AA21071; Thu, 4 Nov 93 18:13:21 PST Received: from gday (localhost) by gday.Eng.Sun.COM (5.0/SMI-SVR4) id AA04596; Thu, 4 Nov 1993 18:14:39 +0800 Message-Id: <9311050214.AA04596@gday.Eng.Sun.COM> To: rem-conf@es.net Subject: Looking for a recording of Tuesday's AVT WG session Date: Thu, 04 Nov 1993 18:14:38 -0800 From: Thomas Maslen Content-Length: 178 If anyone has a recording (vat, nv, whatever) of this Tuesday's AVT WG session and could make it available, I'd be most grateful. Thanks, Thomas Maslen maslen@eng.sun.com From rem-conf-request@es.net Fri Nov 05 08:52:20 1993 X400-Received: by mta osi-west.es.net in /PRMD=ESnet/ADMD= /C=US/; Relayed; Fri, 5 Nov 1993 05:33:49 +0000 Date: Fri, 5 Nov 1993 05:33:49 +0000 X400-Originator: rem-conf-request@es.net X400-Recipients: non-disclosure:; X400-MTS-Identifier: [/PRMD=ESnet/ADMD= /C=US/;osi-west.e.507:05.10.93.13.33.49] Priority: Non-Urgent DL-Expansion-History: rem-conf@es.net ; Fri, 5 Nov 1993 05:33:48 +0000; From: "Marit K. Natvig" Message-ID: <"1317*/G=Marit/S=Natvig/OU=delab/O=sintef/PRMD=uninett/ADMD= /C=no/"@MHS> To: rem-conf@es.net Subject: IP Multicast for PC Does anyone know about IP Multicast extensions and applications for PCs? --------------------------------------------------------------------------- Marit Natvig E-mail: marit.natvig@delab.sintef.no SINTEF DELAB Phone: +47 73 59 70 73 N-7034 Trondheim Fax: +47 73 53 25 86 NORWAY From rem-conf-request@es.net Fri Nov 05 09:32:22 1993 Received: from ftp.com by osi-east.es.net via ESnet SMTP service id <05991-0@osi-east.es.net>; Fri, 5 Nov 1993 06:31:40 +0000 Received: from teflon.ftp.com by ftp.com with SMTP id AA21957; Fri, 5 Nov 93 09:27:22 -0500 Received: from backman.minimillian by teflon.ftp.com.ftp.com (5.0/SMI-SVR4) id AA26660; Fri, 5 Nov 93 09:31:57 EST Date: Fri, 5 Nov 93 09:31:57 EST Message-Id: <9311051431.AA26660@teflon.ftp.com.ftp.com> To: Marit.Natvig@delab.sintef.no Subject: Re: IP Multicast for PC From: backman@teflon.ftp.com (Larry Backman) Cc: rem-conf@es.net Sender: backman@teflon.ftp.com Repository: teflon.ftp.com Originating-Client: minimillian Content-Length: 244 >> Does anyone know about IP Multicast extensions and applications for PCs? >> PCTCP V2.3, currently in beta, supports IP Multicast. I'm not aware of any other multicast packages on the PC at the current time. Larry Backman FTP Software From rem-conf-request@es.net Fri Nov 05 10:07:05 1993 Received: from faui45.informatik.uni-erlangen.de by osi-east.es.net via ESnet SMTP service id <06108-0@osi-east.es.net>; Fri, 5 Nov 1993 06:49:55 +0000 Received: from faui43.informatik.uni-erlangen.de by uni-erlangen.de with SMTP; id AA12023 (5.65c-5/7.3v-FAU); Fri, 5 Nov 1993 15:48:56 +0100 Received: from faui45r.informatik.uni-erlangen.de by immd4.informatik.uni-erlangen.de with SMTP; id AA23782 (5.65c-5/7.3m-FAU); Fri, 5 Nov 1993 15:48:54 +0100 Message-Id: <199311051448.AA23782@faui43.informatik.uni-erlangen.de> Subject: Re: IP Multicast for PC To: backman@teflon.ftp.com Date: Fri, 5 Nov 1993 15:47:43 +0100 (MET) From: Toerless Cc: Marit.Natvig@delab.sintef.no, rem-conf@es.net In-Reply-To: <9311051431.AA26660@teflon.ftp.com.ftp.com> from "rem-conf-request@es.net" at Nov 5, 93 03:31:57 pm Organisation: CSD IMMD IV, University of Erlangen, Germany X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 151 > PCTCP V2.3, currently in beta, supports IP Multicast. I'm not aware > of any other multicast packages on the PC at the current time. BSD Unix ;-)) From rem-conf-request@es.net Fri Nov 05 13:30:53 1993 Received: from zephyr.isi.edu by osi-east.es.net via ESnet SMTP service id <08926-0@osi-east.es.net>; Fri, 5 Nov 1993 10:30:16 +0000 Received: by zephyr.isi.edu (5.65c/5.61+local-13) id ; Fri, 5 Nov 1993 10:30:14 -0800 Date: Fri, 5 Nov 1993 10:30:14 -0800 From: braden@ISI.EDU (Bob Braden) Message-Id: <199311051830.AA14086@zephyr.isi.edu> To: rem-conf@es.net Subject: Recording wanted Hi. If anyone recorded the Wednesday evening 'realtime' BOF from Houston, I would sure like to have a copy. InterNIC intended to record all the MBONE sessions, but when I ftp to the promised archive, the directory is empty. Thanks, Bob Braden From rem-conf-request@es.net Fri Nov 05 15:42:21 1993 Received: from guinan.concert.net by osi-east.es.net via ESnet SMTP service id <11422-0@osi-east.es.net>; Fri, 5 Nov 1993 12:41:44 +0000 Received: by guinan.concert.net (5.59/tas-concert/8-12-92) id AA02751; Fri, 5 Nov 93 15:44:06 -0500 Date: Fri, 5 Nov 93 15:44:06 -0500 From: Chandramouli Sargor Message-Id: <9311052044.AA02751@guinan.concert.net> To: rem-conf@es.net, sargor@concert.net Subject: Packet Audio Video Catalog A Catalog containing a list of Packet Audio and Video Packages currently available has been placed on the ftp site "ftp.concert.net". It can be obtained via anonymous ftp and is located in the directory : comm_research/packet_video/ filename : pv_catalog.txt The catalog is offered as a hopefully helpful tool for those who are interested in finding out about teleconferencing packages currently available. The focus of the catalog is on packet video and/or packet audio packages that support teleconferencing. It is NOT intended as a general catalog covering the broad range of multimedia products. The catalog is intended to be a simple list of the available packages. It does not go into great detail about any of the packages, but gives pointers to where more specific information can be obtained. Since this is a rapidly emerging field, with companies coming, going, changing names quickly, the list is almost certainly out-of-date and incomplete. It is offered as a starting point and a quick reference. The catalog is based on the Products section of Chris Adie's "A Survey of Distributed Multimedia Research, Standards and Products" which Chris compiled and published in January, 1993. Any comments, updates, additions, deletions to the catalog are solicited and encouraged. Please direct such via email to pv-catalog@concert.net. ------------------------------------------------------------------ Each entry in the catalog contains the following fields: PRODUCT NAME: The common name of the package CATEGORY: Type of package - possibilities include Audio only - provides packetized audio Video only - provides packetized video Audio and Video - provides packetized audio and video Audio and Video plus tools - provides packetized audio and video plus other conferencing tools Audio Toolkit - not a complete package, provides tools for building an audio package Video Toolkit - not a complete package, provides tools for building an video package Session Manager - manages audio / video packages DESCRIPTION: Brief description of what the packages does VERSION: Current version PLATFORMS: Systems on which the package runs REQUIREMENTS: Required hardware / software PROVIDER: Organization / Individual developing the package COST: What it costs, and if free, where to get it. STANDARDS/ ENCODING: What encoding, compression, etc. standards are used PROTOCOLS: What transport protocols are used INFORMATION: Where to get additional Information From rem-conf-request@es.net Fri Nov 05 19:34:05 1993 Received: from Sun.COM by osi-east.es.net via ESnet SMTP service id <14459-0@osi-east.es.net>; Fri, 5 Nov 1993 16:33:30 +0000 Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (4.1/SMI-4.1) id AA02144; Fri, 5 Nov 93 16:33:28 PST Received: from kaos.Eng.Sun.COM (control) by Eng.Sun.COM (4.1/SMI-4.1) id AA12695; Fri, 5 Nov 93 16:32:59 PST Received: from gday.Eng.Sun.COM by kaos.Eng.Sun.COM (4.1/SMI-4.1) id AA25060; Fri, 5 Nov 93 16:32:13 PST Received: from gday (localhost) by gday.Eng.Sun.COM (5.0/SMI-SVR4) id AA05521; Fri, 5 Nov 1993 16:33:33 +0800 Message-Id: <9311060033.AA05521@gday.Eng.Sun.COM> To: braden@ISI.EDU (Bob Braden) Cc: rem-conf@es.net Subject: Re: Recording wanted In-Reply-To: Your message of "Fri, 05 Nov 1993 10:30:14 PST." <199311051830.AA14086@zephyr.isi.edu> Date: Fri, 05 Nov 1993 16:33:32 -0800 From: Thomas Maslen Content-Length: 591 I asked the same thing about a different session. I got one reply to the effect that ftp.es.net would be a good place to look but I saw nothing, either there or on ftp.internic.net. My guess is that I should wait a while and then look again. (In your case, maybe Steve Casner has brought the real videotapes back to ISI?). I can testify that the 'realtime' BOF was pretty interesting. Both there and at the RSVP BOF, your partners in crime prefaced their remarks with "These are Bob's slides and I'm not quite sure what's on them", then proceeded to do just fine anyway. Thomas Maslen From rem-conf-request@es.net Fri Nov 05 22:04:23 1993 Received: from is.rice.edu by osi-east.es.net via ESnet SMTP service id <16284-0@osi-east.es.net>; Fri, 5 Nov 1993 19:03:38 +0000 Received: from sabine.is.rice.edu by is.rice.edu (AA19251); Fri, 5 Nov 93 21:03:22 CST Received: by sabine.is.rice.edu (AA10225); Fri, 5 Nov 93 21:03:21 CST From: bmanning@is.rice.edu (William Manning) Message-Id: <9311060303.AA10225@sabine.is.rice.edu> Subject: Recording wanted - The Reel story To: rem-conf@es.net Date: Fri, 5 Nov 93 21:03:19 CST Cc: ietf28-bees@sesqui.net X-Mailer: ELM [version 2.3 PL11] We have all the master tapes.... (except Tuesday - camera two) and will "transcribe" them to disk in the next two weeks. The updates will be available from the Internic in the ususal places, we will also keep copies on ftp.sesqui.net:/pub/ietf28/ -- Regards, Bill Manning bmanning@rice.edu PO Box 1892 713-285-5415 713-527-6099 Houston, Texas R.U. (o-kome) 77251-1892 From rem-conf-request@es.net Sat Nov 06 02:27:43 1993 Received: from RUTGERS.EDU by osi-east.es.net via ESnet SMTP service id <17261-0@osi-east.es.net>; Fri, 5 Nov 1993 23:27:04 +0000 Received: from grimaldi.rutgers.edu by rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA09220; Sat, 6 Nov 93 02:27:01 EST Received: from localhost (news@localhost) by grimaldi.rutgers.edu (8.6.beta.11+ru:bestmx.2/8.5) id CAA02155; Sat, 6 Nov 1993 02:26:18 -0500 To: ru-comp-dev-ietf-rem-conf@rutgers.edu Path: grimaldi.rutgers.edu!jim From: jim@grimaldi.rutgers.edu (Jim Martin) Newsgroups: ru.comp.dev.ietf.rem-conf Subject: Re: IP Multicast for PC Message-Id: Date: 6 Nov 93 07:26:16 GMT References: <"1317*.G=Marit.S=Natvig.OU=delab.O=sintef.PRMD=uninett.ADMD=..C=no."@MHS> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 24 Marit.Natvig@delab.sintef.no ("Marit K. Natvig") writes: >Does anyone know about IP Multicast extensions and applications for PCs? Yep! I've written a full multicasting implementation for WATTCP, and am in the process of creating a prototype NV like (compatible) program for the PC. As soon as I have an example app (the nv like thingie), I'll hand the multicast mods back to Erick ( The original and primary WATTCP developer). Actually though, that's just a proof of concept step. Once multicasting is defined under winsock, I intend to take the guts of my prototype and make a much more polished version for under Windows. As for a timeframe, the multicast support is finished (and tested), the prototype is about a quarter done, and I'm about to bug a few contacts at FTP Inc for their multicast for winsock extensions. If anyone wants to play with the multicast capable WATTCP code, just drop me a line and I'll gladly send out a set of diffs. Sound reasonable? Jim -- Jim Martin Internet: jim@noc.rutgers.edu Network Services UUCP: {backbone}!rutgers!jim Rutgers University Phone: (908) 932-3719 From rem-conf-request@es.net Tue Nov 09 13:29:07 1993 Received: from bnl.gov by osi-east.es.net via ESnet SMTP service id <23364-0@osi-east.es.net>; Tue, 9 Nov 1993 10:28:23 +0000 Received: by bnl.gov (5.57/Ultrix3.0-C) id AA15141; Tue, 9 Nov 93 13:28:18 -0500 Received: by maeva.ccd.bnl.gov.ccd.bnl.gov (5.0/SMI-SVR4) id AA07852; Tue, 9 Nov 93 13:28:07 EST Date: Tue, 9 Nov 93 13:28:07 EST From: gc@maeva.ccd.bnl.gov (Graham Campbell) Message-Id: <9311091828.AA07852@maeva.ccd.bnl.gov.ccd.bnl.gov> To: frederick@parc.xerox.com Subject: Interfaces supported by nv Cc: rem-conf@es.net X-Sun-Charset: US-ASCII Content-Length: 435 I would like to find out which video interfaces are supported by nv. On Suns, are the new Sun boards supported? Is the Parallax board supported? (I am currently using a VideoPix board, but we have plans to expand and would like to test higher performance video with a high end interface) Secondly, I just tried bringing up nv3.2 on a new Indy. It comes up without the camera control panel. Is there a version for the Indy? Graham From rem-conf-request@es.net Tue Nov 09 14:24:03 1993 Received: from munin.fnal.gov by osi-east.es.net via ESnet SMTP service id <24506-0@osi-east.es.net>; Tue, 9 Nov 1993 11:22:46 +0000 Received: from LOCALHOST.fnal.gov by munin.fnal.gov with SMTP id AA17215 (5.65c+/IDA-1.4.4 for rem-conf@es.net); Tue, 9 Nov 1993 13:24:18 -0600 Message-Id: <199311091924.AA17215@munin.fnal.gov> To: gc@maeva.ccd.bnl.gov (Graham Campbell) Cc: rem-conf@es.net Subject: Re: Interfaces supported by nv In-Reply-To: Your message of Tue, 09 Nov 93 13:28:07 EST. <9311091828.AA07852@maeva.ccd.bnl.gov.ccd.bnl.gov> Date: Tue, 09 Nov 93 13:24:18 -0600 From: Matt Crawford Two weeks ago I test-drove the experimental Indy release of nv and found it to work, but v-e-r-y s-l-o-w-l-y. I fetched it from ftp.sgi.com:sgi/ipmcast/nv-indy.Z. Also see README.tools in that directory. _________________________________________________________ Matt Crawford crawdad@fnal.gov Fermilab From rem-conf-request@es.net Tue Nov 09 14:32:48 1993 Received: from relay.nswc.navy.mil by osi-east.es.net via ESnet SMTP service id <24537-0@osi-east.es.net>; Tue, 9 Nov 1993 11:23:41 +0000 Received: from sunoco.nswc.navy.mil by relay.nswc.navy.mil (4.1/SMI-4.1) id AA01096; Tue, 9 Nov 93 14:23:34 EST Received: from vaxless.suKPFVpTHxu8w by sunoco.nswc.navy.mil (4.1/SMI-4.1) id AA25908; Tue, 9 Nov 93 14:23:34 EST Date: Tue, 9 Nov 93 14:23:34 EST From: pirey%sunoco@relay.nswc.navy.mil (Phil Irey 703.663.1582) Message-Id: <9311091923.AA25908@sunoco.nswc.navy.mil> To: rem-conf@es.net Subject: Error message: can't allocate color cube I received the following error message when I tried to run nv on my SparcStation 10 running SunOS 4.1.3: can't allocate color cube All nv sessions started on that machine displayed in black and white even though they were transmitted in color. Any ideas? thanks, phil irey (pirey@relay.nswc.navy.mil) From rem-conf-request@es.net Tue Nov 09 15:39:26 1993 Received: from odin.ucsd.edu by osi-east.es.net via ESnet SMTP service id <25854-0@osi-east.es.net>; Tue, 9 Nov 1993 12:38:29 +0000 Received: from empyrean.ucsd.edu by odin.ucsd.edu; id AA28581 sendmail 5.67/UCSDPSEUDO.4-CS via SMTP Tue, 9 Nov 93 12:38:16 -0800 for rem-conf@es.net Message-Id: <9311092038.AA28581@odin.ucsd.edu> To: pirey%sunoco@relay.nswc.navy.mil (Phil Irey 703.663.1582) Cc: rem-conf@es.net Subject: Re: Error message: can't allocate color cube In-Reply-To: Your message of "Tue, 09 Nov 1993 14:23:34 EST." <9311091923.AA25908@sunoco.nswc.navy.mil> Date: Tue, 09 Nov 1993 12:38:16 -0800 From: Steve Hopper If your frame buffer only handles 256 colors and you have a background image on your desktop there probably aren't enough colors available to support the color information. What I do to prevent this message is xsetroot -solid black. Steve -------- In reply to the following message: -------- >I received the following error message when I tried to run nv on my >SparcStation 10 running SunOS 4.1.3: > >can't allocate color cube > >All nv sessions started on that machine displayed in black and white >even though they were transmitted in color. > >Any ideas? > >thanks, > phil irey (pirey@relay.nswc.navy.mil) -------- From rem-conf-request@es.net Tue Nov 09 15:55:17 1993 Received: from alpha.Xerox.COM by osi-east.es.net via ESnet SMTP service id <26121-0@osi-east.es.net>; Tue, 9 Nov 1993 12:54:23 +0000 Received: from ecco.parc.xerox.com ([13.2.116.196]) by alpha.xerox.com with SMTP id <12061(2)>; Tue, 9 Nov 1993 12:54:02 PST Received: by ecco.parc.xerox.com id <16139>; Tue, 9 Nov 1993 12:53:52 -0800 Received: from Messages.7.15.N.CUILIB.3.45.SNAP.NOT.LINKED.ecco.parc.xerox.com.sun4.41 via MS.5.6.ecco.parc.xerox.com.sun4_41; Tue, 9 Nov 1993 12:53:39 -0800 (PST) Message-ID: Date: Tue, 9 Nov 1993 12:53:39 PST Sender: Ron Frederick From: Ron Frederick To: Matt Crawford Subject: Re: Interfaces supported by nv CC: rem-conf@es.net In-Reply-To: <199311091924.AA17215@munin.fnal.gov> References: <199311091924.AA17215@munin.fnal.gov> > Two weeks ago I test-drove the experimental Indy release of nv and > found it to work, but v-e-r-y s-l-o-w-l-y. I fetched it from > ftp.sgi.com:sgi/ipmcast/nv-indy.Z. Also see README.tools in that > directory. We should be getting some Indys here soon, and I hope to be able to tune that code to run faster there as soon as we get them. For now, I hope that the existing release will let you at least get something up and running. The version I saw was still faster than a SPARC 2 with a VideoPix. -- Ron Frederick frederick@parc.xerox.com From rem-conf-request@es.net Tue Nov 09 15:55:43 1993 Received: from alpha.Xerox.COM by osi-east.es.net via ESnet SMTP service id <26061-0@osi-east.es.net>; Tue, 9 Nov 1993 12:52:31 +0000 Received: from ecco.parc.xerox.com ([13.2.116.196]) by alpha.xerox.com with SMTP id <12061(1)>; Tue, 9 Nov 1993 12:52:10 PST Received: by ecco.parc.xerox.com id <16139>; Tue, 9 Nov 1993 12:52:03 -0800 Received: from Messages.7.15.N.CUILIB.3.45.SNAP.NOT.LINKED.ecco.parc.xerox.com.sun4.41 via MS.5.6.ecco.parc.xerox.com.sun4_41; Tue, 9 Nov 1993 12:51:47 -0800 (PST) Message-ID: Date: Tue, 9 Nov 1993 12:51:47 PST Sender: Ron Frederick From: Ron Frederick To: pirey%sunoco@relay.nswc.navy.mil (Phil Irey 703.663.1582) Subject: Re: Error message: can't allocate color cube CC: rem-conf@es.net In-Reply-To: <9311091923.AA25908@sunoco.nswc.navy.mil> References: <9311091923.AA25908@sunoco.nswc.navy.mil> > I received the following error message when I tried to run nv on my > SparcStation 10 running SunOS 4.1.3: > > can't allocate color cube > > All nv sessions started on that machine displayed in black and white > even though they were transmitted in color. This means that other applications on your system were already using up too much of your colormap, so there wasn't room for the color cube that nv needs to allocate to display things in color. It falls back in that case to using the smaller greyscale ramp that it allocated and displays everything in greyscale. The fix is to find the colormap-hungry applications, quit them, and restart nv. I've been thinking about supporting a less drastic fallback to a smaller color cube, but I haven't had time to implement that yet. -- Ron Frederick frederick@parc.xerox.com From rem-conf-request@es.net Wed Nov 10 09:03:04 1993 Received: from picard.cmf.nrl.navy.mil by osi-east.es.net via ESnet SMTP service id <04200-0@osi-east.es.net>; Wed, 10 Nov 1993 06:02:19 +0000 Received: from herman.cmf.nrl.navy.mil by picard.cmf.nrl.navy.mil (4.1/SMI-4.1) id AA06642; Wed, 10 Nov 93 09:02:10 EST Received: from localhost by herman.cmf.nrl.navy.mil (4.1/client-1.3) id AA14769; Wed, 10 Nov 93 09:02:09 EST Message-Id: <9311101402.AA14769@herman.cmf.nrl.navy.mil> To: Ron Frederick Cc: rem-conf@es.net Subject: Re: Error message: can't allocate color cube In-Reply-To: Your message of "Tue, 09 Nov 93 12:51:47 PST." Date: Wed, 10 Nov 1993 09:02:07 -0500 From: William C Fenner On Tue, 9 Nov 1993 12:51:47 PST Ron Frederick wrote: > I've been thinking about supporting a less drastic fallback to a smaller > color cube, but I haven't had time to implement that yet. How about offering the user the choice of either falling back to grayscale or letting nv allocate and install a private colormap? For some people, a private colormap may be preferable to grayscale. Bill From rem-conf-request@es.net Wed Nov 10 23:50:10 1993 Received: from venera.isi.edu by osi-east.es.net via ESnet SMTP service id <15587-0@osi-east.es.net>; Wed, 10 Nov 1993 20:49:27 +0000 Received: from xfr.isi.edu by venera.isi.edu (5.65c/5.61+local-14) id ; Wed, 10 Nov 1993 20:49:22 -0800 Posted-Date: Wed 10 Nov 93 20:48:37 PST Received: by xfr.isi.edu (4.1/4.0.3-4) id ; Wed, 10 Nov 93 20:48:38 PST Date: Wed 10 Nov 93 20:48:37 PST From: Stephen Casner Subject: Re: Recording wanted - The Reel story To: rem-conf@es.net Cc: ietf28-bees@sesqui.net Message-Id: <752993317.0.CASNER@XFR.ISI.EDU> In-Reply-To: <9311060303.AA10225@sabine.is.rice.edu> Mail-System-Version: Bill Manning said: > We have all the master tapes.... (except Tuesday - camera two) > and will "transcribe" them to disk in the next two weeks. The Rice folks were kind enough to let me borrow the Tuesday camera two tape, but I have shipped it back to them so they should be able to transcribe all the sessions. -- Steve ------- From rem-conf-request@es.net Thu Nov 11 13:21:31 1993 Received: from RUTGERS.EDU by osi-east.es.net via ESnet SMTP service id <20899-0@osi-east.es.net>; Thu, 11 Nov 1993 10:20:50 +0000 Received: from hardees.rutgers.edu by rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA10777; Thu, 11 Nov 93 13:20:47 EST Received: by hardees.rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA13398; Thu, 11 Nov 93 13:20:46 EST To: ru-comp-dev-ietf-rem-conf@rutgers.edu Path: hardees.rutgers.edu!jim From: jim@hardees.rutgers.edu (Jim Martin) Newsgroups: ru.comp.dev.ietf.rem-conf Subject: IP Multicasting support for WATTCP libraries Keywords: IP multicast MSDOS WATTCP Message-Id: Date: 11 Nov 93 18:20:45 GMT Organization: Rutgers Univ., New Brunswick, N.J. Lines: 204 I've added IP Multicasting support to the WATTCP TCP/IP libraries for MS-DOS. These extensions will allow programmers to develop applications that can interact with "groups" of network hosts rather than the more traditional one to one interactions. This code is being released as a separate package at this point, but it is my hope that in the long run I'll be able to convince Erick (the primary author of WATTCP) that it should be part of the base distribution. The package is now available via anonymous FTP on ftp-ns.rutgers.edu in the directory /pub/msdos/wattcp as the file "mcast.zip". I'm including the release notes below. Have fun, and let me know if you have any problems or comments! Jim ----- Release Notes follow ---- Multicast extensions for the WATTCP TCP/IP libraries ---------------------------------------------------- Introduction ------------ IP Multicasting is a mechanism to send and receive data from a group of hosts rather than via the more traditional one on one interaction. This technology is being heavily used for experimentation into Audio/Video Conferencing over IP, but has the potential to be used in a much more far-reaching manner. In fact, one school of thought says that multicasting (1->n) is the general case, and that unicasts (1->1) are simply a special case. This package contains the pieces necessary to extend the WATTCP libraries to support IP multicasting as defined by RFC-1112[1] (Deering). Three new user-level routines have been created to achieve this goal. The routines join_mcast_group and leave_mcast_group allow a process to join and leave a specified multicast group, and udp_SetTTL allows the outgoing ttl on udp packets to be set. Additionally, there are two trivial example/test programs. Lister is a simple program that watches a specified address/port pair and decodes vat[2] style control packets, thus producing a continuous listing of the IDs of the participants. Blather is the flip side of lister. It produces a vat style control packet and sends it to the specified address and port, thus adding a new participant to your vat display. Installation ------------ The installation of this package consists of three basic steps. The package must first be unzipped, the source files then need to be patched, and finally everything needs to be rebuilt. Before you begin, you will need to have the WATTCP source distribution installed, built, and working. WATTCP is available from ftp-ns.rutgers.edu in /pub/msdos/wattcp. The September 30, 1993 distribution was used as a basis for these extensions. Additionally, a connection to the MBone[3], the Internet Multicast Backbone, is a great advantage and the default operation of the example programs assumes that it is present. 1. In the same directory that you unzipped the WATTCP distribution, unzip the mcast.zip file using version 2.04c or greater of pkunzip. Make sure that the "-d" flag is specified so that the files end up in the proper subdirectories rather than all being dumped at the top level. This will create the following files: mcast.txt This file mcast.dif The patch file apps\lister.c The receive example apps\blather.c The send example src\pcigmp.c code to support IGMP src\ipmulti.c generic additional multicast source 2. You now need to patch the source files to add the extensions. To do this, you will need the "patch" program by Larry Wall. It can be found on wuarchive.wustl.edu in /mirrors/msdos/filutl as patch12.zip. Now, again in that same top level directory, type "patch -p0 < mcast.dif". There should be lots of "Hunk Succeeded" messages, and all your code will be patched. 3. The final step is to rebuild the entire set of libraries and example applications. Begin by removing all of the .obj and .exe files in src, apps, and elib plus all of the libraries in lib (effectively doing a "make clean"). Then just do a make in the top level directory and everything will rebuild. Use ___ Network programming for multicasting isn't very different from the network programming that you're already used to. The two basic differences are that you need to join and leave a multicast group and that you need to specify the outgoing ttl on most multicast packets. To join a group you simply need to use the "join_mcast_group" call after you've done the udp_open. This registers the use of the group with the low level routines that need to interact with the multicast router to keep the packets flowing. After you're done, you'll then need to leave the multicast group immediately prior to issuing the close call by using the "leave_mcast_group" routine. The default ttl whenever you open a udp connection with a multicast address is set to 1. That way, your multicasts won't leave your local net. To expand the scope, you'll need to up the ttl by using the "udp_SetTTL" call. This call should be used after the udp_connect is done, but before anything is sent, and is persistent for the life of the connection. Beyond those two points, most things are straightforward. You do a udp_open, a join_mcast_group, set the ttl, read and write a few things, leave_mcast_group, and close. That's all there is to it. The only other thing you need to remember is to define MULTICAST whenever you use this code so that you get all of the multicasting prototypes from the tcp.h header file. Reference --------- join_mcast_group - joins a multicast group int join_mcast_group( longword ina ) Where: ina IP address of the group to be joined Behavior: join_mcast_group registers the use of the multicast address with the internals of the tcp stack that deal with responding to IGMP queries from the multicast router. Returns: 1 if the group was joined successfully 0 if attempt failed leave_mcast_group - leaves a multicast group int leave_mcast_group( longword ina ) Where: ina IP address of the group to be joined Behavior: leave_mcast_group deregisters the use of a particular multicast address so that no IGMP Reports will be sent for that address. Returns: 1 if the group was left successfully 0 if attempt failed udp_SetTTL - Set the TTL on an outgoing UDP datagram. int udp_SetTTL(udp_Socket *s, byte ttl) Where: s the socket of the UDP connection (?!?) in question ttl the desired ttl for the outgoing datagrams Behavior: udp_SetTTL allows the ttl for a particular UDP connection to be changed from the default value of 1. As the ttl is increased, the scope of the packets will expand until it reaches worldwide scope at around 192. Returns: 1 always (there is no error return) Notes ----- [1] RFC-1112, "Host Extensions for IP Multicasting", is a description and specification of IP Multicasting by Steve Deering (deering@parc.xerox.com) of Xerox PARC. It is available via anonymous FTP on ds.internic.net in the /rfc directory as "rfc1112.txt". [2] vat, the Visual Audio Tool, is an audioconferencing application for the X-Windowing system written by Van Jacobson (van@ee.lbl.gov) of Lawrence Berkeley Labs. It is the de-facto standard for audio on the MBone, and can be found via anonymous FTP on ftp.ee.lbl.gov. [3] The MBone or the Internet Multicast Backbone is an outgrowth of the first two IETF "audiocasts". It is a virtual network, layered upon parts of the physical Internet to facilitate worldwide routing of IP multicasts. More information about the MBone can be found in the Frequently Asked Questions document available on venera.isi.edu in /mbone as "faq.txt". Author ------ Jim Martin Rutgers University jim@noc.rutgers.edu 11/10/93 ---- End Release Notes ---- -- Jim Martin Internet: jim@noc.rutgers.edu Network Services UUCP: {backbone}!rutgers!jim Rutgers University Phone: (908) 932-3719 From rem-conf-request@es.net Thu Nov 11 22:10:00 1993 Received: from garam.kreonet.re.kr by osi-east.es.net via ESnet SMTP service id <28160-0@osi-east.es.net>; Thu, 11 Nov 1993 18:57:05 +0000 Received: from maruchi.chungnam.ac.kr ([192.132.251.36]) by garam.kreonet.re.kr (4.1/GARAM-MX-1.0) id AA26698; Fri, 12 Nov 93 11:55:08 KST Received: from comsun.chungnam.ac.kr.ac.kr by maruchi.chungnam.ac.kr (4.1/SMI-4.1) id AA16943; Fri, 12 Nov 93 11:53:59 KST Received: by comsun.chungnam.ac.kr.ac.kr (4.1/SMI-4.1) id AA00934; Fri, 12 Nov 93 10:51:57 PST Date: Fri, 12 Nov 93 10:51:57 PST From: kimd@comsun.chungnam.ac.kr ( Kim Dae Young) Message-Id: <9311121851.AA00934@comsun.chungnam.ac.kr.ac.kr> To: Axel.Belinfante@cs.utwente.nl, J.Crowcroft@cs.ucl.ac.uk Subject: Re: How's the reception of IETF? Cc: CASNER@ISI.EDU, MBONE@ISI.EDU, rem-conf@es.net f ? q From rem-conf-request@es.net Fri Nov 12 10:46:24 1993 Received: from bells.cs.ucl.ac.uk by osi-east.es.net via ESnet SMTP service id <02743-0@osi-east.es.net>; Fri, 12 Nov 1993 07:33:55 +0000 Received: from rodent.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Fri, 12 Nov 1993 15:33:19 +0000 To: mice-seminars@cs.ucl.ac.uk, rem-conf@es.net Subject: MICE seminar Nov 15 Date: Fri, 12 Nov 93 15:33:14 +0000 From: Gordon Joly The next MICE seminar with be on Nov 15 1993 from LBL (Lawrence Berkeley Laborarories). Time: 15.00 CET (14.00 GMT/UTC) Van Jacobson (LBL) "A Conferencing Architecture for `Light-weight Sessions'" The usual multicast addresses will be used: vat 224.5.17.12 (default port) ivs 224.5.17.12 (default port) wb 224.5.17.12 (port 32416) (plus a control wb on the usual address). Abstract:: During the past two years, audio/video conferencing over the global Internet has become both possible and popular. The tools that support this conferencing (vat, nv, ivs, etc.) are built on a new communication model that Steve Deering has dubbed `Light-weight Sessions' (a synthesis of Deering's IP multicast delivery model, Clark's `application level framing' protocol/implementation model and our ideas on receiver adaptation). Recently we have been trying evolve the light-weight sessions model into a complete architecture that supports not only basic audio and video communications but also higher level coordination functions like floor and membership control. In the first part of this talk I will try to describe this conferencing architecture and the new tools we're building to support it. One of the more difficult problems we've faced in building to the light-weight sessions model is applications, such as a shared drawing surface, that require `reliable' data delivery. If time permits, the second part of the talk will describe some of the problems and how we've addressed them in the LBL "wb" whiteboard tool. Gordon Joly Phone +44 71 380 7777 ext 3703 FAX +44 71 387 1397 Internet: G.Joly@cs.ucl.ac.uk UUCP: ...!{uunet,uknet}!ucl-cs!G.Joly Computer Science, University College London, Gower Street, LONDON WC1E 6BT From rem-conf-request@es.net Fri Nov 12 13:44:11 1993 Received: from mvs.oac.ucla.edu by osi-east.es.net via ESnet SMTP service id <05033-0@osi-east.es.net>; Fri, 12 Nov 1993 10:34:37 +0000 Received: from UCLAMVS.BITNET by MVS.OAC.UCLA.EDU (IBM MVS SMTP V2R2.1) with BSMTP id 9222; Fri, 12 Nov 93 10:34:25 PST Date: Fri, 12 Nov 93 10:34 PST To: mbone@ISI.EDU, rem-conf@ES.NET From: Denis DeLaRoca (310) 825-4580 Subject: SIGWAIS/SIGNIDR III broadcast quality It's been mostly ok but here and there noticeable losses *and* quite often, actually, I would lose either one or both the audio and video. Maybe the sessions disappear because of some mrouted doing pruning, it has occurred like 4-5 times this morning. The Xmosaic generated displays come thru in faded pinks and violets, and with lossy video visible ghosting gets in the way of reading text. As is often the case the audio quality is dependent on the audio arrangements in the conference room, the initial audio was quality was very poor but by the end of the morning had become decent enough to make the conference plesant to follow. -- Denis From rem-conf-request@es.net Fri Nov 12 21:35:42 1993 Received: from odin.ucsd.edu by osi-east.es.net via ESnet SMTP service id <11384-0@osi-east.es.net>; Fri, 12 Nov 1993 18:24:13 +0000 Received: from beowulf.ucsd.edu by odin.ucsd.edu; id AA00592 sendmail 5.67/UCSDPSEUDO.4-CS via SMTP Fri, 12 Nov 93 18:24:12 -0800 for rem-conf@es.net Received: by beowulf (5.67/UCSDPSEUDO.4) id AA26157 for rem-conf@es.net; Fri, 12 Nov 93 18:24:09 -0800 From: tnguyen@cs.ucsd.edu (Tuong Quang Nguyen) Message-Id: <9311130224.AA26157@beowulf> Subject: inter-media synch for live applications To: rem-conf@es.net Date: Fri, 12 Nov 1993 18:24:08 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 265 Hi, I'm interested in learning about intermedia synchronization, especially between video and audio, for live applications such as conferencing. If anyone know of any literature on this subject, would you pass me a note? Thanks, Tom Nguyen tnguyen@cs.ucsd.edu From rem-conf-request@es.net Sun Nov 14 08:50:35 1993 Received: from rx7.ee.lbl.gov by osi-east.es.net via ESnet SMTP service id <25919-0@osi-east.es.net>; Sun, 14 Nov 1993 05:44:15 +0000 Received: by rx7.ee.lbl.gov for rem-conf@es.net (5.65/1.44r) id AA27636; Sun, 14 Nov 93 05:44:08 -0800 Message-Id: <9311141344.AA27636@rx7.ee.lbl.gov> To: medin@nsipo.nasa.gov Cc: rem-conf@es.net Subject: vat, wb & nv developed by nasa? Date: Sun, 14 Nov 93 05:44:06 PST From: Van Jacobson Milo, I just finished watching this week's "Computer Chronicles" on public TV which turned out to be all about the Internet. It included a nice segment on the NASA Science Internet which talked about packet video & showed a typical vat+nv+wb session in progress (you could make out all three tools quite clearly). Imagine my surprise to hear your people say, twice, that these tools had been developed by NASA. I have checked with our budget office & they don't recall any NASA funding for vat, wb or sd. Perhaps the check got lost in the mail? - Van From rem-conf-request@es.net Sun Nov 14 10:19:14 1993 Received: from faui45.informatik.uni-erlangen.de by osi-east.es.net via ESnet SMTP service id <26146-0@osi-east.es.net>; Sun, 14 Nov 1993 07:18:35 +0000 Received: from faui43.informatik.uni-erlangen.de by uni-erlangen.de with SMTP; id AA24627 (5.65c-6/7.3v-FAU); Sun, 14 Nov 1993 16:18:16 +0100 Received: from faui45r.informatik.uni-erlangen.de by immd4.informatik.uni-erlangen.de with SMTP; id AA10966 (5.65c-6/7.3m-FAU); Sun, 14 Nov 1993 16:18:14 +0100 Message-Id: <199311141518.AA10966@faui43.informatik.uni-erlangen.de> Subject: Re: vat, wb & nv developed by nasa? To: van@ee.lbl.gov (Van Jacobson) Date: Sun, 14 Nov 1993 16:18:07 +0100 (MET) From: Toerless Eckert Cc: medin@nsipo.nasa.gov, rem-conf@es.net In-Reply-To: <9311141344.AA27636@rx7.ee.lbl.gov> from "Van Jacobson" at Nov 14, 93 02:44:06 pm Organisation: CSD IMMD IV, University of Erlangen, Germany X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 708 > I just finished watching this week's "Computer Chronicles" on > public TV which turned out to be all about the Internet. It > included a nice segment on the NASA Science Internet which > talked about packet video & showed a typical vat+nv+wb session > in progress (you could make out all three tools quite clearly). > Imagine my surprise to hear your people say, twice, that these > tools had been developed by NASA. I have checked with our > budget office & they don't recall any NASA funding for vat, wb > or sd. Perhaps the check got lost in the mail? Why don't you give NASA a choice - either they fund you now afterwards, or you urge the TV station to send out a correction message ;-)) Toerless From rem-conf-request@es.net Sun Nov 14 23:47:03 1993 Received: from dscs.arc.nasa.gov by osi-east.es.net via ESnet SMTP service id <01590-0@osi-east.es.net>; Sun, 14 Nov 1993 20:41:28 +0000 Received: from localhost.arc.nasa.gov by dscs.arc.nasa.gov (4.1/1.5T) id AA16451; Sun, 14 Nov 93 20:41:22 PST Message-Id: <9311150441.AA16451@dscs.arc.nasa.gov> To: Van Jacobson Cc: rem-conf@es.net Subject: Re: vat, wb & nv developed by nasa? In-Reply-To: Your message of "Sun, 14 Nov 93 05:44:06 PST." <9311141344.AA27636@rx7.ee.lbl.gov> Date: Sun, 14 Nov 93 20:41:21 -0800 From: "Milo S. Medin" (NASA ARC NSI Office) Err.... They aren't my people in the first place. :-) If it's the group I think it is, they are more lateral. My group does connectivity... You'd be talking about the Advanced Network Applications group (ANA, which is one of 3 groups in the Wide Area Networks branch - I run Network Systems). Seriously, I haven't the foggiest idea why anyone would claim that. We all ftp'd it from LBL, and I believe it was all DOE funding that paid for it (or maybe ARPA money). If someone claimed NASA paid for it, or that NASA wrote all that, they're clearly all wet. I don't normally watch computer chronicles, and I was on travel all last week (I'm in DC now and visiting the UN in NYC later this week, so I haven't really gotten a chance to watch it. I knew the CC people had come in to do a piece on Internet stuff, but most of the focus was supposed to be on applications. Are you sure April or whoever was talking really said that? That big a mistake is pretty hard to make. I'll forward this on to the people who manage that group, and see if we can address this and find out what happened. Sigh... Thanks, Milo From rem-conf-request@es.net Mon Nov 15 12:39:14 1993 Received: from ocfmail.ocf.llnl.gov by osi-east.es.net via ESnet SMTP service id <07814-0@osi-east.es.net>; Mon, 15 Nov 1993 09:21:57 +0000 Received: from framsparc.ocf.llnl.gov.ocf by ocfmail.ocf.llnl.gov (4.1/SMI-4.0) id AA07254; Mon, 15 Nov 93 09:21:55 PST Received: by framsparc.ocf.llnl.gov.ocf (4.1/SMI-4.1) id AA28710; Mon, 15 Nov 93 09:21:54 PST From: booloo@framsparc.ocf.llnl.gov (Mark Boolootian) Message-Id: <9311151721.AA28710@framsparc.ocf.llnl.gov.ocf> Subject: Re: vat, wb & nv developed by nasa? To: medin@nsipo.nasa.gov (Milo S. Medin) Date: Mon, 15 Nov 1993 09:21:53 -0800 (PST) Cc: van@ee.lbl.gov, rem-conf@es.net In-Reply-To: <9311150441.AA16451@dscs.arc.nasa.gov> from "Milo S. Medin" at Nov 14, 93 08:41:21 pm X-Mailer: ELM [version 2.4 PL17] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 691 Milo S. Medin writes: >really gotten a chance to watch it. I knew the CC people had come in to >do a piece on Internet stuff, but most of the focus was supposed to be on >applications. Are you sure April or whoever was talking really said that? >That big a mistake is pretty hard to make. I didn't see the whole show, but I did catch the part about NASA developing the audio/video stuff. I was surprised when they said this because they were showing vat and nv sessions. My recollection was that the show's host was the one who claimed NASA had developed these applications - however, I wasn't always able to hear the television audio so may have missed someone else's comments. mb From rem-conf-request@es.net Mon Nov 15 14:45:34 1993 Received: from MANNIX.BBN.COM by osi-east.es.net via ESnet SMTP service id <09324-0@osi-east.es.net>; Mon, 15 Nov 1993 11:30:06 +0000 To: Tuong Quang Nguyen cc: rem-conf@es.net, jescobar@BBN.COM Subject: Synchronization Date: Mon, 15 Nov 93 14:27:38 -0500 From: Julio Escobar >Hi, > >I'm interested in learning about intermedia synchronization, >especially between video and audio, for live applications such >as conferencing. If anyone know of any literature on this subject, >would you pass me a note? > >Thanks, > >Tom Nguyen >tnguyen@cs.ucsd.edu Dear Tom Nguyen, Below the dashed line is a postscript version of a paper that Craig Partridge, Debbie Deutsch, and I, published in Globecom 92. A more detailed paper has been accepted for publication in the IEEE/ACM Transactions on Networking. I have more material/information and will be happy to send/discuss if you let me know. Regards, Julio Escobar, Bolt Beranek and Newman, Inc (617) 873-4579, jescobar@bbn.com ---------------------------------------------------------------------- %! for use by dvi2ps Version 2.30 %% The reference info is: %% J.Escobar, D.Deutsch, C.Partridge %% "Flow Synchronization Protocol" %% IEEE Global Communications Conference %% December 1992, p.p. 1381-1387 /TeXDict 200 dict def TeXDict begin /Resolution 300 def /Inch{Resolution mul}def /Mtrx 6 array def /@letter {letter initmatrix 72 Resolution div dup neg scale 310 -3005 translate Mtrx currentmatrix pop }def /@note {note initmatrix 72 Resolution div dup neg scale 310 -3005 translate Mtrx currentmatrix pop }def /@landscape {letter initmatrix 72 Resolution div dup neg scale Mtrx currentmatrix 0 0.0 put Mtrx 1 -1.0 put Mtrx 2 1.0 put Mtrx 3 0.0 put Mtrx setmatrix 300 310 translate Mtrx currentmatrix pop }def /@legal {legal initmatrix 72 Resolution div dup neg scale 295 -3880 translate Mtrx currentmatrix pop }def /@manualfeed {statusdict /manualfeed true put }def /@copies {/#copies exch def }def /@newfont {/newname exch def pop newname 7 dict def newname load begin /FontType 3 def /FontMatrix [1 0 0 -1 0 0] def /FontBBox [0 0 1 1] def /BitMaps 128 array def /BuildChar{CharBuilder}def /Encoding 128 array def 0 1 127{Encoding exch /.undef put}for end newname newname load definefont pop }def /ch-image{ch-data 0 get}def /ch-width{ch-data 1 get}def /ch-height{ch-data 2 get}def /ch-xoff{ch-data 3 get}def /ch-yoff{ch-data 4 get}def /ch-tfmw{ch-data 5 get}def /CharBuilder {/ch-code exch def /font-dict exch def /ch-data font-dict /BitMaps get ch-code get def ch-data null eq not {ch-tfmw 0 ch-xoff neg ch-yoff neg ch-width ch-xoff sub ch-height ch-yoff sub setcachedevice ch-width ch-height true [1 0 0 1 ch-xoff ch-yoff] {ch-image}imagemask } if }def /@sf {dup /FontName known {dup /FontName get tempstring cvs (SmallCaps) search {/smallcaps true def pop pop pop} {/smallcaps false def pop} ifelse } {/smallcaps false def} ifelse setfont() pop }def /@dc {/ch-code exch def dup 0 get length 2 lt {pop [ <00> 1 1 0 0 8.00 ]} if /ch-data exch def currentfont /BitMaps get ch-code ch-data put currentfont /Encoding get ch-code dup ( ) cvs cvn put }def /@bop0 { }def /@bop1 {pop erasepage initgraphics Mtrx setmatrix /SaveImage save def() pop }def /@eop {showpage SaveImage restore() pop }def /@start {@letter }def /@end {end }def /p {moveto }def /r {0 rmoveto }def /s {smallcaps{SmallCapShow}{show}ifelse }def /c {c-string exch 0 exch put c-string s }def /c-string ( ) def /ru {/dy exch neg def /dx exch def /x currentpoint /y exch def def newpath x y moveto dx 0 rlineto 0 dy rlineto dx neg 0 rlineto closepath fill x y moveto }def /@SpecialDefaults {/hs 8.5 Inch def /vs 11 Inch def /ho 0 def /vo 0 def /hsc 1 def /vsc 1 def /CLIP false def }def /@hsize{/hs exch def /CLIP true def}def /@vsize{/vs exch def /CLIP true def}def /@hoffset{/ho exch def}def /@voffset{/vo excl def}def /@hscale{/hsc exch def}def /@vscale{/vsc exch def}def /@setclipper {hsc vsc scale CLIP {newpath 0 0 moveto hs 0 rlineto 0 vs rlineto hs neg 0 rlineto closepath clip} if }def /@beginspecial {gsave /SpecialSave save def currentpoint transform initgraphics itransform translate 0 0 moveto @SpecialDefaults @MacSetUp }def /@setspecial { MacDrwgs {md begin /pxt ho def /pyt vo neg def end} {ho vo translate @setclipper} ifelse }def /@endspecial {SpecialSave restore grestore }def /TeXscale{65536 div}def gsave initgraphics /DocumentInitState [ matrix currentmatrix currentlinewidth currentlinecap currentlinejoin currentdash currentgray currentmiterlimit ] cvx def grestore /startTexFig{ /SavedState save def userdict maxlength dict begin currentpoint transform DocumentInitState setmiterlimit setgray setdash setlinejoin setlinecap setlinewidth setmatrix itransform moveto /ury exch TeXscale def /urx exch TeXscale def /lly exch TeXscale def /llx exch TeXscale def /y exch TeXscale def /x exch TeXscale def currentpoint /cy exch def /cx exch def /sx x urx llx sub div def /sy y ury lly sub div def sx sy scale cx sx div llx sub cy sy div ury sub translate /DefFigCTM matrix currentmatrix def /initmatrix{ DefFigCTM setmatrix }def /defaultmatrix{ DefFigCTM exch copy }def /initgraphics{ DocumentInitState setmiterlimit setgray setdash setlinejoin setlinecap setlinewidth setmatrix DefFigCTM setmatrix }def /showpage{ initgraphics }def }def /clipFig{ currentpoint 6 2 roll newpath 4 copy 4 2 roll moveto 6 -1 roll exch lineto exch lineto exch lineto closepath clip newpath moveto }def /doclip{llx lly urx ury clipFig}def /endTexFig{ end SavedState restore }def /ReEncodeForTeX {/newfontname exch def /basefontname exch def /TeXstr 30 string def /basefontdict basefontname findfont def /newfont basefontdict maxlength dict def basefontdict {exch dup /FID ne {dup /Encoding eq {exch dup length array copy newfont 3 1 roll put} {exch newfont 3 1 roll put} ifelse } {pop pop} ifelse }forall basefontname TeXstr cvs (Dingbat) search {pop pop pop} {pop /TeXvec basefontname TeXstr cvs (Courier) search {pop pop pop TeXcourvec} {pop TeXnormalvec} ifelse def TeXvec aload pop TeXvec length 2 idiv {newfont /Encoding get 3 1 roll put} repeat } ifelse newfontname newfont definefont pop }def /TeXnormalvec [ 8#014 /fi 8#015 /fl 8#020 /dotlessi 8#022 /grave 8#023 /acute 8#024 /caron 8#025 /breve 8#026 /macron 8#027 /ring 8#030 /cedilla 8#031 /germandbls 8#032 /ae 8#033 /oe 8#034 /oslash 8#035 /AE 8#036 /OE 8#037 /Oslash 8#042 /quotedblright 8#074 /exclamdown 8#076 /questiondown 8#134 /quotedblleft 8#136 /circumflex 8#137 /dotaccent 8#173 /endash 8#174 /emdash 8#175 /quotedbl 8#177 /dieresis ] def /TeXcourvec [ 8#016 /exclamdown 8#017 /questiondown 8#020 /dotlessi 8#022 /grave 8#023 /acute 8#024 /caron 8#025 /breve 8#026 /macron 8#027 /ring 8#030 /cedilla 8#031 /germandbls 8#032 /ae 8#033 /oe 8#034 /oslash 8#035 /AE 8#036 /OE 8#037 /Oslash 8#074 /less 8#076 /greater 8#134 /backslash 8#136 /circumflex 8#137 /underscore 8#173 /braceleft 8#174 /bar 8#175 /braceright 8#177 /dieresis ] def /TeXPSmakefont{ /TeXsize exch def findfont [ TeXsize 0 0 TeXsize neg 0 0 ] makefont }def /ObliqueFont{ /ObliqueAngle exch def /ObliqueBaseName exch def /ObliqueFontName exch def /ObliqueTransform [1 0 ObliqueAngle sin ObliqueAngle cos div 1 0 0] def /basefontdict ObliqueBaseName findfont ObliqueTransform makefont def /newfont basefontdict maxlength dict def basefontdict {exch dup /FID ne {dup /Encoding eq {exch dup length array copy newfont 3 1 roll put} {exch newfont 3 1 roll put} ifelse } {pop pop} ifelse }forall newfont /FontName ObliqueFontName put ObliqueFontName newfont definefont pop }def /Times-Oblique /Times-Roman 15.5 ObliqueFont /Times-BoldOblique /Times-Bold 15 ObliqueFont /Palatino-Oblique /Palatino-Roman 10 ObliqueFont /Palatino-BoldOblique /Palatino-Bold 10 ObliqueFont /Times-ItalicUnslanted /Times-Italic -15.15 ObliqueFont /SmallCapsFont{ /SmallCapsBaseName exch def /SmallCapsFontName exch def /basefontdict SmallCapsBaseName findfont def /newfont basefontdict maxlength dict def basefontdict {exch dup /FID ne {dup /Encoding eq {exch dup length array copy newfont 3 1 roll put} {exch newfont 3 1 roll put} ifelse } {pop pop} ifelse }forall newfont /FontName SmallCapsFontName put SmallCapsFontName newfont definefont pop }def /Times-SmallCaps /Times-Roman SmallCapsFont /Palatino-SmallCaps /Palatino-Roman SmallCapsFont /SmallCapShow{ /achar (A) def /xfac 0.8 def /yfac 0.8 def /xrec 1 xfac div def /yrec 1 yfac div def {dup dup 8#141 ge exch 8#172 le and {8#40 sub achar exch 0 exch put achar xfac yfac scale show xrec yrec scale} {achar exch 0 exch put achar show} ifelse }forall }def /tempstring 100 string def /MacDrwgs false def /@MacSetUp {userdict /md known {userdict /md get type /dicttype eq {/MacDrwgs true def md begin /psu /psu load {/letter{}def /note{}def /legal{}def statusdict /waittimeout 300 put /page{pop}def /pyt vo neg def /pxt ho def } concatprocs def /od /od load {@setclipper} concatprocs def end} if} if }def /concatprocs {/p2 exch cvlit def /p1 exch cvlit def /p p1 length p2 length add array def p 0 p1 putinterval p p1 length p2 putinterval p cvx }def end TeXDict begin @start %%Title: draft3.dvi %%Creator: dvi2ps %%EndProlog 1 @bop0 /Times-Roman /t-rom.420 ReEncodeForTeX /t-rom.420 /t-rom.420 58.115401 TeXPSmakefont def /Times-Roman /t-rom.360 ReEncodeForTeX /t-rom.360 /t-rom.360 49.813200 TeXPSmakefont def [ 300 ] /amsy8.300 @newfont amsy8.300 @sf [<060006000400C460E4E03F800E003F80E4E0C460C460040006000600> 16 14 -3 -2 17.642] 3 @dc /Times-Italic /t-ita.330 ReEncodeForTeX /t-ita.330 /t-ita.330 45.662100 TeXPSmakefont def /Times-Bold /t-bol.420 ReEncodeForTeX /t-bol.420 /t-bol.420 58.115401 TeXPSmakefont def /Times-Roman /t-rom.330 ReEncodeForTeX /t-rom.330 /t-rom.330 45.662100 TeXPSmakefont def [ 300 ] /amsy6.300 @newfont amsy6.300 @sf [<0C000C00EDC0FFC00C007F80EDC0CCC00C000C00> 16 10 -3 -2 15.912] 3 @dc /Times-Roman /t-rom.270 ReEncodeForTeX /t-rom.270 /t-rom.270 37.359900 TeXPSmakefont def 1 @bop1 t-rom.420 @sf 446 96 p (FLOW) s 19 r (SYNCHRONIZA) s -5 r (TION) s 18 r (PROT) s 0 r (OCOL) s t-rom.360 @sf 496 223 p (Julio) s 17 r (Escobar) s -1 r 44 c 15 r (Debra) s 17 r (Deutsch,) s 16 r (Craig) s 17 r (Partridge) s amsy8.300 @sf 1454 205 p 3 c t-rom.360 @sf 652 339 p (Bolt) s 17 r (Beranek) s 16 r (and) s 17 r (Newman) s 16 r (Inc.) s 547 397 p (10) s 17 r (Moulton) s 17 r (Street,) s 16 r (Cambridge,) s 17 r (MA02138) s t-ita.330 @sf 313 574 p (Abstract) s -73 708 p (High) s 21 r (Speed) s 23 r (Networks) s 22 r (will) s 23 r (facilitate) s 22 r (the) s 23 r (advent) s 22 r (of) s -119 762 p (multimedia) s 20 r (and) s 22 r (distributed) s 21 r (applications.) s 39 r 87 c -3 r 101 c 20 r (pr) s -1 r (esent) s -119 816 p (an) s 14 r (adaptive) s 15 r (\015ow) s 15 r (synchr) s -1 r (onization) s 14 r (pr) s 0 r (otocol) s 13 r (that) s 15 r (permits) s -119 870 p (synchr) s -2 r (onized) s 19 r (delivery) s 20 r (of) s 20 r (data) s 19 r (to) s 20 r (and) s 20 r (fr) s -1 r (om) s 19 r (geograph-) s -119 924 p (ically) s 26 r (distributed) s 27 r (sites.) s 55 r (Applications) s 26 r (include) s 27 r (inter) s 0 r 45 c -119 978 p (str) s -2 r (eam) s 13 r (synchr) s 0 r (onization,) s 13 r (synchr) s -1 r (onized) s 13 r (delivery) s 14 r (of) s 14 r (infor-) s -119 1032 p (mation) s 17 r (in) s 18 r 97 c 18 r (multisite) s 18 r (confer) s -1 r (ence,) s 18 r (and) s 18 r (synchr) s 0 r (onization) s -119 1086 p (for) s 14 r (concurr) s 0 r (ency) s 14 r (contr) s -1 r (ol) s 14 r (in) s 16 r (distributed) s 15 r (computations.) s -73 1145 p (The) s 12 r (contributions) s 14 r (of) s 14 r (this) s 13 r (pr) s 0 r (otocol) s 12 r (in) s 14 r (the) s 13 r (ar) s 0 r (ea) s 12 r (of) s 14 r (\015ow) s -119 1199 p (synchr) s -2 r (onization) s 10 r (ar) s 0 r 101 c 9 r (the) s 11 r (intr) s 0 r (oduction) s 10 r (of) s 10 r (an) s 11 r (adaptive) s 11 r (syn-) s -119 1253 p (chr) s -2 r (onization) s 17 r (delay) s -1 r 44 c 18 r (the) s 18 r (\015exibility) s 18 r (to) s 18 r (maintain) s 18 r (multiple) s -119 1307 p (synchr) s -2 r (onization) s 10 r (gr) s -1 r (oups,) s 11 r (and) s 10 r (the) s 11 r (use) s 10 r (of) s 11 r 97 c 10 r (modular) s 11 r (ar) s -1 r (chi-) s -119 1361 p (tectur) s -2 r 101 c 13 r (that) s 13 r (permits) s 14 r (the) s 14 r (client) s 13 r (application) s 14 r (to) s 13 r (tailor) s 14 r (syn-) s -119 1415 p (chr) s -2 r (onization) s 21 r (calculations) s 23 r (to) s 22 r (its) s 22 r (service) s 22 r 114 c -1 r (equir) s -1 r (ements.) s -119 1469 p 87 c -4 r 101 c 23 r (take) s 23 r (advantage) s 24 r (of) s 24 r (network) s 23 r (pr) s 0 r (otocols) s 22 r (capable) s 24 r (of) s -119 1523 p (maintaining) s 16 r (network) s 17 r (clock) s 16 r (synchr) s 0 r (onization) s 16 r (in) s 16 r (the) s 17 r (mil-) s -119 1577 p (lisecond) s 14 r (range.) s t-bol.420 @sf -119 1750 p 49 c 57 r (Intr) s 0 r (oduction) s t-rom.330 @sf -119 1860 p (As) s 14 r (network) s 15 r (bandwidth) s 15 r (increases,) s 15 r (we) s 15 r (expect) s 14 r 97 c 15 r (sur) s 0 r (ge) s 14 r (of) s -119 1914 p (communication) s 20 r (applications) s 21 r (such) s 21 r (as) s 20 r (multimedia) s 21 r (con-) s -119 1968 p (ferencing) s 19 r (and) s 20 r (distributed) s 20 r (data) s 20 r (processing,) s 21 r (which) s 20 r (will) s -119 2022 p (require) s 11 r (end-to-end) s 11 r (synchronization) s 12 r (among) s 11 r (participating) s -119 2076 p (\015ows) s 14 r 91 c 0 r (13) s 0 r (].) s 21 r (Flow) s 16 r (synchronization) s 15 r (is) s 15 r (the) s 16 r (process) s 15 r (of) s 15 r (en-) s -119 2130 p (suring) s 10 r (that) s 12 r (information) s 11 r (in) s 11 r (related) s 12 r (\015ows) s 11 r (is) s 11 r (presented) s 11 r (in) s 12 r 97 c -119 2184 p (proper) s 15 r (time-relationship.) s 22 r 65 c 15 r (good) s 16 r (example) s 16 r (of) s 16 r (synchro-) s -119 2238 p (nization) s 12 r (is) s 13 r (the) s 13 r (problem) s 13 r (of) s 13 r (timing) s 13 r (the) s 13 r (outputs) s 13 r (of) s 13 r 97 c 13 r (voice) s -119 2297 p 408 2 ru amsy6.300 @sf -70 2324 p 3 c t-rom.270 @sf -52 2340 p (This) s 13 r (work) s 13 r (was) s 13 r (sponsored) s 13 r (by) s 14 r (the) s 13 r (Defense) s 13 r (Advanced) s 13 r (Research) s -119 2385 p (Projects) s 16 r (Agency) s 16 r (under) s 17 r (contract) s 17 r (No.) s 29 r (MDA-903-89-C-0020.) s 30 r (The) s -119 2431 p (views) s 13 r (expressed) s 14 r (in) s 14 r (this) s 14 r (document) s 14 r (are) s 14 r (not) s 14 r (necessarily) s 14 r (those) s 14 r (of) s 14 r (the) s -119 2477 p (Defense) s 12 r (Advanced) s 13 r (Research) s 13 r (Projects) s 13 r (Agency) s -1 r 46 c 17 r (\(APPROVED) s 13 r (FOR) s -119 2522 p (PUBLIC) s 13 r (RELEASE,) s 14 r (DISTRIBUTION) s 14 r (UNLIMITED.) s 14 r 41 c 14 r (Thanks) s 14 r (to) s -119 2568 p 87 c -3 r (alter) s 8 r (Milliken) s 10 r (and) s 9 r (Isidro) s 10 r (Castineyra) s 9 r (for) s 10 r (many) s 9 r (helpful) s 10 r (suggestions.) s -119 2615 p (IEEE) s 9 r (Global) s 9 r (Communications) s 9 r (Conference,) s 9 r (December) s 9 r (1992.) s t-rom.330 @sf 1050 574 p (stream) s 17 r (and) s 18 r 97 c 17 r (video) s 18 r (stream) s 17 r (so) s 18 r (that) s 17 r (lip) s 18 r (synchronization) s 1050 628 p (is) s 15 r (achieved.) s 1096 693 p (Important) s 44 r (work) s 44 r (exists) s 44 r (on) s 44 r (synchronization) s 45 r (of) s 1050 747 p (constant-rate) s 28 r (data) s 28 r (in) s 28 r (one-to-many) s 28 r (and) s 28 r (many-to-one) s 1050 801 p (con\014gurations) s 25 r (of) s 25 r (sources) s 25 r (to) s 24 r (destinations) s 25 r (\(e.g.,) s 28 r 91 c 0 r 49 c -1 r 49 c 0 r (],) s 1050 855 p 91 c 0 r 56 c 0 r (]\),) s 17 r (on) s 16 r (multimedia) s 17 r (and) s 16 r (distributed) s 17 r (architectures) s 16 r (\(e.g.,) s 1050 909 p 91 c 0 r (13) s 0 r (],) s 25 r 91 c 0 r 57 c 0 r (],) s 25 r 91 c 0 r 49 c 0 r (]\),) s 25 r (on) s 23 r (clock) s 23 r (synchronization) s 23 r (across) s 23 r (net-) s 1050 963 p (works) s 10 r (\(e.g.,) s 12 r 91 c 0 r (12) s 0 r (],) s 11 r 91 c 0 r (10) s 0 r (],) s 11 r 91 c 0 r 50 c 0 r (]\),) s 12 r (and) s 10 r (in) s 10 r (methods) s 10 r (for) s 11 r (schedul-) s 1050 1017 p (ing) s 10 r (delivery) s 11 r (of) s 10 r (components) s 10 r (of) s 11 r 97 c 10 r (multimedia) s 10 r (object) s 11 r (\(e.g.,) s 1050 1071 p 91 c 0 r (20) s 0 r (],) s 15 r 91 c 0 r (19) s 0 r (]\).) s 1096 1135 p (These) s 26 r (developments) s 27 r (have) s 26 r (allowed) s 26 r (network) s 27 r (clock) s 1050 1189 p (synchronization) s 16 r (to) s 17 r (within) s 16 r 97 c 16 r (few) s 17 r (milliseconds) s 16 r 91 c 0 r (12) s 0 r 93 c 16 r (and) s 1050 1243 p (algorithms) s 17 r (for) s 18 r (multimedia) s 17 r (synchronization) s 17 r (across) s 18 r (net-) s 1050 1297 p (works) s 19 r 91 c 0 r (18) s 0 r (],) s 21 r 91 c 0 r 56 c 0 r (].) s 32 r (However) s -1 r 44 c 20 r (current) s 19 r (work) s 20 r (on) s 19 r (synchro-) s 1050 1351 p (nization) s 15 r (services) s 14 r (for) s 15 r (network) s 14 r (applications) s 15 r (does) s 14 r (not) s 15 r (ad-) s 1050 1405 p (dress) s 14 r (the) s 15 r (dynamic) s 14 r (nature) s 15 r (of) s 14 r (the) s 14 r (networks) s 15 r (and) s 14 r (does) s 15 r (not) s 1050 1459 p (explicitly) s 17 r (account) s 17 r (for) s 17 r (the) s 17 r (heterogeneous) s 17 r (nature) s 18 r (of) s 17 r (po-) s 1050 1513 p (tential) s 22 r (applications.) s 42 r 87 c -3 r 101 c 21 r (have) s 23 r (sought) s 22 r (to) s 22 r (redress) s 23 r (this) s 1050 1567 p (imbalance.) s 1096 1631 p 87 c -3 r 101 c 22 r (have) s 22 r (developed) s 23 r 97 c 23 r (\015ow) s 22 r (synchronization) s 23 r (proto-) s 1050 1685 p (col) s 23 r (based) s 23 r (on) s 23 r (synchronized) s 23 r (network) s 22 r (clocks) s 23 r (that) s 23 r (pro-) s 1050 1739 p (vides) s 15 r (end-to-end) s 15 r (synchronization) s 15 r (across) s 15 r (networks,) s 15 r (and) s 1050 1793 p (adapts) s 19 r (to) s 19 r (changes) s 19 r (in) s 19 r (\015ow) s 19 r (delays.) s 31 r (It) s 19 r (can) s 19 r (synchronize) s 1050 1847 p (\015ows) s 22 r (from) s 23 r 97 c 22 r (single) s 22 r (site) s 23 r (or) s 22 r (from) s 22 r (multiple) s 23 r (sites) s 22 r (to) s 22 r 97 c 1050 1901 p (single) s 16 r (or) s 15 r (multiple) s 16 r (destinations) s 15 r (\(one-to-many) s -2 r 44 c 15 r (many-to-) s 1050 1955 p (one,) s 14 r (or) s 14 r (parallel) s 13 r (sets\).) s 20 r (It) s 14 r (can) s 14 r (synchronize) s 13 r (them) s 14 r (per) s 14 r (\015ow) s 1050 2009 p (type) s 17 r (or) s 17 r (user) s 16 r (group,) s 17 r (an) s 17 r (important) s 17 r (service) s 17 r (given) s 17 r (the) s 16 r (di-) s 1050 2063 p (versity) s 16 r (of) s 16 r (applications.) s 23 r (The) s 16 r (protocol) s 16 r (time-stamps) s 16 r (data) s 1050 2117 p (at) s 18 r (the) s 17 r (sources) s 18 r (and) s 18 r (equalizes) s 17 r (delay) s 18 r (at) s 18 r (the) s 17 r (destinations,) s 1050 2171 p (to) s 23 r (enforce) s 22 r 97 c 23 r (\014xed) s 22 r (end-to-end) s 23 r (delay) s 22 r (among) s 23 r (\015ows) s 22 r (to) s 1050 2225 p (be) s 17 r (synchronized.) s 24 r (The) s 17 r (equalized) s 17 r (delay) s 16 r (can) s 17 r (be) s 17 r (\014xed) s 16 r (or) s 1050 2279 p (adaptive.) s 1096 2344 p (The) s 24 r (protocol) s 24 r (uses) s 24 r 97 c 24 r (modular) s 24 r (architecture) s 24 r (that) s 23 r (al-) s 1050 2398 p (lows) s 14 r (applications) s 13 r (to) s 14 r (in\015uence) s 13 r (the) s 14 r (equalization) s 13 r (process:) s 1050 2452 p (for) s 15 r (example,) s 16 r (how) s 15 r (to) s 16 r (deal) s 15 r (with) s 16 r (abnormally) s 15 r (long) s 15 r (delays) s 1050 2506 p (across) s 17 r (the) s 17 r (network) s 17 r (or) s 17 r (with) s 18 r (out-of-sequence) s 17 r (data.) s 26 r (The) s 1050 2560 p (protocol) s 17 r (uses) s 17 r (its) s 17 r (own) s 18 r (time-stamped) s 17 r (data) s 17 r (unit) s 17 r (to) s 17 r (make) s 1050 2614 p (it) s 13 r (minimally) s 13 r (dependent) s 13 r (on) s 13 r (the) s 13 r (transport) s 13 r (mechanisms) s 14 r (of) s 964 2738 p (1381) s @eop 2 @bop0 [ 300 ] /linew10.300 @newfont linew10.300 @sf [<60000000F0000000F8000000780000007C0000003C0000003E0000001E0000001F0000000F0000000F8000000780000007C0 000003C0000003E0000001E0000001F0000000F0000000F8000000780000007C0000003C0000003E0000001E0000001F0000 000F0000000F8000000780000007C0000003C0000003E0000001E0000001F0000000F0000000F8000000780000007C000000 3C0000003E0000001E0000001F0000000F0000000F80000007800000078000000300> 32 46 2 2 20.755] 1 @dc [<0000008000004000006000007000007800007C00003E00003F00003F80003FC0003FE0003FF0003FF8003FFE001FFF001FFF 801FFFC01FFFE01FFF801FFE001FF8001FE0001F80001E0000180000> 24 26 0 0 20.755] 11 @dc /Times-Roman /t-rom.300 ReEncodeForTeX /t-rom.300 /t-rom.300 41.511000 TeXPSmakefont def [<80000000E0000000FC000000FF000000FFC00000FFF80000FFFF0000FFFFE000FFFFFE00FFFFFE00FFFFE000FFFF0000FFF8 0000FFC00000FF000000FC000000E000000080000000> 32 18 -17 9 41.510] 45 @dc [ 329 ] /ammi10.329 @newfont ammi10.329 @sf [<1F003F8079C078E0787078307C303C003C003C003E001E001E001E001F000F000F000F00FFF8FFF80780078007C003C003C0 03C003C00180> 16 28 -1 0 16.287] 116 @dc [ 300 ] /ammi8.300 @newfont ammi8.300 @sf [<7000700078003800380038003C001C001E00DE00FF306F786FF87DF83870> 16 15 -1 0 14.942] 114 @dc ammi10.329 @sf [ 40 31 -2 0 37.878] 1 @dc [<0F80003FE00078F000703000F03800F01C00F00C00F00E00F00600F00600F807007807007807003C07003C07001E0F000F1F 0007FE0003FE0000FC0001F80003E00007C0000780000700000700000700000300C00380C001E3C000FF80003E00> 24 32 -2 0 18.939] 14 @dc ammi8.300 @sf [<1E3C003F7E0071F60060F700607300E07300707800703800703800703800383C00183C000C3C0007FC0003DE00000E00000E 00000E00000F00000700000700001F00001F00> 24 23 -1 0 18.184] 100 @dc [<3E007F80E3C0E0E0C060C000E000F800FF80EFC070E030601C600FE007C0> 16 15 -2 0 15.311] 101 @dc [<3C007E00770073807180718078003800380038003C001C001C00FFC0FFC00E000E000E000F0007000700> 16 21 -1 0 12.799] 116 @dc [<1F003FC071E060706030E000700070007000706038F018F00E7007F001E0> 16 15 -1 0 15.311] 99 @dc [ 300 ] /lcirclew10.300 @newfont lcirclew10.300 @sf [<003FFC000000FFFF000001FFFF800007FFFFE0000FE007F0001F8001F8001F0000F8003E00007C007C00003E007800001E00 F800001F00F000000F00F000000F00F000000F00F000000F00F000000F80F000000F80F000000F00F000000F00F000000F00 F000000F00F800001F007800001E007C00003E003E00007C001F0000F8001F8001F8000FE007F00007FFFFE00001FFFF8000 00FFFF0000003FFC00000000800000> 40 33 16 16 29.057] 102 @dc [<00000007F0000000FFF8000003FFF800001FFFF000003FFC000000FF80000003FE00000007F00000000FE00000001F800000 003E000000007C00000000F800000001F000000003E000000003C000000007C000000007800000000F800000001F00000000 1E000000001E000000003E000000003C000000007C000000007800000000780000000078000000007800000000F800000000 F000000000F000000000F000000000F000000000F000000000F0000000006000000000> 40 37 0 0 66.416] 14 @dc [<7F00000000FFF8000000FFFE0000007FFFC0000001FFE00000000FF800000003FE000000007F000000003F800000000FC000 000003E000000001F000000000F8000000007C000000003E000000001E000000001F000000000F000000000F8000000007C0 00000003C000000003C000000003E000000001E000000001F000000000F000000000F000000000F000000000F000000000F8 0000000078000000007800000000780000000078000000007800000000780000000030> 40 37 33 0 66.416] 13 @dc [<6000000000F000000000F000000000F000000000F000000000F000000000F000000000F80000000078000000007800000000 780000000078000000007C000000003C000000003E000000001E000000001E000000001F000000000F800000000780000000 07C000000003C000000003E000000001F000000000F8000000007C000000003E000000001F800000000FE000000007F00000 0003FE00000000FF800000003FFC0000001FFFF0000003FFF8000000FFF800000007F0> 40 37 0 33 66.416] 15 @dc [<000000003000000000780000000078000000007800000000780000000078000000007800000000F800000000F000000000F0 00000000F000000000F000000001F000000001E000000003E000000003C000000003C000000007C00000000F800000000F00 0000001F000000001E000000003E000000007C00000000F800000001F000000003E00000000FC00000003F800000007F0000 0003FE0000000FF8000001FFE000007FFFC00000FFFE000000FFF80000007F00000000> 40 37 33 33 66.416] 12 @dc [<00000000000FF80000000001FFFC000000000FFFFC000000007FFFF800000003FFF8000000000FFF00000000001FF8000000 00007FC00000000001FE000000000003F8000000000007F000000000001FC000000000003F0000000000007E000000000000 FC000000000001F0000000000003E0000000000007C000000000000F8000000000001F0000000000001E0000000000003E00 00000000007C000000000000F8000000000000F0000000000001F0000000000001E0000000000003E0000000000007C00000 000000078000000000000F8000000000000F0000000000000F0000000000001F0000000000001E0000000000001E00000000 00003E0000000000003C0000000000003C0000000000007C0000000000007800000000000078000000000000780000000000 0078000000000000F8000000000000F0000000000000F0000000000000F0000000000000F0000000000000F0000000000000 F0000000000000F0000000000000F000000000000060000000000000> 56 54 0 0 99.624] 22 @dc [<7FC00000000000FFFE0000000000FFFFC0000000007FFFF800000000007FFF000000000003FFC000000000007FE000000000 000FF8000000000001FE0000000000007F0000000000003F8000000000000FE0000000000003F0000000000001F800000000 0000FC0000000000003E0000000000001F0000000000000F80000000000007C0000000000003E0000000000001E000000000 0001F0000000000000F80000000000007C0000000000003C0000000000003E0000000000001E0000000000001F0000000000 000F8000000000000780000000000007C0000000000003C0000000000003C0000000000003E0000000000001E00000000000 01E0000000000001F0000000000000F0000000000000F0000000000000F80000000000007800000000000078000000000000 78000000000000780000000000007C0000000000003C0000000000003C0000000000003C0000000000003C0000000000003C 0000000000003C0000000000003C0000000000003C00000000000018> 56 54 50 0 99.624] 21 @dc [<60000000000000F0000000000000F0000000000000F0000000000000F0000000000000F0000000000000F0000000000000F0 000000000000F0000000000000F8000000000000780000000000007800000000000078000000000000780000000000007C00 00000000003C0000000000003C0000000000003E0000000000001E0000000000001E0000000000001F0000000000000F0000 000000000F0000000000000F8000000000000780000000000007C0000000000003E0000000000001E0000000000001F00000 00000000F0000000000000F80000000000007C0000000000003E0000000000001E0000000000001F0000000000000F800000 00000007C0000000000003E0000000000001F0000000000000FC0000000000007E0000000000003F0000000000001FC00000 00000007F0000000000003F8000000000001FE0000000000007FC000000000001FF800000000000FFF000000000003FFF800 000000007FFFF8000000000FFFFC0000000001FFFC00000000000FF8> 56 54 0 50 99.624] 23 @dc [<000000000000180000000000003C0000000000003C0000000000003C0000000000003C0000000000003C0000000000003C00 00000000003C0000000000003C0000000000007C000000000000780000000000007800000000000078000000000000780000 00000000F8000000000000F0000000000000F0000000000001F0000000000001E0000000000001E0000000000003E0000000 000003C0000000000003C0000000000007C00000000000078000000000000F8000000000001F0000000000001E0000000000 003E0000000000003C0000000000007C000000000000F8000000000001F0000000000001E0000000000003E0000000000007 C000000000000F8000000000001F0000000000003E000000000000FC000000000001F8000000000003F000000000000FE000 000000003F8000000000007F000000000001FE00000000000FF800000000007FE00000000003FFC0000000007FFF00000000 7FFFF800000000FFFFC000000000FFFE00000000007FC00000000000> 56 54 50 50 99.624] 20 @dc [<6000000000000000000000F000000000000000000000F000000000000000000000F000000000000000000000F00000000000 0000000000F000000000000000000000F000000000000000000000F000000000000000000000F000000000000000000000F0 00000000000000000000F8000000000000000000007800000000000000000000780000000000000000000078000000000000 000000007800000000000000000000780000000000000000000078000000000000000000007C000000000000000000003C00 0000000000000000003C000000000000000000003C000000000000000000003E000000000000000000001E00000000000000 0000001E000000000000000000001E000000000000000000001F000000000000000000000F000000000000000000000F0000 00000000000000000F800000000000000000000780000000000000000000078000000000000000000007C000000000000000 000003C000000000000000000003E000000000000000000001E000000000000000000001E000000000000000000001F00000 0000000000000000F000000000000000000000F80000000000000000000078000000000000000000007C0000000000000000 00003C000000000000000000003E000000000000000000001F000000000000000000000F000000000000000000000F800000 0000000000000007C000000000000000000003C000000000000000000003E000000000000000000001F00000000000000000 0000F000000000000000000000F8000000000000000000007C000000000000000000003E000000000000000000001E000000 000000000000001F000000000000000000000F8000000000000000000007C000000000000000000003E00000000000000000 0001F000000000000000000000F8000000000000000000007C000000000000000000003E000000000000000000001F000000 000000000000000FC000000000000000000007E000000000000000000003F000000000000000000001FC0000000000000000 00007E000000000000000000003F800000000000000000001FC000000000000000000007F000000000000000000003F80000 0000000000000000FE000000000000000000007F800000000000000000001FE00000000000000000000FFC00000000000000 000003FF00000000000000000000FFE00000000000000000003FFC00000000000000000007FFC0000000000000000001FFFC 0000000000000000003FFFF8000000000000000007FFFFFC00000000000000007FFFFE000000000000000007FFFE00000000 00000000000FFC> 88 87 0 83 166.040] 39 @dc [<0000000000000000000FFC000000000000000007FFFE00000000000000007FFFFE0000000000000007FFFFFC000000000000 003FFFF80000000000000001FFFC000000000000000007FFC000000000000000003FFC000000000000000000FFE000000000 0000000003FF0000000000000000000FFC0000000000000000001FE00000000000000000007F80000000000000000000FE00 000000000000000003F800000000000000000007F00000000000000000001FC00000000000000000003F8000000000000000 00007E00000000000000000001FC00000000000000000003F000000000000000000007E00000000000000000000FC0000000 0000000000001F000000000000000000003E000000000000000000007C00000000000000000000F800000000000000000001 F000000000000000000003E000000000000000000007C00000000000000000000F800000000000000000001F000000000000 000000001E000000000000000000003E000000000000000000007C00000000000000000000F800000000000000000000F000 000000000000000001F000000000000000000003E000000000000000000003C000000000000000000007C000000000000000 00000F800000000000000000000F000000000000000000001F000000000000000000003E000000000000000000003C000000 000000000000007C000000000000000000007800000000000000000000F800000000000000000000F0000000000000000000 01F000000000000000000001E000000000000000000001E000000000000000000003E000000000000000000003C000000000 000000000007C0000000000000000000078000000000000000000007800000000000000000000F800000000000000000000F 000000000000000000000F000000000000000000001F000000000000000000001E000000000000000000001E000000000000 000000001E000000000000000000003E000000000000000000003C000000000000000000003C000000000000000000003C00 0000000000000000007C00000000000000000000780000000000000000000078000000000000000000007800000000000000 000000780000000000000000000078000000000000000000007800000000000000000000F800000000000000000000F00000 0000000000000000F000000000000000000000F000000000000000000000F000000000000000000000F00000000000000000 0000F000000000000000000000F000000000000000000000F000000000000000000000F00000000000000000000060000000 00000000000000> 88 87 0 0 166.040] 38 @dc [<000000000000000000000C000000000000000000001E000000000000000000001E000000000000000000001E000000000000 000000001E000000000000000000001E000000000000000000001E000000000000000000001E000000000000000000001E00 0000000000000000001E000000000000000000003E000000000000000000003C000000000000000000003C00000000000000 0000003C000000000000000000003C000000000000000000003C000000000000000000003C000000000000000000007C0000 0000000000000000780000000000000000000078000000000000000000007800000000000000000000F80000000000000000 0000F000000000000000000000F000000000000000000000F000000000000000000001F000000000000000000001E0000000 00000000000001E000000000000000000003E000000000000000000003C000000000000000000003C0000000000000000000 07C000000000000000000007800000000000000000000F800000000000000000000F000000000000000000000F0000000000 00000000001F000000000000000000001E000000000000000000003E000000000000000000003C000000000000000000007C 000000000000000000007800000000000000000000F800000000000000000001F000000000000000000001E0000000000000 00000003E000000000000000000007C000000000000000000007800000000000000000000F800000000000000000001F0000 00000000000000001E000000000000000000003E000000000000000000007C00000000000000000000F80000000000000000 0000F000000000000000000001F000000000000000000003E000000000000000000007C00000000000000000000F80000000 0000000000001F000000000000000000003E000000000000000000007C00000000000000000000F800000000000000000001 F000000000000000000007E00000000000000000000FC00000000000000000001F800000000000000000007F000000000000 00000000FC00000000000000000003F800000000000000000007F00000000000000000001FC00000000000000000003F8000 0000000000000000FE00000000000000000003FC0000000000000000000FF00000000000000000007FE00000000000000000 01FF8000000000000000000FFE0000000000000000007FF8000000000000000007FFC000000000000000007FFF0000000000 0000003FFFF8000000000000007FFFFFC000000000000000FFFFFC0000000000000000FFFFC000000000000000007FE00000 00000000000000> 88 87 83 83 166.040] 36 @dc [<7FE0000000000000000000FFFFC00000000000000000FFFFFC00000000000000007FFFFFC000000000000000003FFFF80000 000000000000007FFF00000000000000000007FFC00000000000000000007FF80000000000000000000FFE00000000000000 000001FF800000000000000000007FE00000000000000000000FF000000000000000000003FC00000000000000000000FE00 0000000000000000003F800000000000000000001FC000000000000000000007F000000000000000000003F8000000000000 00000000FC000000000000000000007F000000000000000000001F800000000000000000000FC000000000000000000007E0 00000000000000000001F000000000000000000000F8000000000000000000007C000000000000000000003E000000000000 000000001F000000000000000000000F8000000000000000000007C000000000000000000003E000000000000000000001F0 00000000000000000000F000000000000000000000F8000000000000000000007C000000000000000000003E000000000000 000000001E000000000000000000001F000000000000000000000F80000000000000000000078000000000000000000007C0 00000000000000000003E000000000000000000001E000000000000000000001F000000000000000000000F8000000000000 0000000078000000000000000000007C000000000000000000003C000000000000000000003E000000000000000000001E00 0000000000000000001F000000000000000000000F000000000000000000000F000000000000000000000F80000000000000 000000078000000000000000000007C000000000000000000003C000000000000000000003C000000000000000000003E000 000000000000000001E000000000000000000001E000000000000000000001F000000000000000000000F000000000000000 000000F000000000000000000000F000000000000000000000F8000000000000000000007800000000000000000000780000 000000000000000078000000000000000000007C000000000000000000003C000000000000000000003C0000000000000000 00003C000000000000000000003C000000000000000000003C000000000000000000003C000000000000000000003E000000 000000000000001E000000000000000000001E000000000000000000001E000000000000000000001E000000000000000000 001E000000000000000000001E000000000000000000001E000000000000000000001E000000000000000000001E00000000 0000000000000C> 88 87 83 0 166.040] 37 @dc [<007FE00001FFF80007FFFE000FFFFF001FC03F803F000FC03C0003C07C0003E0780001E0F80001F0F00000F0F00000F0F000 00F0F00000F8F00000F8F00000F0F00000F0F00000F0F80001F0780001E07C0003E03C0003C03F000FC01FC03F800FFFFF00 07FFFE0001FFF800007FE00000020000> 32 29 14 14 24.906] 101 @dc [<60000000F0000000F0000000F0000000F0000000F0000000F80000007800000078000000780000007C0000003C0000003E00 00001E0000001F0000000F8000000780000007C0000003E0000001F0000000FC0000007E0000003F8000001FE0000007FE00 0003FFF00000FFF800003FF8000003F0> 32 29 0 25 49.812] 11 @dc [<000003F000003FF80000FFF80003FFF00007FE00001FE000003F8000007E000000FC000001F0000003E0000007C000000780 00000F8000001F0000001E0000003E0000003C0000007C000000780000007800000078000000F8000000F0000000F0000000 F0000000F0000000F000000060000000> 32 29 0 0 49.812] 10 @dc [<000000300000007800000078000000780000007800000078000000F8000000F0000000F0000000F0000001F0000001E00000 03E0000003C0000007C000000F8000000F0000001F0000003E0000007C000001F8000003F000000FE000003FC00003FF0000 7FFE0000FFF80000FFE000007E000000> 32 29 25 25 49.812] 8 @dc [<7E000000FFE00000FFF800007FFE000003FF0000003FC000000FE0000003F0000001F80000007C0000003E0000001F000000 0F0000000F80000007C0000003C0000003E0000001E0000001F0000000F0000000F0000000F0000000F80000007800000078 00000078000000780000007800000030> 32 29 25 0 49.812] 9 @dc linew10.300 @sf [<0000000000380000000001FC000000000FFC000000007FF800000003FFE00000001FFF00000000FFF800000007FFC0000000 3FFE00000001FFF00000000FFF800000007FFC00000003FFE00000001FFF000000007FF800000000FFC000000000FE000000 0000700000000000> 48 18 2 2 41.510] 80 @dc [<400000007FFE3FC07FFFFF803FFFFE003FFFFC003FFFF0001FFFE0001FFF80001FFF00000FFE00000FFC00000FF8000007E0 000007C00000078000000300000002000000> 32 17 -15 1 41.510] 113 @dc [<0000000000780000000007FC000000007FFC00000007FFF80000007FFFC000000FFFFC000000FFFFC000000FFFFC000000FF FFC000000FFFF80000007FFF80000000FFF800000000FF8000000000780000000000> 48 14 2 2 41.510] 88 @dc [<80000000FC000000FFF80000FFFFFF807FFFFE007FFFF8007FFFF0007FFFC0003FFF00003FFE00003FF800003FF000001FE0 00001F8000001F0000001E0000000C00000008000000> 32 18 -16 3 41.510] 122 @dc [<700000000000FC0000000000FF00000000007FC0000000001FF00000000007FC0000000001FF00000000007FC0000000001F F00000000007FC0000000001FF00000000007FC0000000001FF00000000007FC0000000001FF00000000007FC0000000001F F00000000007FC0000000001FF00000000007FC0000000001FF00000000007F80000000001FC00000000007C000000000018> 48 25 2 2 41.510] 8 @dc [<010000000180000003C0000003E0000007F0000007F000000FF800000FFC00001FFE00001FFF00003FFF80003FFFC0007FFF E0007FFFF000FFFFF800FFFFFC00001FFE0000001F0000000080> 32 19 -16 -2 41.510] 42 @dc [<700000000000FE0000000000FFC0000000007FF8000000001FFF0000000003FFE0000000007FFC000000000FFF8000000001 FFF0000000003FFE0000000007FFC000000000FFF8000000001FFF0000000003FFE0000000007FF8000000000FFC00000000 01FC000000000038> 48 18 2 2 41.510] 16 @dc [<0000000002000000030000000780000007C0000007E000000FF800000FFC00000FFE00001FFF00001FFF80001FFFE0003FFF F0003FFFFC003FFFFE007FFFFF807FFE3FC040000000> 32 18 -15 3 41.510] 49 @dc [<780000000000FF8000000000FFF8000000007FFF800000000FFFF800000000FFFFC00000000FFFFC00000000FFFFC0000000 0FFFFC000000007FFFC000000007FFF8000000007FFC0000000007FC000000000078> 48 14 2 2 41.510] 24 @dc [<080000000C0000001E0000001F0000001F8000001FE000003FF000003FF800003FFE00003FFF00007FFFC0007FFFF0007FFF F8007FFFFE00FFFFFF80FFF80000FC00000080000000> 32 18 -16 5 41.510] 58 @dc ammi8.300 @sf [ 24 23 -2 0 20.971] 83 @dc [ 300 ] /ammi6.300 @newfont ammi6.300 @sf [<38006C007C007600700038003800DC00DC007C0038000000000000000000070007000700> 16 18 -2 0 11.194] 105 @dc [ 300 ] /ammi9.300 @newfont ammi9.300 @sf [ 24 26 -1 0 16.791] 73 @dc ammi8.300 @sf [ 32 23 -1 0 28.968] 68 @dc ammi9.300 @sf [<03F810000FFF30001F03F0003C00F8007800780070007800F0007800F0003C00F0003C00F003FF80F003FF80F0000000F000 0000F00000007800000078000000780003003C0003001C0003801E0003800F0007800780078003E00FC000F81CC0003FF8C0 000FE040> 32 26 -2 0 30.067] 71 @dc ammi6.300 @sf [ 24 17 -2 0 25.406] 75 @dc [<7800FC00EE00EE000700070007000700038003800380038019C019C00DC007800000000000000000007000700070> 16 23 -1 5 11.588] 106 @dc [ 16 11 -2 0 17.008] 120 @dc [ 16 11 -2 0 14.855] 122 @dc [<7C00E600E300E38001C00FC01BC039C038E038E038E01CE0DC70DC706C703870> 16 16 -2 5 15.768] 121 @dc [ 32 17 -1 0 28.909] 77 @dc ammi10.329 @sf [<1F87803FCFC078FEE0707E70F03E30F01E30F01F30F00F00F00F00F00F00F80F807807807807803C07803C07C01E07C00F07 C0078FC003FFE000F9E00001E00001E00001F00000F00000F00000F00000F80000780000780000780003FC0003FC> 24 32 -2 0 23.658] 100 @dc [ 24 31 -3 0 19.981] 73 @dc 2 @bop1 -122 -69 p 861 3 ru -122 245 p 3 315 ru 856 r 3 315 ru -122 248 p 861 3 ru 550 111 p 3 30 ru linew10.300 @sf 573 54 p 1 c 553 93 p 1 c -19 r 11 c t-rom.300 @sf 94 130 p 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 17 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 94 -4 p 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 17 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 18 r 46 c 94 130 p 46 c 94 103 p 46 c 94 76 p 46 c 94 49 p 46 c 94 22 p 46 c 94 -4 p 46 c 547 130 p 46 c 547 103 p 46 c 547 76 p 46 c 547 49 p 46 c 547 22 p 46 c 547 -4 p 46 c -67 111 p 3 30 ru 755 r 3 30 ru -287 r 3 30 ru -303 r 3 30 ru -74 173 p 765 3 ru linew10.300 @sf 648 171 p 45 c -65 98 p 165 3 ru 57 96 p 45 c 87 98 p 315 3 ru 360 96 p 45 c 402 98 p 150 3 ru 510 96 p 45 c 552 98 p 135 3 ru 645 96 p 45 c t-rom.270 @sf 120 -22 p (Protocol) s 12 r (Boundary) s ammi10.329 @sf 597 10 p 116 c ammi8.300 @sf 613 16 p 114 c ammi10.329 @sf 240 216 p 1 c 600 67 p 14 c ammi8.300 @sf 619 80 p 100 c ammi10.329 @sf 450 67 p 14 c ammi8.300 @sf 469 78 p 101 c ammi10.329 @sf 225 67 p 14 c ammi8.300 @sf 244 78 p 116 c ammi10.329 @sf -14 67 p 14 c ammi8.300 @sf 4 78 p 99 c t-rom.330 @sf -119 431 p (Figure) s 13 r (1:) s 19 r (Model) s 14 r (for) s 13 r (End-to-End) s 14 r (Delay) s -2 r 46 c ammi10.329 @sf 19 r 14 c ammi8.300 @sf 650 442 p 99 c t-rom.330 @sf 681 431 p 61 c 13 r (collection) s -119 487 p (delay) s -3 r 44 c ammi10.329 @sf 17 r 14 c ammi8.300 @sf 24 498 p 116 c t-rom.330 @sf 56 487 p 61 c 17 r (transit) s 18 r (delay) s -2 r 44 c ammi10.329 @sf 17 r 14 c ammi8.300 @sf 375 498 p 101 c t-rom.330 @sf 409 487 p 61 c 18 r (equalization) s 17 r (delay) s -2 r 44 c ammi10.329 @sf 17 r 14 c ammi8.300 @sf 837 500 p 100 c t-rom.330 @sf 874 487 p 61 c -119 544 p (delivery) s 15 r (delay) s -2 r 44 c ammi10.329 @sf 16 r 116 c ammi8.300 @sf 186 551 p 114 c t-rom.330 @sf 218 544 p 61 c 16 r (release) s 17 r (time,) s ammi10.329 @sf 16 r 1 c t-rom.330 @sf 16 r 61 c 17 r (synchronization) s -119 600 p (delay) s -3 r 46 c -119 737 p (the) s 14 r (dif) s 0 r (ferent) s 15 r (networks.) s -73 791 p (The) s 10 r (protocol) s 12 r (should) s 12 r (be) s 11 r (viewed) s 12 r (as) s 12 r 97 c 12 r (tool) s 11 r (within) s 12 r 97 c 12 r (net-) s -119 845 p (work) s 11 r (layer) s -2 r 46 c 18 r 87 c -3 r 101 c 11 r (have) s 12 r (not) s 11 r (rooted) s 12 r (it) s 11 r (in) s 12 r 97 c 11 r (speci\014c) s 12 r (layer) s 12 r (be-) s -119 899 p (cause) s 15 r (there) s 16 r (is) s 16 r (limited) s 17 r (experience) s 16 r (with) s 16 r (synchronization) s -119 953 p (applications.) s 27 r (One) s 18 r (guideline) s 18 r (is) s 18 r (to) s 18 r (encompass) s 18 r (as) s 18 r (much) s -119 1007 p (end-to-end) s 13 r (delay) s 14 r (as) s 14 r (possible) s 13 r (between) s 14 r (source) s 14 r (and) s 14 r (desti-) s -119 1061 p (nation) s 13 r (peers) s 14 r (in) s 14 r (the) s 13 r (synchronization) s 14 r (protocol.) s 20 r (This) s 14 r (sug-) s -119 1115 p (gests) s 11 r (an) s 12 r (implementation) s 12 r (on) s 12 r (or) s 12 r (above) s 13 r (the) s 12 r (transport) s 12 r (layer) s -119 1169 p (for) s 14 r (the) s 16 r (OSI) s 15 r (model) s 15 r 91 c 0 r 54 c 0 r 93 c 15 r (or) s 16 r (the) s 15 r (internet) s 15 r (layer) s 15 r (in) s 16 r (internets) s -119 1223 p 91 c 0 r 55 c 0 r (].) s 18 r (For) s 10 r (multimedia,) s 12 r 91 c 0 r (13) s 0 r (],) s 11 r (we) s 11 r (are) s 11 r (implementing) s 10 r (it) s 11 r (in) s 11 r (the) s -119 1277 p (Multimedia) s 19 r (Mechanisms) s 20 r (Layer) s -1 r 44 c 20 r (below) s 19 r (the) s 20 r (Orchestra-) s -119 1331 p (tion) s 16 r (Layer) s 17 r (which) s 16 r (controls) s 17 r (the) s 17 r (session.) s 25 r (For) s 17 r (distributed) s -119 1385 p (computation) s 15 r (systems,) s 16 r (it) s 17 r (would) s 16 r (\014t) s 16 r (in) s 16 r (the) s 16 r (homogeneous) s -119 1439 p (layer) s 13 r 91 c 0 r 49 c 0 r (],) s 14 r (which) s 13 r (appears) s 14 r (as) s 13 r (network-independent) s 14 r (to) s 14 r (the) s -119 1493 p (user) s -3 r 46 c -73 1548 p (This) s 18 r (paper) s 20 r (describes) s 19 r (the) s 20 r (\015ow) s 19 r (synchronization) s 20 r (pro-) s -119 1602 p (tocol.) s 27 r (After) s 18 r (this) s 17 r (introduction,) s 19 r (Section) s 17 r 50 c 18 r (describes) s 18 r (the) s -119 1656 p (protocol) s 17 r (model,) s 18 r (Section) s 18 r 51 c 18 r (the) s 18 r (initialization) s 18 r (phase) s 18 r (and) s -119 1710 p (the) s 14 r (protocol) s 14 r (control,) s 15 r (Section) s 15 r 52 c 15 r (the) s 14 r (synchronization) s 15 r (op-) s -119 1764 p (eration,) s 14 r (Section) s 16 r 53 c 15 r (contains) s 15 r 97 c 15 r (discussion,) s 16 r (and) s 15 r (Section) s 15 r 54 c -119 1818 p (summarizes) s 14 r (the) s 15 r (work) s 16 r (and) s 15 r (future) s 15 r (plans.) s t-bol.420 @sf -119 1971 p 50 c 57 r (Model) s t-rom.330 @sf -119 2074 p (Consider) s 16 r (\014rst) s 17 r 97 c 17 r (simple) s 17 r (example) s 17 r (where) s 17 r (it) s 17 r (is) s 17 r (desired) s 17 r (to) s -119 2128 p (synchronize) s 20 r (two) s 20 r (\015ows,) s 22 r (an) s 21 r (audio) s 21 r (stream) s 20 r (and) s 21 r 97 c 21 r (video) s -119 2182 p (stream,) s 14 r (traveling) s 14 r (separately) s 15 r (and) s 14 r (independently) s 15 r (through) s -119 2236 p (an) s 12 r (internetwork.) s 20 r (Assume) s 13 r (that) s 14 r (the) s 13 r (clocks) s 14 r (of) s 13 r (the) s 13 r (sources) s -119 2290 p (and) s 14 r (destinations) s 14 r (\(output) s 15 r (devices\)) s 15 r (of) s 14 r (these) s 15 r (\015ows) s 14 r (are) s 15 r (al-) s -119 2344 p (ready) s 15 r (synchronized) s 15 r (to) s 16 r (within) s 16 r 97 c 15 r (few) s 16 r (milliseconds.) s 22 r (One) s -119 2398 p (approach) s 17 r (to) s 18 r (maintain) s 19 r (synchronization) s 18 r (is) s 18 r (to) s 18 r (timestamp) s -119 2452 p (data) s 17 r (as) s 17 r (it) s 18 r (leaves) s 18 r (the) s 17 r (sources) s 18 r (and,) s 18 r (parallel) s 18 r (to) s 18 r (this,) s 18 r (cal-) s -119 2506 p (culate) s 17 r (the) s 19 r (maximum) s 18 r (delay) s 18 r (it) s 19 r (will) s 18 r (take) s 18 r (for) s 18 r (data) s 19 r (of) s 18 r (ei-) s -119 2560 p (ther) s 19 r (\015ow) s 20 r (to) s 21 r (travel) s 20 r (from) s 20 r (source) s 20 r (to) s 20 r (destination.) s 36 r (Once) s -119 2614 p (this) s 12 r (maximum) s 14 r (delay) s 13 r (is) s 13 r (agreed) s 14 r (upon) s 13 r (by) s 13 r (the) s 14 r (destinations) s lcirclew10.300 @sf 1116 82 p 102 c 1249 166 p (\016\015) s 1249 99 p 15 c 0 r 12 c 1424 44 p (\026\025) s 1424 -54 p 23 c 0 r 20 c 1769 143 p (\016\015) s 1769 76 p 15 c 0 r 12 c 1818 257 p (\016\015) s 1818 191 p 15 c 0 r 12 c 2039 299 p 102 c 1991 -4 p 102 c 1619 10 p 39 c 1619 190 p 3 99 ru 1619 275 p 38 c 2012 10 p 36 c 2012 190 p 3 99 ru 2012 275 p 37 c -473 r 227 3 ru 1704 10 p 227 3 ru 2080 457 p 102 c 1960 612 p 101 c 1673 568 p (\016\015) s 1673 502 p 15 c 0 r 12 c 1836 431 p (\016\015) s 1836 364 p 15 c 0 r 12 c 1583 321 p 39 c 1583 506 p 3 104 ru 1583 591 p 38 c 1996 321 p 36 c 1996 506 p 3 104 ru 1996 591 p 37 c -493 r 247 3 ru 1668 321 p 247 3 ru 1265 423 p (\016\015) s 1265 357 p 15 c 0 r 12 c 1137 413 p 102 c 1079 550 p 11 c 1079 585 p 3 11 ru 1079 612 p 10 c 1211 550 p 8 c 1211 585 p 3 11 ru 1211 612 p 9 c -154 r 83 3 ru 1105 550 p 83 3 ru linew10.300 @sf 1134 101 p 80 c 1176 115 p 80 c 1207 125 p 80 c -40 r 113 c 1325 124 p 426 3 ru 1710 123 p 45 c 1047 -74 p 1116 3 ru 1047 651 p 3 727 ru 1112 r 3 727 ru 1047 655 p 1116 3 ru 1884 263 p 88 c 1925 273 p 88 c 1967 284 p 88 c 1985 288 p 88 c -41 r 122 c 1838 72 p 8 c 1879 51 p 8 c 1921 30 p 8 c 1929 26 p 8 c -41 r 42 c 1907 421 p 88 c 1948 432 p 88 c 1990 442 p 88 c 2018 449 p 88 c -40 r 122 c 1736 569 p 88 c 1777 579 p 88 c 1819 590 p 88 c 1860 600 p 88 c 1898 610 p 88 c -40 r 122 c 1341 378 p 16 c 1382 364 p 16 c 1424 350 p 16 c 1465 336 p 16 c 1507 322 p 16 c 1548 308 p 16 c 1590 295 p 16 c 1631 281 p 16 c 1673 267 p 16 c 1714 253 p 16 c 1756 239 p 16 c 1758 238 p 16 c -40 r 49 c 1343 389 p 484 3 ru 1786 388 p 45 c 1333 426 p 88 c 1374 437 p 88 c 1416 447 p 88 c 1458 457 p 88 c 1499 468 p 88 c 1541 478 p 88 c 1582 489 p 88 c 1621 498 p 88 c -41 r 122 c 1157 416 p 24 c 1199 405 p 24 c 1218 401 p 24 c -41 r 58 c t-rom.270 @sf 1241 627 p (group) s 1241 577 p (synchronization) s 1098 133 p (data) s 1098 179 p (in) s ammi8.300 @sf 1262 138 p 83 c ammi6.300 @sf 1286 126 p 105 c ammi9.300 @sf 1460 13 p 73 c ammi8.300 @sf 1782 118 p 68 c ammi6.300 @sf 1812 106 p 105 c ammi9.300 @sf 1919 174 p 71 c ammi6.300 @sf 1949 158 p 75 c t-rom.270 @sf 2039 355 p (data) s 2037 385 p (out) s 2024 3 p (data) s 2024 49 p (out) s ammi8.300 @sf 1825 235 p 68 c ammi6.300 @sf 1855 223 p 106 c 3 r 120 c ammi8.300 @sf 1677 543 p 68 c ammi6.300 @sf 1707 532 p 106 c 3 r 122 c ammi8.300 @sf 1840 403 p 68 c ammi6.300 @sf 1870 391 p 106 c 3 r 121 c t-rom.270 @sf 2062 543 p (out) s 2062 508 p (data) s 2006 592 p (data) s 2009 633 p (out) s ammi9.300 @sf 1879 508 p 71 c ammi6.300 @sf 1909 492 p 77 c ammi8.300 @sf 1277 401 p 83 c ammi6.300 @sf 1301 389 p 106 c t-rom.270 @sf 1098 385 p (in) s 1098 342 p (data) s t-rom.330 @sf 1171 833 p (Figure) s 15 r (2:) s 21 r (Model) s 15 r (for) s 15 r (Protocol) s 15 r (Operation.) s 1050 978 p (they) s 18 r (delay) s 18 r (the) s 18 r (data) s 18 r (they) s 18 r (receive) s 18 r (until) s 18 r 97 c 18 r (time) s 18 r (equal) s 18 r (to) s 1050 1032 p (the) s 14 r (timestamp) s 14 r (of) s 14 r (the) s 14 r (data) s 14 r (plus) s 14 r (this) s 14 r (maximum) s 13 r (delay) s -2 r 46 c 19 r (In) s 1050 1086 p (this) s 15 r (manner) s -1 r 44 c 15 r (the) s 15 r (network) s 15 r (will) s 16 r (appear) s 15 r (to) s 15 r (have) s 16 r (the) s 15 r (same) s 1050 1140 p (delay) s 19 r (to) s 19 r (both) s 19 r (\015ows) s 19 r (and) s 19 r (they) s 18 r (will) s 19 r (be) s 19 r (synchronized) s 19 r (at) s 1050 1194 p (their) s 15 r (destinations.) s 1096 1253 p (While) s 21 r (this) s 22 r (idea) s 21 r (is) s 22 r (simple,) s 23 r (we) s 22 r (still) s 21 r (need) s 22 r (to) s 21 r (face) s 22 r 97 c 1050 1307 p (number) s 23 r (of) s 24 r (complications.) s 45 r 87 c -3 r 101 c 22 r (must) s 24 r (make) s 23 r (this) s 24 r (idea) s 1050 1361 p (work) s 11 r (over) s 11 r 97 c 10 r (wide) s 11 r (range) s 11 r (of) s 11 r (communication) s 11 r (patterns) s 11 r (\(one) s 1050 1415 p (sender) s 18 r (to) s 18 r (multiple) s 18 r (receivers,) s 18 r (multiple) s 18 r (senders) s 18 r (to) s 18 r (mul-) s 1050 1469 p (tiple) s 18 r (receivers,) s 19 r (multiple) s 18 r (senders) s 18 r (to) s 18 r (one) s 19 r (receiver\).) s 29 r 87 c -3 r 101 c 1050 1523 p (must) s 19 r (allow) s 19 r (for) s 19 r (long) s 19 r (term) s 19 r (\015uctuations) s 19 r (of) s 19 r (network) s 19 r (de-) s 1050 1577 p (lay) s 13 r (and) s 14 r (face) s 13 r (situations) s 14 r (where) s 13 r (the) s 14 r (delay) s 13 r (of) s 14 r (some) s 13 r (\015ow) s 14 r (is) s 1050 1631 p (uncomfortably) s 17 r (high) s 16 r (for) s 17 r (other) s 16 r (\015ows) s 17 r (that) s 16 r (cannot) s 17 r (be) s 16 r (de-) s 1050 1685 p (layed) s 17 r (by) s 17 r (much) s 17 r (at) s 17 r (their) s 17 r (destinations.) s 26 r 87 c -3 r 101 c 16 r (must) s 17 r (explain) s 1050 1739 p (then) s 19 r (how) s 20 r (the) s 19 r (protocol) s 20 r (address) s 19 r (these) s 19 r (and) s 20 r (other) s 19 r (issues) s 1050 1793 p (that) s 14 r (arise) s 14 r (in) s 14 r (the) s 14 r (context) s 14 r (of) s 14 r (providing) s 14 r 97 c 14 r (synchronization) s 1050 1847 p (service.) s 1096 1906 p (The) s 12 r (protocol) s 12 r (implements) s 12 r (end-to-end) s 12 r (synchronization) s 1050 1960 p (based) s 14 r (on) s 13 r (the) s 14 r (model) s 14 r (of) s 13 r (data) s 14 r (delay) s 14 r (in) s 13 r (Figure) s 14 r (1.) s 20 r (It) s 13 r (shows) s 1050 2014 p (four) s 12 r (components:) s 18 r 97 c t-ita.330 @sf 12 r (collection) s 11 r (delay) s t-rom.330 @sf 0 r 44 c ammi10.329 @sf 13 r 14 c ammi8.300 @sf 1755 2026 p 99 c t-rom.330 @sf 1772 2014 p 44 c 12 r (from) s 12 r (the) s 11 r (appli-) s 1050 2068 p (cation) s 11 r (to) s 10 r (the) s 11 r (synchronization) s 10 r (protocol) s 11 r (\(for) s 10 r (example) s 11 r (data) s 1050 2122 p (encoding) s 14 r (delay\);) s 15 r 97 c t-ita.330 @sf 14 r (transit) s 14 r (delay) s t-rom.330 @sf 0 r 44 c ammi10.329 @sf 15 r 14 c ammi8.300 @sf 1685 2134 p 116 c t-rom.330 @sf 1700 2122 p 44 c 14 r (to) s 14 r (reach) s 15 r (the) s 14 r (proto-) s 1050 2176 p (col) s 16 r (peer) s 15 r (across) s 16 r (the) s 16 r (network;) s 16 r (an) s t-ita.330 @sf 16 r (equalization) s 16 r (delay) s t-rom.330 @sf 0 r 44 c ammi10.329 @sf 15 r 14 c ammi8.300 @sf 2041 2188 p 101 c t-rom.330 @sf 2059 2176 p 44 c 1050 2230 p (inserted) s 12 r (by) s 13 r (the) s 12 r (protocol) s 13 r (to) s 12 r (equalize) s 12 r (the) s 13 r (end-to-end) s 12 r (\015ow) s 1050 2284 p (delay;) s 19 r (and) s 18 r 97 c t-ita.330 @sf 18 r (delivery) s 18 r (delay) s t-rom.330 @sf 0 r 44 c ammi10.329 @sf 19 r 14 c ammi8.300 @sf 1616 2297 p 100 c t-rom.330 @sf 1636 2284 p 44 c 19 r (from) s 18 r (the) s 18 r (moment) s 18 r (the) s 1050 2338 p (protocol) s 16 r (releases) s 15 r (the) s 16 r (data) s 16 r 40 c t-ita.330 @sf 0 r 114 c -1 r (elease) s 15 r (time) s t-rom.330 @sf 0 r 44 c ammi10.329 @sf 16 r 116 c ammi8.300 @sf 1825 2345 p 114 c t-rom.330 @sf 1843 2338 p 41 c 15 r (to) s 16 r (the) s 16 r (mo-) s 1050 2392 p (ment) s 16 r (this) s 16 r (data) s 16 r (is) s 16 r (presented) s 16 r (to) s 16 r (the) s 15 r (application.) s 23 r 87 c -3 r 101 c 15 r (call) s t-ita.330 @sf 1050 2446 p (synchr) s -1 r (onization) s 10 r (delay) s t-rom.330 @sf 12 r (the) s 11 r (total) s 11 r (equalized) s 11 r (\015ow) s 11 r (delay) s -2 r 44 c ammi10.329 @sf 11 r 1 c t-rom.330 @sf 3 r 44 c 1050 2500 p (and) s t-ita.330 @sf 15 r (\015ow) s 15 r (delay) s t-rom.330 @sf 16 r (the) s 15 r (unequalized) s 15 r (delay) s ammi10.329 @sf 15 r 100 c t-rom.330 @sf 15 r 61 c ammi10.329 @sf 13 r 14 c ammi8.300 @sf 1853 2512 p 99 c t-rom.330 @sf 1881 2500 p 43 c ammi10.329 @sf 10 r 14 c ammi8.300 @sf 1936 2512 p 116 c t-rom.330 @sf 1961 2500 p 43 c ammi10.329 @sf 10 r 14 c ammi8.300 @sf 2015 2513 p 100 c t-rom.330 @sf 2036 2500 p 46 c 1096 2560 p (Figure) s 18 r 50 c 19 r (illustrates) s 19 r (the) s 19 r (protocol) s 19 r (operation.) s 30 r (An) s t-ita.330 @sf 19 r (ini-) s 1050 2614 p (tiator) s 11 r (pr) s -1 r (ocessor) s ammi10.329 @sf 11 r 73 c t-rom.330 @sf 14 r (distributes) s 12 r (control) s 11 r (information) s 11 r (across) s 964 2738 p (1382) s @eop 3 @bop0 lcirclew10.300 @sf [<000000000FF800000000FFFC00000007FFFC0000003FFFF8000000FFF800000003FF800000000FFC000000001FE000000000 7F8000000000FE0000000001F80000000003F00000000007C0000000000F80000000001F00000000003E00000000007C0000 000000F80000000000F00000000001F00000000003E00000000003C00000000007C0000000000780000000000F8000000000 0F00000000001F00000000001E00000000001E00000000003E00000000003C00000000003C00000000007C00000000007800 00000000780000000000780000000000F80000000000F00000000000F00000000000F00000000000F00000000000F0000000 0000F00000000000F00000000000700000000000200000000000> 48 46 0 0 83.020] 18 @dc [<7F8000000000FFF800000000FFFF000000007FFFE000000000FFF8000000000FFE0000000001FF80000000003FC000000000 0FF00000000003F80000000000FC00000000007E00000000001F00000000000F800000000007C00000000003E00000000001 F00000000000F800000000007800000000007C00000000003E00000000001E00000000001F00000000000F00000000000F80 0000000007800000000007C00000000003C00000000003C00000000003E00000000001E00000000001E00000000001F00000 000000F00000000000F00000000000F00000000000F800000000007800000000007800000000007800000000007800000000 0078000000000078000000000078000000000038000000000010> 48 46 41 0 83.020] 17 @dc [<700000000000F00000000000F00000000000F00000000000F00000000000F00000000000F00000000000F00000000000F800 000000007800000000007800000000007800000000007C00000000003C00000000003C00000000003E00000000001E000000 00001E00000000001F00000000000F00000000000F800000000007800000000007C00000000003C00000000003E000000000 01F00000000000F00000000000F800000000007C00000000003E00000000001F00000000000F800000000007C00000000003 F00000000001F80000000000FE00000000007F80000000001FE0000000000FFC0000000003FF8000000000FFF8000000003F FFF800000007FFFC00000000FFFC000000000FF8> 48 45 0 41 83.020] 19 @dc [<0000000000380000000000780000000000780000000000780000000000780000000000780000000000780000000000780000 000000F80000000000F00000000000F00000000000F00000000001F00000000001E00000000001E00000000003E000000000 03C00000000003C00000000007C0000000000780000000000F80000000000F00000000001F00000000001E00000000003E00 000000007C0000000000780000000000F80000000001F00000000003E00000000007C0000000000F80000000001F00000000 007E0000000000FC0000000003F8000000000FF0000000003FC000000001FF800000000FFE00000000FFF80000007FFFE000 0000FFFF00000000FFF8000000007F8000000000> 48 45 41 41 83.020] 16 @dc linew10.300 @sf [<000000800000038000001F8000007F800001FF80000FFF80007FFF8003FFFF803FFFFF803FFFFF8003FFFF80007FFF80000F FF800001FF8000007F8000001F800000038000000080> 32 18 0 9 41.510] 27 @dc [<00000000000008000000180000003C0000007C000000FC000003FE000007FE00000FFE00001FFF00003FFF0000FFFF0001FF FF8007FFFF800FFFFF803FFFFFC07F8FFFC000000040> 32 18 0 3 41.510] 105 @dc [<0000004000000FC00007FFC07FFFFFC01FFFFF8007FFFF8003FFFF8000FFFF80003FFF00001FFF000007FF000003FF000001 FE0000007E0000003E0000001E0000000C0000000400> 32 18 0 3 41.510] 57 @dc [ 24 23 9 -17 41.510] 54 @dc [<00000000000000C00000C00000C00000C00001E00001E00001E00003F00003F00003F00007F80007F80007F8000FFC000FFC 001FFE001FFE003FFF003FFF003FFF007FFF807FFF80FFFFC0> 24 25 9 0 41.510] 63 @dc ammi10.329 @sf [ 40 31 -3 0 37.632] 68 @dc ammi8.300 @sf [<1C003F003F003B8039803D801C001C001E00CE00EF00670077003E001E000000000000000000018003C003C00180> 16 23 0 0 12.290] 105 @dc ammi10.329 @sf [ 32 31 -2 0 27.240] 83 @dc [<1E003F003B8079C07CC03CC03CC03E001E001E001F000F00CF00CF80E780678077803B801F800E0000000000000000000000 00000000007000F800F800F80070> 16 32 -1 0 16.056] 105 @dc [<3F00007FC000FBE000F8F000F8F000707800007800007C00003C00003C00003C00003E00001E00001E00001E00001F00000F 00000F00000F00000F800007800307800387800187C001C3C000E3C0007380003F80001E0000000000000000000000000000 00000000000000000000700000F80000F80000F8000070> 24 41 1 9 16.572] 106 @dc [<7C3F00FE7F80FFF1C0FBE0E0F9E07071E03001F03000F00000F00000F00000F800007800607800607800707C70303CF8387E F81E7FF80FF3F803E1F0> 24 20 -2 0 25.094] 120 @dc [ 8 14 -4 9 12.626] 59 @dc [<1F80003FE00079F0007C78007C3C007C3C00381E00001F00000F0003EF0007FF000F3F801E1F801E0F801E07801E07C01E03 C01E03C01E03C01F03E00F01E0CF81E0C781E0E781F06780F07380F03B80F01F00F00E0060> 24 29 -2 9 22.285] 121 @dc [ 24 20 -2 0 21.138] 122 @dc ammi8.300 @sf [<7800FE00FF00F700678003800380038003C001C001C001C001E000E000E018E01CF00C700E7007E003C00000000000000000 0018003C003C0018> 16 29 0 6 12.712] 106 @dc ammi10.329 @sf [<007F830003FFF30007E0FF800F001F801E000F803E0007807C0007C07C0003C0780003C0780003C0F80003E0F8003FFCF800 3FFCF8000000FC0000007C0000007C0000007E0000003E0000003E0000181F0000181F0000180F80001C07C0001C03E0003C 01F0003C00F8007E007E00FE001FC1CE0007FF860000FF06> 32 31 -1 0 35.738] 71 @dc ammi8.300 @sf [ 32 23 -1 0 29.720] 75 @dc [ 40 23 0 0 33.972] 77 @dc /Times-Roman /t-rom.240 ReEncodeForTeX /t-rom.240 /t-rom.240 33.208800 TeXPSmakefont def ammi10.329 @sf [<1800003C00003E00001E00001E00001E00001F00000F00000F00000F0000070000070000030000C30000C38000E180007180 003FFF803FFF800FFF80> 24 20 -2 0 17.345] 28 @dc ammi8.300 @sf [<078F001FFF801CFD80383DC0381CC0381CC03C1E001C0E001C0E00DE0E00EE0F006E07007E07003E07001C0700> 24 15 -1 0 20.428] 117 @dc [<0FF007F001C001C001E000E01FE03FE071F060F06070E0707078703870387038383C183C0E3C07FC03EC> 16 21 0 6 15.781] 113 @dc [ 16 15 -2 0 19.256] 120 @dc lcirclew10.300 @sf [<000000000000000FFC00000000000003FFFE0000000000003FFFFE000000000001FFFFFC00000000000FFFF8000000000000 3FFE00000000000001FFE000000000000007FF000000000000000FF8000000000000003FE000000000000000FF0000000000 000001FC0000000000000007F8000000000000000FE0000000000000001F80000000000000007F0000000000000000FC0000 000000000001F80000000000000003F00000000000000007C0000000000000000F80000000000000001F0000000000000000 3E00000000000000007C0000000000000000F80000000000000001F00000000000000001E00000000000000003E000000000 00000007C0000000000000000F80000000000000000F00000000000000001F00000000000000003E00000000000000003C00 000000000000007C0000000000000000780000000000000000F80000000000000001F00000000000000001E0000000000000 0003E00000000000000003C00000000000000003C00000000000000007C0000000000000000780000000000000000F800000 00000000000F00000000000000000F00000000000000001F00000000000000001E00000000000000001E0000000000000000 3E00000000000000003C00000000000000003C00000000000000003C00000000000000007C00000000000000007800000000 00000000780000000000000000780000000000000000780000000000000000780000000000000000F80000000000000000F0 0000000000000000F00000000000000000F00000000000000000F00000000000000000F00000000000000000F00000000000 000000F00000000000000000F00000000000000000700000000000000000200000000000000000> 72 71 0 0 132.832] 30 @dc [<7FC000000000000000FFFF00000000000000FFFFF00000000000007FFFFE000000000000007FFFC000000000000001FFF000 0000000000001FFE0000000000000003FF80000000000000007FC0000000000000001FF00000000000000003FC0000000000 000000FE00000000000000007F80000000000000001FC00000000000000007E00000000000000003F80000000000000000FC 00000000000000007E00000000000000003F00000000000000000F800000000000000007C00000000000000003E000000000 00000001F00000000000000000F800000000000000007C00000000000000003E00000000000000001E00000000000000001F 00000000000000000F800000000000000007C00000000000000003C00000000000000003E00000000000000001F000000000 00000000F00000000000000000F800000000000000007800000000000000007C00000000000000003E00000000000000001E 00000000000000001F00000000000000000F00000000000000000F00000000000000000F8000000000000000078000000000 00000007C00000000000000003C00000000000000003C00000000000000003E00000000000000001E00000000000000001E0 0000000000000001F00000000000000000F00000000000000000F00000000000000000F00000000000000000F80000000000 0000007800000000000000007800000000000000007800000000000000007800000000000000007800000000000000007C00 000000000000003C00000000000000003C00000000000000003C00000000000000003C00000000000000003C000000000000 00003C00000000000000003C00000000000000003C00000000000000001C000000000000000008> 72 71 66 0 132.832] 29 @dc [<700000000000000000F00000000000000000F00000000000000000F00000000000000000F00000000000000000F000000000 00000000F00000000000000000F00000000000000000F00000000000000000F8000000000000000078000000000000000078 00000000000000007800000000000000007800000000000000007800000000000000007C00000000000000003C0000000000 0000003C00000000000000003C00000000000000003E00000000000000001E00000000000000001E00000000000000001F00 000000000000000F00000000000000000F00000000000000000F800000000000000007800000000000000007C00000000000 000003C00000000000000003C00000000000000003E00000000000000001E00000000000000001F00000000000000000F800 000000000000007800000000000000007C00000000000000003C00000000000000003E00000000000000001F000000000000 00000F00000000000000000F800000000000000007C00000000000000003E00000000000000001E00000000000000001F000 00000000000000F800000000000000007C00000000000000003E00000000000000001F00000000000000000F800000000000 000007C00000000000000003F00000000000000001F80000000000000000FC00000000000000007F00000000000000001F80 000000000000000FE00000000000000007F80000000000000001FC0000000000000000FF00000000000000003FE000000000 0000000FF80000000000000007FF0000000000000001FFE0000000000000003FFE000000000000000FFFF800000000000001 FFFFFC0000000000003FFFFE00000000000003FFFE000000000000000FFC> 72 70 0 66 132.832] 31 @dc [<00000000000000001C00000000000000003C00000000000000003C00000000000000003C00000000000000003C0000000000 0000003C00000000000000003C00000000000000003C00000000000000003C00000000000000007C00000000000000007800 00000000000000780000000000000000780000000000000000780000000000000000780000000000000000F8000000000000 0000F00000000000000000F00000000000000000F00000000000000001F00000000000000001E00000000000000001E00000 000000000003E00000000000000003C00000000000000003C00000000000000007C000000000000000078000000000000000 0F80000000000000000F00000000000000000F00000000000000001F00000000000000001E00000000000000003E00000000 000000007C0000000000000000780000000000000000F80000000000000000F00000000000000001F00000000000000003E0 0000000000000003C00000000000000007C0000000000000000F80000000000000001F00000000000000001E000000000000 00003E00000000000000007C0000000000000000F80000000000000001F00000000000000003E00000000000000007C00000 00000000000F80000000000000003F00000000000000007E0000000000000000FC0000000000000003F80000000000000007 E0000000000000001FC0000000000000007F8000000000000000FE0000000000000003FC000000000000001FF00000000000 00007FC000000000000003FF800000000000001FFE00000000000001FFF00000000000007FFFC000000000007FFFFE000000 000000FFFFF0000000000000FFFF000000000000007FC000000000000000> 72 70 66 66 132.832] 28 @dc linew10.300 @sf [<0008000000180000003C0000007C000000FC000001FE000003FE000007FF00000FFF00001FFF00003FFF80007FFF8000FFFF C0003FFFC00007FFE00001FFE000003FF000000FF0000003F8000000F80000003C0000000C000000020000000100> 32 24 -18 -18 41.510] 18 @dc [<600000000000F00000000000F800000000007C00000000003E00000000001F00000000000F800000000007C00000000003E0 0000000001F00000000000F800000000007C00000000003E00000000001F00000000000F800000000007C00000000003E000 00000001F00000000000F800000000007C00000000003E00000000001F00000000000F800000000007C00000000003E00000 000001F00000000000F800000000007C00000000003E00000000001F00000000000F800000000007C00000000003E0000000 0001F00000000000F800000000007C00000000003E00000000001F00000000000F800000000007C00000000003E000000000 01F00000000000F800000000007C00000000003C000000000018> 48 46 2 2 41.510] 0 @dc [<8000000040000000300000003C0000001F0000001FC000000FF000000FFC000007FF800007FFE00003FFFC0003FFFF0001FF FE0001FFFC0000FFF80000FFF00000FFE000007FC000007F8000003F0000003E0000003C00000018000000100000> 32 24 0 0 41.510] 9 @dc [<000000000200000200000600000600000E00001E00001E00003E00003E00007E0000FE0000FE0001FF0003FF0007FF0007FF 000FFF001FFF003FFF007FFF80FFFF803FFF8003FF80003F800003C0> 24 26 5 0 10.378] 87 @dc [<0018003C003C003C007C00780078007800F800F000F000F001F001E001E001E003E003C003C003C007C00780078007800780 0F800F000F000F001F001E001E001E003E003C003C003C007C00780078007800F800F000F000F0006000> 16 46 2 2 10.378] 67 @dc [ 24 25 3 -16 10.378] 79 @dc [<80000000700000003C0000001F8000000FF000000FFE000007FFF00003FFFF8001FFFF8001FFFF0000FFFE0000FFFE00007F FC00003FF800003FF000001FF000001FE000000FC00000078000000780000003000000020000> 32 22 0 0 41.510] 61 @dc [<0000008000001F00001FFE00FFFFFC00FFFFF8007FFFF0007FFFE0003FFFC0003FFF80001FFF00001FFE00000FFC00000FF8 000007F0000007F0000003E0000003C000000180000001000000> 32 19 -16 0 41.510] 106 @dc [<000000400000038000001F000001FE00001FFC0003FFF800FFFFF0007FFFF0003FFFE0003FFFC0001FFF80000FFF80000FFF 000007FE000003FC000003FC000001F8000000F8000000F000000060000000200000> 32 21 -16 0 41.510] 115 @dc [<000001000000020000000C0000003C000000F8000003F800000FF000003FF00001FFE00007FFE0003FFFC000FFFFC0007FFF 80003FFF80001FFF00000FFF000007FF000003FE000001FE000000FC0000007C0000003C00000018000000080000> 32 24 -18 0 41.510] 82 @dc [<0000000000200000400000C00001C00003C00007C0000F80001F80003F80007F8000FF8001FF8003FF800FFF801FFF003FFF 007FFF00FFFF003FFF000FFF0003FF0000FF00003F00000F00000300> 24 26 -2 0 20.755] 85 @dc [<0000004000006000006000007000007800007800007C00007E00003E00003F00003F80007FC0007FE0007FF0007FF0007FF8 007FFC007FFE007FFF007FFF807FFE007FF0007F80007C0000E00000> 24 26 1 0 13.837] 13 @dc ammi8.300 @sf [ 16 15 -1 0 16.412] 122 @dc [<3E007F8071C078E078E030700FF01FF03CF83878383838383C3C1C1C1C1CDE1CEE1E6E0E7E0E3E0E1C0E> 16 21 -1 6 17.440] 121 @dc 3 @bop1 lcirclew10.300 @sf -100 51 p 15 c -100 87 p 3 6 ru -100 122 p 14 c 85 51 p 12 c 85 87 p 3 6 ru 85 122 p 13 c -216 r 119 3 ru -65 51 p 119 3 ru 253 -41 p 15 c 253 -5 p 3 6 ru 253 30 p 14 c 445 -41 p 12 c 445 -5 p 3 6 ru 445 30 p 13 c -222 r 125 3 ru 288 -41 p 125 3 ru 296 241 p (\026\025) s 296 142 p 23 c 0 r 20 c 667 260 p (\022\021) s 667 177 p 19 c 0 r 16 c -37 287 p (\022\021) s -37 204 p 19 c 0 r 16 c 613 24 p 15 c 613 60 p 3 6 ru 613 95 p 14 c 804 24 p 12 c 804 60 p 3 6 ru 804 95 p 13 c -222 r 125 3 ru 648 24 p 125 3 ru 102 80 p 45 3 ru 90 r 45 3 ru 90 r 45 3 ru 90 r 45 3 ru 90 r 45 3 ru 90 r 45 3 ru linew10.300 @sf 555 78 p 45 c -494 r 27 c 459 11 p 80 c 462 13 p 80 c 549 41 p 80 c 552 43 p 80 c 552 43 p 113 c 459 11 p 105 c 63 49 p 24 c 63 48 p 24 c 132 31 p 24 c 132 31 p 24 c 201 14 p 24 c 201 14 p 24 c 201 14 p 58 c 63 49 p 57 c -122 -72 p 966 3 ru -122 302 p 3 375 ru 961 r 3 375 ru -122 305 p 966 3 ru 345 75 p 54 c 343 123 p 3 90 ru 2 r 63 c 723 141 p 54 c 721 165 p 3 66 ru 2 r 63 c -5 168 p 54 c -7 192 p 3 66 ru 1 r 63 c t-rom.270 @sf -80 93 p (client) s 285 -1 p (client) s ammi10.329 @sf 306 213 p 73 c 687 246 p 68 c ammi8.300 @sf 725 230 p 105 c ammi10.329 @sf -20 270 p 83 c ammi8.300 @sf 11 254 p 105 c t-rom.270 @sf 642 67 p (client) s t-rom.330 @sf 19 488 p (Figure) s 15 r (3:) s 21 r (Model) s 15 r (of) s 15 r (Distributed) s 15 r (Client.) s -119 641 p (the) s 13 r (protocol.) s 20 r 65 c 14 r (\015ow) s ammi10.329 @sf 14 r 105 c t-rom.330 @sf 14 r (has) s 14 r 97 c t-ita.330 @sf 14 r (sour) s -1 r (ce) s 13 r (pr) s -1 r (ocessor) s ammi10.329 @sf 13 r 83 c ammi8.300 @sf 773 625 p 105 c t-rom.330 @sf 801 641 p (send-) s -119 695 p (ing) s 13 r (data) s 13 r (to) s 14 r 97 c t-ita.330 @sf 13 r (destination) s 14 r (pr) s -1 r (ocessor) s ammi10.329 @sf 12 r 68 c ammi8.300 @sf 572 679 p 105 c t-rom.330 @sf 586 695 p 46 c ammi10.329 @sf 20 r 83 c ammi8.300 @sf 649 679 p 105 c t-rom.330 @sf 677 695 p (time-stamps) s -119 749 p (data) s 20 r (in) s 22 r (the) s 21 r (\015ow) s 21 r (and) s ammi10.329 @sf 21 r 68 c ammi8.300 @sf 340 733 p 105 c t-rom.330 @sf 375 749 p (implements) s 22 r (equalization) s 21 r (by) s -119 803 p (buf) s -1 r (fering) s 15 r (data.) s 21 r 65 c 15 r (\015ow) s 16 r (may) s 15 r (represent) s 16 r (datagrams) s 15 r (or) s 16 r (bit) s -119 857 p (streams.) s 28 r 65 c 18 r (multicast) s 18 r (\015ow) s ammi10.329 @sf 18 r 106 c t-rom.330 @sf 23 r (consists) s 18 r (of) s 18 r (several) s 18 r (\015ows) s -119 911 p 40 c ammi10.329 @sf 0 r 106 c 4 r (x;) s 8 r 106 c 5 r 121 c 2 r 59 c 7 r 106 c 5 r 122 c t-rom.330 @sf 14 r (in) s 12 r (the) s 12 r (\014gure\)) s 13 r (sharing) s 12 r 97 c 12 r (single) s 12 r (source) s 12 r (proces-) s -119 965 p (sor) s ammi10.329 @sf 16 r 83 c ammi8.300 @sf -14 949 p 106 c t-rom.330 @sf 3 965 p 46 c 26 r (Flows) s 18 r (whose) s 17 r (destinations) s 17 r (belong) s 17 r (to) s 17 r (the) s 18 r (same) s t-ita.330 @sf -119 1019 p (synchr) s -2 r (onization) s 13 r (gr) s -1 r (oup) s t-rom.330 @sf 13 r 40 c ammi10.329 @sf 0 r 71 c ammi8.300 @sf 356 1003 p 75 c ammi10.329 @sf 390 1019 p 59 c 8 r 71 c ammi8.300 @sf 446 1003 p 77 c t-rom.330 @sf 486 1019 p 41 c 14 r (will) s 13 r (be) s 14 r (synchronized) s -119 1073 p (to) s 14 r (each) s 15 r (other) s 16 r (by) s 15 r (the) s 15 r (protocol.) s -73 1137 p (For) s 14 r (simplicity) s -2 r 44 c 14 r (we) s 15 r (call) s 15 r (the) s t-ita.330 @sf 15 r (client) s t-rom.330 @sf 16 r (that) s 15 r (distributed) s 15 r (ap-) s -119 1191 p (plication) s 11 r (that) s 12 r (has) s 12 r (local) s 12 r (access) s 11 r (to) s 12 r (all) s 12 r (processors) s 12 r (and) s 12 r (uses) s -119 1245 p (the) s 13 r (protocol) s 15 r (\(Figure) s 14 r (3\).) s 20 r 87 c -3 r 101 c 14 r (call) s t-ita.330 @sf 14 r (session) s t-rom.330 @sf 14 r (the) s 15 r (joint) s 14 r (oper-) s -119 1299 p (ation) s 17 r (of) s 18 r (all) s 18 r (processors,) s 19 r (we) s 18 r (call) s t-ita.330 @sf 18 r (session) s 18 r (pr) s 0 r (ocessor) s t-rom.330 @sf 17 r (any) s -119 1353 p (of) s 15 r (the) s 16 r (protocol) s 17 r (processors,) s 16 r (and) s 16 r (we) s 17 r (call) s t-ita.330 @sf 16 r (\015ow) s 16 r (pr) s -1 r (ocessor) s t-rom.330 @sf -119 1407 p (any) s 14 r (source) s 15 r (or) s 16 r (destination) s 15 r (processor) s -2 r 46 c -73 1470 p (Figure) s 15 r 52 c 17 r (illustrates) s 17 r (the) s 17 r (protocol) s 17 r (control.) s 25 r (The) s 17 r (initia-) s -119 1524 p (tor) s ammi10.329 @sf 14 r 73 c t-rom.330 @sf 20 r (sends) s t-ita.330 @sf 15 r (contr) s -1 r (ol) s 15 r (messages) s t-rom.330 @sf 15 r (to) s 16 r (all) s 15 r (\015ow) s 16 r (processors,) s 15 r (to) s -119 1578 p (initialize) s 13 r (or) s 13 r (change) s 14 r (session) s 14 r (parameters.) s 19 r (Source) s 14 r (proces-) s -119 1632 p (sors) s 19 r (send) s t-ita.330 @sf 20 r (event) s 20 r (messages) s t-rom.330 @sf 20 r (to) s 20 r (their) s 20 r (destination) s 20 r (proces-) s -119 1686 p (sors,) s 16 r (as) s 16 r 97 c 17 r (vehicle) s 16 r (to) s 17 r (communicate) s 16 r (parameters) s 17 r (describ-) s -119 1740 p (ing) s 15 r (the) s 16 r (\015ow) s -2 r 44 c 15 r (if) s 16 r (necessary) s -2 r 46 c 22 r (The) s 16 r (client) s 16 r (partitions) s 16 r (the) s 16 r (set) s -119 1794 p (of) s 20 r (destination) s 20 r (processors) s 21 r (into) s t-ita.330 @sf 20 r (synchr) s -1 r (onization) s 20 r (gr) s -1 r (oups) s ammi10.329 @sf -119 1848 p 71 c ammi8.300 @sf -83 1832 p 75 c ammi10.329 @sf -49 1848 p 59 c 6 r 71 c ammi8.300 @sf 6 1832 p 77 c ammi10.329 @sf 45 1848 p 59 c t-rom.330 @sf 8 r 46 c 8 r 46 c 7 r 46 c 0 r 46 c 34 r (Processors) s 20 r (in) s 19 r 97 c 20 r (synchronization) s 20 r (group,) s ammi10.329 @sf -119 1902 p 71 c ammi8.300 @sf -83 1886 p 75 c t-rom.330 @sf -49 1902 p 44 c 13 r (regularly) s 15 r (exchange) s 14 r (\015ow) s 15 r (information) s 14 r (using) s t-ita.330 @sf 14 r (period) s -119 1956 p (messages) s t-rom.330 @sf 0 r 44 c 12 r (to) s 12 r (compute) s 12 r 97 c 12 r (common) s 12 r (synchronization) s 12 r (delay) s ammi10.329 @sf -119 2010 p 1 c ammi8.300 @sf -81 1994 p 75 c t-rom.330 @sf -30 2010 p (for) s 17 r (the) s 17 r (group.) s 27 r (The) s 17 r (process) s 17 r (of) s 18 r (message) s 17 r (exchange) s -119 2064 p (occurs) s 15 r (typically) s 15 r (at) s 16 r 97 c 15 r (much) s 16 r (lower) s 15 r (rate) s 16 r (than) s 15 r (the) s 16 r (transfer) s -119 2118 p (of) s 14 r (real-time) s 15 r (data.) s -73 2182 p (The) s 9 r (protocol) s 10 r (exploits) s 10 r (synchronized) s 10 r (clocks) s 11 r (not) s 10 r (only) s 10 r (to) s -119 2236 p (time-stamp) s 10 r (data) s 10 r (and) s 11 r (equalize) s 10 r (delay) s -2 r 44 c 11 r (but) s 11 r (also) s 10 r (to) s 11 r (facilitate) s -119 2290 p (control) s 19 r (of) s 19 r (the) s 20 r (protocol.) s 33 r (The) s 20 r (initiator) s 20 r (distributes) s 19 r (four) s t-ita.330 @sf -119 2344 p (time) s 12 r (parameters) s t-rom.330 @sf 13 r (which) s 13 r (divide) s 13 r (the) s 13 r (time-line) s 14 r (into) s t-ita.330 @sf 13 r (update) s -119 2398 p (periods) s t-rom.330 @sf 0 r 44 c 14 r (as) s 15 r (shown) s 15 r (in) s 15 r (Figure) s 15 r (5.) s 20 r (These) s 15 r (parameters) s 15 r (are) s 15 r 97 c t-ita.330 @sf -119 2452 p 114 c -2 r (efer) s -1 r (ence) s 10 r (time) s ammi10.329 @sf 12 r 116 c t-rom.240 @sf 167 2458 p 48 c t-rom.330 @sf 197 2452 p (for) s 12 r (the) s 12 r (session) s 11 r (time) s 12 r (stamps;) s 13 r (the) s 11 r (length) s ammi10.329 @sf -119 2506 p 28 c ammi8.300 @sf -102 2512 p 117 c t-rom.330 @sf -63 2506 p (of) s 16 r (the) s t-ita.330 @sf 16 r (update) s 17 r (period) s t-rom.330 @sf 0 r 59 c 17 r (the) s 16 r (length) s ammi10.329 @sf 17 r 28 c ammi8.300 @sf 573 2512 p 113 c t-rom.330 @sf 608 2506 p (of) s 17 r 97 c t-ita.330 @sf 16 r (quiescence) s -119 2560 p (interval) s t-rom.330 @sf 15 r (at) s 17 r (the) s 16 r (begining) s 17 r (of) s 16 r (the) s 16 r (update) s 17 r (period) s 16 r (and) s 16 r (used) s -119 2614 p (to) s 21 r (exchange) s 21 r (period) s 22 r (messages;) s 25 r (and) s 21 r 97 c t-ita.330 @sf 22 r (change) s 21 r (time) s ammi10.329 @sf 22 r 116 c ammi8.300 @sf 879 2620 p 120 c lcirclew10.300 @sf 1096 238 p (\022\021) s 1096 155 p 19 c 0 r 16 c 1318 84 p (\036\035) s 1318 -48 p 31 c 0 r 28 c 1767 213 p (\026\025) s 1767 113 p 23 c 0 r 20 c 1832 356 p (\022\021) s 1832 273 p 19 c 0 r 16 c 1622 77 p 39 c 1622 309 p 3 151 ru 1622 394 p 38 c 2005 77 p 36 c 2005 309 p 3 151 ru 2005 394 p 37 c -463 r 217 3 ru 1707 77 p 217 3 ru 1643 759 p (\022\021) s 1643 676 p 19 c 0 r 16 c 1855 581 p (\022\021) s 1855 498 p 19 c 0 r 16 c 1576 460 p 39 c 1576 705 p 3 164 ru 1576 790 p 38 c 2018 460 p 36 c 2018 705 p 3 164 ru 2018 790 p 37 c -522 r 276 3 ru 1661 460 p 276 3 ru 1115 571 p (\022\021) s 1115 488 p 19 c 0 r 16 c linew10.300 @sf 1202 568 p 88 c 1207 569 p 88 c 1306 594 p 88 c 1310 595 p 88 c 1410 620 p 88 c 1414 621 p 88 c 1514 646 p 88 c 1518 647 p 88 c 1618 671 p 88 c 1622 673 p 88 c 1622 673 p 122 c 1222 504 p 16 c 1225 503 p 16 c 1305 477 p 16 c 1309 475 p 16 c 1388 449 p 16 c 1392 448 p 16 c 1471 421 p 16 c 1475 420 p 16 c 1554 393 p 16 c 1558 392 p 16 c 1638 366 p 16 c 1641 364 p 16 c 1721 338 p 16 c 1725 337 p 16 c 1725 337 p 49 c 1047 -71 p 1013 3 ru 1047 820 p 3 891 ru 1010 r 3 891 ru 1047 823 p 1013 3 ru 1804 625 p 18 c -41 r 0 c 1762 667 p 0 c 1746 683 p 0 c -40 r 9 c 1881 250 p 87 c -9 r 67 c 1875 226 p 67 c -9 r 79 c 1189 145 p 61 c t-rom.300 @sf 1316 46 p 46 c 1290 66 p 46 c 1263 86 p 46 c 1237 106 p 46 c 1211 125 p 46 c linew10.300 @sf 1715 155 p 106 c t-rom.300 @sf 1455 7 p 46 c 1484 22 p 46 c 1514 36 p 46 c 1544 51 p 46 c 1574 66 p 46 c 1603 81 p 46 c 1633 96 p 46 c 1663 111 p 46 c 1692 125 p 46 c 1722 140 p 46 c linew10.300 @sf 1758 293 p 115 c t-rom.300 @sf 1448 63 p 46 c 1475 81 p 46 c 1501 98 p 46 c 1528 116 p 46 c 1555 134 p 46 c 1581 152 p 46 c 1608 169 p 46 c 1635 187 p 46 c 1661 205 p 46 c 1688 223 p 46 c 1715 240 p 46 c 1741 258 p 46 c 1768 276 p 46 c linew10.300 @sf 1794 494 p 82 c t-rom.300 @sf 1418 83 p 46 c 1441 105 p 46 c 1464 128 p 46 c 1487 151 p 46 c 1510 174 p 46 c 1533 197 p 46 c 1556 220 p 46 c 1579 243 p 46 c 1602 266 p 46 c 1625 289 p 46 c 1648 312 p 46 c 1671 335 p 46 c 1693 358 p 46 c 1716 381 p 46 c 1739 403 p 46 c 1762 426 p 46 c 1785 449 p 46 c 1808 472 p 46 c linew10.300 @sf 1669 653 p 85 c t-rom.300 @sf 1405 92 p 46 c 1419 121 p 46 c 1433 149 p 46 c 1447 177 p 46 c 1461 205 p 46 c 1475 233 p 46 c 1489 261 p 46 c 1503 289 p 46 c 1517 317 p 46 c 1531 345 p 46 c 1546 373 p 46 c 1560 401 p 46 c 1574 429 p 46 c 1588 457 p 46 c 1602 485 p 46 c 1616 513 p 46 c 1630 541 p 46 c 1644 569 p 46 c 1658 597 p 46 c 1672 625 p 46 c linew10.300 @sf 1205 468 p 13 c t-rom.300 @sf 1333 73 p 46 c 1322 103 p 46 c 1312 134 p 46 c 1302 164 p 46 c 1292 195 p 46 c 1282 225 p 46 c 1272 255 p 46 c 1262 286 p 46 c 1251 316 p 46 c 1241 347 p 46 c 1231 377 p 46 c 1221 408 p 46 c 1211 438 p 46 c 1198 179 p 51 3 ru 103 r 51 3 ru 102 r 51 3 ru 102 r 51 3 ru 102 r 51 3 ru 102 r 51 3 ru linew10.300 @sf 1718 178 p 45 c 1231 542 p 47 3 ru 94 r 47 3 ru 94 r 47 3 ru 94 r 47 3 ru 94 r 47 3 ru 94 r 47 3 ru 94 r 47 3 ru 1801 541 p 45 c 1066 788 p 27 c 1066 790 p 129 3 ru 1154 788 p 45 c 1150 689 p 45 c t-rom.300 @sf 1062 690 p 46 c 21 r 46 c 21 r 46 c 21 r 46 c 1066 740 p 43 3 ru 86 r 43 3 ru linew10.300 @sf 1154 739 p 45 c ammi10.329 @sf 1647 729 p 68 c ammi8.300 @sf 1686 712 p 106 c 4 r 122 c ammi10.329 @sf 1109 204 p 83 c ammi8.300 @sf 1141 188 p 105 c ammi10.329 @sf 1367 42 p 73 c 1783 178 p 68 c ammi8.300 @sf 1822 161 p 105 c ammi10.329 @sf 1928 250 p 71 c ammi8.300 @sf 1964 234 p 75 c ammi10.329 @sf 1839 329 p 68 c ammi8.300 @sf 1878 313 p 106 c 3 r 120 c ammi10.329 @sf 1859 547 p 68 c ammi8.300 @sf 1897 531 p 106 c 4 r 121 c ammi10.329 @sf 1908 666 p 71 c ammi8.300 @sf 1944 650 p 77 c ammi10.329 @sf 1129 544 p 83 c ammi8.300 @sf 1161 527 p 106 c t-rom.270 @sf 1231 788 p (period) s 13 r (message) s 1231 739 p (event) s 13 r (message) s 1231 689 p (control) s 13 r (message) s t-rom.330 @sf 1194 1009 p (Figure) s 15 r (4:) s 21 r (Flow) s 15 r (of) s 15 r (Protocol) s 15 r (Messages.) s 1050 1148 p (indicating) s 22 r (when) s 22 r (the) s 21 r (contents) s 22 r (of) s 22 r (the) s 22 r (control) s 22 r (message) s 1050 1202 p (must) s 15 r (come) s 15 r (into) s 16 r (ef) s 0 r (fect) s 14 r (\(see) s 15 r (Section) s 15 r (3\).) s 1096 1259 p (The) s 20 r (client) s 20 r (activates) s 20 r (the) s 20 r (session) s 20 r (processors) s 20 r (and) s 20 r (the) s 1050 1313 p (protocol) s 12 r (begins) s 11 r (with) s 12 r (an) s t-ita.330 @sf 12 r (initialization) s t-rom.330 @sf 12 r (phase,) s 12 r (where) s 12 r (con-) s 1050 1367 p (trol,) s 21 r (event,) s 20 r (and) s 20 r (period) s 19 r (messages) s 20 r (initialize) s 20 r (parameters) s 1050 1421 p (across) s 15 r (\015ow) s 14 r (processors.) s 21 r (At) s 14 r (time) s ammi10.329 @sf 15 r 116 c t-rom.240 @sf 1672 1428 p 49 c t-rom.330 @sf 1703 1421 p 61 c ammi10.329 @sf 13 r 116 c t-rom.240 @sf 1758 1428 p 48 c t-rom.330 @sf 1785 1421 p 43 c ammi10.329 @sf 9 r 28 c ammi8.300 @sf 1838 1428 p 113 c t-rom.330 @sf 1871 1421 p (\(Figure) s 15 r (5\),) s 1050 1475 p (an) s t-ita.330 @sf 21 r (equalization) s t-rom.330 @sf 21 r (phase) s 20 r (begins) s 21 r (and) s 21 r (maintains) s 21 r (synchro-) s 1050 1529 p (nization.) s 1096 1586 p (For) s 25 r (equalization,) s 29 r (destination) s 25 r (processors) s 26 r (use) s 26 r (three) s 1050 1640 p (software) s 29 r (packages) s 30 r (called) s t-ita.330 @sf 29 r (application-oriented) s 29 r (func-) s 1050 1694 p (tions) s t-rom.330 @sf 0 r 58 c 28 r 97 c t-ita.330 @sf 18 r (Synchr) s 0 r (onization) s 18 r (Function) s t-rom.330 @sf 19 r (to) s 18 r (compute) s ammi10.329 @sf 19 r 1 c ammi8.300 @sf 1984 1677 p 75 c t-rom.330 @sf 2018 1694 p 44 c 20 r 97 c t-ita.330 @sf 1050 1748 p (Filtering) s 19 r (Function) s t-rom.330 @sf 20 r (to) s 19 r (estimate) s 20 r (the) s 19 r (\(unequalized\)) s 20 r (\015ow) s 1050 1802 p (delay) s ammi10.329 @sf 15 r 100 c ammi8.300 @sf 1187 1785 p 105 c t-rom.330 @sf 1202 1802 p 44 c 15 r (and) s 15 r 97 c t-ita.330 @sf 14 r (Delivery) s 15 r (Function) s t-rom.330 @sf 15 r (to) s 15 r (schedule) s 15 r (data) s 15 r (de-) s 1050 1856 p (livery) s -2 r 46 c 34 r 87 c -2 r 101 c 19 r (are) s 20 r (experimenting) s 20 r (with) s 21 r (default) s 20 r (functions,) s 1050 1910 p (but) s 16 r (the) s 15 r (client) s 16 r (can) s 15 r (supply) s 16 r (its) s 15 r (own) s 16 r (specialized) s 16 r (functions) s 1050 1964 p (and) s 13 r (verify) s 13 r (session-wide) s 13 r (consistency) s 12 r (using) s 13 r (an) s 13 r (initiator) s 2 r 39 c -2 r 115 c 1050 2018 p (control) s 15 r (message.) s t-bol.420 @sf 1050 2180 p 51 c 58 r (Initialization) s 22 r (and) s 23 r (Contr) s 0 r (ol) s t-rom.330 @sf 1050 2287 p 87 c -3 r 101 c 12 r (will) s 12 r (explain) s 13 r (the) s 12 r (protocol) s 13 r (operation) s 13 r (using) s 12 r (the) s 13 r (timing) s 1050 2341 p (diagram) s 17 r (of) s 16 r (Figure) s 17 r 53 c 17 r (and) s 16 r (making) s 17 r (reference) s 17 r (to) s 16 r (the) s 17 r (pro-) s 1050 2395 p (cessors) s ammi10.329 @sf 18 r 73 c 4 r 59 c 7 r 83 c ammi8.300 @sf 1275 2378 p 105 c ammi10.329 @sf 1290 2395 p 59 c 7 r 68 c ammi8.300 @sf 1349 2378 p 105 c t-rom.330 @sf 1381 2395 p (of) s 19 r (Figure) s 18 r (2.) s 29 r (The) s 18 r (same) s 18 r (explanations) s 1050 2449 p (apply) s 15 r (to) s 15 r (the) s 16 r (remaining) s 15 r (\015ow) s 15 r (processors.) s 1096 2506 p (The) s 15 r (client) s 15 r (activates) s 15 r (all) s 16 r (\015ow) s 15 r (processors) s 15 r (and) s 16 r (supplies) s 1050 2560 p (them) s 12 r (with) s 13 r (parameters) s 12 r (speci\014c) s 13 r (to) s 12 r (each) s 12 r (\015ow) s -2 r 46 c 19 r (This) s 12 r (action) s 1050 2614 p (begins) s 11 r (the) s 12 r (initialization) s 11 r (phase.) s 19 r (Then) s 12 r (the) s 11 r (client) s 12 r (activates) s 964 2738 p (1383) s @eop 4 @bop0 [ 300 ] /cmex10.300 @newfont cmex10.300 @sf [ 24 14 1 9 18.680] 122 @dc [ 24 14 1 0 18.680] 125 @dc [<0001F8000FF8003FF800FFF801FFF803FE0007E0000F80001E0000380000700000600000E00000C00000> 24 14 1 0 18.680] 124 @dc [<0000180000380000300000700000E00003C0000F80003F0003FE00FFFC00FFF800FFE000FF8000FC0000> 24 14 1 9 18.680] 123 @dc [ 329 ] /amsy10.329 @newfont amsy10.329 @sf [ 32 2 -4 -11 35.353] 0 @dc ammi10.329 @sf [<03E1E007F3F00F3FB81E1F9C1E0F8C1E078C1E07CC1E03C01E03C01E03C01F03E00F01E0CF01E0CF81E0E781F06780F07380 F03B80F01F00F00E0060> 24 20 -2 0 26.020] 117 @dc [ 24 29 1 9 22.869] 112 @dc 4 @bop1 -122 -53 p 1038 3 ru -122 564 p 3 619 ru 1033 r 3 619 ru -122 568 p 1038 3 ru 609 247 p 3 37 ru -31 270 p 3 52 ru -29 245 p 847 3 ru linew10.300 @sf 776 244 p 45 c 47 247 p 3 37 ru 216 266 p 3 52 ru 318 r 3 52 ru 291 247 p 3 37 ru -63 436 p 187 3 ru -63 435 p 27 c 124 436 p 694 3 ru 776 435 p 45 c 47 491 p 3 112 ru t-rom.270 @sf 214 543 p (PHASE) s 214 483 p (EQUALIZA) s -3 r (TION) s -100 543 p (PHASE) s -104 483 p (INIT) s -3 r 46 c cmex10.300 @sf -29 156 p (z}|{) s -25 29 p 122 c 0 r 83 5 ru 81 r (}|) s 0 r 83 5 ru 83 r 123 c t-rom.270 @sf 780 318 p (time) s ammi10.329 @sf -246 r 116 c t-rom.240 @sf 616 326 p 53 c ammi10.329 @sf 514 318 p 116 c t-rom.240 @sf 530 325 p 52 c ammi10.329 @sf 285 318 p 116 c t-rom.240 @sf 301 325 p 51 c ammi10.329 @sf 202 318 p 116 c t-rom.240 @sf 219 325 p 50 c ammi10.329 @sf 34 318 p 116 c t-rom.240 @sf 50 325 p 49 c ammi10.329 @sf 86 -7 p 28 c ammi8.300 @sf 104 0 p 117 c ammi10.329 @sf -7 116 p 28 c ammi8.300 @sf 10 123 p 113 c ammi10.329 @sf -40 318 p 116 c t-rom.240 @sf -24 325 p 48 c ammi10.329 @sf 540 169 p 116 c t-rom.240 @sf 556 175 p 52 c amsy10.329 @sf 585 169 p 0 c ammi10.329 @sf 10 r 116 c t-rom.240 @sf 647 175 p 48 c ammi10.329 @sf 450 172 p 116 c ammi8.300 @sf 466 179 p 120 c t-rom.330 @sf 500 172 p 61 c -119 758 p (Figure) s 16 r (5:) s 23 r 84 c -1 r (ime) s 16 r (Parameters) s 16 r (and) s 17 r (Protocol) s 17 r (Phases.) s ammi10.329 @sf 24 r 28 c ammi8.300 @sf 837 765 p 117 c t-rom.330 @sf 874 758 p 61 c -119 814 p (update) s 10 r (period,) s ammi10.329 @sf 12 r 28 c ammi8.300 @sf 171 821 p 113 c t-rom.330 @sf 202 814 p 61 c 11 r (quiescence) s 12 r (period,) s ammi10.329 @sf 12 r 116 c ammi8.300 @sf 607 821 p 120 c t-rom.330 @sf 641 814 p 61 c 11 r (change) s 12 r (time) s -119 871 p 40 c ammi10.329 @sf 0 r 116 c ammi8.300 @sf -88 878 p 120 c t-rom.330 @sf -54 871 p 61 c ammi10.329 @sf 12 r 116 c t-rom.240 @sf 0 878 p 52 c amsy10.329 @sf 29 871 p 0 c ammi10.329 @sf 10 r 116 c t-rom.240 @sf 91 878 p 48 c t-rom.330 @sf 125 871 p (is) s 15 r (one) s 15 r (example\).) s ammi10.329 @sf -119 1026 p 73 c t-rom.330 @sf 3 r 44 c 17 r (through) s 17 r (which) s 17 r (it) s 17 r (controls) s 17 r (the) s 16 r (session.) s 26 r (The) s 17 r (initiator) s -119 1080 p (computes) s 14 r (the) s 15 r (time) s 15 r (parameters) s ammi10.329 @sf 15 r 116 c t-rom.240 @sf 469 1087 p 48 c ammi10.329 @sf 488 1080 p 59 c 7 r 116 c ammi8.300 @sf 524 1087 p 120 c ammi10.329 @sf 545 1080 p 59 c 8 r 28 c ammi8.300 @sf 583 1087 p 113 c ammi10.329 @sf 602 1080 p 59 c 8 r 28 c ammi8.300 @sf 640 1087 p 117 c t-rom.330 @sf 677 1080 p (based) s 15 r (on) s 15 r (its) s -119 1134 p (knowledge) s 15 r (of) s 16 r (the) s 16 r (network,) s 16 r (and) s 16 r (sends) s 16 r (them) s 16 r (to) s 16 r (all) s 16 r (\015ow) s -119 1188 p (processors) s 9 r (in) s 11 r 97 c 10 r (control) s 10 r (message.) s 19 r (The) s 10 r (value) s ammi10.329 @sf 10 r 116 c ammi8.300 @sf 691 1195 p 120 c t-rom.330 @sf 722 1188 p (is) s 11 r (relative) s -119 1242 p (to) s ammi10.329 @sf 10 r 116 c t-rom.240 @sf -57 1249 p 48 c t-rom.330 @sf -27 1242 p (and) s 9 r (for) s 11 r (this) s 10 r (initialization) s 11 r (control) s 10 r (message) s ammi10.329 @sf 11 r 116 c ammi8.300 @sf 751 1249 p 120 c t-rom.330 @sf 785 1242 p 61 c 13 r (0.) s ammi10.329 @sf 18 r 73 c t-rom.330 @sf -119 1296 p (also) s 11 r (includes) s 13 r (session) s 12 r (control) s 13 r (parameters) s 12 r (from) s 12 r (the) s 13 r (client) s -119 1350 p (in) s 14 r (the) s 15 r (control) s 16 r (message.) s -73 1415 p (When) s ammi10.329 @sf 17 r 83 c ammi8.300 @sf 85 1398 p 105 c t-rom.330 @sf 118 1415 p (receives) s 18 r (the) s 19 r (control) s 18 r (message,) s 19 r (it) s 19 r (sends) s 18 r (an) s -119 1469 p (event) s 16 r (message) s 17 r (to) s 17 r (all) s 17 r (its) s 17 r (associated) s 18 r (destination) s 17 r (proces-) s -119 1523 p (sors) s 18 r (and) s 20 r (waits) s 19 r (for) s 20 r (the) s 19 r (start) s 20 r (of) s 19 r (the) s 20 r (equalization) s 19 r (phase) s -119 1577 p 40 c ammi10.329 @sf 0 r 116 c t-rom.240 @sf -88 1584 p 49 c t-rom.330 @sf -69 1577 p (\).) s 19 r (This) s 13 r (message) s 14 r (is) s 13 r 97 c 14 r (vehicle) s 13 r (to) s 14 r (communicate) s 13 r (param-) s -119 1631 p (eters) s 10 r (describing) s 11 r (the) s 12 r (\015ow) s 11 r (if) s 11 r (they) s 11 r (are) s 11 r (known) s 12 r (at) s 11 r (the) s 11 r (source) s -119 1685 p (but) s 16 r (not) s 17 r (at) s 17 r (the) s 17 r (destination.) s 26 r (The) s 17 r (value) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 611 1692 p 48 c t-rom.330 @sf 630 1685 p 44 c 17 r (chosen) s 17 r (by) s ammi10.329 @sf 17 r 73 c t-rom.330 @sf 4 r 44 c -119 1739 p (must) s 19 r (give) s 20 r (enough) s 20 r (time) s 20 r (for) s 20 r (the) s 20 r (reception) s 20 r (of) s 20 r (all) s 20 r (these) s -119 1793 p (control) s 14 r (and) s 15 r (event) s 16 r (messages) s 15 r (sent) s 15 r (during) s 15 r (initialization.) s -73 1858 p (When) s ammi10.329 @sf 9 r 68 c ammi8.300 @sf 84 1841 p 105 c t-rom.330 @sf 108 1858 p (receives) s 11 r (its) s 10 r (control) s 10 r (message) s 10 r (and) s 10 r (event) s 11 r (mes-) s -119 1912 p (sage,) s 16 r (it) s 17 r (waits) s 17 r (until) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 262 1918 p 48 c t-rom.330 @sf 281 1912 p 46 c 25 r (At) s 17 r (this) s 16 r (time) s 17 r (it) s 17 r (assembles) s 17 r 97 c 17 r (pe-) s -119 1966 p (riod) s 17 r (message) s 17 r (and) s 18 r (sends) s 17 r (it) s 18 r (to) s 17 r (all) s 18 r (other) s 17 r (members) s 18 r (of) s 17 r (its) s -119 2020 p (synchronization) s 18 r (group) s ammi10.329 @sf 20 r 71 c ammi8.300 @sf 353 2003 p 75 c t-rom.330 @sf 387 2020 p 46 c 33 r (The) s 19 r (value) s ammi10.329 @sf 20 r 28 c ammi8.300 @sf 657 2026 p 113 c t-rom.330 @sf 676 2020 p 44 c 21 r (chosen) s 19 r (by) s ammi10.329 @sf -119 2074 p 73 c t-rom.330 @sf 3 r 44 c 19 r (must) s 18 r (give) s 18 r (enough) s 19 r (time) s 18 r (for) s 18 r (the) s 19 r (exchange) s 18 r (of) s 18 r (period) s -119 2128 p (messages) s 21 r (in) s 22 r (all) s 22 r (synchronization) s 22 r (groups.) s 41 r (The) s 22 r (period) s -119 2182 p (message) s 16 r (carries) s 17 r (three) s 18 r (parameters:) s ammi10.329 @sf 24 r 100 c ammi8.300 @sf 560 2165 p 105 c t-rom.330 @sf 574 2182 p 44 c ammi10.329 @sf 18 r 117 c ammi8.300 @sf 630 2165 p 105 c t-rom.330 @sf 644 2182 p 44 c ammi10.329 @sf 18 r 112 c ammi8.300 @sf 696 2165 p 105 c t-rom.330 @sf 710 2182 p 46 c 26 r (Parame-) s -119 2236 p (ter) s ammi10.329 @sf 18 r 100 c ammi8.300 @sf -28 2219 p 105 c t-rom.330 @sf 4 2236 p (is) s 19 r (the) s 18 r (\015ow) s 19 r (delay) s -2 r 46 c 30 r (For) s 19 r (initialization,) s ammi10.329 @sf 20 r 68 c ammi8.300 @sf 749 2219 p 105 c t-rom.330 @sf 782 2236 p (uses) s 19 r 97 c -119 2290 p (default) s 16 r (value) s 16 r (for) s ammi10.329 @sf 17 r 100 c ammi8.300 @sf 232 2273 p 105 c t-rom.330 @sf 263 2290 p (supplied) s 17 r (by) s 17 r (the) s 16 r (client) s 17 r (locally;) s 17 r (but) s -119 2344 p (during) s 13 r (equalization) s 14 r (the) s 13 r (Filtering) s 14 r (Function) s 14 r (estimates) s ammi10.329 @sf 14 r 100 c ammi8.300 @sf 874 2327 p 105 c t-rom.330 @sf 889 2344 p 46 c -119 2398 p (Parameter) s ammi10.329 @sf 19 r 117 c ammi8.300 @sf 111 2381 p 105 c t-rom.330 @sf 146 2398 p (is) s 20 r (an) s 20 r (upperbound) s 20 r (on) s 20 r (the) s 20 r (maximum) s 20 r (ac-) s -119 2452 p (ceptable) s 18 r (end-to-end) s 19 r (delay) s 19 r (for) s 19 r (the) s 19 r (\015ow) s 19 r (served) s 18 r (by) s ammi10.329 @sf 19 r 68 c ammi8.300 @sf 874 2435 p 105 c t-rom.330 @sf 889 2452 p 44 c -119 2506 p (and) s ammi10.329 @sf 20 r 112 c ammi8.300 @sf -10 2489 p 105 c t-rom.330 @sf 24 2506 p (is) s 21 r (the) s 20 r (\015ow) s 21 r (priority) s -2 r 46 c 35 r (The) s 21 r (client) s 20 r (supplies) s 21 r (both) s -119 2560 p (values) s ammi10.329 @sf 18 r 117 c ammi8.300 @sf 41 2543 p 105 c t-rom.330 @sf 56 2560 p 44 c ammi10.329 @sf 19 r 112 c ammi8.300 @sf 109 2543 p 105 c t-rom.330 @sf 124 2560 p 46 c 30 r (During) s 19 r (the) s 18 r (quiescence) s 19 r (period,) s ammi10.329 @sf 20 r 68 c ammi8.300 @sf 793 2543 p 105 c t-rom.330 @sf 826 2560 p (also) s -119 2614 p (gives) s 13 r (the) s 14 r (values) s ammi10.329 @sf 15 r 100 c ammi8.300 @sf 215 2597 p 105 c t-rom.330 @sf 229 2614 p 44 c ammi10.329 @sf 15 r 117 c ammi8.300 @sf 281 2597 p 105 c t-rom.330 @sf 296 2614 p 44 c ammi10.329 @sf 14 r 112 c ammi8.300 @sf 344 2597 p 105 c t-rom.330 @sf 373 2614 p (to) s 14 r (its) s 14 r (Synchronization) s 14 r (Func-) s 1050 -44 p (tion.) s 25 r (Before) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 1315 -37 p 49 c t-rom.330 @sf 1333 -44 p 44 c ammi10.329 @sf 18 r 68 c ammi8.300 @sf 1401 -60 p 105 c t-rom.330 @sf 1432 -44 p (receives) s 17 r (period) s 17 r (messages) s 17 r (from) s 16 r (its) s 1050 9 p (peer) s 16 r (processors) s 16 r (in) s ammi10.329 @sf 16 r 71 c ammi8.300 @sf 1440 -6 p 75 c t-rom.330 @sf 1490 9 p (and) s 16 r (hands) s 16 r (their) s 16 r (contents) s 16 r (to) s 16 r (the) s 1050 63 p (Synchronization) s 13 r (Function.) s 19 r (At) s ammi10.329 @sf 13 r 116 c t-rom.240 @sf 1630 70 p 49 c t-rom.330 @sf 1661 63 p (the) s 13 r (equalization) s 13 r (phase) s 1050 117 p (begins) s 14 r (and) s 14 r (time-stamped) s 14 r (units) s 14 r (can) s 14 r (\015ow) s 14 r (across) s 14 r (the) s 14 r (net-) s 1050 171 p (work.) s 1096 301 p (During) s 12 r (the) s 13 r (equalization) s 13 r (phase,) s 14 r (the) s 12 r (client) s 13 r (controls) s 13 r (the) s 1050 355 p (protocol) s 12 r (by) s 13 r (issuing) s 12 r (commands) s 13 r (to) s 12 r (the) s 12 r (processors) s 13 r (and) s 12 r (by) s 1050 409 p (updating) s 17 r (session) s 18 r (parameters.) s 26 r (As) s 18 r (an) s 17 r (example) s 17 r (consider) s 1050 463 p (changing) s 14 r (the) s 14 r (rate) s 13 r (at) s 14 r (which) s ammi10.329 @sf 14 r 1 c ammi8.300 @sf 1593 447 p 75 c t-rom.330 @sf 1641 463 p (is) s 14 r (updated) s 13 r (in) s 14 r 97 c 14 r (session.) s 1050 517 p (This) s 18 r (rate) s 19 r (is) s 18 r (equal) s 19 r (for) s 18 r (all) s 19 r (synchronization) s 18 r (groups,) s 20 r (and) s 1050 571 p (is) s 18 r 97 c 17 r (parameter) s 18 r (carried) s 18 r (in) s 17 r (the) s 18 r (control) s 18 r (messages.) s 27 r (If) s 18 r (the) s 1050 625 p (client) s 22 r (wishes) s 22 r (to) s 22 r (change) s 23 r (this) s 22 r (rate,) s 24 r (it) s 22 r (commands) s ammi10.329 @sf 22 r 73 c t-rom.330 @sf 26 r (to) s 1050 679 p (send) s 13 r 97 c 14 r (new) s 13 r (control) s 14 r (message) s 13 r (with) s 14 r (the) s 13 r (new) s 13 r (rate) s 14 r (value.) s ammi10.329 @sf 19 r 73 c t-rom.330 @sf 1050 733 p (must) s 14 r (recompute) s ammi10.329 @sf 14 r 116 c ammi8.300 @sf 1376 740 p 120 c t-rom.330 @sf 1412 733 p (in) s 14 r (the) s 14 r (message) s 14 r (to) s 14 r (coincide) s 15 r (with) s 14 r (the) s 1050 787 p (begining) s 15 r (of) s 15 r (an) s 15 r (update) s 15 r (period) s 15 r (\(for) s 15 r (example) s ammi10.329 @sf 14 r 116 c ammi8.300 @sf 1873 794 p 120 c t-rom.330 @sf 1907 787 p 61 c ammi10.329 @sf 13 r 116 c t-rom.240 @sf 1962 794 p 52 c amsy10.329 @sf 1990 787 p 0 c ammi10.329 @sf 10 r 116 c t-rom.240 @sf 2051 794 p 48 c t-rom.330 @sf 1050 841 p (in) s 16 r (Figure) s 16 r (5\).) s 22 r (The) s 16 r (new) s 16 r (rate) s 15 r (value) s 16 r (will) s 16 r (enter) s 16 r (into) s 16 r (ef) s 0 r (fect) s 1050 895 p (session-wide) s 18 r (at) s 18 r (time) s ammi10.329 @sf 18 r 116 c t-rom.240 @sf 1470 902 p 48 c t-rom.330 @sf 1501 895 p 43 c ammi10.329 @sf 12 r 116 c ammi8.300 @sf 1555 902 p 120 c t-rom.330 @sf 1576 895 p 46 c 29 r (Similarly) s -2 r 44 c 18 r (the) s 18 r (client) s 17 r (can) s 1050 949 p (command) s ammi10.329 @sf 12 r 83 c ammi8.300 @sf 1274 933 p 105 c t-rom.330 @sf 1300 949 p (to) s 11 r (send) s 12 r 97 c 12 r (new) s 12 r (event) s 11 r (message.) s 19 r (In) s 12 r (this) s 12 r (way) s -2 r 44 c 1050 1003 p (the) s 18 r (client) s 18 r (could) s 18 r (update) s 18 r (from) s 19 r (the) s 18 r (source) s 18 r (the) s 18 r (values) s ammi10.329 @sf 18 r 117 c ammi8.300 @sf 2056 987 p 105 c t-rom.330 @sf 1050 1057 p (or) s ammi10.329 @sf 15 r 112 c ammi8.300 @sf 1126 1041 p 105 c t-rom.330 @sf 1156 1057 p (at) s ammi10.329 @sf 15 r 68 c ammi8.300 @sf 1243 1041 p 105 c t-rom.330 @sf 1257 1057 p 46 c 1096 1187 p (In) s 20 r (the) s 21 r (protocol) s 21 r (speci\014cations,) s 22 r (we) s 21 r (describe) s 20 r (one) s 21 r (re-) s 1050 1241 p (liable) s 19 r (transport) s 19 r (mechanism) s 19 r (for) s 18 r (all) s 19 r (protocol) s 19 r (messages.) s 1050 1295 p (The) s 13 r (protocol) s 13 r (design) s 13 r (is) s 12 r (modular) s 13 r (so) s 13 r (dif) s 0 r (ferent) s 12 r (mechanism) s 1050 1349 p (could) s 12 r (easily) s 13 r (be) s 12 r (speci\014ed) s 12 r (in) s 13 r (other) s 12 r (versions.) s 19 r (Period) s 13 r (mes-) s 1050 1403 p (sages) s 21 r (could) s 20 r (exploit) s 21 r (their) s 21 r (periodicity) s 20 r (as) s 21 r 97 c 21 r (mechanism) s 1050 1457 p (for) s 20 r (reliable) s 21 r (transport,) s 21 r (but) s 21 r (to) s 20 r (simplify) s 20 r (implementation) s 1050 1511 p (we) s 19 r (kept) s 19 r (the) s 19 r (same) s 19 r (mechanism) s 19 r (\(acknowledgement\)) s 20 r (for) s 1050 1565 p (all) s 15 r (messages.) s 1096 1696 p (The) s 22 r (distributed) s 23 r (nature) s 22 r (of) s 23 r (the) s 22 r (protocol) s 23 r (and) s 23 r (its) s 22 r (ap-) s 1050 1750 p (plications) s 19 r (presents) s 20 r (the) s 19 r (problem) s 20 r (of) s 20 r (knowledge) s 19 r (consis-) s 1050 1804 p (tency) s 16 r (across) s 15 r (the) s 16 r (session.) s 21 r (The) s 16 r (protocol) s 16 r (gives) s 15 r (the) s 16 r (client) s 1050 1858 p 97 c 13 r (key-matching) s 12 r (mechanism) s 13 r (to) s 13 r (verify) s 13 r (the) s 12 r (consistency) s 13 r (of) s 1050 1912 p (application-oriented) s 15 r (functions) s 15 r (across) s 15 r (the) s 15 r (network.) s 20 r (The) s 1050 1966 p (client) s 15 r (installs) s 14 r (these) s 15 r (functions) s 14 r (at) s 15 r (the) s 14 r (destination) s 15 r (proces-) s 1050 2020 p (sors,) s 17 r (and) s 16 r (supplies) s 17 r 97 c 16 r (key) s 17 r (value) s 16 r (with) s 17 r (them.) s 24 r (This) s 16 r (key) s 17 r (is) s 1050 2074 p (the) s 18 r (same) s 19 r (for) s 18 r (all) s 19 r (destination) s 18 r (processors,) s 20 r (and) s 18 r (serves) s 19 r (as) s 1050 2128 p (an) s 15 r (identi\014er) s 15 r (for) s 15 r (the) s 15 r (session-wide) s 15 r (combination) s 14 r (of) s 15 r (func-) s 1050 2182 p (tions) s 19 r (chosen) s 18 r (by) s 19 r (the) s 18 r (client.) s 31 r (The) s 18 r (client) s 19 r (must) s 18 r (send) s 19 r (this) s 1050 2236 p (same) s 21 r (key) s 20 r (value) s 21 r (on) s 20 r (the) s 21 r (control) s 21 r (messages) s 20 r (from) s ammi10.329 @sf 21 r 73 c t-rom.330 @sf 3 r 46 c 37 r 65 c 1050 2290 p (key) s 14 r (mismatch) s 14 r (at) s 14 r (any) s ammi10.329 @sf 14 r 68 c ammi8.300 @sf 1487 2273 p 105 c t-rom.330 @sf 1516 2290 p (warns) s 14 r (the) s 14 r (client) s 14 r (of) s 14 r 97 c 14 r (potential) s 1050 2344 p (problem.) s 30 r 65 c 19 r (similar) s 19 r (key-matching) s 18 r (mechanism) s 19 r (is) s 18 r (used) s 1050 2398 p (to) s 15 r (synchronize) s 14 r (the) s 15 r (addition) s 15 r (or) s 14 r (removal) s 15 r (of) s 14 r (\015ow) s 15 r (proces-) s 1050 2452 p (sors) s 16 r (during) s 16 r 97 c 16 r (session.) s 22 r (Flow) s 16 r (processors) s 16 r (that) s 16 r (can) s 15 r (match) s 1050 2506 p 97 c t-ita.330 @sf 20 r (membership) s 21 r (key) s t-rom.330 @sf 20 r (in) s 20 r 97 c 21 r (control) s 20 r (message) s 20 r (with) s 21 r 97 c t-ita.330 @sf 20 r (local) s 1050 2560 p (key) s t-rom.330 @sf 14 r (from) s 15 r (the) s 14 r (client,) s 15 r (schedule) s 14 r (additions) s 15 r (or) s 14 r (removals) s 15 r (for) s 1050 2614 p (time) s ammi10.329 @sf 14 r 116 c ammi8.300 @sf 1162 2620 p 120 c t-rom.330 @sf 1183 2614 p 44 c 15 r (according) s 14 r (to) s 14 r (local) s 15 r (instructions) s 14 r (from) s 14 r (the) s 15 r (client.) s 964 2738 p (1384) s @eop 5 @bop0 ammi10.329 @sf [<1E00003F0000778000F1C000E1E000E0F000E0F000E07800E07800F03C00F03C00F03E00F01E00F01E00F81F007FFF007FFF 00780F007C0F803C07803C07803E07801E07801E07800F07800F078007878003878003C70001E70000FE00003C00> 24 32 -2 0 20.707] 18 @dc [ 40 31 -3 0 38.588] 75 @dc [<0FC0003FF00078F800703C00F01E00F01F00F00F00F00F80F00780F00780F807C07803C07C03C03C03C03E07C01F07800FCF 8007FFFE03FFFE00FFFE> 24 20 -1 0 25.089] 27 @dc ammi8.300 @sf [ 16 23 -2 0 18.372] 107 @dc [<78FCECEEE6E6F0707070783838383C1C1C1C1E0E0E3E3E> 8 23 -1 0 10.531] 108 @dc ammi10.329 @sf [<0FE03E001FFC7F003C3E73807807F180F003F000F000F000F000F000F000F800F000F800F000FC00F800FE007801F6007801 E7003C01E3003C01E3001E01E3800F03C18007C7818003FF000000FE0000> 32 20 -2 0 29.077] 11 @dc 5 @bop1 t-bol.420 @sf -119 -44 p 52 c 57 r (Equalization) s t-rom.330 @sf -119 63 p (The) s 16 r (equalization) s 17 r (phase) s 17 r (starts) s 17 r (at) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 509 69 p 49 c t-rom.330 @sf 543 63 p 61 c ammi10.329 @sf 15 r 116 c t-rom.240 @sf 600 69 p 48 c t-rom.330 @sf 630 63 p 43 c ammi10.329 @sf 11 r 28 c ammi8.300 @sf 685 69 p 113 c t-rom.330 @sf 704 63 p 46 c ammi10.329 @sf 25 r 83 c ammi8.300 @sf 772 46 p 105 c t-rom.330 @sf 804 63 p (time-) s -119 117 p (stamps) s 9 r (all) s 11 r (data) s 10 r (in) s 11 r (its) s 10 r (\015ow) s 11 r (with) s 10 r (time) s 10 r (stamp) s ammi10.329 @sf 11 r 18 c t-rom.330 @sf 14 r 61 c ammi10.329 @sf 12 r 116 c amsy10.329 @sf 1 r 0 c ammi10.329 @sf 1 r 14 c ammi8.300 @sf 803 100 p 105 c 798 128 p 99 c amsy10.329 @sf 818 117 p 0 c ammi10.329 @sf 0 r 116 c t-rom.240 @sf 870 123 p 48 c t-rom.330 @sf 889 117 p 44 c -119 171 p (where) s ammi10.329 @sf 20 r 116 c t-rom.330 @sf 21 r (is) s 20 r (the) s 21 r (current) s 21 r (local) s 21 r (time.) s 37 r (The) s 21 r (value) s ammi10.329 @sf 21 r 14 c ammi8.300 @sf 801 154 p 105 c 797 182 p 99 c t-rom.330 @sf 837 171 p (can) s -119 225 p (account) s 17 r (for) s 19 r (processing) s 18 r (delays,) s 19 r (transit) s 18 r (through) s 19 r (subnet-) s -119 279 p (works,) s 15 r (and) s 16 r (buf) s 0 r (fering) s 15 r (at) s 16 r (the) s 16 r (source.) s 22 r (Expressing) s ammi10.329 @sf 16 r 18 c t-rom.330 @sf 18 r (rela-) s -119 333 p (tive) s 15 r (to) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 33 339 p 48 c t-rom.330 @sf 52 333 p 44 c 17 r (makes) s 16 r (it) s 16 r (simple) s 17 r (to) s 16 r (synchronize) s 17 r (prerecorded) s -119 387 p (time-stamped) s 19 r (data) s 19 r (from) s 20 r (databases) s 19 r (into) s 20 r 97 c 19 r (multimedia-) s -119 441 p (object) s 13 r (schedule) s 14 r (or) s 14 r 97 c 14 r (real-time) s 14 r (session.) s 20 r (Our) s 14 r (current) s 14 r (im-) s -119 495 p (plementation) s 18 r (of) s 18 r (the) s 19 r (protocol) s 18 r (uses) s 19 r (its) s 18 r (own) s 19 r (time-stamp) s -119 549 p (data) s 19 r (unit) s 21 r (to) s 20 r (remain) s 20 r (minimally) s 21 r (dependent) s 20 r (on) s 20 r (the) s 21 r (net-) s -119 603 p (work') s -3 r 115 c 15 r (transport) s 15 r (protocol.) s ammi10.329 @sf -73 660 p 68 c ammi8.300 @sf -34 643 p 105 c t-rom.330 @sf -4 660 p (uses) s 15 r (each) s 16 r (received) s 16 r (time) s 16 r (stamp) s ammi10.329 @sf 15 r 18 c t-rom.330 @sf 18 r (to) s 16 r (compute) s 15 r (the) s -119 714 p (associated) s 14 r (release) s 16 r (time) s 15 r (as) s ammi10.329 @sf 15 r 116 c ammi8.300 @sf 391 721 p 114 c t-rom.330 @sf 422 714 p 61 c ammi10.329 @sf 13 r 116 c t-rom.240 @sf 477 721 p 48 c t-rom.330 @sf 506 714 p 43 c ammi10.329 @sf 10 r 18 c t-rom.330 @sf 11 r 43 c ammi10.329 @sf 11 r 1 c ammi8.300 @sf 648 697 p 75 c amsy10.329 @sf 692 714 p 0 c ammi10.329 @sf 10 r 14 c ammi8.300 @sf 761 697 p 105 c 756 727 p 100 c t-rom.330 @sf 777 714 p 46 c 20 r (\(Fig-) s -119 768 p (ure) s 17 r (1.\)) s 28 r (This) s 18 r (value) s ammi10.329 @sf 17 r 116 c ammi8.300 @sf 265 775 p 114 c t-rom.330 @sf 301 768 p (is) s 18 r (passed) s 18 r (to) s 18 r (the) s 17 r (Delivery) s 18 r (Func-) s -119 822 p (tion,) s 21 r (which) s 20 r (schedules) s 21 r (data) s 20 r (delivery) s -1 r 46 c 35 r (Meanwhile,) s 22 r (the) s -119 876 p (Filtering) s 24 r (Function) s 25 r (makes) s 25 r 97 c 25 r (\015ow-delay) s 25 r (measurement) s -119 930 p 40 c ammi10.329 @sf 0 r 116 c amsy10.329 @sf 9 r 0 c ammi10.329 @sf 10 r 116 c t-rom.240 @sf -16 937 p 48 c amsy10.329 @sf 12 930 p 0 c ammi10.329 @sf 10 r 18 c t-rom.330 @sf 12 r 43 c ammi10.329 @sf 10 r 14 c ammi8.300 @sf 149 913 p 105 c 144 943 p 100 c t-rom.330 @sf 165 930 p 41 c 15 r (to) s 15 r (estimate) s 15 r (the) s 16 r (\015ow) s 15 r (delay) s ammi10.329 @sf 15 r 100 c ammi8.300 @sf 718 913 p 105 c t-rom.330 @sf 733 930 p 46 c -73 987 p (Besides) s 17 r (time-stamping) s 18 r (functions,) s 18 r (the) s 18 r (protocol) s 18 r (must) s -119 1041 p (adapt) s 14 r (to) s 15 r (changes) s 15 r (in) s 14 r (delay) s -2 r 46 c 20 r (This) s 15 r (is) s 14 r (done) s 15 r (by) s 15 r (exchanging) s -119 1095 p (period) s 18 r (messages) s 19 r (within) s 19 r (quiescence) s 19 r (periods.) s ammi10.329 @sf 31 r 68 c ammi8.300 @sf 778 1079 p 105 c t-rom.330 @sf 811 1095 p (must) s -119 1149 p (receive) s 11 r (the) s 12 r (initialization) s 12 r (period) s 12 r (messages) s 12 r (from) s 12 r (all) s 12 r (other) s -119 1203 p (members) s 14 r (of) s ammi10.329 @sf 16 r 71 c ammi8.300 @sf 152 1187 p 75 c t-rom.330 @sf 202 1203 p (by) s ammi10.329 @sf 15 r 116 c t-rom.240 @sf 279 1210 p 49 c t-rom.330 @sf 298 1203 p 59 c 15 r (and) s 16 r (similarly) s 15 r (all) s 15 r (other) s 16 r (destina-) s -119 1257 p (tion) s 15 r (processors.) s 22 r 84 c -2 r 111 c 15 r (spread) s 15 r (the) s 16 r (network) s 16 r (load,) s ammi10.329 @sf 16 r 68 c ammi8.300 @sf 773 1241 p 105 c t-rom.330 @sf 804 1257 p (waits) s -119 1311 p 97 c 14 r (random) s 14 r (number) s 15 r (of) s 15 r (up) s 15 r (to) s ammi10.329 @sf 14 r 75 c t-rom.330 @sf 18 r (update) s 15 r (periods,) s 15 r (and) s 15 r (then) s -119 1365 p (sends) s 16 r (new) s 18 r (period) s 17 r (messages) s 18 r (periodically) s -2 r 44 c 17 r (every) s ammi10.329 @sf 17 r 75 c t-rom.330 @sf 21 r (up-) s -119 1419 p (date) s 18 r (periods.) s 31 r (This) s 19 r (randomness) s 18 r (spreads) s 19 r (over) s 19 r (time) s 19 r (the) s -119 1473 p (total) s 17 r (load) s 18 r (from) s 19 r (the) s 18 r (processors.) s 29 r 84 c -2 r 111 c 17 r (speed) s 19 r (protocol) s 18 r (re-) s -119 1527 p (sponse,) s ammi10.329 @sf 14 r 68 c ammi8.300 @sf 70 1511 p 105 c t-rom.330 @sf 99 1527 p (will) s 15 r (also) s 15 r (send) s 16 r 97 c 15 r (new) s 15 r (message) s 15 r (whenever) s ammi10.329 @sf 15 r 100 c ammi8.300 @sf 886 1511 p 105 c t-rom.330 @sf -119 1581 p (changes) s 19 r (by) s 19 r (more) s 20 r (than) s ammi10.329 @sf 20 r 27 c t-rom.330 @sf 21 r (from) s 20 r (its) s 19 r (value) s 20 r (in) s 20 r (the) s 20 r (previ-) s -119 1635 p (ous) s 16 r (period.) s 27 r (Parameters) s ammi10.329 @sf 17 r 75 c t-rom.330 @sf 20 r (and) s ammi10.329 @sf 18 r 27 c t-rom.330 @sf 19 r (are) s 17 r (set) s 17 r (by) s 17 r (the) s 18 r (client) s -119 1689 p (through) s 14 r (the) s 15 r (control) s 16 r (messages.) s -73 1746 p 87 c -2 r (ithout) s 15 r (loss) s 17 r (of) s 16 r (generality) s -2 r 44 c 16 r (consider) s 16 r (next) s 17 r (the) s 16 r (update) s -119 1800 p (period) s 16 r (starting) s 17 r (at) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 234 1807 p 50 c t-rom.330 @sf 269 1800 p (to) s 17 r (illustrate) s 17 r (the) s 17 r (steady-state) s 17 r (oper-) s -119 1854 p (ation.) s ammi10.329 @sf 37 r 68 c ammi8.300 @sf 59 1838 p 105 c t-rom.330 @sf 94 1854 p (obtains) s 21 r (the) s 21 r (estimate) s ammi10.329 @sf 21 r 100 c ammi8.300 @sf 521 1838 p 105 c t-rom.330 @sf 556 1854 p (from) s 21 r (the) s 21 r (Filtering) s -119 1908 p (Function) s 14 r (at) s 16 r (time) s ammi10.329 @sf 15 r 116 c t-rom.240 @sf 219 1915 p 50 c t-rom.330 @sf 237 1908 p 46 c 21 r (If) s 15 r 97 c 15 r (period) s 16 r (message) s 15 r (must) s 15 r (be) s 16 r (sent,) s ammi10.329 @sf -119 1962 p 68 c ammi8.300 @sf -80 1946 p 105 c t-rom.330 @sf -53 1962 p (passes) s ammi10.329 @sf 11 r 100 c ammi8.300 @sf 99 1946 p 105 c ammi10.329 @sf 113 1962 p 59 c 8 r 117 c ammi8.300 @sf 159 1946 p 105 c ammi10.329 @sf 174 1962 p 59 c 7 r 112 c ammi8.300 @sf 217 1946 p 105 c t-rom.330 @sf 244 1962 p (to) s 12 r (its) s 13 r (Synchronization) s 12 r (Function) s 13 r (and) s -119 2016 p (also) s 15 r (sends) s 16 r (these) s 15 r (parameters) s 16 r (in) s 16 r 97 c 16 r (period) s 16 r (message) s 16 r (to) s 15 r (all) s -119 2070 p (other) s 16 r (processors) s 17 r (in) s ammi10.329 @sf 17 r 71 c ammi8.300 @sf 288 2054 p 75 c t-rom.330 @sf 323 2070 p 46 c 25 r (Before) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 517 2077 p 51 c t-rom.330 @sf 535 2070 p 44 c 17 r (processor) s ammi10.329 @sf 17 r 68 c ammi8.300 @sf 795 2054 p 106 c 3 r 120 c t-rom.330 @sf 849 2070 p (re-) s -119 2124 p (ceives) s 14 r (this) s 14 r (message,) s 15 r (and) s 14 r (passes) s 15 r (its) s 14 r (contents) s 15 r (to) s 14 r (its) s 15 r (Syn-) s -119 2178 p (chronization) s 16 r (Function.) s 24 r (At) s ammi10.329 @sf 17 r 116 c t-rom.240 @sf 402 2185 p 51 c t-rom.330 @sf 421 2178 p 44 c 17 r (this) s 16 r (function) s 17 r (returns) s 17 r (the) s -119 2232 p (updated) s 14 r (value) s 16 r (of) s ammi10.329 @sf 15 r 1 c ammi8.300 @sf 245 2216 p 75 c t-rom.330 @sf 279 2232 p 46 c 21 r (This) s 15 r (value) s 15 r (applies) s 16 r (for) s 15 r (the) s 15 r (com-) s -119 2286 p (putation) s 14 r (of) s ammi10.329 @sf 15 r 116 c ammi8.300 @sf 114 2293 p 114 c t-rom.330 @sf 148 2286 p (during) s 15 r (the) s 15 r (interval) s ammi10.329 @sf 15 r 116 c t-rom.240 @sf 524 2293 p 51 c t-rom.330 @sf 558 2286 p (to) s ammi10.329 @sf 15 r 116 c t-rom.240 @sf 625 2293 p 53 c t-rom.330 @sf 644 2286 p 46 c -73 2344 p 87 c -4 r 101 c 14 r (consider) s 14 r (the) s 15 r (application-oriented) s 15 r (functions) s 14 r (to) s 15 r (be) s -119 2398 p (part) s 15 r (of) s 15 r (the) s 16 r (client') s -1 r 115 c 14 r (domain.) s 22 r 87 c -3 r 101 c 15 r (take) s 16 r (this) s 16 r (approach) s 15 r (be-) s -119 2452 p (cause) s 20 r (we) s 21 r (expect) s 22 r (dif) s 0 r (ferent) s 20 r (families) s 21 r (of) s 21 r (applications) s 22 r (to) s -119 2506 p (lead) s 14 r (to) s 16 r 97 c 15 r (set) s 16 r (of) s 15 r (preferred) s 16 r (functions.) s 21 r (However) s -1 r 44 c 14 r (we) s 16 r (pro-) s -119 2560 p (vide) s 20 r (simple) s 21 r (default) s 20 r (functions) s 21 r (for) s 21 r (completeness.) s 37 r (Our) s -119 2614 p (default) s 16 r (Synchronization) s 18 r (Function) s 17 r (sets) s ammi10.329 @sf 17 r 1 c ammi8.300 @sf 644 2597 p 75 c t-rom.330 @sf 694 2614 p 61 c 16 r (max) s ammi8.300 @sf 815 2621 p 107 c ammi10.329 @sf 844 2614 p 100 c ammi8.300 @sf 867 2597 p 107 c t-rom.330 @sf 889 2614 p 44 c 1050 -44 p (among) s 22 r (delays) s ammi10.329 @sf 22 r 100 c ammi8.300 @sf 1359 -60 p 107 c t-rom.330 @sf 1402 -44 p (in) s ammi10.329 @sf 22 r 71 c ammi8.300 @sf 1495 -60 p 75 c t-rom.330 @sf 1529 -44 p 46 c 41 r (However) s -1 r 44 c 22 r (if) s ammi10.329 @sf 22 r 1 c ammi8.300 @sf 1869 -60 p 75 c t-rom.330 @sf 1925 -44 p (exceeds) s 1050 9 p (any) s 14 r (upperbound) s ammi10.329 @sf 15 r 117 c ammi8.300 @sf 1389 -6 p 108 c t-rom.330 @sf 1416 9 p (in) s ammi10.329 @sf 14 r 71 c ammi8.300 @sf 1501 -6 p 75 c t-rom.330 @sf 1535 9 p 44 c 15 r (the) s 14 r (maximum) s 14 r (is) s 15 r (only) s 14 r (taken) s 1050 63 p (over) s 15 r (those) s 15 r (values) s ammi10.329 @sf 16 r 100 c ammi8.300 @sf 1413 47 p 107 c t-rom.330 @sf 1450 63 p (for) s 15 r (which) s ammi10.329 @sf 15 r 112 c ammi8.300 @sf 1668 47 p 107 c t-rom.330 @sf 1705 63 p (does) s 15 r (not) s 15 r (equal) s 15 r (zero) s 1050 117 p (\(binary) s 19 r (priority) s 19 r (scheme\).) s 31 r (Our) s 19 r (default) s 19 r (Filtering) s 19 r (Func-) s 1050 171 p (tion) s 22 r (borrows) s 22 r 97 c 22 r (simple) s 21 r (smoothing) s 22 r (algorithm) s 22 r 91 c 0 r (21) s 0 r (].) s 40 r (It) s 1050 225 p (sets) s ammi10.329 @sf 22 r 100 c ammi8.300 @sf 1164 209 p 105 c t-rom.330 @sf 1200 225 p (to) s 22 r 97 c 21 r (multiple) s ammi10.329 @sf 22 r 11 c ammi8.300 @sf 1502 232 p 105 c t-rom.330 @sf 1538 225 p (of) s 22 r (the) s 22 r (smoothed) s 21 r (\015ow-delay) s 1050 279 p (measurements\() s ammi10.329 @sf 0 r 116 c amsy10.329 @sf 12 r 0 c ammi10.329 @sf 11 r 116 c t-rom.240 @sf 1418 286 p 48 c amsy10.329 @sf 1448 279 p 0 c ammi10.329 @sf 12 r 18 c t-rom.330 @sf 13 r 43 c ammi10.329 @sf 11 r 14 c ammi8.300 @sf 1589 263 p 105 c 1585 292 p 100 c t-rom.330 @sf 1605 279 p (\).) s 28 r (The) s 17 r (client) s 18 r (can) s 18 r (supply) s 1050 333 p (its) s 19 r (preferred) s 19 r (value) s ammi10.329 @sf 18 r 11 c ammi8.300 @sf 1445 340 p 105 c t-rom.330 @sf 1478 333 p (that) s 19 r (best) s 18 r (suits) s 19 r (its) s 19 r (model) s 19 r (of) s 19 r (de-) s 1050 387 p (lay) s 15 r (distribution.) s 21 r (Our) s 16 r (default) s 15 r (Delivery) s 15 r (Function) s 16 r (simply) s 1050 441 p (schedules) s 18 r (the) s 17 r (release) s 18 r (of) s 17 r (data) s 18 r (from) s 18 r (the) s 17 r (buf) s 0 r (fers) s 17 r (at) s 18 r (time) s ammi10.329 @sf 1050 495 p 116 c ammi8.300 @sf 1066 502 p 114 c t-rom.330 @sf 1084 495 p 46 c 40 r (\(Applications) s 22 r (could) s 21 r (alter) s 22 r (release) s 22 r (values,) s 23 r (at) s 22 r (their) s 1050 549 p (own) s 15 r (risk.\)) s t-bol.420 @sf 1050 716 p 53 c 58 r (Discussion) s t-rom.330 @sf 1050 825 p (It) s 23 r (is) s 23 r (easy) s 23 r (to) s 23 r (imagine) s 22 r (alternative) s 23 r (application-oriented) s 1050 879 p (functions.) s 45 r 65 c 23 r (Synchronization) s 23 r (Function) s 24 r (could) s 23 r (use) s 23 r 97 c 1050 933 p (more) s 19 r (complex) s 19 r (priority) s 19 r (system) s 19 r (than) s 19 r (the) s 19 r (binary) s 19 r (one) s 19 r (in) s 1050 987 p (our) s 19 r (default) s 18 r (function.) s 31 r (Similarly) s -2 r 44 c 19 r (more) s 18 r (complex) s 19 r (Filter-) s 1050 1041 p (ing) s 18 r (and) s 19 r (Delivery) s 18 r (Functions) s 18 r (can) s 18 r (be) s 19 r (designed.) s 29 r 87 c -2 r 101 c 17 r (did) s 1050 1095 p (not) s 16 r (want) s 16 r (to) s 15 r (predict) s 16 r (the) s 16 r (best) s 16 r (functions) s 16 r (for) s 16 r (future) s 15 r (appli-) s 1050 1149 p (cations,) s 14 r (nor) s 13 r (did) s 14 r (we) s 13 r (want) s 13 r (to) s 14 r (create) s 13 r 97 c 14 r (developers') s 13 r (bottle-) s 1050 1203 p (neck) s 15 r (in) s 15 r (legislating) s 16 r (the) s 15 r (possible) s 15 r (functions.) s 1096 1260 p (One) s 17 r (aspect) s 17 r (of) s 17 r (the) s 16 r (protocol) s 17 r (which) s 17 r (has) s 17 r (not) s 17 r (been) s 17 r (dis-) s 1050 1314 p (cussed) s 17 r (here) s 18 r (is) s 17 r (the) s 17 r (way) s 17 r (to) s 18 r (account) s 17 r (for) s 17 r (the) s 18 r (time) s 17 r (uncer-) s 1050 1368 p (tainty) s 22 r (among) s 22 r (network) s 22 r (clocks) s 22 r (\(clock) s 22 r (accuracy\).) s 41 r (The) s 1050 1422 p (clock) s 12 r (accuracy) s 13 r (determines) s 12 r (the) s 13 r (accuracy) s 12 r (of) s 12 r (the) s 13 r (synchro-) s 1050 1476 p (nization) s 17 r (service.) s 27 r (In) s 18 r (its) s 17 r (time) s 18 r (calculations,) s 18 r (the) s 17 r (protocol) s 1050 1530 p (includes) s t-ita.330 @sf 13 r (guar) s -1 r 100 c t-rom.330 @sf 12 r (intervals) s 13 r (equal) s 13 r (to) s 13 r (the) s 13 r (maximum) s 13 r (observ-) s 1050 1584 p (able) s 14 r (clock) s 14 r (deviation) s 15 r (in) s 14 r (the) s 14 r (system,) s 15 r (so) s 14 r (that) s 14 r (the) s 14 r (protocol) s 1050 1638 p (can) s 22 r (tolerate) s 22 r 97 c 23 r (worst-case) s 22 r (time) s 22 r (uncertainty) s 22 r (in) s 23 r (its) s 22 r (op-) s 1050 1692 p (eration) s 20 r (\(e.g.) s 33 r 97 c 20 r (few) s 20 r (milliseconds) s 19 r 91 c 0 r (12) s 0 r (]\).) s 34 r 87 c -3 r 101 c 19 r (have) s 20 r (not) s 1050 1746 p (included) s 15 r (details) s 15 r (to) s 16 r (simplify) s 15 r (the) s 15 r (protocol) s 15 r (description.) s 1096 1804 p (Besides) s 13 r (client) s 14 r (needs,) s 13 r (we) s 14 r (must) s 13 r (consider) s 14 r (issues) s 13 r (of) s 14 r (im-) s 1050 1858 p (plementation.) s 31 r (The) s 18 r (protocol) s 19 r (has) s 19 r (several) s 19 r (asynchronous) s 1050 1912 p (threads) s 15 r (of) s 14 r (events,) s 15 r (like) s 15 r (period) s 15 r (timing,) s 14 r (message) s 15 r (arrivals,) s 1050 1966 p (and) s 22 r (data) s 22 r (arrivals.) s 41 r 65 c 23 r (multithreading) s 22 r (implementation,) s 1050 2020 p (with) s 12 r (\(virtually\)) s 11 r (independent) s 12 r (scheduling) s 12 r (for) s 11 r (each) s 12 r (thread,) s 1050 2074 p (is) s 21 r 97 c 22 r (simpler) s 21 r (approach) s 22 r (than) s 21 r 97 c 22 r (single-threading) s 21 r (imple-) s 1050 2128 p (mentation.) s 31 r 84 c -2 r 111 c 17 r (assist) s 19 r (the) s 19 r (client) s 19 r (in) s 18 r (verifying) s 19 r (data) s 19 r (con-) s 1050 2182 p (sistency) s 14 r (across) s 14 r (the) s 15 r (distributed) s 14 r (application,) s 14 r (the) s 14 r (protocol) s 1050 2236 p (provides) s 17 r (the) s 17 r (two) s 17 r (veri\014cation) s 18 r (keys) s 17 r (in) s 17 r (the) s 17 r (control) s 17 r (mes-) s 1050 2290 p (sages) s 18 r (explained) s 17 r (in) s 18 r (Section) s 17 r (2,) s 18 r (plus) s 18 r (further) s 17 r (consistency) s 1050 2344 p (checks) s 21 r (for) s 21 r (messages.) s 37 r (Our) s 21 r (speci\014cation) s 20 r (for) s 21 r (transport) s 1050 2398 p (of) s 16 r (messages) s 17 r (and) s 16 r (data,) s 17 r (needed) s 16 r (for) s 16 r (interoperability) s -2 r 44 c 16 r (iso-) s 1050 2452 p (lates) s 15 r (transport) s 14 r (functions) s 15 r (from) s 15 r (other) s 14 r (protocol) s 15 r (functions,) s 1050 2506 p (so) s 16 r (that) s 16 r (other) s 16 r (transport) s 16 r (requirements) s 17 r (can) s 16 r (lead) s 16 r (to) s 16 r 97 c 16 r (new) s 1050 2560 p (protocol) s 18 r (version) s 19 r (with) s 18 r (minimal) s 18 r (disruption.) s 29 r (One) s 19 r (major) s 1050 2614 p (simpli\014cation) s 13 r (follows) s 14 r (if) s 13 r (the) s 14 r (implementation) s 13 r (can) s 14 r (use) s 13 r (an) s 964 2738 p (1385) s @eop 6 @bop0 6 @bop1 t-rom.330 @sf -119 -44 p (of) s -1 r (f-the-shelf) s 20 r (protocol) s 21 r (for) s 21 r (reliable) s 21 r (transport) s 21 r (multicast-) s -119 9 p (ing.) s 22 r (At) s 16 r (least) s 16 r (one) s 16 r (such) s 16 r (protocol) s 16 r (has) s 16 r (been) s 16 r (proposed) s 16 r (for) s -119 63 p (the) s 14 r (Internet) s 15 r 91 c 0 r (17) s 0 r (].) s -73 121 p 84 c -4 r 111 c 15 r (place) s 15 r (the) s 15 r (protocol) s 15 r (in) s 15 r (context,) s 16 r (we) s 15 r (can) s 15 r (brie\015y) s 15 r (dis-) s -119 175 p (cuss) s 10 r (examples) s 10 r (from) s 11 r (two) s 10 r (families) s 11 r (of) s 10 r (applications:) s 18 r (multi-) s -119 229 p (media) s 14 r (communications) s 14 r (and) s 15 r (distributed) s 15 r (computing.) s 20 r 87 c -3 r 101 c -119 283 p (are) s 10 r (currently) s 10 r (implementing) s 11 r (the) s 10 r (protocol) s 11 r (in) s 10 r 97 c 11 r (multimedia) s -119 337 p (conferencing) s 15 r (architecture,) s 17 r (at) s 17 r (the) s 16 r (level) s 17 r (of) s 16 r (video,) s 17 r (voice,) s -119 391 p (and) s 15 r (data) s 16 r (transport) s 16 r (protocols) s 16 r 91 c 0 r (14) s 0 r (],) s 16 r 91 c 0 r 52 c 0 r (],) s 16 r 91 c 0 r (15) s 0 r (],) s 17 r (and) s 16 r (below) s -119 445 p (the) s 11 r (multimedia) s 13 r (conference) s 12 r (control) s 13 r (program) s 12 r 91 c 0 r 57 c 0 r 93 c 13 r (char) s 0 r (ged) s -119 499 p (with) s 13 r (orchestrating) s 14 r (the) s 14 r (whole) s 14 r (session.) s 19 r (The) s 14 r (protocol) s 14 r (can) s -119 553 p (also) s 16 r (be) s 17 r (used) s 17 r (to) s 17 r (synchronize) s 17 r (multiple-media) s 18 r (data) s 17 r (from) s -119 607 p (distributed) s 14 r (databases.) s 20 r 65 c 15 r (scheduling) s 15 r (algorithm,) s 14 r (like) s 15 r (the) s -119 661 p (one) s 17 r (presented) s 17 r (in) s 18 r 91 c 0 r (18) s 0 r 93 c 17 r (using) s 18 r (Petri) s 17 r (Nets,) s 19 r (can) s 17 r (determine) s -119 715 p (the) s 10 r (relative) s 12 r (time) s 11 r (alignment) s 11 r (of) s 11 r (packet-like) s 12 r (or) s 11 r (stream-like) s -119 769 p (multimedia) s t-ita.330 @sf 12 r (objects) s t-rom.330 @sf 13 r (across) s 14 r (the) s 13 r (databases,) s 14 r (and) s 13 r (the) s 13 r (proto-) s -119 823 p (col) s 14 r (will) s 14 r (deliver) s 15 r (this) s 14 r (schedule) s 15 r (to) s 15 r (destinations) s 14 r (across) s 15 r (the) s -119 877 p (network) s 14 r (after) s 15 r 97 c 16 r (\014xed,) s 15 r (common) s 15 r (synchronization) s 15 r (delay) s -2 r 46 c -73 934 p 65 c 15 r (second) s 17 r (family) s 17 r (of) s 17 r (applications) s 16 r (is) s 17 r (distributed) s 17 r (com-) s -119 988 p (puting.) s 27 r (Consider) s 18 r (\014rst) s t-ita.330 @sf 18 r (data) s 17 r (fusion) s t-rom.330 @sf 0 r 46 c 28 r (In) s 18 r 97 c 18 r (typical) s 18 r (archi-) s -119 1042 p (tecture,) s 12 r (data) s 11 r (travels) s 12 r (from) s 12 r (distributed) s 12 r (sensors) s 12 r (to) s 12 r 97 c 11 r (digital) s -119 1096 p (signal) s 16 r (processor) s -1 r 44 c 17 r (which) s 17 r (correlates) s 17 r (this) s 17 r (information) s 17 r (for) s -119 1150 p (detection) s 21 r (or) s 22 r (tracking.) s 39 r (Several) s 22 r (such) s 22 r (sensor) s 0 r (-processor) s -119 1204 p (ensembles) s 18 r (send) s 19 r (detection) s 19 r (and) s 19 r (tracking) s 19 r (data) s 19 r (to) s 20 r 97 c 19 r (cen-) s -119 1258 p (tral) s 13 r (fusion) s 15 r (process) s 14 r (that) s 14 r (interprets) s 15 r (all) s 14 r (data) s 14 r (collected) s 15 r (and) s -119 1312 p (makes) s 20 r (control) s 20 r (decisions.) s 36 r (The) s 21 r (synchronization) s 20 r (proto-) s -119 1366 p (col) s 23 r (can) s 24 r (provide) s 24 r (synchronization) s 24 r (of) s 24 r (sensor) s 24 r (data) s 24 r (into) s -119 1420 p (the) s 18 r (signal) s 19 r (processors,) s 19 r (and) s 19 r (also) s 19 r (of) s 19 r (processor) s 19 r (data) s 18 r (into) s -119 1474 p (the) s 20 r (fusion) s 21 r (process.) s 38 r (The) s 21 r (accuracy) s 21 r (of) s 21 r (network) s 21 r (clocks) s -119 1528 p (will) s 17 r (determine) s 19 r (which) s 18 r (fusion) s 19 r (applications) s 18 r (are) s 19 r (feasible.) s -119 1582 p 87 c -4 r 101 c 13 r (are) s 14 r (also) s 14 r (considering) s 14 r (using) s 13 r (the) s 14 r (protocol) s 14 r (in) s 14 r (network-) s -119 1636 p (distributed) s t-ita.330 @sf 20 r (parallel) s 21 r (computations) s t-rom.330 @sf 21 r (for) s 21 r (computationally) s -119 1690 p (intensive) s 16 r (models) s 17 r (\(e.g.,) s 18 r (global) s 17 r (climate) s 17 r (models\).) s 26 r (While) s -119 1744 p (exact) s 15 r (synchronization) s 16 r (of) s 16 r (data) s 17 r (across) s 16 r (participating) s 16 r (pro-) s -119 1798 p (cesses) s 19 r (is) s 21 r (undesirable) s 20 r (in) s 20 r (these) s 21 r (models) s 20 r 91 c 0 r 53 c 0 r (],) s 22 r (loose) s 20 r (syn-) s -119 1852 p (chronization) s 15 r (is) s 16 r (often) s 17 r 97 c 16 r (necessity) s 16 r 91 c 0 r (16) s 0 r (];) s 16 r 97 c 17 r (service) s 16 r (which) s -119 1906 p (can) s 14 r (be) s 15 r (provided) s 16 r (by) s 15 r (our) s 15 r (protocol) s 15 r 91 c 0 r 51 c 0 r (].) s t-bol.420 @sf -119 2073 p 54 c 57 r (Conclusion) s t-rom.330 @sf -119 2182 p (The) s 21 r (main) s 21 r (contributions) s 22 r (of) s 21 r (our) s 22 r (protocol) s 22 r (are) s 21 r (the) s 22 r (con-) s -119 2236 p (cepts) s 13 r (of) s 15 r (an) s 14 r (adaptive) s 15 r (synchronization) s 14 r (delay) s -2 r 44 c 14 r (of) s 14 r (multiple) s -119 2290 p (synchronization) s 22 r (groups,) s 26 r (and) s 23 r (of) s 23 r (modular) s 23 r (application-) s -119 2344 p (oriented) s 18 r (functions.) s 33 r (The) s 19 r (ideas) s 19 r (of) s 19 r (end-to-end) s 20 r (synchro-) s -119 2398 p (nization) s 21 r (and) s 22 r (of) s 21 r (exploiting) s 22 r (network) s 22 r (clocks) s 22 r (is) s 22 r (already) s -119 2452 p (present) s 18 r (in) s 18 r (the) s 19 r (literature,) s 20 r (but) s 18 r (we) s 19 r (have) s 19 r (re\014ned) s 18 r (the) s 19 r (\014rst) s -119 2506 p (by) s 10 r (explicitly) s 12 r (introducing) s 11 r (collection) s 11 r (and) s 11 r (delivery) s 12 r (delays,) s -119 2560 p (and) s 11 r (the) s 12 r (second) s 12 r (by) s 12 r (using) s 11 r (clock) s 12 r (time) s 12 r (to) s 12 r (coordinate) s 12 r (proto-) s -119 2614 p (col) s 15 r (operation.) s 24 r 87 c -3 r 101 c 15 r (believe) s 17 r (that) s 16 r (the) s 16 r (modularity) s 16 r (of) s 17 r (mes-) s 1050 -44 p (sage) s 15 r (and) s 15 r (data) s 16 r (transport) s 15 r (will) s 15 r (also) s 15 r (prove) s 16 r (important.) s 1096 9 p 87 c -3 r 101 c 13 r (have) s 15 r (produced) s 14 r 97 c 14 r (speci\014cations) s 15 r (document) s 14 r (for) s 14 r (the) s 1050 63 p (protocol) s 18 r (and) s 18 r (an) s 18 r (object-oriented-language) s 17 r (implementa-) s 1050 117 p (tion) s 17 r (\(C++\).) s 25 r 87 c -3 r 101 c 16 r (are) s 17 r (beginning) s 16 r (to) s 17 r (test) s 17 r (the) s 17 r (protocol) s 17 r (op-) s 1050 171 p (eration) s 17 r (and) s 17 r (services,) s 17 r (\014rst) s 17 r (on) s 17 r 97 c 17 r (single) s 16 r (site) s 17 r (and) s 17 r (next) s 17 r (on) s 1050 225 p (the) s 17 r (nation-wide) s 16 r (Dartnet) s 17 r (\(Darpa') s -2 r 115 c 16 r (research) s 16 r (testbed) s 17 r (net-) s 1050 279 p (work\).) s 20 r 87 c -3 r 101 c 14 r (are) s 15 r (participating) s 15 r (in) s 14 r (the) s 15 r (Audio/V) s -2 r (ideo) s 14 r 84 c 0 r (rans-) s 1050 333 p (port) s 20 r (working) s 21 r (group) s 20 r (of) s 21 r (the) s 20 r (Internet) s 21 r (Engineering) s 20 r 84 c -2 r (ask) s 1050 387 p (Force) s 17 r (\(IETF\)) s 18 r (to) s 17 r (facilitate) s 18 r (interoperability) s 17 r (between) s 17 r (the) s 1050 441 p (experimental) s 21 r (protocol) s 22 r (architecture) s 21 r (being) s 22 r (produced) s 21 r (in) s 1050 495 p (that) s 17 r (group) s 18 r (and) s 17 r (the) s 18 r (synchronization) s 17 r (protocol) s 17 r (speci\014ca-) s 1050 549 p (tions) s 15 r (and) s 15 r (implementation.) s t-bol.420 @sf 1050 693 p (Refer) s 0 r (ences) s t-rom.330 @sf 1073 794 p ([1]) s 23 r (A.) s 20 r (J.) s 21 r (Herbert,) s 22 r (J.) s 21 r (Monk,) s 22 r (eds.) s t-ita.330 @sf 36 r (The) s 21 r (ANSA) s 21 r (Refer) s 0 r 45 c 1149 848 p (ence) s 21 r (Manual) s 21 r (\(Release) s 20 r (00.03,) s 23 r (Draft\)) s t-rom.330 @sf 0 r 46 c 36 r 84 c -2 r (echnical) s 1149 902 p (Report,) s 19 r (Advanced) s 18 r (Networked) s 18 r (Systems) s 18 r (Architec-) s 1149 956 p (ture,) s 15 r (Cambridge,) s 15 r (England,) s 16 r (June) s 15 r (1987.) s 1073 1041 p ([2]) s 23 r (A.) s 23 r (R.) s 24 r (Guesella,) s 26 r (A.) s 24 r (S.) s 23 r (Zatti.) s 46 r (The) s 23 r (accuracy) s 24 r (of) s 1149 1095 p (the) s 19 r (clock) s 20 r (synchronization) s 19 r (achieved) s 20 r (by) s 19 r (tempo) s 20 r (in) s 1149 1149 p (berkeley) s 17 r (unix) s 17 r (4.3bsd.) s t-ita.330 @sf 25 r (IEEE) s 17 r 84 c -2 r (rans.) s 16 r (Softwar) s 0 r 101 c 15 r (En-) s 1149 1203 p (gineering) s t-rom.330 @sf 0 r 44 c 15 r (15\(7\):847{853,) s 15 r (July) s 16 r (1989.) s 1073 1289 p ([3]) s 23 r (A.Boulanger) s -1 r 44 c 22 r (J.Escobar.) s 38 r (Loosely) s 21 r (coupled) s 22 r (envi-) s 1149 1343 p (ronmental) s 10 r (models.) s t-ita.330 @sf 13 r (Earth) s 10 r (and) s 11 r (Space) s 10 r (Science) s 11 r (Infor-) s 1149 1397 p (mation) s 20 r (Systems) s 20 r (confer) s 0 r (ence) s t-rom.330 @sf 0 r 44 c 20 r (Pasadena,) s 22 r (CA,) s 20 r (Feb.) s 1149 1451 p (1992.) s 1073 1537 p ([4]) s 23 r (Danny) s 19 r (Cohen.) s t-ita.330 @sf 32 r 65 c 19 r (Network) s 19 r 86 c -4 r (oice) s 18 r (Pr) s -1 r (otocol) s 18 r (NVP-) s 1149 1591 p (II) s t-rom.330 @sf 0 r 46 c 32 r 84 c -3 r (echnical) s 19 r (Report,) s 20 r (USC/ISI,) s 19 r (Marina) s 19 r (del) s 19 r (Rey) s -2 r 44 c 1149 1645 p (California,) s 15 r (April) s 15 r (1981.) s 1073 1731 p ([5]) s 23 r (D.Bertsekas,) s 13 r (J.T) s -2 r (sitsiklis.) s t-ita.330 @sf 16 r (Parallel) s 13 r (and) s 13 r (Distributed) s 1149 1785 p (Computation:) s 33 r (Mathematical) s 22 r (Methods) s t-rom.330 @sf 0 r 46 c 40 r (Prentice) s 1149 1839 p (Hall,) s 15 r (Inc.,) s 15 r (1st) s 16 r (edition,) s 15 r (1989.) s 1073 1924 p ([6]) s 23 r (D.Bertsekas,) s 12 r (R.Gallager.) s t-ita.330 @sf 14 r (Data) s 12 r (Networks) s t-rom.330 @sf 0 r 46 c 14 r (Prentice) s 1149 1978 p (Hall,) s 15 r (Inc.,) s 15 r (1st) s 16 r (edition,) s 15 r (1987.) s 1073 2064 p ([7]) s 23 r (D.Comer.) s t-ita.330 @sf 29 r (Internetworking) s 18 r (with) s 18 r (TCP/IP:) s 19 r (Princi-) s 1149 2118 p (ples,) s 19 r (Pr) s -1 r (otocols,) s 18 r (and) s 19 r (Ar) s -1 r (chitectur) s -2 r 101 c t-rom.330 @sf 0 r 46 c 29 r (Prentice) s 18 r (Hall,) s 1149 2172 p (Inc.,) s 15 r (1st) s 15 r (edition,) s 16 r (1988.) s 1073 2258 p ([8]) s 23 r (D.P) s -4 r (.Anderson,) s 13 r (G.Homsy.) s 18 r 65 c 14 r (continuous) s 15 r (media) s 14 r (i/o) s 1149 2312 p (server) s 16 r (and) s 17 r (its) s 17 r (synchronization) s 16 r (mechanism.) s t-ita.330 @sf 24 r (IEEE) s 1149 2366 p (Computer) s t-rom.330 @sf 0 r 44 c 15 r (24\(10\):51{57,) s 15 r (Oct.) s 16 r (1991.) s 1073 2452 p ([9]) s 23 r (E.M.Schooler) s -1 r 44 c 30 r (S.L.Casner.) s t-ita.330 @sf 57 r 65 c 28 r (Packet-switched) s 1149 2506 p (Multimedia) s 18 r (Confer) s -1 r (encing) s 17 r (System) s t-rom.330 @sf 0 r 46 c 29 r 84 c -2 r (echnical) s 17 r (Re-) s 1149 2560 p (port,) s 23 r (Information) s 21 r (Sciences) s 21 r (Institute,) s 23 r (Marina) s 21 r (del) s 1149 2614 p (Rey) s -2 r 44 c 14 r (CA,) s 15 r (July) s 16 r (1991.) s 964 2738 p (1386) s @eop 7 @bop0 7 @bop1 t-rom.330 @sf -119 -44 p ([10]) s 22 r 70 c -3 r (.Cristian.) s 48 r (Probabilistic) s 25 r (clock) s 25 r (synchronization.) s t-ita.330 @sf -20 9 p (Distributed) s 14 r (Computing) s t-rom.330 @sf 0 r 44 c 15 r (1989\(3\):146{158.) s -117 100 p ([1) s -2 r (1]) s 22 r (G.Barberis) s 11 r (and) s 12 r (D.Pazzaglia.) s 14 r (Analysis) s 11 r (and) s 12 r (optimal) s -20 154 p (design) s 20 r (of) s 20 r 97 c 21 r (packet-voice) s 21 r (receiver) s -2 r 46 c t-ita.330 @sf 36 r (IEEE) s 20 r 84 c -1 r (rans.) s -20 208 p (Commun.) s t-rom.330 @sf 0 r 44 c 14 r (COM-28\(2\):217{227,) s 15 r (Feb.) s 16 r (1980.) s -119 300 p ([12]) s 22 r (David) s 19 r (Mills.) s 32 r (Internet) s 20 r (time) s 19 r (synchronization:) s 28 r (the) s -20 354 p (network) s 15 r (protocol.) s t-ita.330 @sf 22 r (IEEE) s 16 r 84 c -1 r (rans.) s 15 r (Commun.) s t-rom.330 @sf 0 r 44 c 16 r (COM-) s -20 408 p (39\(10\):1482{1493,) s 14 r (Oct.) s 15 r (1991.) s -119 499 p ([13]) s 22 r (Cosmos) s 30 r (Nicolaou.) s 66 r (An) s 30 r (architecture) s 30 r (for) s 31 r (real-) s -20 553 p (time) s 19 r (multimedia) s 19 r (communication) s 20 r (systems.) s t-ita.330 @sf 34 r (IEEE) s -20 607 p (Journal) s 26 r (on) s 28 r (Selected) s 28 r (Ar) s -1 r (eas) s 26 r (in) s 28 r (Communication) s t-rom.330 @sf 0 r 44 c -20 661 p (8\(3\):391{400,) s 14 r (April) s 15 r (1990.) s -119 752 p ([14]) s 22 r (Randy) s 23 r (Cole.) s t-ita.330 @sf 43 r (PVP) s 23 r 45 c 23 r 65 c 23 r (Packet) s 22 r 86 c -2 r (ideo) s 22 r (Pr) s -1 r (otocol) s t-rom.330 @sf 0 r 46 c -20 806 p 84 c -3 r (echnical) s 14 r (Report,) s 15 r (USC/ISI,) s 15 r (Marina) s 16 r (del) s 15 r (Rey) s -2 r 44 c 14 r (Cal-) s -20 860 p (ifornia,) s 14 r (August) s 15 r (1981.) s -119 952 p ([15]) s 22 r (R.H.Thomas,) s 87 r (H.C.Forsdick,) s 88 r 84 c -2 r (.R.Crowley) s -3 r 44 c -20 1006 p (R.W) s -4 r (.Schaaf,) s 83 r (R.S.T) s -2 r (omlinson,) s 83 r 86 c -5 r (.M.T) s -1 r (ravers,) s -20 1060 p (G.G.Robertson.) s 18 r (Diamond:) s 20 r 97 c 14 r (multimedia) s 14 r (message) s -20 1114 p (system) s 18 r (built) s 18 r (on) s 19 r 97 c 18 r (distributed) s 19 r (architecture.) s t-ita.330 @sf 30 r (IEEE) s -20 1168 p (Computer) s t-rom.330 @sf 0 r 44 c 14 r (12\(18\):65{77,) s 15 r (Dec.) s 16 r (1985.) s -119 1259 p ([16]) s 22 r (R.Peierls,) s 23 r 80 c -4 r (.Michael,) s 23 r (R.Marr.) s t-ita.330 @sf 40 r (Loosely) s 22 r (Coupled) s -20 1313 p (Distributed) s 11 r (Modeling) s 13 r (of) s 12 r (Climate) s 13 r (Change) s t-rom.330 @sf 0 r 46 c 16 r 84 c -3 r (echni-) s -20 1367 p (cal) s 13 r (Report,) s 14 r (Brookhaven) s 13 r (National) s 14 r (Laboratory) s -2 r 44 c 13 r (Au-) s -20 1421 p (gust) s 14 r (1991.) s -119 1513 p ([17]) s 22 r (S.Armstrong,A.Freier) s -1 r (,K.Marzullo.) s t-ita.330 @sf 115 r (Multicast) s -20 1567 p 84 c -3 r (ransport) s 21 r (Pr) s 0 r (otocol) s 20 r (\(RFC-1301\)) s t-rom.330 @sf 0 r 46 c 40 r 84 c -2 r (echnical) s 21 r (Re-) s -20 1621 p (port,) s 24 r (Network) s 22 r 87 c -2 r (orking) s 21 r (Group,) s 25 r (Xerox) s 23 r 87 c -3 r (ebster) s -2 r 44 c -20 1675 p (Apple) s 14 r (Computer) s -1 r 44 c 15 r (Cornell) s 15 r (University) s -2 r 44 c 14 r (Feb.) s 15 r (1992.) s -119 1766 p ([18]) s 22 r 84 c -3 r (.Little,) s 17 r (A.Ghafoor.) s 27 r (Multimedia) s 18 r (synchronization) s -20 1820 p (protocols) s 11 r (for) s 13 r (broadband) s 12 r (integrated) s 12 r (services.) s t-ita.330 @sf 16 r (IEEE) s -20 1874 p (Jour) s -5 r 46 c 26 r (Select.) s 28 r (Ar) s -1 r (eas) s 26 r (Commun.) s t-rom.330 @sf 0 r 44 c 31 r (9\(9\):1368{1382,) s -20 1928 p (Dec.) s 14 r (1991.) s -119 2019 p ([19]) s 22 r 84 c -3 r (.Little,) s 14 r (A.Ghafoor.) s 18 r (Spatio-temporal) s 14 r (composition) s -20 2073 p (of) s 14 r (distributed) s 14 r (multimedia) s 15 r (objects) s 15 r (for) s 15 r (value-added) s -20 2127 p (networks.) s t-ita.330 @sf 40 r (IEEE) s 23 r (Computer) s t-rom.330 @sf 0 r 44 c 24 r (24\(10\):42{50,) s 24 r (Oct.) s -20 2181 p (1991.) s -119 2273 p ([20]) s 22 r 84 c -3 r (.Little,) s 15 r (A.Ghafoor.) s 23 r (Synchronization) s 15 r (and) s 16 r (storage) s -20 2327 p (models) s 11 r (for) s 13 r (multimedia) s 12 r (objects.) s t-ita.330 @sf 16 r (IEEE) s 12 r (Jour) s -4 r 46 c 12 r (Select.) s -20 2381 p (Ar) s -2 r (eas) s 14 r (Commun.) s t-rom.330 @sf 0 r 44 c 16 r (8\(3\):413{427,) s 15 r (Apr) s -2 r 46 c 15 r (1990.) s -119 2472 p ([21]) s 22 r 86 c -4 r (an) s 12 r (Jacobson.) s 18 r (Congestion) s 13 r (avoidance) s 14 r (and) s 13 r (control.) s t-ita.330 @sf -20 2526 p (ACM) s t-rom.330 @sf 0 r 44 c 14 r (18\(4\):314{329,) s 15 r (Aug.) s 16 r (1988.) s 964 2738 p (1387) s @eop @end From rem-conf-request@es.net Mon Nov 15 16:23:02 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <10664-0@osi-east.es.net>; Mon, 15 Nov 1993 13:15:41 +0000 Received: from sarapis.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA07403; Mon, 15 Nov 93 22:15:32 +0100 Message-Id: <9311152115.AA07403@sics.se> To: rem-conf@es.net Subject: vat replay through NCSA Mosaic Date: Mon, 15 Nov 1993 22:15:30 +0100 From: Anders Klemets I recorded Van Jacobsens talk at the MICE seminar earlier today and I am now making rebroadcasts of it over the Internet available on an experimental basis. To start a rebroadcast of this talk you should must get NCSA Mosaic 2.0 for X which is available from ftp.uiuc.ncsa.edu. Then open the following URL: http://www.it.kth.se/~klemets/vatplay.html This will get you a form in which you should enter your hostname and a free UDP port. Before you submit the form, you should start vat in unicast mode towards my machine, as described in the form. When you submit the form, you will get a unicast transmission of the seminar to your machine. To abort the transmission, just interrupt your vat program. It is possible to do a multicast transmission as well, but for now the TTL is limited to 16, since I have not implemented a way of detetecting whether anybody is still listening. Obviously, if nobody is listening, I'd like to stop the transmission. I have limited the system to allow for only 5 concurrent transmissions. This is highly experimental. Constructive comments are welcome. Anders From rem-conf-request@es.net Mon Nov 15 19:11:14 1993 Received: from cambium.uoregon.edu by osi-east.es.net via ESnet SMTP service id <13153-0@osi-east.es.net>; Mon, 15 Nov 1993 16:02:18 +0000 Received: from localhost (meyer@localhost) by cambium.uoregon.edu (8.6.4/8.6.4) id QAA03547; Mon, 15 Nov 1993 16:02:11 -0800 Date: Mon, 15 Nov 1993 16:02:11 -0800 From: "David M. Meyer 503/346-1747" Message-Id: <199311160002.QAA03547@cambium.uoregon.edu> To: rem-conf@es.net Subject: what is a good camera these days? We are planning to get some of the new Sun video hardware and are wondering what cameras people are using/recommending. Also, (Ron) does anyone have a NV port for this? Thanks, Dave David M. Meyer Voice: 503/346-1747 Senior Network Engineer Pager: 503/342-9458 Office of University Computing FAX: 503/346-4397 Computing Center Internet: meyer@ns.uoregon.edu University of Oregon 1225 Kincaid Eugene, OR 97403 From rem-conf-request@es.net Tue Nov 16 11:38:36 1993 Received: from SGI.COM by osi-east.es.net via ESnet SMTP service id <18491-0@osi-east.es.net>; Tue, 16 Nov 1993 08:23:12 +0000 Received: from relay.sgi.com by sgi.sgi.com via SMTP (931106.SGI.IRIX4/910110.SGI) for rem-conf@es.net id AA19929; Tue, 16 Nov 93 08:23:08 -0800 Received: from shire.corp.sgi.com by relay.sgi.com via SMTP (920330.SGI/920502.SGI) for @sgi.sgi.com:rem-conf@es.net id AA29120; Tue, 16 Nov 93 08:23:07 -0800 Received: by shire.corp.sgi.com (930416.SGI/911001.SGI) for @sgi.com:rem-conf@es.net id AA23188; Tue, 16 Nov 93 08:23:06 -0800 From: trant@shire.corp.sgi.com (Ken Trant) Message-Id: <9311160823.ZM23186@shire.corp.sgi.com> Date: Tue, 16 Nov 1993 08:23:05 -0800 X-Mailer: Z-Mail-SGI (3.0S.1023 23oct93 MediaMail) To: rem-conf@es.net Cc: ian@mti.sgi.com, arc@esd.sgi.com Subject: Multicast Bay-LISA meeting (Sendmail V8) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 This is to inform you of my intention to mcast to the Internet our local Bay-LISA (Bay Area Large Installation System Administration) meeting. We will be hosting Eric Allman for a lecture on Sendmail V8. The informaion on the mcast are as follows. Date: 11/18/93 Time: 7:30pm PST (approx) Speaker: Eric Allman Subject: Sendmail V8 If anyone has any interest/objections please feel free to contact me at trant@sgi.com before the event. Thanks, Ken Trant -- ----- Ken Trant / I think that I shall never see Senior Systems Administrator / A billboard lovely as a tree Information Services, / Indeed, unless the billboards fall Silicon Graphics, Inc / I'll never see a tree at all From rem-conf-request@es.net Tue Nov 16 13:40:42 1993 Received: from alpha.Xerox.COM by osi-east.es.net via ESnet SMTP service id <20029-0@osi-east.es.net>; Tue, 16 Nov 1993 10:28:01 +0000 Received: from ecco.parc.xerox.com ([13.2.116.196]) by alpha.xerox.com with SMTP id <11782(1)>; Tue, 16 Nov 1993 10:27:42 PST Received: by ecco.parc.xerox.com id <16139>; Tue, 16 Nov 1993 10:27:34 -0800 Received: from Messages.7.15.N.CUILIB.3.45.SNAP.NOT.LINKED.ecco.parc.xerox.com.sun4.41 via MS.5.6.ecco.parc.xerox.com.sun4_41; Tue, 16 Nov 1993 10:27:23 -0800 (PST) Message-ID: Date: Tue, 16 Nov 1993 10:27:23 PST Sender: Ron Frederick From: Ron Frederick To: "David M. Meyer 503/346-1747" Subject: Re: what is a good camera these days? CC: rem-conf@es.net In-Reply-To: <199311160002.QAA03547@cambium.uoregon.edu> References: <199311160002.QAA03547@cambium.uoregon.edu> > [SunVideo hardware] > Also, (Ron) does anyone have a NV port for this? There isn't yet a grabber routine for nv to get uncompressed data from the SunVideo card. From what I know about the hardware, this should be possible in some form, but I don't yet know what kind of performance we can expect from it. I've already gotten some interest in writing such a grabber, so you might want to talk to me first if you're thinking about doing it. Otherwise, it may just end up being duplicated effort... I'll try and coordinate things such that anyone with one of these cards and the appropriate developer libraries to do compiling won't have to wait until the official release to make it work... -- Ron Frederick frederick@parc.xerox.com From rem-conf-request@es.net Tue Nov 16 16:20:41 1993 Received: from Sun.COM by osi-east.es.net via ESnet SMTP service id <21828-0@osi-east.es.net>; Tue, 16 Nov 1993 13:02:08 +0000 Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (4.1/SMI-4.1) id AA24017; Tue, 16 Nov 93 13:01:59 PST Received: from kaos.Eng.Sun.COM (control) by Eng.Sun.COM (4.1/SMI-4.1) id AA11975; Tue, 16 Nov 93 13:01:16 PST Received: from gday.Eng.Sun.COM by kaos.Eng.Sun.COM (5.0/SMI-SVR4) id AA06035; Tue, 16 Nov 1993 13:01:48 +0800 Received: from gday (localhost) by gday.Eng.Sun.COM (5.0/SMI-SVR4) id AA02516; Tue, 16 Nov 1993 13:02:09 +0800 Message-Id: <9311162102.AA02516@gday.Eng.Sun.COM> To: Ron Frederick , "David M. Meyer 503/346-1747" Cc: rem-conf@es.net Subject: NV on SunVideo [was Re: what is a good camera these days?] In-Reply-To: Your message of "Tue, 16 Nov 1993 10:27:23 PST." Date: Tue, 16 Nov 1993 13:02:08 -0800 From: Thomas Maslen Content-Length: 549 I've been hacking on a version of this (NV using the XIL library to grab uncompressed frames from SunVideo). It seems to work, but there's rather more latency than there ought to be (compared with other versions of NV or with other XIL programs that use SunVideo); I was planning not to inflict the bits on Ron until I'd got to the bottom of it. I believe there's already a version that grabs CellB-compressed frames, but 'tain't the same as NV's very own compression format. Thomas Maslen (Most definitely not an XIL guru) maslen@eng.sun.com From rem-conf-request@es.net Tue Nov 16 20:32:24 1993 Received: from mothra.nts.uci.edu by osi-east.es.net via ESnet SMTP service id <25095-0@osi-east.es.net>; Tue, 16 Nov 1993 17:19:54 +0000 Received: by mothra.nts.uci.edu id AA07563 (5.65c/IDA-1.4.4 for rem-conf@es.net); Tue, 16 Nov 1993 17:19:53 -0800 Received: from [128.200.132.104] (godzilla.nts.uci.edu) by mothra.nts.uci.edu with SMTP id AA07521 (5.65c/IDA-1.4.4 for rem-conf@es.net); Tue, 16 Nov 1993 17:19:23 -0800 Message-Id: <199311170119.AA07521@mothra.nts.uci.edu> X-Sender: dhwalker@mothra.nts.uci.edu (Unverified) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 16 Nov 1993 17:19:30 -0800 To: Thomas Maslen , Ron Frederick , "David M. Meyer 503/346-1747" From: David Walker Subject: Re: NV on SunVideo [was Re: what is a good camera these days?] Cc: rem-conf@es.net Is there a standard API for frame grabber drivers? Is that what XIL is? It strikes me that we may be heading in the direction of where Ethernet cards on DOS systems were a few years ago. It would be unfortunate if every application had to have its own sets of drivers for every video card it supported. David Walker (Even less of an XIL guru) At 1:02 PM 11/16/93 -0800, Thomas Maslen wrote: >I've been hacking on a version of this (NV using the XIL library to >grab uncompressed frames from SunVideo). It seems to work, but >there's rather more latency than there ought to be (compared with >other versions of NV or with other XIL programs that use SunVideo); I >was planning not to inflict the bits on Ron until I'd got to the >bottom of it. I believe there's already a version that grabs >CellB-compressed frames, but 'tain't the same as NV's very own >compression format. > >Thomas Maslen (Most definitely not an XIL guru) >maslen@eng.sun.com From rem-conf-request@es.net Wed Nov 17 16:53:40 1993 Received: from rx7.ee.lbl.gov by osi-east.es.net via ESnet SMTP service id <03978-0@osi-east.es.net>; Wed, 17 Nov 1993 13:52:50 +0000 Received: by rx7.ee.lbl.gov for rem-conf@es.net (5.65/1.44r) id AA01181; Wed, 17 Nov 93 13:52:54 -0800 Message-Id: <9311172152.AA01181@rx7.ee.lbl.gov> To: rem-conf@es.net Subject: Re: vat replay through NCSA Mosaic In-Reply-To: Your message of Mon, 15 Nov 93 22:15:30 N. Date: Wed, 17 Nov 93 13:52:53 PST From: Van Jacobson If anyone listening to Ander's recording of my MICE seminar wants the associated viewgraphs, they're available for anonymous ftp from ftp.ee.lbl.gov in file vj-lwsarch.ps.Z. (But I should note that the seminar was poorly done & almost content free & you probably shouldn't waste your time on it.) - Van From rem-conf-request@es.net Wed Nov 17 22:02:43 1993 Received: from viipuri.nersc.gov by osi-east.es.net via ESnet SMTP service id <07608-0@osi-east.es.net>; Wed, 17 Nov 1993 18:53:56 +0000 Received: by viipuri.nersc.gov (4.1/ESnet-1.2) id AA00678; Wed, 17 Nov 93 18:53:50 PST Date: Wed, 17 Nov 93 18:53:50 PST From: ari@es.net (Ari Ollikainen) Message-Id: <9311180253.AA00678@viipuri.nersc.gov> To: braden@isi.edu, Bob.Hinden@eng.sun.com Subject: Re: Platforms for network research Cc: end2end-interest@isi.edu, rem-conf@es.net, rcwg@nic.hep.net > > > I have just heard that Sun has announced that on January 21, 1994 they > > will discontinue shipping Sparc 10's that will support 4.1.x; after > > that, they will only support Solaris. > > This is not true. Sun is not planning to discontinue support for 4.1.x on > Sparc 10's on 1/21/94 or anytime in the near future. Current plans call > for supporting 4.1.x on all platforms it currently runs on. > Jaaa...suuure... BUT what does "support" mean? Will there be SUPPORT for the SunVideo card in the form of the XIL in 4.1.x, for example? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ari Ollikainen ari@es.net National Energy Research Supercomputer Center ESnet (Energy Sciences Network) Lawrence Livermore National Laboratory 510-423-5962 FAX:510-423-8744 P.O. BOX 5509, MS L-561, Livermore, CA 94550 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From rem-conf-request@es.net Wed Nov 17 22:16:22 1993 Received: from whistler.cs.washington.edu by osi-east.es.net via ESnet SMTP service id <07814-0@osi-east.es.net>; Wed, 17 Nov 1993 19:15:20 +0000 Received: from localhost by whistler.cs.washington.edu (5.65b/7.1ws) id AA19278; Wed, 17 Nov 93 19:15:36 -0800 Return-Path: Message-Id: <9311180315.AA19278@whistler.cs.washington.edu> To: ari@es.net (Ari Ollikainen) Cc: braden@ISI.EDU, Bob.Hinden@eng.sun.com, end2end-interest@ISI.EDU, rem-conf@es.net, rcwg@nic.hep.net Subject: Re: Platforms for network research In-Reply-To: Your message of "Wed, 17 Nov 93 18:53:50 -0800." <9311180253.AA00678@viipuri.nersc.gov> Date: Wed, 17 Nov 93 19:15:35 -0800 From: bershad@cs.washington.edu According to our local sun sales rep, the new video hardware ( sparclcassic M and friends) will only be supported by Solaris. From rem-conf-request@es.net Thu Nov 18 04:08:33 1993 Received: from bells.cs.ucl.ac.uk by osi-east.es.net via ESnet SMTP service id <09880-0@osi-east.es.net>; Thu, 18 Nov 1993 01:07:53 +0000 Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 18 Nov 1993 09:07:27 +0000 To: Van Jacobson cc: rem-conf@es.net Subject: Re: vat replay through NCSA Mosaic In-reply-to: Your message of "Wed, 17 Nov 93 13:52:53 PST." <9311172152.AA01181@rx7.ee.lbl.gov> Date: Thu, 18 Nov 93 09:07:23 +0000 From: Jon Crowcroft >If anyone listening to Ander's recording of my MICE seminar wants >the associated viewgraphs, they're available for anonymous ftp from >ftp.ee.lbl.gov in file vj-lwsarch.ps.Z. (But I should note that >the seminar was poorly done & almost content free & you probably >shouldn't waste your time on it.) as a witness, i must disagree - until we lost vid & wb (which is not a problem if you retrieve the slides) the seminar was full of a lot of very interesting food for thought. jon From rem-conf-request@es.net Thu Nov 18 05:44:15 1993 Received: from hplb.hpl.hp.com by osi-east.es.net via ESnet SMTP service id <10242-0@osi-east.es.net>; Thu, 18 Nov 1993 02:22:09 +0000 Received: from morse.hpl.hp.com by hplb.hpl.hp.com; Thu, 18 Nov 1993 10:23:19 GMT Message-Id: <9311181023.AA19729@hplb.hpl.hp.com> To: Van Jacobson , rem-conf@es.net Cc: Jon Crowcroft Subject: Re: vat replay through NCSA Mosaic In-Reply-To: Your message of "Thu, 18 Nov 93 10:07:23 N." <"9884 Thu Nov 18 01:08:29 1993"@es.net> Date: Thu, 18 Nov 93 10:18:53 GMT From: Stephen Pink > > > >If anyone listening to Ander's recording of my MICE seminar wants > >the associated viewgraphs, they're available for anonymous ftp from > >ftp.ee.lbl.gov in file vj-lwsarch.ps.Z. (But I should note that > >the seminar was poorly done & almost content free & you probably > >shouldn't waste your time on it.) > > as a witness, i must disagree - until we lost vid & wb (which is > not a problem if you retrieve the slides) the seminar was full of a > lot of very interesting food for thought. > > jon > Van, I agree with Jon. I got a lot out of your Mice seminar and appreciate having your slides. Steve Pink From rem-conf-request@es.net Thu Nov 18 08:05:36 1993 Received: from sun2.nsfnet-relay.ac.uk by osi-east.es.net via ESnet SMTP service id <11108-0@osi-east.es.net>; Thu, 18 Nov 1993 05:04:58 +0000 Via: uk.ac.rutherford.informatics; Thu, 18 Nov 1993 12:09:07 +0000 Received: from bingo by inf.rl.ac.uk; Thu, 18 Nov 93 12:08:47 GMT Date: Thu, 18 Nov 1993 12:08:47 +0000 From: ijj@informatics.rutherford.ac.uk Message-Id: <9311181208.AA02645@bingo> To: rem-conf@es.net Subject: Re: Platforms for network research X-Sun-Charset: US-ASCII Content-Length: 1893 > From rem-conf-request@es.net Thu Nov 18 03:52:07 1993 > To: ari@es.net (Ari Ollikainen) > Cc: braden@EDU.ISI, Bob.Hinden@com.sun.eng, end2end-interest@EDU.ISI, > rem-conf@es.net, rcwg@net.hep.nic > Subject: Re: Platforms for network research > Date: Wed, 17 Nov 93 19:15:35 -0800 > From: bershad@cs.washington.edu > Sender: rem-conf-request@es.net > Content-Length: 126 > > According to our local sun sales rep, the new video hardware ( sparclcassic M > and friends) will only be supported by Solaris. > I hope that this doesn't surprise too many people: Solaris 2.X has been out for almost a year now, so it makes sense for the SunVideo device to be supported by the current operating system. I guess the quibble is that Sun are not supporting SunVideo under SunOS 4.X: I can see why they would not want to have to support two versions of device drivers etc for such a board. For those still using the VideoPix frame capture board, it's worth noting that there is an "unofficial" vfc/Solaris patch available from Sun. (This has been mentioned on this list in the past, and I'm merely repeating what others have discovered). The patch (rather a series of patches) provides a vfc device driver, Solaris versions of vfctool and libvfc.a, example programs, and an XIL pipeline library for VideoPix. These patches are available for FTP from playground.sun.com, under the directory /pub/videopix. I've been using VideoPix/vfctool on a Solaris 2.1 machine for just over a week now, with no problems (i.e. vfctool and nv 3.2 work OK). I'm upgrading this machine to 2.3 today (to get better support for multicast, among other things): if there are problems with the VideoPix support under 2.3, I'll tell the list. -- "You can't get the wood!" Ian Johnson JANET: ijj@uk.ac.rl.inf Rutherford Appleton Laboratory, UUCP: ..!mcsun!ukc!rlinf!ijj Chilton, Didcot, Oxon OX11 0QX. From rem-conf-request@es.net Thu Nov 18 15:10:00 1993 Received: from SKIGO.GRAPHICS.CORNELL.EDU by osi-east.es.net via ESnet SMTP service id <15613-0@osi-east.es.net>; Thu, 18 Nov 1993 11:57:21 +0000 Received: by skigo.graphics.cornell.edu (5.65/DEC-Ultrix/4.3) id AA19404; Thu, 18 Nov 1993 14:57:10 -0500 Message-Id: <9311181957.AA19404@skigo.graphics.cornell.edu> To: sechrest@cs.orst.edu Cc: rem-conf@es.net Subject: netiquette request for SuperComputing 93 Date: Thu, 18 Nov 93 14:57:09 -0500 From: Mitch Collinsworth X-Mts: smtp I would like to request that the SuperComputing folks limit themselves to no more than one simultaneous nv transmission tonite during the Eric Allman lecture from BAY-LISA, starting at 7:30 PST (approx). We on the east coast would greatly appreciate getting good reception for this event. Thanks in advance for your consideration. -Mitch Collinsworth From rem-conf-request@es.net Thu Nov 18 15:14:50 1993 Received: from santiam.CS.ORST.EDU by osi-east.es.net via ESnet SMTP service id <15773-0@osi-east.es.net>; Thu, 18 Nov 1993 12:03:17 +0000 Received: from trillium.CS.ORST.EDU by santiam.CS.ORST.EDU (1.37.109.4/1.15) id AA04430; Thu, 18 Nov 93 11:56:54 -0800 Message-Id: <9311181956.AA04430@santiam.CS.ORST.EDU> To: Mitch Collinsworth Cc: rem-conf@es.net Subject: Re: netiquette request for SuperComputing 93 In-Reply-To: Your message of Thu, 18 Nov 1993 14:57:09 EST. <9311181957.AA19404@skigo.graphics.cornell.edu> Date: Thu, 18 Nov 1993 12:03:39 -0800 From: (John Sechrest) sechrest -------- We will be going off the air at about 4:00 PM PST tonight. So this should not be a problem. Thanks for the request though. I hope that you are getting good things from the SC 93 sessions, I am sorry that I am going to be driving when eric is going to be talking... Mitch Collinsworth writes: > > I would like to request that the SuperComputing folks limit themselves to > no more than one simultaneous nv transmission tonite during the Eric Allman > lecture from BAY-LISA, starting at 7:30 PST (approx). We on the east coast > would greatly appreciate getting good reception for this event. Thanks in > advance for your consideration. > > -Mitch Collinsworth ----- John Sechrest . Internet: sechrest@cs.orst.edu Technical Director . Computer Science Dept . UUCP: hplabs!hp-pcd!orstcs!sechrest Oregon State University . Corvallis,Oregon 97331 . (503) 737-3273 . From rem-conf-request@es.net Thu Nov 18 16:40:20 1993 Received: from venera.isi.edu by osi-east.es.net via ESnet SMTP service id <16645-0@osi-east.es.net>; Thu, 18 Nov 1993 13:29:05 +0000 Received: from xfr.isi.edu by venera.isi.edu (5.65c/5.61+local-14) id ; Thu, 18 Nov 1993 13:28:59 -0800 Posted-Date: Thu 18 Nov 93 13:28:13 PST Received: by xfr.isi.edu (4.1/4.0.3-4) id ; Thu, 18 Nov 93 13:28:14 PST Date: Thu 18 Nov 93 13:28:13 PST From: Stephen Casner Subject: Re: netiquette request for SuperComputing 93 To: mkc@graphics.cornell.edu, sechrest@cs.orst.edu Cc: rem-conf@es.net Message-Id: <753658093.0.CASNER@XFR.ISI.EDU> In-Reply-To: <9311181957.AA19404@skigo.graphics.cornell.edu> Mail-System-Version: Let me second Mitch's request to the SuperComputing folks to send no more than one video stream tonight. I'd also like to add a request that when you are sending video, to please leave the bandwidth limit set at 128Kb/s. At the moment, I am receiving 250Kb/s of video on the "SC 93 Conference" channel, accompanied by audio that is only background noise so the video is essentially useless. The other video channel is only showing people wandering around the terminal room, so an even lower bandwidth setting would seem appropriate. -- Steve ------- From rem-conf-request@es.net Fri Nov 19 12:58:18 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <01897-0@osi-east.es.net>; Fri, 19 Nov 1993 09:46:00 +0000 Received: from krishna.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA06190; Fri, 19 Nov 93 18:45:53 +0100 Message-Id: <9311191745.AA06190@sics.se> To: rem-conf@es.net Subject: Eric Allmans seminar on line Date: Fri, 19 Nov 1993 18:45:50 +0100 From: Anders Klemets Since the remote operation of vat_play through NCSA Mosaic turned out to be quite popular, I am also making a recording of yesterdays Bay-Lisa seminar. The talk was given at SGI by Eric Allman and was about the new version of sendmail, V8.6.4. The URL for this is, as before, http://www.it.kth.se/~klemets/vatplay.html I should stress, that you do need to run the WWW-client NCSA Mosaic version 2.0 to be able to fill out the form. If you succeed in submitting the form, but still receive no audio, there are at least two possible problems. 1) You might be behind a firewall that does not accept unicast transmissions from my site, or 2) You might be running a kernel with old multicast code in it, that will not deliver the UDP packets to vat, but instead return ICMP UDP port unreachable messages. I suspect the reason for this might be that the in_pcb.o patch is missing from the kernel. Anders From rem-conf-request@es.net Fri Nov 19 13:57:01 1993 Received: from venera.isi.edu by osi-east.es.net via ESnet SMTP service id <02850-0@osi-east.es.net>; Fri, 19 Nov 1993 10:46:49 +0000 Received: from btn.isi.edu by venera.isi.edu (5.65c/5.61+local-14) id ; Fri, 19 Nov 1993 10:46:46 -0800 Date: Fri, 19 Nov 93 10:16:49 -0800 From: touch@ISI.EDU Posted-Date: Fri, 19 Nov 93 10:16:49 -0800 Message-Id: <9311191816.AA21808@btn.isi.edu> Received: by btn.isi.edu (NX5.67c/4.0.3-4) id ; Fri, 19 Nov 93 10:16:49 -0800 Original-Received: by NeXT.Mailer (1.87.1) PP-warning: Illegal Received field on preceding line Original-Received: by NeXT Mailer (1.87.1) PP-warning: Illegal Received field on preceding line To: rem-conf@es.net Subject: Tk/TCL embedder tool available Cc: touch@ISI.EDU Because of the use of Tk/TCL for user interfaces in this group, I would like to share the following information: -------------------------------------------------------------------------- tcl2array package - toolkit to help create stand-alone tk/tcl applications V1.0 Tcl2array is a package developed at the University of Southern California Information Sciences Institute, to help in the creation of stand-alone tk/tcl applications. Tcl2array is distributed as a compressed tar archive available via anonymous login from ftp.isi.edu:pub/hpcc-papers/touch/tcl2array.tar.Z (128.9.0.32). This README is in tcl2array.README and in the tar file as well. As distributed, tk/tcl is designed to be used as an installed toolkit, both for application development and application use. Users are expected to install the toolkit, either in their home directory or in a central shared directory. Applications developed in tk/tcl aren't stand-alone; they depend on dynamically-loaded auxilliary tcl files. Also, tk/tcl code is usually maintained as a separate file, rather than being integrated into the executable code main. We prefer to be able to distribute our code fully stand-alone, where a single executable code file contains the tk/tcl source as an embedded data structure, and also contains all auxilliary files. This way, our executables can be used where tk/tcl has not been installed. Here we provide an skeleton application, and a makefile and preprocessor for making embedded tk/tcl stand-alone applications. --------------------------------------------------------------------- From rem-conf-request@es.net Fri Nov 19 15:07:37 1993 Received: from sgigate.SGI.COM by osi-east.es.net via ESnet SMTP service id <03806-0@osi-east.es.net>; Fri, 19 Nov 1993 12:06:49 +0000 Received: from relay.sgi.com by sgigate.sgi.com via SMTP (920330.SGI/920502.SGI) id AA00572; Fri, 19 Nov 93 11:56:24 -0800 Received: from shire.corp.sgi.com by relay.sgi.com via SMTP (920330.SGI/920502.SGI) for @sgigate.sgi.com:baylisa@sysadmin.com id AA11354; Fri, 19 Nov 93 11:56:15 -0800 Received: by shire.corp.sgi.com (930416.SGI/911001.SGI) for @sgi.com:rem-conf@es.net id AA11701; Fri, 19 Nov 93 11:46:13 -0800 Date: Fri, 19 Nov 93 11:46:13 -0800 From: trant@shire.corp.sgi.com (Ken Trant) Message-Id: <9311191946.AA11701@shire.corp.sgi.com> To: baylisa@sysadmin.com, rem-conf@es.net Subject: Multicast of Sendmail lecture Hello & Good morning, After last nites Mcast several issues came up and some questions, so I would like to address them here instead of one by one. 1: Picture quality 2: Slide availability 3: Recording of the lecture for future rebroadcast. 4: Future broadcasts 5: Technology description. So, one at a time. #1. The meeting that was Mcast was the monthly meeting of BayLISA, a non-profit (not for profit, whats the diff?.) group that meets the third Thursday of each month to discuss issues important to System Admins. The camera belongs to one of the members and video tapes of past meetings are available to BayLISA members. SGI has made the facilities available to the group at no charge as well as some equipment, microphones, overhead, network access, and personnel to run them. However I didn't ask for access to the video equipment that is available so the picture quality was not adequate for the broadcast. Sorry, Its Kens fault. I have asked for and been given tentative approval to use this equipment for any future broadcasts. #2. As a result of the picture quality the slides used in Eric's talk last nite could not be seen (am I telling you something you don't know already? :-{ ). Eric has said the slides are available from an anonymous ftp site at Berkeley, BayLISA will put them on their anonymous ftp site as well. I'll follow up with the address for each server as I find out. #2a. In future mcasts I have asked that if possible I get a copy of any slides to be used and I will put them on the system (R3K Indigo) we use to send out the mcast. This will allow me to display the slides with the system and switch back and forth between the speaker and the slides. This will all depend on the speakers ability to get me the slides, if any, soon enough. Since the speakers donate the time it may not always be possible. #3. Two issues here, one is that the BayLISA board is concerned that access to past meetings is one of the benefits it provides to paying members and that to make those available to the network negates one of the main reasons for people to become a member. If membership drops off the meetings will stop. Second, I did plan on recording the broadcast for rebroadcast over our local net but I couldn't find adequate disk space. I'm told that one of the viewers last nite did tape the broadcast and maybe he can set up a rebroadcast once the slides are made available. One possible answer to the membership issue may be that the board can create a new type of membership, call it a Net member, whose cost reflects the lower quality of the access but could possibly help generate sufficient revenue to offset any loss caused by free access to past meetings. I think the board is correct to be concerned, thats what we don't pay them for :-), but I personally see the benefit as being the meetings themselves and not the access to past videos. If you would like to see more broadcasts like the Sendmail lecture please let me know what you think might be a possible solution and I will pass it on to the BayLISA board. #4. I currently don't know the status of future broadcasts, I would like to see them continue. Hopefully we can find a solution to the issue before next months meeting. #5. Unfortunately I wasn't prepared to discuss the technology behind the Mcast at last nites meeting, I assumed (no, don't point out the definition of that word :-} ) that if you were receiving you already knew what it was and how to access it. However some of the people attending last nites meeting were unfamiliar with what the MBONE is, what multicast packets are and what is needed to gain access to the MBONE. The following is information I gleaned from the mail.net.mbone mailing list. Maps of the MBONE exist and are available via anon ftp, as well as source and system specific patches. One such site is ftp.ee.lbl.gov. Other available info can be found: (1) Anonymous FTP - /ietf/0mtg-multicast.guide.93nov.txt on any of the IETF's shadow directories (ds.internic.net, nic.nordu.net, or munnari.oz.au). (2) Gopher - Host "ietf.cnri.reston.va.us". Path "Internet Society (includes IETF) / Internet Engineering Task Force / IETF Meetings / Houston November 1993 / Multicast Guide". I have seen references to a FAQ but no pointers to it's location. Hopefully this answers most of your questions about last nites broadcast. I hope we will be able to do this again next month, either way I will drop you a short note letting you know. Thanks for your support, Ken Trant ----- Ken Trant / I think that I shall never see Senior Systems Administrator / A billboard lovely as a tree Information Services, / Indeed, unless the billboards fall Silicon Graphics, Inc / I'll never see a tree at all From rem-conf-request@es.net Fri Nov 19 17:13:36 1993 Received: from Lehman.COM by osi-east.es.net via ESnet SMTP service id <05261-0@osi-east.es.net>; Fri, 19 Nov 1993 14:02:27 +0000 Received: from relay.lehman.com by lehman.com (8.6.4/LB 0.1) id RAA26935; Fri, 19 Nov 1993 17:02:16 -0500 Received: from kublai.lehman.com by relay.lehman.com (4.1/LB-0.6) id AA00299; Fri, 19 Nov 93 17:02:15 EST Received: from snark.lehman.com by kublai.lehman.com (4.1/SMI-4.1) id AA16380; Fri, 19 Nov 93 17:02:14 EST Date: Fri, 19 Nov 93 17:02:14 EST From: pmetzger@lehman.com (Perry E. Metzger) Message-Id: <9311192202.AA16380@kublai.lehman.com> Received: by snark.lehman.com (4.1/SMI-4.1) id AA05929; Fri, 19 Nov 93 17:02:12 EST To: rem-conf@es.net Subject: unsubscribe Reply-To: pmetzger@lehman.com X-Reposting-Policy: redistribute only with permission Please unsubscribe me -- I'm not sure if my address is pmetzger@lehman.com or perry@gnu.ai.mit.edu... Perry From rem-conf-request@es.net Fri Nov 19 17:53:56 1993 Received: from lhc.nlm.nih.gov by osi-east.es.net via ESnet SMTP service id <05793-0@osi-east.es.net>; Fri, 19 Nov 1993 14:42:48 +0000 Received: from billings.nlm.nih.gov by nlm.nih.gov (4.1/SMI-4.0) id AA25232; Fri, 19 Nov 93 17:42:39 EST Received: by billings.nlm.nih.gov (4.1/SMI-4.1) id AA01333; Fri, 19 Nov 93 17:42:37 EST Date: Fri, 19 Nov 93 17:42:37 EST From: rodgers@nlm.nih.gov (R. P. Channing ["Rick"] Rodgers) Message-Id: <9311192242.AA01333@billings.nlm.nih.gov> To: frederic@ecco.parc.Xerox.com Subject: SIGWEB mbone telecast Cc: rem-conf@es.net Dear SIGWEB Colleagues, We are enjoying the SIGWEB multicast; audio is excellent, and video is technically quite good, though the images of the workstation screens are completely illegible. Cheerio, Rick Rodgers (NLM) From rem-conf-request@es.net Fri Nov 19 18:35:42 1993 Received: from Lehman.COM by osi-east.es.net via ESnet SMTP service id <06284-0@osi-east.es.net>; Fri, 19 Nov 1993 15:24:12 +0000 Received: from relay.lehman.com by lehman.com (8.6.4/LB 0.1) id SAA27671; Fri, 19 Nov 1993 18:24:03 -0500 Received: from kublai.lehman.com by relay.lehman.com (4.1/LB-0.6) id AA02737; Fri, 19 Nov 93 18:23:59 EST Received: from snark.lehman.com by kublai.lehman.com (4.1/SMI-4.1) id AA18161; Fri, 19 Nov 93 18:23:58 EST Date: Fri, 19 Nov 93 18:23:58 EST From: pmetzger@lehman.com (Perry E. Metzger) Message-Id: <9311192323.AA18161@kublai.lehman.com> Received: by snark.lehman.com (4.1/SMI-4.1) id AA06022; Fri, 19 Nov 93 18:23:57 EST To: rem-conf@es.net Subject: Gack! Reply-To: pmetzger@lehman.com X-Reposting-Policy: redistribute only with permission Gack! After years of properly addressing my requests to -request, I act like a newbie. I am sincerely sorry! My fingers slipped while typing -- I really do normally know what I'm doing. Mea culpa, mea culpa, mea maxima culpa! Perry Perry E. Metzger says: > Please unsubscribe me -- I'm not sure if my address is > pmetzger@lehman.com or perry@gnu.ai.mit.edu... > > Perry From rem-conf-request@es.net Fri Nov 19 19:34:54 1993 Received: from optics.wc.novell.com by osi-east.es.net via ESnet SMTP service id <07264-0@osi-east.es.net>; Fri, 19 Nov 1993 16:23:27 +0000 Received: from by wc.novell.com (4.1/smi4.1.1.v91190) id AB29084; Fri, 19 Nov 93 16:20:38 PST Date: Fri, 19 Nov 93 16:20:38 PST Message-Id: <9311200020.AB29084@wc.novell.com> To: rem-conf@es.net From: minshall@wc.novell.com X-Sender: minshall@optics.wc.novell.com Subject: Re: RTP, conferences, ports and flow-ID From my memory, there has been a lot of talk about which port or ports to use for RTP. It all seemed fairly handwavy (and, i contributed my bit of handwaving!)) and, ultimately, unsatisfying. There were arguments for having all audio/video/whatever using RTP on one port. To have one for audio, one for video, one for whiteboard, etc. To have one for each set of intercommunicating programs. Etc. All of which leads me to ask myself "what is a port?", a fairly silly question, i will admit. I am going to make the claim that a "port" is, ultimately, something that leads one to enough knowledge to decode the packets. In other words, a "port" == an "RFC" (or, set thereof). And, i further claim that this is precisely how we should decide what things should be on what port. For example, if vat is, right now, using an undocumented protocol (on top of RTP, say), it should run in the "grab your own and run" port space (a bit tricky in the mcast world, it is true). If vat is, right *now*, running a certain documented protocol (on top of RTP), then it should use a port which, somehow, points to the documentation of that protocol (presumably through a base RFC, possibly the assigned numbers RFC and then another RFC). (Note that i am not claiming that "port" in the above needs to be a UDP port; there could be just *one* UDP port, then some higher level demultiplexer inside RTP.) Thoughts? Greg Minshall ps - Of course, this silly idea breaks down *fairly* soon. I use the same port to telnet to a host, regardless of whether i ultimately want to talk "unix" protocol or "VMS" protocol. From rem-conf-request@es.net Sun Nov 21 12:51:29 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <15574-0@osi-east.es.net>; Sun, 21 Nov 1993 09:37:53 +0000 Received: from anhur.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA19467; Sun, 21 Nov 93 18:37:49 +0100 Received: by anhur.sics.se (5.65+bind 1.7+ida 1.4.2/anhur-1.1) id AA19713 (for rem-conf@es.net); Sun, 21 Nov 93 18:37:48 +0100 Date: Sun, 21 Nov 93 18:37:48 +0100 From: bilting@sics.se Message-Id: <9311211737.AA19713@anhur.sics.se> To: mice-seminars@cs.ucl.ac.uk, rem-conf@es.net Subject: MICE seminar Monday Nov 22 The weekly MICE seminar is held by KTH in Stockholm on Nov 22 at 15.00 CET (=14.00 GMT) It is transmitted on the usual multicast addresses: vat 224.5.17.12/3456 ivs 224.5.17.12/2232 wb 224.5.17.12/32416 Today's topic is CoDesk - the collaborative desktop a set of generic tools for CSCW. CoDesk is an attempt to make collaboration a natural part of the daily use of a computer. Basic principles in the CoDesk interface are object orientation, direct manipulation, a box room metaphor and generic and coediting tools. Speakers are Yngve Sundblad, Hans Marmolin and Konrad Tollmar all at the department of computer science of the Royal Institute of Technology in Stockholm. From rem-conf-request@es.net Mon Nov 22 15:02:42 1993 Received: from alpha.Xerox.COM by osi-east.es.net via ESnet SMTP service id <24842-0@osi-east.es.net>; Mon, 22 Nov 1993 11:48:31 +0000 Received: from ecco.parc.xerox.com ([13.2.116.196]) by alpha.xerox.com with SMTP id <14550(2)>; Mon, 22 Nov 1993 11:48:15 PST Received: by ecco.parc.xerox.com id <16139>; Mon, 22 Nov 1993 11:48:08 -0800 Received: from Messages.7.15.N.CUILIB.3.45.SNAP.NOT.LINKED.ecco.parc.xerox.com.sun4.41 via MS.5.6.ecco.parc.xerox.com.sun4_41; Mon, 22 Nov 1993 11:48:02 -0800 (PST) Message-ID: Date: Mon, 22 Nov 1993 11:48:02 PST Sender: Ron Frederick From: Ron Frederick To: David Walker Subject: Re: NV on SunVideo [was Re: what is a good camera these days?] CC: rem-conf@es.net In-Reply-To: <199311170119.AA07521@mothra.nts.uci.edu> References: <199311170119.AA07521@mothra.nts.uci.edu> > Is there a standard API for frame grabber drivers? Is that what XIL is? > It strikes me that we may be heading in the direction of where Ethernet > cards on DOS systems were a few years ago. It would be unfortunate if > every application had to have its own sets of drivers for every video card > it supported. This is really tricky to do efficiently, though. In many respects, XIL does a pretty good job at trying to tackle this problem, but it has some serious limitations. For example, XIL chose a stream-oriented paradigm for delivering data to applications. This can be a problem when working with an application like nv that wants fine grained control over the frame rate on a moment by moment basis. In this case, _nv_ wants to choose when the system should process a frame and when it should throw frames away. The best it can do in the XIL context is to set a frame skip factor, saying to process only 1 out of every N frames. Another case where efficiency is a problem is in exactly what format the data is delivered in. For example, should "YUV capture" be YUV 4:1:1 or YUV 4:2:2? Should the greyscale & color data be interleaved, and if so on what granularity? Chances are whatever decisions you make won't be right for a given application, so it probably has to do one extra copy of the data anyway. However, you'd prefer not to have to do one translation from whatever the hardware can support into some XIL format and then a second translation from that into what the program wants... Also, if the hardware can't handle some combination, you probably want to let the program know that, rather than performing some computationally intensive software translation in the XIL code behind the program's back. For simple tasks, I think XIL does a fine job at trying to provide a common interface no matter what the specifics of the hardware, and yet still optimizing common paths through the system when it can. However, there are still going to be programs that absolutely need to have details of the hardware exposed, and be able to make sensible decisions which are hardware-specific. Video is a lot more complicated than ethernet, and a one-size-fits-all interface just won't do. -- Ron Frederick frederick@parc.xerox.com From rem-conf-request@es.net Tue Nov 23 00:59:41 1993 Received: from jarrah.itd.adelaide.edu.au by osi-east.es.net via ESnet SMTP service id <00931-0@osi-east.es.net>; Mon, 22 Nov 1993 21:50:32 +0000 Received: by jarrah.itd.adelaide.edu.au with SMTP (5.61+IDA+MU/UA-5.28) id AA11254; Tue, 23 Nov 1993 16:20:09 +1030 Message-Id: <9311230550.AA11254@jarrah.itd.adelaide.edu.au> To: rem-conf@es.net Cc: mbone-nws93@unimelb.edu.au Subject: Provisional Australian Networkshop "TV Guide" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Nov 1993 16:20:08 +1030 From: Mark Prior The Australian Networkshop '93 (30 November - 3 December) will be broadcast across the MBONE. We will be using a SGI Indigo2 kindly loaned to us by Silicon Graphics Australia. Although the conference is divided into multiple streams we will be concentrating our efforts in just multicasting the sessions from the Latrobe theatre. This will include all the keynote addresses and a variety of the available sessions. If we have enough resources we might consider trying to do another channel but I expect that won't be possible. To receive this multicast, you must have an audio-capable workstation (SPARCstation, SGI Indigo/Indy, DEC AXP or DS5000, or HP "Snake") with IP multicast software added to the operating system. You must also be connected to the semi-permanent virtual IP multicast network known as the MBONE. Since this effort has been going on for some time now, we hope that all those who are interested have already arranged to be connected. If not, contact your network provider to see if they are providing MBONE connections. The MBONE is currently structured to follow network topology to its best ability. Please don't break this structure by trying to connect just anywhere. Contact your network provider for the best MBONE connection for you. More information about the MBONE, including what hardware and software is required to receive the multicast, is available by anonymous FTP from ftp.adelaide.edu.au in the file pub/av/faq.txt. There will be (at least) two concurrent multicast streams announced via the LBL Session Directory Tool, sd, for this conference. - Australian Networkshop Audio Channel 1: audio (IDV4) - Australian Networkshop Video Channel 1: video (approx. 25 to 128 kbps) Should it be possible to broadcast another stream concurrently we will announce a second channel using the normal "IETF Channel 2" parameters. sd can be used to automatically invoke the audio and video programs with the appropriate address and TTL parameters. The audio will be originated by the vat program from LBL; you may use vat or any other vat-compatible application to listen in and talk back. For video, the latest version of the nv program from Xerox PARC will be used. The provisional timetable follows Tuesday, 30th of November 93 AEST UTC 09:00-09:10 22:00-22:10 Conference Opening Iain Morrison Registrar Information Technology The University of Melbourne 09:10-09:45 22:10-22:45 Keynote Address Dr Van Jacobson Lawrence Berkeley Laboratories Design Issues for High Speed Networks 09:45-10:30 22:45-23:30 The Global Telecommunications Scene Professor Bill Melody Director, CIRCIT 10:30-11:00 23:30-00:00 Morning Tea 11:00-11:45 00:00-00:45 High Speed Networking Gary Kunis Director Engineering/Consulting Services Cisco Systems 11:45-12:30 00:45-01:30 Panel Discussion: Whither AARNet? 12:30-14:00 01:30-03:00 Lunch 14:00-14:45 03:00-03:45 Collaborative Multimedia Work Paradigms Dr Van Jacobson Lawrence Berkeley Laboratories 14:45-15:30 03:45-04:30 ATM: The Cornerstone for Multienterprise Networking Alan Pettigrew Senior Systems Consultant SynOptics Communications Australia New Zealand 15:30-16:00 04:30-05:00 Afternoon Tea 16:00-16:45 05:00-05:45 Running PABX Protocols through IP Shaun Amy CSIRO 16:45-17:30 05:45-06:30 Birds of a Feather Session Network Security Issues Facilitator: Danny Smith SERT Wednesday, 1st of December 09:00-09:45 22:00-22:45 Keynote Address Carolyn Snyder Southern Illinois University at Carbondale The Electronic Library 09:45-10:30 22:45-23:30 Networked Library Applications: Towards a Coherent Strategy Eric Wainwright Deputy Director-General National Library of Australia 10:30-11:00 23:30-00:00 Morning Tea 11:00-11:45 00:00-00:45 Panel: Library/Public Access Issues. 11:45-12:30 00:45-01:30 AARNet Economics: Will We Cook the Golden Goose? Roger Clarke Reader in Information Systems ANU 12:30-14:00 01:30-03:00 Lunch 14:00-15:30 03:00-04:30 National Network Training Developments: A Report and Exchange of Views Jim Cleary and Guests Information Services Librarian University of Newcastle 15:30-16:00 04:30-05:00 Afternoon Tea 16:00-16:45 05:00-05:45 Information Access-Technologies and Services Tony Barry Head Centre for Networked Access to Scholarly Information ANU Library Thursday, 2nd of December 09:00-09:45 22:00-22:45 Keynote Address Joyce Reynolds Information Sciences Institute University of Southern California The US NREN Initiative-Prospects for Education 09:45-10:30 22:45-23:30 Legal Issues Relating to the Use of Computer Networks Philip Catania Corrs Chambers Westgarth 10:30-11:00 23:30-00:00 Morning Tea 11:00-11:45 00:00-00:45 Panel Discussion: Networked Information- Too Hard to Manage? 11:45-12:30 00:45-01:30 Supercomputing Consortia-Network Implications Professor Michael McRobbie ANU 12:30-2:00 01:30-03:00 Lunch 14:00-14:45 03:00-03:45 Copyright-Prospects for Change Derek Fielding Pro-Vice Chancellor The University of Queensland 14:45-15:30 03:45-04:30 Creating the ACT Education Information Network Dr Brian Denehy Computing Services Manager Australian Defence Force Academy 15:30-16:00 04:30-05:00 Afternoon Tea 16:00-16:45 05:00-05:45 The Nuts and Bolts of an AARNet Seminar for Academic Staff Jackie Edwards University of Technology, Sydney 16:45-17:30 05:45-06:30 Birds of a Feather: AARNet and the Law. Friday, 3rd of December 09:00-09:45 22:00-22:45 Keynote Address Vint Cerf President of the Internet Society [ Multicast from Reston, Virginia, USA ] 09:45-10:30 22:45-23:30 Education Resources and Student Access Associate Professor John Winship Director Computer Centre Curtin University of Technology 10:30-11:00 23:30-00:00 Morning Tea 11:00-11:45 00:00-00:45 Panel Discussion: Networked Delivery of Educational Services- Fact or Fiction? 11:45-12:30 00:45-01:30 The Virtual University Sandra Wills Director Interactive Multimedia Learning Unit The University of Melbourne 12:30-14:00 01:30-03:00 Lunch 14:00-14:45 03:00-03:45 US Gigabit Networking Programmes James Sterbenz IBM Advanced Networking Laboratory 14:45-15:30 03:45-04:30 AARNet: A Technical Perspective Geoff Huston Network Technical Manager AARNet 15:30-16:00 04:30-05:00 Conference Closing Summation From rem-conf-request@es.net Fri Nov 26 17:14:16 1993 Received: from fenris.dhhalden.no by osi-east.es.net via ESnet SMTP service id <27697-0@osi-east.es.net>; Fri, 26 Nov 1993 14:03:13 +0000 Received: from sigallah.dhhalden.no by fenris.dhhalden.no with SMTP (PP) id <23439-0@fenris.dhhalden.no>; Fri, 26 Nov 1993 23:03:03 +0100 Received: by sigallah.dhhalden.no (NX5.67c/NX3.0S) id AA01600; Fri, 26 Nov 93 21:59:49 GMT Date: Fri, 26 Nov 1993 21:57:43 +0000 (GMT) From: Borre Ludvigsen Subject: Safe platform To: rem-conf@es.net Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We want to start working with MBone reception and audio/video conferencing over several local ethernets. Are we safe starting with a Sun SPARCclassic and the SunVideo Multimedia kit? Any recommendations? - Barre Ludvigsen From rem-conf-request@es.net Sat Nov 27 12:29:55 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <00717-0@osi-east.es.net>; Sat, 27 Nov 1993 09:22:46 +0000 Received: from anhur.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA13196; Sat, 27 Nov 93 18:22:42 +0100 Message-Id: <9311271722.AA13196@sics.se> To: rem-conf@es.net Cc: carl@radio.com Subject: Re: Geek of the Week In-Reply-To: Your message of "Wed, 24 Nov 1993 04:00:00 -0400." <9311240906.AA08588@trystero.malamud.com> Date: Sat, 27 Nov 1993 18:22:41 +0100 From: Anders Klemets > Carl Malamud interviews Steve Casner, an active participant > in the work on a multicast backbone and instrumental in setting > up the IETF TV video multicasts of working group meetings and > technical presentations to the Internet. Casner talks about the > future of multicasting and audio/visual work on the Internet. I've put the above interview, and some other episodes of "Geek of the Week" online in my "Media on Demand" service on WWW. Klick at the appropriate places and one receives a unicast transmission of the audio which can be listened to with vat. I am going to add tape deck style remote control buttons as soon as I sort out a problem with the WWW server. Please bear in mind, 1) this is experimental, there might be disruptions in the service without prior notice, 2) you need to have Mosaic 2.0 and vat to use this. The URL is http://www.it.kth.se/~klemets/vatplay.html. Anders From rem-conf-request@es.net Sun Nov 28 10:37:03 1993 Received: from bells.cs.ucl.ac.uk by osi-east.es.net via ESnet SMTP service id <03374-0@osi-east.es.net>; Sun, 28 Nov 1993 07:30:25 +0000 Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Sun, 28 Nov 1993 15:30:00 +0000 To: Anders Klemets cc: rem-conf@es.net, carl@radio.com, J.Crowcroft@cs.ucl.ac.uk Subject: Re: Geek of the Week In-reply-to: Your message of "Sat, 27 Nov 93 18:22:41 +0100." <9311271722.AA13196@sics.se> Date: Sun, 28 Nov 93 15:29:58 +0000 From: Jon Crowcroft >I am going to add tape deck style remote control buttons as soon as I >sort out a problem with the WWW server. this stuff is supercool - really great. comments i) i do want a pause/FF/RW (which i guess you are alluding to above) ii) i would like a tape position readout (elapsed/remaining) iii) i _really_ want rough synch between media (source sync could be done at a crude level if there was a coordination between applications at sink - without vat/nv/wb source to add this, we will need source based - you could parse the input first for 'synchronisation units', and input deliberate large delays to let the net delays die down at those points possibly...a good model for how to start doing this is how music studios mark up the instrument tracks for edit/synching... thanks for providing this (already really useful) experiemental service! jon From rem-conf-request@es.net Mon Nov 29 03:03:40 1993 Received: from inesc.inesc.pt by osi-east.es.net via ESnet SMTP service id <06193-0@osi-east.es.net>; Sun, 28 Nov 1993 23:55:29 +0000 Received: from ra.inesc.pt by inesc.inesc.pt with SMTP; id AA24094 (5.65c/SunOS4.1.3); Mon, 29 Nov 1993 08:54:58 +0100 Received: from localhost by ra.inesc.pt (4.1/SunOS4.1.3) id AA00270; Mon, 29 Nov 93 08:55:19 +0100 Message-Id: <9311290755.AA00270@ra.inesc.pt> To: Anders Klemets Cc: rem-conf@es.net, carl@radio.com Subject: Re: Geek of the Week In-Reply-To: Your message of "Sat, 27 Nov 93 18:22:41 +0100." <9311271722.AA13196@sics.se> Date: Mon, 29 Nov 93 08:55:07 +0100 From: Werner Vogels > I've put the above interview, and some other episodes of "Geek of the > Week" online in my "Media on Demand" service on WWW. Klick at the > appropriate places and one receives a unicast transmission of the > audio which can be listened to with vat. Anders, thanks for this excellent service, but as you are extending the capabilities I have a request that maybe could lighten the load on our suffering European lines: could you as an "option" provide a local remix from PCM to GSM, so that those who still have to rely on international 64 kb lines can enjoy your service better? -- Werner From rem-conf-request@es.net Mon Nov 29 04:58:45 1993 Received: from pat.uio.no by osi-east.es.net via ESnet SMTP service id <06743-0@osi-east.es.net>; Mon, 29 Nov 1993 01:47:50 +0000 Received: from ulrik.uio.no by pat.uio.no with local-SMTP (PP) id <08268-0@pat.uio.no>; Mon, 29 Nov 1993 10:47:43 +0100 Received: from localhost by nyst.uio.no ; Mon, 29 Nov 1993 10:47:38 +0100 Message-Id: <9311290947.AAnyst15362@nyst.uio.no> To: mice-seminars@cs.ucl.ac.uk, rem-conf@es.net Subject: MICE seminar Monday Nov 29 Date: Mon, 29 Nov 93 10:47:36 +0100 From: ronny.nilsen@usit.uio.no X-Mts: smtp The weekly MICE seminar is held by the Univ. of Oslo on Nov 29 at 15.00 CET (=14.00 GMT) It is transmitted on the usual multicast addresses: vat 224.5.17.12/3456 ivs 224.5.17.12/2232 wb 224.5.17.12/32416 The topic for todays seminar is an electronic classroom system for distance education, meetings and seminars. The MUNIN/MultiTeam project is a project to implement, try out and evaluate a system for distance education between electronic classrooms. The electronic classroom provides for video and audio communication as well as an electronic white board. The electronic white board provides the user with a large (2 x 1.3 meters) drawing area for a pen. Two electronic white boards are interconnected so that they appear as a shared electronic white board in the participating classrooms. Communication between the electronic classrooms is based on IP networking technology. The project is organized as a joint project between the Center for Information Technology Services at the University of Oslo (USIT), the Norwegian Telecom Research Department (NTR) and the Center for Technology at Kjeller (UNIK). The development activities within the project is carried out by the University of Oslo. The speakers are Geir Pedersen and Ronny Nilsen of the University of Oslo. From rem-conf-request@es.net Mon Nov 29 11:20:05 1993 Received: from picard.cmf.nrl.navy.mil by osi-east.es.net via ESnet SMTP service id <07751-0@osi-east.es.net>; Mon, 29 Nov 1993 06:11:00 +0000 Received: from herman.cmf.nrl.navy.mil (herman.cmf.nrl.navy.mil [134.207.7.3]) by picard.cmf.nrl.navy.mil (8.6.4/8.6.4) with SMTP id JAA15442; Mon, 29 Nov 1993 09:10:55 -0500 Received: from localhost by herman.cmf.nrl.navy.mil (4.1/client-1.3) id AA12802; Mon, 29 Nov 93 09:10:53 EST Message-Id: <9311291410.AA12802@herman.cmf.nrl.navy.mil> To: Werner Vogels Cc: rem-conf@es.net, carl@radio.com Subject: Re: Geek of the Week In-Reply-To: Your message of "Mon, 29 Nov 93 08:55:07 +0100." <9311290755.AA00270@ra.inesc.pt> Date: Mon, 29 Nov 1993 09:10:51 -0500 From: William C Fenner On Mon, 29 Nov 93 08:55:07 +0100 Werner Vogels wrote: > Anders, thanks for this excellent service, but as you are extending the > capabilities I have a request that maybe could lighten the load on our > suffering European lines [...] I can be a U.S. source for the entire current season of Internet Talk Radio. (although I think it's almost time to take September offline...) That should help with load sharing. I'll work on setting it up when I have some free time, maybe by next week sometime. Bill From rem-conf-request@es.net Mon Nov 29 12:13:23 1993 Received: from trystero.malamud.com by osi-east.es.net via ESnet SMTP service id <09628-0@osi-east.es.net>; Mon, 29 Nov 1993 09:03:05 +0000 Received: by trystero.malamud.com (5.65/IDA-93111801) id AA29101; Mon, 29 Nov 93 12:06:43 -0500 Date: Mon, 29 Nov 93 12:06:43 -0500 From: Carl Malamud Message-Id: <9311291706.AA29101@trystero.malamud.com> To: klemets@sics.se, rem-conf@es.net Subject: Re: Geek of the Week Anders - Thanks much for putting the Steve Casner interview on your Media on Demand server! Some of you may wonder why the Internet Multicasting Service doesn't spend a lot of time multicasting .... We've currently got one poor Sparc 2 which spends most of its time resampling 48 khz .wav files down to 8 khz. That puts our CPU at literally 100% for 24 hours per day, not leaving much room for mrouted, vat, and other programs. We're almost through an upgrade (including some serious CPU horsepower and disk space) and hope to become a permanent presence on the MBONE in January. This includes the live multicasts of National Press Club luncheons *and* the ability for the MBONE to ask questions of the speakers. Stay tuned (and thanks to Anders for putting the data out in the mean time!). Carl From rem-conf-request@es.net Mon Nov 29 19:52:24 1993 Received: from alpha.Xerox.COM by osi-east.es.net via ESnet SMTP service id <01030-0@osi-east.es.net>; Mon, 29 Nov 1993 16:42:57 +0000 Received: from skylark.parc.xerox.com ([13.2.116.7]) by alpha.xerox.com with SMTP id <14694(1)>; Mon, 29 Nov 1993 16:42:37 PST Received: from localhost by skylark.parc.xerox.com with SMTP id <12171>; Mon, 29 Nov 1993 16:42:33 -0800 To: rem-conf@es.net, vat-radio@elxr.jpl.nasa.gov Subject: MBone "reservation" Date: Mon, 29 Nov 1993 16:42:26 PST Sender: Steve Deering From: Steve Deering Message-Id: <93Nov29.164233pst.12171@skylark.parc.xerox.com> A SIPP WG meeting will be held on the MBone on Thursday, Dec. 9, from 9 am to 12 noon California Time (1700 - 2000 GMT). I humbly request that others refrain from (more) frivolous uses of the MBone during that time. Thanks, Steve From rem-conf-request@es.net Tue Nov 30 04:52:09 1993 Received: from venera.isi.edu by osi-east.es.net via ESnet SMTP service id <04648-0@osi-east.es.net>; Tue, 30 Nov 1993 01:36:23 +0000 Received: from xfr.isi.edu by venera.isi.edu (5.65c/5.61+local-14) id ; Tue, 30 Nov 1993 01:33:50 -0800 Posted-Date: Tue 30 Nov 93 01:33:04 PST Received: by xfr.isi.edu (4.1/4.0.3-4) id ; Tue, 30 Nov 93 01:33:05 PST Date: Tue 30 Nov 93 01:33:04 PST From: Stephen Casner Subject: AVT Working Group Minutes To: rem-conf@es.net Message-Id: <754651984.0.CASNER@XFR.ISI.EDU> Mail-System-Version: Reported by Steve Casner/USC-ISI Minutes of Audio/Video Transport Working Group (AVT) The AVT WG met for only one session this time since the draft specification for the Real-time Transport Protocol (RTP) is nearly completed for the first RFC stage. The emphasis of this session was on implementation experience as in the third session at previous IETF meetings, with the focus shifting to companion specifications for profiles and encodings. 1. Status of draft RTP specification This group did not meet in Amsterdam, but there has been substantial progress on the RTP spec via email and a teleconference, and a new draft-ietf-avt-rtp-04.txt and .ps has been installed. The spec has been submitted to the Area Director with a request for "IESG Last Call", and is in review by the Directorate. Steve Casner from ISI gave a brief description of the most recent change to the spec, which was the addition of the APP option. This option allows experimental application-specific options to be defined without official registration while still avoiding conflicts with other option definitions. See the draft RTP spec for details. A brief description was also given on a proposal from Andrew Cherenson from SGI to add an option, not in the main RTP spec but in the audio/video profile, to indicate the mode or state of a participant. The proposed set of states were: active, video frozen (still image), private (listening but not sending), and hold (not listening and not sending). A good fraction of the attendees at this meeting had read the RTP spec. Comments were solicited both on the spec and on the two options just described, but no comments were offered. However, behind the scenes, some objections have been raised to the classification of RTP as a proposed standard and to certain details of the specification. These issues will be discussed further on the mailing list. 2. Implementation experience Ron Frederick from Xerox PARC gave a presentation on his experience with implementing RTP in the nv (network video) program. He reported that overall, the implementation went very cleanly, and that the combination of the sequence number, timestamp and sync bit worked well together. He found the option format easy to generate and parse, but cautioned that the parser much watch out for an illegal option length zero or length greater than the packet length. (The example option parsing code in the appendix to the spec includes these checks.) The one nuisance Ron found was that the program needs to know if an SSRC option is present to fully identify the sender before the parsing can act upon the other options. This requires parsing the options twice, or storing the information while parsing and then acting upon it at the end. To reduce this nuisance, it was proposed that the spec be modified to require that if an SSRC option is present, it must follow immediately after the fixed header. Since this is the logical place for translators to insert the SSRC option, and since there can be only one, this restriction should cause no difficulties. David Kristol from AT&T described his work just beginning on a quality of service monitor for RTP. It would create a map of the MBONE, and display a measure of the reception quality for each receiver on the map using data obtained from reception reports multicast by the receivers. This would allow a visual determination of bottleneck points. One observation was that the measure of video delay is affected by the use of the same timestamp on all packets of a video frame even though the packets are not transmitted at the same time. A solution is to measure delay only on the first packet of a frame. This illustrates that reception quality measurement may be dependent upon the medium. Dave also implemented a vat/RTP translator to allow participation in vat audio sessions inside the AT&T firewall. This turned out to be very simple, the only problem being translation of vat's beginning-of-talkspurt flag into RTP's end-of-talkspurt flag. For now, he is just copying the bit and ignoring the distinction. 3. Encoding specifications Frank Kastenholz from FTP Software asked for the addition in the audio/video profile of an 8-bit linear encoding ("L8") and a format code for L8 encoding at 11.025 KHz. This matches the capability of common audio hardware on PC and Mac platforms. It is possible to convert in software to 8-bit mu-law at 8 KHz, but this increases the minimum processing power required to participate. This request was generally agreed upon, and Frank was requested to provide the details to go into the profile. Henning Schulzrinne cautioned that adding a new "standard" encoding places a burden on all implementations to include at least a decoder for it. Bill Fenner from NRL and Ron Frederick gave presentations on carrying JPEG video over RTP, and on the issues to be addressed in an encoding specification. Although the JPEG spec includes a variety of formats, Ron recommended that we stick with 4:2:2 video format, square pixels (as produced by most of the chips even though CCIR 601 specifies rectangular pixels), a 16x8 block as the minimum coded unit, and progressive scan. Ron also recommended that we use the Q factors defined for C-JPEG and D-JPEG by the Free JPEG Group and use the standard Huffman coding table, though these could be overridden by custom table definitions. Bill has designed an encoding for JPEG over RTP, and implemented it using the Parallax JPEG hardware. He points out that JPEG frames are large, so they are likely to require segmentation and reassembly. Losing one packet out of a frame will result in frame loss because the Huffman reset mechanism that's part of the standard does not provide enough sequence space for packet-size losses. He also observed that the Q factor does not provide much usable quality range (the picture gets lots uglier without the frame rate increasing as much as one would expect). The encoding Bill defined uses the same RTP timestamp on all packets of a frame, and the RTP sync bit indicates the last packet of the frame, as usual. In addition, he has defined a small header to go at the beginning of the data in the first packet of a frame. The presence of this header is indicated by the first two bytes being one of the application-specific codes (0xFF 0xE1) provided in the JPEG spec and guaranteed not appear in the data. This code is followed by two bytes to encode the Q factor, Huffman table index, and some size information. Special values of these indices can be used to indicate that custom quantization and/or Huffman tables will follow. The mechanisms for requesting and/or periodically retransmitting custom tables are still to be decided and tested. There were no major objections to this design except for the suggestion that explicit image width and height factors be included. Bill agreed to produce a first draft specification for JPEG over RTP with assistance from Ron and Fengmin Gong from MCNC. 4. Video decoder API In Columbus we had a good discussion on the feasibility of creating a common interface for software video decoders so that each packet video program can incorporate decoders for many or all of the other programs' native formats to enable interoperation. At this meeting, Ron Frederick gave an update on the decoder API in the nv program in which decoding and rendering of the image data are decoupled: nv does all the network I/O, RTP processing, and X window system interaction; the image decode routines just convert each packet of compressed bits into uncompressed YUV pixels for a portion of the image. A callback routine is provided to render a rectangular portion of the image after decoding. Ron identified several open issues that have arisen: - Is YUV a good choice for color decoding? It allows easy rendering into monochrome or color images, but requires extra processing for encodings that would more naturally use RGB or dithered data. The difficulty is that number of variations in the rendering code is already large to handle variations in pixel depth and ordering. It may not be worthwhile to double or triple this to render from additional input formats. - It is desirable to enable the use of hardware encoders and/or decoders for increased performance, but what additional hooks are required to fit this into the model? Some answers may come from exploring the options for the SunVideo board Cell-B encoder and for JPEG video using the Parallax board as Bill Fenner has done. - Should the common code handle resequencing of packets? Previously, nv ignored packet sequencing because packets of the nv encoding can be processed out of order. Now, nv is processing the sequence numbers to accumulate packet loss information, and could do the resequencing. However, Ron feels that this function should be left to the decode routines because the requirements may not be the same for all encodings, unless we can define as part of the profile an extra level of framing for all the encodings to use. Other API's may also be needed. Henning suggested that video encoding routines should also be sharable to reduce the effort of writing them. Since nv already separates the frame grab from the encoding, an interface could be explored there. Abel Weinrib also pointed out that we need API's at a higher layer, that of whole media agents to be controlled by different session managers. 5. Report from IMA Network Focus Group A the end of the session, we got a report from Thomas Maslen of Sun on the recent first meeting of the IMA Network Focus Group, and on the potential interaction with the IETF AVT and MMUSIC activities. The The Interactive Multimedia Association (IMA) is an industry group chartered to develop standards to support multimedia applications. In particular, the Multimedia System Services (MSS) proposal defines an object-oriented architecture for the infrastructure to support multimedia applications. In a way, the MSS work fits between the AVT and MMUSIC areas. The MSS proposal does not specify media transport mechanisms or protocols. The Network FoG is to address the requirements for network transport in the MSS, and to define network transport interfaces, target environments and protocol profiles to support those requirements. The group will work with other standards groups, including IETF, to incorporate existing protocols and cooperate on the definition of new ones where needed. At first look, it appears that RTP may be suitable as one of the protocols to be used for transport of real-time media. Similarly, MSS provides infrastructure for multimedia applications such at teleconferencing, but does not include the applications themselves. Abel pointed out that it does not include in its model higher-level objects like people, and does not include policies. Therefore, MMUSIC sits above MSS, and the session management mechanisms to be developed in that WG might be used for communication among a set of applications implemented using MSS. 6. Future working group activity The session closed with a discussion of future working group activity. As work on the RTP spec is completed, the group's emphasis will shift to profile and encoding specifications. From the point of view of our Area Director, Allison Mankin, it is appropriate for the group to continue work as needed, or to go on hiatus but keep the mailing list (rem-conf) active. Meetings at future IETFs may then be called to address new questions such as the interface between network real-time services and RTP, or when appropriate to advance any of the specifications through the standards process. ------- From rem-conf-request@es.net Tue Nov 30 05:02:44 1993 Received: from odin.ucsd.edu by osi-east.es.net via ESnet SMTP service id <04683-0@osi-east.es.net>; Tue, 30 Nov 1993 01:50:42 +0000 Received: from kailas.ucsd.edu by odin.ucsd.edu; id AA08400 sendmail 5.67/UCSDPSEUDO.4-CS via SMTP Mon, 29 Nov 93 23:37:56 -0800 for rem-conf@es.net Received: by kailas (5.67/UCSDPSEUDO.4) id AA24740 for mm-announcement-list@odin; Mon, 29 Nov 93 23:37:51 -0800 Date: Mon, 29 Nov 93 23:37:51 -0800 From: avconf@cs.ucsd.edu (AV Workshop) Message-Id: <9311300737.AA24740@kailas> To: mm-announcement-list@cs.ucsd.edu Subject: NOSSDAV'92 Proceedings The formal proceedings of the 3rd International Workshop on Network and Operating System Support for Digital Audio and Video is now available from Springer-Verlag, as a book in its Lecture Notes in Computer Science series (P. Venkat Rangan, Ed.), #712, ISBN #3-540-57183-3 and ISBN #0-387-57183-3. It may be ordered directly from any Springer-Verlag office, or by sending a request to Dr. Hoffmann at e-mail: SV-WOESSNER@DCFRZ1.DAS.NET -- Workshop Organizers. From rem-conf-request@es.net Tue Nov 30 13:00:33 1993 Received: from taurus.cs.nps.navy.mil by osi-east.es.net via ESnet SMTP service id <08240-0@osi-east.es.net>; Tue, 30 Nov 1993 09:56:15 +0000 Received: from betsie.cs.nps.navy.mil by taurus.cs.nps.navy.mil (4.1/SMI-4.1) id AA09066; Tue, 30 Nov 93 09:57:25 PST Date: Tue, 30 Nov 1993 09:48:50 -0800 (PST) From: Michael Macedonia Subject: MBONE members in France and Japan To: rem-conf@es.net Cc: mbone@isi.edu In-Reply-To: <93Nov29.164233pst.12171@skylark.parc.xerox.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII NPS, MBARI, NASA, and the NSF are hosting an international robotics conference here in Monterey 1 -6 May 94. We intend to use MBONE for a feed from France and Japan during that period. Our school of management will be collecting data and surveying participants for their reactions to the teleconference. 1) Can anyone direct me to the names of the persons who are the MBONE points of contact in France and Japan (particularly in Tokyo and INRIA)? 2) Is there a conflict or objection over using MBONE for this experiment ? Thanks, Mike Macedonia | macedoni@cs.nps.navy.mil MAJ, USA | RM H519, CS Dept, Naval Postgraduate School, | Monterey, CA 93943 | PH:(408) 656-2615 FAX:(408) 656-2814 ------------------------------------------------------------ From rem-conf-request@es.net Tue Nov 30 13:39:35 1993 Received: from sics.se by osi-east.es.net via ESnet SMTP service id <08967-0@osi-east.es.net>; Tue, 30 Nov 1993 10:38:51 +0000 Received: from sarapis.sics.se by sics.se (5.65+bind 1.7+ida 1.4.2/SICS-1.4) with SMTP id AA11855; Tue, 30 Nov 93 19:38:46 +0100 Message-Id: <9311301838.AA11855@sics.se> To: rem-conf@es.net Subject: Australian networkshop online Date: Tue, 30 Nov 1993 19:38:45 +0100 From: Anders Klemets I've put some recordings from the Australian networkshop online at my Media on Demand WWW server, thanks to George Michaelson. I have Van Jacobsens two talks, "Design issues for high speed networks" and "Ligthweight sessions, a new architecture for realtime applications and protocols" online. I've been ftp'ing the recordings during the day from their source in Australia, so there is no packet loss. The nv video signal shows Vans slides, and it is actually pretty readable. Anders From rem-conf-request@es.net Tue Nov 30 19:07:56 1993 Received: from mvs.oac.ucla.edu by osi-east.es.net via ESnet SMTP service id <27693-0@osi-east.es.net>; Tue, 30 Nov 1993 16:07:10 +0000 Received: from UCLAMVS.BITNET by MVS.OAC.UCLA.EDU (IBM MVS SMTP V2R2.1) with BSMTP id 9863; Tue, 30 Nov 93 16:06:55 PST Date: Tue, 30 Nov 93 16:05 PST To: mbone@ISI.EDU, rem-conf@ES.NET From: Denis DeLaRoca (310) 825-4580 Subject: Australian Networkshop: reception report The plenary session (wednesday session) came in fine, the next session started allright but halfway thru it the audio started breaking out badly... it still is breaking out badly at tea break. Also, I kept seeing audio/video outages that would last for about 1/2 minute. The slides are showing up nicely, they can be read. :-) -- Denis From rem-conf-request@es.net Tue Nov 30 20:16:27 1993 Received: from psych.psy.uq.oz.au by osi-east.es.net via ESnet SMTP service id <29042-0@osi-east.es.net>; Tue, 30 Nov 1993 17:08:11 +0000 Received: from localhost by psych.psy.uq.oz.au id ; Wed, 1 Dec 1993 11:08:08 +1000 Message-Id: <199312010108.LAA16957@psych.psy.uq.oz.au> To: rem-conf@es.net Subject: Current Feeds.... Date: Wed, 01 Dec 1993 11:08:06 +1000 From: Robert Dal Santo At the moment there are a number of competeing feeds. There is the Australian Networkshop '93 which will run until Friday and the current shuttle mission. At this exact moment, there are two identical video feeds of the shuttle. Could the shuttle feed be limited and, if possible, shut of on Friday (local time). Friday December 3rd at 9.am local time (UTC 20:00) the AARNet Networkshop will be receiving an incoming speech on the Mbone from Vinton G Cerf, so at that time it would be greatly appreciated if other Mbone traffic could be minimised. Thanks, Robert Dal Santo Phone +61 7 365 6687 Fax +61 7 365 4466 Department of Psychology, University of Queensland 4072, AUSTRALIA. "I've reached the driveway to destruction and I'm taking the stationwagon."