From rem-conf Mon Nov 03 09:25:34 1997 From rem-conf-request@es.net Mon Nov 03 09:25:33 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSQ2L-0002Dp-00; Mon, 3 Nov 1997 09:11:37 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Mon, 3 Nov 1997 09:11:02 -0800 (PST) Message-Id: <199711031711.JAA18630@hille.msri.org> To: rem-conf@es.net From: Reply-to: kurino@nc.nihon-u.ac.jp Subject: APEC-CIL'97 Conference X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: APEC-CIL'97 Conference Date: Nov 06, 1997 Time: 00:00 GMT 10 hours Contact: kurino@nc.nihon-u.ac.jp URL: http://www.cil.apec.org Description: mbone broadcast schedule http://www.msri.org/mbone From rem-conf Mon Nov 03 09:25:35 1997 From rem-conf-request@es.net Mon Nov 03 09:25:35 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSQ1Q-0002DV-00; Mon, 3 Nov 1997 09:10:40 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Mon, 3 Nov 1997 09:10:06 -0800 (PST) Message-Id: <199711031710.JAA18603@hille.msri.org> To: rem-conf@es.net From: Reply-to: kurino@nc.nihon-u.ac.jp Subject: APEC-CIL'97 Conference X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: APEC-CIL'97 Conference Date: Nov 05, 1997 Time: 00:00 GMT 10 hours Contact: kurino@nc.nihon-u.ac.jp URL: http://www.cil.apec.org Description: mbone broadcast schedule http://www.msri.org/mbone From rem-conf Mon Nov 03 09:25:37 1997 From rem-conf-request@es.net Mon Nov 03 09:25:36 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSQ3L-0002En-00; Mon, 3 Nov 1997 09:12:39 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Mon, 3 Nov 1997 09:11:50 -0800 (PST) Message-Id: <199711031711.JAA18657@hille.msri.org> To: rem-conf@es.net From: Reply-to: kurino@nc.nihon-u.ac.jp Subject: APEC-CIL'97 Conference X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: APEC-CIL'97 Conference Date: Nov 07, 1997 Time: 00:00 GMT 10 hours Contact: kurino@nc.nihon-u.ac.jp URL: http://www.cil.apec.org Description: mbone broadcast schedule http://www.msri.org/mbone From rem-conf Mon Nov 03 09:25:38 1997 From rem-conf-request@es.net Mon Nov 03 09:25:37 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSQ0O-0002DD-00; Mon, 3 Nov 1997 09:09:36 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Mon, 3 Nov 1997 09:08:10 -0800 (PST) Message-Id: <199711031708.JAA18572@hille.msri.org> To: rem-conf@es.net From: Reply-to: kurino@nc.nihon-u.ac.jp Subject: APEC-CIL'97 Conference X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: APEC-CIL'97 Conference Date: Nov 04, 1997 Time: 02:00 GMT 8 hours Contact: kurino@nc.nihon-u.ac.jp URL: http://www.cil.apec.org Description: mbone broadcast schedule http://www.msri.org/mbone From rem-conf Mon Nov 03 10:02:37 1997 From rem-conf-request@es.net Mon Nov 03 10:02:37 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSQnv-0004UP-00; Mon, 3 Nov 1997 10:00:47 -0800 Message-Id: From: gumbee@ctd.comsat.com To: rem-conf@es.net Date: Mon, 3 Nov 1997 13:00:27 -0500 Subject: Unidentified subject! X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list in the RTP/RTCP spec (RFC 1889), what is the exact difference between timestamp and sequence number? aren't they really performing the same task? thanks, grant From rem-conf Mon Nov 03 10:21:29 1997 From rem-conf-request@es.net Mon Nov 03 10:21:28 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSR5A-00050d-00; Mon, 3 Nov 1997 10:18:36 -0800 From: Mark Handley X-Organisation: Information Sciences Institute, USC X-Phone: +1 617 253 6011 To: gumbee@ctd.comsat.com cc: rem-conf@es.net Subject: Re: Unidentified subject! In-reply-to: Your message of "Mon, 03 Nov 1997 13:00:27 EST." Date: Mon, 03 Nov 1997 13:17:29 -0500 Message-ID: <6039.878581049@north.lcs.mit.edu> Sender: mjh@north.lcs.mit.edu X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list >in the RTP/RTCP spec (RFC 1889), what is the exact >difference between timestamp and sequence number? >aren't they really performing the same task? Timestamp measures media time. Sequence number measures packets. The relationship between the two is complex, because there can be varying amounts of data in a packet or varying numbers of packets in a video frame. For example, 20ms, 40ms and 80ms PCM all use have the same payload type but have different packet rates. Also the number of packets in a single video frame with a single timestamp depends on the coding and the image content. Packets also don't get sent continuously - for example audio with silence detection doesn't send packets continuously, but the audio timestamp clock keeps counting. Cheers, Mark From rem-conf Tue Nov 04 01:50:46 1997 From rem-conf-request@es.net Tue Nov 04 01:50:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSfY3-0002ip-00; Tue, 4 Nov 1997 01:45:23 -0800 Message-Id: <345EEE7F.276F6A6E@athena.polito.it> Date: Tue, 04 Nov 1997 10:44:31 +0100 From: Tommaso Bargiacchi X-Mailer: Mozilla 4.03 [en] (Win95; I) Mime-Version: 1.0 To: rem-conf@es.net Subject: Help VIC & PARALLAX Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Hi, We are two students of the Politecnico di Torino in Italy. We are working on a project about videoconferencing and we would like to use VIC (video conferencing tool) by LBL for our purposes. We have the following problem: Compiling VIC source code on a Sun Solaris 2.5 with a Parallax video card the Makefile is not able to find the XPlxExt.h file included by grabber-plx.cc and plxfuncs.h Does anyone knows where we can find XPlxExt.h ? Thank you very much Roberto & Tommaso From rem-conf Tue Nov 04 05:16:03 1997 From rem-conf-request@es.net Tue Nov 04 05:16:02 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSiiF-0003va-00; Tue, 4 Nov 1997 05:08:07 -0800 Message-Id: <3.0.32.19971104080232.00ae9d30@mailee.bellcore.com> X-Sender: stanm@mailee.bellcore.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 04 Nov 1997 08:02:45 -0500 To: enternet@bbn.com, tccc@cs.umass.edu, dbworld@cs.wisc.edu, end2end-interest@isi.edu, f-troup@CODEX.CIS.upenn.edu, cost237-transport@comp.lancs.ac.uk, reres@laas.fr, hipparch@sophia.inria.fr, xtp-relay@cs.concordia.ca, rem-conf@es.net, sigmedia@bellcore.com, mobile-ip@tadpole.com, cellular@comnets.rwth-aachen.de, ieeetcpc@ccvm.sunysb.edu, cnom@maestro.bellcore.com, commsoft@cc.bellcore.com, multicomm@cc.bellcore.com From: Stan Moyer Subject: ENCOM '98 CFP Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list CALL FOR PAPERS Enterprise Networking and Computing '98 (ENCOM-98) in conjunction with ICC/SUPERCOMM '98 (June7-11), Atlanta, Georgia, Sunday, June 7 sponsored by the IEEE Communications Society's Technical Committee on Enterprise Networking ENCOM-98 will provide an open forum for the enterprise networking and computing communities to review new and emerging technologies, services, and their implications from both business and technological viewpoints. The objective is to bridge the gap between: (a) Enterprise-wide business drivers and (b) Technology- driven solutions and enablers. The conference will include a keynote speech, panel discussions, and paper sessions by leaders, recognized experts and active researchers in the field. Submission Instructions ----------------------- The title page must include the corresponding author's full name, complete postal and e-mail addresses, telephone and fax numbers, and a 200-word abstract. Five double-spaced copies of papers (12 point times font, maximum 3000 words) on 8.5"x11" or A4 papers should be sent to the ENCOM-98 technical chair at the address given below. All submissions will be peer-reviewed and the accepted papers will be published in the proceedings of ENCOM-98. Proposals for panels should be submitted to the panel discussion arrangement chair. Schedule: --------- Complete Manuscript Due: 15 November 1997 Acceptance Note Mailed: 01 February 1998 Camera-ready Paper Due: 01 March 1998 Hot topics: ----------- o Utilization of new and emerging technologies for the evolution of enterprise networks o Intranets, Extranets and Internets: How they are transforming the enterprise networks o Legacy systems integration o Integration of enterprise network subsystems to provide "end-user" oriented services o Enterprise network application/services integration o Internetworking and interoperability of enterprise network components o Enterprise-wide computing, including distributed applications, client-serving computing, etc. o Enterprise information resource management. o Enterprise network management o Business processes re-engineering enterprise networks o Pros and cons of enterprise network outsourcing o Integration of network and systems management from an enterprise viewpoint. General Chair: -------------- Bhumip Khasnabish (bhumip@gte.com), MA, USA Technical Chair: ---------------- Vijay K. Bhagavath (bhagavath@att.com) AT&T Laboratories, Rm. 1L-333 101 Crawfords Corner Rd., Holmdel, NJ 07733, USA Tel: +1-908-949-2837, Fax: +1-908-949-4852 Panels Chair: ------------- Pradeep Ray (P.Ray@st.nepean.uws.edu.au) For more information, see: -------------------------- http://www.comsoc.org/confs/encom/98 Sponsored by the IEEE Communications Society Technical Committee on Enterprise Networking From rem-conf Tue Nov 04 09:29:41 1997 From rem-conf-request@es.net Tue Nov 04 09:29:40 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSmaB-0005TQ-00; Tue, 4 Nov 1997 09:16:03 -0800 Message-ID: <345F5814.755DB885@netscape.com> Date: Tue, 04 Nov 1997 09:15:00 -0800 From: anup@netscape.com (Anup Rao) Organization: Netscape Communications Corporation X-Mailer: Mozilla 4.03 [en]C-NSCP (WinNT; U) MIME-Version: 1.0 To: Tommaso Bargiacchi CC: rem-conf@es.net Subject: Re: Help VIC & PARALLAX References: <345EEE7F.276F6A6E@athena.polito.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Tommaso Bargiacchi wrote: > We have the following problem: > > Compiling VIC source code on a Sun Solaris 2.5 with a > Parallax video card the Makefile is not able to find the > > XPlxExt.h file included by grabber-plx.cc and plxfuncs.h > > Does anyone knows where we can find XPlxExt.h ? That really depends on whether or not you have the Parallax development environment installed. If you do have it installed(in PARALLAX_HOME, say) , then you will find the include files in the $PARALLAX_HOME/include directory. The default for a parallax installation is /opt/parallax. It is quite possible that your machine has only the runtime environment installed(or the runtime and development in seperate places). In this case you will see nothing in the include directory except an "icon" subdirectory. Note that, to build the stuff, you need the development environment. -- ----------------------------------------------------------------- Anup Rao Member Of Technical Staff Netscape Communications Corp. email : anup@netscape.com Phone : (650) 937 3129 ----------------------------------------------------------------- From rem-conf Tue Nov 04 09:38:23 1997 From rem-conf-request@es.net Tue Nov 04 09:38:23 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xSmrt-0005i9-00; Tue, 4 Nov 1997 09:34:21 -0800 Posted-Date: Tue, 4 Nov 1997 09:32:27 -0800 (PST) Date: Tue, 4 Nov 1997 09:32:27 -0800 (PST) From: Steven Berson To: Tommaso Bargiacchi Cc: rem-conf@es.net Subject: Re: Help VIC & PARALLAX In-Reply-To: <345EEE7F.276F6A6E@athena.polito.it> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list On Tue, 4 Nov 1997, Tommaso Bargiacchi wrote: > We have the following problem: > > Compiling VIC source code on a Sun Solaris 2.5 with a > Parallax video card the Makefile is not able to find the > > XPlxExt.h file included by grabber-plx.cc and plxfuncs.h > > Does anyone knows where we can find XPlxExt.h ? They should be with your parallax software if I recall properly. Cheers, Steve From rem-conf Wed Nov 05 00:18:18 1997 From rem-conf-request@es.net Wed Nov 05 00:18:16 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xT0Y0-0003RE-00; Wed, 5 Nov 1997 00:10:44 -0800 Message-Id: <9711050808.AA16422@dxcoms.cern.ch> Subject: LEPC MBone transmission To: rem-conf@es.net, hepnet-l@slacvm.slac.stanford.edu, hrc@frcpn11.in2p3.fr, htasc@listbox.cern.ch, net-teleconferencing@listbox.cern.ch Date: Wed, 5 Nov 1997 09:08:32 +0100 (MET) From: "Martin Fluckiger - CERN/IT/CS" X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list CERN is pleased to announce the MBONE broadcast of the LEP Committee Open Session -------------------------- on Tuesday, 11 November 1997 at 09:00 (UTC+1) from the CERN Auditorium *** Times are UTC+1 *** Reports on the LEP machine: 09:00 - 09:20 Future LEP operation (Chris Llewellyn Smith) 09:20 - 09:50 LEP2 status (Roger Bailey) Reports on the LEP experiments: 09:50 - 10:20 L3 (Martin Pohl) 10:20 - 10:50 OPAL (Alan Honma) 10:50 - 11:15 Coffee break 11:15 - 11:45 ALEPH (Peter Dornan) 11:45 - 12:15 DELPHI (Philippe Charpentier) LEP working group reports: 12:15 - 12:30 Four-jet events (Dieter Schlatter) 12:30 - 13:00 Supersymmetry (Luc Pape) The broadcast is announced via sdr as "CERN LEPC". vat and vic applications will be used with a ttl of 127. In case of questions or problems please contact: multicast@noc.cern.ch This message is sent to distribution lists, sorry if you receive multiple copies of it. Best regards, -------------------------------------------------------------------- Martin Fluckiger & Christian Isnard CERN - CN/CS/EN multicast@noc.cern.ch European Laboratory for Particle Physics Computers and Networks division CH-1211 Geneva 23 - Switzerland From rem-conf Wed Nov 05 12:36:21 1997 From rem-conf-request@es.net Wed Nov 05 12:36:20 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xTBv6-0000OY-00; Wed, 5 Nov 1997 12:19:20 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Wed, 5 Nov 1997 12:19:05 -0800 (PST) Message-Id: <199711052019.MAA00198@hille.msri.org> To: rem-conf@es.net From: Reply-to: davidwu@bmrc.berkeley.edu Subject: A Spreadsheet Approach to Information Visualization X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: A Spreadsheet Approach to Information Visualization Date: Nov 12, 1997 Time: 12:30 PST8PDT 2 hours Contact: davidwu@bmrc.berkeley.edu URL: http://bmrc.berkeley.edu/298/w12.html Description: Ed H. Chi, Computer Science Department, University of Minnesota In information visualization, as the volume and complexity of the data increases, researchers require more powerful visualization tools that enable them to more effectively explore multi-dimensional datasets. In this paper, we discuss the general utility of a novel visualization spreadsheet framework. Just as a numerical spreadsheet enables exploration of numbers, a visualization spreadsheet enables exploration of visual forms of information. We show that the spreadsheet approach facilitates certain information visualization tasks that are more difficult using other approaches. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Wed Nov 05 16:29:58 1997 From rem-conf-request@es.net Wed Nov 05 16:29:57 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xTFf4-0002LZ-00; Wed, 5 Nov 1997 16:19:02 -0800 Date: Wed, 5 Nov 1997 18:50:03 -0500 (EST) From: 6ms5@6ms5ol.net To: friend@oalth33.net Subject: Let Us Do Your Bulk Mailing !!! Reply-To: friendz@cbec1ker.net X-PMFLAGS: 20724340.54 X-UIDL: 20720340_206230.502 Comments: Authenticated Sender is Message-Id: <38288113_53188548> X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list LET US DO YOUR BULK MAILINGS!!! ...$250 PER MILLION ...$150 PER 500,000 THE WAY OF THE FUTURE FOR SUCCESS IN YOUR BUSINESS! Our company will do bulk emailing for your product/service. Addresses are extracted daily by four of our computers, which run 24 hours a day 7 days a week, scanning the net for new addresses. They are fresh! Over 36 million addresses on file. Our prices start at $150 per 1/2 million mailed. No more than 2 pages (50 lines), no porn and no foul language. We do not do targeted mailings at this price. Targeted mailins start at $200 per 100,000. There are no lower prices on the net. Your mailing can be done in a matter of hours. We have 6 computers sending and processing messages. 4 more computers extracting addresses 24/7. For the fastest service, cheapest prices and cleanest mailings call our processing and new accounts office at 904-282-0945, Monday - Friday 9 - 5 EST. Large corporate mailings available - ask for details. Email addresses available on CD, zipped text files. If interested, let our office know and will send our daily extracted list for only $250. Available on CD are over 30 million for ONLY $250. Overnight delivery $14, priority $5 and regular mail $3. New addresses are added daily. All domains available. No .edu,.mil and .gov. domains. Addresses are processed to remove any key names and flamers, who have notified our company and/or clients. $100 extra insures you of new addresses extracted up to 6 months. To have your name removed, call our processing office. Any negative responses will be dealt with accordingly. From rem-conf Thu Nov 06 03:51:40 1997 From rem-conf-request@es.net Thu Nov 06 03:51:39 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xTQQG-0005Du-00; Thu, 6 Nov 1997 03:48:28 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Thu, 6 Nov 1997 03:48:02 -0800 (PST) Message-Id: <199711061148.DAA00403@hille.msri.org> To: rem-conf@es.net From: Reply-to: n-bone@acod1.strl.nhk.or.jp Subject: NHK WORLD ONLINE X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: NHK WORLD ONLINE Date: Nov 11, 1997 Time: 00:00 GMT+0 1 hours Contact: n-bone@acod1.strl.nhk.or.jp URL: http://www.nhk.or.jp/nhkworld/event-e.html Description: NHK World will provide news in English on MBone on an experimental basis from November the 10th to the 23rd. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Thu Nov 06 03:51:40 1997 From rem-conf-request@es.net Thu Nov 06 03:51:40 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xTQLP-0005C1-00; Thu, 6 Nov 1997 03:43:27 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Thu, 6 Nov 1997 03:42:44 -0800 (PST) Message-Id: <199711061142.DAA00376@hille.msri.org> To: rem-conf@es.net From: Reply-to: n-bone@acod1.strl.nhk.or.jp Subject: NHK WORLD ONLINE X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: NHK WORLD ONLINE Date: Nov 10, 1997 Time: 20:00 JST 1 hours Contact: n-bone@acod1.strl.nhk.or.jp URL: http://www.nhk.or.jp/nhkworld/event-e.html Description: NHK World will provide news in English on MBone on an experimental basis from November the 10th to the 23rd. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Thu Nov 06 11:10:32 1997 From rem-conf-request@es.net Thu Nov 06 11:10:32 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xTXDj-0001BH-00; Thu, 6 Nov 1997 11:03:59 -0800 Date: Thu, 6 Nov 1997 13:03:49 -0600 (CST) From: Lawrence Henschen Message-Id: <199711061903.NAA03711@ceylon.ece.nwu.edu> To: rem-conf@es.net, sigmedia@bellcore.com, xtp-relay@cs.concordia.ca Subject: Call for Papers - ICAST98 X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list CALL FOR PAPERS, PANELS AND PARTICIPATION The 14th International Conference on Advanced Science and Technology (ICAST98) April 4-5, 1998 Lucent Technologies 2000 N. Naperville Road Naperville, Illinois, USA THEME: EXPLOITING LEADING EDGE TECHNOLOGIES FOR THE 21ST CENTURY Sponsors: Chinese Academic and Professional Association in Mid-America (CAPAMA) Lucent Technologies - Bell Labs Innovations Northwestern University University of Chicago Argonne National Laboratory Fermi National Accelerator Laboratory The emphasis of this conference is on practical solutions to important problems in today's technological world. The conference organizers intend to stimulate an environment that will enable effective information exchange among researchers, developers, scientists, engineers, and users of cutting edge technology. As technology rapidly advances, the once clear and separate domains of technology tend to merge and their boundaries become blurred. The more radical the change, the greater the risk of failure in cutting edge, high-tech development projects. Thus the focus of the conference is on the application and management of evolutionary and revolutionary leading edge technology in various high-tech domains. Topics include but are not limited to the following: A. Wireless Communications, PCS, Mobile Networks, Switching, Broadband and Networking Technologies B. Distributed Real-Time Systems and Services, Middleware, Software Technology and Tools C. Internet, Intranet, On-line Services, Electronic Commerce, Inferno, Java, Internet Phones and Mails D. Medical Sciences, Clinical Medicine Research, Genetic Engineering, Pharmaceutical Sciences and Biotechnology E. Management in High-Tech Environments, Economic Impact of Technologies, Information Management, Productivity and Quality Management, Process Engineering, Education and Training in Technologies More complete descriptions are given at the end of this message. Conference Chair: Professor Chung Lee Northwestern University 680 N. Lakeshore Drive Chicago, Illinois, 60611, USA Phone: (312) 908-2916 Fax: (312) 908-7275 Program Chair: Professor Lawrence Henschen Electrical and Computer Engineering Northwestern University Evanston, IL 60208, USA Phone: (847) 491-3338 Fax: (847) 467-3550 Email: henschen@ece.nwu.edu For conference information contact the Conference Chair or visit the web site at http://www.capama.org. Abstracts, papers and proposals for panels should be submitted to the Program Chair. Abstract/Paper Submission for Conference Papers: Technical papers will be presented on April 4-5, 1998, and will be published in the Conference Proceedings. Descriptions of original and significant research, the results of empirical studies, and innovative applications in the areas designated by the conference are solicited. We invite submissions from faculty, research scientists/engineers/ managers in industry and graduate students. Both abstracts and full papers will be reviewed for acceptance. Authors of accepted abstracts are expected to submit a full paper for a final review by the Program Committee. This procedure allows the submission of very current research which is near completion but may not be fully written up by the paper submission deadline. Please submit 5 copies of each paper or abstract. Submissions must use 10-point typeface, single-spacing, single column on one side of 8.5" x 11" bond paper with margins one inch on all four sides. The length of a full paper should be 10-15 pages, including figures, tables, and references. The abstract, 400-500 words, should be informative and contain (a) a title with the author's names(s) and affiliation(s); (b) the study's specific objective; (c) brief statements of methods, if pertinent; (d) a summary of the results; (e) the conclusions. A cover letter must accompany the abstract and contain the principal author's address, telephone number and email address for correspondence. Abstracts and full manuscripts in English must be delivered to the Program Chair by the submission dates listed below. Panels: Panel presentations are scheduled for April 4-5, 1998. Topics that examine innovative, controversial, or otherwise provocative issues are being sought. Proposals should be limited to 2 pages and include a 2-paragraph publishable biography of the panel organizer and a tentative list of panelists. Important Deadlines: Abstract Due: November 21, 1997 Paper Submission Due: December 5, 1997 Panel Proposals Due: December 5, 1997 Notification of Acceptance: December 22, 1997 Full/Final Paper (Camera-Ready) due: January 31, 1998 CALL FOR PAPER AREAS OF THE CONFERENCE Track A: WIRELESS, PCS, SWITCHING, and NETWORKING TECHNOLOGIES Global Wireless Communications Status (Opportunities/Problems, Implementations and Results, PACS standards), Personal Devices, Wireless Communications and the Internet (Applications and Services, and Ubiquitous Acces Used as a Model), Wireless ATM and the Information Highway, Advanced Intelligent Networking, Modulation Schemes and Efficiency, Signal Processing Advances, Access Technologies (Spread Spectrum, CDMA, Cable Telephone, TDMA/FDMA), Protocols for Data/Voice, CDPD, GSM, International Standards Update, Spectrum Allocation, Wireless/Wireline Integration, Public and Private Networks, Network Security, PCMCIA, Infrastructure (ATM, Frame Relay, SMDS), Role of Service Providers, Market Perceptions, Government's Role in the Network Development, Changing Roles of Workers. Track B: DISTRBUTED REAL-TIME SYSTEMS, MIDDLEWARE, and SOFTWARE TECHNOLOGIES Real-Time CORBA and Friends, Real-Time Distributed Object Technology, Open Architectures for QoS Control, Experimental Frameworks, Experimental Systems for the Deployment of Real-Time Services, Extending End-to-End Guarantees beyond the Network-Host Boundary, Modern Software Technologies, Programming Languages and Tools, Software Development Process, and Software Technology Transfer. Track C: INTERNET, INTRANET, and ON-LINE SERVICES Internet and Intranet Applications, Web Servers and Services, Internet Phones, Internet Mails, Electronic Commerce, Inferno, Java, C++ Programming Environments, HTML and CGI Programming, Web Security, Industry and University Environments, Best Practices in Internet and Intranet Applications, Design with State-of-the-Art Technologies. Track D: MEDICAL SCIENCES, CLINICAL MEDICINE, GENETIC ENGINEERING, PHARMACEUTICAL SCIENCES and BIOTECHNOLOGY Medical Engineering, Cartilage Biology and Arthritis, Cardiovascular Disorders, Tumor Cell Biology, Molecular Biology, Signal Transduction, Sport Medicine and Rehabilitation, Hormones and Growth Factors, Membrane Biophysics, Pharmaceutical Biotechnology in Drug Discovery, Natural Products in Drug Development, Novel Drug Delivery and Design, Pharmacokinetics of Biotechnology Products, Absorption and Transport of Drugs, Biological Engineering and Economics Track E: MANAGEMENT IN HIGH-TECH, ECONOMIC IMPACT, INFORMATION MANAGEMENT, PRODUCTIVITY AND QUALITY MANAGEMENT, EDUCATION IN TECHNOLOGY, PROCESS ENGINEERING Modern Information Management Technology, Information Infrastructures to Support High Tech R&D, Information Technology Impact on Economics, Information Process Engineering, Financial Factors in Leading Technology Development Environments, Modern Industrial Engineering Process Models and Simulation Techniques, Factors and Environments to Facilitate Information Technology from Research to Development to Production, Marketing Skills and Concerns for Information Technology From rem-conf Fri Nov 07 16:33:37 1997 From rem-conf-request@es.net Fri Nov 07 16:33:36 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xTyYB-0005mP-00; Fri, 7 Nov 1997 16:14:55 -0800 Message-Id: <199711080014.QAA26520@tweety.main.gnac.com> To: baylisa@baylisa.org, sage-members@usenix.org, rem-conf@es.net Cc: bigmac@baylisa.org Subject: BayLISA: Upcoming meeting: Larry Wall, "Second Prize: a Horse Designed by Two Committees" Date: Fri, 07 Nov 1997 16:14:04 -0800 From: Bryan McDonald X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list SPECIAL NOTE: The BayLISA board election will be held immediately before this meeting, starting at 7pm. Please come a few minutes early to register and vote. Candidate statements are available at http://www.baylisa.org/board/elections/1997 ------- The BayLISA group meets monthly to discuss topics of interest to systems and network administrators. The meetings are free and open to the public. Please feel free to redistribute this meeting announcement. BayLISA holds monthly meetings on the third Thursday of each month at 7:30 PM PST. We meet at Cisco Building J in San Jose, on Tasman Drive near First street. See www.baylisa.org for more information. The meetings are also broadcast via MBONE. Schedule ======== November 20, 1997: Second Prize: a Horse Designed by Two Committees, Larry Wall BayLISA Board elections Thursday, October 16, 1997, 7:30 PM: In this talk, Larry Wall will discuss the pitfalls and pratfalls of trying to get Java and Perl talking to each other (politely). Hence, he will talk about JPL (Java Perl Lingo), a hybrid language that lets you write Java methods with Perl implementations. (JPL is currently making its debut on O'Reilly's Perl Resource Kit, just released on November 7.) Please come if you like Java. Please come if you hate Java. Please come if you do both simultaneously. [Schedule subject to change] For further information on BayLISA, check out our web site: http://www.baylisa.org/ To get further information on the meeting location, you can also ftp it from ftp.baylisa.org:/BayLISA/location For any other information, please send email to: info@baylisa.org If you have any questions, please contact me or the info alias listed above. =============================================================================== Bryan McDonald bigmac@baylisa.org President president@baylisa.org BayLISA http://www.baylisa.org =============================================================================== From rem-conf Mon Nov 10 03:39:09 1997 From rem-conf-request@es.net Mon Nov 10 03:39:09 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xUrrP-0002G8-00; Mon, 10 Nov 1997 03:18:27 -0800 Date: Mon, 10 Nov 1997 12:18:21 +0100 From: pate@clarinet.u-strasbg.fr (David PATE) Message-Id: <9711101118.AA05020@clarinet.u-strasbg.fr> To: rem-conf@es.net Subject: Vat 4.0b2 for linux Cc: pate@clarinet.u-strasbg.fr X-Sun-Charset: US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Hi, Is there somebody who uses vat 4.0b2 under Linux 2.0.30. I've got no problem to compile it, but when I launch it, I've got a segmentation fault whith core dumped error. Could you help me to solve this problem? I have no problem to use rat, but I need vat to go with VCR that only know vat. Thanks in advance. DAVID ----- From rem-conf Mon Nov 10 07:48:09 1997 From rem-conf-request@es.net Mon Nov 10 07:48:09 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xUvwn-00048S-00; Mon, 10 Nov 1997 07:40:17 -0800 Message-Id: <199711101539.KAA13644@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce@ietf.org Cc: rem-conf@es.net From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-avt-mpeg-new-02.txt Date: Mon, 10 Nov 1997 10:39:58 -0500 Sender: cclark@cnri.reston.va.us X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Working Group of the IETF. Title : RTP Payload Format for MPEG1/MPEG2 Video Author(s) : D. Hoffman, G. Fernando, V. Goyal, R. Civanlar Filename : draft-ietf-avt-mpeg-new-02.txt Pages : 15 Date : 07-Nov-97 This memo describes a packetization scheme for MPEG video and audio streams. The scheme proposed can be used to transport such a video or audio flow over the transport protocols supported by RTP. Two approaches are described. The first is designed to support maximum interoperability with MPEG System environments. The second is designed to provide maximum compatibility with other RTP-encapsulated media streams and future conference control work of the IETF. This memo is a revision of RFC 2038, an Internet standards track pro- tocol, prepared for publication as a revised RFC. In this revision, the packet loss resilience mechanisms in Section 3.4 were extended to include additional picture header information required for MPEG2. A new section on security considerations for this payload type is added. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-avt-mpeg-new-02.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-avt-mpeg-new-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-avt-mpeg-new-02.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971107150217.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-avt-mpeg-new-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-avt-mpeg-new-02.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971107150217.I-D@ietf.org> --OtherAccess-- --NextPart-- From rem-conf Mon Nov 10 08:10:23 1997 From rem-conf-request@es.net Mon Nov 10 08:10:22 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xUwO2-0004oR-00; Mon, 10 Nov 1997 08:08:26 -0800 Date: Mon, 10 Nov 1997 17:07:54 +0100 From: pate@clarinet.u-strasbg.fr (David PATE) Message-Id: <9711101607.AA05517@clarinet.u-strasbg.fr> To: rem-conf@es.net Subject: Re: Vat 4.0b2 for linux X-Sun-Charset: US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list I thank all of you that answer me. The solution was to adopt a binary version that works. DAVID ----- From rem-conf Mon Nov 10 11:17:21 1997 From rem-conf-request@es.net Mon Nov 10 11:17:21 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xUzGC-0006JO-00; Mon, 10 Nov 1997 11:12:32 -0800 Message-Id: <199711101911.LAA27146@tweety.main.gnac.com> To: baylisa@baylisa.org, sage-members@usenix.org, rem-conf@es.net Cc: bigmac@baylisa.org Subject: BayLISA: Upcoming meeting: Larry Wall, "Second Prize: a Horse Designed by Two Committees" Date: Mon, 10 Nov 1997 11:11:26 -0800 From: Bryan McDonald X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list [[[[[ My appologies, I left last months dates in one place in the message below. To avoid confusion, here is the message again, with the correct dates in all locations. - bigmac ]]]]] SPECIAL NOTE: The BayLISA board election will be held immediately before this meeting, starting at 7pm. Please come a few minutes early to register and vote. Candidate statements are available at http://www.baylisa.org/board/elections/1997 ------- The BayLISA group meets monthly to discuss topics of interest to systems and network administrators. The meetings are free and open to the public. Please feel free to redistribute this meeting announcement. BayLISA holds monthly meetings on the third Thursday of each month at 7:30 PM PST. We meet at Cisco Building J in San Jose, on Tasman Drive near First street. See www.baylisa.org for more information. The meetings are also broadcast via MBONE. Schedule ======== November 20, 1997: Second Prize: a Horse Designed by Two Committees, Larry Wall BayLISA Board elections Thursday, November 20, 1997, 7:30 PM: In this talk, Larry Wall will discuss the pitfalls and pratfalls of trying to get Java and Perl talking to each other (politely). Hence, he will talk about JPL (Java Perl Lingo), a hybrid language that lets you write Java methods with Perl implementations. (JPL is currently making its debut on O'Reilly's Perl Resource Kit, just released on November 7.) Please come if you like Java. Please come if you hate Java. Please come if you do both simultaneously. [Schedule subject to change] For further information on BayLISA, check out our web site: http://www.baylisa.org/ To get further information on the meeting location, you can also ftp it from ftp.baylisa.org:/BayLISA/location For any other information, please send email to: info@baylisa.org If you have any questions, please contact me or the info alias listed above. =============================================================================== Bryan McDonald bigmac@baylisa.org President president@baylisa.org BayLISA http://www.baylisa.org =============================================================================== From rem-conf Tue Nov 11 03:56:46 1997 From rem-conf-request@es.net Tue Nov 11 03:56:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVEjY-0002zl-00; Tue, 11 Nov 1997 03:43:52 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:43:13 -0800 (PST) Message-Id: <199711111143.DAA01621@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 15, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:46 1997 From rem-conf-request@es.net Tue Nov 11 03:56:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVEkn-00030e-00; Tue, 11 Nov 1997 03:45:09 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:44:08 -0800 (PST) Message-Id: <199711111144.DAA01675@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 17, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:46 1997 From rem-conf-request@es.net Tue Nov 11 03:56:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVElh-00031I-00; Tue, 11 Nov 1997 03:46:05 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:44:48 -0800 (PST) Message-Id: <199711111144.DAA01729@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 19, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:46 1997 From rem-conf-request@es.net Tue Nov 11 03:56:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVElp-00031L-00; Tue, 11 Nov 1997 03:46:13 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:45:09 -0800 (PST) Message-Id: <199711111145.DAA01756@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 20, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:46 1997 From rem-conf-request@es.net Tue Nov 11 03:56:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVEkf-00030c-00; Tue, 11 Nov 1997 03:45:01 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:43:49 -0800 (PST) Message-Id: <199711111143.DAA01648@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 16, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:47 1997 From rem-conf-request@es.net Tue Nov 11 03:56:46 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVElZ-00031D-00; Tue, 11 Nov 1997 03:45:57 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:45:29 -0800 (PST) Message-Id: <199711111145.DAA01783@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 21, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:47 1997 From rem-conf-request@es.net Tue Nov 11 03:56:47 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVEmm-00032B-00; Tue, 11 Nov 1997 03:47:12 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:46:12 -0800 (PST) Message-Id: <199711111146.DAA01837@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 23, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:48 1997 From rem-conf-request@es.net Tue Nov 11 03:56:47 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVEme-000325-00; Tue, 11 Nov 1997 03:47:04 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:46:33 -0800 (PST) Message-Id: <199711111146.DAA01864@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 24, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:48 1997 From rem-conf-request@es.net Tue Nov 11 03:56:47 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVEkX-00030V-00; Tue, 11 Nov 1997 03:44:53 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:44:28 -0800 (PST) Message-Id: <199711111144.DAA01702@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 18, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 03:56:48 1997 From rem-conf-request@es.net Tue Nov 11 03:56:48 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVEmW-00031o-00; Tue, 11 Nov 1997 03:46:56 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 03:45:51 -0800 (PST) Message-Id: <199711111145.DAA01810@hille.msri.org> To: rem-conf@es.net From: Reply-to: mc-mbone@iij-mc.co.jp Subject: Saga Hot Air Balloon World Championship X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Saga Hot Air Balloon World Championship Date: Nov 22, 1997 Time: 07:00 JST 12 hours Contact: mc-mbone@iij-mc.co.jp URL: http://www.saganet.ne.jp/balloon/ Description: Please try xdma://tkbbc0.iij-mc.co.jp/balloon-m.ply from Xing StreamWorks Player. We transmit by StreamWorks v3.0. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 04:04:21 1997 From rem-conf-request@es.net Tue Nov 11 04:04:21 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVF2i-0005Nz-00; Tue, 11 Nov 1997 04:03:40 -0800 Date: Tue, 11 Nov 1997 12:04:27 +0000 (GMT) From: Graeme Wood Reply-To: Graeme.Wood@ucs.ed.ac.uk To: rem-conf@es.net Subject: Re: Saga Hot Air Balloon World Championship Message-ID: X-Department: "Unix Systems Support, Computing Services" X-Organisation: "The University of Edinburgh" X-URL: "http://ugwww.ucs.ed.ac.uk/People/Graeme.Wood/" X-Phone: +44 131 650 5003 X-Fax: +44 131 650 6552 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list I have just received 10 almost identical announcements about this. Could the schedule software at http://www.msri.org not be a little less brain dead and handle ranges of dates a bit better? At the moment it seems you have to insert a separate event on every date and send out mail for each. ============================================================================= Graeme Wood Email: Graeme.Wood@ucs.ed.ac.uk Unix Systems Support Phone: +44 131 650 5003 The University of Edinburgh Fax: +44 131 650 6552 ============================================================================= From rem-conf Tue Nov 11 06:11:28 1997 From rem-conf-request@es.net Tue Nov 11 06:11:28 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVGtK-0003dm-00; Tue, 11 Nov 1997 06:02:06 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 11 Nov 1997 06:01:33 -0800 (PST) Message-Id: <199711111401.GAA01926@hille.msri.org> To: rem-conf@es.net From: Reply-to: annemari@mcg.gla.ac.uk Subject: JETAI'97 Conference X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: JETAI'97 Conference Date: Nov 13, 1997 Time: 09:00 GMT 2 hours Contact: annemari@mcg.gla.ac.uk URL: http://www.jetai.mcg.gla.ac.uk/ Description: The theme of JETAI'97 is 'New ways of communicating' Sessions will cover a wide range of topics including network technology and applications, java, telemedicine, and videoconferencing. For a full conference agenda please check out the conference web site. http://www.jetai.mcg.gla.ac.uk/jetai97.html mbone broadcast schedule http://www.msri.org/mbone From rem-conf Tue Nov 11 08:27:16 1997 From rem-conf-request@es.net Tue Nov 11 08:27:15 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVIzm-0004xD-00; Tue, 11 Nov 1997 08:16:54 -0800 Date: Tue, 11 Nov 1997 11:15:23 -0500 (EST) From: Queene Cottingham To: annemari@mcg.gla.ac.uk cc: rem-conf@es.net Subject: Re: JETAI'97 Conference In-Reply-To: <199711111401.GAA01926@hille.msri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list too many announcements re balloons Queene From rem-conf Tue Nov 11 10:40:46 1997 From rem-conf-request@es.net Tue Nov 11 10:40:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVL90-0006Mv-00; Tue, 11 Nov 1997 10:34:34 -0800 To: rem-conf@es.net Subject: Re: Saga Hot Air Balloon World Championship From: YAMAMOTO Bunji In-Reply-To: Your message of "Tue, 11 Nov 1997 12:04:27 +0000 (GMT)" References: X-Mailer: Mew version 1.55 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19971112033344B.bunji@iij-mc.co.jp> Date: Wed, 12 Nov 1997 03:33:44 +0900 Sender: YAMAMOTO Bunji X-Dispatcher: impost version 0.99i (Apr. 6, 1997) Lines: 15 X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list In Message-ID: , Graeme Wood writes; > I have just received 10 almost identical announcements about this. Could I forget to check out "to send rem-conf" for nine times. > the schedule software at http://www.msri.org not be a little less brain > dead and handle ranges of dates a bit better? At the moment it seems you > have to insert a separate event on every date and send out mail for each. I hope the software at msri.org could handle spreading schedule such as this sesssion. --bunji From rem-conf Tue Nov 11 14:17:47 1997 From rem-conf-request@es.net Tue Nov 11 14:17:46 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVOYI-0000Pb-00; Tue, 11 Nov 1997 14:12:54 -0800 Message-Id: <3.0.5.16.19971111150527.292f9b54@shell7.ba.best.com> X-Sender: rsf@shell7.ba.best.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (16) Date: Tue, 11 Nov 1997 15:05:27 To: Graeme.Wood@ucs.ed.ac.uk From: Ross Finlayson Subject: Re: Saga Hot Air Balloon World Championship Cc: rem-conf@es.net In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list >I have just received 10 almost identical announcements about this. Could >the schedule software at http://www.msri.org not be a little less brain >dead and handle ranges of dates a bit better? Why do we even need email at all? This is why we have SDP. People can just read the announcements when they show up in their SDP browser. Ross. From rem-conf Tue Nov 11 14:38:51 1997 From rem-conf-request@es.net Tue Nov 11 14:38:51 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVOvO-00010x-00; Tue, 11 Nov 1997 14:36:46 -0800 Message-Id: <199711112235.OAA09435@shell3.ba.best.com> Subject: Re: Saga Hot Air Balloon World Championship In-Reply-To: <3.0.5.16.19971111150527.292f9b54@shell7.ba.best.com> from Ross Finlayson at "Nov 11, 97 03:05:27 pm" To: finlayson@lvn.com (Ross Finlayson) Date: Tue, 11 Nov 1997 14:35:38 -0800 (PST) Cc: Graeme.Wood@ucs.ed.ac.uk, rem-conf@es.net From: phil@bolthole.com (Philip Brown) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list [ Ross Finlayson writes ] > >I have just received 10 almost identical announcements about this. Could > >the schedule software at http://www.msri.org not be a little less brain > >dead and handle ranges of dates a bit better? > > Why do we even need email at all? This is why we have SDP. People can > just read the announcements when they show up in their SDP browser. because some people would like to set up a temporary firewall relay for specific MBONE sessions, and not leave SDP externally connected all the time. From rem-conf Tue Nov 11 16:09:33 1997 From rem-conf-request@es.net Tue Nov 11 16:09:32 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVQHE-00022M-00; Tue, 11 Nov 1997 16:03:24 -0800 X-Sender: wieselth@pop.itd.nrl.navy.mil Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 11 Nov 1997 18:57:59 -0500 To: enternet@bbn.com, tccc@ieee.org, dbworld@cs.wisc.edu, end2end-interest@isi.edu, f-troup@codex.cis.upenn.edu, cost237-transport@comp.lancs.ac.uk, reres@laas.fr, hipparch@sophia.inria.fr, xtp-relay@cs.concordia.ca, rem-conf@es.net, sigmedia@bellcore.com, mobile-ip@tadpole.com, cellular@comnets.rwth-aachen.de, ieeetcpc@ccvm.sunysb.edu, cnom@maestro.bellcore.com, commsoft@cc.bellcore.com, multicomm@cc.bellcore.com, epr@infotest.com, mouftah@eleceng.ee.queensu.ca, wieselthier@itd.nrl.navy.mil, Hossam.Afifi@enst-bretagne.fr, grash@taz.ho.att.com, baker@itd.nrl.navy.mil, baras@isr.umd.edu, echong@ecn.purdue.edu, cidon@ee.technion.ac.il, fkonst@tinos.mobile.ece.ntua.gr, daneshmand@att.com, hadidi@frcu.eun.eg, elkhamy@alex.eun.eg, aly_elrefaie@hp.com, melsayed@attmail.com, tony@glue.umd.edu, jj@cse.ucsc.edu, evagelos@eng.umd.edu, drjeff1@juno.com, b-hajek@uiuc.edu, jerry@ece.concordia.ca, ckroell@esoc.esa.de, mmalek@lucent.com, maly@cs.odu.edu, moskowit@itd.nrl.navy.mil, nassar@ems.att.com, charles.perkins@Corp.sun.com, cspitsil@turing.cs.ucy.ac.ay, pursley@eng.clemson.edu, saleh@research.att.com, savolaine@ems.att.com, moshe@asterix.technion.ac.il, sykas@cs.ntua.gr, leandros@isr.umd.edu, theolog@cs.ntua.gr, tohme@res.enst.fr, nzervos@lucent.com, aheddaya@infolibria.com From: Jeff Wieselthier Subject: CFP: ISCC'98 Deadline extended to November 21 X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Dear Colleagues, In response to many requests, we have extended the submission deadline for ISCC'98 until November 21, 1997. We hope to see you in Athens! Hussein Mouftah and Jeffrey E. Wieselthier Technical Program Co-Chairs, ISCC'98 --------------------------------------------------------------- Call for Papers The Third IEEE Symposium on Computers and Communications (ISCC'98) Athens, Greece June 30--July 2, 1998 Sponsored by IEEE Communications Society and IEEE Computer Society(*) The fast growing convergence between communications and computer technologies is having an increasingly profound impact on information and networking systems. This third annual event will provide a technical forum for experts >from industry and academia to exchange ideas and present results of ongoing research in the areas listed below. You are invited to submit a full paper, or a proposal for a panel, invited session, or tutorial, related to the following topics: - High Speed Networks, ATM/SONET/SDH - Multimedia Networking, Services and Applications - Intelligent Networks and Network Planning - Optical Systems and Networks - Network Interoperability and Internetworking - Internet Services - Electronic Commerce - Mobile Communications and Nomadic Computing - Wireless Networks - Access Networks - Satellite Communications - Simulation, Modeling, and Performance Evaluation - Network Management and Operations - Control and Optimization Methods for Communication Systems and Networks - Network Reliability and Quality of Service - Signal Processing in Communications and Networking - Distributed Systems - Software Engineering - Fault Tolerant Systems - Security, Privacy and Information Access - Computer Systems and Applications - Intelligent Highway Please send four copies of your original paper (not to exceed 20 double-spaced pages) to reach either Technical Program Co-Chair at the addresses below by November 21, 1997. Keywords should be included. The paper should clearly indicate the complete postal and electronic mailing addresses, as well as the phone and fax numbers of the corresponding author. Prof. Hussein Mouftah Tech Program Co-Chair, ISCC'98 Department of Electrical Engineering Queen's University Kingston, Ontario Canada K7L 3N6 Tel: +1 (613) 545-2934 Fax: +1 (613) 545-6615 mouftah@eleceng.ee.queensu.ca Dr. Jeffrey E. Wieselthier Tech Program Co-Chair, ISCC'98 Code 5521 Naval Research Laboratory 4555 Overlook Ave. SW Washington, DC 20375 USA Tel: +1 (202) 767-3043 Fax: +1 (202) 767-1191 wieselthier@itd.nrl.navy.mil ------------------------------------------------------------------------ Important Dates: - November 21, 1997: Paper submission deadline - February 15, 1998: Notifications of acceptance mailed to authors - March 15, 1998: Final camera-ready manuscripts due. ------------------------------------------------------------------------ General Chair: - P. A. Probst, Swiss Telecom, Switzerland Vice-chair: - H. Mouftah, Queens Univ, Canada. Steering Committee: - H. Abdel-Wahab, Old Dominion Univ, USA - T. N. Saadawi, City Univ of N.Y., USA - M. H. Sherif, AT&T Labs, France - G. Stassinopoulos, Nat Tech Univ of Athens, Greece - A. Tantawy, IBM T.J. Watson Research Ctr., USA Technical Program Commitee: - H. Mouftah, Queens Univ, Canada, (Co-Chair) - J. E. Wieselthier, Naval Res Lab, USA, (Co-Chair) - H. Afifi, ENST-Bertagne, France - J. Ash, AT&T Labs, USA - D. Baker, Naval Research Lab, USA - J. Baras, Univ of Maryland, USA - E. Chong, Purdue University, USA - I. Cidon, Technion, Israel - P. Constantinou, Nat Tech Univ of Athens, Greece - M. Daneshmand, AT&T Labs, USA - M. Elhadidi, Cairo Univ, Egypt - S. Elkhamy, Alexandria Univ, Egypt - A. Elrefaie, HP Labs, USA - M. Elsayed, AT&T Labs, USA - A. Ephremides, Univ of Maryland, USA - J. Garcia-Luna, Univ of CA, Santa Cruz, USA - E. Geraniotis, University of Maryland, USA - J. Gluck, US Patent & Trademark Office, USA - B. Hajek, University of Illinois, USA - J. Hayes, Concordia University, Canada - C. Kroell, European Space Agency, Germany - M. Malek, Lucent Technologies, USA - K. Maly, Old Dominion Univ, USA - I. Moskowitz, Naval Research Lab, USA - M. Nassar, AT&T Labs, USA - C. Perkins, Sun Microsystems, USA - A. Pitsillides, Univ of Cyprus, Cyprus - M. Pursley, Clemson University, USA - A. Saleh, AT&T Research, USA - C. Savolaine, AT&T Labs, USA - M. Sidi, Technion, Israel - E. Sykas, Nat Tech Univ of Athens, Greece - A. Tantawi, IBM T.J. Watson Research Ctr., USA - L. Tassiulas, University of Maryland, USA - M. Theologou, Nat Tech Univ of Athens, Greece - S. Thome, ENST-Paris, France - N. Zervos, Lucent Technologies, USA Registration & Finance Co-Chairs: - S. Elmaghraby, Univ of Louisville, USA - R. Ammar, Univ of Connecticut, USA - M. H. Fallah, Lucent Technologies, USA Local Committee - G. Stassinopoulos, NTU of Athens, Greece (Chair) - P. Constantinou, NTU of Athens, Greece - V. Daskalou, AUEB, Greece Tutorials Committee - H. Akhtar, AT&T Labs, USA (Chair) - W. Makky, FAA, USA - E. Sykas, Nat Tech Univ of Athens, Greece Publicity Committee - A. Heddaya, Boston University, USA (Chair) - S. El Hennaoui, ENST, France - N. Pavlidou, AUTH, Greece - K. Shenawy, AAST, Egypt ------------------------------------------------------------------------ * Technical Committee on Simulation ------------------------------------------------------------------------ Conference history - First ISCC, June 27-29 1995, Alexandria, Egypt - Second ISCC, July 1-3 1997, Alexandria, Egypt - Third ISCC, June 30-July 2 1998, Athens, Greece ------------------------------------------------------------------------ Web site: http://www.cs.bu.edu/ftp/amass/ISCC/ ------------------------------------------------------------------------ Maintained by Abdelsalam Heddaya. From rem-conf Tue Nov 11 16:11:02 1997 From rem-conf-request@es.net Tue Nov 11 16:11:01 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVQOB-00028z-00; Tue, 11 Nov 1997 16:10:35 -0800 Message-ID: <81B710B77B0DD111B3FC00805FC1E69D0901E1@MAILMAN> From: Ari Ollikainen To: "'finlayson@lvn.com '" , "'phil@bolthole.com '" Cc: "'Graeme.Wood@ucs.ed.ac.uk '" , "'rem-conf@es.net '" Subject: RE: Saga Hot Air Balloon World Championship Date: Tue, 11 Nov 1997 04:07:32 -0800 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list >> >>> Why do we even need email at all? This is why we have SDP. People can > just read the announcements when they show up in their SDP browser. > >because some people would like to set up a temporary firewall relay for >specific MBONE sessions, and not leave SDP externally connected all the time. Then the "some people" should solve their problem in some other way WITHOUT using the rem-conf list as an SDP substitute! Irked with the fact that Steve and I could never correct the misperception that this list was for MBONE announcements... From rem-conf Tue Nov 11 23:08:20 1997 From rem-conf-request@es.net Tue Nov 11 23:08:19 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVWpC-0004zq-00; Tue, 11 Nov 1997 23:02:54 -0800 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 12 Nov 1997 08:00:24 +0100 To: atm1:; From: Pascal LORENZ Subject: ICATM98 X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Dear Colleague, We have enclosed the CFP for ICATM'98 below. Please feel free to circulate the CFP to interested colleagues. Please accept our sincere apologies if you receive multiple copies of this CFP. Best Regards, -------------------------------------------------------------------- CALL FOR PAPERS IEEE International Conference on ATM ICATM'98 June 22-24, 1998 - Colmar, France GENERAL INFORMATION The 1998 International Conference on ATM (ICATM'98) is Technical Co-Sponsored by IEEE/ EN. ICATM'98 is organized by academic, research and industrial societies will be held at the Technical Institute, Colmar, part of the University of Haute Alsace, France from Monday June 22, 1998 to Wednesday June 24, 1998. The city of Colmar is ideally situated in the eastern part of France, near the German and Swiss borders. The city of Colmar has been working on its own Metropolitan Area Network (MAN) project, called OASICE, including LAN interconnection, PBX interconnection and interactive video. An exhibition illustrating these topics will be organized for industrial companies and development research institutes. In order to encourage closer interaction between academic and industrial ATM research communities, we solicit both academic research papers and industrial contributions. Papers should describe significant research as well as innovative development and applications relating to ATM. IP or ATM who will be the winner ? TOPICS OF SPECIAL INTEREST Topics of interest include, but are not limited to the following: MPOA LAN Emulation IP over ATM VLANs High-Speed Routing IP Switching, Tag Switching, Fast IP, IP Navigator, Aris ... I-PNNI NHRP MPLS IP and ATM over xDSL Multicast ATM and Internet/Intranet Wireless ATM IP and ATM Telephony Practical experiences results Migration from IP to ATM User applications These topics can be discussed in term of concepts, state of the art, standards, implementations, performance, security and confidentiality, traffic management, running experiments, QoS (Quality of Service) and applications. INSTRUCTIONS FOR AUTHORS Mail four papers versions and a postscript electronic copie of a 2000-word extended abstract summarizing an original work. All the manuscripts must be written in English. The top of the first page of each paper should include the title of the paper, authors' name, position, address, telephone and fax numbers, e-mail of the author responsible for correspondence and a list of four keywords. The deadline for submission of all extended abstracts is December 1, 1997 with notification of acceptance by January 15, 1998. Submission of camera-ready paper is by March 1, 1998. Authors of accepted papers will be invited to submit full-length manuscripts for inclusion in the proceedings. All submitted papers should be sent to the following address: Pascal LORENZ IUT / GTR 34 rue du Grillenbreit 68008 Colmar, France Phone: 33 (0)389202366 Fax: 33 (0)389202359 E-mail: lorenz@colmar.uha.fr Check our Web page at http://iutsun1.colmar.uha.fr/ICATM98.html for the latest information concerning the conference. TUTORIALS AND WORKSHOPS Tutorials and workshops provide overviews of current high interest topics. Proposals for half of full day tutorials are due by November 1, 1997. ORGANIZATION OF ICATM'98 International Advisory Committee: K. Begain (Jordain) - Mu'tah University D. Bonjour (France) - CNET J.P. Coudreuse (France) - Mitsubishi B. Gavish (USA) - Vanderbilt University J. Halpern (USA) - Newbridge R. Israel (France) - IEEE P. Lorenz (France) - University of Haute Alsace J.J. Pansiot (France) - University of Strasbourg M. Potts (Switzerland) - Martel Z. Mammeri (France) - University of Le Havre S. Moyer (USA) - Bellcore R. Muraine (France) - Newbridge G. Pujolle (France) - University of Versailles-Saint-Quentin S. Rao (Switzerland) - Ascom A. Reid (England) - British Telecom S. Ritzenthaler (France) - Newbridge P. Rolin (France) - ENST Bretagne R. Saracco (Italy) - CSELT G. Swallow (USA) - Cisco R. Schneider (France) - University of Strasbourg H. Tobiet (France) - Clemessy Local Organizing Committee: R. Blaes P. Lorenz H. Tobiet M. Toussaint IMPORTANT DATES Extended Abstract due: December 1, 1997 Notification of acceptance: January 15, 1998 Deadline for full-length camera-ready manuscript: March 1, 1998 From rem-conf Wed Nov 12 07:01:26 1997 From rem-conf-request@es.net Wed Nov 12 07:01:25 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVdwf-0000F2-00; Wed, 12 Nov 1997 06:39:05 -0800 Sender: plageman@unik.no Message-ID: <3469BBFA.E95F587B@unik.no> Date: Wed, 12 Nov 1997 15:23:54 +0100 From: Thomas Plagemann Organization: University of Oslo X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: alg@comm.toronto.edu, apc@ee.nthu.edu.tw, apc_members@hornbill.ee.nus.sg, cabernet-general@newcastle.ac.uk, ccrc@dworkin.wustl.edu, cellular@comnets.rwth-aachen.de, cnom@maestro.bellcore.com, commsoft@cc.bellcore.com, comsoc-chapters@ieee.org, comsoc-gicb@ieee.org, comsoc.tac@tab.ieee.org, comswtc@gmu.edu, cost237-transport@comp.lancs.ac.uk, ctc-members@redbank.tinac.com, end2end-interest@ISI.EDU, enternet@bbn.com, f-troup@codex.cis.upenn.edu, fokus-user@fokus.gmd.de, g-troup@ccrc.wustl.edu, giga@tele.pitt.edu, hipparch@sophia.inria.fr, ieee_rtc_list@cs.tamu.edu, ieeetcpc@ccvm.sunysb.edu, isadsoc@fokus.gmd.de, itc@fokus.gmd.de, modern-heuristics@uk.ac.mailbase, multicomm@cc.bellcore.com, osimcast@bbn.com, rem-conf@es.net, reres@laas.fr, sb.all@ieee.org, sc6wg4@ntd.comsat.com, sigmedia@bellcore.com, tccc@ieee.org, xtp-relay@cs.concordia.ca, cost237-teleservices@comp.lancs.ac.uk, tcplw@bsdi.com CC: idms98@unik.no Subject: CfP IDMS'98 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Dear Collegues, please find below the Call for papers for IDMS'98: 5th International Workshop on Interactive Distributed Multimedia Systems and Telecommunication Services 8. - 11. September 1998, Oslo, Norway Online information for IDMS'98 (including the CfP) can be found at: http://www.unik.no/~idms98 You will be doing us a great favor if you disseminate the this Call for papers among your interested colleagues. Please accept our apologies if you receive multiple copies of this announcement. Best regards, Vera Goebel Thomas Plagemann _________________________________________________________________________= _ | | Organization Committee IDMS'98 | | 5th International Workshop on Interactive Distributed Multimedia | Systems and Telecommunication Services | Oslo, Norway, 1998 | | UniK - Center for Technology at Kjeller | University of Oslo | P.O. Box 70, N-2007 Kjeller, Norway | | e-mail: idms98@unik.no | WWW: http://www.unik.no/~idms98 |________________________________________________________________________= __ Call for Papers IDMS'98 5th International Workshop on Interactive Distributed Multimedia Systems and Telecommunication Services 8. - 11. September 1998, Oslo, Norway The Fifth International Workshop on Interactive Distributed Multimedia Systems and Telecommunication Services follows the successful IDMS workshops held 1997 in Darmstadt and 1996 in Berlin. The purpose of this workshop is to bring together researchers, developers, and practitioners >from academia and industry. The workshop serves as a forum for discussion, presentation, and exploration of technologies and their advances in the broad field of interactive distributed multimedia systems and telecommunication services -- ranging from basic system technologies such as networking and operating system support to all kinds of teleservices and distributed multimedia applications. Case studies and papers describing experimental work are especially welcome. Relevant topics include, but are not limited to =B7 High-speed/ATM networks =B7 Mobile multimedia systems =B7 Multimedia over sattelite =B7 Multimedia middelware =B7 Quality of service issues =B7 Media scaling =B7 Resource management =B7 Protocol design and implementation =B7 Distributed multimedia database systems =B7 Development tools for distributed multimedia applications =B7 Multimedia-specific intelligent agents =B7 Computer supported collaborative work =B7 Distributed virtual reality systems =B7 Distance education =B7 Conferencing =B7 Digital libraries =B7 Interactive television =B7 Video-on-demand systems =B7 Compression algorithms IDMS'98 will consist of a three day technical program, a full day of tutorials, and demonstrations during the workshop. In order to keep the flavour of a workshop, the number of participants will be restricted. Furthermore, we encurage contributions in form of full papers and position papers. Full papers are expected to describe innovative and significant work. The purpose of position papers is to provide a seed for debate and discussion. Position papers enable researchers to present exciting ongoing work in early stages, suggestions for future directions, and concerns about current developments. Both types of papers will be reviewed by the program committee and printed in the workshop proceedings. The proceedings will be published in the Springer LNCS series and will be available during the workshop. It is intended to forward selected papers to a special issue of the "Computer Communications" Journal. Information for authors: Authors are invited to submit full papers and position papers for review. Submitted manuscripts must describe original work (not submitted or published elsewhere). Full papers must not be longer than 20 double spaced pages and position papers must not be longer than 8 double spaced pages. Both types of papers should contain an abstract of approximately 300 words, and include title, authors and affiliations. The submission process of papers will be handled electronically. Detailed description of the electronic submission procedures is available on the IDMS'98 web page: http://www.unik.no/~idms98. Authors without web access may send mail to idms98@unik.no requesting electronic submission information. Authors unable to submit electronically are invited to send 5 copies of their contribution to one of the workshops chairs ATTN: IDMS'98. Important dates: Submission due: February 1, 1998 Notification of acceptance: April 15, 1998 Camera ready version: May 15, 1998 Workshop: September 9 - 11, 1998 Program co-chairs: Vera Goebel and Thomas Plagemann UniK - Center for Technology at Kjeller, University of Oslo, P.O. Box 70, N-2007 Kjeller, Norway Email: {goebel; plageman}@unik.no, Phone: +47/63.81.45.70, Fax: +47/63.81.81.46 Program Committee: F. A. Aagesen, NTNU Trondheim, Norway H. Affifi, ENST Bretagne, France E. Biersack, Institut Eur=E9com, France G. Bochmann, University of Montreal, Canada B. Butscher, DeTeBerkom, Germany A. T. Campbell, Columbia University, USA S. Chanson, Hong Kong University of Science & Technology, HK L. Delgrossi, University Cattolica Piacenza, Italy M. Diaz, LAAS-CNRS, France F. Eliassen, University of Troms=F8, Norway W. Effelsberg, University Mannheim, Germany D. Ferrari, University Cattolica Piacenza, Italy J.-P. Hubaux, EPFL Lausanne, Switzerland D. Hutchison, Lancaster University, UK W. Kalfa, TU Chemnitz, Germany T. D. C. Little, Boston University, USA E. Moeller, GMD FOKUS, Germany K. Nahrstedt, University of Illinois, USA G. Parulkar, Washington University St. louis, USA B. Pehrson, KTH Stockholm, Sweden S. Pink, SICS, Sweden B. Plattner, ETH Zurich, Switzerland H. Scholten, University of Twente, Netherlands R. Steinmetz, GMD, Germany H. Tokuda, Keio University, Japan L. Wolf, TH Darmstadt, Germany M. Zitterbart, TU Braunschweig, Germany From rem-conf Wed Nov 12 09:20:33 1997 From rem-conf-request@es.net Wed Nov 12 09:20:33 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVgKg-0001Te-00; Wed, 12 Nov 1997 09:12:02 -0800 Date: Wed, 12 Nov 1997 09:11:54 -0800 From: almeroth@cs.ucsb.edu (Kevin C. Almeroth) Message-Id: <199711121711.JAA10506@jackson.cs.ucsb.edu> To: rem-conf@es.net Subject: Cisco Config [Q] X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list The problem I've got reminds me of what I think I've heard discussed on this list before... On the upstream side of my Cisco router (11.1) I'm hearing MBone traffic just fine. On the downstream side, on my local net, I can join a group, and then see traffic, but only for a short period of time. Apparently, some sort of timeout happens and interaction with IGMP is not happy. Now, I didn't want to send e-mail to cisco-support since this might be an easy problem. And second, has there been any progress on a FAQ-like document with pointers for problems of this sort? =Kevin From rem-conf Wed Nov 12 09:45:07 1997 From rem-conf-request@es.net Wed Nov 12 09:45:07 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVgjp-00021m-00; Wed, 12 Nov 1997 09:38:01 -0800 Message-Id: <199711121734.JAA10004@alicia.nttlabs.com> To: almeroth@cs.ucsb.edu (Kevin C. Almeroth) Cc: rem-conf@es.net Subject: Re: Cisco Config [Q] Reply-to: sumisu@nttlabs.com (Jeffrey D. Smith) In-reply-to: Your message of "Wed, 12 Nov 1997 09:11:54 PST" References: <199711121711.JAA10506@jackson.cs.ucsb.edu> Date: Wed, 12 Nov 1997 09:34:21 -0800 From: Jeff Smith X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Isn't this the routing table flooding bug? |>The problem I've got reminds me of what I think I've heard discussed on |>this list before... |> |> On the upstream side of my Cisco router (11.1) I'm hearing MBone |> traffic just fine. On the downstream side, on my local net, I can |> join a group, and then see traffic, but only for a short period of |> time. Apparently, some sort of timeout happens and interaction with |> IGMP is not happy. |> |>Now, I didn't want to send e-mail to cisco-support since this might be |>an easy problem. And second, has there been any progress on a FAQ-like |>document with pointers for problems of this sort? |> |>=Kevin |> From rem-conf Wed Nov 12 09:46:01 1997 From rem-conf-request@es.net Wed Nov 12 09:46:01 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVgkk-00022E-00; Wed, 12 Nov 1997 09:38:58 -0800 Message-Id: <3.0.32.19971112093833.00755100@ideal.jf.intel.com> X-Sender: bstrahm@ideal.jf.intel.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 12 Nov 1997 09:38:34 -0800 To: almeroth@cs.ucsb.edu (Kevin C. Almeroth), rem-conf@es.net From: Bill Strahm Subject: Re: Cisco Config [Q] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list I don't know if this is what you are looking for but MBoned has a draft out ftp://ftp.ietf.org/internet-drafts/draft-ietf-mboned-mdh-00.txt It's title is Multicast Debugging Handbook by Thaler and Aboba. I don't know if it will solve your problem though Bill At 09:11 AM 11/12/97 -0800, you wrote: >The problem I've got reminds me of what I think I've heard discussed on >this list before... > > On the upstream side of my Cisco router (11.1) I'm hearing MBone > traffic just fine. On the downstream side, on my local net, I can > join a group, and then see traffic, but only for a short period of > time. Apparently, some sort of timeout happens and interaction with > IGMP is not happy. > >Now, I didn't want to send e-mail to cisco-support since this might be >an easy problem. And second, has there been any progress on a FAQ-like >document with pointers for problems of this sort? > >=Kevin > > > Bill Strahm |Programming today is a race between bstrahm@ |software engineers striving to build ibeam.intel.com|bigger and better idiot-proof programs, (503) 264-4632 |and the Universe trying to produce |bigger and better idiots. So far, the |Universe is winning.--Rich Cook I am not speaking for Intel. And Intel rarely speaks for me From rem-conf Wed Nov 12 10:29:06 1997 From rem-conf-request@es.net Wed Nov 12 10:29:05 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVhSy-0003GR-00; Wed, 12 Nov 1997 10:24:40 -0800 Message-ID: <3469F434.CAD98B5@icast.com> Date: Wed, 12 Nov 1997 10:23:49 -0800 From: Peter Tebault Organization: ICAST Corporation X-Mailer: Mozilla 4.03 [en] (WinNT; I) MIME-Version: 1.0 To: "Kevin C. Almeroth" CC: rem-conf@es.net Subject: Re: Cisco Config [Q] References: <199711121711.JAA10506@jackson.cs.ucsb.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Kevin, If your problem has to do with Windows 95, it may be that you are experiencing an IGMP timeout bug in Winsock2. The document below describes the problem and supplies a fix (I haven't tried it myself). http://premium.microsoft.com/support/kb/articles/q174/0/95.asp -Pete- Kevin C. Almeroth wrote: > The problem I've got reminds me of what I think I've heard discussed on > this list before... > > On the upstream side of my Cisco router (11.1) I'm hearing MBone > traffic just fine. On the downstream side, on my local net, I can > join a group, and then see traffic, but only for a short period of > time. Apparently, some sort of timeout happens and interaction with > IGMP is not happy. > > Now, I didn't want to send e-mail to cisco-support since this might be > an easy problem. And second, has there been any progress on a FAQ-like > document with pointers for problems of this sort? > > =Kevin From rem-conf Wed Nov 12 13:00:38 1997 From rem-conf-request@es.net Wed Nov 12 13:00:38 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVjl5-0004wI-00; Wed, 12 Nov 1997 12:51:31 -0800 Date: Wed, 12 Nov 1997 12:50:30 -0800 (PST) From: Karl Auerbach Reply-To: karl@precept.com To: "Kevin C. Almeroth" cc: rem-conf@es.net Subject: Re: Cisco Config [Q] In-Reply-To: <3469F434.CAD98B5@icast.com> Message-ID: X-X-Sender: karl@big-bear.precept.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list > If your problem has to do with Windows 95, it may be that you are > experiencing an IGMP timeout bug in Winsock2. > > The document below describes the problem and supplies a fix (I haven't > tried it myself). > > http://premium.microsoft.com/support/kb/articles/q174/0/95.asp If this is the patch to the Winsock 2.0 SDK, then, yes, it does seem to work. The initial problem only exists for those who have put the Winsock 2.0 SDK onto their Win 95 box(es). One usually doesn't do that by accident. ;-) Anyway, the good news about that SDK is that it does IGMPv2, and hence has the "leave" transaction. The bad news is that it usually overcomputes the time interval needed to send the IGMP join refresh messages. Frequently the refresh messages are longer than the router's timeout interval. We (Precept) worked with Microsoft and Intel to isolate the problem quite some months ago. We've tested the patch and it appears to work. I don't know why Microsoft has not upgraded the SDK to incorporate the patches. By-the-way, if you need a tool to generate IGMPv1 or IGMPv2 in a controlled way, you can pick one up via http://www.cavebear.com/dwtnda/ (It runs on DOS or Win 95.) --karl-- From rem-conf Wed Nov 12 13:15:34 1997 From rem-conf-request@es.net Wed Nov 12 13:15:34 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVk5Z-0005Y8-00; Wed, 12 Nov 1997 13:12:41 -0800 From: Bill Fenner To: almeroth@cs.ucsb.edu, karl@precept.com Subject: Re: Cisco Config [Q] Cc: rem-conf@es.net Message-Id: <97Nov12.131127pst.177476@crevenia.parc.xerox.com> Date: Wed, 12 Nov 1997 13:11:14 PST X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list >The bad news is that it usually overcomputes the time interval needed to >send the IGMP join refresh messages. Frequently the refresh messages are >longer than the router's timeout interval. You imply that the host is responsible for sending periodic messages. It is not, and I hope Microsoft didn't manage to implement it that way. Generally, routers send IGMP queries with a period of about 2 minutes, and time memberships out after about 2 query intervals without hearing a report for a given group. Does this mean that the buggy Windows versions don't respond to an IGMP Query for over 4 minutes? Bill From rem-conf Wed Nov 12 16:57:45 1997 From rem-conf-request@es.net Wed Nov 12 16:57:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVnWz-0007jI-00; Wed, 12 Nov 1997 16:53:13 -0800 Date: Wed, 12 Nov 1997 16:51:59 -0800 (PST) From: Karl Auerbach Reply-To: karl@precept.com To: Bill Fenner cc: almeroth@cs.ucsb.edu, rem-conf@es.net Subject: Re: Cisco Config [Q] In-Reply-To: <97Nov12.131127pst.177476@crevenia.parc.xerox.com> Message-ID: X-X-Sender: karl@big-bear.precept.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list > >The bad news is that it usually overcomputes the time interval needed to > >send the IGMP join refresh messages. Frequently the refresh messages are > >longer than the router's timeout interval. > > You imply that the host is responsible for sending periodic messages. > It is not, and I hope Microsoft didn't manage to implement it that > way. I believe the MS code does send out IGMP joins even in the absence of any IGMP noises from the router. In my own code, I send joins out whether I hear a router making queries or not, but it's a testing tool, not a production system. If that was what the IGMP spec requires, it may not be being expressed with the clarity neccessary. (I haven't looked at the latest version that was announced on the ietf-announce list today.) It does raise the concern that hosts that want to do a snap/fast join upon reboot would be precluded from doing so until they heard something from the router. > Generally, routers send IGMP queries with a period of about 2 minutes, > and time memberships out after about 2 query intervals without hearing > a report for a given group. Does this mean that the buggy Windows > versions don't respond to an IGMP Query for over 4 minutes? The time-to-respond in the queries was not being used correctly and, yes, the response times were often deferred for multiple minutes. The routers (Ciscos), by the way, were timing out in something on the order of 1 to 2 minutes. We might be seeing some "implementation experience" here that indicates that some aspects of the IGMPv2 specification might need additional clarification. --karl-- From rem-conf Wed Nov 12 17:22:36 1997 From rem-conf-request@es.net Wed Nov 12 17:22:35 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVnxU-0000WA-00; Wed, 12 Nov 1997 17:20:36 -0800 To: karl@precept.com cc: Bill Fenner , rem-conf@es.net Subject: Re: Cisco Config [Q] In-reply-to: Your message of "Wed, 12 Nov 97 16:51:59 PST." Date: Wed, 12 Nov 1997 17:19:08 PST Sender: Bill Fenner From: Bill Fenner Message-Id: <97Nov12.171916pst.177476@crevenia.parc.xerox.com> X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Karl Auerbach wrote: >I believe the MS code does send out IGMP joins even in the absence of any >IGMP noises from the router. Sending one or two IGMP Membership Reports when you first join a group is correct behavior. Sending periodic messages that are not in response to an IGMP Membership Query is not. >We might be seeing some "implementation experience" here that indicates >that some aspects of the IGMPv2 specification might need additional >clarification. I would definitely be interested to hear from MS if this was an implementation bug or a misinterpretation of the spec. It's pointless to speculate. Bill From rem-conf Wed Nov 12 22:21:48 1997 From rem-conf-request@es.net Wed Nov 12 22:21:47 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVsYE-0002B8-00; Wed, 12 Nov 1997 22:14:50 -0800 X-Sender: cckrees@dingo.uq.edu.au Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 13 Nov 1997 16:21:55 +1000 To: rem-conf@es.net From: K.Rees@dingo.cc.uq.edu.au (Kay Rees) Subject: 7th International World Wide Web X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Hello, Your name has been included on our mailing list as someone who is interested in the 7th International World Wide Web Conference and Exhibition (WWW7). The Conference is being held in Brisbane, Australia, April 14 - 18, 1998 and is one of the world's largest and most prestigious web events held annually. Please visit our web site http://www7.conf.au Why attend WWW7? If your profession is influenced by the latest developments in Web technology, then you should attend. This Conference is aimed at technical and managerial Web experts, computer scientists, educators, academics, business people and entrepreneurs, all exploring the leading edge of Web technology. Conference topics include protocol developments and standards; Web security; virtual reality; Java; information discovery; Web-based education and training; electronic commerce; Web-based business models; and intranet applications on the Web. The conference aims to foster Web development by exchanging ideas about the underlying technology; and promoting the evolution and interoperability of the Web at various levels -- papers, presentations and discussion will deal with hardware and software architecture developments; user interfaces; and social, educational and business issues and technological policies. What is the WWW Conference Series? The International World Wide Web Conference Series was started in 1994 by Web co-developer Robert Cailliau who is the current chairperson of the International World Wide Web Conference Committee, IW3C2. Past conferences have been held in Europe and the United States, with WWW7 the first in the Asia Pacific Region. The World Wide Web consortium, W3C, is the global body committed to developing a neutral, open forum for the evolution of Web technology. This global consortium is made up of more than 200 companies concerned with maintaining the interoperability and evolution of the Web. W3C presents its work at one major conference each year and in 1998 it will be WWW7. Tim Berners-Lee (Web co-developer) is the Director of W3C and is recognised as being the principal developer of the Web. Tim will be presenting a keynote address at WWW7 as well as attending Developers' Day. WWW7 offers opportunities for sponsorship, exhibition space, tutorial and workshop presentations, panels, Special Interest Group (SIG) meetings, keynote addresses, and poster presentations. Exhibition The associated exhibition, PC-IT'98, which includes the World Wide Web World exhibition, is expected to attract around 25,000 industry representatives. Conference Host Consortium The Conference is being hosted by a consortium of leading Australian Web technology organisations: -Charles Sturt University -Distributed Systems Technology Centre (DSTC) -Prentice Centre, The University of Queensland -Queensland Information Industries Branch -Southern Cross University Want to know more? We will be sending regular email updates to keep you up to date with Conference happenings. But if you would like to be taken off the emailing list, just let us know. We also have a regular newsletter, so if you would like to be included on our mailing list, please give your postal details. For more information about WWW7, please email info@www7.conf.au WWW7 Conference Secretariat PO Box WWW7 St Lucia South Queensland Australia 4067 Phone +61 7 3870 8831 Fax +61 7 3371 9514 Email info@www7.conf.au 7th International World Wide Web Conference 14-18 April 1998 Brisbane Convention & Exhibition Centre Brisbane Australia http://www7.conf.au From rem-conf Thu Nov 13 06:04:04 1997 From rem-conf-request@es.net Thu Nov 13 06:04:03 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xVzmG-0004uT-00; Thu, 13 Nov 1997 05:57:48 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Thu, 13 Nov 1997 05:57:33 -0800 (PST) Message-Id: <199711131357.FAA02696@hille.msri.org> To: rem-conf@es.net From: Reply-to: multicast@dxcoms.cern.ch Subject: CERN - ATLAS sessions X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: CERN - ATLAS sessions Date: Nov 21, 1997 Time: 08:00 GMT 2 hours Contact: multicast@noc.cern.ch URL: http://sunmed2.cern.ch:8888/ATLAS_19-21_11_97.html Description: mbone broadcast schedule http://www.msri.org/mbone From rem-conf Thu Nov 13 09:11:39 1997 From rem-conf-request@es.net Thu Nov 13 09:11:38 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xW2ZQ-0006Va-00; Thu, 13 Nov 1997 08:56:44 -0800 Message-Id: <9711131654.AA07789@dxcoms.cern.ch> Subject: MBone transmission of 19. to 21. of November To: rem-conf@es.net, hepnet-l@slacvm.slac.stanford.edu, HRC@in2p3.fr, htasc@listbox.cern.ch, net-teleconferencing@listbox.cern.ch Date: Thu, 13 Nov 1997 17:54:56 +0100 (MET) From: "Martin Fluckiger - CERN/IT/CS" X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list CERN is pleased to announce the MBONE broadcast of the ATLAS Sessions -------------- on Wednesday to Friday 19th to 21st November 1997 from the CERN Auditorium *** Times are UTC+1 *** Draft agenda for ATLAS sessions: ------------------------------- Wednesday 19 November 1997 9:00 Introduction and status (P Jenni, T Akesson) 9:45 Electronics issues across ATLAS (H Williams) 10:45 --- coffee --- 11:15 Critical integration issues of the overall detector (H Hoffmann) 12:15 Status of the experimental area (G Kantardjian) 12:45 --- lunch --- 14:00 Assembly areas (W Witzeling) 14:20 Overall ATLAS Master Schedule (G Bachy) 14:50 Solenoid (T Kondo) 15:20 Inner detector - Overview of ID engineering (G Tappern) 16:00 --- coffee --- 16:30 - Pixel module development and tests (K Einsweiler) 17:00 - SCT module development and tests (N Unno) 17:30 - TRT status (F Dittus) 18:00 - Simulation results (tba) 18:30 --- end --- Thursday 20 November 1997 9:00 Toroid magnet system and common cryogenics (H ten Kate) 10:00 Muon spectrometer - Overview (J Wotschack) - Precision chambers: status and production preparations (W Blum) 11:00 --- coffee --- 11:30 - RPCs: recent results (P Camarri) - TGC system (tba) - Signal processing in the muon system (J Huth) 12:45 --- lunch --- 14:00 LAr cryostats, feedthroughs and cryogenics (P Pailler) 14:40 LAr calorimeter - EM mechanics and kaptons (tba) - Test beam: installations and results (P Fassnacht) 15:50 --- coffee --- 16:20 - Hadronic end-cap and forward calorimeter (tba) - Electronics (tba) 17:20 Tile calorimeter - Overall status (M Nessi) 17:35 - Module-0 results 1997 (R Leitner) 17:55 - Status of optics components (J Starchenko) 18:10 - Status of the monitoring system (I Vichou) 18:25 - Electronics (K Jon-And) 18:40 - Mechanics for production start-up (L Miralles) 18:50 --- end --- Friday 21 November 9:00 Trigger, DAQ and DCS - System overview (tba) - Level-1 trigger (tba) - Level-2 trigger (tba) - DAQ and event filter (tba) - Detector control system (tba) 11:00 --- coffee --- 11:30 Status of offline computing (H Meinhard) 12:30 Conclusions (P Jenni) 13:00 --- end --- The broadcast is announced via sdr as "CERN ATLAS". vat and vic applications will be used with a ttl of 127. The sessions will also be recorded using the wrtp application. They can be downloaded from our vod server: http://sunmed2.cern.ch/cgi-bin/nph-MBone-sessions/ In case of questions or problems please contact: multicast@noc.cern.ch This message is sent to distribution lists, sorry if you receive multiple copies of it. Best regards, -------------------------------------------------------------------- Martin Fluckiger & Christian Isnard CERN - CN/CS/EN multicast@noc.cern.ch European Laboratory for Particle Physics Computers and Networks division CH-1211 Geneva 23 - Switzerland From rem-conf Thu Nov 13 09:42:36 1997 From rem-conf-request@es.net Thu Nov 13 09:42:36 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xW3FJ-0007FS-00; Thu, 13 Nov 1997 09:40:01 -0800 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Thu, 13 Nov 1997 12:39:35 -0500 From: Anthony Dickson To: CU-SeeMe-L@cornell.edu,rem-conf@es.net, videophone@es.net, mbone@isi.edu Subject: Mailing List Mime-Version: 1.0 Content-Type: text/plain Content-Disposition: inline X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list I recently reviewed some information in Digital Video Magazine. I am very interested in the subject of desktop video. Please add me to your mailing list. My e-mail address is ajd6818@yazaki-na.com. Thank you. From rem-conf Thu Nov 13 13:08:46 1997 From rem-conf-request@es.net Thu Nov 13 13:08:46 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xW6Mh-0002Fr-00; Thu, 13 Nov 1997 12:59:51 -0800 Message-ID: <01BCF033.F8CB6990.CPearson@mailbox.jf.intel.com> From: Chris C Pearson To: "'gumbee@ctd.comsat.com'" , "rem-conf@es.net" Subject: RE: Unidentified subject! Date: Thu, 13 Nov 1997 12:59:25 -0800 Organization: Intel Corporation X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list No. An individual media sample (such as a video frame) may require multiple RTP packets. For a given frame, each packet is given a monotonically increasing sequence number (except for possible wrap around), but all the packets have the same timestamp (identifying the "sampling instant"). Thus, timestamp and sequence number (in conjunction with optional marker bit) enable an RTP receiver to correctly reassemble frames in the face of possible packet loss and out-of-order delivery. -- Chris On Monday, November 03, 1997 10:00 AM, gumbee@ctd.comsat.com [SMTP:gumbee@ctd.comsat.com] wrote: > in the RTP/RTCP spec (RFC 1889), what is the exact > difference between timestamp and sequence number? > aren't they really performing the same task? > > thanks, > grant > > > From rem-conf Thu Nov 13 15:46:06 1997 From rem-conf-request@es.net Thu Nov 13 15:46:06 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xW8rN-0003zI-00; Thu, 13 Nov 1997 15:39:41 -0800 Date: Thu, 13 Nov 97 15:35:00 PST From: Gim L Deisher Message-ID: To: internet-drafts@ietf.org cc: Chad_Zhu@ccm.fm.intel.com, Donald_Newell@ccm.jf.intel.com, Christian_Maciocco@ccm.jf.intel.com, Thomas_R_Gardos@ccm.jf.intel.com, jo@cs.tu-berlin.de, cabo@tzi.org, stewe@cs.tu-berlin.de, lscline@ideal.jf.intel.com, rem-conf@es.net Subject: RTP Payload Format for H.263+ X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Text item: Enclosed is a H.263+ RTP payload draft specification. It describes a packetization scheme for the 1998 version of H.263 video. This document resolves differences between two distinct documents describing this payload which were posted in July. We are planning to submit this draft and present it at the December IETF meeting in D.C. Text item: h263pplh.txt 11/12/97 5:24P Internet Engineering Task Force Audio-Video Transport WG INTERNET-DRAFT C. Bormann / Univ. Bremen L. Cline / Intel G. Deisher / Intel T. Gardos / Intel C. Maciocco / Intel D. Newell / Intel J. Ott / Univ. Bremen S. Wenger / TU Berlin C. Zhu / Intel RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) Status of This Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or made obsolete by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). Distribution of this document is unlimited. 1. Introduction This document specifies an RTP payload header format applicable to the transportation of video streams generated based on the 1998 version of ITU-T Recommendation H.263. The 1998 version of ITU-T Recommendation H.263 added numerous coding options to improve codec performance over the 1996 version. The 1998 version is referred to as H.263+ in this document. Among the new options, the ones with the biggest impact on the RTP payload are the slice structured mode (SS), independent segment decoding mode (ISD), and the scalability mode. This section summarizes the impact of these new coding options on packetization. Refer to [4] for more information on coding options. Slice structure was added to H.263+ for three purposes: to provide enhanced error resilience capability, to make the bitstream more amenable to use with an underlying packet transport such as RTP, and to minimize video delay. The slice structured mode supports fragmentation at macroblock boundaries. When the independent segment decoding option is employed, a video picture frame is broken into segments and encoded in such a way that each segment is independently decodable. Utilizing ISD in a lossy network environment helps prevent the propagation of errors from one segment of the picture to others. H.263+ also includes bitstream scalability as an optional coding mode. Three kinds of scalability are defined: temporal, signal-to-noise ratio (SNR), and spatial scalability. Temporal scalability is achieved via the disposable nature of bi-directionally predicted frames, or B-frames. SNR scalability permits refinement of encoded video frames, thereby improving the quality (or SNR). Spatial scalability is similar to SNR scalability except the refinement layer is twice the size of the base layer in the horizontal dimension, vertical dimension, or both. 2. Usage of RTP When transmitting H.263+ video streams over the internet, the output of the encoder can be packetized directly. All the bits resulting from the bitstream including the fixed length codes and variable length codes will be included in the packet. For H.263+ bitstreams coded with temporal, spatial, or SNR scalability, each layer may be transported to a different network address. More specifically, each layer may use a unique IP address and port combination. In addition, temporal relations between layers shall be expressed using the RTP timestamp so that they can be synchronized at the receiving ends in multicast or unicast applications. The H.263+ video streams will be carried as payload data within RTP packets. A new H.263+ payload header, H.263+ payload header, is defined in section 4. This section defines the usage of the RTP fixed header and H.263+ video packet structure. 2.1 RTP Header Usage Each RTP packet starts with a fixed RTP header. The following fields of the RTP fixed header are used for H.263+ video streams: Marker bit (M bit): The Marker bit of the RTP header is set to 1 when the current packet carries the end of current frame, and is 0 otherwise. Payload Type (PT): The Payload Type shall specify H.263+ video payload format. A dynamic payload can be used initially until a static payload type is assigned. Timestamp: The RTP Timestamp encodes the sampling instance of the first video frame contained in the RTP data packet. The RTP timestamp may be the same on successive packets if a video frame occupies more than one packet. In a multilayer scenario, all pictures corresponding to the same temporal reference should pertain the same timestamp. If temporal scalability is used and B-frames are present, the timestamp may not be monotonically increasing in the video stream. If B-frames are transmitted on a separate layer and address, they must be synchronized properly with the reference frames. Please refer to the 1998 ITU Recommendation for H.263 [4] for information on required transmission order to a decoder. For an H.263+ video stream, the RTP timestamp is based on a 90 kHz clock, the same as that of the RTP payload for H.261 stream [5]. 2.2 Video Packet Structure An H.263+ compressed bitstream is carried as a payload within each RTP packet. For each RTP packet, the RTP header is followed by an H.263+ payload header, which is followed by a standard H.263+ compressed bitstream. The size of the H.263+ payload header is variable depending on the payload involved as detailed in the section 4. The layout of the RTP H.263+ video packet is shown as: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RTP Header ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | H.263+ Payload Header ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | H.263+ Compressed Data Stream ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3. Design Considerations The goal of this payload format is to specify an efficient way of encapsulating an H.263+ standard compliant bitstream and enhance the resiliency towards packet losses. Due to the large number of different possible coding schemes in H.263+, a copy of the picture header with configuration information is inserted into the payload header when appropriate. There are a few assumptions and constraints associated with this H.263+ payload header design. The purpose of this section is to point out various design issues and also discuss several coding options provided by H.263+ that may impact the performance of network video. . It is reasonable to assume that no single macroblock will be too large to fit in a packet. . The optional slice structured mode described in annex K of H.263+ [4] enables more flexibility for packetization. Furthermore, packets based on a slice structure are also inherently more loss resilient. Similar to a picture segment that begins with a GOB header, the motion vector predictors in a slice are restricted to reside within its boundaries. For these reasons, the use of the slice structured mode is strongly recommended for network applications. . In non-rectangular slice structured mode, only complete slices should be included in a packet. In other words, slices should not be fragmented across packets. Optimally, a packet will contain only one slice. . When the slice structure is not applied, the insertion of a GOB header in every GOB is recommended to reduce the dependency on motion vector prediction across GOBs. See section 3.3 of [6] for more information. . The independently segmented decoding described in annex R of [4] does not allow any data dependency across slice or GOB boundaries in reference picture. It can be utilized to further improve resiliency in high loss conditions. . If ISD is used in conjunction with the slice structure, the rectangular slice submode shall be enabled and the dimensions and quantity of the slices present in a frame shall remain the same between two intra-coded frames (I-frames). The ISD segments may be entirely intra coded from time to time to realize quick error recovery without adding latency time associated with sending complete I-frames. . For resiliency, sending a full picture header for every frame is recommended. In other words, the sender should always set the subfield UFEP in PLUSPTYPE to '001' in the video bitstream. . In a multi-layer scenario, each layer can be transmitted to a different network address. The configuration of each layer such as the enhancement layer number (ELNUM), reference layer number (RLNUM), and scalability type should be determined at the start of the session and should not change during the course of the session. 4. H.263+ Payload Header For H.263+ video streams, each RTP packet carries only one H.263+ video packet. The H.263+ payload header is always present for each H.263+ video packet. The payload header has variable length. If a picture header is included in the payload header, the length of the picture header in number of bytes is specified by PLEN. The minimum length of the payload header is 32 bits, corresponding to PLEN equals 0. The H.263+ payload header is structured as follow: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |V=0|SBIT |EBIT | PLEN |PEBIT| TID | Trun | RR | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1 0 0 0 0 0| picture header starting with TR, PTYPE, ... . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ V: 2 bits Version number. Set to '00' for this payload format. [Ed. Note: The version control will not take effect until a draft has been formally submitted to the IETF.] SBIT: 3 bits Start bit position specifies the number of bits that should be ignored in the first data byte of the payload. EBIT: 3 bits End bit position indicates the number of bits that should be ignored in the last data byte of the payload. PLEN: 3 bits Picture header length in number of bytes. PEBIT: 3 bits End bit position indicates the number of bits that should be ignored in the last byte of the picture header. TID: 3 bits Thread id. Used only in optional video redundancy coding mode (VRC). See annex N of [4]. All three bits must be set to 0 unless VRC mode is applied. Trun: 4 bits Cyclic packet number. Used only in optional VRC mode. These bits must be set to 0 unless VRC mode is applied. RR: 9 bits Reserved bits. Notice that the TID and Trun fields are associated only with the video redundancy coding usage scenario derived from the reference picture selection mode specified in annex N of [4]. The TID and Trun bits must be set to 0 if VRC is not used. The use of VRC shall be negotiated by external means. 4.1 Encapsulating Packet that Begins with PSC Any packet that begins with a picture start code (PSC), i.e. the first packet of a picture frame, shall be encapsulated using only the first 32-bit word of the payload header since a picture header is already included in the data bitstream. In this case, PLEN shall be 0. Here is an example of encapsulating the first packet in a frame: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0 0|SBIT |EBIT |0 0 0 0 0|0 0 0| TID | Trun | RR | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | bitstream data starts with complete picture header ... . +---------------------------------------------------------------+ 4.2 Encapsulating Packet that Begins with GBSC or SSC Any packet that begins with either a GOB start code (GBSC) or a slice start code (SSC) shall include a copy of the picture header in the payload header for resiliency. PLEN shall be set to specify the length of the included picture header in bytes. Hence, PLEN > 0. The end bit position corresponding to the last byte of the picture header data is indicated by PEBIT. Actual bitstream data shall begin on an 8-bit byte boundary following the payload header. Notice that only the last six bits of the picture start code, '100000', are included in the payload header. A complete H.263+ picture header with byte aligned picture start code can be conveniently assembled if needed on the receiving end by prepending the sixteen leading '0' bits. Assuming a PLEN of 9, below is an example of a packet that begins with a GBSC or a SSC: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0 0|SBIT |EBIT |0 1 0 0 1|PEBIT| TID | Trun | RR | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1 0 0 0 0 0| picture header starting with TR, PTYPE, ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | bitstream data begins with GBSC/SCC ... . +-+-+-+-+-+-+-+-+-----------------------------------------------+ 4.3 Encapsulating Follow-On Packet When slice structure coding option is not applied, some GOBs in the bitstream may be larger than the size of one packet. Similarly, when ISD option is applied, a picture segment may be larger than the required packet size. The remaining fragment of a picture segment larger than the required packet size is termed "follow-on" packet in this document. These follow-on packets with data fragmented at the macroblock boundaries are not independently recoverable. In this case, the payload header includes only the first 32-bit word and PLEN shall be set to 0. A receiver should discard any follow-on packet it receives if the preceding packet containing the segment header information has been lost. Here is an example of a follow-on packet: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0 0|SBIT |EBIT |0 0 0 0 0|0 0 0| TID | Trun | RR | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | sub-segment bitstream data ... . +---------------------------------------------------------------+ Even though they may have identical payload headers, a follow-on packet can be differentiated from the first packet in a frame since the data in a follow-on packet does not begin with a PSC. 5. Security Considerations RTP packets using the payload format defined in this specification are subject to the security considerations discussed in the RTP specification [1], and any appropriate RTP profile (for example [3]). This implies that confidentiality of the media streams is achieved by encryption. Because the data compression used with this payload format is applied end-to-end, encryption may be performed after compression so there is no conflict between the two operations. A potential denial-of-service threat exists for data encodings using compression techniques that have non-uniform receiver-end computational load. The attacker can inject pathological datagrams into the stream which are complex to decode and cause the receiver to be overloaded. However, this encoding does not exhibit any significant non-uniformity. As with any IP-based protocol, in some circumstances a receiver may be overloaded simply by the receipt of too many packets, either desired or undesired. Network-layer authentication may be used to discard packets >from undesired sources, but the processing cost of the authentication itself may be too high. In a multicast environment, pruning of specific sources may be implemented in future versions of IGMP [5] and in multicast routing protocols to allow a receiver to select which sources are allowed to reach it. A security review of this payload format found no additional considerations beyond those in the RTP specification. 6. References [1] H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson, "RTP : A Transport Protocol for Real-Time Applications", RFC 1889. [2] "Video Codec for Audiovisual Services at px64 kbits/s", ITU-T Recommendation H.261, 1993. [3] "RTP Profile for Audio and Video Conference with Minimal Control", RFC 1890. [4] "Video Coding for Low Bitrate Communication", Draft ITU-T Recommendation H.263, Draft 20, September 1997. [5] T. Turletti, C. Huitema, "RTP Payload Format for H.261 Video Streams", RFC 2032. [6] C. Zhu, "RTP Payload Format for H.263 Video Streams", RFC 2190. From rem-conf Fri Nov 14 00:32:15 1997 From rem-conf-request@es.net Fri Nov 14 00:32:15 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xWH5b-00078h-00; Fri, 14 Nov 1997 00:26:55 -0800 From: Joerg Ott Message-Id: <199711140820.JAA25831@presto.cs.tu-berlin.de> Subject: Re: RTP Payload Format for H.263+ To: Gim_L_Deisher@ccm.jf.intel.com (Gim L Deisher) Date: Fri, 14 Nov 1997 09:20:15 +0100 (MET) Cc: internet-drafts@ietf.org, Chad_Zhu@ccm.fm.intel.com, Donald_Newell@ccm.jf.intel.com, Christian_Maciocco@ccm.jf.intel.com, Thomas_R_Gardos@ccm.jf.intel.com, jo@cs.tu-berlin.de, cabo@tzi.org, stewe@cs.tu-berlin.de, lscline@ideal.jf.intel.com, rem-conf@es.net In-Reply-To: from "Gim L Deisher" at Nov 13, 97 03:35:00 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Gim, did I miss something in your previous e-mail to us where you were saying that you are going to send this draft to the mailing list? Carsten had some issues to raise and we wanted discuss them with Stephan before getting back to you. So I do feel *very* unhappy that you simply sent this off to the reflector without a prior sort "last call" announcement. If I missed something, then this is probably our fault abd you may disregard this e-mail. We will send you those comments anyway, and we should start thinking about how to act if we decide to integrate those changes. Joerg From rem-conf Fri Nov 14 01:27:08 1997 From rem-conf-request@es.net Fri Nov 14 01:27:08 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xWHwH-0000IT-00; Fri, 14 Nov 1997 01:21:21 -0800 Message-ID: <5721C97A32DBD011B3FF0060974B1C632C5371@R-MHS> From: GOULEAU Emmanuel CNET/DSM/REN To: "'rem-conf@es.net'" Subject: "Segmentation&Reassembly" procedures Date: Fri, 14 Nov 1997 09:54:50 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Dear participants, Reading the RFC1889, it seems unclear whether RTP is responsible of the "Segmentation&Reassembly" procedures (in case the payload plus the RTP/UDP/IP header is larger than the MTU) or not. In the latter case, it would be the "Application" upper layer? Does it depend on the payload format? In the same way, which layer (RTP or the "application" upper layer) values the RTP timestamps? Are the RTP timestamps independant from the payload specific timestamps? I wait for your response. Thank you in advance, Emmanuel GOULEAU France Telecom CNET mailto:emmanuel.gouleau@cnet.francetelecom.fr ************************************************************************ ************************** /_/_/_/_/ Emmanuel GOULEAU /_/_/_/_/ France Telecom CNET/DSM/DCM /_/_/_/_/ mailto:emmanuel.gouleau@cnet.francetelecom.fr Tel : +33 2 99 12 43 94 - Fax : +33 2 99 12 40 98 ************************************************************************ ************************** From rem-conf Fri Nov 14 01:57:34 1997 From rem-conf-request@es.net Fri Nov 14 01:57:33 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xWISr-0000st-00; Fri, 14 Nov 1997 01:55:01 -0800 From: Joerg Ott Message-Id: <199711140951.KAA26734@presto.cs.tu-berlin.de> Subject: Re: RTP Payload Format for H.263+ To: rem-conf@es.net Date: Fri, 14 Nov 1997 10:51:09 +0100 (MET) In-Reply-To: <199711140820.JAA25831@presto.cs.tu-berlin.de> from "Joerg Ott" at Nov 14, 97 09:20:15 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Apologies. Please disregard my previous posting to thist list. One should never send e-mail before having had the first mug of coffee in the morning. Joerg From rem-conf Sun Nov 16 11:36:20 1997 From rem-conf-request@es.net Sun Nov 16 11:36:18 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXAFa-000438-00; Sun, 16 Nov 1997 11:20:54 -0800 Message-Id: <3.0.1.32.19971116111859.00caffd8@sc-mail2.corpwest.baynetworks.com> X-Sender: knichols@sc-mail2.corpwest.baynetworks.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Sun, 16 Nov 1997 11:18:59 -0800 To: rem-conf@es.net From: Kathleen_Nichols@BayNetworks.COM (Kathleen Nichols) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Unidentified subject! X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Towards Differentiated Services for the Internet Speaker: Van Jacobson, LBNL Date: Nov 25, 1997 Time: 12:00 EST 2 hours Contact: knichols@baynetworks.com Description: There appears to be an emerging, widespread, agreement that some sort of differentiated service capability must be added to the Internet. However most of the discussion has focused on details of the lowest-level queuing primitives needed to implement different services. While these details are very important, they have meaning only when viewed in a larger, architectural context of what sorts of services are actually viable and deployable in a system as large and heterogeneous as the Internet. This talk will try to expose some of the architectural context & constraints and explore some of the implications for low-level primitives and other aspects of the service. From rem-conf Sun Nov 16 11:57:20 1997 From rem-conf-request@es.net Sun Nov 16 11:57:19 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXAjT-0004Xx-00; Sun, 16 Nov 1997 11:51:47 -0800 Message-ID: <346F79FC.709A@ctr.columbia.edu> Date: Sun, 16 Nov 1997 14:55:56 -0800 From: "Andrew T.Campbell" Reply-To: campbell@ctr.columbia.edu Organization: Center for Telecommunications Research, Columbia University X-Mailer: Mozilla 3.01Gold (WinNT; I) MIME-Version: 1.0 To: mnl@ctr.columbia.edu, irl@cs.columbia.edu CC: rem-conf@es.net Subject: Re: Unidentified subject! References: <3.0.1.32.19971116111859.00caffd8@sc-mail2.corpwest.baynetworks.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Kathleen Nichols wrote: > > MBone Broadcast Announcement > ---------------------------- > > Title: > Towards Differentiated Services for the Internet > Speaker: > Van Jacobson, LBNL > Date: > Nov 25, 1997 > Time: > 12:00 EST 2 hours > Contact: > knichols@baynetworks.com > > Description: > > There appears to be an emerging, widespread, agreement that some > sort of differentiated service capability must be added to > the Internet. However most of the discussion has focused on > details of the lowest-level queuing primitives needed to implement > different services. While these details are very important, they > have meaning only when viewed in a larger, architectural context > of what sorts of services are actually viable and deployable in > a system as large and heterogeneous as the Internet. > > This talk will try to expose some of the architectural context & > constraints and explore some of the implications for low-level > primitives and other aspects of the service. -- Andrew T. Campbell http://comet.ctr.columbia.edu/~campbell Wireless Media Systems Project http://comet.ctr.columbia.edu/wireless From rem-conf Sun Nov 16 23:42:31 1997 From rem-conf-request@es.net Sun Nov 16 23:42:27 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXLhi-00007o-00; Sun, 16 Nov 1997 23:34:42 -0800 Message-Id: <199711170734.QAA22984@rama.osaka.iij.ad.jp> To: rem-conf@es.net Subject: STS-87 Shuttle mission From: FUJII Naoto X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 17 Nov 1997 16:34:15 +0900 Sender: fujii@rama.osaka.iij.ad.jp X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Hi, folks. I really want to know that the space shuttle launch is going to be relayed via MBone on Nov. 19, for sure. If you know, please let me know as soon as possible. Thanks. -- FUJII Naoto Internet Initiative Japan Inc. From rem-conf Mon Nov 17 00:15:12 1997 From rem-conf-request@es.net Mon Nov 17 00:15:11 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXMIr-0000iq-00; Mon, 17 Nov 1997 00:13:05 -0800 Date: Mon, 17 Nov 1997 00:12:00 -0800 (PST) From: Stephen Casner To: rem-conf@es.net Subject: AVT Meeting at December IETF Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list To the Audio/Video Transport working group: We have two sessions scheduled for AVT at the upcoming IETF: Wednesday, December 10 at 1300-1500 (opposite ospf, ftpext, pkapext, pkix) Thursday, December 11 at 0900-1130 (opposite tip, nntpext, rps, qosr, ipngwg) I requested two sessions since we overran the one session in Munich. Please send a message to me if you would like to make a presentation at the upcoming meeting. (Those who have already sent requests to which I have responded need not repeat them.) One suggested topic: There was quite a bit of discussion on this mailing list regarding the proposed payload format for ASF. I saw nothing following the message that I sent, but I don't know whether my message somehow squelched the discussion or if it was already complete. I stated several reasons why I thought it was not a good idea to create an general-purpose umbrella format that adds another level of multiplexing to get to the real encoding type. I should point out that this observation applies equally to the QuickTime payload format that was proposed earlier in the year but did not get the same attention as the ASF proposal. As I said, I believe that dynamic payload types should be used to establish a binding to the specific encodings and parameters. This allows the demultiplexing to remain at the payload type field and conveys constant information out-of-band rather than in an additional payload-specific header. However, there is an important task remaining to make this work, and this is one of the shortcomings that the ASF proposal was trying to address: we need to specify the name space in which the many existing encodings (and new ones to be defined) will be identified in the dynamic payload type binding (in SDP or other means), along with any necessary parameters for those encodings. One proposal is to use GUIDs because no registration process is required to define them. In my view, that doesn't really help because the real problem is not in making up unique identifiers but rather in making sure that all parties in a conversation agree what a particular identifier means. The bigger problem is not technical but political: there are already multiple name spaces covering many of the encodings. I believe it is important that we do _not_ create a solution for the dynamic payload type binding syntax that incorporates all the names spaces such that the same encoding can be specified in any of several different ways. That's a sure path to incompatibility. One possibility is to expand the MIME type namespace for audio and video, which is an idea that was suggested on this list by Harald Alvestrand and Keith Moore a while back. In particular, they wanted to be able to specify these encodings for incorporation into MIME messages as well as for real-time streaming. Indeed, if the syntax of the dynamic payload type binding (including encoding parameters) was also suitable for describing the bits in a MIME message, that seems like a real plus. I'm sure there are a number of opinions on this topic among those who have participated in AVT and on the rem-conf list. I'd like to discuss this more on the list and at the upcoming meeting. If you would like to speak on this topic at the meeting, please tell me. -- Steve From rem-conf Mon Nov 17 07:56:00 1997 From rem-conf-request@es.net Mon Nov 17 07:56:00 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXTGV-0003SM-00; Mon, 17 Nov 1997 07:39:07 -0800 Message-Id: <199711171538.KAA15237@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce@ietf.org Cc: rem-conf@es.net From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-avt-rtp-h263-video-00.txt Date: Mon, 17 Nov 1997 10:38:57 -0500 Sender: cclark@cnri.reston.va.us X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Working Group of the IETF. Title : RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) Author(s) : C. Bormann, L. Cline, G. Deisher, C. Maciocco, T. Gardos, D. Newell, J. Ott, S. Wenger, C. Zhu Filename : draft-ietf-avt-rtp-h263-video-00.txt Pages : 6 Date : 14-Nov-97 This document specifies an RTP payload header format applicable to the transportation of video streams generated based on the 1998 version of ITU-T Recommendation H.263. The 1998 version of ITU-T Recommendation H.263 added numerous coding options to improve codec performance over the 1996 version. The 1998 version is referred to as H.263+ in this document. Among the new options, the ones with the biggest impact on the RTP payload are the slice structured mode (SS), independent segment decoding mode (ISD), and the scalability mode. This section summarizes the impact of these new coding options on packetization. Refer to [4] for more information on coding options. Slice structure was added to H.263+ for three purposes: to provide enhanced error resilience capability, to make the bitstream more amenable to use with an underlying packet transport such as RTP, and to minimize video delay. The slice structured mode supports fragmentation at macroblock boundaries. When the independent segment decoding option is employed, a video picture frame is broken into segments and encoded in such a way that each segment is independently decodable. Utilizing ISD in a lossy network environment helps prevent the propagation of errors from one segment of the picture to others. H.263+ also includes bitstream scalability as an optional coding mode. Three kinds of scalability are defined: temporal, signal-to-noise ratio (SNR), and spatial scalability. Temporal scalability is achieved via the disposable nature of bi-directionally predicted frames, or B-frames. SNR scalability permits refinement of encoded video frames, thereby improving the quality (or SNR). Spatial scalability is similar to SNR scalability except the refinement layer is twice the size of the base layer in the horizontal dimension, vertical dimension, or both. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-avt-rtp-h263-video-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-avt-rtp-h263-video-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-avt-rtp-h263-video-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971114174531.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-avt-rtp-h263-video-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-avt-rtp-h263-video-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971114174531.I-D@ietf.org> --OtherAccess-- --NextPart-- From rem-conf Mon Nov 17 11:01:37 1997 From rem-conf-request@es.net Mon Nov 17 11:01:37 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXWII-0005ds-00; Mon, 17 Nov 1997 10:53:10 -0800 Message-Id: <3.0.3.32.19971117114816.00c3cb48@mail.arc.nasa.gov> X-Sender: mallard@mail.arc.nasa.gov X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 17 Nov 1997 11:48:16 -0800 To: FUJII Naoto From: Mark Allard Subject: Re: STS-87 Shuttle mission Cc: rem-conf@es.net In-Reply-To: <199711170734.QAA22984@rama.osaka.iij.ad.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list It is with great pleasure that I can confirm the next U.S. Space Shuttle Mission (STS-87 - U.S. MICROGRAVITY PAYLOAD - 4) will be broadcast on the MBone as part of the continuing service effort by NASA-Ames Research Center to provide informational content of international interest to the MBone community as part of Ames' Expert Center for Desktop Video research efforts within the Agency. Additional mission details are provided below- MISSION: STS-87 - U.S. MICROGRAVITY PAYLOAD - 4 VEHICLE: Columbia/OV-102 LOCATION: Pad 39B KSC LAUNCH DATE/TIME: Nov. 19 at 2:46 p.m. LAUNCH WINDOW: 2 hours, 30 minutes TARGET KSC LANDING DATE/TIME: Dec. 5 at about 7:20 a.m. MISSION DURATION: 15 days, 16 hours, 34 minutes CREW: Kregel, Lindsey, Scott, Chawla, Doi, Kadenyuk ORBITAL ALTITUDE and INCLINATION: 150 nautical miles/28.45 degrees Glad we can be of service, M At 04:34 PM 11/17/97 +0900, FUJII Naoto wrote: >Hi, folks. > >I really want to know that the space shuttle launch is going to be >relayed via MBone on Nov. 19, for sure. > >If you know, please let me know as soon as possible. >Thanks. >-- >FUJII Naoto Internet Initiative Japan Inc. > > > From rem-conf Mon Nov 17 11:46:45 1997 From rem-conf-request@es.net Mon Nov 17 11:46:44 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXWvw-0006aS-00; Mon, 17 Nov 1997 11:34:08 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Mon, 17 Nov 1997 11:33:36 -0800 (PST) Message-Id: <199711171933.LAA04068@hille.msri.org> To: rem-conf@es.net From: Reply-to: multicast@lists.uoregon.edeu Subject: UO Special Events Presents Steve Deering X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: UO Special Events Presents Steve Deering Date: Nov 25, 1997 Time: 13:30 PST8PDT 1.5 hours Contact: multicast@lists.uoregon.edeu URL: http://darkwing.uoregon.edu/~netcast/video/index.html Description: UO Presents Steve Deering, part of the Computer Science Colloquium Series. IPv6, the Next Generation Internet Protocol. http://www.cs.uoregon.edu/resources/colloq.html#Deering mbone broadcast schedule http://www.msri.org/mbone From rem-conf Mon Nov 17 12:06:20 1997 From rem-conf-request@es.net Mon Nov 17 12:06:18 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXXN2-0007NA-00; Mon, 17 Nov 1997 12:02:08 -0800 Message-ID: <3470A269.6362BF41@dnrc.bell-labs.com> Date: Mon, 17 Nov 1997 15:00:41 -0500 From: "Jonathan D. Rosenberg" Reply-To: jdrosen@dnrc.bell-labs.com X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: rem-conf@es.net, pint@lists.research.bell-labs.com, confctrl@isi.edu Subject: BoF Session in December IETF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list pint'ers, avt'ers and mmusic'ers, There will be a BoF Session at December's IETF, on Wed. from 9 - 11:30am, to consider the formation of a new working group to examine the usage of SIP (the Session Initiation Protocol) for Internet telephony for thin clients. You can find a proposed charter and agenda at: ftp://ftp.ietf.org/ietf/97dec/siptel-agenda-97dec.txt To facilitate discussion during the BoF, a mailing list has been set up to begin a conversation on the subject beforehand. To subscribe or unsubscribe yourself to the mailing list, send a message to siptel-request@lists.research.bell-labs.com with the single word subscribe or unsubscribe in the body. To send to the list, address the mail to siptel@lists.research.bell-labs.com. Please feel free to send mail to this list with any questions/comments/concerns about the proposed charter and agenda. Thanks, Jonathan R. -- Jonathan D. Rosenberg Lucent Technologies Member of Technical Staff 101 Crawfords Corner Rd. High Speed Networks Research Holmdel, NJ 07733 PHONE: (908) 949-6418 Rm. 4C-526 FAX: (908) 834-5379 EMAIL: jdrosen@bell-labs.com URL: http://www.cs.columbia.edu/~jdrosen From rem-conf Mon Nov 17 12:18:45 1997 From rem-conf-request@es.net Mon Nov 17 12:18:44 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXXZ7-0007j7-00; Mon, 17 Nov 1997 12:14:37 -0800 Date: Mon, 17 Nov 1997 12:12:39 -0800 () From: Stephen Casner To: Scott Petrack cc: rem-conf@es.net Subject: Re: payload formats for the two new GSM coders - is it too late? In-Reply-To: <42256551.002D0DC7.00@il4.vocaltec.co.il> Message-ID: X-X-Sender: casner@big-bear.precept.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Scott, > I am writing as Chair of the Working Group in ETSI project TIPHON on IP > Telephony that is responsible for protocols. We would like to add two > payload formats for the two "new" GSM coders to the RTP basic profile? Is > it too late to do this? I believe it would be reasonable to add descriptions of the payload format for these GSM coders to the Internet-Draft which revises RFC 1890, ietf-avt-profile-new-01.txt. Working with Henning, I would like to get an update posted before the deadline. > The payload formats as simple as the original GSM 6.10 format, and at the > last TIPHON meeting, the payload formats were approved. It was agreed to > send them to AVT with a request to include them in the basic profile which > will be the successor to RFC 1890. You will need to provide payload format descriptions to be added to the I-D. These descriptions should include information similar to what has been added in the I-D for GSM 06.10 (it was not in the RFC). Because the bit packing for 06.10 is not specified elsewhere (at least as used in RTP), Henning painstakingly created a table to specify it. Perhaps in the case of the two new GSM coders this information is specified elsewhere and can be included by reference. At a minimum, the description would need to say how big each encoded block is and that one or more integral blocks may be included in each packet (or whatever is appropriate). I assume no payload-specific header needs to be added for these encodings. > It's all pretty straightforward stuff, and we doubt that anything needs > changing. But TIPHON definitely agreed that rem-conf is the final authority > on such payload formats. Comments are always solicited on drafts, but at the upcoming AVT meeting comments on these proposed payload formats should also be solicited. -- Steve From rem-conf Mon Nov 17 15:14:26 1997 From rem-conf-request@es.net Mon Nov 17 15:14:25 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXaJR-0002Aj-00; Mon, 17 Nov 1997 15:10:37 -0800 Message-ID: <0D8F265A565BD111BE7E00805F9A53F5168CBB@red-40-msg.dns.microsoft.com> From: Eric Fleischman To: rem-conf@es.net Subject: Recording MBone Sessions to ASF Files Date: Mon, 17 Nov 1997 15:10:31 -0800 X-Mailer: Internet Mail Service (5.5.1960.3) X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Anders Klemets and I have just submitted a new Internet-draft document for your consideration and comment. This document is entitled "Recording MBone Sessions to ASF Files" and it is currently available at http://www.microsoft.com/asf/resources/draft-fleischman-asf-rtp-record-00.tx t. From rem-conf Mon Nov 17 15:42:43 1997 From rem-conf-request@es.net Mon Nov 17 15:42:43 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXanH-0002sV-00; Mon, 17 Nov 1997 15:41:27 -0800 Date: Mon, 17 Nov 1997 15:51:52 -0800 (PST) From: Andrew Daviel Reply-To: Andrew Daviel To: RemConf List Subject: Win95 sdr out-of-space alerts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list We got (I think) winsdr-24a4. It runs OK, but often generates an alert popup saying there isn't enough space in table, or something, for many incoming session announcements. Anyone else seen this, or have a fix? (developers: (mice?) how about a few words on how exactly to set up HOME and (?) PATH for non-DOS-savvy Win95 users ? ) BTW, I've been making a tool table at http://andrew.triumf.ca/mbone/tools.html Contributions ? Andrew Daviel mailto:advax@triumf.ca TRIUMF From rem-conf Mon Nov 17 18:36:33 1997 From rem-conf-request@es.net Mon Nov 17 18:36:31 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXdQb-0004cD-00; Mon, 17 Nov 1997 18:30:13 -0800 Message-Id: <199711180229.LAA26094@rama.osaka.iij.ad.jp> To: mallard@mail.arc.nasa.gov Cc: rem-conf@es.net Subject: Re: STS-87 Shuttle mission From: FUJII Naoto In-Reply-To: Your message of "Mon, 17 Nov 1997 11:48:16 -0800" References: <3.0.3.32.19971117114816.00c3cb48@mail.arc.nasa.gov> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Nov 1997 11:29:57 +0900 Sender: fujii@rama.osaka.iij.ad.jp X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Mark, From: Mark Allard > It is with great pleasure that I can confirm the next U.S. Space Shuttle > Mission (STS-87 - U.S. MICROGRAVITY PAYLOAD - 4) will be broadcast on the > MBone as part of the continuing service effort by NASA-Ames Research Center > to provide informational content of international interest to the MBone > community as part of Ames' Expert Center for Desktop Video research efforts > within the Agency. Thank you for your information. I'm looking forward to watching it. -- FUJII Naoto Internet Initiative Japan Inc. From rem-conf Tue Nov 18 09:29:44 1997 From rem-conf-request@es.net Tue Nov 18 09:29:43 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXrMb-0001uB-00; Tue, 18 Nov 1997 09:23:01 -0800 Date: Tue, 18 Nov 1997 18:22:22 +0100 From: pate@clarinet.u-strasbg.fr (David PATE) Message-Id: <9711181722.AA05982@clarinet.u-strasbg.fr> To: mbone@sics.se, rem-conf@es.net Subject: mrouted 3.81 on Linux 2.0.30 X-Sun-Charset: US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Hi, I've got a problem similar than others, but I don't find any solution. I receive data from all the world in vic or vat or something else, but what I try to send is never received on other stations. My mrouted and mbone applications are on the same PC. It's like mrouted works in only one direction. Could someone help to make it work bidirectional ? Thanks in advance. (Please mail me directly, because I'm not sure to get all messages of the list) DAVID ----- From rem-conf Tue Nov 18 09:29:46 1997 From rem-conf-request@es.net Tue Nov 18 09:29:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xXrPf-0001ul-00; Tue, 18 Nov 1997 09:26:11 -0800 Date: Tue, 18 Nov 1997 18:25:46 +0100 From: pate@clarinet.u-strasbg.fr (David PATE) Message-Id: <9711181725.AA05996@clarinet.u-strasbg.fr> To: mbone-eu@sics.se, rem-conf@es.net Subject: mrouted 3.81 on Linux 2.0.30 X-Sun-Charset: US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Hi, I've got a problem similar than others, but I don't find any solution. I receive data from all the world in vic or vat or something else, but what I try to send is never received on other stations. My mrouted and mbone applications are on the same PC. It's like mrouted works in only one direction. Could someone help to make it work bidirectional ? Thanks in advance. (Please mail me directly, because I'm not sure to get all messages of the list) DAVID ----- From rem-conf Wed Nov 19 03:32:39 1997 From rem-conf-request@es.net Wed Nov 19 03:32:38 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xY83s-0001VE-00; Wed, 19 Nov 1997 03:12:48 -0800 Date: Wed, 19 Nov 1997 11:59:38 +0100 (MET) From: Kors Bos Reply-To: Kors Bos To: Martin Fluckiger - CERN/IT/CS Cc: rem-conf@es.net, hepnet-l@slacvm.slac.stanford.edu, HRC@in2p3.fr, htasc@listbox.cern.ch, net-teleconferencing@listbox.cern.ch Subject: Re: MBone transmission of 19. to 21. of November In-Reply-To: <9711131654.AA07789@dxcoms.cern.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list On Thu, 13 Nov 1997, Martin Fluckiger - CERN/IT/CS wrote: > The broadcast is announced via sdr as "CERN ATLAS". vat and vic applications > will be used with a ttl of 127. For Windows NT users, the broadcast cannot be seen on sd, the NT equivalent of the unix sdr. I started vic and vat from a DOS window: vat -r 224.2.214.27/21118 vic 224.2.158.150/58778 The sound is excellent but the transparencies unreadable as usual, but that's not the fault of mbone. I suppose also many people in the Auditorium cannot read Hans Hoffmann's slides -:) ----------------------------- Kors Bos NIKHEF, Postbus 41882, NL-1009 DB Amsterdam, The Netherlands Office H156, tel. +31-(0)20-592.5083, fax +31-(0)20-592.5155 email k.bos@nikhef.nl, cellular phone +31-(0)6-5364.9224 From rem-conf Wed Nov 19 03:58:37 1997 From rem-conf-request@es.net Wed Nov 19 03:58:36 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xY8jK-00027U-00; Wed, 19 Nov 1997 03:55:38 -0800 Message-Id: <3.0.1.32.19971119115617.00854680@pop3.soton.ac.uk> X-Sender: djp@pop3.soton.ac.uk X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Wed, 19 Nov 1997 11:56:17 +0000 To: rem-conf@es.net From: David Price Subject: Mrouted 3.81 on Linux - Please post any fixes to this mailbases as well Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Hi, I am experiencing the same problems as David Pate (See previous messages) with Mrouted 3.81 on Linux. If anyone has the solution could they please post it to the mailbase. Thanks David Price From rem-conf Wed Nov 19 06:05:05 1997 From rem-conf-request@es.net Wed Nov 19 06:05:04 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYAdr-00033t-00; Wed, 19 Nov 1997 05:58:07 -0800 Date: Wed, 19 Nov 1997 14:57:26 +0100 From: pate@clarinet.u-strasbg.fr (David PATE) Message-Id: <9711191357.AA08230@clarinet.u-strasbg.fr> To: rem-conf@es.net Subject: Re: mrouted 3.81 on Linux 2.0.30 X-Sun-Charset: ISO-8859-1 X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Thanks for answers. I have patched my kernel like it is explained at the bottom, but it still doesn't work. My netstat -r : Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 130.79.74.0 * 255.255.255.0 U 1500 0 0 eth0 127.0.0.0 * 255.0.0.0 U 3584 0 0 lo 224.0.0.0 * 240.0.0.0 U 1500 0 0 eth0 default api-cisco.u-str 0.0.0.0 UG 1500 0 0 eth0 and mtrace clarinet videonet : Mtrace from 130.79.6.130 to 130.79.74.22 via group 224.2.0.1 Querying full reverse path... 0 videonet.u-strasbg.fr (130.79.74.22) -1 videonet.u-strasbg.fr (130.79.74.22) DVMRP thresh^ 1 -2 clarinet.u-strasbg.fr (130.79.6.130) DVMRP thresh^ 8 -3 clarinet.u-strasbg.fr (130.79.6.130) Round trip time 12 ms and mtrace videonet clarinet : Mtrace from 130.79.74.22 to 130.79.6.130 via group 224.2.0.1 Querying full reverse path... * switching to hop-by-hop: 0 clarinet.u-strasbg.fr (130.79.6.130) -1 * * * Timed out receiving responses Perhaps receiver 130.79.6.130 is not a member of group 224.2.0.1, or no router local to it has a route for source 130.79.74.22, or multicast at ttl 64 doesn't reach its last-hop router for that source Please help me. DAVID ----- > In message <10989.868441790@kant>, Atanu Ghosh writes: > > I have just tried something similar between a Cisco running PIM and a > > linux box running 2.0.30. I don't think thats its possible to join > > mbone sessions on a linux box which is running a mrouted. The other > > machines on the subnet being seviced by the linux mrouted were able to > > join multicast sessions. > > > > It looks like the mrouted doesn't gets any notification when the local > > machine joins/leaves a multicast group. > > > > Atanu. > > Hi ! > > There are some patches (made by Brad Parker) available at > ftp://ftp.parker.boston.ma.us/pub/mbone/ > that are supposed to fix these problems. > These are for 2.0.27, but it is possible to add them to 2.0.30. > One of the files, ipmr.c, can replace the original 2.0.30 as it is > and the other, ip_forward.c, seem to be just a few lines (one really) > that has to be added/changed to the 2.0.30 version. > Here is a diff between the original 2.0.27 ip_forward.c and the > modified version: > > -------------------------------------------------------------------------------- > *** ip_forward.c Sun Apr 27 21:23:04 1997 > --- ORG/ip_forward.c Wed Oct 30 02:42:42 1996 > *************** > *** 404,414 **** > skb2->devÞv2; > #ifdef CONFIG_IP_MROUTE > if(is_frag&IPFWD_MULTITUNNEL) > ! #ifdef BROKEN > ! xxx ip_encap(skb,skb->len, dev2, raddr); > ! #else > ! ip_encap(skb, 0, dev2, target_addr); > ! #endif > else > { > #endif > --- 404,410 ---- > skb2->devÞv2; > #ifdef CONFIG_IP_MROUTE > if(is_frag&IPFWD_MULTITUNNEL) > ! ip_encap(skb,skb->len, dev2, raddr); > else > { > #endif > -------------------------------------------------------------------------------- > > Also, a few lines has to be added to /usr/include/linux/mroute.h: > > -------------------------------------------------------------------------------- > struct mfc_cache > { > struct mfc_cache *next; /* Next entry on cache line */ > __u32 mfc_mcastgrp; /* Group the entry belongs to */ > __u32 mfc_origin; /* Source of packet */ > vifi_t mfc_parent; /* Source interface */ > struct timer_list mfc_timer; /* Expiry timer */ > int mfc_flags; /* Flags on line */ > struct sk_buff_head mfc_unresolved; /* Unresolved buffers */ > int mfc_queuelen; /* Unresolved buffer counter */ > unsigned char mfc_ttls[MAXVIFS]; /* TTL thresholds */ > unsigned long mfc_bytecnt; /* <-- New field */ > unsigned long mfc_pktcnt; /* <-- New field */ > unsigned long mfc_wrong_if; /* <-- New field */ > }; > -------------------------------------------------------------------------------- > > With the above changes the 2.0.30 kernel will at least compile and run. > I have not yet had the opportunity to test that things works as expected > in conjuction with mrouted though... > > /Håkan > From rem-conf Wed Nov 19 06:07:58 1997 From rem-conf-request@es.net Wed Nov 19 06:07:57 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYAky-00037y-00; Wed, 19 Nov 1997 06:05:28 -0800 Sender: chandru@serabi.lkg.dec.com Message-Id: <3472EE5D.493F@serabi.lkg.dec.com> Date: Wed, 19 Nov 1997 08:49:17 -0500 From: "Chandrasekar.K" X-Mailer: Mozilla 3.0Gold (X11; I; OSF1 V4.0 alpha) Mime-Version: 1.0 To: David PATE Cc: David Price , rem-conf@es.net Subject: Re: mrouted 3.81 on Linux 2.0.30 References: <9711191104.AA07715@clarinet.u-strasbg.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list David(s), what version ur using? i was using 2.1.9 . i think u have to use version 2.1.35 or above. -chandru ---------------------------------------- Do all "Davids" have the same problem!! ------------------------------------------ > > > Hi David, > > > > i think u have to configure the route for the IP multicast net > > . like route add 224.0.0.0 eth0 > > or something like this. > > Of course. > > > > > sorry i could not give u exact command , since my linux box has crashed. > > > > but it is the problem of routing information. > > > > hope this will help. > > -chandru > > > > > > Thanks for your answer, but it seems to be a linux kernel bug. > > DAVID > ----- From rem-conf Wed Nov 19 17:18:40 1997 From rem-conf-request@es.net Wed Nov 19 17:18:39 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYL6k-0000jz-00; Wed, 19 Nov 1997 17:08:38 -0800 Date: Wed, 19 Nov 1997 17:08:29 -0800 (PST) From: Andrew Daviel Reply-To: Andrew Daviel To: RemConf List Subject: Video capture card for Iris Indigo ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list What (if any) video capture card is supported by the current Mbone tools (vic, nv ?) for an SGI Iris Indigo Entry 4000 ? Any ideas on $$, composite video/s-video NTSC in, and other stuff required (upgrading graphics card ??) I've just been looking at a couple of pages such as http://www.sgi.com/TasteOfDT/documents/video/lurker/ev1s.html http://www.sgi.com/Support/QNA/FAQ.book_1073.html which lead me to suspect I have a strong chance of screwing up and buying something that isn't supported ..... Andrew Daviel, TRIUMF From rem-conf Wed Nov 19 20:33:57 1997 From rem-conf-request@es.net Wed Nov 19 20:33:56 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYOF6-0002AN-00; Wed, 19 Nov 1997 20:29:28 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Wed, 19 Nov 1997 20:28:50 -0800 (PST) Message-Id: <199711200428.UAA05170@hille.msri.org> To: rem-conf@es.net From: Reply-to: nemo@comet.columbia.edu Subject: Pricing Differential Services on the Internet X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Pricing Differential Services on the Internet Date: Nov 20, 1997 Time: 17:00 GMT 1 hours Contact: nemo@comet.columbia.edu URL: http://comet.columbia.edu/activities/seminars/fall97/abs-nemo.html Description: his talk will review briefly the proposed differentiated service model, and then analyze the applicability of various pricing policies to it. Using simple models of user's valuation of delay, and a static traffic model based on measured http transfer sizes, we compare canonical pricing policies based on criteria of stability and controlability of demand. We end with rough estimates of actual prices that might result under realistic scenaria. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Thu Nov 20 00:09:12 1997 From rem-conf-request@es.net Thu Nov 20 00:09:11 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYRaw-0003LO-00; Thu, 20 Nov 1997 00:04:14 -0800 X-Authentication-Warning: thales.informatik.uni-mannheim.de: cjk owned process doing -bs Date: Thu, 20 Nov 1997 09:03:58 +0100 (MET) From: Christoph Kuhmuench X-Sender: cjk@thales Reply-To: Christoph Kuhmuench To: Andrew Daviel cc: RemConf List Subject: Re: Video capture card for Iris Indigo ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list On Wed, 19 Nov 1997, Andrew Daviel wrote: > Subject: Video capture card for Iris Indigo ? > > > What (if any) video capture card is supported by the current Mbone tools > (vic, nv ?) for an SGI Iris Indigo Entry 4000 ? > > Any ideas on $$, composite video/s-video NTSC in, and other > stuff required (upgrading graphics card ??) > > > I've just been looking at a couple of pages such as > http://www.sgi.com/TasteOfDT/documents/video/lurker/ev1s.html > http://www.sgi.com/Support/QNA/FAQ.book_1073.html > which lead me to suspect I have a strong chance of screwing up and > buying something that isn't supported ..... > > Andrew Daviel, TRIUMF > > As far as I know the vino, the galileo and the cosmo card are supported by vic. My experience is that only the vino card is useful for video conferences. I only got about 4-5 frames per second out of the galileo board. Cosmo was much better (exactly 30 frames per second with about 3-5MBit/s) but I could not reduce the number of frames per second. You get only 30 f/s or nothing. My suggestion: buy a Sun workstation. Regards, Chris ------------------------------------------------------------------------------ Christoph Kuhmuench email:cjk@pi4.informatik.uni-mannheim.de Praktische Informatik IV http://www.informatik.uni-mannheim.de/~cjk Universitaet Mannheim Tel: ++49 621 292 1554 L15,16 Fax: ++49 621 292 5745 68131 Mannheim Germany ------------------------------------------------------------------------------ From rem-conf Thu Nov 20 00:15:53 1997 From rem-conf-request@es.net Thu Nov 20 00:15:53 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYRlX-0003oy-00; Thu, 20 Nov 1997 00:15:11 -0800 Message-Id: <199711200814.AAA01375@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Christoph Kuhmuench cc: Andrew Daviel , RemConf List Subject: Re: Video capture card for Iris Indigo ? In-reply-to: Your message of "Thu, 20 Nov 1997 09:03:58 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Nov 1997 00:14:59 -0800 From: Amancio Hasty X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Or get a Pentium II 300MHz, a Bt848 based video capture + plus tuner for $77 from Fry's and run FreeBSD. Cheers, Amancio > > > On Wed, 19 Nov 1997, Andrew Daviel wrote: > > Subject: Video capture card for Iris Indigo ? > > > > > > What (if any) video capture card is supported by the current Mbone tools > > (vic, nv ?) for an SGI Iris Indigo Entry 4000 ? > > > > Any ideas on $$, composite video/s-video NTSC in, and other > > stuff required (upgrading graphics card ??) > > > > > > I've just been looking at a couple of pages such as > > http://www.sgi.com/TasteOfDT/documents/video/lurker/ev1s.html > > http://www.sgi.com/Support/QNA/FAQ.book_1073.html > > which lead me to suspect I have a strong chance of screwing up and > > buying something that isn't supported ..... > > > > Andrew Daviel, TRIUMF > > > > > > As far as I know the vino, the galileo and the cosmo card are supported by > vic. My experience is that only the vino card is useful for video > conferences. I only got about 4-5 frames per second out of the galileo > board. Cosmo was much better (exactly 30 frames per second with about > 3-5MBit/s) but I could not reduce the number of frames per second. You get > only 30 f/s or nothing. My suggestion: buy a Sun workstation. > > Regards, > Chris > > > ------------------------------------------------------------------------------ > Christoph Kuhmuench email:cjk@pi4.informatik.uni-mannheim.de > Praktische Informatik IV http://www.informatik.uni-mannheim.de/~cjk > Universitaet Mannheim Tel: ++49 621 292 1554 > L15,16 Fax: ++49 621 292 5745 > 68131 Mannheim > Germany > ------------------------------------------------------------------------------ > > > From rem-conf Fri Nov 21 08:16:23 1997 From rem-conf-request@es.net Fri Nov 21 08:16:23 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYvQF-0004v1-00; Fri, 21 Nov 1997 07:55:11 -0800 Message-ID: <315C9546C76FD01186210020AFD79C2B07D091@ntmail.ist.ucf.edu> From: "Sharp, Sean" To: "'rem-conf@es.net'" Subject: RE: UO Special Events Presents Steve Deering Date: Fri, 21 Nov 1997 10:55:02 -0500 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list What time will the presentation begin? It says 13:30 PST in your post, but the URL you listed says it starts at 3:30 PST. Sean > MBone Broadcast Announcement > ---------------------------- > >Title: > UO Special Events Presents Steve Deering >Date: > Nov 25, 1997 > >Time: > 13:30 PST8PDT 1.5 hours > >Contact: > multicast@lists.uoregon.edeu > >URL: > http://darkwing.uoregon.edu/~netcast/video/index.html From rem-conf Fri Nov 21 08:30:57 1997 From rem-conf-request@es.net Fri Nov 21 08:30:57 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYvuh-0005S2-00; Fri, 21 Nov 1997 08:26:39 -0800 Message-ID: <315C9546C76FD01186210020AFD79C2B07D092@ntmail.ist.ucf.edu> From: "Sharp, Sean" To: "'rem-conf@es.net'" Subject: RE: UO Special Events Presents Steve Deering Date: Fri, 21 Nov 1997 11:26:32 -0500 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list What time will the presentation begin? Your message says 13:30 PST, while the URL has the presentation scheduled to start at 3:30 PST. Sean Sharp Institute for Simulation and Training University of Central Florida From rem-conf Fri Nov 21 08:39:39 1997 From rem-conf-request@es.net Fri Nov 21 08:39:39 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYw53-0005oV-00; Fri, 21 Nov 1997 08:37:21 -0800 Message-Id: <199711211637.IAA14632@cs.uoregon.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: "Sharp, Sean" cc: rem-conf@es.net Subject: Re: UO Special Events Presents Steve Deering In-reply-to: Your message of "Fri, 21 Nov 1997 10:55:02 PST." <315C9546C76FD01186210020AFD79C2B07D091@ntmail.ist.ucf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Nov 1997 08:37:11 -0800 From: Daniel Zappala X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list > What time will the presentation begin? It says 13:30 PST in > your post, but the URL you listed says it starts > at 3:30 PST. The presentation will actually start at 4:00 PST (refreshments are at 3:30 and they won't be broadcast). > > Sean > > > > MBone Broadcast Announcement > > ---------------------------- > > > >Title: > > UO Special Events Presents Steve Deering > >Date: > > Nov 25, 1997 > > > >Time: > > 13:30 PST8PDT 1.5 hours > > > >Contact: > > multicast@lists.uoregon.edeu > > > >URL: > > http://darkwing.uoregon.edu/~netcast/video/index.html > From rem-conf Fri Nov 21 08:53:21 1997 From rem-conf-request@es.net Fri Nov 21 08:53:21 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYwEr-0006WV-00; Fri, 21 Nov 1997 08:47:29 -0800 From: "David M. Meyer" Message-Id: <199711211647.IAA07855@network-services.uoregon.edu> Subject: Re: UO Special Events Presents Steve Deering To: SSHARP@ist.ucf.edu (Sharp Sean) Date: Fri, 21 Nov 1997 08:47:05 -0800 (PST) Cc: rem-conf@es.net In-Reply-To: <315C9546C76FD01186210020AFD79C2B07D091@ntmail.ist.ucf.edu> from "Sharp, Sean" at Nov 21, 97 10:55:02 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Actually, 1600 PST. Sorry about the confusion. Dave According to Sharp, Sean: > > What time will the presentation begin? It says 13:30 PST in > your post, but the URL you listed says it starts > at 3:30 PST. > > Sean > > > > MBone Broadcast Announcement > > ---------------------------- > > > >Title: > > UO Special Events Presents Steve Deering > >Date: > > Nov 25, 1997 > > > >Time: > > 13:30 PST8PDT 1.5 hours > > > >Contact: > > multicast@lists.uoregon.edeu > > > >URL: > > http://darkwing.uoregon.edu/~netcast/video/index.html > > > From rem-conf Fri Nov 21 12:40:40 1997 From rem-conf-request@es.net Fri Nov 21 12:40:39 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xYznS-0000nN-00; Fri, 21 Nov 1997 12:35:26 -0800 Message-Id: <199711212028.MAA08993@ideal.jf.intel.com> From: "David Putzolu" To: , Cc: Subject: New ID - Heuristics for Utilizing ISSLOW Mechanisms w/out Announcement Protocols Date: Fri, 21 Nov 1997 12:40:01 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01BCF67A.95964EB0" Content-Transfer-Encoding: 7bit X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list This is a multi-part message in MIME format. ------=_NextPart_000_01BCF67A.95964EB0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all, I have just submitted a new draft titled, "Heuristics for utilizing ISSL Mechanisms for A/V Streams Over Low bandwidth Links in the Absence of Announcement Protocols". This draft will (tentatively) be named draft-putzolu-heuristic-00.txt. The abstract is attached. Any comments or corrections would be most appreciated! Cheers, David Putzolu dputzolu@ibeam.jf.intel.com ------=_NextPart_000_01BCF67A.95964EB0 Content-Type: application/octet-stream; name="Abstract.txt" Content-Transfer-Encoding: 7bit Content-Description: Abstract.txt (Text Document) Content-Disposition: attachment; filename="Abstract.txt" 1. Abstract The ISSLOW subgroup of the ISSL working group has defined a set of mechanisms for providing integrated services over low bandwidth links [1]. These mechanisms rely on an announcement protocol (typically RSVP [2]) to determine which streams require other than best-effort service and to determine what level and type of service to provide for such streams. It is anticipated that at least some of the mechanisms defined by the ISSLOW subgroup, specifically Compressed RTP [3] (CRTP) [4] and Multi-Channel Multi-Link PPP (MCML) [5], will be available well before RSVP has been widely deployed. Given the proliferation of applications streaming audio and video using the mechanisms defined in the AVT working group (e.g., RTP), a means of utilizing these mechanisms in the absence of an announcement protocol would be beneficial. Such means have been proposed in [6], but they require changes to applications so as to be able to indicate the need for special treatment. This document describes a set of heuristics for use with the mechanisms defined in the ISSLOW subgroup that provide an enhanced degree of service for audio/video streaming applications without requiring that changes be made to applications. The approach taken is to provide a default set of heuristics that implementations of MCML and CRTP can use to provide enhanced service over PPP links for audio and video streams without requiring any application or infrastructure changes. ------=_NextPart_000_01BCF67A.95964EB0-- From rem-conf Sat Nov 22 07:12:08 1997 From rem-conf-request@es.net Sat Nov 22 07:12:07 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xZH5K-0005mM-00; Sat, 22 Nov 1997 07:03:02 -0800 Message-Id: <199711221502.KAA05692@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rem-conf@es.net From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-civanlar-bmpeg-02.txt Date: Sat, 22 Nov 1997 10:02:55 -0500 Sender: scoya@cnri.reston.va.us X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Working Group of the IETF. Title : RTP Payload Format for Bundled MPEG Author(s) : R. Civanlar, G. Cash, B. Haskell Filename : draft-civanlar-bmpeg-02.txt Pages : 8 Date : 21-Nov-97 This document describes a payload type for bundled, MPEG-2 encoded video and audio data that may be used with RTP, version 2. Bundling has some advantages for this payload type particularly when it is used for video-on-demand applications. This payload type may be used when its advantages are important enough to sacrifice the modularity of having separate audio and video streams. A technique to improve packet loss resilience based on ''out-of-band'' transmission of MPEG-2 specific, vital information is described as an Appendix. A section on security considerations for this payload type is added. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-civanlar-bmpeg-02.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-civanlar-bmpeg-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-civanlar-bmpeg-02.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971122092444.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-civanlar-bmpeg-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-civanlar-bmpeg-02.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971122092444.I-D@ietf.org> --OtherAccess-- --NextPart-- From rem-conf Sat Nov 22 10:26:08 1997 From rem-conf-request@es.net Sat Nov 22 10:26:08 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xZK4m-0006sI-00; Sat, 22 Nov 1997 10:14:40 -0800 Message-Id: <3.0.1.32.19971122101305.00ce9ff8@sc-mail2.corpwest.baynetworks.com> X-Sender: knichols@sc-mail2.corpwest.baynetworks.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Sat, 22 Nov 1997 10:13:05 -0800 To: rem-conf@es.net From: Kathleen_Nichols@BayNetworks.COM (Kathleen Nichols) Subject: Van Jacobson's talk, Nov 25 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Note: There are currently no slides available for this talk, but background for the talk can be obtained at: ftp://ftp.ee.lbl.gov/papers/dsarch.pdf (This document is being submitted as an internet draft.) MBone Broadcast Announcement ---------------------------- Title: Towards Differentiated Services for the Internet Speaker: Van Jacobson, LBNL Date: Nov 25, 1997 Time: 12:00 EST 2 hours Contact: knichols@baynetworks.com Description: There appears to be an emerging, widespread, agreement that some sort of differentiated service capability must be added to the Internet. However most of the discussion has focused on details of the lowest-level queuing primitives needed to implement different services. While these details are very important, they have meaning only when viewed in a larger, architectural context of what sorts of services are actually viable and deployable in a system as large and heterogeneous as the Internet. This talk will try to expose some of the architectural context & constraints and explore some of the implications for low-level primitives and other aspects of the service. From rem-conf Tue Nov 25 06:14:54 1997 From rem-conf-request@es.net Tue Nov 25 06:14:54 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xaLP8-0000wE-00; Tue, 25 Nov 1997 05:51:54 -0800 Message-Id: <199711251351.IAA01376@hobbes.risq.qc.ca> X-Mailer: exmh version 2.0zeta 7/24/97 From: support@risq.qc.ca To: rem-conf@es.net Subject: CA*net II Workshop Broadcast Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Nov 1997 08:51:52 -0500 Sender: yboudrea@risq.qc.ca X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: CA*net II Workshop Date: Nov 26-27, 1997 Time: 9:00 - 17:00 EST Contact: support@risq.qc.ca URL: Http://www.canarie.ca/c2 From rem-conf Tue Nov 25 06:22:54 1997 From rem-conf-request@es.net Tue Nov 25 06:22:54 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xaLq5-0001P0-00; Tue, 25 Nov 1997 06:19:45 -0800 Message-Id: <3.0.1.32.19971125061822.00707968@sc-mail2.corpwest.baynetworks.com> X-Sender: knichols@sc-mail2.corpwest.baynetworks.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 25 Nov 1997 06:18:22 -0800 To: rem-conf@es.net From: Kathleen_Nichols@BayNetworks.COM (Kathleen Nichols) Subject: slides for Van Jacobson's talk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Slides for today's talk are now available at: ftp://ftp.ee.lbl.gov/talks/vj-baydsarch.pdf (or .ps) From rem-conf Tue Nov 25 09:40:41 1997 From rem-conf-request@es.net Tue Nov 25 09:40:41 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xaOr6-0006Y7-00; Tue, 25 Nov 1997 09:33:00 -0800 Date: Tue, 25 Nov 1997 09:29:48 -0800 (PST) From: "T. Todd Elvins" To: scwpf@sdsc.edu, web-watchers -- K Claffy , rem-conf@es.net, webteam@qualcomm.com, webheads@sio.ucsd.edu, java-ucsd@mib.org, flesner@nosc.mil Cc: talks@ucsd.edu Subject: Wednesday night Web Programmer's Forum - FREE Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Web programmer's, We have a GREAT forum lined up for tomorrow night, Weds, 11/26, 7pm, at San Diego Supercomputer Center. You don't want to miss this one. Our keynote speakers are Stu Harris and Gayle Kidder, Point Loma-based authors, who will answer the question "What Exactly is Dynamic HTML?" And Stu is going to give away a few copies of their book !! And our capstone speaker will be Paul Colton, Live Software, who will speak on "Developing Java Servlets" This will also be broadcast live on the MBONE. Details, Directions, and Parking info are at our web site www.sdsc.edu/scwpf See you Wednesday, Todd ----------------------------------------------------------------- T. Todd Elvins todd@sdsc.edu Science Department, San Diego Supercomputer Center University of California, San Diego (619) 534-5128 P.O. Box 85608 FAX (619) 534-5117 San Diego, CA 92186-9784 http://www.sdsc.edu/~todd/ ----------------------------------------------------------------- From rem-conf Tue Nov 25 10:44:26 1997 From rem-conf-request@es.net Tue Nov 25 10:44:26 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xaPuH-0005Dv-00; Tue, 25 Nov 1997 10:40:21 -0800 Date: Tue, 25 Nov 1997 10:38:37 -0800 (PST) From: "T. Todd Elvins" To: scwpf@sdsc.edu, web-watchers -- K Claffy , rem-conf@es.net, webteam@qualcomm.com, webheads@sio.ucsd.edu, java-ucsd@mib.org, flesner@nosc.mil Subject: Re: Wednesday night Web Programmer's Forum - FREE (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Web programmers, Rick cleverly pointed out that the MBONE participants should also be eligible to receive one of Stu and Gayle's books. So here's what we'll do. We'll pick a random number and give a book to the person in that slot as listed on the MBONE broadcaster. See you Wednesday, Todd ---------- Forwarded message ---------- Date: Tue, 25 Nov 1997 13:04:49 -0500 From: "R. P. Channing [Rick] Rodgers" To: todd@sdsc.edu Subject: Re: Wednesday night Web Programmer's Forum - FREE Todd, You ought to reserve one copy of the their book to give away to someone in the MBONE audience (perhaps by random draw from the names listed in vat/rat). Would be a nice way of making us feel more involved... Cheerio, Rick Rodgers > From todd@SDSC.EDU Tue Nov 25 12:49:25 1997 > Date: Tue, 25 Nov 1997 09:29:48 -0800 (PST) > From: "T. Todd Elvins" > To: scwpf@SDSC.EDU, web-watchers -- K Claffy , rem-conf@es.net, > webteam@qualcomm.com, webheads@sio.ucsd.edu, java-ucsd@mib.org, > flesner@nosc.mil > Cc: talks@ucsd.edu > Subject: Wednesday night Web Programmer's Forum - FREE > Mime-Version: 1.0 > X-Mailing-List: > X-Loop: rem-conf@es.net > > > Web programmer's, > > We have a GREAT forum lined up for tomorrow night, Weds, 11/26, 7pm, > at San Diego Supercomputer Center. You don't want to miss this one. > > Our keynote speakers are Stu Harris and Gayle Kidder, Point Loma-based > authors, who will answer the question "What Exactly is Dynamic HTML?" > And Stu is going to give away a few copies of their book !! > > And our capstone speaker will be Paul Colton, Live Software, > who will speak on "Developing Java Servlets" > > This will also be broadcast live on the MBONE. > > Details, Directions, and Parking info are at our web site > > www.sdsc.edu/scwpf > > See you Wednesday, > Todd > > ----------------------------------------------------------------- > T. Todd Elvins todd@sdsc.edu > Science Department, San Diego Supercomputer Center > University of California, San Diego (619) 534-5128 > P.O. Box 85608 FAX (619) 534-5117 > San Diego, CA 92186-9784 http://www.sdsc.edu/~todd/ > ----------------------------------------------------------------- > > > > From rem-conf Tue Nov 25 14:22:46 1997 From rem-conf-request@es.net Tue Nov 25 14:22:45 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xaTCQ-0004Rt-00; Tue, 25 Nov 1997 14:11:18 -0800 X-Authentication-Warning: msri.org: smap set sender to using -f Date: Tue, 25 Nov 1997 14:10:39 -0800 (PST) Message-Id: <199711252210.OAA07073@hille.msri.org> To: rem-conf@es.net From: Reply-to: davidwu@bmrc.berkeley.edu Subject: Pricing TCP Based Internet Services through the Web X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list MBone Broadcast Announcement ---------------------------- Title: Pricing TCP Based Internet Services through the Web Date: Nov 26, 1997 Time: 12:40 PST8PDT 2 hours Contact: davidwu@bmrc.berkeley.edu URL: http://bmrc.berkeley.edu/298/w14.html Description: Jon Crowcroft, Department of Computer Science, University College London Pricing TCP Based Internet Services through the Web (Wednesday November 26, 1997 12:30-2:00 PDT 405 Soda Hall) Jon Crowcroft Department of Computer Science University College London To be filled in. mbone broadcast schedule http://www.msri.org/mbone From rem-conf Wed Nov 26 06:53:44 1997 From rem-conf-request@es.net Wed Nov 26 06:53:43 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xaiUr-00061j-00; Wed, 26 Nov 1997 06:31:21 -0800 Message-Id: <199711261431.JAA15247@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce@ns.ietf.org Cc: rem-conf@es.net From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-avt-rtp-mib-01.txt Date: Wed, 26 Nov 1997 09:31:15 -0500 Sender: cclark@cnri.reston.va.us X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list --NextPart A Revised Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Working Group of the IETF. Title : Real-Time Transport Protocol Management Information Base Author(s) : S. Naudus, M. Baugher, J. Du Filename : draft-ietf-avt-rtp-mib-01.txt Pages : 33 Date : 24-Nov-97 This memo defines an experimental Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Real-Time Transport Protocol systems [1]. Comments should be made to the IETF Audio/Video Transport Working Group at rem-conf@es.net. This memo does not specify a standard for the Internet community. Internet-Drafts are available by anonymous FTP. Login wih the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-avt-rtp-mib-01.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-avt-rtp-mib-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-avt-rtp-mib-01.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971124174801.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-avt-rtp-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-avt-rtp-mib-01.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971124174801.I-D@ietf.org> --OtherAccess-- --NextPart-- From rem-conf Wed Nov 26 08:06:37 1997 From rem-conf-request@es.net Wed Nov 26 08:06:37 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xajqF-0006ql-00; Wed, 26 Nov 1997 07:57:31 -0800 To: rem-conf@es.net From: info@infowatch.net (Info Desk) Subject: Advertisement: Website Hosting Date: Tue, 25 Nov 1997 19:19:14 -0500 Message-ID: <19971125231431839.EPI174@mail1.infowatch.net> X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list ----------------------------------------------------------------------------- If you wish to be excluded from any future mailings, reply with "remove" in the subject header. ----------------------------------------------------------------------------- http://www.infowatch.net InfoWatch would like to introduce our complete Hosting and Promotional service. FOR ONLY $29.95 PER MONTH ! * 30 MB (megabytes) of disk space * 1000 MB = 1 GB (gigabyte) of data transfer per month * 8 E-mail accounts * INTERNATIONAL Hosting * Access to your account anytime via the Web Control Panel * Full MS Front Page support * Unlimited FTP updates * Personal CGI directory for your own scripts (or use ours) * Comprehensive statistics program shows you everything * E-mail forwarding, auto responders and vacation reply * Domain name registration (www.yourname.com) * Register your domain with over 250 search engines-FREE * Friendly customer support * Inquire about our $24.95 plan If for any reason you are not satisfied with InfoWatch's service after 30 days, we will transfer you back to your original host and pay any transfer fees. http://www.infowatch.net info@infowatch.net From rem-conf Wed Nov 26 12:06:37 1997 From rem-conf-request@es.net Wed Nov 26 12:06:37 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xanXu-000388-00; Wed, 26 Nov 1997 11:54:50 -0800 Message-Id: <199711261954.OAA21020@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce@ns.ietf.org Cc: rem-conf@es.net From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-avt-jpeg-new-00.txt,.ps Date: Wed, 26 Nov 1997 14:54:42 -0500 Sender: cclark@cnri.reston.va.us X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Working Group of the IETF. Title : RTP Payload Format for JPEG-compressed Video Author(s) : L. Berc, R. Frederick, B. Fenner, S. McCanne, P. Stewart Filename : draft-ietf-avt-jpeg-new-00.txt,.ps Pages : 24 Date : 24-Nov-97 This memo describes the RTP payload format for JPEG video streams. The packet format is optimized for real-time video streams where codec parameters change rarely from frame to frame. This document is a product of the Audio-Video Transport working group within the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at rem-conf@es.net and/or the author(s). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-avt-jpeg-new-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-avt-jpeg-new-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-avt-jpeg-new-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971126143755.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-avt-jpeg-new-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-avt-jpeg-new-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971126143755.I-D@ietf.org> --OtherAccess-- --NextPart-- From rem-conf Wed Nov 26 12:58:12 1997 From rem-conf-request@es.net Wed Nov 26 12:58:11 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xaoQW-0003xS-00; Wed, 26 Nov 1997 12:51:16 -0800 Date: Wed, 26 Nov 1997 12:50:48 -0800 (PST) From: "T. Todd Elvins" To: scwpf@sdsc.edu, rem-conf@es.net, webteam@qualcomm.com, webheads@sio.ucsd.edu, java-ucsd@mib.org, flesner@nosc.mil, talks@ucsd.edu Subject: Christmas @ SCWPF meeting tonight Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list Web Programmers, Its Christmas here at SCWPF. Not only do we have four books (hot off the press) to give away, but we now have four (4) CDs to give away. One item of each media will be given to a person watching the meeting on the MBONE. Bring a business card to drop in the hat for the drawing. See you tonight. Drive safe. Todd www.sdsc.edu/scwpf From rem-conf Wed Nov 26 14:36:51 1997 From rem-conf-request@es.net Wed Nov 26 14:36:50 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xapsX-0005HX-00; Wed, 26 Nov 1997 14:24:17 -0800 Date: Wed, 26 Nov 1997 17:20:42 -0500 From: garys@python.pictel.com (Gary Sullivan) Message-Id: <9711262220.AA07310@python.pictel.com> To: itu-adv-video@listserv.iterated.com, rem-conf@es.net Subject: H.263+ RTP Packetization X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list To ITU-T Q.15/SG16 and IETF AVT Experts, Attached is the plain-text version of some comments I have written regarding the drafted RTP payload packetization format specification for H.263+. I understand that this topic will be discussed at the IETF meeting on Dec 10&11 as well as at the ITU-T Q.15/16 meeting Dec 2-5. Best Wishes, Gary Sullivan PictureTel Corp. M/S 635 Tel: +1 978 623 4324 100 Minuteman Road Fax: +1 978 749 2804 Andover MA 01810 USA Email: garys@pictel.com ____________________________________________________ ITU - Telecommunications Standardization Sector STUDY GROUP 16 Video Coding Experts Group _________________ Third Meeting: Eibsee, Germany, 2-5 December 1997 Document: Q15-C-39 Filename: q15c39.txt Date generated: 11/25/97 Question: Q.15/16 Source: Gary Sullivan PictureTel Corporation 100 Minuteman Rd. Andover, MA 01810 Tel: +1 978 623 4324 Fax: +1 978 749 2804 Email: garys@pictel.com Title: Comments on Draft RTP Payload Packetization Format Specification for H.263+ Purpose: Information _____________________________ This contribution contains a few comments regarding the draft RTP payload packetization document for H.263+ as circulated on the itu-adv-video@listserv.iterated.com email reflector on 13 November 1997. Some or all of these comments may be obsolete if the draft has been revised since that time. I first wish to say that I am very pleased to see that the work on this topic is progressing and that it in fact appears to be reaching a pretty stable specification. However, I would like to express a few (mostly minor) concerns. Although the work toward the specification of the packetization is being conducted primarily in the IETF, the ITU-T video coding experts would also presumably be interested in these remarks as well. Please note that none of the changes that I request below would have any effect of invalidating a packetization process or a packetized bitstream designed according to the existing draft [Oops - that's not true about item 2d]. 1) The introduction (section 1) should mention Reference Picture Selection along with Slices and ISD mode as a key aspect of H.263+ affecting packet-network transport use. 2) The specified format seems a bit heavy on the amount of overhead recommended or required. Specifically: a) It *requires* (Sec. 4.2, first sentence) a copy of the entire picture header to be attached to every packet that starts with a GOB or slice start code. Although I think it is a *great* idea to allow such extra picture headers to be attached, I strongly suggest changing the text to *allow* and perhaps to *encourage*, but not to require them. The extra picture headers can be very repetitive and unnecessary in many circumstances, and can result in a great deal of extra data being sent. b) It strongly recommends a header and a separate packet for every GOB. But is it a bad idea, for example, to put two GOBs in each packet and only have a header on the first of each two (cutting the overhead in half)? I think the wording on this could be softened a little bit (although the present wording does allow freedom for implementers as I read it). c) It recommends a complete picture header (UFEP = '001') on every picture. In some circumstances, this may be unnecessary since the OPPTYPE and its accompanying data may be the same for many, many pictures in a row and since GFID will let the decoder at least know when it changes (and since a complete picture header will appear periodically anyway). I think the wording on this could be softened a little bit (although the present wording does allow freedom for implementers as I read it). d) When sending a redundant copy of a picture header, the first six bits ('100000') are always the same, and are therefore unnecessary. I suggest not sending them. I suppose the motivation is ease of byte-oriented processing, but it doesn't seem like that much of a burden to always shift the header by six bits. 3) The description of the TID and Trun fields is clearly inadequate (Sec. 4). Their use is entirely undefined, and the reference given as a citation (draft 20 of H.263+) will be of little or no help to the reader trying to figure them out. (Also, I suspect that TID and Trun will sometimes be present in INTRA pictures, although no INTRA picture will use the RPS mode of H.263+.) 4) It may be useful to allow redundant picture headers to be attached to packets already containing picture headers, and to allow the redundant picture header attached to packets that begin with a GSC or SSC to be altered in one key way. If the picture header in the H.263+ payload bitstream itself is an abbreviated picture header (UFEP = '000'), then it would be useful to allow the packetization process to construct and attach a redundant complete picture header (rather than attaching a copy of the abbreviated picture header). In this way, the error robustness of the system can be enhanced without increasing the bit rate of the payload or adding knowledge of the packetization process to the encoder which is generating the payload bitstream. 5) The draft as I have it appears not to be dated. Dating the document would be helpful to establish when the draft has become obsolete or which of two versions is newer. Again, however, I wish to say that my overarching sentiment is that I am pleased with the progress of work on this topic. From rem-conf Wed Nov 26 17:59:53 1997 From rem-conf-request@es.net Wed Nov 26 17:59:52 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xat2f-0006ie-00; Wed, 26 Nov 1997 17:46:57 -0800 Date: Wed, 26 Nov 1997 17:35:13 -0800 From: Allyn.Romanow@eng.Sun.COM (Allyn Romanow) Message-Id: <199711270135.RAA15857@offshore.eng.sun.com> To: rem-conf@es.net Subject: ADAPTS BOF at DC IETF Cc: Harald.T.Alvestrand@uninett.no, allyn@jurassic.eng.Sun.COM, moore@cs.utk.edu X-Sun-Charset: US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list There will be a BOF on Adaptive Applications Support (ADAPTS)- in the Transport area, Tuesday from 15:45-18:00. This is specifically adaptive applications, not general QoS :) Although the presentation time is already filled up, the main purpose of the BOF is to see what can usefully be done in a WG. So, please bring your ideas about what a WG can accomplish in this domain- There is as yet no separate mailing list now, one will be created after the BOF if a WG is created. --------------------- (ADAPTS) ADaptive APplicaTions Support: BOF Description Adaptive applications, those that can adapt their resource requirements to variations in network resources, can provide a significant reduction in Internet congestion. In addition, adaptive applications can offer much better quality to end users than can non-adaptive applications under varying network conditions. Such applications will represent an important piece in the solution to the current Internet congestion control/QoS (quality of service) problems. The technology for making audio and video applications adaptive has been under development by researchers over the last 10 years. Applications built on protocols that do not do congestion control can hamper the performance of the Internet. TCP backs off in the face of congestion but other transport protocols, such as UDP and RTP, do not, and thus can contribute significantly to network congestion. Many Internet researchers and developers have come to believe that the network forwarding devices (e.g. routers) must do internal congestion control in order to provide robust and viable network service. A variety of schemes have been suggested for policing traffic and managing router buffer queues. In such a controlled environment, non-adaptive applications will fare badly while those applications which can adapt will provide better performance to the user. This BOF will consider what can constructively be done to further the development of adaptive applications. For example, what additional protocol support is needed from RTP? While the technology for making applications adaptive, does not require standardization, it would be helpful to publish an Informational RFC which states what behavior is required from applications to perform well in the Internet today and in particular in an Internet where the routers implement internal congestion control. It would also be useful to make clear the issues involved in constructing adaptive applications, and to show some example mechanisms and algorithms which are known to work. This BOF focuses on best-effort traffic, rather than traffic for which QoS reservations of some kind have been made (by RSVP for example). It is reasonable to expect that best effort traffic will be the bulk of the Internet traffic in the near future. ------------------------------------------------- Agenda Agenda Bashing (5 min) Introduction - (5) Presentations Why Adaptive Apps are Necessary - Van Jacobson (15) Adaptive Apps Tutorial - Jean Bolot (25) Changes needed in RTP - Steve Casner (10) Motivation - Christian Huitema - Motivation (10) Issues, examples, RTP - K. Lakshman (10) Discussion of Proposed Working Group Activities (55) Informational RFC Straw outline Protocol support Other From rem-conf Thu Nov 27 19:49:23 1997 From rem-conf-request@es.net Thu Nov 27 19:49:22 1997 Received: from list by mail1.es.net with local (Exim 1.71 #1) id 0xbH6m-0004Qh-00; Thu, 27 Nov 1997 19:28:48 -0800 X-Authentication-Warning: eratosthenes.informatik.uni-mannheim.de: whd owned process doing -bs Date: Fri, 28 Nov 1997 04:28:41 +0100 (MET) From: Wieland Holfelder X-Sender: whd@eratosthenes To: Multicast Backbone , Remote Conferencing Subject: MBone VCR on Demand Service (MVoD) *new* Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailing-List: X-Loop: rem-conf@es.net Precedence: list ...for all those people that asked me so often and for me to get real feedback and to make all these valuable MBone session available for our childrens and grandchildrens and to fill all those empty disks... a binary release of the MBone VCR on Demand Service (MVoD) is now available for download at the MVoD home page at: http://www.informatik.uni-mannheim.de/~whd/mvod MVoD is the follow up project of the MBone VCR (which will no longer be supported) and brings a lot of enhancements to the old MBone VCR (well in fact it has not much to do with it anymore). Some of the new features: - distributed client/server architecture - remote playback and recording on demand - fully RTPv2 compatible - interface to SAP/SDP - multi user capable - multi session capable - playback per multicast or unicast - scheduling of playback or record commands in the background - and more... The package comes with four components, an MVoD Client, an MVoD Server, an RTP DataPump daemon and an MVoD Administration tool. Client, Server and Admin Tool are pure Java (JDK 1.1), the RTP DataPump is written in C++. Communication between Client and Server is Corba based (Java IDL), communication between Server and RTP DataPump is realized with the RTP DataPump Control Protocol (RDCP) which is a fully text based protocol much like RTSP. The communication between Admin Tool and Server is implemented with Java RMI. Did we forget any RPC mechanism? For installation instructions see the README in the package. Supported platforms for the RTP DataPump in this release: - SUN Sparc Solaris 2.6 - SUN Sparc Solaris 2.5.1 - DEC Alpha OSF 4.0 - SGI Mips Irix 6.2 - i586 Linux (kernel version 2.30 or higher) This project is part of my PhD Thesis, any feedback is more then welcome. Special thanks goes to Achim Steinacker, Markus Kaas, Matthias Mattsson, Michael Grundel, Reinhard Kirchner, Christian Bartolomae and many others that supported me during the project! Enjoy, -- Wieland --------------------------------------------------------------------- Wieland Holfelder University of Mannheim Praktische Informatik IV Phone: +49-621-292-5679 L 15,16 Fax : +49-621-292-5745 68131 Mannheim whd@pi4.informatik.uni-mannheim.de Germany http://www.informatik.uni-mannheim.de/~whd ---------------------------------------------------------------------