From rem-conf Tue May 02 11:13:36 2000 
From rem-conf-request@es.net Tue May 02 11:13:34 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12mgte-0002Gl-00; Tue, 2 May 2000 10:55:46 -0700
Received: from gumby.cs.berkeley.edu [128.32.32.38] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12mgtc-0002Gb-00; Tue, 2 May 2000 10:55:44 -0700
Received: from sockeye (sockeye.CS.Berkeley.EDU [128.32.36.74])
	by gumby.cs.berkeley.edu (8.9.3/8.9.3) with SMTP id KAA16496;
	Tue, 2 May 2000 10:31:46 -0700
Message-Id: <3.0.3.32.20000502103000.0094da50@plateau.cs.berkeley.edu>
X-Sender: florissa@plateau.cs.berkeley.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 02 May 2000 10:30:00 -0700
To: (Recipient list suppressed)
From: Florissa Colina <florissa@bmrc.berkeley.edu>
Subject: 5/3 Design and Evaluations of Multimedia Proxy Caching
  Mechanisms for the Internet -- Reza Rejaie, AT&T Labs - Research  
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Berkeley Multimedia, Graphics and Interfaces Seminar

Design and Evaluations of Multimedia Proxy Caching Mechanisms for the Internet

Wednesday May 3, 2000 
1:10-2:30 p.m. PDT
Fujitsu Seminar Room (405 Soda Hall) 

Reza Rejaie
AT&T Labs - Research 

Most of the existing Internet multimedia streaming applications are based
on the client-server architecture. This architecture has two major
limitations: 1) The quality of delivered streams is limited to the
bottleneck bandwidth between the server and the client. Thus a client with
a high bandwidth local connectivity may receive low quality streams due to
a remote bottleneck. 2) Its scalability is limited, in that it is difficult
to support a large number of concurrent high quality sessions due to
network and server load. Multimedia proxy caching (MCaching) is a natural
extension of the client-server architecture that addresses both limitations
simultaneously. The idea is to cache popular streams with appropriate
quality at a proxy close to interested clients. Thus the proxy can
effectively enhance the delivered quality and improve scalability by
significantly reducing the load on the network and the server. 

In this talk, we address the design and performance evaluations of MCaching
mechanisms. First the design of an efficient MCaching mechanism for
layered-encoded streams is outlined. We observe that in addition to cache
efficiency (measured by hit ratio), MCaching introduces the notion of
``quality'' for delivered streams as a new dimension to Web caching. Thus
performance of MCaching mechanisms should be collectively evaluated along
both dimensions caching efficiency and delivered quality. We identify a
fundamental tradeoff between these two dimensions. Our simulation results
show that our proposed MCaching design can adaptively exploit this tradeoff
to improve overall performance whereas simple extension of current Web
caching schemes can only enhance the performance along one dimension.
---------------

The seminar is broadcast live on the Internet Mbone and as a Real Networks
G2 broadcast.

You can connect to the live RealNetworks broadcast at:

http://media2.bmrc.berkeley.edu/bibs/schedule.cfm 
You'll see a link to cs298-5/real networks/live programs.  

You can also directly put in this url into the Real Player: 
rtsp://media2.bmrc.berkeley.edu/encoder/cs298-5.rm

To do so you will need to have the "Real Player G2" installed, which is
available from:
http://www.real.com/products/player/downloadrealplayer.html

To tune into the Internet MBone broadcast, look for the announcement in
your MBone session directory program ('sdr').  If you are not receiving the
announcement you may be able to receive the session by manually configuring
the client programs ('vic', and 'vat') with the session addresses:

low bit rate
	video: 233.0.25.1/22334
	audio: 233.0.25.2/22446

medium bit rate
	video: 233.0.25.129/22334
	audio: 233.0.25.2/22446

You can get further information about this seminar, and access to replays
of previous seminars at the MIG Seminar web page:

http://bmrc.berkeley.edu/298/index.html

Sponsored by the Berkeley Multimedia Research Center 




From rem-conf Wed May 03 01:45:58 2000 
From rem-conf-request@es.net Wed May 03 01:45:57 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12mudj-0002Nr-00; Wed, 3 May 2000 01:36:15 -0700
Received: from dyn83.access4.nyc.i-2000.net (oemcomputer) [207.97.128.248] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12mude-0002Nh-00; Wed, 3 May 2000 01:36:12 -0700
From: "Scott" <scot@grabmail.com>
To: <rem-conf@es.net>
Subject: The BEST PRICES on Ink-Jet and Toner cartridges ANYWHERE!!!
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Wed, 3 May 2000 04:32:18
Message-Id: <E12mude-0002Nh-00@mail1.es.net>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

INK-JET AND TONER CARTRIDGES ARE EXPENSIVE

If you are tired of paying ridiculous prices for 
ink-jet, laser printer, copier, and fax supplies, call:

First Class Print Supply

TOLL FREE - 1-877-302-8025

VISA  /  MASTERCARD  /  AMEX

FREE SHIPPING AVAILABLE!!!

One of our representatives will be happy to quote you the
lowest prices on the net for ANY of your ink-jet, laser, fax,
or copier supplies.

9am - 12midnight  7 days a week

Residential and Commercial Customers Welcome!

Check out a sample of our prices:
HP 51645A - $17.99
HP 51626A - $16.99
Epson Black cartridges - $11.99
Epson Color cartridges - $13.99
Canon BC-20 - $18.99
Canon BCI-21Bk - $4.99
Canon BCI-21Cl - $11.99

Please call Toll Free number. If you reply to this message,
one of our sales representatives may not receive your inquiry
on a timely basis.

First Class Print Supply
1060 Neshaminy Valley Road
Bensalem, PA 19020
TOLL FREE - 1-877-302-8025
__________________________________________________
This message is sent in compliance of the new e-mail bill: 
SECTION 301. Per Section 301, Paragraph (a)(2)(C) of S. 1618, 
http://www.senate.gov/~murkowski/commercialemail/S771index.html
Further transmissions to you by the sender of this email may be 
stopped at no cost to you by sending a reply to this email address
with the word "remove" in the subject line.

IF YOU REPLY TO THIS MESSAGE WITH THE WORD
"REMOVE" IN THE SUBJECT HEADING, THIS EMAIL
ADDRESS WILL NEVER AGAIN RECEIVE MAIL FROM 
OUR COMPANY.
___________________________________________________

CALL NOW FOR A FREE PRICE QUOTE!!!
TOLL FREE - 1-877-302-8025




From rem-conf Wed May 03 04:32:38 2000 
From rem-conf-request@es.net Wed May 03 04:32:35 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12mxKP-0004MY-00; Wed, 3 May 2000 04:28:29 -0700
Received: from bells.cs.ucl.ac.uk [128.16.5.31] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12mxKI-0004MO-00; Wed, 3 May 2000 04:28:24 -0700
Received: from eucharisto.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.24505-0@bells.cs.ucl.ac.uk>; Wed, 3 May 2000 12:28:11 +0100
To: rem-conf@es.net
Subject: Draft AVT minutes
Date: Wed, 03 May 2000 12:28:10 +0100
Message-ID: <4550.957353290@cs.ucl.ac.uk>
From: Colin Perkins <C.Perkins@cs.ucl.ac.uk>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Folks,

A first draft of the AVT minutes from the Adelaide meeting is attached
below. Please send any comments to me by Monday 8th May, so I can submit
these to the secretariat. Note that copies of the presentation slides are
available at http://www-mice.cs.ucl.ac.uk/multimedia/misc/avt/IETF47/slides/

Thanks,
Colin

-------------------------------------------------------------------------------
Minutes of the Audio/Video Transport Working Group

Reported by Colin Perkins and Steve Casner.

The audio/video transport working group met twice at the 47th IETF in
Adelaide. In the first session the group discussed the update of the RTP
specification, work on a new profile for unicast RTP with retransmission,
and RTP header compression and multiplexing. The second session included
discussion of a number of payload formats, transport of MPEG-4, and
authentication of RTP streams.

The meeting started with a review of work in progress. A number of RFCs 
have been published since the last meeting:
- RTP payload format for generic FEC (RFC 2733)
- Guidelines for authors of RTP payload formats (RFC 2736)
- Sampling group membership (RFC 2762)
In addition, a number of drafts are with the IESG, awaiting publication:
- RTP MIB
- RTP payload format for DMTF tones
- RTP payload format for real-time pointers

The working group last call on the RTP specification and audio/video profile 
concluded at the Washington DC meeting, and the set of edits agreed at that 
meeting were completed in January, resulting in draft-ietf-avt-rtp-new-06.txt 
and draft-ietf-avt-profile-new-08.txt. 

A number of additional minor edits have since been made to the RTP
specification, based on comments made on the mailing list, leading to
draft-ietf-avt-rtp-new-07.txt. Updates for the profile text on G.729 and
G.723.1 have been received from the ITU-T, but have yet to be incorporated.

Considering the companion documents to the RTP specification, the MIME
registration document (draft-ietf-avt-rtp-mime-02.txt) has had L16
pre-emphasis parameters added, whilst the RTCP bandwidth modifiers document
(draft-ietf-avt-rcp-bw-01.txt) has not changed (just an increase in version
number, to prevent the draft expiring). Both of these are intended for
proposed standard. 

The RTP specification and audio/video profile are considered ready for IETF
last call, however they cannot be issued as draft standard RFCs until an
interoperability statement has been produced. 

The current status of the testing was presented by Colin Perkins. There are a 
number of drafts listing interoperability requirements and testing strategies:
- draft-ietf-avt-rtp-interop-02.txt 
- draft-ietf-avt-profile-interop-00.txt
- draft-ietf-avt-rtptest-02.txt
which have not changed since the last meeting. There is also a web page 
  http://www-mice.cs.ucl.ac.uk/multimedia/mist/avt/RTPinterop/
showing the current status. It was noted that progress has been slow and
that we urgently require interoperability statements from implementors of
rtp and the audio/video profile.

In particular, please contact the working group chairs if you have an
implementation which implements any of the following features of RTP:
padding, header extension, SDES PHONE/LOC/PRIV, BYE with multiple
SSRC/reason text, RTCP APP packets, encryption, RTCP reconsideration
algorithms and step join back-off, SSRC collision/loop detection,
modification of the RTCP bandwidth fraction, or transport using TCP.

Furthermore, if you have implemented any of the following codecs and have
tested against another implementation, please contact the chairs: 1016,
G.726-32, G.723, G.722, QCELP, G.728, G.729, GSM HR/EFR, PCMA, CellB, JPEG,
MPT, MP1S, MP2P, BMPEG, H.263, H.263+, BT.656.

The other area of discussion relating to the base RTP specification was
congestion control. Steve Casner noted that the IESG are concerned that RTP
does not implement congestion control, and that this has the potential to
harm the network. Other protocols are required to have congestion control
to advance on the standards track, why should RTP be exempt?

It was suggested that the requirements for congestion control are, to some
extent, profile specific: it makes sense to include a warning of the dangers 
of not implementing congestion control in the main RTP specification, but to
defer details to the profiles. A number of people agreed with this, noting
also that there is not much more we can design in right now, but a discussion 
of how to do congestion control would be a useful addition - exploring the 
design space for adaptation, and why it's needed. 

Mark Handley noted that we have work ongoing with the retransmission profile
for unicast, which needs to have strong congestion control. The existing
A/V profile also needs a discussion of the TCP-equivalent rate and when to
stop or adapt if your loss rate exceeds that. Steve Casner asked if the
existing feedback from RTCP was sufficient to perform rate adaptation for
congestion control. Mark Handley answered that it probably was not, but
should be sufficient to know when to leave the session.

The consensus of the group was that the main RTP spec will mention that
congestion control is important, but will defer to the profiles for the
details. Mark Handley volunteered to write the congestion control section
for the A/V profile, which he did before end of this IETF.  The
suggested text will be discussed on the mailing list.

The next items for discussion were retransmission schemes for RTP packets,
and RTCP reporting extensions. 

Colin Perkins presented work on RTCP Reporting Extensions for Timur Friedman 
(draft-friedman-avt-rtcp-report-extns-00.txt). This proposes a framework to
extend SR/RR packets, using profile specific reporting extensions. This
comprises a minimal header (two fields only: type and length) with several
proposed uses:
- Run length encoding (RLE) of the packet loss pattern
- RLE of duplicates
- List of timestamps
- Detailed loss/duplicate/jitter statistics

The motivation for the work is that RTCP SR/RR packets include limited 
information, and a number of applications (e.g. MINC and MRM) can use
extended statistics if provided in a uniform format. There are a number 
of open issues: How to handle large extensions? Include all extensions?  
Some?  Which? As extensions to the SR/RR reception report array, or in
a separate APP packet?  Feedback is solicited.

The next presentation was on the subject of RTCP-based retransmission
(draft-podolsky-avt-rtptx-01.txt) by Koichi Yano. The changes from the
previous version include:
- Now posed as a new profile, RTP/RX, which inherits the A/V profile,
  except for the RTCP interval (it allows immediate NACKs, but still keeps
  the average bandwidth limit) and the provision of a new RTCP packet type
  for NACKs (including first sequence number, 16 bit loss bitmap, and SSRC)
- The SSRC is now included in NACK packets
- It has been simplified: only for NACK (former draft defined a
  multi-purpose ACK, but  NACK is enough for most purposes)
- Removed RX-protocol sybtype and flag fields (for simplicity, ease of
  implementation)

The need for congestion control to be well specified and non-optional in
this profile was noted. Mark Handley stated that we have to assume that
loss is due to congestion, this means that just re-transmitting lost
packets is something we have to be very careful of, since it can lead to a
positive feedback loop, worsening congestion. The TCP equivalent throughput
should be considered to be the maximum acceptable rate for a scheme such as
this. It was also noted that retransmissions bias your loss fraction sample, 
since by definition, they are only sent when the network is congested and 
likely to drop packets.

The effects of retransmission on RTCP receiver reports were discussed (e.g.
should packets repaired by retransmission be included in the loss fraction?), 
as was the possibility to extend the RR to include the number of NACKs sent, 
requested packets, duplicates, etc. Another open issue is how to denote the 
loss bitmap. As the first sequence number plus bitmap or as the last sequence 
number plus bitmap?

It was noted that there are a number of security implications to this
profile: for example, the potential for denial of service due to bogus
NACKs, especially if multicast is used.  Also NACKs may need to include 
an unpredictable nonce/cookie, to make this difficult to spoof. Finally, 
the NACK format is deployable for multicast, but does it make sense?
Note that retransmission is being considered only for unicast at this
point pending further work in the Reliable Multicast Research Group
and RMT working group.

The next steps for this draft are as follows:
- Re-issue as an AVT work item (draft-ietf-avt-...) 
- Add more description relating to SDP, RTSP
- Add more description of sender and receiver's recommended behavior
- Implement and test

The final presentation in this area was an RTP payload for selective
retransmission (draft-miyazaki-avt-rtp-selret-00) presented by Carsten
Burmeister. The target applications for this payload format are streaming
applications over wireless links which have a high bit error rate, which
implies non-congestive packet loss, hence a retransmission scheme is useful
(just the important data, if possible). The draft defines a new payload
format, with header additions to mark important packets, together with a
retransmission request scheme.

A number of comments were made following this presentation:
- It was noted that there are IPR consideration with this proposal.
- Steve Casner noted that it is not clear that a payload format is the right 
  thing to do here. Either this scheme is specific to MPEG, in which case it 
  should be merged with the MPEG payload format, or it should be a new RTP 
  profile.
- Some meeting participants did not like the use of two payload type
  identifiers, when a single one would be sufficient. The introduction 
  of excess de-multiplexing points is to be avoided.
- Concern was raised that the necessary changes to RTCP timing rules have
  not been addressed.
- A comment was made that the idea of marking important packets within an
  application level header is `hackish'. It may be better to multiplex under 
  different connections (e.g. all the I frames in one stream, P frames in a 
  different one) using the UDP/IP layer as a multiplex (e.g. use different 
  UDP ports, or a different diffserv TOS).

This section of the meeting concluded with the suggestion that this
proposal could be combined with the previous.

The next section of the meeting discussed RTP compression and multiplexing.
The first presentation was by Tmima Koren on enhancements to CRTP. This
work makes CRTP more robust to packet loss, and allows it to work better on
high delay links. Discussion related to whether the extra complexity of
this form of compressed packet is justified by the efficiency gain. It was
noted that we need to introduce this complexity to correct for the
non-constant increment of the IP-ID. Carsten Bormann asked how much we care
about preserving the IP-ID, since it's redundant if DF is set. It was noted
that the IESG have previously expressed pushback on schemes which don't
protect the IP-ID. If we consider patterns of the IP-ID, can we reduce the
number of bits (e.g. we may be able to send the least significant bits of
the IP-ID in many common cases). We don't always need 16 bits for this. How
much do we care about backwards compatibility with RFC2508, since we have
to negotiate use of this extension anyway? Are these changes the correct
ones to make when moving CRTP to draft standard? These questions require
further discussion on the mailing list.

Carsten Bormann gave a pointer to the robust header compression working
group, which is doing related work.

Bruce Thompson presented tunnel compressed RTP (draft-ietf-avt-tcrtp-00.txt).  
The scheme proposed in the original draft submitted in Oslo (draft-wing-avt-
tcrtp-00.txt) has since been broken into distinct parts: IP Tunneling, PPP
Multiplexing, and CRTP with enhancements. The current draft reflects this
split, and describes how those parts fit together. It was noted that the
bandwidth efficiency of multiplexing in this manner is equivalent to CRTP,
once 3-4 calls are multiplexed.

Steve Casner noted that this is intended to be the standard multiplexing
solution for RTP streams in place of other "RTP multiplexing" schemes
discussed previously in AVT. Comments from the authors of the other schemes 
on the suitability of this solution would be greatly appreciated.

In the last presentation of the first day, Lou Berger discussed the
extension of CRTP to work with MPLS (draft-berger-mpls-hdr-comp-00.txt,
draft-berger-mpls-hdr-comp-over-ppp-00.txt). This work will be done in 
the MPLS working group, in conjunction with AVT. Open issues include:
- A bit naming collision with draft-koren-avt-crtp-enhance-01.txt (both
  define a bit named "N" in different locations)
- The current draft doesn't support the CRTP enhancements introduced by
  Koren
- Should MPLS/IP header compression over PPP reuse the same packet type 
  values as IP header compression or new values to allow for easier debugging?

The second day of the meeting comprised discussion of RTP payload formats
for a number of codecs. The first of these was the G.722.1 payload format
(draft-ietf-avt-rtp-g7221-00.txt) presented by Steve Casner for Tony
Crossman. This is a straight forward payload format, with one or more codec
frames being packed into an RTP packet with no additional payload header.
It was noted that G.722.1 is specified to use 16kHz RTP timestamp clock
(unlike G.722 which was mistakenly specified to use an 8kHz clock which is
retained for backward compatibility).  G.722.1 also supports several data
rates, which must be signaled out of band.

A number of drafts were submitted relating to the RTP payload format for
the AMR speech codec. The current status of this work was presented by
Johan Sjoberg and Ari Lakaniemi. It has been agreed that the authors of
these drafts will merge them into a single draft over the next few weeks.
In addition, the MIME type registration will be merged into the payload
format document, and an additional document will be referenced to specify
the storage format.

The RTP payload formats for DV audio/video were presented by Katsushi
Kobayashi. Changes to the DV video format are minor. The major discussion
point was if audio-only streams should be sent as DV format, or converted
to, for example, L16. It was decided to leave the current specification
unchanged in recommending that audio-only streams be converted to a native
format. We also discussed how to specify audio channels, since DV allows
for more channels than the AIFF-C convention used in the A/V profile, hence
an SDP attribute may be needed to define the channel ordering. This is only
needed when sending the data unbundled from DV, as native audio. This can
clearly be defined for the new audio formats specified here, but does it
make sense to allow this channel specification to be applied to L16 format?
Should it be allowed for channel specifications which fit into the AIFF-C
convention?  Carsten Bormann stated the question as: can we just add, after
the fact, a=fmtp parameters to existing payload formats? I.e. can this be
written to apply to L16 also? Do we need to revise the L16 MIME
registration? After some discussion Steve Casner noted that the group
consensus was to go ahead and define this SDP method.

The RTP payload formats for HDTV and AC3 audio were discussed by Allison
Mankin. She noted that a lot of implementation work has been conducted
since the last meeting (by  the University of Washington, 3com, and
Tektronics) and this has lead to a number of changes in the drafts, and
some issues remain. Bill Nowicki has asked if this can be written as a
payload format for any kind of uncompressed video, to make it more generic?
It has also been noted that a breakdown on which SMPTE standards should be
included here needs to be added: there are compressed (but still high
bandwidth) payloads which may need a format. It is not entirely clear which
way to cut the document, and advice is solicited. It is also unclear if
1920 scanlines is enough. It is now, but what about in future? Can we use
SDP signaling to save bits in the header but still allow a wider scanline
range? What about the Vertical Blanking Interval? This has been left out of
the current draft, to be thought about (since it increases the data rate
significantly). Several people have wanted to include this, so it will most
likely go back in. Is a 90kHz timestamp sufficient? Finally, a plea was
made for anyone who has implemented RTP in hardware to contact Allison;
insights are sought...

Ross Finlayson presented a revision of the more-loss-tolerant payload
format for MP3 audio (draft-ietf-avt-rtp-mp3-01.txt). Since the previous
version, the draft has been updated to include optional support for
interleaving (as discussed in Washington DC), and the process by which this
is achieved was described.  Feedback is solicited, and it was proposed to
advance this document to proposed standard after next meeting. A question
was asked regarding performance analysis, relative to RFC 2250.  The
payload format just moves bytes around compared to RFC 2250, and is not
expected to be significantly processor intensive. Subjective tests show it
sounds better, but these were not done in a very scientific manner.

MP2 transport stream extensions were presented by Steve Casner for Humphrey
Liu. This draft extends RFC 2250 to allow an alternate RTP timestamp clock
rate of 27MHz so that the every MPEG packet in a 40Mb/s multi-program MPEG
transport stream can be positioned accurately in time, and defines a
"piecewise CBR" method to reconstruct timing at the receiver. At the last
AVT meeting, some participants questioned whether this would work.  Since
the last meeting, work has been underway on experimental validation of the
draft. This work was outlined, and it was noted that it seems to work so
far, but more experiments are needed.

The discussion of MPEG-4 was introduced by Colin Perkins, with a review of
the consensus from the last meeting. It was noted that:
- We should allow MPEG-4 elementary stream codecs to be packetized in a manner 
  similar to other codecs, with standards track payload formats. The group has 
  adopted draft-ietf-avt-rtp-mpeg4-es-00.txt as a work item, for eventual 
  submission to the standards track.
- Multiplexed MPEG-4 media is to be treated in a similar manner to earlier
  bundled MPEG transport. Hence, we will consider a FlexMux payload format
  if one is submitted.
- We do not believe we fully understand the issues involved in the
  transport of the complete MPEG-4 system over RTP. Hence we will submit
  such payload formats for publication as experimental RFCs, whilst we gain
  implementation experience. At present we have two such payload formats:
  draft-ietf-avt-rtp-mpeg4-02.txt and draft-ietf-avt-mpeg4streams-00.txt
The primary focus of the discussion at this meeting was the payload format
for elementary streams, and in particular the transport of back-channel
information. We also had an update on one of the formats for the complete
system, the other payload format (draft-ietf-avt-rtp-mpeg4-02.txt) has not
changed since the last meeting.

The payload format for elementary streams (draft-ietf-avt-rtp-mpeg4-es-00.txt) 
was presented by Yoshihiro Kikuchi. Changes since the last meeting include:
- The marker bit in the visual format has changed from marking random
  access points to marking the last packet in a VOP (for consistency with
  other video formats).
- The timestamp resolution has a default of 90KHz, for consistency with
  other MPEG formats.
- The specification has been updated to match changes in MPEG-4 Version 2
  in the move from FPDAM to FDAM. 
There were also several minor editorial changes. A number of
interoperability tests have also been conducted, successfully. 

The payload format for elementary streams also includes an RTCP format for
MPEG-4 backward channel messages, such as NEWPRED error resilience. This
was presented by Shigeru Fukunaga. A number of issues were noted:
- Timing of Sending RTCP: RTCP packets should be sent as soon as possible,
  the issues are much as in the re-transmission profiles. Is a new profile
  required here?
- Multicast or Unicast: NEWPRED is workable with small scale multicast, but
  it is probably desirable to restrict this to unicast.
- Congestion Control: There is no description in the current draft
  (congestion control may not be a major issue, since the data rate of a
  media stream is not increased when NEWPRED is in use; although there is
  the additional backtraffic).
- Should be backchannel information be transported in RTCP or in a
  separate RTP stream? The consensus of the group was that RTCP is appropriate.
- What should be the format of compound RTCP packets which include these
  backchannel messages?

Steve Casner noted that he thinks this doesn't need a new profile, but we
may need to relax some of the rules in the RTP spec to allow this. Carsten
Bormann noted that this is not the first codec which needs a backchannel,
and won't be the last one (for example, H.263+ needs a similar backchannel). 
Having a common means for sending these backchannel messages would be nice.
Maybe a more generic RTCP extension (profile addition)?  Jonathan Rosenberg
noted that a common backchannel may just be a namespace.  Or do we have
more information in common? Carsten Bormann noted that the value here is
more in getting the other issues out of the way - bandwidth and timing
issues, etc.

Steve Casner concluded with the chairs' view that we should proceed 
with the definition of this backchannel scheme as is, and consider a 
more general solution in future.

Paul Christ presented draft-ietf-avt-mpeg4streams-00.txt. Changes since 
the previous draft include:
- Adoption as an AVT work item for eventual submission as an experimental
  RFC, hence the name change (from draft-guillemot-avt-genrtp-03.txt).
- Flexmux section added, see draft-rgcc-flexmuxmpeg4- 00.txt
- Payload Type: Different payload types should be assigned for ES, SL-PDU
  and FlexMux streams. A payload type in the dynamic range should be chosen. 
- TSOFFSET removed, E bits included

Steve Casner asked if this is ready for working group last call for
experimental? Paul Christ noted that there are RTCP retransmission issues
to be resolved (NEWPRED, etc).  Further discussion is needed, but if
retransmission is not relevant it is ready for last call.

The final presentation of the day was by Michael Thomas, summarizing the
PacketCable security extensions to RTP. There are two main goals of this
work: providing privacy and integrity for media, and selecting algorithms
friendly to large PSTN gateways. RTP header and payload are to be covered
by an MMH MAC, placed as a trailer in the packet; the payload is to be
protected by RC-4 encryption. It is hoped that a draft will be submitted
describing this work in time for the next meeting. It should also be noted
that there are several proposals for insertion of the MAC: hide it in RTP
padding, use a header extension, or use a profile extension to specify a
fixed-length trailer. Further discussion is clearly needed.

Due to lack of time, the meeting closed at this point. The final agenda
item - charter bashing - was omitted. It should be noted that the last
milestone on our charter was in November 1999, and we actually completed
most milestones! It's now time to re-charter or close-down the group, and
since we still have ongoing work, we propose to re-charter.  The chairs'
proposal, which will be elaborated in more detail on the mailing list, is 
to include the following items in the revised charter:
- Move RTP to draft standard (needs interoperability statements, and a
  discussion of congestion control)
- RTP Multiplexing (move the TCRTP framework to BCP)
- Transport of MPEG-4
	- ES format to proposed
	- Formats for complete system to experimental
	- FlexMux?
	- Applicability statement (informational)
- New RTP profile including unicast retransmission and congestion control
- Authentication of RTP streams
	- New profile? Padding? Header extension?
- Ongoing development of payload formats 
This is a preliminary suggestion only; comments from the working group
are solicited.
-------------------------------------------------------------------------------



From rem-conf Wed May 03 08:54:18 2000 
From rem-conf-request@es.net Wed May 03 08:54:16 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n1KW-0007Df-00; Wed, 3 May 2000 08:44:52 -0700
Received: from turin.trillium.com [206.216.108.218] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n1KV-0007Cm-01; Wed, 3 May 2000 08:44:51 -0700
Received: from aiglos.trillium.com (unverified) by turin.trillium.com
 (Content Technologies SMTPRS 4.1.2) with ESMTP id <Bced86cda4bf28fe8ed@turin.trillium.com> for <rem-conf@es.net>;
 Wed, 3 May 2000 08:54:24 -0700
Received: from aega.trillium.com (aega.trillium.com [192.168.1.19])
	by aiglos.trillium.com (8.9.3/8.9.3) with ESMTP id IAA20678
	for <rem-conf@es.net>; Wed, 3 May 2000 08:43:46 -0700 (PDT)
Received: by aega.trillium.com with Internet Mail Service (5.5.2650.21)
	id <JS4NMWPA>; Wed, 3 May 2000 08:42:47 -0700
Message-ID: <8BBD33A986C5D311804000902719FF5D0870F2@aega.trillium.com>
From: Tim Chen <scc@trillium.com>
To: "'rem-conf@es.net'" <rem-conf@es.net>
Subject: FW: Current RTP-MIB definition precludes multi-unicast RTP sessio
	n?
Date: Wed, 3 May 2000 08:42:46 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


> Hello,
> 
> I see a problem with current "RTP session" definition in RTP MIB 
> <draft-ietf-avt-rtp-mib-09.txt>. 
> This MIB definition precludes multi-unicast RTP session which is clearly 
> permissible under section 3 of RFC 1889:
> 
> RTP session: The association among a set of participants communicating
> with RTP. For each participant, the session is defined by a particular
> pair of destination transport addresses (one network address plus a port
> pair for RTP and RTCP). The destination transport address pair may be
> common for all participants, as in the case of IP multicast, or may be
> different for each, as in the case of individual unicast network addresses
> plus a common port pair. 
> 
> Hence each participant in an RTP session could have
> a different RTP receive address.  The only requirement
> from the specs is that the RTP and RTCP port pair used by all participants
> has to be the same.  For example, I can have the following 
> RTP session with three participants, each receiving RTP packets 
> on a different IP address:
> 
> participant A : receive RTP on 103.403.25.45 port 6000
> participant B : receive RTP on 103.403.33.34 port 6000
> participant C : receive RTP on 103.403.25.98 port 6000
> 
> So for participant A, he will send to two remote addresses:
> 103.403.33.34:6000 (that B listens to) and 103.403.25.98:6000 
> (that C listens to).  
> 
> However, the current RTP session MIB draft (page 10) has the 
> following structure:
> 
> RtpSessionEntry ::= SEQUENCE {  
>         rtpSessionIndex         Integer32,
>         rtpSessionDomain        TDomain,       
>         rtpSessionRemAddr       TAddress,
>         rtpSessionLocAddr       TAddress,
>         rtpSessionIfIndex       InterfaceIndex,
>         rtpSessionSenderJoins   Counter32,
>         rtpSessionReceiverJoins Counter32,
>         rtpSessionByes          Counter32,
>         rtpSessionStartTime     TimeStamp,
>        	rtpSessionMonitor       TruthValue,
>        	rtpSessionRowStatus     RowStatus       
>         }
> 
> This definition allows only a single remote address.  This
> is contradictory to RFC 1889 which clearly permits
> multiple remote addresses in a single RTP session.
> 
> Will the authors of this MIB give some clarification?  Thanks.
> 
> 
> Regards,
> Tim Chen
> 
> 



From rem-conf Wed May 03 09:11:51 2000 
From rem-conf-request@es.net Wed May 03 09:11:51 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n1ff-0000S1-00; Wed, 3 May 2000 09:06:43 -0700
Received: from thalia.fm.intel.com [132.233.247.11] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n1fd-0000Rp-00; Wed, 3 May 2000 09:06:41 -0700
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.22 2000/04/06 17:58:51 dmccart Exp $) with SMTP id QAA21203
	for <rem-conf@es.net>; Wed, 3 May 2000 16:07:28 GMT
Received: from fmsmsx17.intel.com ([132.233.48.17]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Wed, 03 May 2000 16:06:40 0000 (GMT)
Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2448.0)
	id <KFHBMBNZ>; Wed, 3 May 2000 09:06:38 -0700
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB20344B7B2@orsmsx41.jf.intel.com>
From: "Strahm, Bill" <bill.strahm@intel.com>
To: "'rem-conf@es.net'" <rem-conf@es.net>
Subject: FW: Current RTP-MIB definition precludes multi-unicast RTP sessio
	n?
Date: Wed, 3 May 2000 09:06:36 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


My comments inline

______________________________________________
Bill Strahm        Programming today is a race between
bill.strahm@      software engineers striving to build
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


> -----Original Message-----
> From: Tim Chen [mailto:scc@trillium.com]
> Sent: Tuesday, May 02, 2000 5:19 PM
> To: ITU-SG16@mailbag.cps.intel.com
> Cc: 'mbaugher@passedge.com'; 'bill.strahm@intel.com';
> 'irina@ennovatenetworks.com'; Michael Bird
> Subject: Current RTP-MIB definition precludes multi-unicast 
> RTP session?
> 
> 
> Hello,
> 
> I see a problem with current "RTP session" definition in RTP MIB 
> <draft-ietf-avt-rtp-mib-09.txt>. 
> This MIB definition precludes multi-unicast RTP session which 
> is clearly 
> permissible under section 3 of RFC 1889:
> 
> RTP session: The association among a set of participants 
> communicating with
> RTP. For each participant, the session is defined by a 
> particular pair of
> destination transport addresses (one network address plus a 
> port pair for
> RTP and RTCP). The destination transport address pair may be 
> common for all
> participants, as in the case of IP multicast, or may be 
> different for each,
> as in the case of individual unicast network addresses plus a 
> common port
> pair. 
> 
> Hence each participant in an RTP session could have
> a different RTP receive address.  The only requirement
> from the specs is that the RTP and RTCP port pair used by all 
> participants
> has to be the same.  For example, I can have the following 
> RTP session with three participants, each receiving RTP packets 
> on a different IP address:
> 
> participant A : receive RTP on 103.403.25.45 port 6000
> participant B : receive RTP on 103.403.33.34 port 6000
> participant C : receive RTP on 103.403.25.98 port 6000
> 
> So for participant A, he will send to two remote addresses:
> 103.403.33.34:6000 (that B listens to) and 103.403.25.98:6000 
> (that C listens to).  
> 
> However, the current RTP session MIB draft (page 10) has the 
> following structure:
> 
> RtpSessionEntry ::= SEQUENCE {  
>         rtpSessionIndex         Integer32,
>         rtpSessionDomain        TDomain,       
>         rtpSessionRemAddr       TAddress,
>         rtpSessionLocAddr       TAddress,
>         rtpSessionIfIndex       InterfaceIndex,
>         rtpSessionSenderJoins   Counter32,
>         rtpSessionReceiverJoins Counter32,
>         rtpSessionByes          Counter32,
>         rtpSessionStartTime     TimeStamp,
>        	rtpSessionMonitor       TruthValue,
>        	rtpSessionRowStatus     RowStatus       
>         }
> 
> This definition allows only a single remote address.  This
> is contradictory to RFC 1889 which clearly permits
> multiple remote addresses in a single RTP session.
> 
> Will the authors of this MIB give some clarification?  Thanks.
> 
I see each one of these as seperate channels, with different feedback
streams.  Therefor participant A would have a RtpSessionEntry for A->B and
A->C, participant B would have B->A and B->C etc.  Yes this doesn't scale
very well as you add many participants, but then neither does sending
multiple copies of the same stream, so I think it is a wash.

To clarify.  The RtpReceiverEntry needs to have the feedback for just ONE
receiver anyway, so why not model it as multiple unicast flows (since that
is indeed what we have here)

I do not see a problem

Bill Strahm




From rem-conf Wed May 03 09:29:12 2000 
From rem-conf-request@es.net Wed May 03 09:29:11 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n1wk-0001KI-00; Wed, 3 May 2000 09:24:22 -0700
Received: from marjan.fesb.hr [161.53.166.3] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n1wc-0001Ju-00; Wed, 3 May 2000 09:24:17 -0700
Received: from jurica (jurica.fesb.hr [161.53.166.43])
	by marjan.fesb.hr (8.9.3/8.9.3) with SMTP id QAA28452;
	Wed, 3 May 2000 16:06:36 +0200 (MET DST)
Message-ID: <060601bfb509$c1e66c20$2ba635a1@fesb.hr>
From: "SoftCOM Secretary" <softcom@fesb.hr>
To: "SoftCOM Mailing List" <softcom@fesb.hr>
Subject: Second Call for Papers
Date: Wed, 3 May 2000 16:07:37 +0200
Organization: FESB, University of Split
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Dear All

A Gentle Reminder

* Kindly ignore this email if you have received this before. Please give
* this remainder to your coleagues that might be interested.

Thank you for your kind attention and cooperation.


***********************************************************

The 8th IEEE International Conference on Software, Telecommunications and

Computer networks (SoftCOM 2000) will be held from October 11-14, 2000

aboard the luxury ship Marko Polo travelling on the route Split (Croatia) -

Rijeka (Croatia) - Trieste (Italy) - Venice (Italy) - Dubrovnik (Croatia).

The aim of the conference is to provide an international forum for experts

to promote, share and discuss various issues and developments in the broad

field of telecommunication and computer networks. We thus seek and solicit

your contributions in the form of original/unpublished papers, tutorials,

and topics for special sessions/panel discussions. More information on the

scope of the conference and the guidelines for the submission of

contributions can be obtained at this web site: http://www.fesb.hr/SoftCOM



We look forward to your participation. Thank you.

SoftCOM 2000 Organizing Committee















From rem-conf Wed May 03 09:53:29 2000 
From rem-conf-request@es.net Wed May 03 09:53:28 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n2J3-0002Lo-00; Wed, 3 May 2000 09:47:25 -0700
Received: from turin.trillium.com [206.216.108.218] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n2J2-0002LU-00; Wed, 3 May 2000 09:47:24 -0700
Received: from aiglos.trillium.com (unverified) by turin.trillium.com
 (Content Technologies SMTPRS 4.1.2) with ESMTP id <Bced86cda4bf2c92de0@turin.trillium.com>;
 Wed, 3 May 2000 09:56:57 -0700
Received: from aega.trillium.com (aega.trillium.com [192.168.1.19])
	by aiglos.trillium.com (8.9.3/8.9.3) with ESMTP id JAA21984;
	Wed, 3 May 2000 09:46:19 -0700 (PDT)
Received: by aega.trillium.com with Internet Mail Service (5.5.2650.21)
	id <JS4NMWQQ>; Wed, 3 May 2000 09:45:20 -0700
Message-ID: <8BBD33A986C5D311804000902719FF5D0870F5@aega.trillium.com>
From: Tim Chen <scc@trillium.com>
To: "'Strahm, Bill'" <bill.strahm@intel.com>,
        "'rem-conf@es.net'"
	 <rem-conf@es.net>,
        ITU-SG16@mailbag.cps.intel.com
Cc: Michael Bird <m_bird@trillium.com>
Subject: RE: Current RTP-MIB definition precludes multi-unicast RTP sessio
	 n?
Date: Wed, 3 May 2000 09:45:19 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Bill,

Thank you for your reply.  However, I am not 
convinced that multi-unicast RTP session MIB is
properly handled in the current RTP MIB draft.  
Please find my comments below.

> I see each one of these as seperate channels, with different feedback
> streams.  Therefor participant A would have a RtpSessionEntry 
> for A->B and
> A->C, participant B would have B->A and B->C etc.  Yes this 
> doesn't scale
> very well as you add many participants, but then neither does sending
> multiple copies of the same stream, so I think it is a wash.
> 
> To clarify.  The RtpReceiverEntry needs to have the feedback 
> for just ONE
> receiver anyway, so why not model it as multiple unicast 
> flows (since that
> is indeed what we have here)
> 
> I do not see a problem

The issue I am raising is that we are dividing up what is truly 
a single RTP session as defined in RFC 1889 with multiple RTP sessions 
in MIB.  The RTP MIB draft has changed the definition of a RTP session.

Let's say if I want to implement a monitor for the above
example where A is sending to both B and C in a RTP session.
I send a MIB request for a RTP session and according to the 
current MIB specs, I will be getting back only a single stream 
in the RTP session (say A->B).  I cannot be certain if
another stream (A->C) exists for this RTP session 
unless I dump the whole MIB and try to correlate all the 
"MIB RTP session" with the local address of A. 

In addition, the reverse sender table mapping is non unique.
Let's continue with the above example and look at the
sender A.  Sender A's send address is common to the stream
A->B and A->C.  Then using sender A's rtpSessionDomain and rtpSenderAddr,
I can map to the session index corresponding either to the (A->B) stream
or the session index corresponding to the (A->C) stream.  This
is contradictory to the statement in the MIB rtpSenderInverseEntry
that "Each entry corresponds to exactly one entry in the
rtpSenderTable - the entry containing the index pair, 
rtpSessionIndex, rtpSenderSSRC".

The MIB draft should specify clearly how the multi-unicast 
RTP session scenario should be handled and clarify some 
of these inconsistencies.

Regards,
Tim Chen
  



From rem-conf Wed May 03 10:20:22 2000 
From rem-conf-request@es.net Wed May 03 10:20:20 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n2m3-0003Oy-00; Wed, 3 May 2000 10:17:23 -0700
Received: from thalia.fm.intel.com [132.233.247.11] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n2m1-0003Oo-00; Wed, 3 May 2000 10:17:21 -0700
Received: from SMTP (fmsmsxvs05-1.fm.intel.com [132.233.42.205])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.22 2000/04/06 17:58:51 dmccart Exp $) with SMTP id RAA01197;
	Wed, 3 May 2000 17:18:08 GMT
Received: from fmsmsx28.FM.INTEL.COM ([132.233.48.28]) by 132.233.48.205
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Wed, 03 May 2000 17:17:20 0000 (GMT)
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2448.0)
	id <KFHG9G9N>; Wed, 3 May 2000 10:17:18 -0700
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB20344B7B5@orsmsx41.jf.intel.com>
From: "Strahm, Bill" <bill.strahm@intel.com>
To: "'Tim Chen'" <scc@trillium.com>, "Strahm, Bill" <bill.strahm@intel.com>,
        "'rem-conf@es.net'" <rem-conf@es.net>, ITU-SG16@mailbag.cps.intel.com
Cc: Michael Bird <m_bird@trillium.com>,
        "'rem-conf@es.net'"
	 <rem-conf@es.net>,
        "'mbaugher@passedge.com'" <mbaugher@passedge.com>
Subject: RE: Current RTP-MIB definition precludes multi-unicast RTP sessio
	 n?
Date: Wed, 3 May 2000 10:17:16 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

I think you are going a little overboard on your definition of "One Session"

First off I do not see how you could have a third party monitor setup to
catch all of the unicast streams involved.  Third party monitors were
designed to handle multicast cases where you can setup the monitor to
receive the multicast address/port combination that is needed to get the
management data.

I do not believe that your multi-unicast session is held up in the RTP Spec
>From RFC 1889 Sec 3 Definitions

   RTP session: The association among a set of participants
        communicating with RTP. For each participant, the session is
        defined by a particular pair of destination transport addresses
        (one network address plus a port pair for RTP and RTCP). The
        destination transport address pair may be common for all
        participants, as in the case of IP multicast, or may be
        different for each, as in the case of individual unicast network
        addresses plus a common port pair.  In a multimedia session,
        each medium is carried in a separate RTP session with its own
        RTCP packets. The multiple RTP sessions are distinguished by
        different port number pairs and/or different multicast
        addresses.

>From this reading each of the A->B A->C is a seperate RTP Session ( there
are different destination transport address pairs).

If you want to define a seperate definition of an RTP session as Where one
endpoint unicasts the same information to multiple destination addresses on
the same port, I do not see this definition supported by the RTP spec, and I
do not see how this can work because B and C will not see each others RTCP
packets to create a single session to be managed.

Bill
> -----Original Message-----
> From: Tim Chen [mailto:scc@trillium.com]
> Sent: Wednesday, May 03, 2000 9:45 AM
> To: 'Strahm, Bill'; 'rem-conf@es.net'; ITU-SG16@mailbag.cps.intel.com
> Cc: Michael Bird
> Subject: RE: Current RTP-MIB definition precludes multi-unicast RTP
> sessio n?
> 
> 
> Bill,
> 
> Thank you for your reply.  However, I am not 
> convinced that multi-unicast RTP session MIB is
> properly handled in the current RTP MIB draft.  
> Please find my comments below.
> 
> > I see each one of these as seperate channels, with 
> different feedback
> > streams.  Therefor participant A would have a RtpSessionEntry 
> > for A->B and
> > A->C, participant B would have B->A and B->C etc.  Yes this 
> > doesn't scale
> > very well as you add many participants, but then neither 
> does sending
> > multiple copies of the same stream, so I think it is a wash.
> > 
> > To clarify.  The RtpReceiverEntry needs to have the feedback 
> > for just ONE
> > receiver anyway, so why not model it as multiple unicast 
> > flows (since that
> > is indeed what we have here)
> > 
> > I do not see a problem
> 
> The issue I am raising is that we are dividing up what is truly 
> a single RTP session as defined in RFC 1889 with multiple RTP 
> sessions 
> in MIB.  The RTP MIB draft has changed the definition of a 
> RTP session.
> 
> Let's say if I want to implement a monitor for the above
> example where A is sending to both B and C in a RTP session.
> I send a MIB request for a RTP session and according to the 
> current MIB specs, I will be getting back only a single stream 
> in the RTP session (say A->B).  I cannot be certain if
> another stream (A->C) exists for this RTP session 
> unless I dump the whole MIB and try to correlate all the 
> "MIB RTP session" with the local address of A. 

Third party monitors were not designed for Unicast applications.  How do you
expect to get the Unicast RTCP information to this third party monitor
somewhere else in the network ???

> In addition, the reverse sender table mapping is non unique.
> Let's continue with the above example and look at the
> sender A.  Sender A's send address is common to the stream
> A->B and A->C.  Then using sender A's rtpSessionDomain and 
> rtpSenderAddr,
> I can map to the session index corresponding either to the 
> (A->B) stream
> or the session index corresponding to the (A->C) stream.  This
> is contradictory to the statement in the MIB rtpSenderInverseEntry
> that "Each entry corresponds to exactly one entry in the
> rtpSenderTable - the entry containing the index pair, 
> rtpSessionIndex, rtpSenderSSRC".
> 
Again I say that the A->B stream is seperate than the A->C stream.  Looking
at endpoint A we have a table that has two entries in the RtpSessionEntry
one for each stream, and we have uniqueness.  From B we have one entry in
the RtpSessionEntry table (for the A->B stream) and no knowledge of the A->C
stream (we can't see it so we can't manage it from here).  The same thing
applies for C.
> The MIB draft should specify clearly how the multi-unicast 
> RTP session scenario should be handled and clarify some 
> of these inconsistencies.
> 
> Regards,
> Tim Chen
>   
> 




From rem-conf Wed May 03 12:11:43 2000 
From rem-conf-request@es.net Wed May 03 12:11:43 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n4RT-0005LE-00; Wed, 3 May 2000 12:04:15 -0700
Received: from brisco.passedge.com [4.18.242.15] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n4RS-0005Ir-00; Wed, 3 May 2000 12:04:14 -0700
Received: by BRISCO with Internet Mail Service (5.5.2650.21)
	id <25BKH7BJ>; Wed, 3 May 2000 12:04:06 -0700
Message-ID: <07E816C410ECD311BBEE00C04FA14BCF0C5F05@BRISCO>
From: "Baugher, Mark" <mbaugher@passedge.com>
To: 'Tim Chen' <scc@trillium.com>, "'rem-conf@es.net'" <rem-conf@es.net>
Subject: RE: Current RTP-MIB definition precludes multi-unicast RTP sessio
	 n?
Date: Wed, 3 May 2000 12:03:59 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

hi Tim
  Here's the first part of the RFC 1889 definition that
you cite:

> > RTP session: The association among a set of participants 
> communicating
> > with RTP. For each participant, the session is defined by a 
> particular
> > pair of destination transport addresses (one network 
> 

It reads that "For each participant, the session is defined by
a particular pair of destination transport addresses."  I think
you are interpreting this to mean a "set of pairs," which
is not what RFC 1889 says.  The MIB maintains management 
information for a participant, if it is a host, or
for all participants in the case of a multicast monitor.
A mixer or translator may have a different view of a
session, but the RTP MIB draft document states that mixers 
and translators are for further study.

Mark

> -----Original Message-----
> From: Tim Chen [mailto:scc@trillium.com]
> Sent: Wednesday, May 03, 2000 8:43 AM
> To: 'rem-conf@es.net'
> Subject: FW: Current RTP-MIB definition precludes multi-unicast RTP
> sessio n?
> 
> 
> 
> > Hello,
> > 
> > I see a problem with current "RTP session" definition in RTP MIB 
> > <draft-ietf-avt-rtp-mib-09.txt>. 
> > This MIB definition precludes multi-unicast RTP session 
> which is clearly 
> > permissible under section 3 of RFC 1889:
> > 
> > RTP session: The association among a set of participants 
> communicating
> > with RTP. For each participant, the session is defined by a 
> particular
> > pair of destination transport addresses (one network 
> address plus a port
> > pair for RTP and RTCP). The destination transport address 
> pair may be
> > common for all participants, as in the case of IP 
> multicast, or may be
> > different for each, as in the case of individual unicast 
> network addresses
> > plus a common port pair. 
> > 
> > Hence each participant in an RTP session could have
> > a different RTP receive address.  The only requirement
> > from the specs is that the RTP and RTCP port pair used by 
> all participants
> > has to be the same.  For example, I can have the following 
> > RTP session with three participants, each receiving RTP packets 
> > on a different IP address:
> > 
> > participant A : receive RTP on 103.403.25.45 port 6000
> > participant B : receive RTP on 103.403.33.34 port 6000
> > participant C : receive RTP on 103.403.25.98 port 6000
> > 
> > So for participant A, he will send to two remote addresses:
> > 103.403.33.34:6000 (that B listens to) and 103.403.25.98:6000 
> > (that C listens to).  
> > 
> > However, the current RTP session MIB draft (page 10) has the 
> > following structure:
> > 
> > RtpSessionEntry ::= SEQUENCE {  
> >         rtpSessionIndex         Integer32,
> >         rtpSessionDomain        TDomain,       
> >         rtpSessionRemAddr       TAddress,
> >         rtpSessionLocAddr       TAddress,
> >         rtpSessionIfIndex       InterfaceIndex,
> >         rtpSessionSenderJoins   Counter32,
> >         rtpSessionReceiverJoins Counter32,
> >         rtpSessionByes          Counter32,
> >         rtpSessionStartTime     TimeStamp,
> >        	rtpSessionMonitor       TruthValue,
> >        	rtpSessionRowStatus     RowStatus       
> >         }
> > 
> > This definition allows only a single remote address.  This
> > is contradictory to RFC 1889 which clearly permits
> > multiple remote addresses in a single RTP session.
> > 
> > Will the authors of this MIB give some clarification?  Thanks.
> > 
> > 
> > Regards,
> > Tim Chen
> > 
> > 
> 



From rem-conf Wed May 03 13:02:50 2000 
From rem-conf-request@es.net Wed May 03 13:02:50 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n5Jg-000746-00; Wed, 3 May 2000 13:00:16 -0700
Received: from turin.trillium.com [206.216.108.218] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n5Jf-00073Q-00; Wed, 3 May 2000 13:00:15 -0700
Received: from aiglos.trillium.com (unverified) by turin.trillium.com
 (Content Technologies SMTPRS 4.1.2) with ESMTP id <Bced86cda4bf379c759@turin.trillium.com>;
 Wed, 3 May 2000 13:09:51 -0700
Received: from aega.trillium.com (aega.trillium.com [192.168.1.19])
	by aiglos.trillium.com (8.9.3/8.9.3) with ESMTP id MAA26441;
	Wed, 3 May 2000 12:59:12 -0700 (PDT)
Received: by aega.trillium.com with Internet Mail Service (5.5.2650.21)
	id <JS4NMWWM>; Wed, 3 May 2000 12:58:11 -0700
Message-ID: <8BBD33A986C5D311804000902719FF5D0870F9@aega.trillium.com>
From: Tim Chen <scc@trillium.com>
To: "'Baugher, Mark'" <mbaugher@passedge.com>, Tim Chen <scc@trillium.com>,
        "'rem-conf@es.net'" <rem-conf@es.net>
Cc: Michael Bird <m_bird@trillium.com>
Subject: RE: Current RTP-MIB definition precludes multi-unicast RTP sessio
	 n?
Date: Wed, 3 May 2000 12:58:11 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Mark,

Thank you for your reply.  Please find my comments inline:

> 
> hi Tim
>   Here's the first part of the RFC 1889 definition that
> you cite:
> 
> > > RTP session: The association among a set of participants 
> > communicating
> > > with RTP. For each participant, the session is defined by a 
> > particular
> > > pair of destination transport addresses (one network 
> > 
> 
> It reads that "For each participant, the session is defined by
> a particular pair of destination transport addresses."  

Here the pair of addresses refer to the receiving RTP and
RTCP address for that participant,  NOT a local RTP address
and a remote RTP address as in the current MIB draft.  
That is clear if we look at the entire sentence in the specs:

"For each participant, the session is defined by
a particular pair of destination transport addresses (one
network address plus a port pair for RTP and RTCP)."

So it is quite clear from the specs that each participant
in a session should receive RTP on one address/port and
RTCP on the same network address but another port.  However, the
specs explicitly mention that the receive addresses for
each participant need not be the same:

"The destination transport address pair may be be common
for all participants, as in the case of IP multicast, or
MAY BE DIFFERENT FOR EACH, as in the case of individual
unicast network addresses plus a common port pair."

So the specs allow for a scenario where I have user A, B and
C each using a different transport address pair to receive
RTP and RTCP packets to participate in a single RTP session.  
This is quite a valid scenario for a 3-way conference
call.  Under the current MIB definition, I cannot treat
this as a single RTP session.  

> I think
> you are interpreting this to mean a "set of pairs," which
> is not what RFC 1889 says.  

I hope the above explanation clarifies my interpretation
of the RFC 1889's definition of a RTP session.

> The MIB maintains management 
> information for a participant, if it is a host, or
> for all participants in the case of a multicast monitor.
> A mixer or translator may have a different view of a
> session, but the RTP MIB draft document states that mixers 
> and translators are for further study.
> 
> Mark


Regards,
Tim Chen



From rem-conf Wed May 03 14:28:51 2000 
From rem-conf-request@es.net Wed May 03 14:28:51 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12n6cr-0000NY-00; Wed, 3 May 2000 14:24:09 -0700
Received: from ip62.cincinnati14.oh.pub-ip.psi.net ([38.31.50.62] helo=opera)
	by mail2.es.net with smtp (Exim 1.92 #1)
	id 12n6cn-0000N8-00; Wed, 3 May 2000 14:24:05 -0700
From: opera9@flash.net
To: 
Subject: Best New Trade Show Display by Opera Portables, Inc. adv
Date: Wed, 03 May 2000 17:19:46 -0400
X-Sender: opera9@flash.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E12n6cn-0000N8-00@mail2.es.net>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Opera Portables, Inc. is offering "by invitation" visits to our web site.  Packed full of exciting projects and news, Opera is leading the industry with displays that as much eye-popping as they are eye catching.

Winner of numerous industry awards, including Ernst & Young's Crescendo Award, Exhibitor Magazine's Best New Product, Forty Under 40 and Emerging 30, Opera Portables is a progressive young company with imagination and vision.

If you use displays, you really owe it to yourself to check out our stuff!  go to http://www.operadisplays.net.@3637331613/

Opera Portables, Inc.

All removes honored at http://www.operadisplays.net.@3637331613/removes.htm



From rem-conf Wed May 03 14:30:08 2000 
From rem-conf-request@es.net Wed May 03 14:30:07 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n6bF-0000tW-00; Wed, 3 May 2000 14:22:29 -0700
Received: from dnai.com [207.181.194.98] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12n6bE-0000tM-00; Wed, 3 May 2000 14:22:28 -0700
Received: from hariv (cougar.chiplogic.com [216.15.52.34])
	by dnai.com (8.9.3/8.9.3) with SMTP id OAA40039
	for <rem-conf@es.net>; Wed, 3 May 2000 14:22:27 -0700 (PDT)
Message-ID: <018e01bfb545$1a057780$03000004@hariv.domain>
Reply-To: "Hari Krishna Vuppaladhadiam" <hariv@chiplogic.com>
From: "Hari Krishna Vuppaladhadiam" <hariv@chiplogic.com>
To: <rem-conf@es.net>
Subject: Voice Activity Detection (VAD)
Date: Wed, 3 May 2000 14:18:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi,
  I need to know what are the standards defined for VAD for sample based
speech codecs like G711, G726 etc. in the VoIP chain. Is there any reference
available for this implementation?

Regards
Hari





From rem-conf Wed May 03 16:49:57 2000 
From rem-conf-request@es.net Wed May 03 16:49:56 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12n8ps-0004Br-00; Wed, 3 May 2000 16:45:44 -0700
Received: from bells.cs.ucl.ac.uk [128.16.5.31] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12n8pr-0004Bh-00; Wed, 3 May 2000 16:45:43 -0700
Received: from host212-140-35-199.btinternet.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.15778-0@bells.cs.ucl.ac.uk>;
          Thu, 4 May 2000 00:45:24 +0100
Message-ID: <002c01bfb552$5a9dcce0$c7238cd4@oemcomputer>
Reply-To: Farez <f.abdulrahman@cs.ucl.ac.uk>
From: Farez <f.abdulrahman@cs.ucl.ac.uk>
To: rem-conf <rem-conf@es.net>, agents <agents@cs.umbc.edu>, 
    mymobile <mymobile@egroups.com>, 
    mobile-systems <mobile-systems@cs.ucl.ac.uk>
Subject: CFP: AMOC 2000, Malaysia
Date: Wed, 3 May 2000 23:49:21 +0100
Organization: University College London
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


                          Call for Papers

         FIRST ASIAN INTERNATIONAL MOBILE COMPUTING CONFERENCE
                            (AMOC 2000)
            31 October - 3 November, 2000. Penang, Malaysia
                
                Organised by University Malaya, Malaysia
                   In cooperation with ACM SIGMOBILE
                 With main support from MRCB Multimedia

                    http://www.fsktm.um.edu.my/amoc
            http://www.cs.ucl.ac.uk/staff/F.AbdulRahman/amoc

             *** Submission deadline: 30 May, 2000 ***

Latest update:
1. 200 word abstract to be included in the separate 'Author details'  
   plain text document.
2. Tutorials confirmed - see details below.

Mobile computing is a new and highly dynamic field which combines
modern computer science, networking and wireless communication
technologies. This conference will provide a platform for researchers
and practitioners to meet and discuss current issues in this field. 
The conference is also unique as it highly encourages contributions 
>from the Asian region alongside those from other parts of the globe. 
The focus on Asia is important because there are unique regional 
issues not given attention in typical international conferences, where 
technological issues in developed nations receive centre stage. These 
issues include different infrastructural and economic requirements; 
the effect of a more diverse socio-economic environment on 
technical specifications; the far-reaching impact of wireless 
communication in rural areas and the great interest in the rapid 
deployment of cutting edge technology due to the high progress rate of 
technological implementation in many Asian countries. 

The main objectives of this conference are:

1. To provide a platform for international and Asian researchers and 
   professionals to meet and discuss issues pertinent to both universal 
   and Asia-centric mobile computing issues.
2. To provide participants with up-to-date information regarding the
   development in this field.
3. To provide a yardstick by which researchers may compare the quality
   of their work to that of their peers in order to maintain a high
   standard of research.

The topics of interest include, but are not limited to, those listed
below:

o Quality of Service(QoS)           o handover & location management
o systems infrastructure            o satellite technology
o internet access                   o power management
o data services                     o lower layer protocols
o rural wireless communications     o data management
o billing                           o security
o e-commerce                        o agent technology
o multimedia                        o hardware
o Personal Communication Systems    o terminal design & ergonomics
o wireless LANs / WANs              o nomadic systems

Important Dates
-------------------
Submission deadline: 30 May, 2000
Notification of acceptance: 15 July, 2000
Camera ready copy: 15 August, 2000

Submission Guidelines
----------------------------
Papers should be original, unpublished and not more than ten
single-spaced pages with a minimum font size of 10 pt. Papers must be 
in postscript format, and should only contain the paper
title and the body of the paper, WITHOUT author names and
affiliations. A separate plain text document containing only the 
title, author names, their respective affiliations and 200 word 
abstract, is required. Please send your paper (in postscript format) 
and your separate author page (in plain text format) in separate 
emails to amoc-submission@fsktm.um.edu.my by the 30th of May, 2000.

For more information, please visit http://www.fsktm.um.edu.my/amoc/ or
email amoc-submission@fsktm.um.edu.my

Best Student Paper Award
------------------------
The best paper with a student as primary author will be awarded a
really cool prize of US$500 during the conference. Student authors who
would like to be considered for this award should write 'Student Paper' 
in the plain text document containing the paper title and author 
name(s) and affiliation(s).

Tutorials
---------

There will be two half-day and one full-day tutorials on 31 October. 
The full-day tutorial will run in parallel with each of the half-day
tutorials. The tutorials are:

1. Client-server Computing in Wireless and Mobile Environments
   Prof. Abdelsalam Helal, University of Florida. 
   (Full Day)

2. Java based Mobile Computing - JINI, Mobile Objects and Agents 
   Dr. Omer F. Rana, University of Wales. 
   (Half Day)

3. Mobile Ad Hoc Wireless Networks 
   Dr. Somprakash Bandyopadhyay from PriceWaterhouse Coopers Ltd.,
   Dr. Krishna Paul from Cognizant Technology Solutions, India. 
   (Half Day)


Organising Committee
--------------------
Prof. Ir. Dr. Mashkuri Hj. Yaacob (Universiti Malaya)
Dr Mazliza Othman (Universiti Malaya)
Alfarez Abdul Rahman (University College London)
Dr Roziati Zainuddin (Universiti Malaya)
Dr. Zaitun Abu Bakar (Universiti Malaya)
Rodziah Latih (Universiti Kebangsaan Malaysia)
Norizan Mohd Yasin (Universiti Malaya)
Omar Zakaria (Universiti Malaya)
Mustaffa Kamal (Universiti Malaya)

Technical Program Committee
---------------------------
Assc. Prof. David K. Asano, Shinshu University, Japan
Prof. Boualem Boashash, Queensland University of Technology, Australia 
Dr. Che Nyan Husain, Telekom Malaysia 
Prof. Chuah Hean Teik, Universiti Multimedia Telekom, Malaysia 
Prof. Jon Crowcroft, University College London, UK
Prof. Sajal Das, University of North Texas, USA 
Assc. Prof. Norsheila Faisal, Universiti Teknologi Malaysia
Prof. Sandeep Gupta, Colorado State University, USA 
Dr. Stephen Hailes, University College London, UK
Prof. Abdelsalam Helal, University of Florida, USA
Ravi Jain, Telcordia, USA 
Dr. Minseok Kang, LG Corporate Institute of Technology, Korea 
Prof. Ryuji Kohno, Yokohama University, Japan 
Prof. Sung-Kwon Chung, Seoul National University, Korea 
Dr. Jong-Hyeon Lee, Cambridge University, UK 
Bo Li, Hong Kong University of Science & Technology
Prof Jason Yi-Bing Lin, National Chiao Tung University, Taiwan
Dr. Seng-Wai Loke, Monash University, Australia 
Dr. Jelena Misic, Hong Kong University of Science & Technology
Assc. Prof. George Mohay, Queensland University of Technology, Australia 
Susan Pancho, Cambridge University, UK
Prof. Pradip Srimani, Colorado State University, USA
Dr. Fumio Teraoka, Sony Computer Science Labs, Inc., Japan
Prof. C-K Toh, Georgia Institute of Technology 
Prof. Yu-Chee Tseng, National Central University, Taiwan 
Dr. Arkady Zaslavsky, Monash University, Australia 
Dr. Jianying Zhou, Kent Ridge Digital Lab, Singapore 





From rem-conf Wed May 03 19:22:53 2000 
From rem-conf-request@es.net Wed May 03 19:22:51 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12nBEW-0006jS-00; Wed, 3 May 2000 19:19:20 -0700
Received: from brisco.passedge.com [4.18.242.15] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12nBEV-0006iv-00; Wed, 3 May 2000 19:19:19 -0700
Received: by BRISCO with Internet Mail Service (5.5.2650.21)
	id <25BKH7ND>; Wed, 3 May 2000 19:19:11 -0700
Message-ID: <07E816C410ECD311BBEE00C04FA14BCF0C5F13@BRISCO>
From: "Baugher, Mark" <mbaugher@passedge.com>
To: 'Tim Chen' <scc@trillium.com>, "'rem-conf@es.net'" <rem-conf@es.net>
Cc: Michael Bird <m_bird@trillium.com>
Subject: RE: Current RTP-MIB definition precludes multi-unicast RTP sessio
	 n?
Date: Wed, 3 May 2000 19:19:05 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Tim


> Here the pair of addresses refer to the receiving RTP and
> RTCP address for that participant,  NOT a local RTP address
> and a remote RTP address as in the current MIB draft.  

I agree though the RTP MIB draft does correctly support
the RTP/RTCP port pair in its definitions.  Your statement
might lead someone to think otherwise.  The MIB does
not support multipoint unicast addresses for an RTP
session from an RTP end system.  In the RTP MIB,
a "unicast RTP session" is an association between
two endpoints.

> 
> "The destination transport address pair may be be common
> for all participants, as in the case of IP multicast, or
> MAY BE DIFFERENT FOR EACH, as in the case of individual
> unicast network addresses plus a common port pair."
> 
> So the specs allow for a scenario where I have user A, B and
> C each using a different transport address pair to receive
> RTP and RTCP packets to participate in a single RTP session.  

Yes, an RTP session can have multiple unicast endpoints.  The
spec discusses this in the context of a translator.  Yo 

> This is quite a valid scenario for a 3-way conference
> call.  Under the current MIB definition, I cannot treat
> this as a single RTP session. 

I think it would be cleaner to call this an RTP translator
function and write a translator MIB for it.

Mark 





From rem-conf Thu May 04 08:42:34 2000 
From rem-conf-request@es.net Thu May 04 08:42:33 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12nNds-00079I-00; Thu, 4 May 2000 08:34:20 -0700
Received: from 20-168.015.popsite.net (manager-one) [216.126.188.168] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12nNcy-00078d-00; Thu, 4 May 2000 08:33:31 -0700
From: <manager-one@ccnmail.com>
Subject: Fulfill Your Potential
Date: Thu, 4 May 2000 04:57:14
Message-Id: <899.130837.574343@manager-one>
Bcc:
To: rem-conf@es.net
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

THIS IS NOT SPAM.  THE FOLLOWING INFORMATION HAS BEEN REQUESTED BY YOU 
OR SOMEONE ELSE.  IF YOU WISH TO BE REMOVED FROM OUR MAILING LIST JUST 
TYPE THE WORD REMOVE IN THE SUBJECT AND E-MAIL TO 
MAMAGER-ONE@CCNMAIL.COM
________________________________________________________________________

WORK AT HOME USING YOUR COMPUTER!!!

Dear Friend,

You can earn $46,000 or more in next the 90 days sending e-mail.
Seem impossible? Read on for details (no, there is no "catch")...

"AS SEEN ON NATIONAL T.V."

Thank you for your time and Interest.

This is the letter you've been reading about in the news lately.

Due to the popularity of this letter on the internet, a major nightly 
news program recently devoted an entire show to the investigation of the 
program described below, to see if it really can make people money.

The show also investigated whether or not the program was legal.  Their 
findings proved once and for all that there are, absolutely no laws 
prohibiting the participation in the program. This has helped to show 
people that this is a simple, harmless and fun way to make some extra 
money at home.

The results of this show have been truly remarkable. So many people are 
participating that those involved are doing, much better than ever 
before.  Since everyone makes more as more people try it out, it's been 
very exciting to be a part of lately. You will understand once you 
experience it.

"HERE IT IS BELOW"


*** Print This Now For Future Reference ***

The following income opportunity is one you may be interested in taking 
a look at. It can be started with VERY LITTLE investment and the income 
return is TREMENDOUS!!!

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

If you would like to make at least $46,000 in less than 90 days! Please 
read the enclosed program...THEN READ IT AGAIN!!!

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

THIS IS A LEGITIMATE, LEGAL, MONEY MAKING OPPORTUNITY. It does not 
require you to come into contact with people, do any hard work, and best 
of all, you never have to leave the house except to get the mail. If you 
believe that someday you'll get that big break that you've been waiting 
for, THIS IS IT! Simply follow the instructions, and your dreams will 
come true.


This multi-level e-mail order marketing program works perfectly...100%
EVERY TIME. E-mail is the sales tool of the future. Take advantage of 
this non-commercialized method of advertising NOW!!! The longer you 
wait, the more people will be doing business using e-mail. Get your 
piece of this action!!!

MULTI-LEVEL MARKETING (MLM) has finally gained respectability. It is 
being taught in the Harvard Business School, and both Stanford Research 
and the Wall Street Journal have stated that between 50% and 65% of all 
goods and services will be sold through multi-level methods by the mid 
to late 1990's.

This is a Multi-Billion Dollar industry and of the 3,500,000 
millionaires in the WORLD, 20% (700,000) made their fortune in the last 
several years in MLM. Moreover, statistics show that over 100 people 
become millionaires everyday through Multi-Level Marketing.

You may have heard this story before, but over the summer Donald Trump 
(A MULTI-BILLIONAIRE, ONE OF THE WEALTHIEST MEN IN THE WORLD) made an 
appearance on the David Letterman show. Dave asked him what he would do 
if he lost everything and had to start over from scratch. Without 
hesitating, Trump said he would find a good network marketing company 
and get to work.  The audience started to hoot and boo him. He looked 
out at the audience and dead-panned his response "That's why I'm sitting 
up here and you are all sitting out there!"

With network marketing you have two sources of income. Direct 
commissions from sales you make yourself and commissions from sales made 
by people you introduce to the business.

Residual income is the secret of the wealthy. It means investing time or 
money once and getting paid again and again and again. In network 
marketing, it also means getting paid for the work of others.

This program is currently being utilized in more than 50 different 
countries across the world.

The enclosed INF0RMATION is something I almost let slip through my 
fingers.  Fortunately, sometime later I re-read everything and gave some 
thought and study to it.

My name is Johnathon Rourke. Two years ago, the corporation I worked at 
for the past twelve years downsized and my position was eliminated.  
After unproductive job interviews, I decided to open my own business.  
Over the past year, I incurred many unforeseen financial problems. I 
owed my family, friends and creditors over $35,000. The economy was 
taking a toll on my business and I just couldn't seem to make ends meet. 
I had to refinance and borrow against my home to support my family and 
struggling business.

AT THAT MOMENT something significant happened in my life and I am 
writing to share the experience in hopes that this will change your life 
FOREVER FINANCIALLY!!!

In mid December, I received this program via e-mail. Six month's prior 
to receiving this program I had been sending away for INF0RMATION on 
various business opportunities. All of the programs I received, in my 
opinion, were not cost effective. They were either too difficult for me 
to comprehend or the initial investment was too much for me to risk to 
see if they would work or not. One claimed that I would make a million 
dollars in one year...it didn't tell me I'd have to write a book to make 
it!

But like I was saying, in December of 1997 I received this program.  I 
didn't send for it, or ask for it, they just got my name off a mailing 
list. THANK GOODNESS FOR THAT!!! After reading it several times, to make 
sure I was reading it correctly, I couldn't believe my eyes. Here was a 
MONEY MAKING PHENOMENON. I could invest as much as I wanted to start, 
without putting me further into debt.  After I got a pencil and paper 
and figured it out, I would at least get my money back. But like most of 
you I was still a little skeptical and a little worried about the legal 
aspects of it all. So I checked it out with the U.S. Post Office 
(1-800-725-2161 24-hrs) and they confirmed that it is indeed legal! 
After determining the program was LEGAL and NOT A CHAIN LETTER, I 
decided "WHY NOT."

Initially I sent out 100,000 e-mails. It cost me about $15 for my time 
on-line. The great thing about e-mail is that I don't need any money for 
printing to send out the program, and because all of my orders are 
fulfilled via e-mail, the only expense is my time. I am telling you like 
it is, I hope it doesn't turn you off, but I promised myself that I 
would not "rip-off" anyone, no matter how much money it cost me.

In less than one week, I was starting to receive orders for REPORT #1.  
By January 13, I had received 26 orders for REPORT #1. Your goal is to 
"RECEIVE at least 20 ORDERS FOR REPORT #1 WITHIN 2 WEEKS. IF YOU DON'T,
SEND OUT MORE PROGRAMS UNTIL YOU DO!" My first step in making $46,000 in 
90 days was done.

By January 30, I had received 196 orders for REPORT #2.  Your goal is to 
"RECEIVE AT LEAST 100+ ORDERS FOR REPORT #2 WITHIN 2 WEEKS. IF NOT, SEND
OUT MORE PROGRAMS UNTIL YOU DO. ONCE YOU HAVE 100 ORDERS, THE REST IS 
EASY, RELAX, YOU WILL MAKE YOUR $46,000 GOAL." Well, I had 196 orders 
for REPORT #2, 96 more than I needed. So I sat back and relaxed.

By March 1, of my e-mailing of 100,000, I received $58,000 with more 
coming in every day.

I paid off ALL my debts and bought a much-needed new car. Please take 
time to read the attached program, IT WILL CHANGE YOUR LIFE FOREVER!!!  
Remember, it won't work if you don't try it. This program does work, but 
you must follow it EXACTLY, especially the rules of not trying to place 
your name in a different place. It won't work, you'll lose out on a lot 
of money! 

In order for this program to work, you must meet your goal of 20+ orders 
for REPORT #1, and 100+ orders for REPORT #2 and you will make $46,000 
or more in 90 days. I AM LIVING PROOF THAT IT WORKS!!!

If you choose not to participate in this program, I am sorry. It really 
is a great opportunity with little cost or risk to you. If you choose to 
participate, follow the program and you will be on your way to financial 
security.

If you are a fellow business owner and are if financial trouble like 
I was, or you want to start your own business, consider this a sign. I 
DID!

Sincerely,

Johnathon Rourke


A PERSONAL NOTE FROM THE ORIGINATOR OF THIS PROGRAM:

By the time you have read the enclosed program and reports, you should 
have concluded that such a program, and one that is legal, could not 
have been created by an amateur.

Let me tell you a little about myself. I had a profitable business for 
10 years. Then in 1979 my business began falling off. I was doing the 
same things that were previously successful for me, but it wasn't 
working.  Finally, I figured it out.  It wasn't me, it was the economy. 
Inflation and recession had replaced the stable economy that had been 
with us since 1945.  I don't have to tell you what happened to the 
unemployment rate, because many of you know from first hand experience. 
There were more failures and bankruptcies than ever before.

The middle class was vanishing. Those who knew what they were doing 
invested wisely and moved up. Those who did not, including those who 
never had anything to save or invest, were moving down into the ranks of 
the poor. As the saying goes, "THE RICH GET RICHER AND THE POOR GET 
POORER."  The traditional methods of making money will never allow you 
to "move up" or "get rich", inflation will see to that.

You have just received INF0RMATION that can give you financial freedom 
for the rest of your life, with "NO RISK" and "JUST A LITTLE BIT OF 
EFFORT."
You can make more money in the next few months than you have ever 
imagined.

I should also point out that I will not see a penny of this money, nor 
anyone else who has provided a testimonial for this program. I have 
already made over 4 MILLION DOLLARS! I have retired from the program 
after sending out over 1,600,000 programs. Now I have several offices 
that make this and several other programs here and over seas.

Follow the program EXACTLY AS INSTRUCTED. Do not change it in any way.  
It works exceedingly well as it is now. Remember to e-mail a copy of 
this exciting report to everyone you can think of.  One of the people 
you send this to may send out 100,000 or more...and your name will be on 
everyone of them! Remember though, the more you send out the more 
potential customers you will reach.

So my friend, I have given you the ideas, INF0RMATION, materials and 
opportunity to become financially independent, IT IS UP TO YOU NOW!

"THINK ABOUT IT"

Before you delete this program from your mailbox, as I almost did, take 
a little time to read it and REALLY THINK ABOUT IT. Get a pencil and 
figure out what could happen when YOU participate. Figure out the worst 
possible response and no matter how you calculate it, you will still 
make a lot of money! You will definitely get back what you invested. Any 
doubts you have will vanish when your first orders come in. IT WORKS!
Jody Jacobs, Richmond, VA

HERE'S HOW THIS AMAZING PROGRAM WILL MAKE YOU THOUSANDS OF DOLLAR$

INSTRUCTIONS:

This method of raising capital REALLY WORKS 100% EVERY TIME. I am sure 
that you could use up to $46,000 or more in the next 90 days. Before you 
say: "BULL.... ", please read this program carefully. This is not a 
chain letter, but a perfectly legal money making opportunity. Basically, 
this is what you do: 

As with all multi-level businesses, we build our business by recruiting 
new partners and selling our products. Because of the global nature of 
the internet, you will be able to recruit new multi-level business 
partners from all over the world, and we offer a product for EVERY 
dollar sent. YOUR ORDERS COME BY MAIL AND ARE FILLED BY E-MAIL, so you 
are not involved in personal selling. You do it privately in your own 
home, store or office.  This is the GREATEST Multi-Level Mail Order 
Marketing anywhere.

This is what you MUST do:

1. Order all 5 reports shown on the list below (you can't sell them if 
you don't order them).

a. For each report, send $5.00 CASH, the NAME & NUMBER OF THE REPORT YOU
ARE ORDERING, YOUR E-MAIL ADDRESS, and YOUR NAME & RETURN ADDRESS (in 
case of a problem) to the person whose name appears on the list next to 
the report.  MAKE SURE YOUR RETURN ADDRESS IS ON YOUR ENVELOPE IN CASE 
OF ANY MAIL PROBLEMS!

b. When you place your order, make sure you order each of the five 
reports.  You will need all five reports so that you can save them on 
your computer and resell them.

c. Within a few days you will receive, via e-mail, each of the five 
reports. Save them on your computer so they will be accessible for you 
to send to the 1,000's of people who will order them from you.

2. IMPORTANT-- DO NOT alter the names of the people who are listed next 
to each report, or their sequence on the list, in any way other than is 
instructed below in steps "a" through "g" or you will lose out on the 
majority of your profits. Once you understand the way this works, you'll 
also see how it doesn't work if you change it. Remember, this method has 
been tested, and if you alter it, it will not work.

a. Look below for the listing of available reports.

b. After you've ordered the five reports, take this advertisement and 
REM0VE the name and address under REPORT #5. This person has made it 
through the cycle and is no doubt counting their $46,000! Also, change 
the name of the company, the address, and the REM0VE e-mail address on 
the top of this document to your own.

c. Move the name and address under REPORT #4 down to REPORT #5.

d. Move the name and address under REPORT #3 down to REPORT #4.

e. Move the name and address under REPORT #2 down to REPORT #3.

f. Move the name and address under REPORT #1 down to REPORT #2.

g. Insert your name/address in the REPORT #1 position.

Please make sure you copy every name and address ACCURATELY!

3. Take this entire letter, including the modified list of names, and 
save it to your computer. Make NO changes to the instruction portion of 
this letter.

Your cost to participate in this is practically nothing (surely you can 
afford $25). You obviously already have an Internet connection and 
e-mail is FREE!

To assist you with marketing your business on the internet, the 5 
reports you purchase will provide you with invaluable marketing 
INF0RMATION which includes how to send bulk e-mails, where to find 
thousands of free classified ads and much, much more.

In addition you will be provided with INF0MATION on Internet Marketing 
Clubs such as INTERNET MARKETING RESOURCES (IMR): This is one the 
premiere internet marketing clubs on the INTERNET. This club provides a 
forum where internet marketers from all over the world can exchange 
ideas and secrets on Internet Marketing. In addition, members of this 
club are provided free internet marketing tools and services for the
Do-Yourself-Internet-Marketer.

They will provide you with free bulk e-mail software and up to 1,000,000 
fresh e-mail addresses each week. This club will provide you with 
hundreds of free resources that include: How to obtain free web sites, 
how to obtain top rankings in search engines for your web-site, how to 
send bulk e-mail into AOL and Compuserve, how to market your products on 
newsgroups, free classified ads, electronic malls, bulletin boards, 
banner ads and much more.

There are two primary methods of building your downline:

METHOD #1: SENDING BULK E-MAIL

Let's say that you decide to start small, just to see how it goes, and 
we'll assume you and all those involved send out only 2,000 programs 
each.  Let's also assume that the mailing receives a 0.3% response.  
Using a good list the response could be much better. Also, many people 
will send out hundreds of thousands of programs instead of 2,000. But 
continuing with this example, you send out only 2,000 programs. With a 
0.3% response, that is only 6 orders for REPORT #1. Those 6 people 
respond by sending out 2,000 programs each for a total of 12,000. Out of 
those 0.3%, 36 people respond and order REPORT #2. Those 36 mail out 
2,000 programs each for a total of 72,000. The 0.3% response to that is 
216 orders for REPORT #3.  Those 216 send out 2,000 programs each for a 
432,000 total.  The 0.3% response to that is 1,296 orders for REPORT #4. 
Those 1,296 send out 2,000 programs each for a 2,592,000 total. The 0.3% 
response to that is 7,776 orders for REPORT #5.

That's 7,776 $5 bills for you, CASH!!! Your total income in this 
example is $30 + $180 + $1,080+ $6,480 + $38,880 for a total of 
$46,650!!!

REMEMBER, FRIEND, THIS IS ASSUMING 1,994 OUT OF THE 2,000 PEOPLE 
YOU MAIL TO WILL DO ABSOLUTELY NOTHING AND TRASH THIS PROGRAM! DARE TO 
THINK FOR A MOMENT WHAT WOULD HAPPEN IF EVERYONE, OR HALF SENT OUT 
100,000 PROGRAMS INSTEAD OF 2,000.  Believe me, many people will do just 
that, and more!  By the way, your cost to participate in this is 
practically nothing. You obviously already have an internet connection 
and e-mail is FREE!!!

REPORT #2 and #5 will show you the best methods for bulk emailing, tell 
you where to obtain free bulk e-mail software and where to obtain e-mail 
lists and show you how to send out 1,000,000 e-mails for free.

METHOD #2 - PLACING FREE ADS ON THE INTERNET

1. Advertising on the 'Net is very, very inexpensive, and there are 
HUNDREDS of FREE places to advertise. Let's say you decide to start 
small just to see how well it works. Assume your goal is to get ONLY 6 
people to participate on your first level. (Placing a lot of FREE ads on 
the internet will EASILY get a larger response.) Also assume that 
everyone else in YOUR ORGANIZATION gets ONLY 6 downline members. Follow 
this example to achieve the STAGGERING results below.

1st level--your 6 members with $5 ($5 x 6)........................$30
2nd level--6 members from those 6 ($5 x 36)....................$180
3rd level--6 members from those 36 ($5 x 216)............ $1,080
4th level--6 members from those 216 ($5 x 1,296)....... $6,480
5th level-6 members from those 1,296 ($5 x 7,776)... $38,880
.................................................$46,650


Remember friends, this assumes that the people who participate only 
recruit 6 people each. Think for a moment what would happen if they got 
20 people to participate! Many people will get 100's of participants!
THINK ABOUT IT!

For every $5.00 you receive, all you must do is e-mail them the report 
they ordered. THAT'S IT! ALWAYS PROVIDE SAME-DAY SERVICE ON ALL 
ORDERS!  This will guarantee that the e-mail THEY send out, with YOUR 
name and address on it, will be prompt because they can't advertise 
until they receive the report!

AVAILABLE REPORTS

*** Order Each REPORT by NUMBER and NAME ***

Notes:

ALWAYS SEND $5 CASH (U.S. CURRENCY) FOR EACH REPORT
CHECKS NOT ACCEPTED
ALWAYS SEND YOUR ORDER VIA FIRST CLASS MAIL
Make sure the cash is concealed by wrapping it in at least two sheets of 
paper. On one of those sheets of paper, include: (a) the number & name 
of the report you are ordering, (b) your e-mail address, and (c) your 
name & postal address.

PLACE YOUR ORDER FOR THESE REPORTS NOW:
______________________________________________________

REPORT #1 "The Insider's Guide to Advertising for Free on the Internet"

ORDER REPORT #1 FROM:

K and P Scott
48832 Andorra Street
Indio CA 92201
______________________________________________________

REPORT #2 "The Insider's Guide to Sending Bulk E-mail on the 
Internet"

ORDER REPORT #2 FROM:

Michele Richter
P.O. Box 4534
Fort Lauderdale, Fl. 33338-4534

______________________________________________________

REPORT #3 "The Secrets to Multilevel Marketing on the Internet"

ORDER REPORT #3 FROM:

Paul Bowen
1105 Amble Lane
Clearwater, FL
33755

______________________________________________________

REPORT #4 "How to become a Millionaire utilizing the Power of 
Multilevel
Marketing and the Internet"

ORDER REPORT #4 FROM:

RML, Inc.
1584 Huron Church Road
Suite 105
Windsor, ON
N9C 2L1

______________________________________________________

REPORT #5 "How to SEND 1,000,000 e-mails for FREE"

ORDER REPORT #5 FROM:

Ray Jones
113 Thunderlane
Mena, AR 71953-7714
______________________________________________________

______________________________________________________

There currently more than 175,000,000 people online worldwide!


******* TIPS FOR SUCCESS *******

* TREAT THIS AS YOUR BUSINESS! Be prompt, professional, and follow the 
directions accurately.

* Send for the five reports IMMEDIATELY so you will have them when the 
orders start coming in because:

* When you receive a $5 order, you MUST send out the requested 
product/report.

* ALWAYS PROVIDE SAME-DAY SERVICE ON THE ORDERS YOU RECEIVE.

* Be patient and persistent with this program. If you follow the 
instructions exactly, your results WILL BE SUCCESSFUL!

* ABOVE ALL, HAVE FAITH IN YOURSELF AND KNOW YOU WILL SUCCEED!

******* YOUR SUCCESS GUIDELINES *******

Follow these guidelines to guarantee your success:

If you don't receive 20 orders for REPORT #1 within two weeks, continue 
advertising or sending e-mails until you do. Then, a couple of weeks 
later you should receive at least 100 orders for REPORT#2. If you don't, 
continue advertising or sending e-mails until you do.

Once you have received 100 or more orders for REPORT #2, YOU CAN RELAX, 
because the system is already working for you, and the cash will 
continue to roll in!

THIS IS IMPORTANT TO REMEMBER:

Every time your name is moved down on the list, you are placed in front 
of a DIFFERENT report. You can KEEP TRACK of your PROGRESS by watching 
which report people are ordering from you. If you want to generate more 
income, send another batch of e-mails or continue placing ads and start 
the whole process again! There is no limit to the income you will 
generate from this business!

Before you make your decision as to whether or not you participate in 
this program, please answer one question: DO YOU WANT TO CHANGE YOUR 
LIFE?  If the answer is yes, please look at the following facts about 
this program:

1. YOU ARE SELLING A PRODUCT THAT DOES NOT COST ANYTHING TO PRODUCE!

2. YOU ARE SELLING A PRODUCT THAT DOES NOT COST ANYTHING TO SHIP!

3. YOU ARE SELLING A PRODUCT THAT DOES NOT COST YOU ANYTHING TO 
ADVERTISE!

4. YOU ARE UTILIZING THE POWER OF THE INTERNET AND THE POWER OF 
MULTI-LEVEL MARKETING TO DISTRIBUTE YOUR PRODUCT ALL OVER THE WORLD!

5. YOUR ONLY EXPENSES OTHER THAN YOUR INITIAL $25 INVESTMENT IS YOUR 
TIME!

6. VIRTUALLY ALL OF THE INCOME YOU GENERATE FROM THIS PROGRAM IS PURE 
PROFIT!

7. THIS PROGRAM WILL CHANGE YOUR LIFE FOREVER.

******* T E S T I M O N I A L S *******

This program does work, but you must follow it EXACTLY!  Especially the 
rule of not trying to place your name in a different position, it won't 
work and you'll lose a lot of potential income. I'm living proof that it 
works. It really is a great opportunity to make relatively easy money, 
with little cost to you. If you do choose to participate, follow the 
program exactly, and you'll be on your way to financial security.
Fred Dellaca, Westport, New Zealand

My name is Mitchell. My wife, Jody, and I live in Chicago, IL. I am a 
cost accountant with a major U.S. Corporation and I make pretty good 
money. When I received the program I grumbled to Jody about receiving 
"junk mail." I made fun of the whole thing, spouting my knowledge of the 
population and percentages involved. I "knew" it wouldn't work. Jody 
totally ignored my supposed intelligence and jumped in with both feet. I 
made merciless fun of her, and was ready to lay the old "I told you so" 
on her when the thing didn't work... well, the laugh was on me! Within 
two weeks she had received over 50 responses. Within 45 days she had 
received over $147,200 in $5 bills! I was shocked! I was sure that I had 
it all figured and that it wouldn't work. I AM a believer now. I have 
joined Jody in her "hobby." I did have seven more years until 
retirement, but I think of the "rat race" and it's not for me.  We owe 
it all to MLM.
Mitchell Wolf MD., Chicago, IL

The main reason for this letter is to convince you that this system is 
honest, lawful, extremely profitable, and is a way to get a large amount 
of money in a short time. I was approached several times before I 
checked this out. I joined just to see what one could expect in return 
for the minimal effort and money required. To my astonishment, I 
received $36,470.00 in the first 14 weeks, with money still coming in.
Sincerely yours,
Pam Hedland Halmstad, Sweden


I had received this program before. I deleted it, but later I wondered 
if I shouldn't have given it a try. Of course, I had no idea who to 
contact to get another copy, so I had to wait until I was e-mailed 
another program.  11 months passed then it came...I didn't delete this 
one!  I made more than $41,000 on the first try!!
Mohamed, Cairo, Egypt

This is my third time to participate in this plan. We have quit our 
jobs, and will soon buy a home on the beach and live off the interest on 
our money. The only way on earth that this plan will work for you is if 
you do it.  For your sake, and for your family's sake don't pass up this 
golden opportunity. 
Good luck and happy spending!
Sam Lee Suva, Fiji Islands


ORDER YOUR REPORTS TODAY AND GET STARTED ON YOUR ROAD TO FINANCIAL 
FREEDOM!

NOW IS THE TIME FOR YOUR TURN

DECISIVE ACTION YIELDS POWERFUL RESULTS 
 
 
 
 
 
 
 



From rem-conf Thu May 04 16:33:01 2000 
From rem-conf-request@es.net Thu May 04 16:33:01 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12nUrf-0005rZ-00; Thu, 4 May 2000 16:17:03 -0700
Received: from boreas.isi.edu [128.9.160.161] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12nUre-0005rP-00; Thu, 4 May 2000 16:17:02 -0700
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA03789;
	Thu, 4 May 2000 16:17:00 -0700 (PDT)
Message-Id: <200005042317.QAA03789@boreas.isi.edu>
To: IETF-Announce: ;
Subject: RFC 2793 on RTP Payload for Text Conversation
Cc: rfc-ed@ISI.EDU, rem-conf@es.net
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 04 May 2000 16:16:59 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 2793

        Title:	    RTP Payload for Text Conversation
        Author(s):  G. Hellstrom
        Status:     Standards Track
	Date:       May 2000
        Mailbox:    gunnar.hellstrom@omnitor.se
        Pages:      10
        Characters: 20674
        Updates/Obsoletes/SeeAlso: None   

        URL:        ftp://ftp.isi.edu/in-notes/rfc2793.txt


This memo describes how to carry text conversation session contents
in RTP packets. Text conversation session contents are specified in
ITU-T Recommendation T.140 [1].
 
Text conversation is used alone or in connection to other
conversational facilities such as video and voice, to form multimedia
conversation services.
 
This RTP payload description contains an optional possibility to
include redundant text from already transmitted packets in order to
reduce the risk of text loss caused by packet loss. The redundancy
coding follows RFC 2198.

This document is a product of the Audio/Video Transport Working Group
of the IETF.  

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited. 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <000504161443.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2793

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2793.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <000504161443.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--



From rem-conf Fri May 05 06:18:56 2000 
From rem-conf-request@es.net Fri May 05 06:18:55 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12nhv6-0007Ja-00; Fri, 5 May 2000 06:13:28 -0700
Received: from soleil.uvsq.fr [193.51.24.1] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12nhv1-0007JQ-00; Fri, 5 May 2000 06:13:26 -0700
Received: from lucifer.prism.uvsq.fr (lucifer.prism.uvsq.fr [193.51.25.7])
          by soleil.uvsq.fr (8.9.3/jtpda-5.3.3) with ESMTP id OAA19498
          ; Fri, 5 May 2000 14:47:02 +0200 (CEST)
Received: from prism.uvsq.fr (baudelaire.prism.uvsq.fr [193.51.25.167])
          by lucifer.prism.uvsq.fr (8.9.3/jtpda-5.3.2) with ESMTP id OAA07318
          ; Fri, 5 May 2000 14:29:55 +0200 (MET DST)
Message-ID: <3912C0C5.D8129652@prism.uvsq.fr>
Date: Fri, 05 May 2000 14:38:29 +0200
From: Guy Pujolle <Guy.Pujolle@prism.uvsq.fr>
X-Mailer: Mozilla 4.7 [fr] (Win98; I)
X-Accept-Language: fr
MIME-Version: 1.0
To: net2000@prism.uvsq.fr
Subject: Networking 2000 is just around the corner
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
apologies if you receive multiple copies of this email
<br>&nbsp;****************************************
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<b>IFIP NETWORKING 2000</b>
<br><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
PARIS, May 14-19, 2000</b>
<p><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<A HREF="http://netconf.lip6.fr/net2000">http://netconf.lip6.fr/net2000</A></b>
<p>Networking 2000 conference is a joint conference of:
<p><b>HPN (High Performance Networking) </b>Aaren 1987, Liege 1988, Berlin
1990, Liege 1992, Grenoble 1994, Palma 1995, New York 1997, Vienna 1998,
Paris 2000.
<p><b>BC (Broadband Communications) </b>Paris 1995, Montreal 1996, Lisboa
1997, Stuttgart 1998, Hong-Kong 1999, Paris 2000.
<p><b>PCN (Performance of Communication Networks) </b>Paris 1981, Zurich
1984, Rio de Janeiro 1987, Barcelona 1990, Raleigh 1993, Lund 1998, Paris
2000.
<p>In addition to the conference program :
<br><b>15 tutorials</b>
<br>Cellular IP Approaches: Pr Behcet Sarikaya
<br>Algorithms for forwarding lookup and filtering in high performance
routers: Pr Ernst Biersack
<br>New developments in internet protocols and architecture: Dr Christophe
Diot
<br>Mobile Software Agents for Telecommunication Services on Internet:
Pr Ahmed Karmouch
<br>Les algorithmes pour les routeurs hautes performances: Pr Ernst Biersack
<br>Les technologies d'agents mobiles pour les t&eacute;l&eacute;communications:
Pr Ahmed Karmouch
<br>Mobile Ad-Hoc Networks: Dr Philippe Jacquet
<br>Understanding DWDM Technology in Networks: Dr Stamatios Kartalopoulos
<br>IP Cellulaire: Pr Behcet Sarikaya
<br>Les nouvelles architectures de l'Internet: Dr Christophe Diot
<br>Understanding SLA: Dr Lundy Lewis
<br>Modern Distributed Application Development: CORBA, Servlets, and XML:
Dr Stefan Understanding QoS: Dr Jagannath Shantigram
<br>Voice Over IP: Dr Henning Schulzrinne
<br>Multimedia Enabling Technologies and Applications: Pr Nicolas Georganas
<p><b>8 international workshop and&nbsp; mini-conferences</b> featuring
hot topics in networking
<br>MWCN - Second International Workshop on Mobile and Wireless Communication
Networks
<br>Broadband Satellite Networks
<br>Multimedia Management
<br>Quality of Service and Multimedia Applications
<br>Ressource Allocation for Mobile Networks
<br>Internet and the Web
<br>Programmable Networks and Active Networks
<br>IATE - Intelligent Agents for Telecommunication Environments
<br>&nbsp;</html>




From rem-conf Fri May 05 14:14:41 2000 
From rem-conf-request@es.net Fri May 05 14:14:39 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12npD8-0004XG-00; Fri, 5 May 2000 14:00:34 -0700
Received: from grinch.cks.com [209.116.192.146] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12npD7-0004Wq-00; Fri, 5 May 2000 14:00:33 -0700
Received: (from pmm@localhost)
	by grinch.cks.com (8.9.3/8.9.3) id LAA16897;
	Fri, 5 May 2000 11:19:18 -0700
Date: Fri, 5 May 2000 11:19:17 -0700
From: "Paul M. Moriarty" <pmm@uswebcks.com>
To: friends_and_contacts@grinch.cks.com
Subject: Leaving marchFIRST, formerly USWeb/CKS
Message-ID: <20000505111917.B16880@grinch.cks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hello,

Well, after 3-1/2 yrs, first at CKS, then USWeb/CKS, and finally marchFIRST 
the time has come for me to move on.

Today, Friday, May 5th is my last day.  

For the time being, I can be reached at pmm@igtc.com

Regards,

-> Paul <-

-- 
P A U L   M .   M O R I A R T Y
Partner, Administrative Operations
__________________________________________
USWeb/CKS       <http://www.uswebcks.com/>
2880 Lakeside Drive, Suite 300
Santa Clara, CA  95054
ph: +1 408 986 6776   fax: +1 408 987 3230



From rem-conf Fri May 05 22:26:10 2000 
From rem-conf-request@es.net Fri May 05 22:26:08 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12nwqM-0001Jw-00; Fri, 5 May 2000 22:09:34 -0700
Received: from ha1.rdc1.tn.home.com (mail.rdc1.tn.home.com) [24.2.7.66] (imail)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12nwqL-0001Jc-00; Fri, 5 May 2000 22:09:33 -0700
Received: from ci39026-a.home.com ([24.15.71.131]) by mail.rdc1.tn.home.com
          (InterMail vM.4.01.02.00 201-229-116) with ESMTP
          id <20000506050918.VBMX4902.mail.rdc1.tn.home.com@ci39026-a.home.com>;
          Fri, 5 May 2000 22:09:18 -0700
Message-Id: <4.3.0.20000505220645.00d33100@ctrvax.vanderbilt.edu>
X-Sender: gavishb@mail
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Fri, 05 May 2000 22:09:32 -0500
To: Bezalel Gavish <gavishb@ctrvax.vanderbilt.edu>
From: Bezalel Gavish <gavishb@home.com>
Subject: ICTEC 3 Conference CFPs              g
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=====================_34756492==_"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

--=====================_34756492==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

You are invited to Participate in the 3rd International Conference on 
Telecommunications and Electronic Commerce, which will be held in Dallas, 
TX November 16-19, 2000.

My apologies if you receive multiple copies of the CFPs. 
--=====================_34756492==_
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="ICTEC CFP_20003.txt"

                           Call for Papers
     The Third International Conference on Telecommunications and
                    Electronic Commerce (ICTEC)

        		  Dallas, Texas, USA

	   November 16 (late afternoon) - November 19, 2000
                   http://tecom.cox.smu.edu/ictec


                             Sponsored by
        Cox School of Business, Southern Methodist University
                                ATSMA
               INFORMS College on Information Systems
               INFORMS College on Telecommunications
                             IFIP WG 7.3


                           Important Dates:

Paper (or Extended Abstract) Submission Deadline: July 1, 2000
Panel Proposal Submission Deadline: July 15, 2000
Final Paper Submission Deadline: October 1, 2000
Conference Dates: November 16 - November 19, 2000


Over the past few years, electronic commerce (EC) has emerged as a
dramatic new mode of business. Today, almost every company is either
using or considering EC. Also, advances in telecommunications and
automated processes are already forcing dramatic changes in a variety
of industries, ranging from banking and finance to music and
entertainment. Yet, the TEC (telecommunications and electronic
commerce) environment is still in a relatively early state of
evolution, and many of the significant advances in understanding and
implementing TEC are occurring concurrently in academia and industry.
The traditional sequential process of technology innovation followed
by technology transfer no longer applies. Thus, dialogue on this field
between academia and industry is important. As TEC spans a wide
range of reference disciplines, forums focusing on TEC are
necessary to stimulate the necessary interactions and knowledge
sharing across this broad community.

ICTEC'00 is intended to address these needs. Following on the heels of
the successful second conference in 1999, the goal of the conference
is to bring together both academic and industrial researchers in the
fields of telecommunications and EC on an ongoing, annual basis, to
discuss new technological developments and their implications for
TEC, as well as technological issues that need to be addressed to
further the effectiveness and efficiency of TEC. The conference
combines research tracks in which technical papers will be presented,
with industrial tracks consisting of panels, plenary speakers and exhibits.

Topics of interest for the conference include (but are not limited to)
the following:

* Impact of EC on supply chain, distribution chain management, EDI and
  IOS
* Secure transaction processing methods for electronic commerce
* Design and analysis of multimedia applications on the Internet
* The impact of mobility on EC mechanisms
* Internet traffic management and analysis
* Pricing Internet services
* EC market mechanisms and business models
* EC intermediary roles and their analysis
* Electronic payment mechanisms
* Economic analysis of intranets and extranets
* Design and analysis of intranets
* Data management issues in EC
* Managing response time and content in Web-based information services
* Effective management of electronic commerce transaction servers
* EC developments and challenges in specific industries (e.g.,
  financial services, music, manufacturing, tourism, publishing)
* Globalization issues in EC (standards, regulation, property rights,
  etc.)

Authors should submit an extended abstract of at least 2,000 words, or
a complete paper, to Ms. Dru Lundeng, Conference Manager, by July 1,
2000. In your submission letter indicate which of the Program
Co-chairs should handle the paper. Three hard-copies should be
submitted. Electronic submissions are welcome, but must be augmented
with at least one hard-copy. Authors of accepted papers will be asked
to submit their complete manuscripts to Ms. Lundeng, by October 1,
2000. Accepted papers that are presented at the conference will be
included in the Conference Proceedings. Formatting instructions for
accepted papers will be sent with the acceptance notice. All submitted
papers will be considered for publication in the ACM/Baltzer
Electronic Commerce Research journal
(http://www.baltzer.nl/ecr/ecr.asp).

Panels: Proposals for panels are also invited. Both academic and
industry panels are encouraged. Each proposal should include a list of
panelists with their affiliations. A brief statement explaining the
motivation for the design and composition of the panel should also be
included. The deadline for proposal submission to the program chair is
July 15, 2000.


General Conference Chair:

Bezalel Gavish, Cox School of Business, Southern Methodist University,
P.O. Box 750333, Dallas, TX 75275-0333, USA, gavishb@mail.cox.smu.edu.


Technical Program Co-chairs:

Amit Basu, Cox School of Business, Southern Methodist University, P.O.
Box 750333, Dallas, TX 75275-0333, USA, basua@mail.cox.smu.edu.

Joakim Kalvenes, Cox School of Business, Southern Methodist
University, P.O. Box 750333, Dallas, TX 75275-0333, USA,
kalvenes@mail.cox.smu.edu.


Conference Manager:

Dru Lundeng, Cox School of Business, Southern Methodist University,
P.O. Box 750333, Dallas, TX 75275-0333, USA, dru.lundeng@mail.cox.smu.edu.



--=====================_34756492==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

Professor Bezalel Gavish
Eugene J. and Ruth F. Constantin Distinguished Chair in Business
Edwin L. Cox School of Business
Southern Methodist University
P.O. Box 750333
Dallas, TX 75275-0333
E-mail: gavishb@mail.cox.smu.edu



--=====================_34756492==_--




From rem-conf Fri May 05 22:26:10 2000 
From rem-conf-request@es.net Fri May 05 22:26:07 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12nwsW-0001Mh-00; Fri, 5 May 2000 22:11:48 -0700
Received: from ha1.rdc1.tn.home.com (mail.rdc1.tn.home.com) [24.2.7.66] (imail)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12nwsV-0001Ln-00; Fri, 5 May 2000 22:11:47 -0700
Received: from ci39026-a.home.com ([24.15.71.131]) by mail.rdc1.tn.home.com
          (InterMail vM.4.01.02.00 201-229-116) with ESMTP
          id <20000506051132.VCOH4902.mail.rdc1.tn.home.com@ci39026-a.home.com>;
          Fri, 5 May 2000 22:11:32 -0700
Message-Id: <4.3.0.20000505221021.00d486e0@ctrvax.vanderbilt.edu>
X-Sender: gavishb@mail
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Fri, 05 May 2000 22:11:46 -0500
To: Bezalel Gavish <gavishb@ctrvax.vanderbilt.edu>
From: Bezalel Gavish <gavishb@home.com>
Subject: ICTEC 3 Conference CFPs             h
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=====================_34890961==_"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

--=====================_34890961==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

You are invited to Participate in the 3rd International Conference on 
Telecommunications and Electronic Commerce, which will be held in Dallas, 
TX November 16-19, 2000.

My apologies if you receive multiple copies of the CFPs. 
--=====================_34890961==_
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="ICTEC CFP_20003.txt"

                           Call for Papers
     The Third International Conference on Telecommunications and
                    Electronic Commerce (ICTEC)

        		  Dallas, Texas, USA

	   November 16 (late afternoon) - November 19, 2000
                   http://tecom.cox.smu.edu/ictec


                             Sponsored by
        Cox School of Business, Southern Methodist University
                                ATSMA
               INFORMS College on Information Systems
               INFORMS College on Telecommunications
                             IFIP WG 7.3


                           Important Dates:

Paper (or Extended Abstract) Submission Deadline: July 1, 2000
Panel Proposal Submission Deadline: July 15, 2000
Final Paper Submission Deadline: October 1, 2000
Conference Dates: November 16 - November 19, 2000


Over the past few years, electronic commerce (EC) has emerged as a
dramatic new mode of business. Today, almost every company is either
using or considering EC. Also, advances in telecommunications and
automated processes are already forcing dramatic changes in a variety
of industries, ranging from banking and finance to music and
entertainment. Yet, the TEC (telecommunications and electronic
commerce) environment is still in a relatively early state of
evolution, and many of the significant advances in understanding and
implementing TEC are occurring concurrently in academia and industry.
The traditional sequential process of technology innovation followed
by technology transfer no longer applies. Thus, dialogue on this field
between academia and industry is important. As TEC spans a wide
range of reference disciplines, forums focusing on TEC are
necessary to stimulate the necessary interactions and knowledge
sharing across this broad community.

ICTEC'00 is intended to address these needs. Following on the heels of
the successful second conference in 1999, the goal of the conference
is to bring together both academic and industrial researchers in the
fields of telecommunications and EC on an ongoing, annual basis, to
discuss new technological developments and their implications for
TEC, as well as technological issues that need to be addressed to
further the effectiveness and efficiency of TEC. The conference
combines research tracks in which technical papers will be presented,
with industrial tracks consisting of panels, plenary speakers and exhibits.

Topics of interest for the conference include (but are not limited to)
the following:

* Impact of EC on supply chain, distribution chain management, EDI and
  IOS
* Secure transaction processing methods for electronic commerce
* Design and analysis of multimedia applications on the Internet
* The impact of mobility on EC mechanisms
* Internet traffic management and analysis
* Pricing Internet services
* EC market mechanisms and business models
* EC intermediary roles and their analysis
* Electronic payment mechanisms
* Economic analysis of intranets and extranets
* Design and analysis of intranets
* Data management issues in EC
* Managing response time and content in Web-based information services
* Effective management of electronic commerce transaction servers
* EC developments and challenges in specific industries (e.g.,
  financial services, music, manufacturing, tourism, publishing)
* Globalization issues in EC (standards, regulation, property rights,
  etc.)

Authors should submit an extended abstract of at least 2,000 words, or
a complete paper, to Ms. Dru Lundeng, Conference Manager, by July 1,
2000. In your submission letter indicate which of the Program
Co-chairs should handle the paper. Three hard-copies should be
submitted. Electronic submissions are welcome, but must be augmented
with at least one hard-copy. Authors of accepted papers will be asked
to submit their complete manuscripts to Ms. Lundeng, by October 1,
2000. Accepted papers that are presented at the conference will be
included in the Conference Proceedings. Formatting instructions for
accepted papers will be sent with the acceptance notice. All submitted
papers will be considered for publication in the ACM/Baltzer
Electronic Commerce Research journal
(http://www.baltzer.nl/ecr/ecr.asp).

Panels: Proposals for panels are also invited. Both academic and
industry panels are encouraged. Each proposal should include a list of
panelists with their affiliations. A brief statement explaining the
motivation for the design and composition of the panel should also be
included. The deadline for proposal submission to the program chair is
July 15, 2000.


General Conference Chair:

Bezalel Gavish, Cox School of Business, Southern Methodist University,
P.O. Box 750333, Dallas, TX 75275-0333, USA, gavishb@mail.cox.smu.edu.


Technical Program Co-chairs:

Amit Basu, Cox School of Business, Southern Methodist University, P.O.
Box 750333, Dallas, TX 75275-0333, USA, basua@mail.cox.smu.edu.

Joakim Kalvenes, Cox School of Business, Southern Methodist
University, P.O. Box 750333, Dallas, TX 75275-0333, USA,
kalvenes@mail.cox.smu.edu.


Conference Manager:

Dru Lundeng, Cox School of Business, Southern Methodist University,
P.O. Box 750333, Dallas, TX 75275-0333, USA, dru.lundeng@mail.cox.smu.edu.



--=====================_34890961==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

Professor Bezalel Gavish
Eugene J. and Ruth F. Constantin Distinguished Chair in Business
Edwin L. Cox School of Business
Southern Methodist University
P.O. Box 750333
Dallas, TX 75275-0333
E-mail: gavishb@mail.cox.smu.edu



--=====================_34890961==_--




From rem-conf Sat May 06 03:37:43 2000 
From rem-conf-request@es.net Sat May 06 03:37:41 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12o1nQ-0005Oq-00; Sat, 6 May 2000 03:26:52 -0700
Received: from (winbet systems) [212.49.255.202] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12o1nK-0005Of-00; Sat, 6 May 2000 03:26:50 -0700
From:     WIN-BET <winlots@winwin.co.uk>
To:        <rem-conf@es.net>
Message-Id: <419.436652.47720012winlots@winwin.co.uk>
Subject:  FREE,FOOTBALL FORECASTING TRIAL, HAVE FUN AND WIN
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Sat, 6 May 2000 03:26:50 -0700
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


Hi,
would you like an additional income of Ł6000- Ł8000 per annum?
Our football investment programme can give you just that.

We have a simple proven winning system, you have nothing to lose by checking it out

Have fun on a saturday afternoon watching for our scores to come in, have even more fun on a 
monday morning picking up your winnings


for more information      winlots@winwin.co.uk    
please type more info in the subject line

If you've recieved this e-mail in error we apologise, please reply to   winbet@junglemail.net   and in the 
subject box type remove , to be removed from all mailing lists , again please accept our apologies for 
bothering you 

By providing a contact and remove address we are complying with statute,and this mail cannot legally 
be interpreted as spam




From rem-conf Sat May 06 11:53:24 2000 
From rem-conf-request@es.net Sat May 06 11:53:21 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12o9cn-0002QA-00; Sat, 6 May 2000 11:48:25 -0700
Received: from mrs-2-fix.smartworld.net (mrs-2.smartworld.net) [216.70.64.26] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12o9ci-0002PW-00; Sat, 6 May 2000 11:48:20 -0700
Received: from smtp.freewwweb.com (1Cust197.tnt17.dfw5.da.uu.net [63.22.251.197])
	by mrs-2.smartworld.net (8.9.1a/8.9.1) with SMTP id OAA57861;
	Sat, 6 May 2000 14:48:06 -0500 (CDT)
From: IAMBLESSEDRU3@netscape.net
Received: from mailhost.extrememail2000.com (alt1.extrememail2000.com(208.9.77.000)) by extrememail2000.com (8.8.5/8.6.5) with SMTP id GAA07209 for <Dear inquirer>; Sat, 06 May 2000 13:21:51 -0600 (EST)
Date: Sat, 06 May 00 13:21:51 EST
To: Dear@mrs-2.smartworld.net, inquirer@mrs-2.smartworld.net
Subject: IT'S ME..my new address...
Message-ID: <199702170026.GAA08056@extrememail2000.com>
Reply-To: iamblessedru3@netscape.net
X-UIDL: 98745632123654789874563212365478
Comments: Authenticated sender is <iamblessedru3@netscape.net>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi, Thanks for registering for your 2 FREE airline tickets. Just visit our website to redeem. Simply click on the appropiate banner. Now,

  
How to receive $400.00  A DAY BY SENDING ONE SIMPLE FAX !!


 "BEST KEPT SECRETS OF THE WEALTHY REVEALED" !!


  Discover how to GENERATE HUGE AMOUNTS OF CASH IN DAYS and BECOME LITERALLY WEALTHY OVERNIGHT......
  and we have a $10,000.00 Guarantee to back it up!!!


  You will discover:

  THE GOVERNMENT LOTTERY YOU CAN'T LOSE ! (Your money back if you don't win!)

  HOW TO MAKE $9000 A MONTH FROM ANY BANK YOU CAN FIND !

  HOW TO GET YOUR PART OF THE BILLIONS THE GOVERNMENT IS HOLDING !

  HOW TO EARN A $1000 OR MORE READING NEWSPAPERS !

  HOW TO GET $20,000 WORTH OF FURNITURE FREE !

  HOW TO OWN A BRAND NEW CAR EVERY YEAR ABSOLUTELY FREE !

  HOW TO TRAVEL ANYWHERE IN THE WORLD 2-WAY -FREE !

  HOW TO GET FREE ADVICE FROM "TOP LAWYERS" !

  HOW TO GET REGULAR MAIL POSTAGE FOR 1/2 THE NORMAL PRICE !

  HOW TO REMOVE UNFAVORABLE REMARKS FROM YOUR CREDIT FILE !

  THE SECRET LAW THAT ERASES ALL YOUR DEBT !


  These are only a few of the many "insider secrets" that could make you wealthy overnight ! 

Click here now! http://3506561037/%69%6E%73%74%61%6E%74%6D%6F%6E%65%79%32/%73%65c%72e%74%73.%68%74%6D

(If you experience problems finding our site, please write to: < Link2U98@netscape.net> and we will provide you with a link to our homepage)
NOTE: Please DO NOT use this address to be removed from our list. Please see instructions at the bottom of this ad.


  P.S. Please don't let a moment go by that could keep you from the money and lifestyle you desire and deserve. ACT NOW!


  xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  Bulk E-Mail Senate Bill (We conform to this bill)
**************************************************
  Under Bill S.1618 Title III passed by the 105th U.S. Congress this letter cannot
  be considered, labeled, or treated as "illegal" unsolicited commercial email
  (spam) as long as:
  1. It contains contact information (the site itself)
  2. It contains a method of removal at no cost to the recepient.
  
  If you wish to be removed from any further offers you may do so by hitting reply with  the word "Remove" in the subject field and you will not receive any further mailings from us.






From rem-conf Sat May 06 13:38:09 2000 
From rem-conf-request@es.net Sat May 06 13:38:07 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12oBHd-00049Z-00; Sat, 6 May 2000 13:34:41 -0700
Received: from sun1.cskwam.mil.pl (cskwam.mil.pl) [148.81.119.2] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12oBHL-000494-00; Sat, 6 May 2000 13:34:23 -0700
Received: from localhost by cskwam.mil.pl (SMI-8.6/SMI-SVR4)
	id WAA08342; Sat, 6 May 2000 22:33:15 +0200
From: stanton@uol.com.ar
Message-ID: <0000791e0f3d$000059e5$000029d0@localhost>
To: <>
Subject: FWD:Boost it Naturally
Date: Sat, 06 May 2000 15:48:39 -0400
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Outlook Express  5.75.3210.1
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

<HTML><FONT  SIZE=3D3 PTSIZE=3D10><BR>
</P><P ALIGN=3DCENTER></FONT><FONT  COLOR=3D"#0000ff" SIZE=3D4 PTSIZE=3D11=
><B><I><U> Boost Your Sex Drive!</U><BR>
  </FONT><FONT  COLOR=3D"#ff0066" SIZE=3D4 PTSIZE=3D12>LibidoMagic!</FONT>=
<FONT  COLOR=3D"#000000" SIZE=3D1 PTSIZE=3D6></B></I>(TM)</FONT><FONT  COL=
OR=3D"#ff0000" SIZE=3D4 PTSIZE=3D12><B><I><BR>
  </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D9></I>A Potent 100% al=
l natural Herbal Aphrodisiac for men and women</FONT><FONT  SIZE=3D3 PTSIZ=
E=3D10><BR>
  </FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D9></B>Men and women, w=
ho suffer from sexual dysfunction<BR>
  such as lack of desire, impotency, orgasmic function and lack of fertili=
ty,<BR>
  have for a long time been at the mercy of giant pharmaceutical companies=
.<BR>
  These companies, through their vast advertising budgets, convinced us <B=
R>
that their </FONT><FONT  SIZE=3D3 PTSIZE=3D10>chemically produced remedies=
,are the most effective.<I> </I><BR>
  </FONT><FONT  COLOR=3D"#ff0000" SIZE=3D2 PTSIZE=3D8><B><I>HOWEVER</FONT>=
<FONT  SIZE=3D3 PTSIZE=3D10>,</B></I> </FONT><FONT  COLOR=3D"#000000" SIZE=
=3D3 PTSIZE=3D9>there are equally  powerful</FONT><FONT  COLOR=3D"#0000ff"=
 SIZE=3D3 PTSIZE=3D9><B><U> Natural Alternatives</U><BR>
</FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D9></B>subject to the con=
dition of the individual, that can Revitalize</FONT><FONT  SIZE=3D4 PTSIZE=
=3D11><BR>
  </FONT><FONT  SIZE=3D3 PTSIZE=3D9>and Rejuvenate</FONT><FONT  SIZE=3D3 P=
TSIZE=3D10> </FONT><FONT  SIZE=3D3 PTSIZE=3D9>the system through Natural M=
eans!<U><BR>
</U>Yes, an all natural and safe, alternative to Viagra (tm) </FONT><FONT =
 COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D10><B><BR>
  </FONT><FONT  COLOR=3D"#00cc00" SIZE=3D3 PTSIZE=3D10><U>If you are Norma=
l, it will turbocharge your Sexual Experiences! </U><BR>
  </FONT><FONT  COLOR=3D"#ff0066" SIZE=3D3 PTSIZE=3D10>LibidoMagic! </FONT=
><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10></B>is a 100% natural blend=
 of herbs which causes no side effects,</FONT><FONT  COLOR=3D"#ff0066" SIZ=
E=3D3 PTSIZE=3D10> <BR>
  </FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D9> it  rejuvenates and=
 enhances,the sexual performance of Men and Women.<BR>
  Increase Your Desire, Experience all Natural Sexual Ecstasy<BR>
 add more Romance and Passion into your life. <BR>
Ingredients in LibidoMagic are known to improve prostate health.   <B><BR>
 </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D9>FIRM, POWERFUL, LONG =
LASTING ERECTIONS!<BR>
</FONT><FONT  COLOR=3D"#ff0000" SIZE=3D3 PTSIZE=3D10>ORDER NOW !</FONT><FO=
NT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D9> </FONT><FONT  COLOR=3D"#ff0000"=
 SIZE=3D3 PTSIZE=3D10><BR>
  </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D10> </FONT><FONT  COLO=
R=3D"#000000" SIZE=3D3 PTSIZE=3D10>CREDIT CARD ORDERS</FONT><FONT  SIZE=3D=
4 PTSIZE=3D12>  </FONT><FONT  SIZE=3D4 PTSIZE=3D11>CALL</FONT><FONT  SIZE=3D=
4 PTSIZE=3D12>  954-974-9903</FONT><FONT  SIZE=3D3 PTSIZE=3D10></B><BR>
  </FONT><FONT  COLOR=3D"#ff0066" SIZE=3D4 PTSIZE=3D12><B>LibidoMagic</FON=
T><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10> only </FONT><FONT  COLOR=3D=
"#003333" SIZE=3D3 PTSIZE=3D10>$49.99 Per Bottle of Sixty Capsules +$7.00 =
S/H</FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10> </FONT><FONT  COL=
OR=3D"#008000" SIZE=3D3 PTSIZE=3D10> </FONT><FONT  COLOR=3D"#000033" SIZE=3D=
3 PTSIZE=3D10>  </FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10></B><=
BR>
  </FONT><FONT  COLOR=3D"#003333" SIZE=3D3 PTSIZE=3D10><B> Two bottles for=
 $89.99 save $10.00</FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10><B=
R>
Distributors Welcome!!</FONT><FONT  COLOR=3D"#008000" SIZE=3D3 PTSIZE=3D10=
> </FONT><FONT  COLOR=3D"#000000" SIZE=3D4 PTSIZE=3D12></B><BR>
  </FONT><FONT  SIZE=3D3 PTSIZE=3D9><B>To Order By Mail See End of Message=
.</FONT><FONT  SIZE=3D3 PTSIZE=3D10><BR>
  </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D10>To Fax Orders Only =
That Number   is<BR>
  310-358-7317</FONT><FONT  COLOR=3D"#ff0000" SIZE=3D3 PTSIZE=3D9>   <BR>
  </FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D9>It will help Women t=
o have,<BR>
  </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D9>FASTER AROUSAL! STRO=
NGER & DEEPER FULFILLMENT!<BR>
  STIMULATING SENSATIONS !</FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D=
9></B><BR>
</FONT><FONT  COLOR=3D"#ff0000" SIZE=3D3 PTSIZE=3D10><B> LibidoMagic</FONT=
><FONT  SIZE=3D2 PTSIZE=3D8> </FONT><FONT  COLOR=3D"#000000" SIZE=3D2 PTSI=
ZE=3D8></B>is formulated to</FONT><FONT  COLOR=3D"#ff0066" SIZE=3D3 PTSIZE=
=3D10> </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D9><B>enhance</B> =
</FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D9>your sexual experience=
 </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D9><B>naturally.</FONT><=
FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D9></B><BR>
  The active ingredient in<B> </FONT><FONT  COLOR=3D"#ff0066" SIZE=3D3 PTS=
IZE=3D10>LibidoMagic </FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10>=
</B>has been proven<BR>
  to be a natural sexual enhancer.<BR>
  Increase in energy and well being, relief of many PMS<BR>
  and menopausal symptoms in women,strength and endurance as well<BR>
  as stamina, which is why multiple orgasms will be experienced. It helps<=
BR>
  to enhance sexual sensations, improves responsiveness and assertiveness.=
</FONT><FONT  COLOR=3D"#ff0066" SIZE=3D3 PTSIZE=3D10>   </FONT><FONT  COLO=
R=3D"#000000" SIZE=3D3 PTSIZE=3D10><BR>
  <B><U>Order This Fabulous Product Today!<BR>
</U>LibidoMagic</FONT><FONT  SIZE=3D2 PTSIZE=3D8> </FONT><FONT  SIZE=3D3 P=
TSIZE=3D9>out performs, and the price beats TV advertised competition!</FO=
NT><FONT  COLOR=3D"#ff0000" SIZE=3D3 PTSIZE=3D10><U><BR>
</U>GO AHEAD, ORDER NOW ! MONEY BACK GUARANTEE !</FONT><FONT  COLOR=3D"#00=
0000" SIZE=3D3 PTSIZE=3D10></B><BR>
  <B>CREDIT CARD ORDERS</FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D1=
0><BR>
  </FONT><FONT  COLOR=3D"#000000" SIZE=3D4 PTSIZE=3D12>Call 954-974-9903</=
FONT><FONT  COLOR=3D"#ff0000" SIZE=3D3 PTSIZE=3D10><BR>
 </FONT><FONT  SIZE=3D4 PTSIZE=3D12> LibidoMagic!</FONT><FONT  SIZE=3D4 PT=
SIZE=3D11><I><U><BR>
</FONT><FONT  COLOR=3D"#ff0066" SIZE=3D4 PTSIZE=3D12></I></U>LibidoMagic</=
FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10> only </FONT><FONT  COL=
OR=3D"#003333" SIZE=3D3 PTSIZE=3D10>$49.99 Per Bottle of Sixty Capsules +$=
7.00 S/H</FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10> </FONT><FONT=
  COLOR=3D"#008000" SIZE=3D3 PTSIZE=3D10> </FONT><FONT  COLOR=3D"#000033" =
SIZE=3D3 PTSIZE=3D10>  </FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D1=
0></B><BR>
  </FONT><FONT  COLOR=3D"#003333" SIZE=3D3 PTSIZE=3D10><B> Two bottles for=
 $89.99 save $10.00</FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10><B=
R>
  </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D3 PTSIZE=3D10>To Fax an Order onl=
y the number is 310-358-7317<BR>
  No Credit Card? No Problem<BR>
  Make Check or Money Order payable to VNR<BR>
  and mail to:<BR>
  </FONT><FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10>VNR<BR>
  P.O. BOX 590953<BR>
  FT. LAUDERDALE <BR>
  FL. 33359<BR>
  <BR>
  </FONT><FONT  SIZE=3D2 PTSIZE=3D8>We do wait until personal checks clear=
 our bank, before mailing   your order<BR>
  For Fax Orders, please print and fax the following to:<BR>
  </FONT><FONT  COLOR=3D"#0000ff" SIZE=3D4 PTSIZE=3D12>310-358-7317</FONT>=
<FONT  COLOR=3D"#000000" SIZE=3D3 PTSIZE=3D10></B><BR>
  </FONT><FONT  SIZE=3D3 PTSIZE=3D9>Name__________________________________=
_______________<BR>
  <BR>
  Address_______________________________________________<BR>
  <BR>
  City_______________________State_______Zip______________<BR>
  <BR>
  Phone#__________________Email Address__________________<BR>
  <BR>
  CreditCard____________________________MC/ V/ AmEx<BR>
  <BR>
  Card Number___________________________________________<BR>
  <BR>
  Expiration Date_______________<BR>
  <BR>
  I wish to order_____Bottle(s) </FONT><FONT  SIZE=3D3 PTSIZE=3D10><BR>
  <B><BR>
  </B> </FONT><FONT  SIZE=3D3 PTSIZE=3D9>you will receive a confirmation o=
f your   order .</FONT><FONT  SIZE=3D3 PTSIZE=3D10><BR>
  </FONT><FONT  SIZE=3D2 PTSIZE=3D8> This e-mail message is being sent in =
accordance   with proposed <BR>
  U.S. Federal regulations for commercial e-mail as well as the <BR>
  Washington state commercial e-mail law. <BR>
  To be removed from list click <A HREF=3D"stanton@uol.com.ar?subject=3Dre=
move">   REMOVE</A><BR>
  </FONT><FONT  SIZE=3D3 PTSIZE=3D10><BR>
  <BR>
</FONT><FONT  SIZE=3D2 PTSIZE=3D8><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  </FONT><FONT  SIZE=3D3 PTSIZE=3D10> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</P></HTML>






From rem-conf Sun May 07 19:55:24 2000 
From rem-conf-request@es.net Sun May 07 19:55:22 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12odTj-0004ya-00; Sun, 7 May 2000 19:41:03 -0700
Received: from compuscan.co.za (mail.compuscan.co.za) [196.25.202.131] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12odTd-0004xp-00; Sun, 7 May 2000 19:40:58 -0700
Received: from 209.149.163.79 [209.149.163.79] by mail.compuscan.co.za
  (SMTPD32-4.07) id AF3E7180148; Mon, 08 May 2000 04:04:30 PST
From: gft6@aol.com
To: lkw3@aol.com
Subject: Accept Visa and Mastercard Lowest Rates !!!
Date: Sun, 07 May 00 22:12:07 Eastern Daylight Time
Reply-To: gft6@aol.com
X-Priority: 3
X-MSMailPriority: Normal
Importance: Normal
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_018C_01BD9940.715D52A0"
Message-Id: <E12odTd-0004xp-00@mail1.es.net>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_018C_01BD9940.715D52A0
Content-Type: text/html;

<HTML>
<BODY>

<FONT face="MS Sans Serif">
<FONT size=3>
<FONT color="#000000"> ACCEPT ALL MAJOR CREDIT CARDS<BR>
99% APPROVAL RATE ALL BUSINESSES ACCEPTED<BR>
0 DOWN , NO APPLICATION FEES<BR>
LOWEST RATES,LOW MONTHLY PAYMENTS<BR>
WE WILL BEAT ANY COMPETITOR'S PRICE<BR>
CALL NOW 800-487-9955<BR>
<BR>
ASK ABOUT OUR $100 CASH BACK<BR>
<BR>
<BR>
</FONT></FONT></BODY></HTML>





From rem-conf Mon May 08 03:04:15 2000 
From rem-conf-request@es.net Mon May 08 03:04:13 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12okL2-0002B1-00; Mon, 8 May 2000 03:00:32 -0700
Received: from ausmtp02.au.ibm.com [202.135.136.105] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12okKx-0002AY-00; Mon, 8 May 2000 03:00:28 -0700
Received: from f03n05e.au.ibm.com 
	by ausmtp02.au.ibm.com (IBM AP 1.0) with ESMTP id TAA182182
	for <rem-conf@es.net>; Mon, 8 May 2000 19:54:10 +1000
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n05e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id TAA57120
	for <rem-conf@es.net>; Mon, 8 May 2000 19:59:08 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568D9.0036D94E ; Mon, 8 May 2000 19:59:05 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: rem-conf@es.net
Message-ID: <CA2568D9.0036CA44.00@d73mta05.au.ibm.com>
Date: Mon, 8 May 2000 14:10:11 +0530
Subject: [Fwd: INVITE with RTP RR's to a different address ...]
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list



Actually, this is a discussion more for rem-conf than SIP.

-Jonathan R.
--
Jonathan D. Rosenberg                       200 Executive Drive
Chief Scientist                             Suite 120
dynamicsoft                                 West Orange, NJ 07052
jdrosen@dynamicsoft.com                     FAX:   (732) 741-4778
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com

Received: from wodc7mr4.ffx.ops.us.uu.net by wodc7ps1.ffx.ops.us.uu.net
with ESMTP     (peer crosschecked as: paleoalterdial.UU.NET [192.48.96.22])
id QQifju05095 for <mail183751@vpop0-alterdial.uu.net>; Mon, 6 Mar 2000
20:42:36 GMT
Received: from ns.fmmo.ca by wodc7mr4.ffx.ops.us.uu.net with ESMTP
(peer crosschecked as: www.fmmo.ca [207.253.160.156])   id QQifju22154
for <jdrosen@dynamicsoft.com>; Mon, 6 Mar 2000 20:42:35 GMT
Received: from localhost (fm-listproc@localhost)   by ns.fmmo.ca
(8.9.3/8.9.3) with ESMTP id PAA11741;    Mon, 6 Mar 2000 15:46:33 -0500
Date: Mon, 6 Mar 2000 15:46:32 -0500 (EST)
From: Francois Menard List Account <fm-listproc@fmmo.ca>
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
cc: Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
"'sip@lists.research.bell-labs.com'" <sip@lists.research.bell-labs.com>
Subject: Re: INVITE with RTP RR's to a different address ...
In-Reply-To: <38C2DC68.973CB2F7@dynamicsoft.com>
Message-ID: <Pine.LNX.4.20.0003061544200.11678-100000@ns.fmmo.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mozilla-Status2: 00000000



Does anybody oppose the idea of designing a specific way to do this ... I
know that RTCP has to be managed end-to-end, but there are good instances
where capturing the RTCP feedback in a central repository is better
than doing Netflow analysis ...

-=Francois=-


On Sun, 5 Mar 2000, Jonathan Rosenberg wrote:

> You can easily have both the RTP and RTCP go to one IP address,
> different than the SIP originator (media will go to the address listed
> in the SDP). However, there is no way to have the RTP and RTCP go to
> different addresses.
>
> -Jonathan R.
>
> Francois Menard List Account wrote:
> >
> > Is there a quick way to require the RTP RR's to go to a different IP
> > address than the originating party through a SIP INVITE ?
> >
> > -=Francois=-
>
> --
> Jonathan D. Rosenberg                       200 Executive Drive
> Chief Scientist                             Suite 120
> dynamicsoft                                 West Orange, NJ 07052
> jdrosen@dynamicsoft.com                     FAX:   (732) 741-4778
> http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
> http://www.dynamicsoft.com
>







From rem-conf Mon May 08 03:04:15 2000 
From rem-conf-request@es.net Mon May 08 03:04:13 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12okKJ-0002Ai-00; Mon, 8 May 2000 02:59:47 -0700
Received: from ausmtp01.au.ibm.com [202.135.136.97] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12okKG-0002AR-00; Mon, 8 May 2000 02:59:44 -0700
Received: from f03n05e.au.ibm.com 
	by ausmtp01.au.ibm.com (IBM AP 1.0) with ESMTP id TAA178964
	for <rem-conf@es.net>; Mon, 8 May 2000 19:53:17 +1000
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n05e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id TAA26304
	for <rem-conf@es.net>; Mon, 8 May 2000 19:58:34 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568D9.0036CC62 ; Mon, 8 May 2000 19:58:32 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: rem-conf@es.net
Message-ID: <CA2568D9.0036BFA3.00@d73mta05.au.ibm.com>
Date: Mon, 8 May 2000 14:10:07 +0530
Subject: Re: [Fwd: INVITE with RTP RR's to a different address ...]
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list





There are several reasons why I'm not sure this is the best approach:

1. RRs are needed end to end to enable application adaptation
2. If you want centralized access to the feedback, then have the end
system implement the RTP MIB, and collect the data through that.
3. RRs must be end to end for multicast. I don't like special casing
unicast.

-Jonathan R.

Francois Menard wrote:
> Does anybody oppose the idea of designing a specific way to do this ... I
> know that RTCP has to be managed end-to-end, but there are good instances
> where capturing the RTCP feedback in a central repository is better
> than doing Netflow analysis ...
>
> -=Francois=-
>
> On Sun, 5 Mar 2000, Jonathan Rosenberg wrote:
>
> > You can easily have both the RTP and RTCP go to one IP address,
> > different than the SIP originator (media will go to the address listed
> > in the SDP). However, there is no way to have the RTP and RTCP go to
> > different addresses.
> >
> > -Jonathan R.
> >
> > Francois Menard List Account wrote:
> > >
> > > Is there a quick way to require the RTP RR's to go to a different IP
> > > address than the originating party through a SIP INVITE ?
> > >
> > > -=Francois=-
> >
> > --
> > Jonathan D. Rosenberg                       200 Executive Drive
> > Chief Scientist                             Suite 120
> > dynamicsoft                                 West Orange, NJ 07052
> > jdrosen@dynamicsoft.com                     FAX:   (732) 741-4778
> > http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
> > http://www.dynamicsoft.com
> >

--
Jonathan D. Rosenberg                       200 Executive Drive
Chief Scientist                             Suite 120
dynamicsoft                                 West Orange, NJ 07052
jdrosen@dynamicsoft.com                     FAX:   (732) 741-4778
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com





From rem-conf Mon May 08 03:04:15 2000 
From rem-conf-request@es.net Mon May 08 03:04:13 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12okLe-0002BT-00; Mon, 8 May 2000 03:01:10 -0700
Received: from ausmtp01.au.ibm.com [202.135.136.97] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12okLc-0002Ar-00; Mon, 8 May 2000 03:01:08 -0700
Received: from f03n05e.au.ibm.com 
	by ausmtp01.au.ibm.com (IBM AP 1.0) with ESMTP id TAA143574;
	Mon, 8 May 2000 19:54:05 +1000
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n05e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id TAA72946;
	Mon, 8 May 2000 19:59:22 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568D9.0036DF01 ; Mon, 8 May 2000 19:59:20 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: Martin Mauve <mauve@pi4.informatik.uni-mannheim.de>
cc: rem-conf@es.net, Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Message-ID: <CA2568D9.0036CF9E.00@d73mta05.au.ibm.com>
Date: Mon, 8 May 2000 14:10:13 +0530
Subject: Re: Unique SSRC IDs?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list





Martin Mauve wrote:
>
> It therefore seems that the problem of unique ID distribution has to
> be solved anyway (addressing the concerns you mentioned).

I'm not so sure. Its possible (and is often done), to generate unique
IDs without a central server to guarantee that uniqueness. The problem
is that these IDs are long. Its not an issue for many protocols that use
them, but RTP is different since its packets are so short. Having a 20
byte UUID in the header for a G.723.1 voice packet is simply too much
overhead. Thats why RTP uses this SSRC, which is short, and then binds
it to a unique ID (note that this ID is chosen locally and is still
unique), the CNAME, sent in an RTCP packet.

So, a global unique ID distribution service is only needed for protocols
where the cost of transferring a 20 or so byte identifier is too high. I
somehow doubt this is a very large set of protocols.

-Jonathan R.


--
Jonathan D. Rosenberg                       200 Executive Drive
Chief Scientist                             Suite 120
dynamicsoft                                 West Orange, NJ 07052
jdrosen@dynamicsoft.com                     FAX:   (732) 741-4778
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com





From rem-conf Mon May 08 05:02:29 2000 
From rem-conf-request@es.net Mon May 08 05:02:28 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12omBw-0005fi-00; Mon, 8 May 2000 04:59:16 -0700
Received: from ausmtp02.au.ibm.com [202.135.136.105] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12omBt-0005fT-00; Mon, 8 May 2000 04:59:14 -0700
Received: from f03n07e.au.ibm.com 
	by ausmtp02.au.ibm.com (IBM AP 1.0) with ESMTP id VAA135870;
	Mon, 8 May 2000 21:53:06 +1000
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n07e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id VAA53000;
	Mon, 8 May 2000 21:58:05 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568D9.0041BBDF ; Mon, 8 May 2000 21:57:59 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: "Strahm, Bill" <bill.strahm@intel.com>
cc: "'Martin Mauve'" <mauve@pi4.informatik.uni-mannheim.de>, rem-conf@es.net
Message-ID: <CA2568D9.0041B857.00@d73mta05.au.ibm.com>
Date: Mon, 8 May 2000 14:10:23 +0530
Subject: Re: Unique SSRC IDs?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list



There are several problems with a centralized unique ID allocator:

- yet another point of failure (calls to mind Tanenbaum's dictum about
distributed systems which fail because a system fails that you didn't
even know existed)

- yet another target for a high-payoff denial-of-service attack (neat -
I can shut down the world's telephone, TV and radio by shutting down the
number server...)

- how do you keep me (and various copies of my little virus) from
sucking up all identifiers for some high-profile event?

- firewalls, NATs

- making sure that identifiers get returned - kind of a global DHCP
problem, just much worse

- fast joins for channel surfing add another step (and with channel
surfing, the number of requests to this server could be quite large)

Thus, I'd think that some test code that exercises the SSRC allocation
would be a far more useful contribution. If we ever want to get to
5-nines reliability, we can't keep adding centralized servers whose
failure brings down the whole phone system, radio and TV.
--
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs





From rem-conf Mon May 08 10:06:07 2000 
From rem-conf-request@es.net Mon May 08 10:06:06 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12oquW-00023k-00; Mon, 8 May 2000 10:01:36 -0700
Received: from odin.ietf.org (ietf.org) [132.151.1.176] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12oquU-00023Z-00; Mon, 8 May 2000 10:01:34 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12094;
	Mon, 8 May 2000 13:01:25 -0400 (EDT)
Message-Id: <200005081701.NAA12094@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>, iana@iana.org
Cc: Internet Architecture Board <iab@isi.edu>
Cc: rem-conf@es.net
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: RTP Payload Format for Real-Time Pointers to
	 Proposed Standard
Date: Mon, 08 May 2000 13:01:25 -0400
Sender: scoya@cnri.reston.va.us
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list



The IESG has approved the Internet-Draft 'RTP Payload Format for
Real-Time Pointers' <draft-ietf-avt-pointer-02.txt> as a Proposed
Standard.  This document is the product of the Audio/Video Transport
Working Group.  The IESG contact persons are Scott Bradner and Allison 
Mankin.
 
 
Technical Summary
 
 This document describes an RTP payload format for transporting the
 coordinates of a dynamic pointer such as might be used during a
 presentation.  The payload format is narrowly scoped; in particular,
 it is not meant to serve as a general mouse event transmission mechanism.

Working Group Summary

 The payload format was first presented at the Oslo IETF meeting. A number
 of changes were suggested at that meeting, and incorporated into the
 format, with the result of making it resolution independent and easier
 to synchronize with other media formats. There is now good WG consensus
 for publishing the document.

Protocol Quality

 Vern Paxson reviewed the spec for the IESG.

Note to RFC Editor:

Please replace the first occurance of the phrase "mouse buttons" with 
"pointer special effects flags, such as mouse buttons", and all
subsequent occurances of the phrase "mouse buttons" with "pointer flags".



From rem-conf Mon May 08 19:05:59 2000 
From rem-conf-request@es.net Mon May 08 19:05:56 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12ozGD-0007Zg-00; Mon, 8 May 2000 18:56:33 -0700
Received: from ns.r-net.sk [193.58.193.10] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12ozG9-0007ZW-00; Mon, 8 May 2000 18:56:30 -0700
Received: from jakab (Kosice55.r-net.sk [193.58.192.183])
	by NS.r-net.sk (8.9.3/8.9.3/Debian/GNU) with SMTP id DAA24318;
	Tue, 9 May 2000 03:54:42 +0200
Message-ID: <001201bfb95a$6f5b1aa0$b7c03ac1@jakab>
From: "jakab frantisek" <jakab@elfa.sk>
To: <j-fukuza@sdl.hitachi.co.jp>
Cc: <hgs@cs.columbia.edu>, <yoshida@sdl.hitachi.co.jp>, <alchiu@att.com>,
        <whay@dma.isg.mot.com>, <end2end-interest@isi.edu>, <int-serv@isi.edu>,
        <conf@colmar.colmar.uha.fr>, <rem-conf@es.net>, <qbone@internet2.edu>,
        <diffserv-interest@external.cisco.com>
Subject: Symposium  ATMTU 2000 in Slovakia
Date: Tue, 9 May 2000 02:21:16 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0A0F_01BFB95D.410F92E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_0A0F_01BFB95D.410F92E0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Accept my apologies if you receive multiple copies of this call. Please =
forward to your colleagues.
                =
___________________________________________________________
                      The deadline for abstract submission is quickly =
approaching (May)
               =
___________________________________________________________
=20
             THE SECOND INTERNATIONAL ATM TECHNOLOGY USERS SYMPOSIUM

                                                     ATMTU 2000
                                            13 - 15 September 2000
                                                   Kosice, Slovakia
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Dear colleagues,

Enclosed is a Call for Papers for a special issue of The ATMTU 2000 =
Symposium.=20

Detailed information about the Symposium and registration form 4you will =
 also fing
on the Symposium web site: http://www.elfa.sk.
The Symposium will be devoted to exchange of experiences in  =
implementation and
operation of the broad-band networks based on the ATM technology, =
presentation of=20
verified applications and presentation of the offered services. It will =
promote the ATM=20
technology transfer between the producers and customers - users of the =
ATM technology.
In framework of the Symposium we are preparing an exhibition of new =
products and=20
components of the ATM technology, applications, measurement equipment, =
etc.
The exhibition will be held in the same location as the Symposium. =
Companies and
institutions will have an opportunity to exhibit their products and =
advertise them among
the specialists and potential customers. Also, a special session will be =
devoted to=20
introducing their products and applications (short lectures in duration =
of approx. 10-20 min.).=20
In the plenary session we expect a presentation of the ambassadors of =
the ATM Forum
and also presentation of important business, academical and public =
representative.

Yours sincerely,

Organising Committee ATMTU 2000
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Scope of the Symposium
The Symposium will be devoted to the:

  a.. Presentation and sharing of experiences in the implementation and =
operation                                                                =
                                               of the broad-band =
networks based on ATM technologies=20
  b.. Presentation of verified ATM based applications=20
  c.. Presentation of the offered services=20
  d.. Perspectives of the ATM based technologies=20
Aims of the Symposium
  a.. To support dissemination of experiences pursuant to ATM technology =
utilisation=20
  b.. To get an extensive base of future customers and users=20
  c.. To support various forms of links among users and service =
providers.=20
The Symposium will be open for the exhibition of new ATM products and =
services.

Symposium Structure and Suggested Topics for Papers
Symposium will consist of plenary sessions and technical sessions.

Plenary Session I.(1st day of the Symposium)

Presentations of topics of general interest, e.g. building the =
"information highways"                                                   =
                                                          in the =
international context, strategic aims of governmental institutions etc.  =
                                                                         =
                                             =20

Plenary Session II. (2nd day of the Symposium)

Presentations of the world leading

  a.. vendors=20
  b.. operators=20
  c.. investors=20
  d.. integrators and=20
  e.. users of the ATM technology.=20
Presentations of the implemented pilot projects and services in the ATM =
based networks.

Technical Sessions:

Technical sessions will be held on the second day of the Symposium, in =
parallel                                                                 =
                                               with the Plenary Session =
II. It is proposed for general audience and specialists from             =
                                                                         =
              research, industry and academic institutions, intending to =
present their experiences                                                =
                                                            and =
recommendations from the field of ATM technology utilisation. The =
session will                                                             =
                                                cover the following =
topics:=20

  a.. Comparison of ATM technologies from the view of their =
implementation, protection                                               =
                                                          of investments =
and further development=20
  b.. Standardisation of the ATM technology=20
  c.. Multimedia applications (videoconferencing etc.)=20
  d.. Broadband services and quality of services=20
  e.. Broadband networks management=20
  f.. Security in the broadband networks=20
  g.. Future of the ATM technology=20
Exhibition
The Symposium will promote ATM technology transfer between producers and =
users.                                                                   =
                             Producers and institutions will have the =
opportunity to present new products, components,                         =
                                                                    =
applications, measurement equipment, etc. The exhibition will be held on =
same premises                                                            =
                                            as the Symposium.

Symposium Languages
Slovak, Czech and English are the official languages of the symposium.=20

Symposium Proceedings
The proceedings will be published in time for the Symposium. Each =
registered participant                                                   =
                                                     will receive the =
proceedings in both printed and electronic forms (CD).

Contributions
Authors intending to submit a paper are welcome to mail in 1 page:

  a.. (approx. 300 words) of abstract on A4 standard sheet=20
  b.. borders 2,5 cm=20
  c.. Times New Roman or similar font, 12 p.,=20
  d.. in one of the symposium languages.=20
The abstract should be headed as follows:

  a.. Title of the paper=20
  b.. Author's name(s)=20
  c.. Affiliation=20
  d.. Mailing address.=20
The deadline is 10 of May 2000.=20

If you need extension for few days,  please let us know in advance -     =
                                                                         =
                       we will try to accomodate such requests.

The Organising Committee will also accept abstracts processed by the "MS =
Word"                                                                    =
                                        text editor and mailed to the =
Organising Committee by Internet. Authors of papers,                     =
                                                                         =
           selected for the presentation, will be mailed a pack with =
instructions for full papers.                                            =
                                                                 .

Deadlines
  1.. Acceptance of registration forms and abstracts and/or proposals to =
exhibition

  10 May 2000


  2.. Notification of acceptance, rules for full paper preparation and =
Second Call

  30 May 2000

  3.. Receipt of full paper and advanced registration

  15 August 2000

  4.. Last information and Final Program

  25 August 2000=20

 All deadlines are as per postmark.
Venue
Presentation hall and associated lecture halls at the Technical =
University,
Letna 9, Kosice, Slovak Republic.

Optional Agenda
On the third day of the Symposium one of the following optional programs =
will be at your disposal:

  a.. either technical program - visit to see the advanced ATM solutions =

  b.. or a trip, according to the choice (the High Tatras or Tokaj vine =
region) with the social program.=20
Registration Fee
It is supposed that the registration fee will be in range of 290 USD. =
The PhD. students presenting                                             =
                                           their contributions will have =
30 % discount from the registration fee.

The details will be announced in the Second Announcement.

Information about Kosice
Kosice, the metropolis of Eastern Slovakia, has more than 750 years rich =
history. It has always been                                              =
                                          a town of both national and =
international significance. Kosice belongs to the most beautiful and =
lovely                                                                   =
                 cities in Slovakia. There is an attractive, recently =
renewed historical centre. Towering over the centre                      =
                                                                  is the =
gothic Cathedral of St. Elizabeth, completed in 1508.

In last decades Kosice quickly expanded and at the present there are =
nearly 250 thousands of inhabitants.                                     =
                                           It is the second largest city =
in the Slovak Republic (after the capital - Bratislava) and is the =
centre of the                                                            =
               industrial activities, business and commerce, =
communications, civic admi-nistration, shopping, cultural                =
                                                                    and =
leisure activities for the whole Eastern Slovakia.=20

The first in-town university was established in 1657. At present there =
are five universities.                                                   =
                                          Technical University of =
Kosice, established in 1952, with over 11 500 students, consists of =
eight faculties.                                                         =
                    The Faculty of Electrical Engineering and =
Informatics, established in 1969, is the leading institution of          =
                                                                      =
higher education in fields of electrical engineering and information =
technologies. The education programs                                     =
                                            are firmly linked with =
research and scientific activities.

Address and Contact
ATMTU 2000 Symposium Secretariat
Martina Atanasova
elfa, s.r.o.
Letna 9
042 00 Kosice, Slovak Republic
Tel.:+421-95-62 538 39, 62 53202
Fax: +421-95-62 532 00
E-mail: elfa@elfa.sk, www.elfa.sk


------=_NextPart_000_0A0F_01BFB95D.410F92E0
Content-Type: text/html;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-2" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV style=3D"FONT: 10pt arial"></DIV>
<DIV align=3Djustify><FONT size=3D2><SPAN =
class=3D360575917-31032000><FONT=20
color=3D#0000ff face=3DArial>Accept my apologies if you receive multiple =
copies of=20
this call.</FONT></SPAN><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
class=3D360575917-31032000><SPAN class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000> </SPAN>Please forward to your=20
colleagues.</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D360575917-31032000><SPAN class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
___________________________________________________________</SPAN></SPAN>=
</SPAN></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D360575917-31032000><SPAN class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
The deadline for abstract&nbsp;submission is quickly approaching=20
(May)</SPAN></SPAN></SPAN></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff><FONT face=3DArial><FONT =
color=3D#0000ff=20
face=3DArial size=3D2><SPAN class=3D360575917-31032000><SPAN=20
class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
___________________________________________________________</SPAN></SPAN>=
</SPAN></FONT></FONT></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial><FONT=20
size=3D2></FONT></FONT>&nbsp;</DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
THE SECOND&nbsp;INTERNATIONAL ATM TECHNOLOGY USERS=20
SYMPOSIUM<BR></DIV></FONT></FONT>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</FONT><FONT color=3D#0000ff face=3DArial size=3D2>ATMTU =
2000</FONT></DIV>
<DIV align=3Djustify><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
13 - 15 September 2000</FONT></DIV>
<DIV align=3Djustify><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;Kosice,=20
Slovakia</FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff><FONT face=3DArial =
size=3D2><SPAN=20
class=3D370211018-31032000>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D</SPAN></FONT></FONT></DIV>
<P align=3Djustify><FONT size=3D2>Dear colleagues,</FONT></P>
<P align=3Djustify><FONT size=3D2>Enclosed is a Call for Papers for a =
special issue=20
of The&nbsp;ATMTU 2000 Symposium. </FONT></P>
<DIV align=3Djustify><FONT size=3D2>Detailed information about the =
Symposium and=20
registration form 4you will&nbsp; also fing</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>on the Symposium web site: <A=20
href=3D"http://www.elfa.sk">http://www.elfa.sk</A>.<BR>The Symposium =
will be=20
devoted to exchange of experiences in&nbsp; implementation =
and</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>operation of the&nbsp;broad-band =
networks based=20
on the ATM technology, presentation of </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>verified applications and =
presentation of the=20
offered services. It will promote the ATM </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>technology transfer between the =
producers and=20
customers - users of the ATM technology.</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>In framework of the Symposium we are =
preparing=20
an exhibition of new products and </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>components of the ATM technology, =
applications,=20
measurement equipment, etc.</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>The exhibition will be held in the =
same location=20
as the Symposium. Companies and<BR>institutions will have an opportunity =
to=20
exhibit their products and advertise them among</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>the specialists and potential =
customers. Also, a=20
special session will be devoted to </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>introducing their products and =
applications=20
(short lectures in duration of approx. 10-20 min.). </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>In the plenary session we expect a =
presentation=20
of the ambassadors of the ATM Forum</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>and also presentation of important =
business,=20
academical and public representative.</FONT></DIV>
<DIV align=3Djustify>&nbsp;</DIV>
<DIV align=3Djustify><FONT size=3D2>Yours sincerely,<BR><BR>Organising =
Committee=20
ATMTU=20
2000<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT></DIV><FONT=20
size=3D2><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica" =
size=3D2>
<DIV>&nbsp;</DIV><STRONG>
<DIV></FONT><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica" =
size=3D2>Scope of=20
the Symposium</FONT></STRONG></DIV>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The Symposium will =
be devoted to=20
the:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentation and =
sharing of=20
  experiences in the implementation and operation</FONT><FONT=20
  face=3D"Arial, Vedana, Helvetica"=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; of=20
  the broad-band networks based on ATM technologies</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentation of =
verified ATM=20
  based applications</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentation of =
the offered=20
  services</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Perspectives of =
the ATM based=20
  technologies</FONT> </LI></UL>
<H3><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica" =
size=3D2>Aims of the=20
Symposium</FONT></H3>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>To support =
dissemination of=20
  experiences pursuant to ATM technology utilisation</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>To get an =
extensive base of=20
  future customers and users</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>To support =
various forms of=20
  links among users and service providers.</FONT> </LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The Symposium will =
be open for=20
the exhibition of new ATM products and services.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Symposium =
Structure and=20
Suggested Topics for Papers</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Symposium will =
consist of=20
plenary sessions and technical sessions.</FONT></P>
<P><I><B><FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2>Plenary=20
Session I.</FONT></B></I><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>(1st day=20
of the Symposium)</FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentations of =
topics of=20
general interest, e.g. building the <B>"information=20
highways"</B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
in the international context, strategic aims of governmental =
institutions=20
etc.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</FONT></P>
<P><I><B><FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2>Plenary=20
Session II.</FONT></B></I> <FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>(2nd day=20
of the Symposium)</FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentations of the =
world=20
leading</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>vendors</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>operators</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>investors</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>integrators =
and</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>users of the ATM=20
  technology.</FONT> </LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentations of the =
implemented=20
pilot projects and services in the ATM based networks.</FONT></P>
<P><FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2><B><I>Technical=20
Sessions:</I></B></FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Technical sessions =
will be held=20
on the second day of the Symposium, in parallel&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; with the <I><A=20
href=3D"http://www.elfa.sk/atm2k/uk/ps-2.htm">Plenary Session =
II.</A></I> It is=20
proposed for general audience and specialists from&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
research, industry and academic institutions, intending to present their =

experiences&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; and=20
recommendations from the field of ATM technology utilisation. The =
session will=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; cover the =
following=20
topics:&nbsp;</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Comparison of ATM =

  technologies from the view of their implementation, protection=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; of investments and further=20
  development</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Standardisation =
of the ATM=20
  technology</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Multimedia =
applications=20
  (videoconferencing etc.)</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Broadband =
services and=20
  quality of services</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Broadband =
networks=20
  management</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Security in the =
broadband=20
  networks</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Future of the ATM =

  technology</FONT> </LI></UL>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, =
Helvetica">Exhibition</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The Symposium will =
promote ATM=20
technology transfer between producers and users.&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Producers and=20
institutions will have the opportunity to present new products, =
components,=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; applications,=20
measurement equipment, etc. The exhibition will be held on same=20
premises&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; </FONT><FONT face=3D"Arial, Vedana, Helvetica"=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
as the Symposium.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Symposium=20
Languages</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Slovak, Czech and =
English are=20
the official languages of the symposium. </FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Symposium=20
Proceedings</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The proceedings will =
be=20
published in time for the Symposium. Each registered=20
participant&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; will receive =
the=20
proceedings in both printed and electronic forms (CD).</FONT></P>
<H5><FONT color=3D#ff0000=20
face=3D"Arial, Vedana, Helvetica">Contributions</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Authors intending to =
submit a=20
paper are welcome to mail in 1 page:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>(approx. 300 =
words) of=20
  abstract on A4 standard sheet</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>borders 2,5 =
cm</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Times New Roman =
or similar=20
  font, 12 p.,</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>in one of the =
symposium=20
  languages.</FONT> </LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The abstract should =
be headed as=20
follows:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Title of the =
paper</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Author's =
name(s)</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>Affiliation</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Mailing =
address.</FONT>=20
</LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The deadline is =
<STRONG><EM>10=20
of May 2000</EM></STRONG>. </FONT></P>
<P><STRONG><FONT face=3D"Arial, Vedana, Helvetica" size=3D3>If you need =
extension=20
for few days,&nbsp; please let us know in advance - &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; we=20
will&nbsp;try to accomodate&nbsp;such =
requests.<BR><BR></FONT></STRONG><FONT=20
face=3D"Arial, Vedana, Helvetica" size=3D2>The Organising Committee will =
also accept=20
abstracts processed by the <B><I>"MS Word"&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; </I></B>text editor and mailed to the Organising =
Committee by=20
Internet. Authors of papers, &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
selected for the presentation, will be mailed a pack with instructions =
for full=20
papers.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, =
Helvetica">Deadlines</FONT></H5>
<OL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Acceptance of =
registration=20
  forms and abstracts and/or proposals to exhibition<BR><BR><B>10 May=20
  2000</B><BR><BR></FONT>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Notification of =
acceptance,=20
  rules for full paper preparation and Second Call<BR><BR><B>30 May=20
  2000</B><BR></FONT>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Receipt of full =
paper and=20
  advanced registration<BR><BR><B>15 August 2000</B><BR></FONT>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Last information =
and Final=20
  Program<BR><BR><B>25 August 2000</B></FONT>&nbsp;</LI></OL>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;<FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2><B><I>All=20
deadlines are as per postmark.</I></B></FONT></DIV>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, =
Helvetica">Venue</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>Presentation&nbsp;hall and=20
associated lecture halls at the Technical University,<BR>Letna 9, =
Kosice, Slovak=20
Republic.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Optional=20
Agenda</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>On the third day of =
the=20
Symposium one of the following optional programs will be at your=20
disposal:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>either technical =
program -=20
  visit to see the advanced ATM solutions</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>or a trip, =
according to the=20
  choice (the High Tatras or Tokaj vine region) with the social program. =

  </FONT></LI></UL>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Registration =

Fee</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>It is supposed that =
the=20
registration fee will be in range of 290 USD. The PhD. students=20
presenting&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; their =
contributions=20
will have 30 % discount from the registration fee.</FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The details will be =
announced in=20
the Second Announcement.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Information =
about=20
Kosice</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Kosice, the =
metropolis of=20
Eastern Slovakia, has more than 750 years rich history. It has always=20
been&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
a town of both national and international significance. Kosice belongs =
to the=20
most beautiful and lovely&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
cities in=20
Slovakia. There is an attractive, recently renewed historical centre. =
Towering=20
over the centre&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; is the gothic =
Cathedral=20
of St. Elizabeth, completed in 1508.<BR><BR>In last decades Kosice =
quickly=20
expanded and at the present there are nearly 250 thousands of=20
inhabitants.&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; It is the second largest city in the Slovak Republic =
(after=20
the capital - Bratislava) and is the centre of the&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; industrial activities, business =
and=20
commerce, communications, civic admi-nistration, shopping,=20
cultural&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; and leisure activities for the =
whole=20
Eastern Slovakia. <BR><BR>The first in-town university was established =
in 1657.=20
At present there are five universities. &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; Technical University of Kosice, established in 1952, =
with=20
over 11 500 students, consists of eight faculties. &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; The Faculty of Electrical =
Engineering and=20
Informatics, established in 1969, is the leading institution=20
of&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
higher education in fields of electrical engineering and information=20
technologies. The education programs &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; are firmly linked with research =
and=20
scientific activities.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Address and=20
Contact</FONT></H5>
<DIV><FONT face=3D"Arial, Vedana, Helvetica" size=3D2><STRONG><U>ATMTU =
2000=20
Symposium Secretariat</U><BR></STRONG>Martina Atanasova</FONT></DIV>
<DIV><FONT face=3D"Arial, Vedana, Helvetica" size=3D2><STRONG>elfa,=20
s.r.o.</STRONG><BR>Letna 9<BR>042 00 Kosice, Slovak =
Republic</FONT></DIV>
<P><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2><B>Tel.:</B>+421-95-62 538=20
39,&nbsp;62 53202<BR><B>Fax:</B> +421-95-62 532 00<BR><B>E-mail:</B> <A=20
href=3D"mailto:elfa@elfa.sk">elfa@elfa.sk</A><STRONG>, <A=20
href=3D"http://www.elfa.sk">www.elfa.sk</A></STRONG></FONT></P></FONT></B=
ODY></HTML>

------=_NextPart_000_0A0F_01BFB95D.410F92E0--




From rem-conf Mon May 08 19:06:18 2000 
From rem-conf-request@es.net Mon May 08 19:06:17 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12ozJs-0007af-00; Mon, 8 May 2000 19:00:20 -0700
Received: from ns.r-net.sk [193.58.193.10] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12ozJp-0007aV-00; Mon, 8 May 2000 19:00:18 -0700
Received: from jakab (Kosice55.r-net.sk [193.58.192.183])
	by NS.r-net.sk (8.9.3/8.9.3/Debian/GNU) with SMTP id DAA24341;
	Tue, 9 May 2000 03:55:24 +0200
Message-ID: <001601bfb95a$91e59280$b7c03ac1@jakab>
From: "jakab frantisek" <jakab@elfa.sk>
To: <atm2000@ccrle.nec.de>
Cc: <Undisclosed.Recipients@leonis.nus.edu.sg>,
        =?iso-8859-2?B?UmVu6SBTYWxmaWNr/Q==?= <rene_salficky@lion.cz>,
        <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>,
        <dbworld@cs.wisc.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>,
        <kia@usl.edu>, <multicomm@cc.bellcore.com>, <osimcast@bbn.com>,
        <performance@haven.epm.ornl.gov>, <rem-conf@es.net>, <reres@laas.fr>,
        <C.GHAOUI@livjm.ac.uk>
Subject: ATMTU 2000 
Date: Tue, 9 May 2000 02:40:02 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0B3D_01BFB95F.E0741980"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_0B3D_01BFB95F.E0741980
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Accept my apologies if you receive multiple copies of this call. Please =
forward to your colleagues.
                =
___________________________________________________________
                      The deadline for abstract submission is quickly =
approaching (May)
               =
___________________________________________________________
=20
             THE SECOND INTERNATIONAL ATM TECHNOLOGY USERS SYMPOSIUM

                                                     ATMTU 2000
                                            13 - 15 September 2000
                                                   Kosice, Slovakia
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Dear colleagues,

Enclosed is a Call for Papers for a special issue of The ATMTU 2000 =
Symposium.=20

Detailed information about the Symposium and registration form 4you will =
 also fing
on the Symposium web site: http://www.elfa.sk.
The Symposium will be devoted to exchange of experiences in  =
implementation and
operation of the broad-band networks based on the ATM technology, =
presentation of=20
verified applications and presentation of the offered services. It will =
promote the ATM=20
technology transfer between the producers and customers - users of the =
ATM technology.
In framework of the Symposium we are preparing an exhibition of new =
products and=20
components of the ATM technology, applications, measurement equipment, =
etc.
The exhibition will be held in the same location as the Symposium. =
Companies and
institutions will have an opportunity to exhibit their products and =
advertise them among
the specialists and potential customers. Also, a special session will be =
devoted to=20
introducing their products and applications (short lectures in duration =
of approx. 10-20 min.).=20
In the plenary session we expect a presentation of the ambassadors of =
the ATM Forum
and also presentation of important business, academical and public =
representative.

Yours sincerely,

Organising Committee ATMTU 2000
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Scope of the Symposium
The Symposium will be devoted to the:

  a.. Presentation and sharing of experiences in the implementation and =
operation                                                                =
                                               of the broad-band =
networks based on ATM technologies=20
  b.. Presentation of verified ATM based applications=20
  c.. Presentation of the offered services=20
  d.. Perspectives of the ATM based technologies=20
Aims of the Symposium
  a.. To support dissemination of experiences pursuant to ATM technology =
utilisation=20
  b.. To get an extensive base of future customers and users=20
  c.. To support various forms of links among users and service =
providers.=20
The Symposium will be open for the exhibition of new ATM products and =
services.

Symposium Structure and Suggested Topics for Papers
Symposium will consist of plenary sessions and technical sessions.

Plenary Session I.(1st day of the Symposium)

Presentations of topics of general interest, e.g. building the =
"information highways"                                                   =
                                                          in the =
international context, strategic aims of governmental institutions etc.  =
                                                                         =
                                             =20

Plenary Session II. (2nd day of the Symposium)

Presentations of the world leading

  a.. vendors=20
  b.. operators=20
  c.. investors=20
  d.. integrators and=20
  e.. users of the ATM technology.=20
Presentations of the implemented pilot projects and services in the ATM =
based networks.

Technical Sessions:

Technical sessions will be held on the second day of the Symposium, in =
parallel                                                                 =
                                               with the Plenary Session =
II. It is proposed for general audience and specialists from             =
                                                                         =
              research, industry and academic institutions, intending to =
present their experiences                                                =
                                                            and =
recommendations from the field of ATM technology utilisation. The =
session will                                                             =
                                                cover the following =
topics:=20

  a.. Comparison of ATM technologies from the view of their =
implementation, protection                                               =
                                                          of investments =
and further development=20
  b.. Standardisation of the ATM technology=20
  c.. Multimedia applications (videoconferencing etc.)=20
  d.. Broadband services and quality of services=20
  e.. Broadband networks management=20
  f.. Security in the broadband networks=20
  g.. Future of the ATM technology=20
Exhibition
The Symposium will promote ATM technology transfer between producers and =
users.                                                                   =
                             Producers and institutions will have the =
opportunity to present new products, components,                         =
                                                                    =
applications, measurement equipment, etc. The exhibition will be held on =
same premises                                                            =
                                            as the Symposium.

Symposium Languages
Slovak, Czech and English are the official languages of the symposium.=20

Symposium Proceedings
The proceedings will be published in time for the Symposium. Each =
registered participant                                                   =
                                                     will receive the =
proceedings in both printed and electronic forms (CD).

Contributions
Authors intending to submit a paper are welcome to mail in 1 page:

  a.. (approx. 300 words) of abstract on A4 standard sheet=20
  b.. borders 2,5 cm=20
  c.. Times New Roman or similar font, 12 p.,=20
  d.. in one of the symposium languages.=20
The abstract should be headed as follows:

  a.. Title of the paper=20
  b.. Author's name(s)=20
  c.. Affiliation=20
  d.. Mailing address.=20
The deadline is 10 of May 2000.=20

If you need extension for few days,  please let us know in advance -     =
                                                                         =
                       we will try to accomodate such requests.

The Organising Committee will also accept abstracts processed by the "MS =
Word"                                                                    =
                                        text editor and mailed to the =
Organising Committee by Internet. Authors of papers,                     =
                                                                         =
           selected for the presentation, will be mailed a pack with =
instructions for full papers.                                            =
                                                                 .

Deadlines
  1.. Acceptance of registration forms and abstracts and/or proposals to =
exhibition

  10 May 2000


  2.. Notification of acceptance, rules for full paper preparation and =
Second Call

  30 May 2000

  3.. Receipt of full paper and advanced registration

  15 August 2000

  4.. Last information and Final Program

  25 August 2000=20

 All deadlines are as per postmark.
Venue
Presentation hall and associated lecture halls at the Technical =
University,
Letna 9, Kosice, Slovak Republic.

Optional Agenda
On the third day of the Symposium one of the following optional programs =
will be at your disposal:

  a.. either technical program - visit to see the advanced ATM solutions =

  b.. or a trip, according to the choice (the High Tatras or Tokaj vine =
region) with the social program.=20
Registration Fee
It is supposed that the registration fee will be in range of 290 USD. =
The PhD. students presenting                                             =
                                           their contributions will have =
30 % discount from the registration fee.

The details will be announced in the Second Announcement.

Information about Kosice
Kosice, the metropolis of Eastern Slovakia, has more than 750 years rich =
history. It has always been                                              =
                                          a town of both national and =
international significance. Kosice belongs to the most beautiful and =
lovely                                                                   =
                 cities in Slovakia. There is an attractive, recently =
renewed historical centre. Towering over the centre                      =
                                                                  is the =
gothic Cathedral of St. Elizabeth, completed in 1508.

In last decades Kosice quickly expanded and at the present there are =
nearly 250 thousands of inhabitants.                                     =
                                           It is the second largest city =
in the Slovak Republic (after the capital - Bratislava) and is the =
centre of the                                                            =
               industrial activities, business and commerce, =
communications, civic admi-nistration, shopping, cultural                =
                                                                    and =
leisure activities for the whole Eastern Slovakia.=20

The first in-town university was established in 1657. At present there =
are five universities.                                                   =
                                          Technical University of =
Kosice, established in 1952, with over 11 500 students, consists of =
eight faculties.                                                         =
                    The Faculty of Electrical Engineering and =
Informatics, established in 1969, is the leading institution of          =
                                                                      =
higher education in fields of electrical engineering and information =
technologies. The education programs                                     =
                                            are firmly linked with =
research and scientific activities.

Address and Contact
ATMTU 2000 Symposium Secretariat
Martina Atanasova
elfa, s.r.o.
Letna 9
042 00 Kosice, Slovak Republic
Tel.:+421-95-62 538 39, 62 53202
Fax: +421-95-62 532 00
E-mail: elfa@elfa.sk, www.elfa.sk


------=_NextPart_000_0B3D_01BFB95F.E0741980
Content-Type: text/html;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-2" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Djustify><FONT size=3D2><SPAN =
class=3D360575917-31032000><FONT=20
color=3D#0000ff face=3DArial>Accept my apologies if you receive multiple =
copies of=20
this call.</FONT></SPAN><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
class=3D360575917-31032000><SPAN class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000> </SPAN>Please forward to your=20
colleagues.</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D360575917-31032000><SPAN class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
___________________________________________________________</SPAN></SPAN>=
</SPAN></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D360575917-31032000><SPAN class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
The deadline for abstract&nbsp;submission is quickly approaching=20
(May)</SPAN></SPAN></SPAN></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff><FONT face=3DArial><FONT =
color=3D#0000ff=20
face=3DArial size=3D2><SPAN class=3D360575917-31032000><SPAN=20
class=3D370211018-31032000><SPAN=20
class=3D800540809-24042000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
___________________________________________________________</SPAN></SPAN>=
</SPAN></FONT></FONT></FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial><FONT=20
size=3D2></FONT></FONT>&nbsp;</DIV>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
THE SECOND&nbsp;INTERNATIONAL ATM TECHNOLOGY USERS=20
SYMPOSIUM<BR></DIV></FONT></FONT>
<DIV align=3Djustify><FONT color=3D#0000ff face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</FONT><FONT color=3D#0000ff face=3DArial size=3D2>ATMTU =
2000</FONT></DIV>
<DIV align=3Djustify><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
13 - 15 September 2000</FONT></DIV>
<DIV align=3Djustify><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;Kosice,=20
Slovakia</FONT></DIV>
<DIV align=3Djustify><FONT color=3D#0000ff><FONT face=3DArial =
size=3D2><SPAN=20
class=3D370211018-31032000>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D</SPAN></FONT></FONT></DIV>
<P align=3Djustify><FONT size=3D2>Dear colleagues,</FONT></P>
<P align=3Djustify><FONT size=3D2>Enclosed is a Call for Papers for a =
special issue=20
of The&nbsp;ATMTU 2000 Symposium. </FONT></P>
<DIV align=3Djustify><FONT size=3D2>Detailed information about the =
Symposium and=20
registration form 4you will&nbsp; also fing</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>on the Symposium web site: <A=20
href=3D"http://www.elfa.sk">http://www.elfa.sk</A>.<BR>The Symposium =
will be=20
devoted to exchange of experiences in&nbsp; implementation =
and</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>operation of the&nbsp;broad-band =
networks based=20
on the ATM technology, presentation of </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>verified applications and =
presentation of the=20
offered services. It will promote the ATM </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>technology transfer between the =
producers and=20
customers - users of the ATM technology.</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>In framework of the Symposium we are =
preparing=20
an exhibition of new products and </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>components of the ATM technology, =
applications,=20
measurement equipment, etc.</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>The exhibition will be held in the =
same location=20
as the Symposium. Companies and<BR>institutions will have an opportunity =
to=20
exhibit their products and advertise them among</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>the specialists and potential =
customers. Also, a=20
special session will be devoted to </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>introducing their products and =
applications=20
(short lectures in duration of approx. 10-20 min.). </FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>In the plenary session we expect a =
presentation=20
of the ambassadors of the ATM Forum</FONT></DIV>
<DIV align=3Djustify><FONT size=3D2>and also presentation of important =
business,=20
academical and public representative.</FONT></DIV>
<DIV align=3Djustify>&nbsp;</DIV>
<DIV align=3Djustify><FONT size=3D2>Yours sincerely,<BR><BR>Organising =
Committee=20
ATMTU=20
2000<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT></DIV><FONT=20
size=3D2><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica" =
size=3D2>
<DIV>&nbsp;</DIV><STRONG>
<DIV></FONT><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica" =
size=3D2>Scope of=20
the Symposium</FONT></STRONG></DIV>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The Symposium will =
be devoted to=20
the:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentation and =
sharing of=20
  experiences in the implementation and operation</FONT><FONT=20
  face=3D"Arial, Vedana, Helvetica"=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; of=20
  the broad-band networks based on ATM technologies</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentation of =
verified ATM=20
  based applications</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentation of =
the offered=20
  services</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Perspectives of =
the ATM based=20
  technologies</FONT> </LI></UL>
<H3><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica" =
size=3D2>Aims of the=20
Symposium</FONT></H3>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>To support =
dissemination of=20
  experiences pursuant to ATM technology utilisation</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>To get an =
extensive base of=20
  future customers and users</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>To support =
various forms of=20
  links among users and service providers.</FONT> </LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The Symposium will =
be open for=20
the exhibition of new ATM products and services.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Symposium =
Structure and=20
Suggested Topics for Papers</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Symposium will =
consist of=20
plenary sessions and technical sessions.</FONT></P>
<P><I><B><FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2>Plenary=20
Session I.</FONT></B></I><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>(1st day=20
of the Symposium)</FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentations of =
topics of=20
general interest, e.g. building the <B>"information=20
highways"</B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
in the international context, strategic aims of governmental =
institutions=20
etc.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</FONT></P>
<P><I><B><FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2>Plenary=20
Session II.</FONT></B></I> <FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>(2nd day=20
of the Symposium)</FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentations of the =
world=20
leading</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>vendors</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>operators</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>investors</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>integrators =
and</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>users of the ATM=20
  technology.</FONT> </LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Presentations of the =
implemented=20
pilot projects and services in the ATM based networks.</FONT></P>
<P><FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2><B><I>Technical=20
Sessions:</I></B></FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Technical sessions =
will be held=20
on the second day of the Symposium, in parallel&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; with the <I><A=20
href=3D"http://www.elfa.sk/atm2k/uk/ps-2.htm">Plenary Session =
II.</A></I> It is=20
proposed for general audience and specialists from&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
research, industry and academic institutions, intending to present their =

experiences&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; and=20
recommendations from the field of ATM technology utilisation. The =
session will=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; cover the =
following=20
topics:&nbsp;</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Comparison of ATM =

  technologies from the view of their implementation, protection=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; of investments and further=20
  development</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Standardisation =
of the ATM=20
  technology</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Multimedia =
applications=20
  (videoconferencing etc.)</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Broadband =
services and=20
  quality of services</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Broadband =
networks=20
  management</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Security in the =
broadband=20
  networks</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Future of the ATM =

  technology</FONT> </LI></UL>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, =
Helvetica">Exhibition</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The Symposium will =
promote ATM=20
technology transfer between producers and users.&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Producers and=20
institutions will have the opportunity to present new products, =
components,=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; applications,=20
measurement equipment, etc. The exhibition will be held on same=20
premises&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; </FONT><FONT face=3D"Arial, Vedana, Helvetica"=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
as the Symposium.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Symposium=20
Languages</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Slovak, Czech and =
English are=20
the official languages of the symposium. </FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Symposium=20
Proceedings</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The proceedings will =
be=20
published in time for the Symposium. Each registered=20
participant&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; will receive =
the=20
proceedings in both printed and electronic forms (CD).</FONT></P>
<H5><FONT color=3D#ff0000=20
face=3D"Arial, Vedana, Helvetica">Contributions</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Authors intending to =
submit a=20
paper are welcome to mail in 1 page:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>(approx. 300 =
words) of=20
  abstract on A4 standard sheet</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>borders 2,5 =
cm</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Times New Roman =
or similar=20
  font, 12 p.,</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>in one of the =
symposium=20
  languages.</FONT> </LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The abstract should =
be headed as=20
follows:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Title of the =
paper</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Author's =
name(s)</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>Affiliation</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Mailing =
address.</FONT>=20
</LI></UL>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The deadline is =
<STRONG><EM>10=20
of May 2000</EM></STRONG>. </FONT></P>
<P><STRONG><FONT face=3D"Arial, Vedana, Helvetica" size=3D3>If you need =
extension=20
for few days,&nbsp; please let us know in advance - &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; we=20
will&nbsp;try to accomodate&nbsp;such =
requests.<BR><BR></FONT></STRONG><FONT=20
face=3D"Arial, Vedana, Helvetica" size=3D2>The Organising Committee will =
also accept=20
abstracts processed by the <B><I>"MS Word"&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; </I></B>text editor and mailed to the Organising =
Committee by=20
Internet. Authors of papers, &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
selected for the presentation, will be mailed a pack with instructions =
for full=20
papers.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, =
Helvetica">Deadlines</FONT></H5>
<OL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Acceptance of =
registration=20
  forms and abstracts and/or proposals to exhibition<BR><BR><B>10 May=20
  2000</B><BR><BR></FONT>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Notification of =
acceptance,=20
  rules for full paper preparation and Second Call<BR><BR><B>30 May=20
  2000</B><BR></FONT>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Receipt of full =
paper and=20
  advanced registration<BR><BR><B>15 August 2000</B><BR></FONT>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Last information =
and Final=20
  Program<BR><BR><B>25 August 2000</B></FONT>&nbsp;</LI></OL>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;<FONT color=3D#0000ff face=3D"Arial, Vedana, Helvetica" =
size=3D2><B><I>All=20
deadlines are as per postmark.</I></B></FONT></DIV>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, =
Helvetica">Venue</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2>Presentation&nbsp;hall and=20
associated lecture halls at the Technical University,<BR>Letna 9, =
Kosice, Slovak=20
Republic.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Optional=20
Agenda</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>On the third day of =
the=20
Symposium one of the following optional programs will be at your=20
disposal:</FONT></P>
<UL>
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>either technical =
program -=20
  visit to see the advanced ATM solutions</FONT>=20
  <LI><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>or a trip, =
according to the=20
  choice (the High Tatras or Tokaj vine region) with the social program. =

  </FONT></LI></UL>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Registration =

Fee</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>It is supposed that =
the=20
registration fee will be in range of 290 USD. The PhD. students=20
presenting&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; their =
contributions=20
will have 30 % discount from the registration fee.</FONT></P>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>The details will be =
announced in=20
the Second Announcement.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Information =
about=20
Kosice</FONT></H5>
<P><FONT face=3D"Arial, Vedana, Helvetica" size=3D2>Kosice, the =
metropolis of=20
Eastern Slovakia, has more than 750 years rich history. It has always=20
been&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
a town of both national and international significance. Kosice belongs =
to the=20
most beautiful and lovely&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
cities in=20
Slovakia. There is an attractive, recently renewed historical centre. =
Towering=20
over the centre&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; is the gothic =
Cathedral=20
of St. Elizabeth, completed in 1508.<BR><BR>In last decades Kosice =
quickly=20
expanded and at the present there are nearly 250 thousands of=20
inhabitants.&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; It is the second largest city in the Slovak Republic =
(after=20
the capital - Bratislava) and is the centre of the&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; industrial activities, business =
and=20
commerce, communications, civic admi-nistration, shopping,=20
cultural&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; and leisure activities for the =
whole=20
Eastern Slovakia. <BR><BR>The first in-town university was established =
in 1657.=20
At present there are five universities. &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; Technical University of Kosice, established in 1952, =
with=20
over 11 500 students, consists of eight faculties. &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; The Faculty of Electrical =
Engineering and=20
Informatics, established in 1969, is the leading institution=20
of&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
higher education in fields of electrical engineering and information=20
technologies. The education programs &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; are firmly linked with research =
and=20
scientific activities.</FONT></P>
<H5><FONT color=3D#ff0000 face=3D"Arial, Vedana, Helvetica">Address and=20
Contact</FONT></H5>
<DIV><FONT face=3D"Arial, Vedana, Helvetica" size=3D2><STRONG><U>ATMTU =
2000=20
Symposium Secretariat</U><BR></STRONG>Martina Atanasova</FONT></DIV>
<DIV><FONT face=3D"Arial, Vedana, Helvetica" size=3D2><STRONG>elfa,=20
s.r.o.</STRONG><BR>Letna 9<BR>042 00 Kosice, Slovak =
Republic</FONT></DIV>
<P><FONT face=3D"Arial, Vedana, Helvetica" =
size=3D2><B>Tel.:</B>+421-95-62 538=20
39,&nbsp;62 53202<BR><B>Fax:</B> +421-95-62 532 00<BR><B>E-mail:</B> <A=20
href=3D"mailto:elfa@elfa.sk">elfa@elfa.sk</A><STRONG>, <A=20
href=3D"http://www.elfa.sk">www.elfa.sk</A></STRONG></FONT></P></FONT></B=
ODY></HTML>

------=_NextPart_000_0B3D_01BFB95F.E0741980--




From rem-conf Mon May 08 19:24:04 2000 
From rem-conf-request@es.net Mon May 08 19:24:02 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12ozal-0000mp-00; Mon, 8 May 2000 19:17:47 -0700
Received: from dialup-63.208.206.217.tampa1.level3.net (63.208.206.217) [63.208.206.217] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12ozaW-0000kh-00; Mon, 8 May 2000 19:17:34 -0700
From:     JLB@CUSTOMERS
To:       rem-conf@KFIL.es.net
Subject:  Don't Delete, Read This -FBOL
X-Reply-To:  4X4@england.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <E12ozaW-0000kh-00@mail1.es.net>
Date: Mon, 8 May 2000 19:17:34 -0700
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list



$ Earn Unlimited Income Working From Home!!!$

DO NOT DELETE THIS, PRINT IT, AND READ IT . IT HAS WORKED SO
WELL, THIS IS MY THIRD TIME AROUND. I QUIT MY BORING JOB AND
WORK AT THIS ABOUT ONE TO TWO HOURS A DAY PROCESSING
ORDERS, INCLUDING MY DRIVE TO THE BANK!

SO GO FOR IT, YOU WILL BE GLAD YOU DID!


Dear Friend,

You can earn $50,000 or more in next the 90 days sending e-mail, Seem
impossible? Read on for details; is there a catch; NO, there is no
catch, just send your emails and be on your way to financial
freedom.

"AS SEEN ON NATIONAL TELEVISION"

Thank you for your time and Interest. This is the letter you've been
reading about in the news lately.

Due to the popularity of this letter on the Internet, a major nightly
news program recently devoted an entire show to the investigation of
the program described below to see, if it really can make people
money.

The show also investigated whether or not the program was legal.
Their findings proved once and for all that there are, absolutely no
laws prohibiting the participation in the program. This has helped to
show people that this is a simple, harmless and fun way to make some
extra money at home.

The results of this show have been truly remarkable. So many people
are participating that those involved are doing,much better than ever
before. Since everyone makes more as more people try it out, its been  very
exciting to be a part of lately. You will understand once you     experience
it.

"HERE IT IS BELOW"
================================================
================================================

*** Print This Now For Future Reference ***

The following income opportunity is one you may be interested in
taking a look at. It can be started with VERY LITTLE investment and
the income return is TREMENDOUS!!!

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

If you would like to make at least $50,000 in less than 90 days!
Please read the enclosed program...THEN READ IT AGAIN !!!
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

THIS IS A LEGITIMATE, LEGAL, MONEY MAKING OPPORTUNITY. It does not
require you to come into contact with people, do any hard work, and
best of all, you never have to leave the house except to get the
mail. If you believe that someday you'll get that big break that
you've been waiting for, THIS IS IT! Simply follow the instructions,
and your dreams will come true. This Multi-level e-mail order
marketing program works perfectly 100% EVERY TIME. E-mail is the
sales tool of the future. Take advantage of this non-commercialized
method of advertising NOW!

The longer you wait, the more people will be doing business using
e-mail. Get your piece of this action !!!

MULTI-LEVEL MARKETING (MLM) has finally gained respectability. It is
being taught in the Harvard Business School, and both Stanford
Research and the Wall Street Journal have stated that between 50% and
65% of all goods and services will be sold through multi-level
methods by the mid to late 1990's. This is a Multi-Billion Dollar
industry and of the 500,000 millionaires in the U.S., 20% (100,000)
made their fortune in the last several years in MLM. Moreover,
statistics show 45 people become millionaires everyday through Multi-
Level Marketing.

You may have heard this story before, but over the summer Donald Trump
made an appearance on the David Letterman show. Dave asked him what
he would do if he lost everything and had to start over from scratch.
Without hesitating, Trump said he would find a good network marketing
company and get to work. The audience started to hoot and boo him. He
looked out at the audience and dead-panned his response "That's why
I'm sitting up here and you are all sitting out there!"

With network marketing you have two sources of income. Direct
commissions from sales you make yourself and commissions from sales
made by people you introduce to the business.

Residual income is the secret of the wealthy. It means investing time
or money once and getting paid again and again and again. In network
marketing, it also means getting paid for the work of others.

The enclosed information is something I almost let slip through my
fingers. Fortunately, sometime later I re-read everything and gave    some
thought and study to it.

My name is Johnathon Rourke. Two years ago, the corporation I worked
at for the past twelve years down-sized and my position was
eliminated. After unproductive job interviews, I decided to open my
own business. Over the past year, I incurred many unforeseen
financial problems. I owed my family, friends and creditors over
$35,000. The economy was taking a toll on my business and I just
couldn't seem to make ends meet. I had to refinance and borrow
against my home to support my family and struggling business. AT THAT
MOMENT something significant happened in my life and I am writing to
share the experience in hopes that this will change your life FOREVER
FINANCIALLY!!!

In mid December, I received this program via e-mail. Six month's
prior to receiving this program I had been sending away for
information on various business opportunities. All of the programs I
received, in my opinion, were not cost effective. They were either
too difficult for me to comprehend or the initial investment was too   much
for me to risk to see if they would work or not. One claimed
that I would make  a million dollars in one year...it didn't tell me   I'd
have to write a book to make it!

But like I was saying, in December of 1997 I received this program. I didn't
send for it, or ask for it, they just got my name off a mailing list. THANK
GOODNESS FOR THAT!!! After reading it several times, to  make sure I was
reading it correctly, I couldn't believe my eyes.

Here was a MONEY MAKING PHENOMENON.

I could invest as much as I wanted to start, without putting me further into
debt. After I got a pencil and paper and figured it out,  I would at least
get my money back. But like most of you I was still  a little skeptical and
a little worried about the legal aspects of it  all. So I checked it out
with the U.S. Post Office (1-800-725-2161)   24 hrs, and they confirmed that
it is indeed legal! After determining  the program was LEGAL and NOT A CHAIN
LETTER, I decided "WHY NOT."

Initially I sent out 10,000 e-mails. It cost me about $15 for my time
on-line. The great thing about e-mail is that I don't need any money
for printing to send out the program, and because all of my orders are
fulfilled via e-mail, the only expense is my time. I am telling you
I was starting to receive orders for REPORT #1.By January 13, I had
received 26 orders for REPORT #1. Your goal is to "RECEIVE at least 20
ORDERS FOR REPORT #1 WITHIN 2 WEEKS. IF YOU DON'T, SEND OUT MORE   
PROGRAMS
UNTIL YOU DO!" My first step in making $50,000 in 90 days was done. By
January 30, I had received 196 orders for REPORT #2. Your   goal is to
"RECEIVE AT LEAST 100+ ORDERS FOR REPORT #2 WITHIN 2 WEEKS. IF NOT, SEND OUT
MORE PROGRAMS UNTIL YOU  DO. ONCE YOU HAVE 100    ORDERS, THE REST IS EASY,
RELAX, YOU WILL MAKE YOUR $50,000 GOAL."   Well, I had 196 orders for REPORT
#2, 96 more than I needed. So I sat  back and relaxed. By March 1, of my
e-mailing of 10,000, I received  $58,000 with more coming in every day.

I paid off ALL my debts and bought a much needed new car. Please take
time to read the attached program, IT WILL CHANGE YOUR LIFE FOREVER!!!
Remember, it won't work if you don't try it. This program does work,
but you must follow it EXACTLY! Especially the rules of not trying to
place your name in a different place. It won't work, you'll lose out
on a lot of money! In order for this program to work, you must meet
your goal of 20+ orders for REPORT #1, and 100+ orders for REPORT #2
and you will make $50,000 or more in 90 days. I AM LIVING PROOF THAT
IT WORKS!!!

If you choose not to participate in this program, I am sorry. It
really is a great opportunity with little cost or risk to you. If you
choose to participate, follow the program and you will be on your way
to financial security.

If you are a fellow business owner and are in financial trouble like I
was, or you want to start your own business, consider this a sign. I
DID!

Sincerely,

Johnathon Rourke

P.S. Do you have any idea what 11,700 $5 bills ($58,000) look like
piled up on a kitchen table? IT'S AWESOME!

A PERSONAL NOTE FROM THE ORIGINATOR OF THIS PROGRAM:

By the time you have read the enclosed program and reports, you should
have concluded that such a program, and one that is legal, could not
have been created by an amateur.

Let me tell you a little about myself. I had a profitable business for
10 years. Then in 1979 my business began falling off. I was doing the
same things that were previously successful for me, but it wasn't
working. Finally, I figured it out. It wasn't me, it was the economy.
Inflation and recession had replaced the stable economy that had been
with us since 1945. I don't have to tell you what happened to the
unemployment rate... because many of you know from first hand
experience. There were more failures and bankruptcies than ever  before.

The middle class was vanishing. Those who knew what they were doing
invested wisely and moved up. Those who did not, including those who
never had anything to save or invest, were moving down into the ranks
of the poor. As the saying goes, "THE RICH GET RICHER AND THE POOR GET
POORER." The traditional methods of making money will never allow you
to "move up" or "get rich", inflation will see to that.

You have just received information that can give you financial freedom
for the rest of your life, with "NO RISK" and "JUST A LITTLE BIT OF
EFFORT." You can make more money in the next few months than you have
ever imagined.

I should also point out that I will not see a penny of this money, nor
anyone else who has provided a testimonial for this program. I have
already made over 4 MILLION DOLLARS! I have retired from the program
after sending out over 16,000 programs. Now I have several offices
that make this and several other programs here and over seas.

Follow the program EXACTLY AS INSTRUCTED. Do not change it in any way.
It works exceedingly well as it is now. Remember to e-mail a copy of
this exciting report to everyone you can think of. One of the people
you send this to may send out 50,000...and your name will be on
everyone of them! Remember though, the more you send out the more
potential customers you will reach.

So my friend, I have given you the ideas, information, materials and
opportunity to become financially independent, IT IS UP TO YOU NOW!
************************************************************

"THINK ABOUT IT"
Before you delete this program from your mailbox, as I almost did,
take a little time to read it and REALLY THINK ABOUT IT. Get a pencil
and figure out what could happen when YOU participate. Figure out the
worst possible response and no matter how you calculate it, you will
still make a lot of money! You will definitely get back what you
invested. Any doubts you have will vanish when your first orders come
in. IT WORKS!
Jody Jacobs, Richmond, VA

************************************************************

HERE'S HOW THIS AMAZING PROGRAM WILL MAKE YOU THOUSAND OF DOLLAR$

INSTRUCTIONS:

This method of raising capital REALLY WORKS 100% EVERY
TIME. I am sure that you could use up to $50,000 or more in the next
90 days.

Before you say "BULL... ", please read this program carefully. This is
not a chain letter, but a perfectly legal money making opportunity.
Basically, this is what you do: As with all multi-level businesses, we
build our business by recruiting new partners and selling our   products.
Every state in the USA allows you to recruit new  multi-level business
partners, and we offer a product for EVERY dollar sent. YOUR ORDERS COME BY
MAIL AND ARE FILLED BY E-MAIL, so you are not involved in personal selling.
You do it privately in your own home, store oroffice. This is the GREATEST
Multi-Level Mail Order Marketing  anywhere:

This is what you MUST do:

1. Order all 4 reports shown on the list below (you can't sell them if
you don't order them).

* For each report, send $5.00 CASH, the NAME & NUMBER OF THE REPORT
YOU ARE ORDERING, YOUR E-MAIL ADDRESS, YOUR NAME & RETURN
ADDRESS (in case of a problem) and to the person whose name appears on the
list next to the report.

MAKE SURE YOUR RETURN ADDRESS IS ON YOUR ENVELOPE
IN CASE OF ANY MAIL PROBLEMS!

* When you place your order, make sure you order each of the four
reports. You will need all four reports so that you can save them on
your computer and resell them.

* Within a few days you will receive, via e-mail, each of the four
reports. Save them on your computer so they will be accessible for
you to send to the 1,000's of people who will order them from you.

2. IMPORTANT-- DO NOT alter the names of the people who are listed
next to each report, or their sequence on the list,in any way other
than is instructed below in steps "a" through "f" or you will lose
out on the majority of your profits. Once you understand the way this
works, you'll also see how it doesn't work if you change it.     Remember,
this method has been tested, and if you alter it, it will
not work.

 a. Look below for the listing of available reports.

 b. After you've ordered the four reports, take this Advertisement and
 remove the name and address under REPORT #4. This person has made it
 through the cycle and is no doubt counting their $50,000!

  c. Move the name and address under REPORT #3 down to REPORT #4.

  d. Move the name and address under REPORT #2 down to REPORT #3.

  e. Move the name and address under REPORT #1 down to REPORT #2.

  f. Insert your name/address in the REPORT #1 position.

  Please make sure you copy every name and address ACCURATELY!

3. Take this entire letter, including the modified list of names, and
save it to your computer. Make NO changes to the Instruction portion
of this letter.

Your cost to participate in this is practically nothing (surely you
can afford $20). You obviously already have an Internet Connection and
e-mail is FREE!

To assist you with marketing your business on the internet, the 4
reports you purchase will provide you with invaluable marketing
information which includes how to send bulk e-mails, where to find
thousands of free classified ads and much, much more.

In addition you will be provided with information on Internet
Marketing Clubs such as INTERNET MARKETING RESOURCES (IMR): This Is
one the premiere Internet marketing clubs on the INTERNET. This club
provides a forum where internet marketers from all over the world can
exchange ideas and secrets on Internet Marketing.

In addition, this club specializes in providing free internet
marketing tools and services for the Do-Yourself-Internet-Marketer.
They will provide you with free bulk e-mail software and up to
1,000,000 fresh e-mail addresses each week. This club will provide
you with hundreds of free resources, which include:

How to obtain free web sites, how to obtain top rankings in search
engines for your web-site, how to send bulk e-mail into AOL and
Compuserve, how to market your products on newsgroups, free classified
ads, electronic malls, bulletin boards, banner ads and much more.

There are two primary methods of building your downline:

METHOD #1: SENDING BULK E-MAIL

Let's say that you decide to start small, just to see how it goes, and
we'll assume you and all those involved send out only 2,000 programs
each. Let's also assume that the mailing receives a 0.5% response.
Using a good list the response could be much better. Also, many people
will send out hundreds of thousands of programs instead of 2,000. But
continuing with this example, you send out only 2,000 programs. With a
0.5% response, that is only 10 orders for REPORT #1. Those 10 people
respond by sending out 2,000 programs each for a total of 20,000. Out
of those 0.5%, 100 people respond and order REPORT #2. Those 100 mail
out 2,000 programs each for a total of 200,000. The 0.5% response to
that is 1,000 orders for REPORT #3. Those 1,000 send out 2,000
programs each for a 2,000,000 total. The 0.5% response to that is
10,000 orders for REPORT #4. That's 10,000 $5 bills for you. CASH!!!
Your total income in this example is $50 + $500 + $5,000+ $50,000 for
a total of $55,550!!!

REMEMBER FRIEND, THIS IS ASSUMING 1,990 OUT OF THE 2,000
PEOPLE YOU MAIL TO WILL DO ABSOLUTELY NOTHING AND TRASH THIS
PROGRAM! DARE TO THINK FOR A MOMENT WHAT WOULD HAPPEN IF EVERYONE, OR 
HALF
SENT OUT 100,000 PROGRAMS INSTEAD OF 2,000. Believe me, many people will do
just that, and more! By the way, your cost to participate in this is
practically nothing. You obviously already have an internet connection and
e-mail is FREE !!! REPORT #2 will show you the best methods for bulk
e-mailing, tell you where to obtain free bulk e-mail software and where to
obtain e-mail lists.

METHOD #2 - PLACING FREE ADS ON THE INTERNET

1. Advertising on the 'Net is very, very inexpensive, and there are
HUNDREDS of FREE places to advertise. Let's say you decide to start
small just to see how well it works. Assume your goal is to get ONLY
10 people to participate on your first level. (Placing a lot of FREE
ads on the internet will EASILY get a larger response.) Also assume
that everyone else in YOUR ORGANIZATION gets ONLY 10 downline
members.

Follow this example to achieve the STAGGERING results below.

 1st level-your 10 members with $5 .........$50
 2nd level-10 mems from those 10 ($5 x 100).......$500
 3rd level-10 mems from those 100 ($5 x 1,000) $5,000
 4th level-10 mems from those 1,000 ($5 x 10k) $50,000
 THIS TOTALS ---------------------------$55,550

Remember friends, this assumes that the people who participate only
recruit 10 people each. Think for a moment what would happen if they
got 20 people to participate! Most people get 100's of participants! THINK
ABOUT IT!

For every $5.00 you receive, all you must do is e-mail them the report
they ordered. THAT'S IT! ALWAYS PROVIDE SAME-DAY SERVICE ON ALL
ORDERS! This will guarantee that the e-mail THEY send out, with YOUR
name and address on it, will be prompt because they can't advertise
until they receive the report!

------------------------------------------
AVAILABLE REPORTS
------------------------------------------

*** Order Each REPORT by NUMBER and NAME ***

Notes:

 - ALWAYS SEND $5 CASH (U.S. CURRENCY) FOR EACH REPORT CHEQUES NOT
ACCEPTED
 - ALWAYS SEND YOUR ORDER VIA FIRST CLASS MAIL
 - Make sure the cash is concealed by wrapping it in at least two
   sheets of paper
 - On one of those sheets of paper, include: (a) the number & name of
   the report you are ordering, (b) your e-mail address, and (c) your
   name & postal address.

PLACE YOUR ORDER FOR THESE REPORTS NOW:
______________________________________________________

REPORT #1 "The Insider's Guide to Advertising for Free on the
           Internet"

ORDER REPORT #1 FROM:

 Jannette Black
 7101 18th St. N.
 St. Petersburg, FL. 33702
_____________________________________________________

REPORT #2 "The Insider's Guide to Sending Bulk E-mail on the
            Internet"

 ORDER REPORT #2 FROM:

 Myron Creamer
 6720 Cherrywood Dr
 Beaumont TX 77706-4215

 ______________________________________________________

REPORT #3 "The Secrets to Multilevel Marketing on the Internet"

 ORDER REPORT #3 FROM:

 H. Anker
 355 N. Tusa Rd
 Maricopa,AZ,85239

______________________________________________________

REPORT #4 "How to become a Millionaire utilizing the Power
            of Multilevel Marketing and the Internet"

 ORDER REPORT #4 FROM:
 Lance Brillion
 Box 38
 North Battleford, SK, Canada, S9A2X6

 ______________________________________________________

About 50,000 new people get online every month!

******* TIPS FOR SUCCESS *******
* TREAT THIS AS YOUR BUSINESS! Be prompt, professional,
and follow the directions accurately.

* Send for the four reports IMMEDIATELY so you will have them when the
orders start coming in because:

When you receive a $5 order, you MUST send out the
requested product/report.

* ALWAYS PROVIDE SAME-DAY SERVICE ON THE ORDERS YOU
RECEIVE.

* Be patient and persistent with this program. If you follow the
instructions exactly, your results WILL BE SUCCESSFUL!

* ABOVE ALL, HAVE FAITH IN YOURSELF AND KNOW YOU WILL SUCCEED!

******* YOUR SUCCESS GUIDELINES *******

Follow these guidelines to guarantee your success:

If you don't receive 20 orders for REPORT #1 within two weeks,
continue advertising or sending e-mails until you do.
Then, a couple of weeks later you should receive at least 100 orders
for REPORT#2. If you don't, continue advertising or sending e-mails
until you do.

Once you have received 100 or more orders for REPORT #2, YOU CAN RELAX,
because the system is already working for you, and the cash
will continue to roll in!

THIS IS IMPORTANT TO REMEMBER:

Every time your name is moved down on the list, you are placed in
front of a DIFFERENT report. You can KEEP TRACK of your PROGRESS by
watching which report people are ordering from you. If you want to
generate more income, send another batch of e-mails or continue
placing ads and start the whole process again! There is no limit to
the income you will generate from this business!

Before you make your decision as to whether or not you participate in  this
program. Please answer one question. DO YOU WANT TO CHANGE YOUR   LIFE? If
the answer is yes, please look at the folllowing facts about  this program:

 1. YOU ARE SELLING A PRODUCT WHICH DOES NOT
 COST ANYTHING TO PRODUCE!

 2. YOU ARE SELLING A PRODUCT WHICH DOES NOT
 COST ANYTHING TO SHIP!

 3. YOU ARE SELLING A PRODUCT WHICH DOES NOT
 COST YOU ANYTHING TO ADVERTISE!

 4. YOU ARE UTILIZING THE POWER OF THE INTERNET
 AND THE POWER OF MULTI-LEVEL MARKETING TO
 DISTRIBUTE YOUR PRODUCT ALL OVER THE
 WORLD!

 5. YOUR ONLY EXPENSES OTHER THAN YOUR
 INITIAL $20 INVESTMENT IS YOUR TIME!

 6. VIRTUALLY ALL OF THE INCOME YOU GENERATE
 FROM THIS PROGRAM IS PURE PROFIT!

 7. THIS PROGRAM WILL CHANGE YOUR LIFE FOREVER.

******* T E S T I M O N I A L S *******
This program does work, but you must follow it EXACTLY!
Especially the rule of not trying to place your name in a different
position, it won't work and you'll lose a lot of potential income.
I'm living proof that it works. It really is a great opportunity to
make relatively easy money, with little cost to you. If you do choose
to participate, follow the program exactly, and you'll be on your way
to financial security.
Steven Bardfield, Portland, OR
************************************************************
My name is Mitchell. My wife, Jody, and I live in Chicago, IL. I am a
cost accountant with a major U.S. Corporation and I make pretty good
money. When I received the program I grumbled to Jody about receiving
"junk mail." I made fun of the whole thing, spouting my knowledge of
the population and percentages involved. I "knew" it wouldn't work.
Jody totally ignored my supposed intelligence and jumped in with both
feet. I made merciless fun of her, and was ready to lay the old "I
told you so" on her when the thing didn't work... well, the laugh was
on me! Within two weeks she had received over 50 responses. Within 45
days she had received over $147,200 in $5 bills! I was shocked! I was
sure that I had it all figured and that it wouldn't work. I AM a
believer now. I have joined Jody in her "hobby." I did have seven
more years until retirement, but I think of the "rat race" and it's
not for me. We owe it all to MLM.
Mitchell Wolf MD., Chicago, IL
************************************************************
The main reason for this letter is to convince you that this system is
honest, lawful, extremely profitable, and is a way to get a large
amount of money in a short time. I was approached several times
before I checked this out. I joined just to see what one could expect
in return for the minimal effort and money required. To my
astonishment, I received $36,470.00 in the first 14 weeks, with money
still coming in.
Charles Morris, Esq.
************************************************************
Not being the gambling type, it took me several weeks to make up my
mind to participate in this plan. But conservative that I am, I
decided that the initial investment was so little that there was just
no way that I wouldn't get enough orders to at least get my money
back. Boy, was I surprised when I found my medium-size post office
box crammed with orders! For awhile, it got so overloaded that I had
to start picking up my mail at the window. I'll make more money this
year than any 10 years of my life before. The nice thing about this
deal is that it doesn't matter where people live. There simply isn't
a better investment with a faster return.
Paige Willis, Des Moines, IA
************************************************************
I had received this program before. I deleted it, but later I wondered
if I shouldn't have given it a try. Of course, I had no idea who to
contact to get another copy, so I had to wait until I was e-mailed
another program, ....11 months passed then it came...I didn't delete
this one!...I made more than $41,000 on the first try!!
Violet Wilson, Johnstown, PA
***********************************************************
This is my third time to participate in this plan. We have quit our
jobs, and will soon buy a home on the beach and live off the interest
on our money. The only way on earth that this plan will work for you
is if you do it. For your sake, and for your family's sake don't pass
up this golden opportunity. Good luck and happy spending!
Kerry Ford, Centerport, NY
************************************************************

ORDER YOUR REPORTS TODAY AND GET STARTED ON YOUR ROAD TO
FINANCIAL FREEDOM!

NOW IS THE TIME FOR YOUR TURN

DECISIVE ACTION YIELDS POWERFUL RESULTS

PLEASE NOTE: If you need help with starting a business, registering a
business name, learning how income tax is handled, etc., contact your
local office of the Small Business Administration (a Federal agency)
1-(800)827-5722 for free help and answers to questions. Also, the
Internal Revenue Service offers free help via telephone and free
seminars about business tax requirements. Your earnings and results
are highly dependant on your activities and advertising. This letter
constitutes no guarantees stated nor implied. In the event that it is
determined that this letter constitutes a guarantee of any kind, that
guarantee is now void. Any testimonials or amounts of earnings listed
in this letter may be factual or fictitious. If you have any question
of the legality of this letter contact the Office of Associate
Director for Marketing Practices Federal Trade Commission Bureau of
Consumer Protection in Washington DC.

--------------------
If this message has reached you in error, please accept our apologies. To
remove your address from future mailings, please reply with   "REMOVE" in
the subject heading.  We   promptly honour all remove   requests This
message is sent in compliance  of the new email bill:    Per  SECTION 301,
Paragraph (a) (2) (C) of S.  1618,
http://www.senate.gov/~murkowski/commercialmail/





  God Bless All Of You, May this Money be used according to His Will.








From rem-conf Tue May 09 16:46:39 2000 
From rem-conf-request@es.net Tue May 09 16:46:38 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12pJWP-00054W-00; Tue, 9 May 2000 16:34:37 -0700
Received: from gumby.cs.berkeley.edu [128.32.32.38] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12pJWN-00054M-00; Tue, 9 May 2000 16:34:35 -0700
Received: from BMRC.Berkeley.EDU (opus.cs.berkeley.edu [128.32.131.116])
	by gumby.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id QAA17748;
	Tue, 9 May 2000 16:32:35 -0700
Message-ID: <3918A013.4F30FA1C@BMRC.Berkeley.EDU>
Date: Tue, 09 May 2000 16:32:35 -0700
From: "Lawrence A. Rowe" <Rowe@bmrc.berkeley.edu>
Reply-To: Rowe@bmrc.berkeley.edu
Organization: U.C. Berkeley
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rowe, Lawrence" <Rowe@BMRC.Berkeley.EDU>
Subject: Planning for 1st OpenMash Workshop
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi -

Well, after a long period of silence, we are slowly getting the OpenMash
project off the ground.  We want to hold a 1-2 day workshop at Berkeley
this summer. The goal is to do some community building,
introductory/advanced training on using and extending mash, and lastly
provide a forum for discussion of what is being done and what needs to
be done to enable high bandwidth interactive streaming media
applications.

Given other constraints, our thought was to hold the meeting thursday
July 20 and if there is enough interest continue on friday July 21.  At
this point we need some indication of who wants to attend, what topics
they would be most interested in, and whether you'd be willing to give a
short presentation on your application and use of Mash.

Here are some possible presentation/session topics.  Let me know which,
if any, you would be most interested in attending.

"Adding a New Device/Media Type to Mash"
"TclCl - The Magic between C++ and Otcl"
"Interfacing to Commercial Streaming Media Systems"
"Distributed Client/Server Programming in Mash"
"Finding Your Way Around the Mash Source Code"
<put your good idea here>

Any other comments and feedback appreciated.
	Larry Rowe
-- 
Professor Lawrence A. Rowe          Internet:  Rowe@BMRC.Berkeley.EDU
Computer Science Division - EECS       Phone: 510-642-5117
University of California, Berkeley       Fax: 510-642-5615
Berkeley, CA 94720-1776            URL: http://bmrc.berkeley.edu/~larry



From rem-conf Wed May 10 08:36:04 2000 
From rem-conf-request@es.net Wed May 10 08:36:02 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12pYHT-00067T-00; Wed, 10 May 2000 08:20:11 -0700
Received: from dialup-209.246.100.173.newyork2.level3.net ([209.246.100.173] helo=mailer1.netexecutive.com)
	by mail2.es.net with smtp (Exim 1.92 #1)
	id 12pYHR-000673-00; Wed, 10 May 2000 08:20:09 -0700
From: <paradoks@excite.com>
Subject: A Great Way to Supplement Your Income! - ADV
Date: Wed, 10 May 2000 07:45:08
Message-Id: <346.885187.315397@mailer1.netexecutive.com>
Bcc:
To: rem-conf@es.net
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

If you would like information on a legitimate way to earn a 
significant income from your computer, then type "More Info."
in the subject box.  I will send you information that can easily 
add $2,000.00 or more a month to your income.
This is not a get rich quick scheme.


*****************************************************************

If this email has reached you as an error, I apologize.  Simply 
type "Remove" in the subject box and I will remove your name from 
my list.
 
 
 
 
 
 
 
 



From rem-conf Wed May 10 10:38:21 2000 
From rem-conf-request@es.net Wed May 10 10:38:20 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12paGy-0006zF-00; Wed, 10 May 2000 10:27:48 -0700
Received: from [203.106.107.108] (helo=unknown)
	by mail2.es.net with smtp (Exim 1.92 #1)
	id 12paGw-0006z5-00; Wed, 10 May 2000 10:27:46 -0700
From: <ttserve@tm.net.my>
Subject: Homeworker Needed
Date: Thu, 11 May 2000 02:00:30
Message-Id: <E12paGw-0006z5-00@mail2.es.net>
Bcc:
To: rem-conf@es.net
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

 Interested to earn $1200 or more? We're seeking people to assist 
 in typing and data processing works at home. Only serious 
 applicants need to apply.
  
 
 
 
 
 
 
 
 



From rem-conf Wed May 10 16:11:26 2000 
From rem-conf-request@es.net Wed May 10 16:11:25 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12pfTb-0002s1-00; Wed, 10 May 2000 16:01:11 -0700
Received: from (linux1.charleskendall.com) [193.130.145.37] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12pfTW-0002rD-00; Wed, 10 May 2000 16:01:07 -0700
Received: from myrop ([4.4.205.214]) by linux1.charleskendall.com ; Thu, 04 May 2000 21:56:00 -0000
Message-ID: <00007b2b30ab$00007caf$00007252@taffar (pool-209-138-205-92-dlls.grid.net [219.138.205.92]) by smtp7.atl.mindspring.net (ts029d25.nil-ny.concentric.net [216.173.24.181])>
To: <howardloan@newmail.net>
From: howardloan@newmail.net
Subject: Strategies on the U.S. Dollar                         29266
Date: Thu, 04 May 2000 17:00:35 -0500
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
Reply-To: howardloan@newmail.net
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

<HTML>
<BODY>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Do You Yen To Be A Miilionare!</TITLE>
<SCRIPT language=3DJavaScript1.1>



<!-- Begin
function right(e)


 {


var msg =3D "Not Available";


if (navigator.appName =3D=3D 'Netscape' && e.which =3D=3D 3)


 {


alert(msg);  // Delete this line to disable but not alert user


return false;


}


else


if (navigator.appName =3D=3D 'Microsoft Internet Explorer' && event.button=
=3D=3D2)


 {


alert(msg); // Delete this line to disable but not alert user


return false;


}


return true;


}

function cy(form)
{
    var remmsg =3D "Error!  Please enter an email address to be removed fr=
om our list.";
    if (!form.removeemail.value)
         {
         alert(remmsg);
          return;
          }
    else
         {
         form.submit();
          return; 
         }      
} // End of function validate_remove


function cyorder(form)
{
  var x=3D1;
  var ordermsg =3D "Error!  Entry required for Name and Email.";
  
  if (!form.Name.value)
         { x=3D2; } else {x=3D1;}
 if (!form.Email.value)
         { x=3D2; } else {x=3D1;}

if (x=3D=3D2) 
{
   alert(ordermsg);
   return; 
}else{
      form.submit();
     return; }
   
} // End of function validate_remove
  

document.onmousedown =3D right;
<!-- http://anywhereelse.com -->
<!--http://anywhereelse.net-->
<!--http://anywhereelse.org-->
<!--http://anyplaceelse.com-->
<!--http://anyplaceelse.net-->
<!--http://anyplaceelse.org-->


// End -->


</SCRIPT>

<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<META content=3Dtext/html;CHARSET=3Diso-8859-1 http-equiv=3DContent-Type><=
/HEAD>
<BODY aLink=3D#ffffff bgColor=3D#ffffff link=3D#ffffff vLink=3D#ffffff>
<P>
<TABLE bgColor=3D#ffffff border=3D0 cellPadding=3D0 cellSpacing=3D1 width=3D=
573>
  <TBODY>
  <TR>
    <TD vAlign=3Dtop width=3D571>
      <P><FONT color=3D#0033ff face=3DArial><B>Do you have the Yen to be a=
 
      Millionare?<BR><BR></B></FONT><FONT color=3D#000000 face=3DArial><B>=
200% 
      return in less than 30 days!</B></FONT><FONT color=3D#0033ff 
      face=3DArial><B><BR><BR></B></FONT><FONT color=3D#000000 face=3DAria=
l><B>Unique 
      Strategy Trading in the International Currency Markets!</B></FONT><F=
ONT 
      color=3D#0033ff face=3DArial><B><BR><BR></B></FONT><FONT color=3D#00=
0000 
      face=3DArial><B>Largest MarketPlace in the World!</B></FONT><FONT 
      color=3D#0033ff face=3DArial><B><BR><BR></B></FONT><FONT color=3D#00=
0000 
      face=3DArial><B>Get our Reports, Charts and Strategies on the U.S. D=
ollar 
      vs<BR>Japanese yen and euro dollar.<BR><BR>Example:</B></FONT><FONT 
      color=3D#0033ff face=3DArial><B><BR><BR></B></FONT><FONT color=3D#ff=
3300 
      face=3DArial><B>A $5,000 Investment in the yen vs the dollar, "prope=
rly 
      positioned",<BR>on 08/18 could have returned $15,000 on 
      09/18/99.</B></FONT></P>
      <CENTER>
      <P>
      <FORM action=3Dhttp://161.58.99.129/cgi-local/mgr.cgi method=3Dpost>=
<INPUT 
      name=3Dcoopid size=3D-1 type=3Dhidden value=3D0003><INPUT name=3Dact=
ivity size=3D-1 
      type=3Dhidden value=3DM></P></CENTER>
      <CENTER>
      <P><INPUT name=3DSubmit type=3Dsubmit value=3D"Click Here For More I=
nformation"></P></CENTER>
      <P><FONT color=3D#000000 face=3DArial><BR>I</FONT> 
      <TABLE bgColor=3D#dddddd border=3D0 width=3D563>
        <TBODY>
        <TR>
          <TD height=3D44 width=3D112></FORM>
            <FORM action=3Dhttp://161.58.99.129/cgi-local/mgr.cgi 
            method=3Dpost><INPUT name=3Dcoopid size=3D-1 type=3Dhidden val=
ue=3D0003><INPUT 
            name=3Dactivity size=3D-1 type=3Dhidden value=3DR></TD>
          <TD height=3D44 vAlign=3Dtop width=3D"100%"><FONT color=3D#00000=
0>Our E-Mail 
            List was filtered against a global remove database<BR>and our =
own 
            remove database. We do respect our remove lists! <BR>Please do=
 not 
            use reply to this e-mail, e-mail replies cannot be read!<BR>Th=
is 
            message is intended to reach a large audience, however,<BR>fur=
ther 
            transmissions to you by the sender of this e-mail<BR>may be st=
opped 
            at no cost to you by entering your email address and click the=
 
            remove button. </FONT><INPUT name=3Dacctemail size=3D34><INPUT=
 name=3DSubmit type=3Dsubmit value=3DRemove></TD></TR></TBODY></TABLE></P>=
</TD></TR></TBODY></TABLE></FORM></P></BODY></HTML>
<p><p><p><p><p><p><p><p><p><p>





<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><p><HTML><HE=
AD><TITLE>Do You Yen To Be A Miilionare!</TITLE><p><SCRIPT language=3DJava=
Script1.1><p><p><p><p><!-- Begin<p>function right(e)<p><p><p><p><p><p><p><=
p><p><p><p>
</BODY>
</HTML>





From rem-conf Thu May 11 09:20:00 2000 
From rem-conf-request@es.net Thu May 11 09:19:58 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12pvSd-00031j-00; Thu, 11 May 2000 09:05:15 -0700
Received: from ftpbox.mot.com [129.188.136.101] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12pvSa-00031Z-00; Thu, 11 May 2000 09:05:13 -0700
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id JAA25359 for <rem-conf@es.net>; Thu, 11 May 2000 09:05:04 -0700 (MST)]
Received: [from il75exm02.cig.mot.com (IL75EXM02.cig.mot.com [136.182.110.102]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id JAA24578 for <rem-conf@es.net>; Thu, 11 May 2000 09:05:04 -0700 (MST)]
Received: by IL75EXM02.cig.mot.com with Internet Mail Service (5.5.2650.21)
	id <KQ6X6X8T>; Thu, 11 May 2000 11:05:04 -0500
Message-ID: <BB60654DFAA8D311B16400508B6F25380107E042@IL27EXM05>
From: Fonteny Aurelia-AFONTEN1 <Aurelia_Fonteny-AFONTEN1@email.mot.com>
To: "'rem-conf@es.net'" <rem-conf@es.net>
Subject: SSRC field
Date: Thu, 11 May 2000 11:04:55 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi,

I'm rigth now working on RTP header compression, and there is one point that
is very unclear to me and I was wondering if someone could clarify it for
me.
Here is the overall problem : 
In RTP header compression (RFC2508), context-states have to be kept to be
able to compress the RTP header : but do the context have to be indexed on
{IPsource, IPdest, Port source, Port destination, SSRC}, or can they simply
be indexed on {IPsource, IPdest, Port source, Port destination} = does the
SSRC field of RTP add an information to {IPsource, IPdest, Port source, Port
destination}, or does {IPsource, IPdest, Port source, Port destination}
itself uniquely defines the ssrc.
 
In other words : 
RFC 1889 says RTP session = a pair of transport addresses (=network address
+ port for RTP and port for RTCP).
Within a RTP session, we define sources by their SSRC and different streams
within a RTP session have different SSRC.
RFC also says :
In a multimedia session, each medium is carried in a separate RTP session.
So, if we have two different streams coming from the same IP source (one
stream for one camera, another for a second camera), do they have to
communicate over two different source Port or is it possible that they both
go through the same Port source and Port destination in RTP?
What is the exact role of SSRC : distinguish between streams coming from
differents sources =( IP addresses + Port only), or also between different
streams for the same (IP source + Port)?
Thanks for your help.
Aurelie




From rem-conf Fri May 12 22:44:08 2000 
From rem-conf-request@es.net Fri May 12 22:44:06 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12qUUs-0006lo-00; Fri, 12 May 2000 22:29:54 -0700
Received: from (mail.sverige.com) [195.22.70.13] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12qUUp-0006la-00; Fri, 12 May 2000 22:29:52 -0700
Received: by mail.sverige.com from localhost
    (router,SLMail V3.2); Thu, 11 May 2000 07:25:01 +0200
Received: from 172.137.203.249 [172.137.203.249]
 by mail.sverige.com [195.22.70.15]  (SLmail 3.2.3113) with SMTP
 id AE557A1E20C411D4BCFE00508B62543B
 for <rdbateman@bluecrow.com> plus 153 more; Thu, 11 May 2000 07:24:57 0200
Message-ID: <00000e944509$00005d45$0000057c@>
To: Undisclosed Recipients@sverige.com
From: ywoe3@post.com
Subject: Are you working from home?
Date: Wed, 10 May 2000 23:56:17 -0500
X-Priority: 3
X-MSMail-Priority: Normal
Reply-To: ywoe3@post.com
X-SLUIDL: D98188BB-26F911D4-BCFE0050-8B62543B
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Have you ever dreamed of:
 
- Owning Your Own Time? 

- Controlling your Financial Future? 

- Feeling Good about what you do and Helping Others? 

Are you:

- Tired of working for someone else and getting paid what "they" feel you're worth?

- Tired of the "get-rich-quick" $5 fantasy programs?

- Tired of the MLM "dream scene"?

- Looking for a legitimate home-based enterprise that can generate you $10k-20k+ monthly?

THEN CHECK THIS OUT

- Make $1,000 to $15,000 profit on every sale and our system does the selling for you!

- No personal selling or "convince me" tactics involved.

- Complete information system in place that does the explaining for you.

- Free enterprise in its purest form, not MLM or franchise.

- Full training and support in an environment of utmost integrity.

- Exceptional products, not "vitamins, lotions, and potions".

- Lead generation system that brings qualified prospects to you.

- A multiple 6-figure income is realistically attainable in 1st year.

- 2 to 3-year retirement program... PERIOD!

- This program is all about money... how to make it, how to keep it, and how to make it work for you.

CALL:

1-800-340-8929 (Free recorded message)

You have nothing to lose and everything to gain, so call NOW!


To be removed reply with remove in the subject

 You will not be removed by calling the 800 number!
























Have you ever dreamed of:
 
- Owning Your Own Time? 

- Controlling your Financial Future? 

- Feeling Good about what you do and Helping Others? 











From rem-conf Mon May 15 16:00:15 2000 
From rem-conf-request@es.net Mon May 15 16:00:14 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12rTX6-0005GC-00; Mon, 15 May 2000 15:40:16 -0700
Received: from ns3.safepages.com (server3.safepages.com) [216.127.139.9] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12rTX4-0005Fg-00; Mon, 15 May 2000 15:40:14 -0700
Received: from localhost (cust-205-19.as03.snjs.eli.net [209.104.205.19])
	by server3.safepages.com (Postfix) with ESMTP id E938336612
	for <rem-conf@es.net>; Mon, 15 May 2000 18:40:01 -0400 (EDT)
From: "Laurie Bacardi" <earnathome_2000@excite.com>
To: "rem-conf@es.net" <rem-conf@es.net>
Date: Mon, 15 May 2000 15:37:54 -0700
Subject: please send more info
Reply-To: earnathome_2000@excite.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-Priority: 3
Message-Id: <20000515224001.E938336612@server3.safepages.com>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi, 

My name is Laurie Bacardi, my friend Debbie Hussey and I 
saw your ad. Please send me the following information 
about this: How much have you spent promoting it? 
And how many hours do you work it per week?
If you are open to looking at a club that builds your downline 
BEFORE you spend a dime, please check out this website:

http://www.freeyellow.com/members8/freesignup111/index.html

Debbie and I are in a great opportunity! This is Debbie's
website and I am helping her to promote it. 
If you are interested in working with us, we will also work 
with you to help you build your residual income.

This program is based on TEAM WORK! You won't be 
alone. If you are interested in working with us, we will 
also work with you to help you build your residual income.

With this program there are great benefits:

No meetings
No inventory
Free Post Launch 
Try it before you buy it!!! 
Long-term residual income 
A great value and a great business opportunity 
and much more...

With our great upline support Debbie made Team Leader
position in about one month. Laurie made the
Team Captain position in one month! And my sponsor 
Jim made the Gold Manager position in about 4 months. 

It is FREE to join and as a free member you can 
enjoy many benefits with NO obligation!

FINALLY, you have a CHOICE! A BETTER SOLUTION! 

You can sign up for free right now by going to 
http://www.freeyellow.com/members8/freesignup111/index.html

Once you sign up for free you can begin to watch your downline grow!! 

Thanks for your attention.

Regards,
Laurie
Team Captain (Thanks to TEAM Work!)


mailto:earnathome_2000@excite.com?subject=I-more info
http://www.freeyellow.com/members8/freesignup111/index.html


==========================================
This is not Spam:
Your business opportunity is posted at a web site and/or ad.
You have published your email address for those who are
interested. I'm sending you this message to ask for more
information about your business opportunity and to show
you an alternative regarding what you have on your web
site and/or ad. This is a one-time email. If you receive this more
than once please accept our apologies, it is because you
have more than one website and/or ad. Thank you and have
a great day!
==========================================








From rem-conf Tue May 16 08:54:10 2000 
From rem-conf-request@es.net Tue May 16 08:54:09 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12rjZd-0006SH-00; Tue, 16 May 2000 08:47:57 -0700
Received: from (hcgnet.com.br) [200.241.86.21] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12rjZY-0006ND-00; Tue, 16 May 2000 08:47:55 -0700
Received: from default by hcgnet.com.br (SMI-8.6/SMI-SVR4)
	id MAA19310; Tue, 16 May 2000 12:44:31 GMT
Date: Tue, 16 May 2000 12:44:31 GMT
From: fio@correo.sopde.es
Message-Id: <200005161244.MAA19310@hcgnet.com.br>
To: <rem-conf@es.net>
Subject: web site hosting
MIME-Version: 1.0
Content-Type: text/plain; charset=unknown-8bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


Get your own web site from only $11.75 per month!
Your web site comes with your own .com domain name 
and your own .com email address.
To sign up call 888 248 0765.
If you are calling outside the use please fax 240 337 8325.
____________________________________________________

WE do bulk email for you!
Call 888 248 0765 to promote your business today!
Half million email blast $600.00.
One million email blast $1275.00
Two million email blast $2500.00
For further information if you are outside the USA fax 240 337 8325
________________________________________________________

Get your estate planned today!
Avoid the prying eyes of the public!
Creditor proof your assets from those who want to get your 
money!
For further details fax 240 337 8325                                      





From rem-conf Tue May 16 12:36:10 2000 
From rem-conf-request@es.net Tue May 16 12:36:09 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12rmzm-0006LB-00; Tue, 16 May 2000 12:27:10 -0700
Received: from kmr-187-191.tm.net.my ([202.188.187.191] helo=unknown)
	by mail2.es.net with smtp (Exim 1.92 #1)
	id 12rmzj-0006Ko-00; Tue, 16 May 2000 12:27:08 -0700
From: <ttserve@tm.net.my>
Subject: Homeworker Needed
Date: Wed, 17 May 2000 00:01:21
Message-Id: <E12rmzj-0006Ko-00@mail2.es.net>
Bcc:
To: rem-conf@es.net
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Interested to earn $1200 or more? We're seeking people to assist 
in typing and data processing works at home. Only serious 
applicants need to apply.
 
 
 
 
 
 
 
 



From rem-conf Tue May 16 21:01:06 2000 
From rem-conf-request@es.net Tue May 16 21:01:05 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12runh-0000J6-00; Tue, 16 May 2000 20:47:13 -0700
Received: from max1-13.hou.stsi.net (email) [208.242.235.141] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12runf-0000Iw-00; Tue, 16 May 2000 20:47:11 -0700
From:  <trump08@globalnet.net>
To: <rem-conf@es.net>
Date: Tue, 16 May 2000 19:12:20
Message-Id: <639.267391.394332@email>
Subject: Tired Of Earning What Someone Else Thinks You Are Worth?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Do You Dream Of:

-Controlling Your Financial Future?

-Taking Back Your Time

-Feeling Good About What You Do And Helping Others?

Are You:

-Tired Of Working For  Someone Else And
  Getting Paid What "They" Think You Are Worth?

-Tired Of The MLM "Dream Scene"?

-Looking For A Legitimate Home-Based Enterprise That
Can Generate You $10k-20k+ Monthly?

THEN CHECK THIS OUT:

-Make $1,000 to $15,000 Profit on Every Sale AND our
System Does The Selling For You!

-No Personal Selling Or "Convince Me" Tactics Involved.

-Free Enterprise In Its Purest Form, Not MLM Or Franchise.

-Lead Generation System That Brings Qualified
Prospects To You.

-A Multiple 6-Figure Income Is Realistically Attainable In 1st 
Year.

-2-3 Year Retirement Program...PERIOD!

-This Program Is All About Money...How To Make It, How To Keep
  It, And How To Make It Work For You.

CALL:

1-800-320-9895  Extension 5433 (Free Recorded Message)

You Have Nothing To Lose And Everything To Gain, So Call Now!






 
 
 
 
 
 
 



From rem-conf Wed May 17 09:53:43 2000 
From rem-conf-request@es.net Wed May 17 09:53:41 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12s6yR-0004S5-00; Wed, 17 May 2000 09:47:07 -0700
Received: from ip236.cincinnati13.oh.pub-ip.psi.net ([38.31.49.236] helo=opera)
	by mail2.es.net with smtp (Exim 1.92 #1)
	id 12s6yO-0004RU-00; Wed, 17 May 2000 09:47:05 -0700
From: Opera9@flash.net
To: 
Subject: Best New Trade Show Display by Opera Portables, Inc. adv
Date: Wed, 17 May 2000 12:42:31 -0500
X-Sender: Opera9@flash.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E12s6yO-0004RU-00@mail2.es.net>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Opera Portables, Inc. is offering "by invitation" visits to our web site.  Packed full of exciting projects and news, Opera is leading the industry with displays that are as much eye-popping as they are eye catching.

Winner of numerous industry awards, including Ernst & Young's Crescendo Award, Exhibitor Magazine's Best New Product, Forty Under 40 and Emerging 30, Opera Portables is a progressive young company with imagination and vision.

If you use displays, you really owe it to yourself to check out our stuff!   Go to http://3637331613/

Opera Portables, Inc.

All removes honored at http://3637331613/removes.htm



From rem-conf Wed May 17 10:23:55 2000 
From rem-conf-request@es.net Wed May 17 10:23:54 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12s7VZ-0000w4-00; Wed, 17 May 2000 10:21:21 -0700
Received: from (ubvideo.com) [154.5.158.38] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12s7VY-0000vA-00; Wed, 17 May 2000 10:21:20 -0700
Received: from cherif - 90.0.0.6 by ubvideo.com  with Microsoft SMTPSVC(5.5.1774.114.11);
	 Wed, 17 May 2000 10:16:45 +0100
Message-ID: <002601bfc024$349fb260$0600005a@ubvideo.com>
From: "Mohamed K CHERIF" <mohamedc@ubvideo.com>
To: <rem-conf@es.net>
Subject: RTP (encapsulating H263) framing mechanism?
Date: Wed, 17 May 2000 10:20:32 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0023_01BFBFE9.88393940"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_0023_01BFBFE9.88393940
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,
I need to depacketize RTP packets which encapsulate H263 streams. I was =
=3D
thinking that there should be a packet length field in the RTP header, =
=3D
but there was not. If an RTP stream is provided, is there a way to tell =
=3D
where does the second RTP packet starts?
Thank you so much.
Mohamed



------=_NextPart_000_0023_01BFBFE9.88393940
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi All,<BR>I need to depacketize RTP =
packets which=20
encapsulate H263 streams. I was =3D<BR>thinking that there should be a =
packet=20
length field in the RTP header, =3D<BR>but there was not. If an RTP =
stream is=20
provided, is there a way to tell =3D<BR>where does the second RTP packet =

starts?<BR>Thank you so =
much.<BR>Mohamed<BR><BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_0023_01BFBFE9.88393940--




From rem-conf Wed May 17 18:32:53 2000 
From rem-conf-request@es.net Wed May 17 18:32:52 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sF4v-0006fM-00; Wed, 17 May 2000 18:26:21 -0700
Received: from cello.ocn.ne.jp [210.190.142.43] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sF4t-0006fC-00; Wed, 17 May 2000 18:26:19 -0700
Received: from pc130 (p33-dn14kitafuse.osaka.ocn.ne.jp [210.227.215.226])
	by cello.ocn.ne.jp (8.9.1a/OCN/) with SMTP id KAA01312;
	Thu, 18 May 2000 10:26:12 +0900 (JST)
From: "Adam Li" <adamli@icsl.ucla.edu>
To: "Mohamed K CHERIF" <mohamedc@ubvideo.com>, <rem-conf@es.net>
Subject: RE: RTP (encapsulating H263) framing mechanism?
Date: Wed, 17 May 2000 18:24:22 -0700
Message-ID: <NDBBLCHIMLPHDKFAGOGPMECECDAA.adamli@icsl.ucla.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0000_01BFC02D.1F583900"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <002601bfc024$349fb260$0600005a@ubvideo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01BFC02D.1F583900
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

RTP is for packet-switch network. That means you get them in individual
packets, not a continues bitstream as in circuit-switched case.

Hope it helps.

Adam


PS:

In RFC 1889 :
    o The length of the packet must be consistent with CC and
         payload type (if payloads have a known length).

H.263 payloads don't have a fixed length.

----------
Adam H. Li
Image Communication Lab                          (310) 825-5178 (Lab)
University of California, Los Angeles            (310) 825-7928 (Fax)

  -----Original Message-----
  From: Mohamed K CHERIF [mailto:mohamedc@ubvideo.com]
  Sent: Wednesday, May 17, 2000 10:21 AM
  To: rem-conf@es.net
  Subject: RTP (encapsulating H263) framing mechanism?


  Hi All,
  I need to depacketize RTP packets which encapsulate H263 streams. I was =
  thinking that there should be a packet length field in the RTP header, =
  but there was not. If an RTP stream is provided, is there a way to tell =
  where does the second RTP packet starts?
  Thank you so much.
  Mohamed



------=_NextPart_000_0000_01BFC02D.1F583900
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3013.2600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D760361701-18052000>RTP is=20
for packet-switch network. That means you get them in individual =
packets, not a=20
continues bitstream as in circuit-switched case.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D760361701-18052000>Hope=20
it helps.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000>Adam</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000>PS:</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D760361701-18052000>In RFC=20
1889 :</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000>&nbsp;&nbsp;&nbsp; o The length of the packet =
must be=20
consistent with CC =
and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
payload type (if payloads have a known length).<BR></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760361701-18052000>H.263&nbsp;payloads don't have a fixed =
length.<BR>
<P><FONT size=3D2>----------<BR>Adam H. Li<BR>Image Communication=20
Lab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
(310) 825-5178 (Lab)<BR>University of California, Los=20
Angeles&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 (310)=20
825-7928 (Fax)</FONT> </P></DIV></SPAN></FONT>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Mohamed K CHERIF=20
  [mailto:mohamedc@ubvideo.com]<BR><B>Sent:</B> Wednesday, May 17, 2000 =
10:21=20
  AM<BR><B>To:</B> rem-conf@es.net<BR><B>Subject:</B> RTP (encapsulating =
H263)=20
  framing mechanism?<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Hi All,<BR>I need to depacketize RTP =
packets=20
  which encapsulate H263 streams. I was =3D<BR>thinking that there =
should be a=20
  packet length field in the RTP header, =3D<BR>but there was not. If an =
RTP=20
  stream is provided, is there a way to tell =3D<BR>where does the =
second RTP=20
  packet starts?<BR>Thank you so=20
much.<BR>Mohamed<BR><BR></FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0000_01BFC02D.1F583900--




From rem-conf Wed May 17 19:41:18 2000 
From rem-conf-request@es.net Wed May 17 19:41:17 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sG7q-0000EL-00; Wed, 17 May 2000 19:33:26 -0700
Received: from cello.ocn.ne.jp [210.190.142.43] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sG7n-0000Do-00; Wed, 17 May 2000 19:33:23 -0700
Received: from pc130 (p33-dn14kitafuse.osaka.ocn.ne.jp [210.227.215.226])
	by cello.ocn.ne.jp (8.9.1a/OCN/) with SMTP id LAA04697;
	Thu, 18 May 2000 11:33:03 +0900 (JST)
From: "Adam Li" <adamli@icsl.ucla.edu>
To: "Tom Morrison" <SoMnyRds@ziplink.net>,
        "Mohamed K CHERIF" <mohamedc@ubvideo.com>, <rem-conf@es.net>
Subject: RE: RTP (encapsulating H263) framing mechanism?
Date: Wed, 17 May 2000 19:31:12 -0700
Message-ID: <NDBBLCHIMLPHDKFAGOGPEECHCDAA.adamli@icsl.ucla.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000D_01BFC036.75979AA0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <026b01bfc06e$bc4c8450$0100a8c0@terrapin>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01BFC036.75979AA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Thanks for the message.

Unfortunately, RFC 2429 doesn't specify packet length.
H.263 payload in RTP has header :
      0                   1
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RR    |P|V|   PLEN    |PEBIT|
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
There is no length field (and indeed shouldn't be a length field).

RTP is not designed to be used as a stream. In another word,
you can not search for a code that signals a new packet
(like what you can do in H.263 with PSC). There is nothing
to prevend the H.263 bitstream to emulate a valid RTP header.

If you wrote a bounch of RTP packets into a file (for simulation
or whatever), the solution is to record the starting position of
each packet in a seperate file.

Hope it helps.

Adam



----------
Adam H. Li
Image Communication Lab                          (310) 825-5178 (Lab)
University of California, Los Angeles            (310) 825-7928 (Fax)


  -----Original Message-----
  From: Tom Morrison [mailto:SoMnyRds@ziplink.net]
  Sent: Wednesday, May 17, 2000 7:14 PM
  To: Adam Li; Mohamed K CHERIF; rem-conf@es.net
  Subject: Re: RTP (encapsulating H263) framing mechanism?


  excuse me for inject my humble opinion...

  but isn't he asking how to figure out
  the total size of RTP packets that
  he has received that has an H.263
  Payload type?

  I haven't looked specificially at the RFC payload
  type for H.263, but I am betting that there
  is some type of extended header that shall
  define the length of the rest of the packet
  (and if I remember from my picturetel dayz...
  so long ago...)

  wasn't there also some requirement to define the
  start of a H.263 Video frame within that extended
  header...

  I hope I read his question correctly, and remember something...?

  ...sorry, I'll go back to my lurking...


    ----- Original Message -----
    From: Adam Li
    To: Mohamed K CHERIF ; rem-conf@es.net
    Sent: Wednesday, May 17, 2000 9:24 PM
    Subject: RE: RTP (encapsulating H263) framing mechanism?


    RTP is for packet-switch network. That means you get them in individual
packets, not a continues bitstream as in circuit-switched case.

    Hope it helps.

    Adam


    PS:

    In RFC 1889 :
        o The length of the packet must be consistent with CC and
             payload type (if payloads have a known length).

    H.263 payloads don't have a fixed length.

    ----------
    Adam H. Li
    Image Communication Lab                          (310) 825-5178 (Lab)
    University of California, Los Angeles            (310) 825-7928 (Fax)

      -----Original Message-----
      From: Mohamed K CHERIF [mailto:mohamedc@ubvideo.com]
      Sent: Wednesday, May 17, 2000 10:21 AM
      To: rem-conf@es.net
      Subject: RTP (encapsulating H263) framing mechanism?


      Hi All,
      I need to depacketize RTP packets which encapsulate H263 streams. I
was =
      thinking that there should be a packet length field in the RTP header,
=
      but there was not. If an RTP stream is provided, is there a way to
tell =
      where does the second RTP packet starts?
      Thank you so much.
      Mohamed



------=_NextPart_000_000D_01BFC036.75979AA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3013.2600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>Thanks=20
for the message.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000>Unfortunately, RFC 2429 doesn't specify =
packet=20
length.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>H.263=20
payload in RTP has header :</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4=20
5<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;=20
RR&nbsp;&nbsp;&nbsp; |P|V|&nbsp;&nbsp; PLEN&nbsp;&nbsp;&nbsp;=20
|PEBIT|<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>There=20
is no length field (and indeed shouldn't be a length =
field).</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>RTP is=20
not designed to be used as a stream. In another =
word,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>you=20
can not search for a code that signals a new packet </SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>(like=20
what you can do in H.263 with PSC). There is nothing</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>to=20
prevend the H.263 bitstream to emulate a valid </SPAN></FONT><FONT =
color=3D#0000ff=20
face=3DArial size=3D2><SPAN class=3D720341902-18052000>RTP =
header.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>If you=20
wrote a bounch of RTP packets into a file (for =
simulation</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>or=20
whatever), the solution is to record the starting position of=20
</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>each=20
packet in a seperate file.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>Hope=20
it helps.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000>Adam</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000><BR>
<P><FONT size=3D2>----------<BR>Adam H. Li<BR>Image Communication=20
Lab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
(310) 825-5178 (Lab)<BR>University of California, Los=20
Angeles&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 (310)=20
825-7928 (Fax)</FONT> </P></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Tom Morrison=20
  [mailto:SoMnyRds@ziplink.net]<BR><B>Sent:</B> Wednesday, May 17, 2000 =
7:14=20
  PM<BR><B>To:</B> Adam Li; Mohamed K CHERIF; =
rem-conf@es.net<BR><B>Subject:</B>=20
  Re: RTP (encapsulating H263) framing mechanism?<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>excuse me for inject my humble=20
  opinion...</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D3>but isn't he asking how to figure=20
out</FONT></DIV>
  <DIV><FONT face=3DArial>the total size of RTP packets that =
</FONT></DIV>
  <DIV><FONT face=3DArial>he has received that has an</FONT><FONT =
face=3DArial>=20
  H.263 </FONT></DIV>
  <DIV><FONT face=3DArial>Payload type?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial>I haven't looked specificially at the RFC=20
  payload</FONT></DIV>
  <DIV><FONT face=3DArial>type for H.263, but I am betting that =
there</FONT></DIV>
  <DIV><FONT face=3DArial>is some type of extended header that =
shall</FONT></DIV>
  <DIV><FONT face=3DArial>define the length of the rest of the =
packet</FONT></DIV>
  <DIV><FONT face=3DArial>(and if I remember from my picturetel=20
  dayz...</FONT></DIV>
  <DIV><FONT face=3DArial>so long ago...)</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial>wasn't there also some requirement to define=20
  the</FONT></DIV>
  <DIV><FONT face=3DArial>start of a H.263 Video frame within that=20
  extended</FONT></DIV>
  <DIV><FONT face=3DArial>header...</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I hope I read his question correctly, =
and=20
  remember something...?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial>...sorry, I'll go back to my =
lurking...</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A href=3D"mailto:adamli@icsl.ucla.edu" =
title=3Dadamli@icsl.ucla.edu>Adam Li</A>=20
    </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
    href=3D"mailto:mohamedc@ubvideo.com" =
title=3Dmohamedc@ubvideo.com>Mohamed K=20
    CHERIF</A> ; <A href=3D"mailto:rem-conf@es.net"=20
    title=3Drem-conf@es.net>rem-conf@es.net</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, May 17, 2000 =
9:24=20
    PM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: RTP =
(encapsulating H263)=20
    framing mechanism?</DIV>
    <DIV><BR></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000>RTP is for packet-switch network. That =
means you=20
    get them in individual packets, not a continues bitstream as in=20
    circuit-switched case.</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000>Hope it helps.</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000>Adam</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000>PS:</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D760361701-18052000>In=20
    RFC 1889 :</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000>&nbsp;&nbsp;&nbsp; o The length of the =
packet must=20
    be consistent with CC=20
    and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; payload type =
(if=20
    payloads have a known length).<BR></SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D760361701-18052000>H.263&nbsp;payloads don't have a fixed =
length.<BR>
    <P><FONT size=3D2>----------<BR>Adam H. Li<BR>Image Communication=20
    =
Lab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
    (310) 825-5178 (Lab)<BR>University of California, Los=20
    =
Angeles&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    (310) 825-7928 (Fax)</FONT> </P></DIV></SPAN></FONT>
    <BLOCKQUOTE=20
    style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
      <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
      size=3D2>-----Original Message-----<BR><B>From:</B> Mohamed K =
CHERIF=20
      [mailto:mohamedc@ubvideo.com]<BR><B>Sent:</B> Wednesday, May 17, =
2000=20
      10:21 AM<BR><B>To:</B> rem-conf@es.net<BR><B>Subject:</B> RTP=20
      (encapsulating H263) framing mechanism?<BR><BR></DIV></FONT>
      <DIV><FONT face=3DArial size=3D2>Hi All,<BR>I need to depacketize =
RTP packets=20
      which encapsulate H263 streams. I was =3D<BR>thinking that there =
should be a=20
      packet length field in the RTP header, =3D<BR>but there was not. =
If an RTP=20
      stream is provided, is there a way to tell =3D<BR>where does the =
second RTP=20
      packet starts?<BR>Thank you so=20
    =
much.<BR>Mohamed<BR><BR></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE></BODY></HTML>

------=_NextPart_000_000D_01BFC036.75979AA0--




From rem-conf Thu May 18 03:40:49 2000 
From rem-conf-request@es.net Thu May 18 03:40:46 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sNZQ-0005ld-00; Thu, 18 May 2000 03:30:24 -0700
Received: from ferao.jungle.bt.co.uk [132.146.107.45] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sNZO-0005l9-00; Thu, 18 May 2000 03:30:23 -0700
Received: from sherekhan.jungle.bt.co.uk (sherekhan [132.146.107.25])
	by ferao.jungle.bt.co.uk (8.9.1b+Sun/Jungle-8.9.1-03) with SMTP id LAA21484
	for <rem-conf%es.net@ferao.jungle.bt.co.uk>; Thu, 18 May 2000 11:18:25 +0100 (BST)
Received: from jungle.bt.co.uk ([132.146.107.59]) by sherekhan.jungle.bt.co.uk; Thu, 18 May 00 11:18:24 BST
Message-Id: <3923C6D0.8475F481@jungle.bt.co.uk>
Date: Thu, 18 May 2000 11:32:48 +0100
From: Sylvie Brunelle <sylvie@jungle.bt.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
Mime-Version: 1.0
To: rem <rem-conf@es.net>
Subject: one SSRC for each participants??
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi everybody,

Does someone know if all participants of a RTP session do have an SSRC
or if it is only for sources.

Indeed when I read the definition of the SSRC, I understand that only
sources do have an SSRC.
"Synchronization source (SSRC): The source of a stream of RTP
             packets, identified by a 32-bit numeric SSRC identifier
             carried in the RTP header so as not to be dependent upon
             the network address. All packets from a synchronization
             source form part of the same timing and sequence number
             space, so a receiver groups packets by synchronization
             source for playback. Examples of synchronization sources
             include the sender of a stream of packets derived from a
             signal source such as a microphone or a camera, or an RTP
             mixer (see below)..."

But if I look at the format of the RTCP packets, I see that there is
always the SSRC of the packet sender specified in the header of the RTCP
packet and that participants that are only receivers do send RTCP
packets (RR...). Thus that would involve that ALL participants of an RTP
session (even receivers) do have an SSRC.

Is that right?
Cheers
Sylvie







From rem-conf Thu May 18 05:17:26 2000 
From rem-conf-request@es.net Thu May 18 05:17:25 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sPBT-0007Ri-00; Thu, 18 May 2000 05:13:47 -0700
Received: from bells.cs.ucl.ac.uk [128.16.5.31] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12sPBR-0007RY-00; Thu, 18 May 2000 05:13:45 -0700
Received: from eucharisto.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.19617-0@bells.cs.ucl.ac.uk>; Thu, 18 May 2000 13:13:39 +0100
To: Sylvie Brunelle <sylvie@jungle.bt.co.uk>
cc: rem <rem-conf@es.net>
Subject: Re: one SSRC for each participants??
In-reply-to: Your message of "Thu, 18 May 2000 11:32:48 BST." <3923C6D0.8475F481@jungle.bt.co.uk>
Date: Thu, 18 May 2000 13:13:38 +0100
Message-ID: <1518.958652018@cs.ucl.ac.uk>
From: Colin Perkins <C.Perkins@cs.ucl.ac.uk>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Sylvie,

--> Sylvie Brunelle writes:
>Does someone know if all participants of a RTP session do have an SSRC
>or if it is only for sources.
>
>Indeed when I read the definition of the SSRC, I understand that only
>sources do have an SSRC.
...
>But if I look at the format of the RTCP packets, I see that there is
>always the SSRC of the packet sender specified in the header of the RTCP
>packet and that participants that are only receivers do send RTCP
>packets (RR...). Thus that would involve that ALL participants of an RTP
>session (even receivers) do have an SSRC.
>
>Is that right?

Yes. ALL participants in an RTP session have an SSRC.

Colin



From rem-conf Thu May 18 11:17:46 2000 
From rem-conf-request@es.net Thu May 18 11:17:45 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sUif-00040L-00; Thu, 18 May 2000 11:08:25 -0700
Received: from ip121.vancouver5.dialup.canada.psi.net (ubvideo.com) [154.5.128.121] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sUiY-0003zh-00; Thu, 18 May 2000 11:08:19 -0700
Received: from cherif - 90.0.0.6 by ubvideo.com  with Microsoft SMTPSVC(5.5.1774.114.11);
	 Thu, 18 May 2000 11:03:03 +0100
Message-ID: <006301bfc0f3$d6df2f40$0600005a@ubvideo.com>
From: "Mohamed K CHERIF" <mohamedc@ubvideo.com>
To: <rem-conf@es.net>
Cc: "Amr Mohamed" <amrm@ece.ubc.ca>
References: <NDBBLCHIMLPHDKFAGOGPEECHCDAA.adamli@icsl.ucla.edu>
Subject: RTP (encapsulating H263+) 
Date: Thu, 18 May 2000 11:06:50 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0060_01BFC0B9.2A772F80"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_0060_01BFC0B9.2A772F80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks for Adam, Tom and Martin for their interesting reply. I agree =
with Adam in that the input to my RTP depacketizer is not supposed to be =
a continous octet stream. As Tom said too the bytes might not be aligned =
and the start offset has to be read from the extension payload header =
(this is only valid for H263 not H263+ I believe).=20
One last question guys, is the time stamp increment for H263+ equal to =
one? (I assume a 90 Khz clock). In that case, I think of an "artificial" =
way to get the next packet from the RTP stream (even if it's =
continuous). I just need to calculate the next timestamp and assume the =
data is unlikely to produce a pattern (sequence # + timestamp).
Thanks a lot for all.

Mohamed K Cherif, M.A.Sc. - UBC
UB Video - Application Developer
Tel 737 2426 Ext 26
  ----- Original Message -----=20
  From: Adam Li=20
  To: Tom Morrison ; Mohamed K CHERIF ; rem-conf@es.net=20
  Sent: Wednesday, May 17, 2000 7:31 PM
  Subject: RE: RTP (encapsulating H263) framing mechanism?


  Thanks for the message.
  =20
  Unfortunately, RFC 2429 doesn't specify packet length.
  H.263 payload in RTP has header :
        0                   1
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |   RR    |P|V|   PLEN    |PEBIT|
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  There is no length field (and indeed shouldn't be a length field).
  =20
  RTP is not designed to be used as a stream. In another word,
  you can not search for a code that signals a new packet=20
  (like what you can do in H.263 with PSC). There is nothing
  to prevend the H.263 bitstream to emulate a valid RTP header.
  =20
  If you wrote a bounch of RTP packets into a file (for simulation
  or whatever), the solution is to record the starting position of=20
  each packet in a seperate file.
  =20
  Hope it helps.
  =20
  Adam
  =20


  ----------
  Adam H. Li
  Image Communication Lab                          (310) 825-5178 (Lab)
  University of California, Los Angeles            (310) 825-7928 (Fax)=20

  =20
    -----Original Message-----
    From: Tom Morrison [mailto:SoMnyRds@ziplink.net]
    Sent: Wednesday, May 17, 2000 7:14 PM
    To: Adam Li; Mohamed K CHERIF; rem-conf@es.net
    Subject: Re: RTP (encapsulating H263) framing mechanism?


    excuse me for inject my humble opinion...

    but isn't he asking how to figure out
    the total size of RTP packets that=20
    he has received that has an H.263=20
    Payload type?

    I haven't looked specificially at the RFC payload
    type for H.263, but I am betting that there
    is some type of extended header that shall
    define the length of the rest of the packet
    (and if I remember from my picturetel dayz...
    so long ago...)

    wasn't there also some requirement to define the
    start of a H.263 Video frame within that extended
    header...

    I hope I read his question correctly, and remember something...?

    ...sorry, I'll go back to my lurking...


      ----- Original Message -----=20
      From: Adam Li=20
      To: Mohamed K CHERIF ; rem-conf@es.net=20
      Sent: Wednesday, May 17, 2000 9:24 PM
      Subject: RE: RTP (encapsulating H263) framing mechanism?


      RTP is for packet-switch network. That means you get them in =
individual packets, not a continues bitstream as in circuit-switched =
case.
      =20
      Hope it helps.
      =20
      Adam
      =20
      =20
      PS:
      =20
      In RFC 1889 :
          o The length of the packet must be consistent with CC and
               payload type (if payloads have a known length).

      H.263 payloads don't have a fixed length.

      ----------
      Adam H. Li
      Image Communication Lab                          (310) 825-5178 =
(Lab)
      University of California, Los Angeles            (310) 825-7928 =
(Fax)=20

        -----Original Message-----
        From: Mohamed K CHERIF [mailto:mohamedc@ubvideo.com]
        Sent: Wednesday, May 17, 2000 10:21 AM
        To: rem-conf@es.net
        Subject: RTP (encapsulating H263) framing mechanism?


        Hi All,
        I need to depacketize RTP packets which encapsulate H263 =
streams. I was =3D
        thinking that there should be a packet length field in the RTP =
header, =3D
        but there was not. If an RTP stream is provided, is there a way =
to tell =3D
        where does the second RTP packet starts?
        Thank you so much.
        Mohamed



------=_NextPart_000_0060_01BFC0B9.2A772F80
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Thanks for Adam, Tom and Martin for=20
their&nbsp;interesting reply. I agree with Adam in that the input to my =
RTP=20
depacketizer is not supposed to be a continous octet stream. As Tom said =
too the=20
bytes might not be aligned and the start offset has to be read from the=20
extension payload header (this is only valid for H263 not H263+ I =
believe).=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>One last question guys, is the time =
stamp increment=20
for H263+ equal to one? (I assume a 90 Khz clock). In that case, I think =
of an=20
"artificial" way to get the next packet from the RTP stream (even if =
it's=20
continuous). I just need to calculate the next timestamp and assume the =
data is=20
unlikely to produce a pattern (sequence # + timestamp).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot for all.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>Mohamed K Cherif, M.A.Sc. - UBC<BR>UB Video - Application =
Developer<BR>Tel=20
737 2426 Ext 26</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:adamli@icsl.ucla.edu" =
title=3Dadamli@icsl.ucla.edu>Adam Li</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:SoMnyRds@ziplink.net"=20
  title=3DSoMnyRds@ziplink.net>Tom Morrison</A> ; <A=20
  href=3D"mailto:mohamedc@ubvideo.com" =
title=3Dmohamedc@ubvideo.com>Mohamed K=20
  CHERIF</A> ; <A href=3D"mailto:rem-conf@es.net"=20
  title=3Drem-conf@es.net>rem-conf@es.net</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, May 17, 2000 =
7:31=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: RTP (encapsulating =
H263)=20
  framing mechanism?</DIV>
  <DIV><BR></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000>Thanks for the message.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000>Unfortunately, RFC 2429 doesn't specify =
packet=20
  length.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000>H.263 payload in RTP has header =
:</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4=20
  5<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;=20
  RR&nbsp;&nbsp;&nbsp; |P|V|&nbsp;&nbsp; PLEN&nbsp;&nbsp;&nbsp;=20
  |PEBIT|<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000>There is no length field (and indeed =
shouldn't be a=20
  length field).</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>RTP=20
  is not designed to be used as a stream. In another =
word,</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>you=20
  can not search for a code that signals a new packet =
</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000>(like what you can do in H.263 with PSC). =
There is=20
  nothing</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>to=20
  prevend the H.263 bitstream to emulate a valid </SPAN></FONT><FONT=20
  color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>RTP=20
  header.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>If=20
  you wrote a bounch of RTP packets into a file (for=20
  simulation</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>or=20
  whatever), the solution is to record the starting position of=20
  </SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>each=20
  packet in a seperate file.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000>Hope=20
  it helps.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000>Adam</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D720341902-18052000><BR>
  <P><FONT size=3D2>----------<BR>Adam H. Li<BR>Image Communication=20
  =
Lab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
  (310) 825-5178 (Lab)<BR>University of California, Los=20
  =
Angeles&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  (310) 825-7928 (Fax)</FONT> </P></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D720341902-18052000></SPAN></FONT>&nbsp;</DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Tom Morrison=20
    [mailto:SoMnyRds@ziplink.net]<BR><B>Sent:</B> Wednesday, May 17, =
2000 7:14=20
    PM<BR><B>To:</B> Adam Li; Mohamed K CHERIF;=20
    rem-conf@es.net<BR><B>Subject:</B> Re: RTP (encapsulating H263) =
framing=20
    mechanism?<BR><BR></DIV></FONT>
    <DIV><FONT face=3DArial size=3D2>excuse me for inject my humble=20
    opinion...</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D3>but isn't he asking how to figure=20
    out</FONT></DIV>
    <DIV><FONT face=3DArial>the total size of RTP packets that =
</FONT></DIV>
    <DIV><FONT face=3DArial>he has received that has an</FONT><FONT =
face=3DArial>=20
    H.263 </FONT></DIV>
    <DIV><FONT face=3DArial>Payload type?</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3DArial>I haven't looked specificially at the RFC=20
    payload</FONT></DIV>
    <DIV><FONT face=3DArial>type for H.263, but I am betting that=20
    there</FONT></DIV>
    <DIV><FONT face=3DArial>is some type of extended header that=20
shall</FONT></DIV>
    <DIV><FONT face=3DArial>define the length of the rest of the=20
    packet</FONT></DIV>
    <DIV><FONT face=3DArial>(and if I remember from my picturetel=20
    dayz...</FONT></DIV>
    <DIV><FONT face=3DArial>so long ago...)</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3DArial>wasn't there also some requirement to define =

    the</FONT></DIV>
    <DIV><FONT face=3DArial>start of a H.263 Video frame within that=20
    extended</FONT></DIV>
    <DIV><FONT face=3DArial>header...</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>I hope I read his question =
correctly, and=20
    remember something...?</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3DArial>...sorry, I'll go back to my =
lurking...</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV>&nbsp;</DIV>
    <BLOCKQUOTE=20
    style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
      <DIV style=3D"FONT: 10pt arial">----- Original Message ----- =
</DIV>
      <DIV=20
      style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
      <A href=3D"mailto:adamli@icsl.ucla.edu" =
title=3Dadamli@icsl.ucla.edu>Adam=20
      Li</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
      href=3D"mailto:mohamedc@ubvideo.com" =
title=3Dmohamedc@ubvideo.com>Mohamed K=20
      CHERIF</A> ; <A href=3D"mailto:rem-conf@es.net"=20
      title=3Drem-conf@es.net>rem-conf@es.net</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, May 17, =
2000 9:24=20
      PM</DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: RTP =
(encapsulating H263)=20
      framing mechanism?</DIV>
      <DIV><BR></DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000>RTP is for packet-switch network. That =
means you=20
      get them in individual packets, not a continues bitstream as in=20
      circuit-switched case.</SPAN></FONT></DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000>Hope it helps.</SPAN></FONT></DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000>Adam</SPAN></FONT></DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000>PS:</SPAN></FONT></DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000>In RFC 1889 :</SPAN></FONT></DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000>&nbsp;&nbsp;&nbsp; o The length of the =
packet=20
      must be consistent with CC=20
      and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; payload =
type (if=20
      payloads have a known length).<BR></SPAN></FONT></DIV>
      <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
      class=3D760361701-18052000>H.263&nbsp;payloads don't have a fixed=20
length.<BR>
      <P><FONT size=3D2>----------<BR>Adam H. Li<BR>Image Communication=20
      =
Lab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      (310) 825-5178 (Lab)<BR>University of California, Los=20
      =
Angeles&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
      (310) 825-7928 (Fax)</FONT> </P></DIV></SPAN></FONT>
      <BLOCKQUOTE=20
      style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
        <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
        size=3D2>-----Original Message-----<BR><B>From:</B> Mohamed K =
CHERIF=20
        [mailto:mohamedc@ubvideo.com]<BR><B>Sent:</B> Wednesday, May 17, =
2000=20
        10:21 AM<BR><B>To:</B> rem-conf@es.net<BR><B>Subject:</B> RTP=20
        (encapsulating H263) framing mechanism?<BR><BR></DIV></FONT>
        <DIV><FONT face=3DArial size=3D2>Hi All,<BR>I need to =
depacketize RTP=20
        packets which encapsulate H263 streams. I was =3D<BR>thinking =
that there=20
        should be a packet length field in the RTP header, =3D<BR>but =
there was=20
        not. If an RTP stream is provided, is there a way to tell =
=3D<BR>where=20
        does the second RTP packet starts?<BR>Thank you so=20
        =
much.<BR>Mohamed<BR><BR></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0060_01BFC0B9.2A772F80--




From rem-conf Thu May 18 13:50:37 2000 
From rem-conf-request@es.net Thu May 18 13:50:36 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sX9c-0006f6-00; Thu, 18 May 2000 13:44:24 -0700
Received: from cr703217-a.ktchnr1.on.wave.home.com (cybertron.div8.net) [24.42.217.5] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sX9a-0006ew-00; Thu, 18 May 2000 13:44:22 -0700
Received: by div8.net
	via sendmail from stdin
	id <m12sX9H-003ErYC@cybertron.div8.net> (Debian Smail3.2.0.102)
	for rem-conf@es.net; Thu, 18 May 2000 16:44:03 -0400 (EDT) 
Date: Thu, 18 May 2000 16:44:03 -0400
From: Billy Biggs <vektor@div8.net>
To: Mohamed K CHERIF <mohamedc@ubvideo.com>
Cc: rem-conf@es.net, Amr Mohamed <amrm@ece.ubc.ca>
Subject: Re: RTP (encapsulating H263+)
Message-ID: <20000518164403.A17334@div8.net>
References: <NDBBLCHIMLPHDKFAGOGPEECHCDAA.adamli@icsl.ucla.edu> <006301bfc0f3$d6df2f40$0600005a@ubvideo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i
In-Reply-To: <006301bfc0f3$d6df2f40$0600005a@ubvideo.com>; from mohamedc@ubvideo.com on Thu, May 18, 2000 at 11:06:50AM -0700
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Mohamed K CHERIF (mohamedc@ubvideo.com):

> Thanks for Adam, Tom and Martin for their interesting reply. I agree with
> Adam in that the input to my RTP depacketizer is not supposed to be a
> continous octet stream. As Tom said too the bytes might not be aligned and
> the start offset has to be read from the extension payload header (this is
> only valid for H263 not H263+ I believe). 

> One last question guys, is the time stamp increment for H263+ equal to
> one?  (I assume a 90 Khz clock). In that case, I think of an
> "artificial" way to get the next packet from the RTP stream (even if
> it's continuous). I just need to calculate the next timestamp and
> assume the data is unlikely to produce a pattern (sequence # +
> timestamp).

  If you're still trying to hack it so you don't have to know the size of
the packet, you're going to get very messed up if you try to do some hack
based on the clock.  What if some broken implementation sends you a
packet that is too long?  What if the clock on the sender is a little
off?

  The only solution would seem to be that your upper layers need to know
the size of the frame.  In the interests of robustness, better re-design
your streamer.

-- 
Billy Biggs                         vektor@div8.net
http://www.div8.net/billy       wbiggs@uwaterloo.ca



From rem-conf Thu May 18 14:36:54 2000 
From rem-conf-request@es.net Thu May 18 14:36:53 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sXup-0000DG-00; Thu, 18 May 2000 14:33:11 -0700
Received: from ip121.vancouver5.dialup.canada.psi.net (ubvideo.com) [154.5.128.121] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sXun-0000Cu-00; Thu, 18 May 2000 14:33:10 -0700
Received: from cherif - 90.0.0.6 by ubvideo.com  with Microsoft SMTPSVC(5.5.1774.114.11);
	 Thu, 18 May 2000 14:27:56 +0100
Message-ID: <00a901bfc110$75a2bc20$0600005a@ubvideo.com>
From: "Mohamed K CHERIF" <mohamedc@ubvideo.com>
To: "Billy Biggs" <vektor@div8.net>
Cc: <rem-conf@es.net>,
	"Amr Mohamed" <amrm@ece.ubc.ca>
References: <NDBBLCHIMLPHDKFAGOGPEECHCDAA.adamli@icsl.ucla.edu> <006301bfc0f3$d6df2f40$0600005a@ubvideo.com> <20000518164403.A17334@div8.net>
Subject: Re: RTP (encapsulating H263+)
Date: Thu, 18 May 2000 14:31:42 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Thanks Billy.
I'm developing an application which implements RTP only. I need to deliver
it to someone else who will have the packet sizes (I guess inside the IP
pakets). Is there a way to generate a librairy that can get the packet sizes
as input from the upper layers? (I can't deliver source code).
All help is much appreciated.

Mohamed K Cherif, M.A.Sc. - UBC
UB Video - Application Developer
Tel 737 2426 Ext 26
----- Original Message -----
From: Billy Biggs <vektor@div8.net>
To: Mohamed K CHERIF <mohamedc@ubvideo.com>
Cc: <rem-conf@es.net>; Amr Mohamed <amrm@ece.ubc.ca>
Sent: Thursday, May 18, 2000 1:44 PM
Subject: Re: RTP (encapsulating H263+)


> Mohamed K CHERIF (mohamedc@ubvideo.com):
>
> > Thanks for Adam, Tom and Martin for their interesting reply. I agree
with
> > Adam in that the input to my RTP depacketizer is not supposed to be a
> > continous octet stream. As Tom said too the bytes might not be aligned
and
> > the start offset has to be read from the extension payload header (this
is
> > only valid for H263 not H263+ I believe).
>
> > One last question guys, is the time stamp increment for H263+ equal to
> > one?  (I assume a 90 Khz clock). In that case, I think of an
> > "artificial" way to get the next packet from the RTP stream (even if
> > it's continuous). I just need to calculate the next timestamp and
> > assume the data is unlikely to produce a pattern (sequence # +
> > timestamp).
>
>   If you're still trying to hack it so you don't have to know the size of
> the packet, you're going to get very messed up if you try to do some hack
> based on the clock.  What if some broken implementation sends you a
> packet that is too long?  What if the clock on the sender is a little
> off?
>
>   The only solution would seem to be that your upper layers need to know
> the size of the frame.  In the interests of robustness, better re-design
> your streamer.
>
> --
> Billy Biggs                         vektor@div8.net
> http://www.div8.net/billy       wbiggs@uwaterloo.ca
>




From rem-conf Thu May 18 15:55:19 2000 
From rem-conf-request@es.net Thu May 18 15:55:18 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sZ5Q-0001tX-00; Thu, 18 May 2000 15:48:12 -0700
Received: from boreas.isi.edu [128.9.160.161] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sZ5O-0001tI-00; Thu, 18 May 2000 15:48:10 -0700
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA02460;
	Thu, 18 May 2000 15:48:08 -0700 (PDT)
Message-Id: <200005182248.PAA02460@boreas.isi.edu>
To: IETF-Announce: ;
Subject: RFC 2833 on Tones
Cc: rfc-ed@ISI.EDU, rem-conf@es.net
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 18 May 2000 15:48:08 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 2833

        Title:	    RTP Payload for DTMF Digits, Telephony Tones and
                    Telephony Signals
        Author(s):  H. Schulzrinne, S. Petrack
        Status:     Standards Track
	Date:       May 2000
        Mailbox:    schulzrinne@cs.columbia.edu,
                    scott.petrack@metatel.com 
        Pages:      30
        Characters: 68786
        Updates/Obsoletes/SeeAlso:  None

        URL:        ftp://ftp.isi.edu/in-notes/rfc2833.txt


This memo describes how to carry dual-tone multifrequency (DTMF)
signaling, other tone signals and telephony events in RTP packets.

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <000518154538.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2833

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2833.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <000518154538.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--



From rem-conf Thu May 18 18:34:54 2000 
From rem-conf-request@es.net Thu May 18 18:34:53 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sbYa-0004mK-00; Thu, 18 May 2000 18:26:28 -0700
Received: from (ami4000.hei.co.kr) [202.30.128.31] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sbYY-0004ll-00; Thu, 18 May 2000 18:26:26 -0700
Received: from aaa (localhost [127.0.0.1])
	by ami4000.hei.co.kr (8.9.3/8.9.3) with SMTP id KAA17472;
	Fri, 19 May 2000 10:23:07 +0900 (KST)
Message-ID: <005601bfc131$de32e960$56fb7da6@hei.co.kr>
From: "Nam Kyu Kim" <batman@hei.co.kr>
To: "Colin Perkins" <C.Perkins@cs.ucl.ac.uk>
Cc: <rem-conf@es.net>
References: <1518.958652018@cs.ucl.ac.uk>
Subject: Re: one SSRC for each participants??
Date: Fri, 19 May 2000 10:30:44 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0053_01BFC17D.49C0AD20"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_0053_01BFC17D.49C0AD20
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

Dear Colin and all

I have one question for clear understanding..

For example, in case there are two participant-one is a sender another =
is=20
a only receiver, ssrc value of RTCP control packets(RR, SDES, BYE) in=20
receiver is the same as sender's ssrc?

SR of sender
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=3D2|P|    RC   |   PT=3DSR=3D200   |             length            | =
header
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         SSRC of sender                        |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|              NTP timestamp, most significant word             | sender
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
:

RR of receiver
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=3D2|P|    RC   |   PT=3DRR=3D201   |             length            | =
header
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     SSRC of packet sender                     |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                 SSRC_1 (SSRC of first source)                 | report
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ block
| fraction lost |       cumulative number of packets lost       |   1
:

SDES of receiver
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=3D2|P|    SC   |  PT=3DSDES=3D202  |             length            | =
header
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                          SSRC/CSRC_1                          | chunk
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   1
|                           SDES items                          |
:

Underlined SSRCs of above packet formats are all same?
Or not same?
Or participant only receiving can not send SDES, BYE and APP?

-----------------------------------------------------
Nam Kyu Kim=20
R & D Team 9
Mobile Telecommunication Terminal Division
HYUNDAI ELECTRONICS INDUSTRIES Co., Ltd.

TEL : (82-2)580-5511       FAX : (82-2)580-5487
Home : (82-2)2282-3077   C.P. : 017-211-3077
E-mail : batman@good.to
-----------------------------------------------------


> Sylvie,
>=20
> --> Sylvie Brunelle writes:
> >Does someone know if all participants of a RTP session do have an =
SSRC
> >or if it is only for sources.
> >
> >Indeed when I read the definition of the SSRC, I understand that only
> >sources do have an SSRC.
> ...
> >But if I look at the format of the RTCP packets, I see that there is
> >always the SSRC of the packet sender specified in the header of the =
RTCP
> >packet and that participants that are only receivers do send RTCP
> >packets (RR...). Thus that would involve that ALL participants of an =
RTP
> >session (even receivers) do have an SSRC.
> >
> >Is that right?
>=20
> Yes. ALL participants in an RTP session have an SSRC.
>=20
> Colin
>=20
>=20

------=_NextPart_000_0053_01BFC17D.49C0AD20
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dks_c_5601-1987" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT size=3D2>Dear Colin and all</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>I have one question for clear =
understanding..</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>For example, in case there are two participant-one =
is a sender=20
another is&nbsp;</FONT></DIV>
<DIV><FONT size=3D2>a only receiver, </FONT><FONT size=3D2>ssrc value of =
RTCP=20
control packets(RR, SDES, BYE) in </FONT></DIV>
<DIV><FONT size=3D2>receiver is the same as </FONT><FONT =
size=3D2>sender's=20
ssrc?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>SR of sender</FONT></DIV>
<DIV><FONT=20
size=3D2>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>|V=3D2|P|&nbsp;&nbsp;&nbsp;=20
RC&nbsp;&nbsp; |&nbsp;&nbsp; PT=3DSR=3D200&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|=20
header<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
<STRONG><U><FONT color=3D#ff0000>SSRC</FONT></U> </STRONG>of=20
sender&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+<BR>|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
NTP timestamp, most significant=20
word&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |=20
sender<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+=20
</FONT></DIV>
<DIV><FONT size=3D2>:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>RR of receiver</FONT></DIV>
<DIV><FONT=20
size=3D2>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>|V=3D2|P|&nbsp;&nbsp;&nbsp;=20
RC&nbsp;&nbsp; |&nbsp;&nbsp; PT=3DRR=3D201&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|=20
header<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<STRONG><U><STRONG><U><FONT =
color=3D#ff0000>SSRC</FONT></U></STRONG></U></STRONG>=20
of packet=20
sender&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+<BR>|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
<STRONG><U><FONT color=3D#ff0000>SSRC</FONT></U></STRONG>_1 (SSRC of =
first=20
source)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
| =
report<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+=20
block<BR>| fraction lost |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
cumulative number=20
of packets lost&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;=20
1<BR>:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>SDES of receiver</FONT></DIV>
<DIV><FONT=20
size=3D2>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>|V=3D2|P|&nbsp;&nbsp;&nbsp;=20
SC&nbsp;&nbsp; |&nbsp; PT=3DSDES=3D202&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|=20
header<BR>+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+<BR>|&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
<STRONG><U><FONT=20
color=3D#ff0000>SSRC</FONT></U></STRONG>/CSRC_1&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|=20
chunk<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+&nbsp;&nbsp;=20
1<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
SDES=20
items&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
|<BR>:<BR></FONT></DIV>
<DIV><FONT size=3D2>Underlined SSRCs of above packet formats are all=20
same?</FONT></DIV>
<DIV><FONT size=3D2>Or not same?</FONT></DIV>
<DIV><FONT size=3D2>Or participant only receiving </FONT><FONT =
size=3D2>can not send=20
SDES, BYE and APP?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT =
size=3D2>-----------------------------------------------------<BR>Nam=20
Kyu Kim <BR>R &amp; D Team 9<BR>Mobile Telecommunication Terminal=20
Division<BR>HYUNDAI ELECTRONICS INDUSTRIES Co., Ltd.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>TEL : =
(82-2)580-5511&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX :=20
(82-2)580-5487<BR>Home : (82-2)2282-3077&nbsp;&nbsp; C.P. :=20
017-211-3077<BR>E-mail : <A=20
href=3D"mailto:batman@good.to">batman@good.to</A><BR>--------------------=
---------------------------------<BR></DIV></FONT>
<DIV><FONT size=3D2>&nbsp;</DIV></FONT><FONT size=3D2>&gt; =
Sylvie,<BR>&gt; <BR>&gt;=20
--&gt; Sylvie Brunelle writes:<BR>&gt; &gt;Does someone know if all =
participants=20
of a RTP session do have an SSRC<BR>&gt; &gt;or if it is only for=20
sources.<BR>&gt; &gt;<BR>&gt; &gt;Indeed when I read the definition of =
the SSRC,=20
I understand that only<BR>&gt; &gt;sources do have an SSRC.<BR>&gt; =
...<BR>&gt;=20
&gt;But if I look at the format of the RTCP packets, I see that there =
is<BR>&gt;=20
&gt;always the SSRC of the packet sender specified in the header of the=20
RTCP<BR>&gt; &gt;packet and that participants that are only receivers do =
send=20
RTCP<BR>&gt; &gt;packets (RR...). Thus that would involve that ALL =
participants=20
of an RTP<BR>&gt; &gt;session (even receivers) do have an SSRC.<BR>&gt;=20
&gt;<BR>&gt; &gt;Is that right?<BR>&gt; <BR>&gt; Yes. ALL participants =
in an RTP=20
session have an SSRC.<BR>&gt; <BR>&gt; Colin<BR>&gt; <BR>&gt;=20
</FONT></BODY></HTML>

------=_NextPart_000_0053_01BFC17D.49C0AD20--




From rem-conf Thu May 18 21:20:52 2000 
From rem-conf-request@es.net Thu May 18 21:20:51 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12se9E-0006zk-00; Thu, 18 May 2000 21:12:28 -0700
Received: from mailer4.mail.vanderbilt.edu [129.59.1.214] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12se9C-0006za-00; Thu, 18 May 2000 21:12:26 -0700
Received: from acis-fax.acis.vanderbilt.edu (acis-fax.acis.Vanderbilt.Edu [129.59.1.109])
	by mailer4.mail.vanderbilt.edu (8.9.1a/8.9.1/VU-3.0.2) with SMTP id XAA25993
	for <rem-conf@es.net>; Thu, 18 May 2000 23:12:24 -0500 (CDT)
TO: <rem-conf@es.net>
Received: from localhost by acis-fax.acis.vanderbilt.edu ; 19 May 100 04:10:03 Central Standard Time
From: <homebiz009@talk21.com>
To: <remark@earthlink.net>
Date: Thu, 18 May 2000 23:17:17
Subject: #1 Best Business Opportunity Available?
Message-ID: <c52kodpus2ve6hv.180520002317@localhost>
Content-Type: text/plain
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

*************************************************************
OPPOSED TO COMMERCIAL EMAILS?
Advice on how to keep your email address from being
harvested for commercial purposes at the end of this message.
*************************************************************

Hi,

Here's the URGENT "INSIDE INFO" just for you!

I just wanted to let you in on this extremely explosive Income
Program. This Company has been around for 3 years. All the bugs have
been worked out and it is poised at the very beginning of the
tremendous growth stage. And Yes, the company is worldwide.

If you have been looking for an honest, work from home business that
has dynamite products and a desire to help the "little guy" succeed,
you have just found it! The Company even gives away corporate
enrollments to their distributors...FREE! Lots of other Freebies too!

Heavy hitters are joining this International company. Those that
know the industry recognize the superior opportunity that the
Company is offering! You have just gotten lucky; you're in the right
place at the right time!

Folks, this is Real! Just reply back and I'll send you the website
address where you can get all the info including the enrollment
form!!! Please DON"T MISS OUT ON THIS!!

I will help you in every way possible, although, as you'll soon see,
the only way you'll mess up is if you miss out!

UPDATE! We have just formed a group consisting of the Top Recruiters
within the Company. Everyone belonging to this elite group has vowed
to promote and create tremendous spillover for everyone. All those
that enroll because of this email will go into this leg of the
organization!

PLEASE REPLY BACK NOW!!! The timing is perfect!

I challenge you to find a better opportunity anywhere! No empty
promises, just solid support along with the dedication to help you
succeed!

mailto:netbiz002@mail.com?subject=More-Info

You'll be glad you did!

Have a wonderful day!
-----------------------------------------------------------------
Ladies and Gentleman:
IF YOU ARE OPPOSED TO ALL COMMERCIAL EMAIL:

If you are completely opposed to any and all commercial email, ask
your Internet Service Provider to make your email address unlisted.
Your address cannot be harvested if it is a non-published address.
Your ISP is bound by the U.S. Federal Privacy Act and must comply
with your request if you are paying for their services.

This mailing is done by an independent marketing company. We
apologize if this message has reached you in error. Save the Planet,
Save the Trees! Advertise via E-mail. No wasted paper!



From rem-conf Fri May 19 04:43:36 2000 
From rem-conf-request@es.net Fri May 19 04:43:35 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12skz4-0004Wg-00; Fri, 19 May 2000 04:30:26 -0700
Received: from wodc7-2.corprelay.mail.uu.net [192.48.96.69] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12skz3-0004WW-00; Fri, 19 May 2000 04:30:25 -0700
Received: from neserve0.corp.us.uu.net by wodc7mr2.ffx.ops.us.uu.net with ESMTP 
	(peer crosschecked as: neserve0.corp.us.uu.net [153.39.201.88])
	id QQipvq29443;
	Fri, 19 May 2000 11:30:24 GMT
Received: by neserve0.corp.us.uu.net 
	id QQipvq23265;
	Fri, 19 May 2000 07:30:18 -0400 (EDT)
From: jhall@UU.NET (Jeremy Hall)
Message-Id: <QQipvq23265.200005191130@neserve0.corp.us.uu.net>
Subject: Re: audio coverage of space shuttle mission STS-101
In-Reply-To: <QQimpe04856.200004261437@neserve0.corp.us.uu.net> from Jeremy Hall
 at "Apr 26, 2000 10:36:57 am"
To: Jeremy Hall <jhall@UU.NET>
Date: Fri, 19 May 2000 07:30:18 -0400 (EDT)
CC: mbone@ISI.EDU, rem-conf@es.net
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi,

After a mostly flawless launch, Atlantis lifted off from the Kenedy Space
Centre at 10:12:10 GMT.

The audio coverage is online and functional.  Let me know if problems or
packet loss are observed.

_J

In the new year, Jeremy Hall wrote:
> Hi,
> 
> Out of curiosity, is anybody interested in mp3 streams of shuttle audio
> during space missions?
> 
> _J
> 




From rem-conf Fri May 19 05:47:57 2000 
From rem-conf-request@es.net Fri May 19 05:47:56 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sm7x-0005yM-00; Fri, 19 May 2000 05:43:41 -0700
Received: from correu.urv.es [193.147.222.10] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sm7m-0005xh-00; Fri, 19 May 2000 05:43:37 -0700
Received: from mar (mar.si.urv.es)
 by correu.urv.es (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FUT0089E4NANW@correu.urv.es> for rem-conf@es.net; Fri,
 19 May 2000 14:42:48 +0200 (MET DST)
Date: Fri, 19 May 2000 14:47:00 +0200
From: Encarna Perez <eperez@correu.urv.es>
Subject: MBONE-Vinton G. Cerf, Honorary Doctor of the URV
X-Sender: epr@correu.urv.es
To: rem-conf@es.net
Message-id: <4.2.0.58.20000519144247.00a29da0@correu.urv.es>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Content-type: MULTIPART/ALTERNATIVE;
 BOUNDARY="Boundary_(ID_MQEDRAni9tTd+XT3EGXXjA)"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


--Boundary_(ID_MQEDRAni9tTd+XT3EGXXjA)
Content-type: text/plain; format=flowed; charset=us-ascii

Announcement of another MBone session
Title: Vinton G. Cerf, Honorary Doctor of the URV
URL : http://www.fut.es/vint_cat.html
Contact : ols@si.urv.es
Start : 22 May 2000, 13 h (GMT)
Time : 3 hours
Length: 1 day
           until 22 May 2000 , 16 h (GMT)
Scope (TTL): International (128).
Formats : Audio: PCM2 (71 Kbps)
                Video: H.261
               Maximum of 1 video transmission at a time
Other tools:
         UCL/nt
Type: public
Mode: Reading
Broadcast: Live
Description: Ceremony of Investiture of Vinton G. Cerf as Honorary Doctor
Of the Rovira i Virgili University, Tarragona, Spain
More information:
http://www.rediris.es/mbone/agenda


_________________________________________________________
Encarna Perez Ruiz
Coordinadora de Comunicacions i Atencio als Usuaris
Servei d'Informatica -  Universitat Rovira i Virgili
C/ de l'Escorxador s/n               Tel:  +34 (9) 77 55 80 30
43003 Tarragona                       Fax:  +34 (9) 77 55 82 57
Spain                                      mailto:eperez@si.urv.es
_________________________________________________________ 

--Boundary_(ID_MQEDRAni9tTd+XT3EGXXjA)
Content-type: text/html; charset=us-ascii

<html>
Announcement of another MBone session <br>
Title: Vinton G. Cerf, Honorary Doctor of the URV <br>
URL :
<a href="http://www.fut.es/vint_cat.html" eudora="autourl"><font color="#0000FF"><u>http://www.fut.es/vint_cat.html</a></font></u>
<br>
Contact : ols@si.urv.es <br>
Start : 22 May 2000, 13 h (GMT)<br>
Time : 3 hours <br>
Length: 1 day <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; until 22 May 2000 , 16 h (GMT) <br>
Scope (TTL): International (128). <br>
Formats : Audio: PCM2 (71 Kbps) <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Video: H.261 <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Maximum of 1 video transmission at a time <br>
Other tools: <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UCL/nt <br>
Type: public <br>
Mode: Reading <br>
Broadcast: Live <br>
Description: Ceremony of Investiture of Vinton G. Cerf as Honorary Doctor <br>
Of the Rovira i Virgili University, Tarragona, Spain<br>
More information: <br>
<font color="#0000FF"><u><a href="http://www.rediris.es/mbone/agenda" eudora="autourl">http://www.rediris.es/mbone/agenda<br>
<br>
</a></font></u><br>
<div>_________________________________________________________</div>
<div>Encarna Perez Ruiz</div>
<div>Coordinadora de Comunicacions i Atencio als Usuaris</div>
<div>Servei d'Informatica -&nbsp; Universitat Rovira i Virgili</div>
<div>C/ de l'Escorxador s/n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tel:&nbsp; +34 (9) 77 55 80 30</div>
<div>43003 Tarragona&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fax:&nbsp; +34 (9) 77 55 82 57</div>
<div>Spain&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="mailto:eperez@si.urv.es" EUDORA=AUTOURL>mailto:eperez@si.urv.es</a></div>
_________________________________________________________
</html>

--Boundary_(ID_MQEDRAni9tTd+XT3EGXXjA)--



From rem-conf Fri May 19 07:25:19 2000 
From rem-conf-request@es.net Fri May 19 07:25:17 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12snfG-00000a-00; Fri, 19 May 2000 07:22:10 -0700
Received: from (redball.dynamicsoft.com) [216.173.40.51] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12snfD-0007n3-00; Fri, 19 May 2000 07:22:08 -0700
Received: from dynamicsoft.com (1Cust22.tnt3.freehold.nj.da.uu.net [63.25.172.22])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id KAA01471;
	Fri, 19 May 2000 10:22:28 -0400 (EDT)
Message-ID: <39255090.99A41DC5@dynamicsoft.com>
Date: Fri, 19 May 2000 10:32:48 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Nam Kyu Kim <batman@hei.co.kr>
CC: Colin Perkins <C.Perkins@cs.ucl.ac.uk>, rem-conf@es.net
Subject: Re: one SSRC for each participants??
References: <1518.958652018@cs.ucl.ac.uk> <005601bfc131$de32e960$56fb7da6@hei.co.kr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list



> Nam Kyu Kim wrote:
> 
> Dear Colin and all
> 
> I have one question for clear understanding..
> 
> For example, in case there are two participant-one is a sender another
> is
> a only receiver, ssrc value of RTCP control packets(RR, SDES, BYE) in
> receiver is the same as sender's ssrc?

Let A be the sender, and B be the receiver.


> 
> SR of sender
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |V=2|P|    RC   |   PT=SR=200   |             length            |
> header
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |                         SSRC of sender                        |
> +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> |              NTP timestamp, most significant word             |
> sender
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> :

This is SSRC of A.



> 
> RR of receiver
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |V=2|P|    RC   |   PT=RR=201   |             length            |
> header
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |                     SSRC of packet sender                     |
> +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> |                 SSRC_1 (SSRC of first source)                 |
> report
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> block
> | fraction lost |       cumulative number of packets lost       |   1
> :


The first SSRC (of packet sender) is SSRC of B.
The second SSRC (SSRC_1, of first source) is the SSRC of A.

> 
> SDES of receiver
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |V=2|P|    SC   |  PT=SDES=202  |             length            |
> header
> +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> |                          SSRC/CSRC_1                          |
> chunk
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   1
> |                           SDES items                          |

SSRC/CSRC_1 is the SSRC of B, since you have indicated that this is the
SDES from the receiver, B.


> :
> Underlined SSRCs of above packet formats are all same?
> Or not same?
> Or participant only receiving can not send SDES, BYE and APP?

The receiving-only participant can send SDES, BYE or APP. In fact, it
SHOULD send SDES. It can even send BYE (but only if it has previously
send an SDES).

-Jonathan R.
-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (732) 741-4778
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com



From rem-conf Fri May 19 07:25:19 2000 
From rem-conf-request@es.net Fri May 19 07:25:19 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sneO-0007mr-00; Fri, 19 May 2000 07:21:16 -0700
Received: from bells.cs.ucl.ac.uk [128.16.5.31] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12sneM-0007mh-00; Fri, 19 May 2000 07:21:14 -0700
Received: from eucharisto.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.26412-0@bells.cs.ucl.ac.uk>; Fri, 19 May 2000 15:20:46 +0100
To: Nam Kyu Kim <batman@hei.co.kr>
cc: rem-conf <rem-conf@es.net>
Subject: Re: one SSRC for each participants??
In-reply-to: Your message of "Fri, 19 May 2000 10:30:44 +0900." <005601bfc131$de32e960$56fb7da6@hei.co.kr>
Date: Fri, 19 May 2000 15:20:45 +0100
Message-ID: <3591.958746045@cs.ucl.ac.uk>
From: Colin Perkins <C.Perkins@cs.ucl.ac.uk>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

--> Nam Kyu Kim writes:
>Dear Colin and all
>
>I have one question for clear understanding..
>
>For example, in case there are two participant-one is a sender another 
>is a only receiver, ssrc value of RTCP control packets(RR, SDES, BYE) 
>in receiver is the same as sender's ssrc?

The SSRC in SR and SDES packets is that of the participant generating
those SR/SDES packets. The first SSRC in an RR packet is that of the
participant generating that RR packet, the other SSRC(s) are those of
the participants being reported upon.

>SR of sender
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|V=2|P|    RC   |   PT=SR=200   |             length            | header
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                         SSRC of sender                        |
>+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>|              NTP timestamp, most significant word             | sender
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>:
>
>RR of receiver
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|V=2|P|    RC   |   PT=RR=201   |             length            | header
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                     SSRC of packet sender                     |
>+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>|                 SSRC_1 (SSRC of first source)                 | report
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ block
>| fraction lost |       cumulative number of packets lost       |   1
>:
>
>SDES of receiver
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|V=2|P|    SC   |  PT=SDES=202  |             length            | header
>+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>|                          SSRC/CSRC_1                          | chunk
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   1
>|                           SDES items                          |
>:
>
>Underlined SSRCs of above packet formats are all same?
>Or not same?

Not the same.

>Or participant only receiving can not send SDES, BYE and APP?

A receiver is allowed to send SDES, BYE and APP packets.

Colin



From rem-conf Fri May 19 11:20:14 2000 
From rem-conf-request@es.net Fri May 19 11:20:14 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12srHr-0004MC-00; Fri, 19 May 2000 11:14:15 -0700
Received: from mail-out2.apple.com [17.254.0.51] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12srHq-0004M2-00; Fri, 19 May 2000 11:14:14 -0700
Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225])
	by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id LAA28707
	for <rem-conf@es.net>; Fri, 19 May 2000 11:14:12 -0700 (PDT)
Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <T118064e11264c457567cf@mailgate1.apple.com>;
 Fri, 19 May 2000 11:13:56 -0700
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv1.apple.com (8.9.3/8.9.3) with ESMTP id LAA06300;
	Fri, 19 May 2000 11:14:10 -0700 (PDT)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com
Message-Id: <p04310106b54b2b6162df@[17.202.35.52]>
In-Reply-To: <C166CCE3B1B0D311B16C0060974B1C63DD9FC0@R-MHS>
References: <C166CCE3B1B0D311B16C0060974B1C63DD9FC0@R-MHS>
Date: Fri, 19 May 2000 11:13:21 -0700
To: "'4on2andIP-sys@advent.ee.columbia.edu'" <4on2andIP-sys@advent.ee.columbia.edu>
From: Dave Singer <singer@apple.com>
Subject: MPEG-4 (including Flexmux), over RTP/RTSP
Cc: "'Colin Perkins'" <C.Perkins@cs.ucl.ac.uk>,
        CURET Dominique FTRD/DMI/REN <dominique.curet@rd.francetelecom.fr>,
        peterw@us.ibm.com, rem-conf@es.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a portmanteau message, trying to cover the whole space of 
carriage of MPEG-4 in IETF protocols.  I'm trying to pull everything 
together.

It started by the resurgence of comment on FlexMux in RTP, so I'll 
start with packing formats.


PACKING FORMATS

I have been thinking about packing formats for MPEG-4 data, and I 
feel that we need to be a little more flexible.  I'd suggest that at 
least the following have value:

a) a simple packing of a single, arbitrary, elementary stream into 
RTP packets.  The packing would not be stream-format-aware, and so 
could carry any one ES.  [MPEG4-GENERIC]

b) a packing of MPEG-4 video, with care to place RTP packet 
boundaries at sub-frame boundaries, such that partial frame display 
is possible at the reciever.  I suspect that the video group's "video 
packet" meets the need, and may not require any RTP-specific header. 
However, it should be a distinct payload name so that receivers can 
know that video-aware packetization has happened.  [MPEG4-VIDEO]

c) a packing of MPEG-4 audio which interleaves the audio frames.  See 
the existing specifications for QCELP and the draft from Ross 
Finlayson for MP3 for examples.  Many audio decoders can do some 
sensible fill-in for single missing frames, but this fill-in error 
concealment rapdily gets worse if multiple consecitive frames are 
lost.  By intrerleaving, the decoder gets a sporting chance to 
conceal errors.  A small RTP header is needed to indicate that this 
has happened.  (With a suitable choice of header, it's possible that 
packing (a) could be a special case of this.)  [MPEG4-AUDIO]

d) a packing of flexmux into RTP.  This enables the carriage of large 
numbers of streams, where the use of separate RTP streams becomes 
prohibitive.  [MPEG4-FLEXMUX]

It may be that some formats become common enough, and have such 
characteristics, that a unique payload format for it becomes 
warranted (e.g. AAC).  That should be possible down the road.

For those streams requiring reliable delivery, I'd like to see us 
leverage existing work in the IETF in this area (including, but not 
limited to FEC, re-transmission, or repetition), rather than making 
it a characteristic of the packing scheme itself.

I'd like to think that all these, though separate payload schemes 
with separate names (in the RTPMAP) can be otherwise treated 
uniformly, in terms of timescale and timestamp, ES-ID to RTP mapping, 
and so on.


TIME-STAMP HANDLING

I think we are all agreed on this: that the MPEG-4 timescale for an 
ES becomes the RTP timescale, that the composition time maps to the 
RTP time, and the decode time maps to transmission order.


SDP INFORMATION

I think we can assume, for the moment, that any session described by 
SDP (e.g. in SAP, as a file download, as a DESCRIBE over RTSP) has at 
most one MPEG-4 session, though I'd like to see how we could lift 
this restriction.

We need
i) RTP stream to elementary stream mapping.  This needs to cover the 
Flexmux case as well as the single stream.
a=x-mpeg4-esid a.b.c
or
a=x-mpeg4-esids m.i:a.b.c,n.k:p.q

The first attribute is used for single streams; the second for 
flexmux.  In this, a is the ESID of the top-level OD stream, b is the 
ESID within that scope of another OD stream, and c is the ESID within 
that scope of the stream;  similarly for p and q.  m and n are 
muxcodes (identifying the table used), and i and k are flexmux 
channel numbers within the indicated muxcode.

The entire muxcode table(s) also need to be transferred.  For the 
moment, I propose another attribute for them.  Since these tables 
have a length indicator, multiple tables can be concatenated 
together, if required.
a=x-mpeg4-muxcodetable <location>

where <location> is a URL that will supply the table(s).  If they are 
small, a DATA: URL will probably suffice to carry them in-line. If 
not, the URL should use a file-retrieval scheme (e.g. HTTP, FTP). 
The data at the indicated URL consists of some number of muxcode 
tables, complete, in binary format (but note that DATA URLs allow for 
base64 encoding of binary data, which would be needed here).  The 
mime type of a muxcode table needs deciding 
(application/x-mpeg4-muxcodetable?).


ii)  Some indication that an MPEG-4 session is carried, and the means 
to get the IOD, if the terminal doesn't already have it by some other 
means.
In SDP, as a session-level attribute:
      a=x-mpeg4-iod [<location>]
      In an RTSP session, the location is optional.  If not supplied, 
the IOD is retrieved over the RTSP session by using either DESCRIBE 
with an accept of type application/x-mpeg4-iod, or a GET-PARAMETER 
(we need to decide which). Where the SDP information is supplied by 
some other means (e.g. as a file, in SAP), the location is obligatory 
and should be a URL which will supply the IOD (e.g. small ones may be 
encoded using DATA:, or otherwise HTTP: or other suitable file-access 
URL).
-- 
David Singer
Apple Computer/QuickTime



From rem-conf Fri May 19 15:32:45 2000 
From rem-conf-request@es.net Fri May 19 15:32:45 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sv8h-0007mf-00; Fri, 19 May 2000 15:21:03 -0700
Received: from mail-out1.apple.com [17.254.0.52] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sv8g-0007mV-00; Fri, 19 May 2000 15:21:02 -0700
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id PAA24715
	for <rem-conf@es.net>; Fri, 19 May 2000 15:21:00 -0700 (PDT)
Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0004686416@mailgate2.apple.com>;
 Fri, 19 May 2000 15:20:59 -0700
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv3.apple.com (8.9.3/8.9.3) with ESMTP id PAA05761;
	Fri, 19 May 2000 15:20:58 -0700 (PDT)
MIME-Version: 1.0
X-Sender: singer@mail.apple.com
Message-Id: <p04310108b54b6819e512@[17.202.35.52]>
In-Reply-To: <4.3.1.20000310134941.00be8e50@shell7.ba.best.com>
References: <3.0.6.32.20000303155648.00953ba0@shell7.ba.best.com>
 <3.0.6.32.20000306174707.0091f100@shell7.ba.best.com>
 <4.3.1.20000310134941.00be8e50@shell7.ba.best.com>
Date: Fri, 19 May 2000 15:17:48 -0700
To: Ross Finlayson <finlayson@live.com>
From: Dave Singer <singer@apple.com>
Subject: Re: Interleaving MP3 for RTP
Cc: Stefan Gewinner <gew@iis.fhg.de>, rem-conf@es.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

>http://www.live.com/rtp-mp3/rtp-mp3.txt

Ross

Overall, I like this draft, but on thinking it over, I think there 
are a few comments to make.


The draft attempts to retain some compatibility with the MPEG 
packings, but since it is a different packing, I'm not sure what this 
compatibility really gains us.  The most obvious point here is the 
4-byte header, which really only serves a useful function if an MP3 
frame is split across multiple RTP packets.  Given that MP3 frames 
are usually small, and we'd only split if a frame won't fit into a 
packet by itself, I expect such splitting to be extremely rare.  I'd 
rather see us use a bit in the header of a frame to say that this 
'frame' is actually a continuation of a previous fragment with the 
same sequence number.

In the header byte, you do need to know the number of this frame 
within its group, but I don't think you need a group number.  You can 
tell exactly where this MP3 belongs in time without it, so there is 
no danger of de-interleaving two groups together.  Basically, the RTP 
timestamp R is (as always) the timestamp of the oldest (earliest) MP3 
frame within the packet.  Say that this has group index M, and the 
frame you want to time has group index N.  Since the MP3 frames have 
constant duration D, the RTP time of this frame is (N-M)*D + R.

You don't discuss timescale and timestamps, and so I think you expect 
the scale to be 90kHz, like general MPEG.  I think it would be better 
if it were the sampling rate of the audio, just like other audio 
packing formats.

It might (?) help de-interleavers, and provide a consistency check, 
if there was a bit used in the header to indicate that more MP3 
frames occur in this packet (or not).

I also think that it can really help the de-packetizer if it knows 
the interleave group size.  I think that this can be indicated in 
very few bits, like 2.  Say these have value I.  Since any group size 
does for the case where we are not going to interleave (we can always 
pack sequential MP3 frames into packets), we don't need a group size 
value of 0 or 1.  If this has value X, I'd say it would indicate to 
the receiver that the maximum de-interleave buffer it needs is of 
size 2**(X+2), i.e. 4,8,16,32.

Comments?
-- 
David Singer
Apple Computer/QuickTime



From rem-conf Fri May 19 17:51:47 2000 
From rem-conf-request@es.net Fri May 19 17:51:45 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12sxPY-00020R-00; Fri, 19 May 2000 17:46:36 -0700
Received: from prognet.com [205.219.198.1] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12sxPW-00020E-00; Fri, 19 May 2000 17:46:34 -0700
Received: from stromtrooper ([63.201.5.254])
	by prognet.com (8.9.2/8.9.0) with ESMTP id RAA14905;
	Fri, 19 May 2000 17:46:40 -0700 (PDT)
Message-Id: <4.2.0.58.20000519175211.00a26d00@mail.real.com>
X-Sender: csloan@mail.real.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Fri, 19 May 2000 17:54:46 -0700
To: finlayson@live.com
From: Chris Sloan <csloan@real.com>
Subject: Loss Tolerant MP3 Streaming
Cc: gew@iis.fhg.de, rem-conf@es.net, singer@apple.com, ceddy@real.com,
        jeff Ayars <jeffa@real.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Ross,

I am an employee of RealNetworks.  I am looking at your draft of "A More 
Loss Tolerant RTP Payload Format for MP3 Audio" and I would like to make 
suggestions on two things.

1. ADU Frame Interleaving
Instead of modifying the syncword to indicate the interleave cycle count 
and index, use one of the reserved bytes in the payload header.  As it 
stands today, there are two payload header bytes not being used by mpeg 
audio which are intended for uses such as this one.  Having worked with 
mpeg audio for years, tampering with the FFF? seems sacrilegious.

2. Frame Fragmentation
Since ADU frames vary in size, knowing when an ADU frame begins and ends is 
more useful than a fragmentation offset.  I propose adding ADU frame 
begin/end bits in the payload header the same way video slice begin/end 
bits are used for video slices in RFC 2250.   This way, the client can 
decode ADU frames directly from RTP packet buffers if the frames are 
self-contained.  Also, these bits would prevent the client from having to 
determine the size of the ADU frames by buffering RTP packets and looking 
at time stamps (and not messing up during packet loss).  If you are 
concerned with the number of available payload header bits, you can do away 
with the fragmentation offset bits and just use ADU frame begin/end bits.

These two changes would make it easier on developers writing MP3 servers
and clients, reduce the amount of buffering on the client side, and
preserve the integrity of the MP3 payload.

Please contact me with any questions or comments.
Thanks.

Chris Sloan
RealNetworks, Inc.
805 783 4916
csloan@real.com






From rem-conf Fri May 19 22:01:10 2000 
From rem-conf-request@es.net Fri May 19 22:01:08 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12t1Ib-00055o-00; Fri, 19 May 2000 21:55:41 -0700
Received: from proxy2.ba.best.com [206.184.139.14] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12t1Ia-00055e-00; Fri, 19 May 2000 21:55:40 -0700
Received: from kaipara.live.com (mg134-199.ricochet.net [204.179.134.199])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id VAA24655;
	Fri, 19 May 2000 21:55:19 -0700 (PDT)
Message-Id: <4.3.1.1.20000519195408.00b44930@shell7.ba.best.com>
X-Sender: rsf@shell7.ba.best.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 19 May 2000 21:47:24 -0700
To: Dave Singer <singer@apple.com>
From: Ross Finlayson <finlayson@live.com>
Subject: Re: Interleaving MP3 for RTP
Cc: Stefan Gewinner <gew@iis.fhg.de>, rem-conf@es.net
In-Reply-To: <p04310108b54b6819e512@[17.202.35.52]>
References: <4.3.1.20000310134941.00be8e50@shell7.ba.best.com>
 <3.0.6.32.20000303155648.00953ba0@shell7.ba.best.com>
 <3.0.6.32.20000306174707.0091f100@shell7.ba.best.com>
 <4.3.1.20000310134941.00be8e50@shell7.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

At 03:17 PM 5/19/00, Dave Singer wrote:
>The draft attempts to retain some compatibility with the MPEG packings, 
>but since it is a different packing, I'm not sure what this compatibility 
>really gains us.

Dave (cc. "rem-conf" et al),

Here's the motivation for basing the new payload format on RFC2250:  RFC 
2250 is the existing standards-track format for streaming MPEG 1 or 2 audio 
using RTP, so any application that wishes to receive RTP-streamed MPEG 
audio (including MP3 - i.e., MPEG 1 or 2 layer III) already *has to* 
implement the RFC 2250 format.  However, because RFC 2250 doesn't handle 
MP3 well, we'd like implementors to also support the use of the new, 
alternative payload format for streaming MP3.  This seems like a much 
easier sell if the new payload format is based upon the existing payload 
format (RFC 2250) that implementors are already familiar with - it makes 
the new format easier to understand and implement.  (In particular, because 
the new payload format uses the same packetization/depacketization scheme 
as RFC 2250, much of an existing RFC 2250 implementation can be used.)

I.e., basing the new payload format on RFC 2250 seems like "the path of 
least resistance" to having it become widely implemented and used.

>   The most obvious point here is the 4-byte header, which really only 
> serves a useful function if an MP3 frame is split across multiple RTP packets
>Given that MP3 frames are usually small, and we'd only split if a frame 
>won't fit into a packet by itself, I expect such splitting to be extremely 
>rare.

Agreed - this is probably the worst aspect of RFC 2250: The presence of a 
4-byte "MPEG audio-specific header" (for fragmentation) that's usually just 
wasted space.  Fortunately, however, this wastage is typically quite small: 
Just 0.4% in a 1000-byte RTP packet, and less than 0.3% in a 1500-byte RTP 
packet.  If you're in an environment where this level of wastage is 
considered important, then you're probably better off using a more 
efficient codec than MP3 anyway (e.g., AAC or MPEG-4 GA).

>   I'd rather see us use a bit in the header of a frame to say that this 
> 'frame' is actually a continuation of a previous fragment with the same 
> sequence number.

Note that any 'continuation' frame has to include a byte offset, because 
otherwise you wouldn't know how many bytes were in any preceding RTP 
packet(s) that got lost.  (Note also that in RTP, sequence numbers 
increase, even for packets that make up the same 'frame'.)

>You don't discuss timescale and timestamps

Actually, I mention timestamps (briefly) in section 6.  Because it's an 
important point that's relevant both to your comments and to Chris Sloan's 
(which I'll respond to in my next message), I'll repeat it here:

         "Step 3 is the packetizing of a sequence of (interleaved) ADU frames
         into RTP packets - exactly as specified in RFC 2250.  When
         computing the RTP timestamps for each packet, this step ignores
         any reordering that took place in step 2, and treats the sequence
         of packetized ADU frames as if they were generated sequentially.
         I.e., the RTP timestamps on outgoing packets are always
         monotonically increasing, regardless of interleaving."

This makes an implementation much simpler.  It allows the 
packetizing/depacketizing code (which can also be shared with an existing 
implementation of RFC 2250) to be independent of the reordering/tagging code.

>  You don't discuss timescale and timestamps, and so I think you expect 
> the scale to be 90kHz, like general MPEG.  I think it would be better if 
> it were the sampling rate of the audio, just like other audio packing formats.

Note, however, that in either RFC 2250 or the new format it's possible 
(although strange) for a RTP packet to include consecutive frames that were 
encoded using different sampling frequencies.  In any case (in either 
format), the actual sampling frequency is always known from the (MP3 or 
ADU) 'frame'; the RTP timestamp is not needed for this purpose.

>In the header byte, you do need to know the number of this frame within 
>its group, but I don't think you need a group number.  You can tell 
>exactly where this MP3 belongs in time without it, so there is no danger 
>of de-interleaving two groups together.

The group number (which I refer to as an "Interleave Cycle Count") is for 
the benefit of receivers.  It allows a receiver to easily distinguish 
between frame(s) that are missing merely because they haven't yet appeared 
in the reordering, and frames that are missing because they were in lost 
packets.  E.g., suppose a receiver sees a sequence of frames with 
"Interleave Index" 1, 3, 4 (i.e., with 2 missing).  If it then starts 
seeing frames with a different "Interleave Cycle Count", it then knows for 
sure that frame 2 has been lost, and so can immediately release frames 
1,3,4 to the decoder (or ADU->MP3 converter), rather than having to wait 
around to see if frame 2 ends up appearing later in the order.

I think this also addresses your later question about receivers knowing the 
interleave group size.  In this scheme the receiver knows the maximum 
possible group size (this is a fixed number, given by the number of bits in 
the "Interleave Index"), but doesn't know *in advance* the size of the 
current cycle.  It does, however, know when the currently cycle ends , by 
the change in the "Interleave Cycle Count".

         Ross.




From rem-conf Fri May 19 22:01:10 2000 
From rem-conf-request@es.net Fri May 19 22:01:08 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12t1If-000560-00; Fri, 19 May 2000 21:55:45 -0700
Received: from proxy2.ba.best.com [206.184.139.14] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12t1Ie-00055q-00; Fri, 19 May 2000 21:55:44 -0700
Received: from kaipara.live.com (mg134-199.ricochet.net [204.179.134.199])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id VAA24722;
	Fri, 19 May 2000 21:55:24 -0700 (PDT)
Message-Id: <4.3.1.1.20000519211033.00b46bd0@shell7.ba.best.com>
X-Sender: rsf@shell7.ba.best.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 19 May 2000 21:48:57 -0700
To: Chris Sloan <csloan@real.com>
From: Ross Finlayson <finlayson@live.com>
Subject: Re: Loss Tolerant MP3 Streaming
Cc: gew@iis.fhg.de, rem-conf@es.net, singer@apple.com, ceddy@real.com,
        jeff Ayars <jeffa@real.com>
In-Reply-To: <4.2.0.58.20000519175211.00a26d00@mail.real.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Chris (cc. "rem-conf" et al),

I think you may have misinterpreted the description of the way that 'ADU 
frames' are packetized into RTP packets.

Let's start by reviewing the packetization of MPEG audio frames in RFC 
2250.  In RFC 2250, each RTP packet contains:
         1/ a regular RTP header
         2/ a 4-byte MPEG audio-specific header (see RFC 2250, section 3.5)
then either
         3a/ an *integral number* of MPEG frames
or
         3b/ a fragment of a single, fragmented MPEG frame
                 (with byte offset given by the "MPEG audio-specific header")

The new, alternative payload format for MP3 uses *exactly the same* 
packetization, except using "ADU frames" instead of "MPEG (MP3) 
frames".  (Note that "ADU frames" are defined in section 4 of the Internet 
Draft.)

This has the following consequences:

- The Interleave Cycle Count and Index - being properties of a (ADU) frame 
- cannot be stored in the RTP header (or MPEG audio-specific header), 
because there can be an arbitrary (integral) number of frames in a given 
RTP packet.  Instead, this information has to be stored within the frames 
themselves.  Fortunately, there are 'otherwise always-1' bits within the 
MPEG header that can be used to store this.  ('Tampering' with these bits 
isn't a problem, because it loses no information, and a receiver will 
always restore these bits (to 'all-1s') before they get fed to a decoder.)

- Except in case 3b (a single large frame being fragmented over more than 
one RTP packet), each RTP packet contains exactly an integral number of ADU 
frames.  So, these can be identified and extracted from the RTP packet 
immediately.

I think I am partially to blame for the confusion.  Because the new payload 
format is based so heavily upon RFC 2250, it seems clear to me now that the 
Internet Draft should have included an overview - similar to the one above 
- of RFC 2250's MPEG audio packetization scheme.  A familiarity with this 
is important for understanding the rest of the draft, so I'll be sure to 
add this to the next revision.

         Ross.




From rem-conf Sat May 20 06:49:39 2000 
From rem-conf-request@es.net Sat May 20 06:49:37 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12t9OF-0003k0-00; Sat, 20 May 2000 06:34:03 -0700
Received: from cmlab.csie.ntu.edu.tw [140.112.29.131] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12t9OD-0003jq-00; Sat, 20 May 2000 06:34:01 -0700
Received: from cmln4 (cmln4 [140.112.29.184])
	by cmlab.csie.ntu.edu.tw (8.9.3+Sun/8.9.3) with SMTP id VAA28796
	for <rem-conf@es.net>; Sat, 20 May 2000 21:31:49 +0800 (CST)
Message-ID: <002f01bfc260$279d6a60$b81d708c@CMLAB.CSIE.NTU.EDU.TW>
From: "CCFang" <ccfang@cmlab.csie.ntu.edu.tw>
To: <rem-conf@es.net>
Subject: One question of CRTP
Date: Sat, 20 May 2000 21:34:41 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002C_01BFC2A3.354B0530"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_002C_01BFC2A3.354B0530
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

Dear all...

    I have a question of CRTP.
    How does the destination know the packet received is a compress =
packet or full-header packet?
   =20
    Best Regards

Justin Fang

------=_NextPart_000_002C_01BFC2A3.354B0530
Content-Type: text/html;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dbig5" http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dear all...</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; I have a question of =

CRTP.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; How does the =
destination know=20
the packet received is a compress packet or full-header =
packet?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; Best =
Regards</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Justin Fang</FONT></DIV></BODY></HTML>

------=_NextPart_000_002C_01BFC2A3.354B0530--




From rem-conf Sat May 20 10:00:56 2000 
From rem-conf-request@es.net Sat May 20 10:00:55 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12tCTD-00063v-00; Sat, 20 May 2000 09:51:23 -0700
Received: from omega.cisco.com [171.69.63.141] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12tCTB-00063V-00; Sat, 20 May 2000 09:51:21 -0700
Received: from localhost (localhost [127.0.0.1])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id JAA14050;
	Sat, 20 May 2000 09:49:49 -0700 (PDT)
Date: Sat, 20 May 2000 09:49:49 -0700 (PDT)
From: Dan Wing <dwing@cisco.com>
To: CCFang <ccfang@cmlab.csie.ntu.edu.tw>
cc: rem-conf@es.net
Subject: Re: One question of CRTP
In-Reply-To: <002f01bfc260$279d6a60$b81d708c@CMLAB.CSIE.NTU.EDU.TW>
Message-ID: <0005200949320.12815-100000@omega.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

On Sat, 20 May 2000 21:34 +0800, CCFang wrote:

> Dear all...
> 
>     I have a question of CRTP.
>
>     How does the destination know the packet received is a compress
> packet or full-header packet?

It's identified by the protocol type in the PPP header.

-Dan Wing

>     
>     Best Regards
> 
> Justin Fang
> 




From rem-conf Sat May 20 13:51:58 2000 
From rem-conf-request@es.net Sat May 20 13:51:56 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12tG7D-0001vW-00; Sat, 20 May 2000 13:44:55 -0700
Received: from (ftp.genuine.com.tw) [210.63.128.2] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12tG7C-0001uL-00; Sat, 20 May 2000 13:44:54 -0700
Received: from ftp.genuine.com.tw by ftp.genuine.com.tw (NTMail 3.02.11) with ESMTP id da305009 for <rem-conf@es.net>; Sun, 21 May 2000 01:03:43 +0800
Date: Sun, 21 May 00 11:31:11 EST
From: ReduceDebt@ollo.fsnet.co.uk
To: ReduceDebt@ollo.fsnet.co.uk
Subject: FREE!  Confidential Debt Reduction Analysis
X-Info: Evaluation version at ftp.genuine.com.tw
Message-Id: <17034325701986@genuine.com.tw>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Sign-up for a Completely FREE, Confidential Debt Reduction Analysis. 
***Limited Time FREE Offer.***

http://3518593971/bin/redirector.cgi?http://3506561041/redirector_cgi?

Our Non-Profit Organization can do
the following JUST BY ASKING YOUR CREDITORS:

(*)Cut your bills in half.
(*)Consolidate your bills into ONE LOW monthly payment.
(*)Eliminate interest and late fee charges.
(*)Improve your credit rating.
(*)NO Need To Own Any Property


A trained professional negotiates with your creditors to:

	1)Lower your monthly debt payments by 40-60%
	2)End creditor harassment
	3)Save thousands of dollars in interest and late charges
	4)Start improving your credit rating.


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
If you have received this message in error and would
like to be removed from future mailings, please reply
with the word remove in the subject. 
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/



From rem-conf Sun May 21 02:50:01 2000 
From rem-conf-request@es.net Sun May 21 02:50:00 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12tSEu-0001tD-00; Sun, 21 May 2000 02:41:40 -0700
Received: from (syntechon.co.kr) [210.217.139.1] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12tSEr-0001sy-00; Sun, 21 May 2000 02:41:38 -0700
Received: from localhost by syntechon.co.kr (SMI-8.6/SMI-SVR4)
	id SAA18670; Sun, 21 May 2000 18:43:04 +0900
From: cmichaels7@mail.md
Message-ID: <00000d1043ce$00000189$00005cf2@localhost>
To: <clients@swbell.net>
Subject: Truly Life Changing, $10K+ Monthly. 
Date: Sun, 21 May 2000 05:07:37 -0700
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

<HTML><FONT  SIZE=3D3 PTSIZE=3D10><B>You are invited to call toll free:   <=
/FONT><FONT  SIZE=3D4 PTSIZE=3D11>1-800-281-7098</FONT><FONT  SIZE=3D3 PTS=
IZE=3D10><BR>
<BR>
Where you will learn about:<BR>
<BR>
 An honest Ethical Home Business - Not Multi-Level-Marketing<BR>
<BR>
 * Committed Individual Earns $10,000+ Monthly in 30 to 90 Days<BR>
<BR>
 * </FONT><FONT  SIZE=3D4 PTSIZE=3D11>80% Profits !</FONT><FONT  SIZE=3D3 =
PTSIZE=3D10><BR>
<BR>
 * Turn-key Lead Generation System - Prospects Call You<BR>
<BR>
 * 2.4 Million-Dollar Teleconferencing System Does Selling For You<BR>
<BR>
 * Daily Support and Training<BR>
<BR>
You must supply the work ethic and commitment.<BR>
<BR>
We are not selling travel, lotions, potions or vitamins. We have an<BR>
exclusive product/service attractive to anyone with an income.<BR>
<BR>
You owe it to yourself and family to find out more.<BR>
You are invited to call toll free:  </FONT><FONT  SIZE=3D4 PTSIZE=3D11>1-8=
00-281-7098</FONT><FONT  SIZE=3D3 PTSIZE=3D10><BR>
<BR>
I look forward to our interview,<BR>
<BR>
Clay<BR>
******************************<BR>
</B>to be removed from mailing click <A HREF=3D"mailto:cmichaels7@mail.md?=
subject=3Dremove">REMOVE</A><B><B><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</B></B></HTML>






From rem-conf Mon May 22 06:21:27 2000 
From rem-conf-request@es.net Mon May 22 06:21:25 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12trx6-0002PA-00; Mon, 22 May 2000 06:09:00 -0700
Received: from sitemail.everyone.net (omta01.mta.everyone.net) [216.200.145.35] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12trx3-0002P0-00; Mon, 22 May 2000 06:08:58 -0700
Received: from sitemail.everyone.net (reports.everyone.net [216.200.145.62])
	by omta01.mta.everyone.net (Postfix) with ESMTP id 5E9D026F0
	for <rem-conf@es.net>; Mon, 22 May 2000 06:08:57 -0700 (PDT)
Received: by sitemail.everyone.net (Postfix, from userid 60001)
	id B2A9B50AB; Mon, 22 May 2000 06:06:03 -0700 (PDT)
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
X-Mailer: MIME-tools 4.104 (Entity 4.117)
Date: Mon, 22 May 2000 06:06:03 -0700 (PDT)
From: abhishek rungta <abhishek@ashree.com>
To: rem-conf@es.net
Subject: Live Video Webcasting
Reply-To: abhishek@ashree.com
X-Originating-Ip: [138.38.32.88]
Message-Id: <20000522130603.B2A9B50AB@sitemail.everyone.net>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Dear Members,

I introduce myself as a student of University of Bath,UK working on webcasting LIVE video. 

We have our own codec and we are trying to implement a webcasting system to telecast live events. I am in the very begining of this project and will require some help and advice from anybody who is willing to help me on ocassions when i get stuck.

I have a model in mind which will take data from our codec, and pass it on to the RTP protocol layer, followed by the UDP and finally the IP protocol layer using the multicast facilities.

>From my understanding i have downloaded some RFC's such as one on RTP and RTCP protocol and others. I would like to know what all reference material do i need to have and read, to move ahead in this kind of a project. Any suggested reading (preferably in a order) or website containing some material regarding the same.

Any RTP protocol implementation source code for reference. (A call to the OpenSource community)

Any guidance and help will be greatly appriciated.

Thanking everybody for taking time to read this mail and expecting a early reply.

Regard's
Abhishek Rungta
Postgraduate Student
University of Bath
Bath Spa, UK.


_____________________________________________________________
Email Powered by Everyone.net



From rem-conf Mon May 22 14:09:46 2000 
From rem-conf-request@es.net Mon May 22 14:09:45 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12tz9z-0000T8-00; Mon, 22 May 2000 13:50:47 -0700
Received: from mail-out1.apple.com [17.254.0.52] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12tz9x-0000Sy-00; Mon, 22 May 2000 13:50:45 -0700
Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225])
	by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id NAA15507
	for <rem-conf@es.net>; Mon, 22 May 2000 13:50:39 -0700 (PDT)
Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <T118064e115b4c5577a1ed@mailgate1.apple.com>;
 Mon, 22 May 2000 13:50:18 -0700
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by scv3.apple.com (8.9.3/8.9.3) with ESMTP id NAA19329;
	Mon, 22 May 2000 13:50:32 -0700 (PDT)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com
Message-Id: <p04310129b54f4bccd622@[17.202.35.52]>
In-Reply-To: <4.3.1.1.20000519195408.00b44930@shell7.ba.best.com>
References: <4.3.1.20000310134941.00be8e50@shell7.ba.best.com>
 <3.0.6.32.20000303155648.00953ba0@shell7.ba.best.com>
 <3.0.6.32.20000306174707.0091f100@shell7.ba.best.com>
 <4.3.1.20000310134941.00be8e50@shell7.ba.best.com>
 <4.3.1.1.20000519195408.00b44930@shell7.ba.best.com>
Date: Mon, 22 May 2000 13:48:53 -0700
To: Ross Finlayson <finlayson@live.com>
From: Dave Singer <singer@apple.com>
Subject: Re: Interleaving MP3 for RTP
Cc: Stefan Gewinner <gew@iis.fhg.de>, rem-conf@es.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

At 21:47 -0700 5/19/00, Ross Finlayson wrote:
>At 03:17 PM 5/19/00, Dave Singer wrote:
>>The draft attempts to retain some compatibility with the MPEG 
>>packings, but since it is a different packing, I'm not sure what 
>>this compatibility really gains us.
>
>Dave (cc. "rem-conf" et al),
>
>Here's the motivation for basing the new payload format on RFC2250: 
>RFC 2250 is the existing standards-track format for streaming MPEG 1 
>or 2 audio using RTP, so any application that wishes to receive 
>RTP-streamed MPEG audio (including MP3 - i.e., MPEG 1 or 2 layer 
>III) already *has to* implement the RFC 2250 format.  However, 
>because RFC 2250 doesn't handle MP3 well, we'd like implementors to 
>also support the use of the new, alternative payload format for 
>streaming MP3.  This seems like a much easier sell if the new 
>payload format is based upon the existing payload format (RFC 2250) 
>that implementors are already familiar with - it makes the new 
>format easier to understand and implement.  (In particular, because 
>the new payload format uses the same packetization/depacketization 
>scheme as RFC 2250, much of an existing RFC 2250 implementation can 
>be used.)
>
>I.e., basing the new payload format on RFC 2250 seems like "the path 
>of least resistance" to having it become widely implemented and used.

I think at the point where I'm implementing a new payload format, its 
similarity to others is probably moot as long as it is simple.

>>   The most obvious point here is the 4-byte header, which really 
>>only serves a useful function if an MP3 frame is split across 
>>multiple RTP packets
>>Given that MP3 frames are usually small, and we'd only split if a 
>>frame won't fit into a packet by itself, I expect such splitting to 
>>be extremely rare.
>
>Agreed - this is probably the worst aspect of RFC 2250: The presence 
>of a 4-byte "MPEG audio-specific header" (for fragmentation) that's 
>usually just wasted space.  Fortunately, however, this wastage is 
>typically quite small: Just 0.4% in a 1000-byte RTP packet, and less 
>than 0.3% in a 1500-byte RTP packet.  If you're in an environment 
>where this level of wastage is considered important, then you're 
>probably better off using a more efficient codec than MP3 anyway 
>(e.g., AAC or MPEG-4 GA).

Well, perhaps.  Compressed audio doesn't tend to use very large (1K) 
packets, because of buffering delay considerations.  I am unconvinced 
that it is a good idea to waste space because it doesn't matter very 
much!  I'd prefer a 'tight' design at the outset.

>>   I'd rather see us use a bit in the header of a frame to say that 
>>this 'frame' is actually a continuation of a previous fragment with 
>>the same sequence number.
>
>Note that any 'continuation' frame has to include a byte offset, 
>because otherwise you wouldn't know how many bytes were in any 
>preceding RTP packet(s) that got lost.  (Note also that in RTP, 
>sequence numbers increase, even for packets that make up the same 
>'frame'.)

Not really.  You can't use the second fragment if you don't get the 
first, and then you'll know the length.  You'll know that a fragment 
is missing if either (a) you get a continuation piece without the 
start piece or (b) the packet sequence number of the continuation is 
not 1 greater than the sequence number of the previous piece.

>>You don't discuss timescale and timestamps
>
>Actually, I mention timestamps (briefly) in section 6.  Because it's 
>an important point that's relevant both to your comments and to 
>Chris Sloan's (which I'll respond to in my next message), I'll 
>repeat it here:
>
>         "Step 3 is the packetizing of a sequence of (interleaved) ADU frames
>         into RTP packets - exactly as specified in RFC 2250.  When
>         computing the RTP timestamps for each packet, this step ignores
>         any reordering that took place in step 2, and treats the sequence
>         of packetized ADU frames as if they were generated sequentially.
>         I.e., the RTP timestamps on outgoing packets are always
>         monotonically increasing, regardless of interleaving."
>
>This makes an implementation much simpler.  It allows the 
>packetizing/depacketizing code (which can also be shared with an 
>existing implementation of RFC 2250) to be independent of the 
>reordering/tagging code.

OK, I think we are in agreement about different things.  I think that 
we should say explicitly that the RTP time-stamp is the time-stamp of 
the oldest (first?) data in the packet *and* that interleaving should 
be done in such a way time-stamps are non-decreasing (they would only 
be the same for a split frame).

>>  You don't discuss timescale and timestamps, and so I think you 
>>expect the scale to be 90kHz, like general MPEG.  I think it would 
>>be better if it were the sampling rate of the audio, just like 
>>other audio packing formats.
>
>Note, however, that in either RFC 2250 or the new format it's 
>possible (although strange) for a RTP packet to include consecutive 
>frames that were encoded using different sampling frequencies.  In 
>any case (in either format), the actual sampling frequency is always 
>known from the (MP3 or ADU) 'frame'; the RTP timestamp is not needed 
>for this purpose.

But I think that there is a lot of benefit in sample-accurate 
time-stamping, and actually saying that if you change sample-rates 
you change payload ID (with a new RTPMAP) is a really good thing.

>>In the header byte, you do need to know the number of this frame 
>>within its group, but I don't think you need a group number.  You 
>>can tell exactly where this MP3 belongs in time without it, so 
>>there is no danger of de-interleaving two groups together.
>
>The group number (which I refer to as an "Interleave Cycle Count") 
>is for the benefit of receivers.  It allows a receiver to easily 
>distinguish between frame(s) that are missing merely because they 
>haven't yet appeared in the reordering, and frames that are missing 
>because they were in lost packets.  E.g., suppose a receiver sees a 
>sequence of frames with "Interleave Index" 1, 3, 4 (i.e., with 2 
>missing).  If it then starts seeing frames with a different 
>"Interleave Cycle Count", it then knows for sure that frame 2 has 
>been lost, and so can immediately release frames 1,3,4 to the 
>decoder (or ADU->MP3 converter), rather than having to wait around 
>to see if frame 2 ends up appearing later in the order.

But you can as easily work that out from the time-stamp, as I said; 
the time-stamp will tell you that the earliest frame in this packet 
belongs in a different group from the group in hand.

>I think this also addresses your later question about receivers 
>knowing the interleave group size.  In this scheme the receiver 
>knows the maximum possible group size (this is a fixed number, given 
>by the number of bits in the "Interleave Index"), but doesn't know 
>*in advance* the size of the current cycle.  It does, however, know 
>when the currently cycle ends , by the change in the "Interleave 
>Cycle Count".
>
>         Ross.

Sure, we know a max.  This may not be worth worrying about if the max 
is as small as 32.
-- 
David Singer
Apple Computer/QuickTime



From rem-conf Mon May 22 16:47:58 2000 
From rem-conf-request@es.net Mon May 22 16:47:57 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12u1ij-0002Xq-00; Mon, 22 May 2000 16:34:49 -0700
Received: from bells.cs.ucl.ac.uk [128.16.5.31] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12u1ih-0002Xg-00; Mon, 22 May 2000 16:34:47 -0700
Received: from host62-6-26-168.btinternet.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.02693-0@bells.cs.ucl.ac.uk>;
          Tue, 23 May 2000 00:34:33 +0100
Message-ID: <00f301bfc446$6efea440$a81a063e@oemcomputer>
Reply-To: Farez <f.abdulrahman@cs.ucl.ac.uk>
From: Farez <f.abdulrahman@cs.ucl.ac.uk>
To: agents <agents@cs.umbc.edu>, rem-conf <rem-conf@es.net>, 
    mymobile <mymobile@egroups.com>
Subject: 1 week to deadline: AMOC 2000, Malaysia. (CFP)
Date: Tue, 23 May 2000 00:19:49 +0100
Organization: University College London
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

                          Call for Papers

         FIRST ASIAN INTERNATIONAL MOBILE COMPUTING CONFERENCE
                            (AMOC 2000)
            31 October - 3 November, 2000. Penang, Malaysia
                
                Organised by University Malaya, Malaysia
                   In cooperation with ACM SIGMOBILE
                 With main support from MRCB Multimedia

                    http://www.fsktm.um.edu.my/amoc
            http://www.cs.ucl.ac.uk/staff/F.AbdulRahman/amoc


              *** Submission deadline: 30 May, 2000 ***

Important update: 
200 word abstract to be included in the separate 'Author details' 
plain text document.

Mobile computing is a new and highly dynamic field which combines
modern computer science, networking and wireless communication
technologies. This conference will provide a platform for researchers
and practitioners to meet and discuss current issues in this field. 
The conference is also unique as it highly encourages contributions 
>from the Asian region alongside those from other parts of the globe. 
The focus on Asia is important because there are unique regional 
issues not given attention in typical international conferences, where 
technological issues in developed nations receive centre stage. These 
issues include different infrastructural and economic requirements; 
the effect of a more diverse socio-economic environment on 
technical specifications; the far-reaching impact of wireless 
communication in rural areas and the great interest in the rapid 
deployment of cutting edge technology due to the high progress rate of 
technological implementation in many Asian countries. 

The main objectives of this conference are:

1. To provide a platform for international and Asian researchers and 
   professionals to meet and discuss issues pertinent to both universal 
   and Asia-centric mobile computing issues.
2. To provide participants with up-to-date information regarding the
   development in this field.
3. To provide a yardstick by which researchers may compare the quality
   of their work to that of their peers in order to maintain a high
   standard of research.

The topics of interest include, but are not limited to, those listed
below:

o Quality of Service(QoS)           o handover & location management
o systems infrastructure            o satellite technology
o internet access                   o power management
o data services                     o lower layer protocols
o rural wireless communications     o data management
o billing                           o security
o e-commerce                        o agent technology
o multimedia                        o hardware
o Personal Communication Systems    o terminal design & ergonomics
o wireless LANs / WANs              o nomadic systems

Important Dates
-------------------
Submission deadline: 30 May, 2000
Notification of acceptance: 15 July, 2000
Camera ready copy: 15 August, 2000

Submission Guidelines
----------------------------
Papers should be original, unpublished and not more than ten
single-spaced pages with a minimum font size of 10 pt. Papers must be 
in postscript format, and should only contain the paper
title and the body of the paper, WITHOUT author names and
affiliations. A separate plain text document containing only the 
title, author names, their respective affiliations and 200 word 
abstract, is required. Please send your paper (in postscript format) 
and your separate author page (in plain text format) in separate 
emails to amoc-submission@fsktm.um.edu.my by the 30th of May, 2000.

For more information, please visit http://www.fsktm.um.edu.my/amoc/ or
email amoc-submission@fsktm.um.edu.my

Best Student Paper Award
------------------------
The best paper with a student as primary author will be awarded a
really cool prize of US$500 during the conference. Student authors who
would like to be considered for this award should write 'Student Paper' 
in the plain text document containing the paper title and author 
name(s) and affiliation(s).

Tutorials
---------
There will be two half-day and one full-day tutorials on 31 October. 
The full-day tutorial will run in parallel with each of the half-day
tutorials. The tutorials are:

1. Client-server Computing in Wireless and Mobile Environments
   Prof. Abdelsalam Helal, University of Florida. 
   (Full Day)

2. Java based Mobile Computing - JINI, Mobile Objects and Agents 
   Dr. Omer F. Rana, University of Wales. 
   (Half Day)

3. Mobile Ad Hoc Wireless Networks 
   Dr. Somprakash Bandyopadhyay from PriceWaterhouse Coopers Ltd.,
   Dr. Krishna Paul from Cognizant Technology Solutions, India. 
   (Half Day)


Organising Committee
--------------------
Prof. Ir. Dr. Mashkuri Hj. Yaacob (Universiti Malaya)
Dr Mazliza Othman (Universiti Malaya)
Alfarez Abdul Rahman (University College London)
Dr Roziati Zainuddin (Universiti Malaya)
Dr. Zaitun Abu Bakar (Universiti Malaya)
Rodziah Latih (Universiti Kebangsaan Malaysia)
Norizan Mohd Yasin (Universiti Malaya)
Omar Zakaria (Universiti Malaya)
Mustaffa Kamal (Universiti Malaya)

Technical Program Committee
---------------------------
Assc. Prof. David K. Asano, Shinshu University, Japan
Prof. Boualem Boashash, Queensland University of Technology, Australia 
Prof. Sung-Kwon Chung, Infomore, Inc., Korea 
Dr. Che Nyan Husain, Telekom Malaysia 
Prof. Chuah Hean Teik, Universiti Multimedia Telekom, Malaysia 
Prof. Jon Crowcroft, University College London, UK
Prof. Sajal Das, University of North Texas, USA 
Assc. Prof. Norsheila Faisal, Universiti Teknologi Malaysia
Prof. Sandeep Gupta, Colorado State University, USA 
Dr. Stephen Hailes, University College London, UK
Prof. Abdelsalam Helal, University of Florida, USA
Ravi Jain, Telcordia, USA 
Dr. Minseok Kang, LG Corporate Institute of Technology, Korea 
Prof. Ryuji Kohno, Yokohama University, Japan 
Dr. Jong-Hyeon Lee, Cambridge University, UK 
Bo Li, Hong Kong University of Science & Technology
Prof Jason Yi-Bing Lin, National Chiao Tung University, Taiwan
Dr. Seng-Wai Loke, DSTC Monash University, Australia
Dr. Jelena Misic, Hong Kong University of Science & Technology
Assc. Prof. George Mohay, Queensland University of Technology, Australia 
Susan Pancho, Cambridge University, UK
Prof. Pradip Srimani, Colorado State University, USA
Dr. Fumio Teraoka, Sony Computer Science Labs, Inc., Japan
Prof. C-K Toh, Georgia Institute of Technology 
Prof. Yu-Chee Tseng, National Central University, Taiwan 
Dr. Arkady Zaslavsky, Monash University, Australia 
Dr. Jianying Zhou, Kent Ridge Digital Lab, Singapore 





From rem-conf Tue May 23 02:09:12 2000 
From rem-conf-request@es.net Tue May 23 02:09:11 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12uAXI-0006wk-00; Tue, 23 May 2000 01:59:36 -0700
Received: from mail.iqpc.co.uk [212.158.26.251] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12uAXG-0006wY-00; Tue, 23 May 2000 01:59:35 -0700
Received: from iqpc_exchange(192.168.0.7) by iqpc_firewall.iqpc.co.uk 
 via Gauntlet (3.0) Tue, 23 May 2000 10:01:33 -0000
Received: by IQPC_EXCHANGE with Internet Mail Service (5.5.2650.21)
	id <KXLS8GPP>; Tue, 23 May 2000 09:58:48 +0100
Message-ID: <8BBA9503270DD31183D90008C7F3733284C38B@IQPC_EXCHANGE>
From: Katie Blackburn <Katie.Blackburn@iqpc.co.uk>
To: mymobile@egroups.com, agents <agents@cs.umbc.edu>, rem-conf
	 <rem-conf@es.net>
Subject: RE: [MyMobile] 1 week to deadline: AMOC 2000, Malaysia. (CFP)
Date: Tue, 23 May 2000 09:58:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

unsubscribe

Katie Blackburn
Marketing Manager

IQPC
Chancery House
Chancery Lane
London
WC2A 1QU
Telephone: +44 (0) 207 430 7357
Fax	 : +44 (0) 207 430 7304

To share the latest in business thinking, visit http://www.iqpc.co.uk


> -----Original Message-----
> From:	Farez [SMTP:F.AbdulRahman@cs.ucl.ac.uk]
> Sent:	Tuesday, May 23, 2000 12:20 AM
> To:	agents; rem-conf; mymobile
> Subject:	[MyMobile] 1 week to deadline: AMOC 2000, Malaysia. (CFP)
> 
>                           Call for Papers
> 
>          FIRST ASIAN INTERNATIONAL MOBILE COMPUTING CONFERENCE
>                             (AMOC 2000)
>             31 October - 3 November, 2000. Penang, Malaysia
>                 
>                 Organised by University Malaya, Malaysia
>                    In cooperation with ACM SIGMOBILE
>                  With main support from MRCB Multimedia
> 
>                     http://www.fsktm.um.edu.my/amoc
>             http://www.cs.ucl.ac.uk/staff/F.AbdulRahman/amoc
> 
> 
>               *** Submission deadline: 30 May, 2000 ***
> 
> Important update: 
> 200 word abstract to be included in the separate 'Author details' 
> plain text document.
> 
> Mobile computing is a new and highly dynamic field which combines
> modern computer science, networking and wireless communication
> technologies. This conference will provide a platform for researchers
> and practitioners to meet and discuss current issues in this field. 
> The conference is also unique as it highly encourages contributions 
> from the Asian region alongside those from other parts of the globe. 
> The focus on Asia is important because there are unique regional 
> issues not given attention in typical international conferences, where 
> technological issues in developed nations receive centre stage. These 
> issues include different infrastructural and economic requirements; 
> the effect of a more diverse socio-economic environment on 
> technical specifications; the far-reaching impact of wireless 
> communication in rural areas and the great interest in the rapid 
> deployment of cutting edge technology due to the high progress rate of 
> technological implementation in many Asian countries. 
> 
> The main objectives of this conference are:
> 
> 1. To provide a platform for international and Asian researchers and 
>    professionals to meet and discuss issues pertinent to both universal 
>    and Asia-centric mobile computing issues.
> 2. To provide participants with up-to-date information regarding the
>    development in this field.
> 3. To provide a yardstick by which researchers may compare the quality
>    of their work to that of their peers in order to maintain a high
>    standard of research.
> 
> The topics of interest include, but are not limited to, those listed
> below:
> 
> o Quality of Service(QoS)           o handover & location management
> o systems infrastructure            o satellite technology
> o internet access                   o power management
> o data services                     o lower layer protocols
> o rural wireless communications     o data management
> o billing                           o security
> o e-commerce                        o agent technology
> o multimedia                        o hardware
> o Personal Communication Systems    o terminal design & ergonomics
> o wireless LANs / WANs              o nomadic systems
> 
> Important Dates
> -------------------
> Submission deadline: 30 May, 2000
> Notification of acceptance: 15 July, 2000
> Camera ready copy: 15 August, 2000
> 
> Submission Guidelines
> ----------------------------
> Papers should be original, unpublished and not more than ten
> single-spaced pages with a minimum font size of 10 pt. Papers must be 
> in postscript format, and should only contain the paper
> title and the body of the paper, WITHOUT author names and
> affiliations. A separate plain text document containing only the 
> title, author names, their respective affiliations and 200 word 
> abstract, is required. Please send your paper (in postscript format) 
> and your separate author page (in plain text format) in separate 
> emails to amoc-submission@fsktm.um.edu.my by the 30th of May, 2000.
> 
> For more information, please visit http://www.fsktm.um.edu.my/amoc/ or
> email amoc-submission@fsktm.um.edu.my
> 
> Best Student Paper Award
> ------------------------
> The best paper with a student as primary author will be awarded a
> really cool prize of US$500 during the conference. Student authors who
> would like to be considered for this award should write 'Student Paper' 
> in the plain text document containing the paper title and author 
> name(s) and affiliation(s).
> 
> Tutorials
> ---------
> There will be two half-day and one full-day tutorials on 31 October. 
> The full-day tutorial will run in parallel with each of the half-day
> tutorials. The tutorials are:
> 
> 1. Client-server Computing in Wireless and Mobile Environments
>    Prof. Abdelsalam Helal, University of Florida. 
>    (Full Day)
> 
> 2. Java based Mobile Computing - JINI, Mobile Objects and Agents 
>    Dr. Omer F. Rana, University of Wales. 
>    (Half Day)
> 
> 3. Mobile Ad Hoc Wireless Networks 
>    Dr. Somprakash Bandyopadhyay from PriceWaterhouse Coopers Ltd.,
>    Dr. Krishna Paul from Cognizant Technology Solutions, India. 
>    (Half Day)
> 
> 
> Organising Committee
> --------------------
> Prof. Ir. Dr. Mashkuri Hj. Yaacob (Universiti Malaya)
> Dr Mazliza Othman (Universiti Malaya)
> Alfarez Abdul Rahman (University College London)
> Dr Roziati Zainuddin (Universiti Malaya)
> Dr. Zaitun Abu Bakar (Universiti Malaya)
> Rodziah Latih (Universiti Kebangsaan Malaysia)
> Norizan Mohd Yasin (Universiti Malaya)
> Omar Zakaria (Universiti Malaya)
> Mustaffa Kamal (Universiti Malaya)
> 
> Technical Program Committee
> ---------------------------
> Assc. Prof. David K. Asano, Shinshu University, Japan
> Prof. Boualem Boashash, Queensland University of Technology, Australia 
> Prof. Sung-Kwon Chung, Infomore, Inc., Korea 
> Dr. Che Nyan Husain, Telekom Malaysia 
> Prof. Chuah Hean Teik, Universiti Multimedia Telekom, Malaysia 
> Prof. Jon Crowcroft, University College London, UK
> Prof. Sajal Das, University of North Texas, USA 
> Assc. Prof. Norsheila Faisal, Universiti Teknologi Malaysia
> Prof. Sandeep Gupta, Colorado State University, USA 
> Dr. Stephen Hailes, University College London, UK
> Prof. Abdelsalam Helal, University of Florida, USA
> Ravi Jain, Telcordia, USA 
> Dr. Minseok Kang, LG Corporate Institute of Technology, Korea 
> Prof. Ryuji Kohno, Yokohama University, Japan 
> Dr. Jong-Hyeon Lee, Cambridge University, UK 
> Bo Li, Hong Kong University of Science & Technology
> Prof Jason Yi-Bing Lin, National Chiao Tung University, Taiwan
> Dr. Seng-Wai Loke, DSTC Monash University, Australia
> Dr. Jelena Misic, Hong Kong University of Science & Technology
> Assc. Prof. George Mohay, Queensland University of Technology, Australia 
> Susan Pancho, Cambridge University, UK
> Prof. Pradip Srimani, Colorado State University, USA
> Dr. Fumio Teraoka, Sony Computer Science Labs, Inc., Japan
> Prof. C-K Toh, Georgia Institute of Technology 
> Prof. Yu-Chee Tseng, National Central University, Taiwan 
> Dr. Arkady Zaslavsky, Monash University, Australia 
> Dr. Jianying Zhou, Kent Ridge Digital Lab, Singapore 
> 
> 
> 
> ------------------------------------------------------------------------
> Failed tests, classes skipped, forgotten locker combinations. 
> Remember the good 'ol days
> http://click.egroups.com/1/4053/2/_/107031/_/959038491/
> ------------------------------------------------------------------------
> 



From rem-conf Wed May 24 02:07:31 2000 
From rem-conf-request@es.net Wed May 24 02:07:30 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12uWp5-0001qz-00; Wed, 24 May 2000 01:47:27 -0700
Received: from correio.inescn.pt [192.35.246.2] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12uWp2-0001pn-00; Wed, 24 May 2000 01:47:25 -0700
Received: from newton.inescn.pt (newton.inescn.pt [194.117.24.17])
	by correio.inescn.pt (8.9.1/8.9.1/11) with SMTP id JAA22960;
	Wed, 24 May 2000 09:47:01 +0100
Received: from pimpim.inescporto.pt by newton.inescn.pt (SMI-8.6/SMI-SVR4)
	id JAA06475; Wed, 24 May 2000 09:46:48 +0100
Message-Id: <4.3.1.2.20000524093236.00b8dec0@newton.inescn.pt>
X-Sender: lmt@newton.inescn.pt
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 24 May 2000 09:45:25 +0100
To: IMAGELIB@LISTSERV.ARIZONA.EDU, comsoc-chapters@ieee.org,
        info-confs@comsoc.org, rem-conf@es.net, confctrl@ISI.EDU,
        Archive-L@tcf.ua.edu, mpeg-video@tele10.ist.utl.pt,
        sc29wg11doc@dkuug.dk
From: =?iso-8859-1?Q?Lu=EDs?= Teixeira <lmt@inescn.pt>
Subject: Pre-doctoral positions in Multimedia Archives and Video
  Analysis
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_2372301==_.ALT"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

--=====================_2372301==_.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable


<< Apologies for duplicate copies! >>

----------------------------------------------------------------------------=
--------
Pre-doctoral positions in Multimedia Archives
and Video Analysis
----------------------------------------------------------------------------=
---=20

INESC Porto, PORTUGAL
------------------------------------------------------------------------

Applications are invited for two pre-doctoral research position in the areas
of multimedia archives and video analysis for multimedia information
retrieval systems. The positions are for periods of six months to two and
a half years and are funded by the European Commission project MOUMIR
- MOdels for Unified Multimedia Information Retrieval, with university
collaborators from Trinity College Dublin (Ireland), INRIA (France), Ben
Gurion University (Israel), Aristotle University of Thessonaliki (Greece),
Cambridge University (UK), INESC Porto (Portugal) and content providers
>from RTP (the Portuguese public TV broadcaster) and BAL-Bridgeman
Art Library (UK).

-----------------------------------------------------------------------

Position in Multimedia Archives
Multimedia Archives are at the centre of many content-rich applications
and information services which are getting increasing attention and
investment. Searching multimedia archives requires the use of metadata
descriptions according to emerging standards.
The proposed goal is to start with an existing specification of a metadata
description scheme for multimedia materials and develop tools to store,
browse and query an archive of such items.
The metadata description scheme has taken into account the on-going work by
several communities:
    - the archival description community on a standard for the traditional
      documents (ISAD) and on dealing with new types of documents,=
 electronic,
      multimedia, distributed;
    - the multimedia/Internet search community on indexing the raw texts,
      and on characterising the other components of the Web sites;
    - the video coding community on searching audio and video sequences,
      and describing its contents in particular using the emerging MPEG7=20
standard.

An application area will be selected for the prototype, either photography
archives or broadcaster video archives.

-----------------------------------------------------------------------

Position in Video Analysis
The main objective of this work is to participate in the development of the
basis for a Video Analysis System with an high level of integration of the
video analysis tools. For that purpose a Generic Video Analysis Toolbox will
be implemented, including a wide variety of techniques for video
segmentation (face/object detection), scene cuts detection, global and=
 camera
motion estimation and text extraction. In order to obtain an integrated set=
 of
tools, evaluation tests will be performed to determine the inter-relations=
 and
synergies among the different content-based tools. The results of those
tests will allow the improvement of the performance of each specific tool=20
based on
the information provided by the others. Based on the information provided by
the video analysis tools, software for the video interpretation will be
implemented in order to achieve a description of the video content. A
specific type of application, like video content filtering applied to TV=20
News, will
be selected, to validate the developed techniques.

-------------------------------------------------------------------------

The successful applicant will be an independent-minded and ambitious
researcher with a MsC or equivalent on related areas. It will be possible to
include the applicants on the PhD programmes of the Porto University
(Faculdade de Engenharia - Engineering College,
http://www.fe.up.pt/feupwww/bem-vindo.html)

The European Commission stipulates that candidates should be EU
Nationals, or nationals of 5th Framework member countries, who
have not been resident in Portugal for more than 12 months.
Applications including CV and two academic references should be sent to the
address below.

Contact at INESC Porto with:
Prof. Luis Corte-Real, email: lreal@inescn.pt
Prof. Gabriel David, email: gtd@fe.up.pt

----------------------------------------------------------------------------=
-----------------------------
INESC Porto - Instituto de Engenharia de Sistemas e Computadores do Porto
(Institute for Systems and Computer Engineering of Porto)
(http://www2.inescporto.pt/uk/default1.asp)
is a private non-profit association that was created in December 1998,
having as associates INESC and the University of Porto.

INESC Porto is an interface between the academic world and the Information
Technology, Telecommunications and Electronics (ITT&E) industrial sector,
carrying out scientific research and development as well as technology
transfer and advanced professional training.

The ultimate goals of INESC Porto are to achieve high international
standards in science and technology as well as carrying out on the job
training of human resources, in its areas of expertise. At the same time,
as a result of its tight coupling to the University through the involvement
of a significant number of professors in its activities, INESC Porto also
promotes the adequacy of the teaching system to the needs of the
economical and social fabric.
INESC Porto is therefore a strategic instrument of the University and a
source of R&D and of young scientists to the ITT&T industry.

---------------------------------------------------------
Luis Miguel Lopes Teixeira
Escola das Artes - Universidade Cat=F3lica Portuguesa
Rua Diogo Botelho, 1327, 4169-005 Porto, Portugal
Email: lmt@artes.ucp.pt   http://artes.ucp.pt/dsi

INESC - Unidade de Telecomunica=E7=F5es & Multimedia
Prc. da Rep=FAblica, 93, 4050-497 Porto, Portugal
Phone: + 351 22 2094237         Fax: + 351 22 2087829
Email: lmt@inescporto.pt      http://telecom.inescn.pt/people/lmt/index.htm=
=20
--=====================_2372301==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<br>
&lt;&lt; Apologies for duplicate copies! &gt;&gt;<br>
<br>
----------------------------------------------------------------------------=
--------<br>
Pre-doctoral positions in Multimedia Archives <br>
and Video Analysis<br>
----------------------------------------------------------------------------=
---
<br>
INESC Porto, PORTUGAL<br>
------------------------------------------------------------------------<br>
<br>
Applications are invited for two pre-doctoral research position in the
areas <br>
of multimedia archives and video analysis for multimedia information
<br>
retrieval systems. The positions are for periods of six months to two and
<br>
a half years and are funded by the European Commission project
MOUMIR<br>
- MOdels for Unified Multimedia Information Retrieval, with university
<br>
collaborators from Trinity College Dublin (Ireland), INRIA (France), Ben
<br>
Gurion University (Israel), Aristotle University of Thessonaliki
(Greece), <br>
Cambridge University (UK), INESC Porto (Portugal) and content providers
<br>
>from RTP (the Portuguese public TV broadcaster) and BAL-Bridgeman <br>
Art Library (UK).<br>
<br>
-----------------------------------------------------------------------<br>
<br>
Position in Multimedia Archives<br>
Multimedia Archives are at the centre of many content-rich applications
<br>
and information services which are getting increasing attention and=20
<br>
investment. Searching multimedia archives requires the use of metadata
<br>
descriptions according to emerging standards.<br>
The proposed goal is to start with an existing specification of a
metadata <br>
description scheme for multimedia materials and develop tools to store,
<br>
browse and query an archive of such items.<br>
The metadata description scheme has taken into account the on-going work
by <br>
several communities: <br>
&nbsp;&nbsp; - the archival description community on a standard for the
traditional <br>
&nbsp;&nbsp;&nbsp;&nbsp; documents (ISAD) and on dealing with new types
of documents, electronic, <br>
&nbsp;&nbsp;&nbsp;&nbsp; multimedia, distributed; <br>
&nbsp;&nbsp; - the multimedia/Internet search community on indexing the
raw texts, <br>
&nbsp;&nbsp;&nbsp;&nbsp; and on characterising the other components of
the Web sites; <br>
&nbsp;&nbsp; - the video coding community on searching audio and video
sequences, <br>
&nbsp;&nbsp;&nbsp;&nbsp; and describing its contents in particular using
the emerging MPEG7 standard.<br>
<br>
An application area will be selected for the prototype, either
photography <br>
archives or broadcaster video archives.<br>
<br>
-----------------------------------------------------------------------<br>
<br>
Position in Video Analysis<br>
The main objective of this work is to participate in the development of
the <br>
basis for a Video Analysis System with an high level of integration of
the <br>
video analysis tools. For that purpose a Generic Video Analysis Toolbox
will <br>
be implemented, including a wide variety of techniques for video <br>
segmentation (face/object detection), scene cuts detection, global and
camera <br>
motion estimation and text extraction. In order to obtain an integrated
set of <br>
tools, evaluation tests will be performed to determine the
inter-relations and <br>
synergies among the different content-based tools. The results of those
<br>
tests will allow the improvement of the performance of each specific tool
based on <br>
the information provided by the others. Based on the information provided
by <br>
the video analysis tools, software for the video interpretation will be
<br>
implemented in order to achieve a description of the video content. A
<br>
specific type of application, like video content filtering applied to TV
News, will <br>
be selected, to validate the developed techniques.<br>
<br>
-------------------------------------------------------------------------<br=
>
<br>
The successful applicant will be an independent-minded and ambitious
<br>
researcher with a MsC or equivalent on related areas. It will be possible
to <br>
include the applicants on the PhD programmes of the Porto University
<br>
(Faculdade de Engenharia - Engineering College, <br>
<font color=3D"#0000FF"><u><a=
 href=3D"http://www.fe.up.pt/feupwww/bem-vindo.html"=
 eudora=3D"autourl">http://www.fe.up.pt/feupwww/bem-vindo.html</a></u></font=
>)<br>
<br>
The European Commission stipulates that candidates should be EU <br>
Nationals, or nationals of 5th Framework member countries, who <br>
have not been resident in Portugal for more than 12 months.<br>
Applications including CV and two academic references should be sent to
the <br>
address below.<br>
<br>
Contact at INESC Porto with: <br>
Prof. Luis Corte-Real, email: lreal@inescn.pt <br>
Prof. Gabriel David, email: gtd@fe.up.pt<br>
<br>
----------------------------------------------------------------------------=
-----------------------------<br>
INESC Porto - Instituto de Engenharia de Sistemas e Computadores do Porto
<br>
(Institute for Systems and Computer Engineering of Porto) <br>
(<a href=3D"http://www2.inescporto.pt/uk/default1.asp"=
 eudora=3D"autourl"><font color=3D"#0000FF"><u>http://www2.inescporto.pt/uk/=
default1.asp</a></u></font>)
<br>
is a private non-profit association that was created in December 1998,
<br>
having as associates INESC and the University of Porto.<br>
<br>
INESC Porto is an interface between the academic world and the
Information <br>
Technology, Telecommunications and Electronics (ITT&amp;E) industrial
sector, <br>
carrying out scientific research and development as well as technology
<br>
transfer and advanced professional training.<br>
<br>
The ultimate goals of INESC Porto are to achieve high international=20
<br>
standards in science and technology as well as carrying out on the job
<br>
training of human resources, in its areas of expertise. At the same time,
<br>
as a result of its tight coupling to the University through the
involvement <br>
of a significant number of professors in its activities, INESC Porto also
<br>
promotes the adequacy of the teaching system to the needs of the <br>
economical and social fabric.<br>
INESC Porto is therefore a strategic instrument of the University and a
<br>
source of R&amp;D and of young scientists to the ITT&amp;T=20
industry.<br>
<br>
<div>---------------------------------------------------------</div>
<div>Luis Miguel Lopes Teixeira</div>
<div>Escola das Artes - Universidade Cat=F3lica Portuguesa </div>
<div>Rua Diogo Botelho, 1327, 4169-005 Porto, Portugal</div>
<div>Email: lmt@artes.ucp.pt&nbsp;&nbsp;
<a href=3D"http://artes.ucp.pt/dsi"=
 EUDORA=3DAUTOURL>http://artes.ucp.pt/dsi</a></div>
<br>
<div>INESC - Unidade de Telecomunica=E7=F5es &amp; Multimedia</div>
<div>Prc. da Rep=FAblica, 93, 4050-497 Porto, Portugal</div>
<div>Phone: + 351 22
2094237&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fax: + 351 22
2087829</div>
Email: lmt@inescporto.pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href=3D"http://telecom.inescn.pt/people/lmt/index.htm"=
 EUDORA=3DAUTOURL>http://telecom.inescn.pt/people/lmt/index.htm</a>=20
</html>

--=====================_2372301==_.ALT--




From rem-conf Thu May 25 06:24:30 2000 
From rem-conf-request@es.net Thu May 25 06:24:28 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12uxSX-0007Vv-00; Thu, 25 May 2000 06:13:57 -0700
Received: from cs.columbia.edu [128.59.16.20] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12uxSV-0007Vl-00; Thu, 25 May 2000 06:13:55 -0700
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id JAA11342
	for <rem-conf@es.net>; Thu, 25 May 2000 09:13:54 -0400 (EDT)
Sender: hgs@cs.columbia.edu
Message-ID: <392D2712.3F9D9A30@cs.columbia.edu>
Date: Thu, 25 May 2000 09:13:54 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: rem-conf@es.net
Subject: Osprey 150 video on Solaris
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Anybody got vic running with the Osprey 150 (not the Osprey 1500 or
similar) on Solaris? Viewcast mentions a custom version in their
documentation, but it is nowhere to be found...
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From rem-conf Fri May 26 03:19:54 2000 
From rem-conf-request@es.net Fri May 26 03:19:52 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12vGzC-0002SZ-00; Fri, 26 May 2000 03:04:58 -0700
Received: from buffy.tpgi.com.au [203.12.160.34] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12vGz9-0002Rv-00; Fri, 26 May 2000 03:04:56 -0700
Received: (from smtpd@localhost)
	by buffy.tpgi.com.au (8.9.3/8.9.3) id UAA18450
	for <rem-conf@es.net>; Fri, 26 May 2000 20:04:50 +1000
Date: Fri, 26 May 2000 20:04:50 +1000
From: info@animationallsorts.com
Message-Id: <200005261004.UAA18450@buffy.tpgi.com.au>
Received: from syd3-56k-150.tpgi.com.au(203.29.148.150), claiming to be "home"
 via SMTP by buffy.tpgi.com.au, id smtpdELgBCR; Fri May 26 20:04:41 2000
To: rem-conf@es.net
X-Mailer: 5E333EDF.6AC484F8.a1e2cc4eeeffa1824c2a9425aaa3bee0
Subject: Open Mind
Organization: Animation Allsorts
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

I have discovered your webside on the Internet and find it
really interesting.I do believe that you or your clients may
benefit from the information we are offering. 

There are a lot of people trying to get rich quick, without 
any interest in another human being whatsoever. Well, I 
doubt that they will succeed. There is a law in success like 
there is a law in physics.

You may not believe in gravity or not know about it, but it still works.

The Law of Success says: 
If you help enough people to get what they want, 
You will get what You want.

Therefore, if you think, that you may gain and discover a benefit
for yourself, click on:

http://www.animationallsorts.com/00-Main-Journey.htm

or you can have a look at our Newsletter to find out if you can
benefit from it:

http://www.animationallsorts.com/NEWSLETER/April-00/NLetter-index.htm

Don't hesitate to forward a copy of this newsletter to friends
and associates, but please ask for permission before reproducing
the content in any form -- we would like to know who you are.

Pavel Kyral
Director

Animation Allsorts - Open Mind
105/3 Bruce Street, Crows Nest, NSW, 2065, Australia 
Phone: 612 9955 7990 | Fax: 612 9955 0076 
Copyright © 1990-2000 All Rights Reserved

If you think, that you will not benefit from this corespondence, send

an email to:

remove@animationallsorts.com	Subject:Remove gravity




From rem-conf Sat May 27 15:08:09 2000 
From rem-conf-request@es.net Sat May 27 15:08:08 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12voWH-0002uk-00; Sat, 27 May 2000 14:53:21 -0700
Received: from asn2-7.mcmail.com ([195.44.2.7] helo=Mailer003)
	by mail2.es.net with smtp (Exim 1.92 #1)
	id 12voVQ-0002tc-00; Sat, 27 May 2000 14:52:34 -0700
From: <vickers@another.co.uk>
Subject: Earn $100,000 Per Year sending E-mail !!
Date: Sat, 27 May 2000 19:14:52
Message-Id: <894.696011.309750@Mailer003>
Bcc:
To: rem-conf@es.net
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Tens of thousands of new people are going online every week, 
within the next three to four years there will be over 250 
million people surfing the net, and within the next eight years 
there will be over a billion. That is a lot of people, and they 
are all within your reach.  

To be removed from our mailing list click reply,and type remove 
in the subject box. Thankyou.

EARN $100,000 PER YEAR SENDING E-MAIL!!!

DON'T DELETE THIS.....PRINT IT......READ IT!!!    YOU'LL BE GLAD 
YOU DID!!!!

Dear Friend,

You can earn $50,000 or more in the next 90 days sending e-mail, 
seem impossible?

------------------------------------------------------------
"AS SEEN ON NATIONAL T.V."

Thank you for your time and Interest. This is the letter you've 
been reading about in the news lately.
Due to the popularity of this letter on the Internet, a major 
nightly news program recently devoted an
Entire show to the investigation of the program described below 
to see, if it really can make people money.
The show also investigated whether or not the program was legal. 
Their findings proved once and for
All that there are, absolutely no laws prohibiting the 
participation in the program. This has helped to
Show people that this is a simple, harmless and fun way to make 
some extra money at home.

The results of this show have been truly remarkable. So many 
people are participating that those involved are doing, much 
better than ever before. Since everyone makes more as more people 
try it out, its been very exciting to be a part of lately. You 
will understand once you experience it.

"HERE IT IS BELOW"

============================================================
*** Print This Now For Future Reference ***
The following income opportunity is one you may be interested in 
taking a Look at. It can be started with VERY LITTLE investment 
and the income return is TREMENDOUS!!!

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

If you would like to make at least $50,000 in less than 90 days! 
Please read the enclosed program..
 THEN READ IT AGAIN!!!

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

THIS IS A LEGITIMATE, LEGAL, MONEYMAKING OPPORTUNITY. It does not 
require you to come into contact with people, do any hard work, 
and best of all, you
Never have to leave the house except to get the mail. If you 
believe that someday you'll get that big break that you've been 
waiting for, THIS IS IT! Simply follow the instructions, and your 
dreams will come true. This multi-level e-mail order marketing 
program works perfectly...100% EVERY TIME. E-mail is the sales 
tool of the future. Take advantage of this non-commercialised 
method of advertising NOW!!!
The longer you wait, the more people will be doing business using 
e-mail.
Get your piece of this action

MULTI-LEVEL MARKETING (MLM) has finally gained respectability. It 
is being taught in the Harvard Business School, and both Stanford 
Research and the Wall Street Journal have stated that between 50% 
and 65% of all goods and services will be sold through 
multi-level methods by the mid to late 1990's. This is a 
Multi-Billion Dollar industry and of the 500,000 millionaires in 
the U.S., 20% (100,000) made their fortune in the last several 
years in MLM. Moreover, statistics show 45 people become 
millionaires everyday through Multi-Level Marketing.

You may have heard this story before, but over the summer Donald 
Trump made an appearance on the
David Letterman show. Dave asked him what he would do if he lost 
everything and had to start over
>From scratch. Without hesitating, Trump said he would find a good 
network marketing company and
Get to work. The audience started to hoot and boo him. He looked 
out at the audience and dead-panned
His response "That's why I'm sitting up here and you are all 
sitting out there!"

With network marketing you have two sources of income. Direct 
commissions from sales you make yourself and commissions from 
sales made by people you introduce to the business.

Residual income is the secret of the wealthy. It means investing 
time or money once and getting paid
Again and again and again. In network marketing, it also means 
getting paid for the work of others.

The enclosed information is something I almost let slip through 
my fingers. Fortunately, sometime later I re-read everything and 
gave some thought and study to it.

My name is Johnathon Rourke. Two years ago, the corporation I 
worked at for the past twelve years
Down-sized and my position was eliminated. After unproductive job 
interviews, I decided to open my own business. Over the past 
year, I incurred many unforeseen financial problems. I owed my 
family, friends and creditors over $35,000. The economy was 
taking a toll on my business and I just couldn't seem to make 
ends meet. I had to refinance and borrow against my home to 
support my family and struggling business. 
AT THAT MOMENT something significant happened in my life and I am 
writing to share the experience in hopes that this will change 
your life FOREVER FINANCIALLY!!!

In mid December, I received this program via e-mail. Six month's 
prior to receiving this program I had been sending away for 
information on various business opportunities. All of the 
programs I received, in my opinion, were not cost effective. They 
were either too difficult for me to comprehend or the initial 
investment was too much for me to risk to see if they would work 
or not. One claimed that I would make a million dollars in one 
year...it didn't tell me I'd have to write a book to make it!

But like I was saying, in December of 1997 I received this 
program. I didn't send for it, or ask for it,
They just got my name off a mailing list. THANK GOODNESS FOR 
THAT!!! After reading it several times, to make sure I was 
reading it correctly, I couldn't believe my eyes. Here was a 
MONEY MAKING PHENOMENON.I could invest as much as I wanted to 
start, without putting me further into debt. After I got a pencil 
and paper and figured it out, I would at
Least gets my money back. But like most of you I was still a 
little sceptical and a little worried about the legal aspects of 
it all. So I checked it out with the U.S. Post Office 
(1-800-725-2161 24-hrs) and they confirmed that it is
Indeed legal! After determining the program was LEGAL and NOT A 
CHAIN LETTER, I decided "WHY NOT."
Initially I sent out 10,000 e-mails. It cost me about $15 for my 
time on-line. The great thing about e-mail is that I don't need 
any money for printing to send out the program, and because all 
of my orders are fulfilled via e-mail, the only expense is my 
time. I am telling you like it is, I hope it doesn't turn you 
off, but I promised myself that I would not "rip-off" anyone, no 
matter how much money it cost me.

In less than one week, I was starting to receive orders for 
REPORT #1. By January 13, I had received 26 orders for REPORT #1. 
Your goal is to "RECEIVE at least 20 ORDERS FOR REPORT #1
WITHIN 2 WEEKS. IF YOU DON'T, SEND OUT MORE PROGRAMS UNTIL YOU 
DO!" My first step in making $50,000 in 90 days was done. By 
January 30, I had received 196 orders for REPORT #2. 
Your goal is to "RECEIVE AT LEAST 100+ ORDERS FOR REPORT #2 
WITHIN 2 WEEKS. IF NOT, SEND OUT MORE PROGRAMS UNTIL YOU DO. ONCE 
YOU HAVE 100 ORDERS, THE REST IS EASY, RELAX, YOU WILL MAKE YOUR 
$50,000 GOAL."
Well, I had 196 orders for REPORT #2, 96 more than I needed. So I 
sat back
And relaxed. By March 1, of my e-mailing of 10,000, I received 
$58,000 with more coming in every day. 
I paid off ALL my debts and bought a much needed new car. Please 
take time to read the attached program, 
IT WILL CHANGE YOUR LIFE FOREVER!!! Remember that it won't work 
if you don't try it. This program does work, but you must follow 
it EXACTLY! Especially the rules of not trying to place your name 
in a different place. It won't work, you'll lose out on a lot of 
money! In order for this program to work, you must meet your goal 
of 20+ orders for REPORT#1, and100+ orders for REPORT #2 and you 
will make $50,000 or more in 90 days. 
I AM LIVING PROOF THAT IT WORKS!!!

If you choose not to participate in this program, I am sorry. It 
really is a great opportunity with little cost or risk to you. If 
you choose to participate, follow the program and you will be on 
your way to financial security.

If you are a fellow business owner and are if financial trouble 
like I was, or you want to start your own business, consider this 
a sign. I DID!

Sincerely,
Johnathon Rourke

P.S. Do you have any idea what 11,700 $5 bills ($58,000) look 
like piled upon a kitchen table? IT'S AWESOME!

------------------------------------------------------------

A PERSONAL NOTE FROM THE ORIGINATOR OF THIS PROGRAM:

By the time you have read the enclosed program and reports, you 
should have concluded that an amateur could, not have created 
such a program, and one that is legal.

Let me tell you a little about myself. I had a profitable 
business for 10 years. Then in 1979 my business began falling 
off. I was doing the same things that were previously successful 
for me, but it wasn't working. Finally, I figured it out. It 
wasn't me, it was the economy. Inflation and recession had 
replaced the stable economy that had been with us since 1945. I 
don't have to tell you what happened to the unemployment rate... 
because many of you know from first hand experience. There were 
more failures and bankruptcies than ever before. The middle class 
was vanishing. Those who knew what they were doing invested 
wisely and moved up. Those who did not, including those who never 
had anything to save or invest, were moving down into the ranks 
of the poor. As the saying goes, "THE RICH GET RICHER AND THE 
POOR GET POORER." The traditional methods of making money will 
never allow you to "move up" or "get rich", inflation will see to 
that.

You have just received information that can give you financial 
freedom for the rest of your life, with
"NO RISK" and "JUST A LITTLE BIT OF EFFORT." You can make more 
money in the next few months than you have ever imagined. I 
should also point out that I will not see a penny of this money, 
nor anyone else who has provided a
Testimonial for this program. I have already made over 4 MILLION 
DOLLARS! I have retired from the program after sending out over 
16,000 programs. Now I have several offices that make this and 
several other programs here and over seas.
Follow the program EXACTLY AS INSTRUCTED. Do not change it in any 
way. It works exceedingly well as it is now. Remember to e-mail a 
copy of this exciting report to everyone you can think of. One of 
the people you send this to may send out 50,000...and your name 
will be on everyone of them!
Remember though, the more you send out the more potential 
customers you will reach.

So my friend, I have given you the ideas, information, materials 
and opportunity to become financially independent, 
IT IS UP TO YOU NOW!

"THINK ABOUT IT"
Before you delete this program from your mailbox, as I almost 
did, take a little time to read it and REALLY THINK ABOUT IT. Get 
a pencil and figure out what could happen when YOU participate. 
Figure out the worst possible response and no matter how you 
calculate it, you will still make a lot of money! You will 
definitely get back what you invested. Any doubts you have will 
vanish when your first orders come in. IT WORKS!
Jody Jacobs, Richmond, VA

------------------------------------------------------------
HERE'S HOW THIS AMAZING PROGRAM WILL MAKE YOU THOUSANDS OF 
DOLLAR$
------------------------------------------------------------
INSTRUCTIONS:

Before you say "BULL... ", Please read this program carefully. 
This is not a chain letter, but a perfectly legal money making 
opportunity. Basically, this is what you do: As with all 
multi-level businesses, we build our business by recruiting new 
partners and selling our products. Every state in the USA allows 
you to recruit new multi-level business partners, and we offer a 
product for EVERY dollar sent.
YOUR ORDERS COME BY MAIL AND ARE FILLED BY E-MAIL, so you are not 
involved in personal selling. You do it privately in your own 
home, store or office. This is the GREATEST Multi-Level Mail 
Order Marketing anywhere:


This is what you MUST do:
1. Order all 4 reports shown on the list below (you can't sell 
them if
You don't order them).

* For each report, send $5.00 CASH, the NAME & NUMBEROF THE 
REPORT YOU ARE
ORDERING, YOUR E-MAIL ADDRESS, and YOUR NAME & RETURN ADDRESS (in 
case of a
problem) to the person whose name appears on the list next to the 
report.

MAKE SURE YOUR RETURN ADDRESS IS ON YOUR ENVELOPE IN CASE OF ANY 
MAIL PROBLEMS!
* When you place your order, make sure you order each of the four 
reports. You will need all four reports so that you can save them 
on your computer and resell them.

* Within a few days you will receive, via e-mail, each of the 
four reports. Save them on your computer so they will be 
accessible for you to send to the 1,000's of people who will 
order them from you.

2. IMPORTANT-- DO NOT alter the names of the people who are 
listed next to each report, or their sequence on the list, in any 
way other than is instructed below in steps "a" through "f" or 
you will lose out on the majority of your profits. Once you 
understand the way this works, you'll also see how it doesn't 
work if you change it. Remember that this method has been tested, 
and if you alter it, it will not work.

a. Look below for the listing of available reports.

b. After you've ordered the four reports, take this advertisement 
and remove the name and address under REPORT #4. This person has 
made it through the cycle and is no doubt counting their $50,000!

c. Move the name and address under REPORT #3 down to REPORT #4.

d. Move the name and address under REPORT #2 down to REPORT #3.

e. Move the name and address under REPORT #1 down to REPORT #2.

f. Insert your name/address in the REPORT #1 position.

Please make sure you copy every name and address ACCURATELY!

3. Take this entire letter, including the modified list of names, 
and save it to your computer. Make NO changes to the instruction 
portion of this letter.

Your cost to participate in this is practically nothing (surely 
you can afford $20). You obviously already have an Internet 
connection and e-mail is FREE!

To assist you with marketing your business on the internet, the 4 
reports you purchase will provide you with invaluable marketing 
information which includes how to send bulk e-mails, where to 
find thousands of free classified ads and much, much more.

In addition you will be provided with information on Internet 
Marketing 
Clubs such as INTERNET
MARKETING RESOURCES (IMR): This is one the premiere Internet 
marketing clubs on the INTERNET. This club provides a forum where 
Internet marketers from all over the world can exchange ideas and 
secrets on Internet Marketing. In addition, this club specialises 
in providing free Internet marketing tools and services for the 
Do-Yourself-Internet-Marketer.
They will provide you with free bulk e-mail software and up to 
1,000,000 fresh e-mail addresses each week. This club
Will provide you with hundreds of free resources which include:

How to obtain free web sites, how to obtain top rankings in 
search engines for your web-site, how to send bulk e-mail into 
AOL and CompuServe, how to market your products on newsgroups, 
free classified ads, electronic malls, bulletin boards, banner 
ads and much more.

http://homepage1-2.virtualave.net/index3.htm

There are two primary methods of building your downline:
METHOD #1: SENDING BULK E-MAIL
Let's say that you decide to start small, just to see how it 
goes, and we'll assume you and all those involved send out only 
2,000 programs each. Let's also assume that the mailing receives 
a 0.5% response.  Using a good list the response could be much 
better. Also, many people will send out hundreds of thousands of 
programs instead of 2,000. But continuing with this example, you 
send out only 2,000 programs. With a 0.5% response, that is only 
10 orders for REPORT #1. Those 10 people respond by sending out 
2,000 programs each for a total of 20,000. Out of those 0.5%, 100 
people respond and order REPORT #2. Those 100 mails out 2,000 
programs each for a total of 200,000. The 0.5% response to that 
is 1,000 orders for REPORT #3. Those 1,000 send out 2,000 
programs each for a 2,000,000 total. The 0.5% response to that is 
10,000 orders for REPORT #4. That's 10,000 $5 bills for you. 
CASH!!! Your total income in this example is $50 + $500 + $5,000 
+
$50,000 for a total of  $55,550!!!
REMEMBER FRIEND, THIS IS ASSUMING 1,990 OUT OF THE 2,000 PEOPLE 
YOU MAIL TO
WILL DO ABSOLUTELY NOTHING AND TRASH THIS PROGRAM! DARE TO THINK 
FOR A
MOMENT WHAT WOULD HAPPEN IF EVERYONE, OR HALF SENT OUT 100,000 
PROGRAMS
INSTEAD OF 2,000. Believe me, many people will do just that, and 
more! By the way, your cost to participate in this is practically 
nothing. You obviously already have an Internet connection and 
e-mail is FREE!!!

REPORT #2 will show you the best methods for bulk e mailing, tell 
you where to obtain free bulk e-mail software and where to obtain 
e-mail lists.
METHOD #2 - PLACING FREE ADS ON THE INTERNET

1. Advertising on the 'Net is very, very inexpensive, and there 
are HUNDREDS of FREE places to advertise. Let's say you decide to 
start small just to see how well it works. Assume your goal is to 
get ONLY 10 people to participate on your first level. (Placing a 
lot of FREE ads on the Internet will EASILY get a larger 
response.) Also assume that everyone else in YOUR ORGANIZATION 
gets ONLY 10 downline members.

Follow this example to achieve the STAGGERING results below.

1st level--your 10 members with $5 .........................$50
2nd level--10 members from those 10 ($5 x 100)..............$500
3rd level--10 members from those 100 ($5 x 
1,000)...........$5,000
4th level--10 members from those 1,000 ($5 x 
10,000)........$50,000
----------- THIS TOTALS 
------------------------------------$55,550

Remember friends, this assumes that the people who participate 
only recruit 10 people each. Think for a moment what would happen 
if they got 20 people to participate! Most people get 100's of 
participants! THINK ABOUT IT!

For every $5.00 you receive, all you must do is e-mail them the 
report they ordered. THAT'S IT! ALWAYS PROVIDE SAME-DAY SERVICE 
ON ALL ORDERS! This will guarantee that the e-mail THEY send out, 
with YOUR name and address on it, will be prompt because they 
can't advertise until they receive the report!

------------------------------------------------------------
AVAILABLE REPORTS
------------------------------------------------------------

*** Order Each REPORT by NUMBER and NAME ***
Notes:

- ALWAYS SEND $5 CASH (U.S. CURRENCY) FOR EACH REPORT (CHEQUES 
NOT ACCEPTED)
- ALWAYS SEND YOUR ORDER VIA FIRST CLASS MAIL
- Make sure wrapping it in at least two sheets of paper conceals 
the cash
- On one of those sheets of paper, include:
 (a) The number & name of the report you are ordering, (b) your 
e-mail address, and (c) your name & postal address.

PLACE YOUR ORDER FOR THESE REPORTS NOW:
____________________________________________________________

REPORT #1 "The Insiders Guide To Advertising For Free on the 
Internet"

ORDER REPORT #1 FROM:

Casper Godber
2 NEWFIELD AVENUE,
CASTLEFORD,
WEST YORKSHIRE.
WF10 4BH
U.K.
____________________________________________________________


REPORT #2 "The Insider's Guide to Sending Bulk E-mail on the 
Internet"

ORDER REPORT #2 FROM:

R Tweed
51 VICTORIA ROAD
SYDENHAM
BELFAST
BT4 1QU
U.K.____________________________________________________________

REPORT #3 "The Secrets to Multilevel Marketing on the Internet"

ORDER REPORT #3 FROM:
Reports
Connaught House
Old Rectory Close
Mersham
Kent
TN25 6LZ
UK

____________________________________________________________

REPORT #4 "How to become a Millionaire utilising the Power
Of Multilevel Marketing and the Internet"

ORDER REPORT #4 FROM:
Susie Norman
801 N.W. Blvd.
Ardmore,
OKLAHOMA 73401
USA.

____________________________________________________________


******* TIPS FOR SUCCESS *******

* TREAT THIS AS YOUR BUSINESS! Be prompt, professional, and 
follow the directions accurately.

* Send for the four reports IMMEDIATELY so you will have them 
when the orders start coming in because:
When you receive a $5 order, you MUST send out the requested 
product/report.

* ALWAYS PROVIDE SAME-DAY SERVICE ON THE ORDERS YOU RECEIVE.

* Be patient and persistent with this program. If you follow the 
instructions exactly, your results
WILL BE SUCCESSFUL!

* ABOVE ALL, HAVE FAITH IN YOURSELF AND KNOW YOU WILL SUCCEED!

******* YOUR SUCCESS GUIDELINES *******
Follow these guidelines to guarantee your success:

If you don't receive 20 orders for REPORT #1 within two weeks, 
continue advertising or sending e-mails until you do. Then, a 
couple of weeks later you should receive at least 100 orders for 
REPORT#2. If you don't, continue advertising or sending e-mails 
until you do.

Once you have received 100 or more orders for REPORT #2, YOU CAN 
RELAX, because the system is already working for you, and the 
cash will continue to roll in!

THIS IS IMPORTANT TO REMEMBER:

Every time your name is moved down on the list, you are placed in 
front of a DIFFERENT report. You can KEEP TRACK of your PROGRESS 
by watching which report people are ordering from you. If you 
want to generate more income, send another batch of e-mails or 
continue placing ads and start the whole process again!

There is no limit to the income you will generate from this 
business!


Before you make your decision as to whether or not you 
participate in this program. Please answer one question. DO YOU 
WANT TO CHANGE YOUR LIFE? If the answer is yes, please look at 
the following facts about this program:

1. YOU ARE SELLING A PRODUCT WHICH DOES NOT COST ANYTHING TO 
PRODUCE!
2. YOU ARE SELLING A PRODUCT WHICH DOES NOT COST ANYTHING TO 
SHIP!
3. YOU ARE SELLING A PRODUCT WHICH DOES NOT COST YOU ANYTHING TO 
ADVERTISE!
4. YOU ARE UTILIZING THE POWER OF THE INTERNET AND THE POWER OF 
MULTI-LEVEL MARKETING TO DISTRIBUTE YOUR PRODUCT ALL OVER THE 
WORLD!
5. YOUR ONLY EXPENSES OTHER THAN YOUR INITIAL $20 INVESTMENT IS 
YOUR TIME!
6. VIRTUALLY ALL OF THE INCOME YOU GENERATE FROM THIS PROGRAM IS 
PURE
PROFIT!
7. THIS PROGRAM WILL CHANGE YOUR LIFE FOREVER.


******* T E S T I M O N I A L S *******

This program does work, but you must follow it EXACTLY! 
Especially the rule of not trying to place your name in a 
different position, it won't work and you'll lose a lot of 
potential income. I'm living proof that it works. It really is a 
great opportunity to make relatively easy money, with little cost 
to you. If you do choose to participate, follow the program 
exactly, and you'll be on your way to financial security. Steven 
Bardfield, Portland, OR

My name is Mitchell. My wife, Jody, and I live in Chicago, IL. I 
am a cost accountant with a major U.S. Corporation and I make 
pretty good money. When I received the program I grumbled to Jody 
about receiving "junk mail." I made fun of the whole thing, 
spouting my knowledge of the population and percentages involved. 
I "knew" it wouldn't work. Jody totally
Ignored my supposed intelligence and jumped in with both feet. I 
made merciless fun of her, and was ready to lay the old "I told 
you so" on her when the thing didn't work... well, the laugh was 
on me! Within two weeks she had received over 50 responses. 
Within 45 days she had received over $147,200 in $5 bills! I was 
shocked! I was sure that I had it all figured and that it 
wouldn't work. I AM a believer now. I have joined Jody in her 
"hobby." I did have seven more years until retirement, but I 
think of the "rat race" and it's not for me. We owe it all to 
MLM. Mitchell Wolf MD., Chicago, IL

The main reason for this letter is to convince you that this 
system is honest, lawful, extremely profitable, and is a way to 
get a large amount of money in a short time. I was approached 
several times before I checked this out. I joined just to see 
what one could expect in return for the minimal effort and money 
required. To my astonishment, I received $36,470.00 in the first 
14 weeks, with money still coming in. Sincerely yours, Charles 
Morris, Esq.

Not being the gambling type, it took me several weeks to make up 
my mind to participate in this plan. But conservative that I am, 
I decided that the initial investment was so little that there 
was just no way that I wouldn't get enough orders to at least get 
my money back. Boy, was I surprised when I found my medium-size 
post office box crammed with orders! For awhile, it got so 
overloaded that I had to start picking up my mail at the window. 
I'll make more money this
Year than any 10 years of my life before. The nice thing about 
this deal is that it doesn't matter where people live. There 
simply isn't a better investment with a faster return            
 Paige Willis, Des Moines, IA


I had received this program before. I deleted it, but later I 
wondered if I shouldn't have given it a try. Of course, I had no 
idea who to contact to get another copy, so I had to wait until I 
was e-mailed another program, ...11 months passed then it 
came...I didn't delete this one!...I made more than $41,000 on 
the first try!!                     Violet Wilson, Johnstown, PA

This is my third time to participate in this plan. We have quit 
our jobs, and will soon buy a home on the beach and live off the 
interest on our money. The only way on earth that this plan will 
work for you is if you do it. For your sake and for your family's 
sake don't pass up this golden opportunity.
Good luck and happy spending!                 Kerry Ford, 
Centerport, NY

ORDER YOUR REPORTS TODAY AND GET STARTED ON YOUR ROAD TO 
FINANCIAL FREEDOM!

NOW IS THE TIME FOR YOUR TURN DECISIVE ACTION YIELDS POWERFUL 
RESULTS

PLEASE NOTE: If you need help with starting a business, 
registering a business name, learning how income tax is handled, 
etc., contact your local office of the Small Business 
Administration (a Federal agency) 1-(800)827-5722 for free help 
and answers to questions. Also, the Internal Revenue Service 
offers free help via telephone and free seminars about business 
tax requirements. Your earnings and results are highly dependent 
on your activities and advertising. This letter
Constitute no guarantees stated or implied. In the event that it 
is determined that this letter constitutes a guarantee of any 
kind, that guarantee is now void. Any testimonials or amounts of 
earnings listed in this letter may be factual or fictitious. If 
you have any question of the legality of this letter contact the 
Office of Associate Director for Marketing Practices Federal 
Trade Commission Bureau of Consumer Protection in Washington DC.

============================================================




This ad is being sent in compliance with Senate bill 1618, Title 
3, section 301.
http://www.senate.gov/~murkowski/commercialemail/S771index.html



This message is sent in compliance of the new e-mail bill: 
SECTION 301. Per Section 301, paragraph (a)(2)(C) of S. 1618,
http://www.senate.gov/~murkowski/commercialemail/S771index.html

Further transmissions to you by the sender of this email may be 
stopped at no cost to you by sending a reply to this email 
address with the word "remove" in the subject line.

 
 
 
 
 
 
 
 



From rem-conf Sun May 28 07:00:47 2000 
From rem-conf-request@es.net Sun May 28 07:00:44 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12w3PW-0003PK-00; Sun, 28 May 2000 06:47:22 -0700
Received: from cast.kornet.net (wwwcast.kornet21.net) [168.126.72.41] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12w3PS-0003ON-00; Sun, 28 May 2000 06:47:19 -0700
Received: by wwwcast.kornet21.net id AA01040; Sun, 28 May 2000 22:37:38 +0900
Message-Id: <200005281337.AA01040@wwwcast.kornet21.net>
From: kellyspears@usa.com
To: 
Subject: Are You a Life-Changer?
Date: Sun, 28 May 2000 04:40:32 -0400
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_2C89_00000C0B.00006162"
X-Priority: 3
X-Msmail-Priority: Normal
Reply-To: kellyspears@usa.com
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

------=_NextPart_000_2C89_00000C0B.00006162
Content-Type: text/html;

<HTML>
<BODY>

<FONT face="MS Sans Serif">
<FONT size=2>
<FONT color="#000000"> <BR>
 Dear Friend,<BR>
<BR>
<BR>
Let me ask you a very straightforward question and <BR>
before you answer, think about it for a moment. <BR>
When you have trouble making ends meet on today's<BR>
income, how do you expect to retire and live on <BR>
less money than you earn now? Read the question <BR>
again before you go on - it is a very serious<BR>
question. If your income stopped today, how many<BR>
months could you survive in your current lifestyle<BR>
with no money coming in? What will be different in<BR>
your life two years from now if you continue<BR>
doing what you are doing now?<BR>
<BR>
Corporate America has conditioned us to believe <BR>
that security comes from employment.  Yet we hope <BR>
we never become the victims of downsizing, career<BR>
burn out, illness or injury.  The frightening <BR>
reality for most people is the plastic in their <BR>
wallets determines the quality of their lives.<BR>
<BR>
<BR>
Ask yourself, are you.....<BR>
<BR>
* Tired of working for someone else and getting <BR>
    paid what THEY tell you you're worth?<BR>
* Do your credit card balances total more than <BR>
    your bank accounts?<BR>
* Tired of the get rich quick on $5 fantasy <BR>
    programs?<BR>
* Tired of the Multi Level marketing residual<BR>
    income illusion?<BR>
* Looking for REAL wealth?<BR>
<BR>
CALL NOW  1-800-676-5633<BR>
<BR>
THEN LOOK AT THIS!!!<BR>
<BR>
* Free enterprise in its purest form, not Multi<BR>
    Level marketing or franchise.<BR>
* Proven lead generation system brings qualified<BR>
    prospects to you.<BR>
* Multiple 6 figure lifestyle realistically <BR>
    attainable in the first year.<BR>
* Endless support in an environment of <BR>
    REAL integrity.<BR>
* 90% profit on all sales paid directly to you.<BR>
<BR>
Our team of professionals is looking for a few <BR>
quality individuals with a strong work ethic and<BR>
DESIRE to generate $2,000 to $5,000 per week from <BR>
the comfort of their home.  With 5 different income<BR>
streams available we teach people how to achieve a<BR>
6 figure cash flow within the first 6 to 12 months <BR>
and how to retire for good within 2 to 4 years.<BR>
<BR>
SERIOUS SELF-STARTERS WITH A STRONG DESIRE TO IMPROVE<BR>
THEIR IMMEDIATE FINANCIAL FUTURE CALL NOW...<BR>
<BR>
1-800-914-0116<BR>
<BR>
Success is a matter of choice....your choice always.<BR>
<BR>
Prosperous regards!<BR>
<BR>
<BR>
Doug<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
To be removed from all future mailings reply to <BR>
this email Please type remove in the subject line.<BR>
Calling the 800 number will not get you removed.<BR>
Under Bill s.1618 TITLE III passed by the 105th<BR>
U.S. Congress this letter can not be considered<BR>
spam as long as we include: <BR>
Contact information & a Remove Link         <BR>
<BR>
<BR>
<BR>
</FONT></FONT></BODY></HTML>





From rem-conf Tue May 30 17:27:02 2000 
From rem-conf-request@es.net Tue May 30 17:27:00 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12ww2h-0000ZM-00; Tue, 30 May 2000 17:07:27 -0700
Received: from igate.nuera.com ([204.216.240.98] helo=sd_exchange.nuera.com)
	by mail2.es.net with esmtp (Exim 1.92 #1)
	for rem-conf@es.net
	id 12ww2f-0000Z6-00; Tue, 30 May 2000 17:07:25 -0700
Received: by sd_exchange.nuera.com with Internet Mail Service (5.5.2650.21)
	id <LQR7WZSC>; Tue, 30 May 2000 17:05:50 -0700
Message-ID: <613A6A6A3F09D3118F5C00508B2C24FE67A711@sd_exchange.nuera.com>
From: "Bratakos, Maroula" <mbratakos@nuera.com>
To: rem-conf@es.net
Subject: RFC 2833 on Tones
Date: Tue, 30 May 2000 17:05:41 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

I have a question about the last paragraph in section 2 that discusses
gateways which send signaling events via RTP.  It states: 

If a gateway cannot present a tone representation, it SHOULD send the audio
tones as regular RTP audio packets (e.g., as payload format PCMU), in
addition to the named signals. 
If the audio tones are sent along with named signals then shouldn't the
redundant method of RFC 2198 be used?

Maroula Bratakos
Nuera Communications, Inc.
mbratakos@nuera.com



From rem-conf Tue May 30 18:22:07 2000 
From rem-conf-request@es.net Tue May 30 18:22:07 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12wx66-0001am-00; Tue, 30 May 2000 18:15:02 -0700
Received: from lint.cisco.com [171.68.224.209] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12wx65-0001SG-00; Tue, 30 May 2000 18:15:01 -0700
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id SAA03369; Tue, 30 May 2000 18:14:00 -0700 (PDT)
Date: Tue, 30 May 2000 18:14:00 -0700 (PDT)
From: Dan Wing <dwing@cisco.com>
To: "Bratakos, Maroula" <mbratakos@nuera.com>
cc: rem-conf@es.net
Subject: Re: RFC 2833 on Tones
In-Reply-To: <613A6A6A3F09D3118F5C00508B2C24FE67A711@sd_exchange.nuera.com>
Message-ID: <0005301808390.5220-100000@omega.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

On Tue, 30 May 2000 17:05 -0700, Bratakos, Maroula wrote:

> I have a question about the last paragraph in section 2 that discusses
> gateways which send signaling events via RTP.  It states: 
> 
> If a gateway cannot present a tone representation, it SHOULD send the
> audio tones as regular RTP audio packets (e.g., as payload format
> PCMU), in addition to the named signals.
>
> If the audio tones are sent along with named signals then shouldn't the
> redundant method of RFC 2198 be used?

That would cause 'issues' (to put it mildly) if you're on any sort of
bandwidth allocation or near the saturation point for the access link,
such as with DSL or cable.

For example, if the admitted calls are currently consuming nearly
all of the upstream bandwidth, then doubling the bandwidth consumed
when someone touches a DTMF keypad will cause problems for the other
calls using that link.

-Dan Wing




From rem-conf Tue May 30 19:16:22 2000 
From rem-conf-request@es.net Tue May 30 19:16:22 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12wxx7-0005G8-00; Tue, 30 May 2000 19:09:49 -0700
Received: from inet-tsb.toshiba.co.jp [202.33.96.40] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12wxx3-0005Fo-00; Tue, 30 May 2000 19:09:45 -0700
Received: from tis2.tis.toshiba.co.jp (tis2 [133.199.160.66])
	by inet-tsb.toshiba.co.jp (3.7W:TOSHIBA-ISC-2000030918) with ESMTP id LAA20052;
	Wed, 31 May 2000 11:09:24 +0900 (JST)
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp (8.8.4+2.7Wbeta4/3.3W9-95082317)
	id LAA29747; Wed, 31 May 2000 11:09:24 +0900 (JST)
Received: from mailhost.eel.rdc.toshiba.co.jp by toshiba.co.jp (8.7.1+2.6Wbeta4/3.3W9-TOSHIBA-GLOBAL SERVER) id LAA03631; Wed, 31 May 2000 11:09:23 +0900 (JST)
Received: from ave (kwa0109.mobile.toshiba.co.jp [133.120.199.25]) by mailhost.eel.rdc.toshiba.co.jp (8.9.3/1.10) with SMTP id LAA85444; Wed, 31 May 2000 11:09:11 +0900 (JST)
Message-ID: <01ec01bfcaa5$28ce8160$19c77885@ave>
From: "Yoshihiro Kikuchi" <kiku@eel.rdc.toshiba.co.jp>
To: "4on2andIP-sys" <4on2andIP-sys@advent.ee.columbia.edu>,
        "IETF AVT" <rem-conf@es.net>
Cc: "Yoshihiro Kikuchi" <kiku@eel.rdc.toshiba.co.jp>
Subject: Updated I/D for MPEG-4 Audio/Visual RTP payload format
Date: Wed, 31 May 2000 11:08:47 +0900
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_01E7_01BFCAF0.97899040"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_01E7_01BFCAF0.97899040
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit

Dear MPEG-4 on IP experts,

I have just submitted the attached text as an updated Internet-Draft for the
MPEG-4 Audio/Visual RTP payload format.

The following is the list of changes from the previous Internet-Draft.

(1) Revision on the MPEG-4 upstream message RTCP (Section 5)
The RTCP specification was changed according to the discussion at the
Adelaide meeting.

(2) MIME type registration (Section 6)
As announced in Adelaide, a new section was added for the MIME type
registrations and SDP usages of MPEG-4 Audio/Visual streams.

(3) Some other clarifications and wording changes.

There is no essential change on the RTP part from the previous version,
which was verified and demonstrated by companies in Noordwijkerhout.

If you have any comments and questions, please let us know. Depend on the
discussion, we may provide another updated I/D with reflecting all comments
and suggestions, which should be the very final version of the I/D. We hope
we can finalize it by the end of the next week. We appreciate if we can have
all comments, if any, by then.

Best regards,
Yoshihiro

----
        Yoshihiro Kikuchi

E-mail: kiku@eel.rdc.toshiba.co.jp
Corporate Research and Development Center
TOSHIBA Corporation
TEL: +81 +44 549 2288    FAX: +81 +44 520 1267



------=_NextPart_000_01E7_01BFCAF0.97899040
Content-Type: text/plain;
	name="draft-ietf-avt-rtp-mpeg4-es-01.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-ietf-avt-rtp-mpeg4-es-01.txt"


Internet Engineering Task Force                 Yoshihiro Kikuchi - =
Toshiba
Internet Draft                                       Toshiyuki Nomura - =
NEC
Document: draft-ietf-avt-rtp-mpeg4-es-01.txt         Shigeru Fukunaga - =
Oki
                                              Yoshinori Matsui - =
Matsushita
                                                       Hideaki Kimata - =
NTT
                                                               May 31, =
2000


             RTP payload format for MPEG-4 Audio/Visual streams


Status of this Memo

   This document is an Internet-Draft and is in full conformance with =
all
      provisions of Section 10 of RFC2026 [1].

   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 obsoleted 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."
   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt
   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.






                                   Abstract

   This document describes RTP payload formats for the carriage of =
MPEG-4
   Audio and Visual streams[2][3], and an RTCP format for MPEG-4 =
upstream
   messages functionalities[4]. In this specification, MPEG-4 =
Audio/Visual
   bitstreams are directly mapped into RTP packets. The RTP header =
fields
   usage and the fragmentation rule for MPEG-4 Visual and Audio =
bitstreams
   are specified. It also specifies an RTCP packet usage to carry the =
MPEG-4
   upstream messages. In addition, MIME type registrations and SDP =
usages
   for the MPEG-4 Audio and Visual streams are defined in this document.











Kikuchi/Nomura/Fukunaga/Kimata/Matsui                           [Page 1]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


1. Introduction

1.1 Why MPEG-4 Audio/Visual RTP format needed?

   The RTP payload formats described in this Internet-Draft specify a =
way of
   how MPEG-4 Audio and Visual streams are fragmented and mapped =
directly
   onto RTP packets.

   H.323 terminals could be an example where such RTP payload formats =
are
   used.  MPEG-4 Audio/Visual streams are not managed by Object =
Descriptors
   of MPEG-4 Systems[6] but by H.245. The streams are directly mapped =
onto
   RTP packets without using the synchronization functionality of MPEG-4
   Systems [6].

   The semantics of RTP headers in such cases need to be clearly =
defined,
   including the association with the MPEG-4 Audio/Visual data elements. =
 In
   addition, it would be beneficial to define the fragmentation rule of =
RTP
   packets for MPEG-4 Video streams so as to enhance error resiliency by
   utilizing the error resilience tools provided inside the MPEG-4 Video
   stream.  However, these items are not covered by other RTP payload =
format
   proposals.


1.2 MPEG-4 Visual RTP payload format

   MPEG-4 Visual is a visual coding standard with many new =
functionalities:
   high coding efficiency, high error resiliency, multiple arbitrary =
shaped
   object based coding, etc. [2]. It covers a wide range of bitrate from
   several Kbps to many Mbps. It also covers a wide variety of networks
   ranging from guarantied to be almost error-free to mobile networks =
with
   high error rate due to its error resilience functionalities.

   A fragmentation rule for an MPEG-4 visual bitstream into RTP packets =
is
   defined in this document. Since MPEG-4 Visual is used for a wide =
variety
   of networks, it is desirable not to apply too much restriction to the
   fragmentation.  A fragmentation rule like "a single video packet =
shall
   always be mapped on a single RTP packet" may be inappropriate. On the
   other hand, a careless media unaware fragmentation may cause =
degradation
   of the error resiliency and the bandwidth efficiency. The =
fragmentation
   rule described in this document is flexible but to define the minimum
   rules and guidelines for preventing the meaningless fragmentation and =
to
   utilizing the error resilience functionality of MPEG-4 visual.

   For video coding media such as H.261 or MPEG-1/2, the additional =
media
   specific RTP header works effectively for recovering. e.g., of a =
picture
   header corrupted by packet losses. However, there are error =
resilience
   functionalities inside MPEG-4 Visual to recover corrupt headers. =
These
   functionalities can commonly be used on RTP/IP network as well as =
other
   networks. (H.223/mobile, MPEG-2/TS, etc.) Therefore, no extra RTP =
header
   fields are defined in the MPEG-4 Visual RTP payload format.



Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 2]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


1.3 Consideration on the MPEG-4 Audio RTP payload format

   MPEG-4 Audio is a new kind of audio standard that integrates many
   different types of audio coding tools. It also supports a mechanism
   representing synthesized sounds. Low-overhead MPEG-4 Audio Transport
   Multiplex (LATM) manages the sequence of the compressed or the
   represented audio data by MPEG-4 Audio tools with relatively small
   overhead. In audio-only applications, the LATM-based MPEG-4 Audio
   bitstreams, therefore, are desirable to be directly mapped into the =
RTP
   packets without using MPEG-4 Systems.

   Furthermore, if the payload of a packet is a single audio frame, a =
packet
   loss does not impair the decodability of adjacent packets. Therefore, =
a
   payload specific header for MPEG-4 Audio is not required as same as =
one
   for the other audio coders.


1.4 MPEG-4 Audio/Visual upstream messaging on RTCP packets

   Some particular tools of MPEG-4 Audio/Visual support upstream =
messaging
   functionalities. These messages are extremely Audio/Visual specific,
   since coders directly use these messages for controlling coding
   parameters. From the point of view of controlling parameters, these
   messages should be transmitted without delay. Therefore, these =
messages
   are directly mapped onto some kind of low delay RTCP packets. The use =
of
   this type of RTCP packets is limited to the case when the MPEG-4 =
upstream
   functionalities in some particular profiles are used (e.g. MPEG-4 =
Visual
   Advanced Real Time Simple Profile, NEWPRED tool).




2. Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC-2119 [7].




3. RTP Packetization of MPEG-4 Visual bitstream

   This section specifies the RTP packetization rule for MPEG-4 Visual
   content. An MPEG-4 Visual bitstream is mapped directly onto the RTP
   payload without any addition of extra header fields or removal of any
   Visual syntax elements. The Combined Configuration/Elementary streams
   mode is used so that the configuration information is carried in the =
same
   RTP port as the elementary stream. (see 6.2.1 "Start codes" of =
ISO/IEC
   14496-2 [2][9][4])



Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 3]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   When the short video header mode is used, RTP payload format for =
H.263
   specified in the relevant RFCs or other standards MAY be used.



















































Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 4]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   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=3D2|P|X|  CC   |M|     PT      |       sequence number         | =
RTP
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           timestamp                           | =
Header
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   =
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
   |            contributing source (CSRC) identifiers             |
   |                             ....                              |
   =
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
   |                                                               | RTP
   |       MPEG-4 Visual stream (byte aligned)                     | =
Payload
   |                                                               |
   |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               :...OPTIONAL RTP padding        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

        Figure 1 - An RTP packet for MPEG-4 Visual stream




3.1 RTP header fields usage for MPEG-4 Visual

   Payload Type (PT): Distinct payload type should be assigned to =
specify
   MPEG-4 Visual RTP payload format. If the dynamic payload type =
assignment
   is used, it is specified by some out-of-band means (e.g. H.245, SDP,
   etc.) that the MPEG-4 Visual payload format is used for the =
corresponding
   RTP packet.


   Extension (X) bit: Defined by the RTP profile used.


   Sequence Number: Increment by one for each RTP data packet sent. It
   starts with a random initial value for security reasons.


   Marker (M) bit: The marker bit is set to one to indicate the last RTP
   packet (or only RTP packet) of a VOP.


   Timestamp: The timestamp indicates the composition time, or the
   presentation time in a no-compositor decoder by adding a constant =
random
   offset for security reasons. For a video object plane, it is defined =
by
   vop_time_increment (in units of 1/vop_time_increment_resolution =
seconds)
   plus the cumulative number of whole seconds specified by =
module_time_base
   and time_code of Group_of_VideoObjectPlane() if present. In the case =
of
   interlaced video, a VOP consists of lines from two fields and the
   timestamp indicates the composition time of the first field. If the =
RTP

Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 5]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   packet contains only configuration information and/or
   Group_of_VideoObjectPlane(), the composition time of the subsequent =
VOP
   in the coding order is used. If the RTP packet contains only
   visual_object_sequence_end_code, the composition time of the =
immediately
   preceding VOP in the coding order is used.

   Unless specified by an out-of-band means (e.g. SDP parameter or MIME
   parameter as defined in section 6), the resolution of the timestamp =
is
   set to its default (90KHz).


   SSRC, CC and CSRC fields are used as described in RFC 1889 [8].


3.2 Fragmentation of MPEG-4 Visual bitstream

   A fragmented MPEG-4 Visual bitstream is mapped directly onto the RTP
   payload without any addition of extra header fields or removal of any
   Visual syntax elements. The Combined Configuration/Elementary streams
   mode is used. The following rules apply for the fragmentation.

   (1) The configuration information and Group_of_VideoObjectPlane() =
SHALL
   be placed at the beginning of the RTP payload (just after the RTP =
header)
   or just after the header of the syntactically upper layer function.

   (2) If one or more headers exist in the RTP payload, the RTP payload
   SHALL begin with the header of the syntactically highest function.
   Note: The visual_object_sequence_end_code is regarded as the lowest
   function.

   (3) A header SHALL NOT be split into a plurality of RTP packets.

   (4) Two or more VOPs SHALL be fragmented into different RTP packets =
so
   that one RTP packet consists of the data bytes associated with an =
unique
   presentation time (that indicated to the timestamp field in the RTP
   packet header).

   (5) A single video packet SHOULD NOT be split into a plurality of RTP
   packets. The size of a video packet SHOULD be adjusted such that the
   resulting RTP packet is not larger than the path-MTU. A video packet =
MAY
   be split into a plurality of RTP packets when the size of the video
   packet is large.


   Here, header means:
   - Configuration information (Visual Object Sequence Header, Visual =
Object
     Header and Video Object Layer Header)
   - visual_object_sequence_end_code
   - The header of the entry point function for an elementary stream
     (Group_of_VideoObjectPlane() or the header of VideoObjectPlane(),
     video_plane_with_short_header(), MeshObject() or FaceObject())


Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 6]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   - The video packet header (video_packet_header() excluding
     next_resync_marker())
   - The header of gob_layer()
   See 6.2.1 "Start codes" of ISO/IEC 14496-2[2][9][4] for the =
definition of
   the configuration information and the entry point functions.


   The video packet starts with the VOP header or the video packet =
header,
   followed by motion_shape_texture(), and ends with =
next_resync_marker() or
   next_start_code).


3.3 Examples of packetized MPEG-4 Visual bitstream

   Considering that MPEG-4 Visual is used on a wide variety of networks =
from
   several Kbps to many Mbps, from guaranteed networks which are almost
   error-free to mobile networks with high error rate, it is desirable =
not
   to apply too much restriction to the fragmentation. On the other =
hand, a
   careless media unaware fragmentation will cause degradation of the =
error
   resiliency and the bandwidth efficiency. The fragmentation criteria
   described in 3.2 are flexible but to define the minimum rules to =
prevent
   meaningless fragmentation.

   For video coding media such as H.261 or MPEG-1/2, the additional =
media
   specific RTP header works effectively for recovering, e.g., of a =
picture
   header corrupted by packet losses. However, there is an error =
resilience
   functionality inside MPEG-4 Visual to recover corrupt headers. This
   functionality can commonly be used on RTP/IP network as well as other
   networks. (H.223/mobile, MPEG-2/TS, etc.) Therefore, there is no =
strong
   reason to define MPEG-4 Visual specific extra RTP header fields.


   Figure 2 shows examples of RTP packets generated based on the =
criteria
   described in 3.2

   (a) is an example of the first RTP packet or the random access point =
of
   an MPEG-4 visual bitstream. This RTP packet contains the =
configuration
   information. According to the criterion (1), the Visual Object =
Sequence
   Header(VS header) is placed at the beginning of the RTP payload, and =
the
   Visual Object Header and the Video Object Layer Header(VO header, VOL
   header) follow it. Since the fragmentation rule defined in 3.2 =
guarantees
   that the configuration information, starting with
   visual_object_sequence_start_code, is always placed at the beginning =
of
   the RTP payload, RTP receivers can detect the random access point by
   checking if the first 32-bit field of the RTP payload is
   visual_object_sequence_start_code.

   (b) is another example of the RTP packet containing the configuration
   information. The difference from the example (a) is that this RTP =
packet
   also contains a video packet in the VOP following the configuration
   information. Since the length of the configuration information is
   relatively short (typically several ten bytes), an RTP packet =
containing

Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 7]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   only the configuration information may increase the overhead. =
Therefore,
   the configuration information and the immediately following GOV =
and/or (a
   part of) VOP can be packetized into a single RTP packet like this
   example.

   (c) is an example the RTP packet that contains
   Group_of_VideoObjectPlane(GOV). Following the criterion (1), the GOV =
is
   placed at the beginning of the RTP payload. It is a waste of RTP/IP
   header overhead to generate a RTP packet containing only a GOV whose
   length is 7 bytes. Therefore, (a part of) the following VOP can be =
placed
   in the same RTP packet as shown in (c).

   (d) is an example of the case where one video packet is packetized =
into
   one RTP packet. When the packet-loss rate of the underlying network =
is
   high, this kind of packetization is recommended. It is strongly
   recommended to set resync_marker_disable to 0 in the VOL header to =
enable
   adjustment of the video packet size. Even when the RTP packet =
containing
   the VOP header is discarded by a packet loss, the other RTP packets =
can
   be decoded by using the HEC(Header Extension Code) information in the
   video packet header. No extra RTP header field is necessary.

   (e) is an example of the case where more than one video packets are
   packetized into one RTP packet. This kind of packetization is =
effective
   to save the overhead of RTP/IP headers if the bit-rate of the =
underlying
   network is low. However, it will decrease the packet-loss resiliency
   because multiple video packets are discarded by a single RTP packet =
loss.
   The adequate number of video packets in a RTP packet and the RTP =
packet
   length depend the packet-loss rate and the bit-rate of the underlying
   network.


   Figure 3 shows examples of RTP packets prohibited by the criteria of =
3.2.

   Fragmentation of a header into multiple RTP packets, like (a), will =
not
   only increase the overhead of RTP/IP headers but also decrease the =
error
   resiliency. Therefore, it is prohibited by the criterion (3).

   When concatenating more than one video packets into an RTP packet, =
VOP
   header or video_packet_header() shall not be placed in the middle of =
the
   RTP payload. The packetization like (b) is not allowed by the =
criterion
   (2). This is because of the error resiliency. Comparing this example =
with
   Figure 2(c), two video packets are mapped onto two RTP packets in =
both
   cases. However, there is a difference between the packet-loss =
resiliency.
   When the second RTP packet is lost, both video packets 1 and 2 are =
lost
   in the case of Figure 3(b) whereas only video packet 2 is lost in the
   case of Figure 2(c).

   An RTP packet containing more than one VOPs, like (c), is not =
allowed.





Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 8]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


       +------+------+------+------+
   (a) | RTP  |  VS  |  VO  | VOL  |
       |header|header|header|header|
       +------+------+------+------+

       +------+------+------+------+------------+
   (b) | RTP  |  VS  |  VO  | VOL  |Video Packet|
       |header|header|header|header|            |
       +------+------+------+------+------------+

       +------+-----+------------------+
   (c) | RTP  | GOV |Video Object Plane|
       |header|     |                  |
       +------+-----+------------------+

       +------+------+------------+  +------+------+------------+
   (d) | RTP  | VOP  |Video Packet|  | RTP  |  VP  |Video Packet|
       |header|header|    (1)     |  |header|header|    (2)     |
       +------+------+------------+  +------+------+------------+

       =
+------+------+------------+------+------------+------+------------+
   (e) | RTP  |  VP  |Video Packet|  VP  |Video Packet|  VP  |Video =
Packet|
       |header|header|     (1)    |header|    (2)     |header|    (3)    =
 |
       =
+------+------+------------+------+------------+------+------------+

        Figure 2 - Examples of RTP packetized MPEG-4 Visual bitstream


       +------+-------------+  +------+------------+------------+
   (a) | RTP  |First half of|  | RTP  |Last half of|Video Packet|
       |header|  VP header  |  |header|  VP header |            |
       +------+-------------+  +------+------------+------------+

       +------+------+----------+  =
+------+---------+------+------------+
   (b) | RTP  | VOP  |First half|  | RTP  |Last half|  VP  |Video =
Packet|
       |header|header| of VP(1) |  |header| of VP(1)|header|    (2)     =
|
       +------+------+----------+  =
+------+---------+------+------------+

       +------+------+------------------+------+------------------+
   (c) | RTP  | VOP  |Video Object Plane| VOP  |Video Object Plane|
       |header|header|        (1)       |header|       (2)        |
       +------+------+------------------+------+------------------+

   Figure 3 - Examples of prohibited RTP packetization for MPEG-4 Visual
   bitstream








Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 9]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


4. RTP Packetization of MPEG-4 Audio bitstream

   When tools defined in MPEG-4 Systems are not used MPEG-4 Audio stream =
is
   formatted by LATM (Low-overhead MPEG-4 Audio Transport Multiplex)
   format[5], and then mapped onto RTP packets as described the =
subsequent
   section.

4.1 RTP Packet Format

   The LATM consists of the sequence of audioMuxElements that include =
one or
   more audio frames. A complete audioMuxElement or the part of
   audioMuxElements SHALL be mapped directly onto the RTP payload =
without
   removal of any audioMuxElement syntax elements as shown in Figure 4. =
The
   first byte of each audioMuxElement SHALL be located at the first =
payload
   location of an RTP 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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=3D2|P|X|  CC   |M|     PT      |       sequence number         =
|RTP
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           timestamp                           =
|Header
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   =
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
   |            contributing source (CSRC) identifiers             |
   |                             ....                              |
   =
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
   |                                                               |RTP
   :                 audioMuxElement (byte aligned)                =
:Payload
   |                                                               |
   |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               :...OPTIONAL RTP padding        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                Figure 4 - An RTP packet for MPEG-4 Audio

   It is required for the audioMuxElement to indicate the following
   muxConfigPresent information by an out-of-band means.

   muxConfigPresent: If this information is set to 1, the =
audioMuxElement
   SHALL include an indication bit "useSameStreamMux" and MAY include =
the
   configuration information for audio compression "StreamMuxConfig". =
The
   useSameStreamMux bit indicates whether the StreamMuxConfig element in =
the
   previous frame is applied in the current frame.

4.2 RTP Header Fields Usage

   Payload Type (PT): Distinct payload type should be assigned to =
specify
   MPEG-4 Audio RTP payload format. If the dynamic payload type =
assignment
   is used, it is specified by some out-of-band means (e.g. H.245, SDP,


Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 10]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   etc.) that the MPEG-4 Audio payload format is used for the =
corresponding
   RTP packet.

   Marker (M) bit: The marker bit indicates audioMuxElement boundaries. =
This
   bit is set to one to mark the RTP packet contains a complete
   audioMuxElement or the last fragment of an audioMuxElement.

   Timestamp: The timestamp indicates the composition time, or the
   presentation time in a no-compositor decoder. Timestamps are =
recommended
   to start at a random value for security reasons.

   Unless specified by an out-of-band means, the resolution of the =
timestamp
   is set to its default (90 kHz).

   Sequence Number: Increment by one for each RTP packet sent. It starts
   with a random value for security reasons.

   SSRC, CC and CSRC fields are used as described in RFC 1889 [8].

4.3 Fragmentation of MPEG-4 Audio bitstream

   It is desirable to put one audioMuxElement per RTP packet. The size =
of an
   audioMuxElement is tried to be adjusted such that the resulting RTP
   packet is not larger than the path-MTU. If this is not possible, the
   audioMuxElement MAY be fragmented across several packets based on the
   following rules.

   (1) "payloadMux" which consists of payload elements MAY be fragmented
   into several RTP packets so that one RTP packet consists of one or =
more
   payload elements. A payload element SHOULD NOT be fragmented.

   (2) If the audioMuxElement includes StreamMuxConfig, StreamMuxConfig
   SHALL be included into the RTP packet containing the first payload
   element.




5. RTCP Packetization of MPEG-4 upstream messages

   This section specifies the usage of particular RTCP packets to carry =
the
   upstream messages generated using the MPEG-4 Audio/Visual upstream
   messaging functionalities. In the current specification, NEWPRED in =
the
   MPEG-4 Visual Advance Real Time Simple (ARTS) Profile[4] is only the =
tool
   which uses this RTCP payload specification. This particular RTCP =
packet
   SHALL ONLY be used when it is indicated by some out of band means =
that
   the corresponding MPEG-4 Visual codec is compliant with the ARTS =
profile
   and it is indicated in the configuration information of the MPEG-4 =
visual
   bitstream that the NEWPRED tool is enabled (newpred_enable is set to =
1).


5.1. Abstract of NEWPRED in the ARTS profile

Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 11]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D



   NEWPRED in the ARTS profile is an error resilience tool using the
   upstream messages from the decoder to the encoder.  As the =
inter-frame
   coding is used in the MPEG-4 Visual standard, the image degradation =
by
   packet loss will be propagated to the after several frames.  In order =
to
   prevent the temporal error propagation, the reference frames of the
   inter-frame coding are switched according to the upstream messages in =
the
   NEWPRED.  As the correct frames are used as the reference frame, the
   error propagation is refreshed.

   As neither the re-transmission nor the intra refresh are used, the =
coding
   efficiency can be kept high.  And the NEWPRED can achieve the faster
   error recovery than the intra refresh.

   There are two types of upstream messages; acknowledged message =
(NP_ACK)
   and non-acknowledged message (NP_NACK).  NP_ACK and/or NP_NACK =
messages
   are transmitted on the particular RTCP packets in the NEWPRED.  The
   selecting methods of reference frames are dependent on the kind of =
used
   messages.

5.2. Particular RTCP packets keep low delay

   The real-time Audio/Visual transmission is more sensitive to delay =
and
   does not require full reliability.  For Audio/Visual applications it =
is
   more effective to send the MPEG-4 upstream message packets as soon as
   possible, i.e. as soon as a loss is detected, without adding any =
random
   delays.

5.3.  Congestion control

   In the cases of the demand type of intra refresh or the =
re-transmission,
   the amount of bits during the congestion is larger than that in the =
error
   free terms.  Therefore they may cause some another congestion.  While =
in
   the NEWPRED, as the intra-frame coding is not used, the increased =
amount
   of bits is much lower than that of the intra refresh or the re-
   transmission even in the case of packet loss.  Therefore NEWPRED =
causes
   less additional burden for the congestion.

   The amount of the upstream messages is dependent on the strategy of =
the
   selecting methods of reference frames of the encoder and that of the
   sending upstream messages of the decoder.  In order to avoid =
congestion,
   the amount of upstream message packets should be small. In the =
NEWPRED,
   the decoder can control the amount of them by not sending some =
upstream
   messages; For example, in the case that the NP_NACK messages are =
mainly
   used to select the reference frames in the encoder, the decoder may =
not
   send the NP_ACK messages even if it receives downstream data.  On the
   other hand, in the case that the NP_ACK messages are mainly used in =
the
   encoder, the decoder may not send the NP_NACK messages. The amount of =
the
   upstream messages is at most 5% (normally about 1%) of the visual
   downstream data.



Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 12]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   Especially the amount of NP_ACK messages is decreased in the case of
   packet loss.  Therefore the NP_ACK message has no additional burden =
for
   the congestion.  On the other hand, NP_NACK messages corresponding to =
the
   lost packets are usually sent after the congestion, because the =
decoder
   detects the packet loss after the next downstream packet reaches.
   Therefore the NP_NACK message has less additional burden for the
   congestion, too.

   And to reduce the number of particular RTCP packets, multiple =
upstream
   messages can be concatenated in the payload of one particular RTCP
   packet.  In this case, it is desirable to send these concatenated
   messages as soon as possible.

   The particular RTCP transmission interval is according to the =
interval of
   the decoding the visual downstream data.  Both the receiving interval =
of
   the visual RTP packet and the decoding time for each packet data have
   some jitter for themselves.  Therefore the particular RTCP =
transmission
   interval has some jitter for itself.  It is effective for the =
congestion
   control, and there is no need to add any random delays.  This means =
that
   the size of sending jitter is enough to avoid another congestion only =
in
   case of the unicast.

5.4. Limiting to Unicast

   The NEWPRED can work in multicast only in the case that the number of
   decoders is small.  However in order to avoid the additional =
congestion,
   the NEWPRED over RTP/RTCP SHALL NOT be used in multicast.

5.5. Relations with SR and RR
   The particular low delay RTCP packets for the MPEG-4 upstream =
messages
   SHALL be treated as the completely different kind of packets from the
   normal RTCP packets; such as SR, RR and so on.

   For example, if the particular RTCP packets would be included in the
   calculation of RTCP sending interval, the RR packets should be =
generated
   in the timing of the particular low delay RTCP packets.  In this =
case,
   the interval of the RR packets would be smaller than 5 seconds, and =
the
   number of the normal RTCP packets is much increased. It is bad for =
the
   congestion.

   Therefore all particular RTCP packets SHALL be ignored to analyze the
   information in the sender and receiver reports (SR and RR), and only
   normal RTCP packets are used.

   Multiple particular RTCP packets can be concatenated without any
   intervening separators to form a compound RTCP packet.  The normal
   compound RTCP packet SHOULD start with SR or RR packets. However in =
the
   case of compound particular RTCP packet, other normal RTCP packets =
SHALL
   NOT be included, and only particular RTCP packets SHALL be included =
in
   one compound particular RTCP packet.

5.6.  MPEG-4 Visual upstream message packets definition

Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 13]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D



        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=3D2|P|   UMT   | PT=3DRTCP_MP4U  |           length            =
  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                              SSRC                             |
       =
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
       |       MPEG-4 Upstream Messages Payload (byte aligned)         |
       |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                               :             padding           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   version (V): 2 bits
        Identifies the version of RTP, which is the same in RTCP packets =
as
       in RTP data packets.

   padding (P): 1 bit
        If the padding bit is set, this RTCP packet contains some =
additional
        padding octets at the end which are not part of the control
        information. The last octet of the padding is a count of how =
many
        padding octets should be ignored. In the case several upstream
        messages are mapped onto one RTCP packet, padding should only be
        required on the last individual message.

   upstream message type (UMT): 5 bits
       Identifies the type of the MPEG-4 upstream messages.
       0:       forbidden
       1:       MPEG-4 Visual NEWPRED in the ARTS Profile
       2-63:    reserved
       In this internet-draft, only the NEWPRED in the ARTS profile is
       assigned as the candidate of the UMT for the moment.  Some other
       MPEG-4 Audio/Visual applications using the upstream messages may =
be
       assigned in the future.

   packet type (PT): 8 bits
       The value of the packet type (PT) identifier is the constant
       RTCP_MP4U (TBD).

   SSRC: 32 bits
       SSRC is the synchronization source identifier for the sender of =
this
       packet.

   MPEG-4 Upstream Message Payload: variable
        The syntax and semantics of the MPEG-4 upstream messages are =
defined
        in the ISO/IEC 14496-2/3[4][5]. All messages are byte aligned.
        Normally one message is mapped onto one RTCP packet, and several
        messages with same UMT could be continuously mapped onto one =
RTCP
        packet.  One message SHALL NOT be fragmented into different RTCP
        packets.



Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 14]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D




6. MIME type registration for MPEG-4 Audio/Visual streams

   The following sections describe the MIME type registrations for the =
MPEG-
   4 Audio/Visual streams. MIME type registration and SDP usage for the
   MPEG-4 Visual stream are described in sections 6.1 and 6.2, =
respectively.
   MIME type registration and SDP usage for the MPEG-4 Audio stream are
   described in sections 6.3 and 6.4, respectively.

   (In the following sections, the RFC number "XXXX" represents the RFC
   number, which should be assigned for this Internet Draft.)


6.1 MIME type registration for MPEG-4 Visual

   MIME media type name: video

   MIME subtype name: MP4V

   Required parameters: none

   Optional parameters:
     rate: This parameter is used only for RTP transport. It indicates =
the
     resolution of the timestamp field in the RTP header. If this =
parameter
     is not specified, the default value of 90000 (90KHz) is used.

     profile-level-id: A decimal representation of MPEG-4 Visual Profile
     Level indication value (profile_and_level_indication) defined in =
Table
     G-1 of ISO/IEC 14496-2 [2][4].


     mpeg4-newpred-upstream-message: A boolean number to indicate the
     receiver capability of sending the upstream message of NEWPRED in
     MPEG-4 video. The upstream messages are delivered on the particular
     RTCP packets which are described in section 5. This optional exist
     when and only when the "profile-level-id" is 145, 146, 147 or 148
     (Advance Real Time Simple Profile/Level 1, 2, 3 or 4).

     Example usages for these parameters are show bellow:
       - MPEG-4 Visual Core Profile/Level 2:
          Content-type: video/mp4v; profile-level-id=3D34

       - MPEG-4 Visual Advanced Real Time Simple Profile/Level 1, =
upstream
       message is used:
          Content-type: video/mp4v; profile-level-id=3D145; =
mpeg4-newpred-
          upstream-message=3D1


   Published specification:
     The specification of MPEG-4 Visual stream is presented in ISO/IEC
     14469-2[2][4][9]. The RTP payload format is described in RFCXXXX.

Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 15]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D



   Encoding considerations:
     A video bitstream must be generated according to the MPEG-4 Visual
     specification (ISO/IEC 14496-2). The video bitstream is binary =
data,
     and must be encoded for non-binary transport; the Base64 encoding =
is
     suitable for Email. This type is also defined for transfer via RTP.
     The RTP packets must be packetized according to the MPEG-4 Visual =
RTP
     payload format defined in RFCXXXX.

   Security considerations:
     See section 9 of RFCXXXX.

   Interoperability considerations:
     MPEG-4 Visual provides a large and rich set of tools for the coding =
of
     visual objects. In order to allow effective implementations of the
     standard, subsets of the MPEG-4 Visual tool sets have been =
identified,
     that can be used for specific applications. These subsets, called
     'Profiles', limit the tool set a decoder has to implement. For each =
of
     these Profiles, one or more Levels have been set, restricting the
     computational complexity. A Profile@Level combination allows:

     o a codec builder to implement only the subset of the standard he
     needs, while maintaining interworking with other MPEG-4 devices =
built
     to the same combination, and

     o checking whether MPEG-4 devices comply with the standard
     ('conformance testing').

     The visual stream SHALL be compliant with the MPEG-4 Visual
     Profile@Level specified by the parameter "profile-level-id". The
     interoperability between a sender and a receiver may be achieved by
     specifying the parameter "profile-level-id" in MIME content, or by
     exchanging this parameter in the capability exchange procedure.


   Applications which use this media type:
     Audio and visual streaming and conferencing tools, Internet =
messaging
     and e-mail applications.

   Additional information: none

   Person & email address to contact for further information:
     The authors of RFCXXXX. (See section 9)

   Intended usage: COMMON

   Author/Change controller:
     The authors of RFCXXXX. (See section 9)


6.2 SDP usage of MPEG-4 Visual


Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 16]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


   The MIME media type video/MP4V string is mapped to fields in the =
Session
   Description Protocol (SDP), RFC 2327, as follows:

   o The MIME type (video) goes in SDP "m=3D" as the media name.

   o The MIME subtype (MP4V) goes in SDP "a=3Drtpmap" as the encoding =
name.

   o The optional parameter "rate" goes in "a=3Drtpmap" as clock rate.

   o The optional parameter "profile-level-id" MAY go in "a=3Dfmtp" =
line. The
   optional parameter "mpeg4-newpred-upstream-message" MAY go in =
"a=3Dfmtp"
   line, when and only when the "profile-level-id" is 145, 146, 147 or
   148(Advance Real Time Simple Profile/Level 1, 2, 3 or 4). The format =
and
   syntax of these parameters is the MIME media type string as a =
semicolon
   separated list of parameter=3Dvalue pairs.

   The followings are some examples of the media representation in SDP:

   Simple Profile/Level 1, rate=3D90000(90KHz), "profile-level-id" is =
present
   in "a=3Dfmtp" line:
     m=3Dvideo 49170/2 RTP/AVP 98
     a=3Drtpmap:98 MP4V/90000
     a=3Dfmtp:98 profile-level-id=3D1

   Advance Real Time Simple Profile/Level 1, rate=3D25(25Hz), =
"profile-level-
   id" and "      newpred-=0D            mpeg4-        upstream-message" =
are present in "a=3Dfmtp" line:
     m=3Dvideo 49170/2 RTP/AVP 98
     a=3Drtpmap:98 MP4V/25
     a=3Dfmtp:98 profile-level-id=3D145; =
mpeg4-newpred-upstream-message=3D1




6.3 MIME type registration of MPEG-4 Audio

   MIME media type name: audio

   MIME subtype name: MP4A

   Required parameters:
     rate: the rate parameter indicates the RTP time stamp clock rate. =
The
     default value is 90000. Other rates CAN be specified only if it =
would
     be set to the same value with the audio sampling rate (number of
     samples per second).

   Optional parameters:
     profile-level-id: a decimal representation of MPEG-4 Audio Profile
     Level indication value defined in ISO/IEC 14496-1 [11]. This =
parameter
     indicates the capability of subsets in MPEG-4 Audio tools.

     object: a decimal representation of MPEG-4 Audio Object Type value
     defined in ISO/IEC 14496-3 [5]. This parameter specifies the tool =
to

Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 17]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


     be used by the coder. It CAN be used to limit the capability within
     the specified "profile-level-id".

     bitrate: the data rate for the audio bit stream.

     cpresent: this parameter indicates whether audio payload =
configuration
     data is multiplexed into the RTP payload (See section 4.1 in this
     document).

     config: a hexadecimal representation of octet string indicating the
     audio payload configuration data "StreamMuxConfig" defined in =
ISO/IEC
     14496-3 [5]. The configuration data is mapped into the octet string =
in
     an MSB-first basis. The first bit of the configuration data shall =
be
     located at the MSB of the first octet. In the last octet, =
zero-padding
     bits shall follow the configuration data, if necessary.

     ptime: RECOMMENDED duration of each packet in milliseconds.

   Published specification:
     The payload format specification is described in this document. The
     specification of encoding is provided in ISO/IEC 14496-3 [3][5].

   Encoding considerations:
     This type is only defined for transfer via RTP [RFC YYYY, =
draft-ietf-
     avt-rtp-new].

   Security considerations:
     See section 9 of RFCXXXX.

   Interoperability considerations:
     MPEG-4 Audio provides a large and rich set of tools for the coding =
of
     visual objects. In order to allow effective implementations of the
     standard, subsets of the MPEG-4 Audio tool sets have been =
identified
     similar to MPEG-4 Audio (See section 6.1).

     The audio stream SHALL be compliant with the MPEG-4 Audio
     Profile@Level specified by the parameter "profile-level-id". The
     interoperability between a sender and a receiver may be achieved by
     specifying the parameter "profile-level-id" in MIME content, or by
     exchanging this parameter in the capability exchange procedure.
     Furthermore, the "object" parameter can be used to limit the
     capability within the specified Profile@Level in capability =
exchange.


   Applications which use this media type:
     Audio and video streaming and conferencing tools.

   Additional information: none

   Personal & email address to contact for further information:
     See section 9 of RFCXXXX.


Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 18]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D



   Intended usage: COMMON

   Author/Change controller:
     See section 9 of RFCXXXX.


6.4 SDP usage of MPEG-4 Audio

   The MIME media type audio/MP4A string is mapped to fields in the =
Session
   Description Protocol (SDP), RFC 2327, as follows:

   o The MIME type (audio) goes in SDP "m=3D" as the media name.

   o The MIME subtype (MP4A) goes in SDP "a=3Drtpmap" as the encoding =
name.

   o The required parameter "rate" goes in "a=3Drtpmap" as clock rate.

   o The optional parameter "ptime" goes in SDP "a=3Dptime" attribute.

   o The optional parameter "profile-level-id" goes in "a=3Dfmtp" line =
to
   indicate the coder capability. The "object" parameter goes in =
"a=3Dfmtp"
   attribute. Any payload-format-specific parameters "bitrate", =
"cpresent"
   and "config" go in "a=3Dfmtp" line. The format and syntax of these
   parameters is the MIME media type string as a semicolon separated =
list of
   parameter=3Dvalue pairs.

   The followings are some examples of the media representation in SDP:

   For 6 kb/s CELP bitstream (the audio sampling rate of 8 kHz),
     m=3Daudio 49230 RTP/AVP 96
     a=3Drtpmap:96 MP4A/8000
     a=3Dfmtp:96 =
profile-level-id=3D9;object=3D8;cpresent=3D0;config=3D9128B1071070
     a=3Dptime:20

   For 64 kb/s AAC LC stereo bitstream (the audio sampling rate is 24 =
kHz),
     m=3Daudio 49230 RTP/AVP 96
     a=3Drtpmap:96 MP4A/24000
     a=3Dfmtp:96 profile-level-id=3D1; bitrate=3D64000; cpresent=3D0;
     config=3D9122620000

   In the above two examples, the audio configuration data is not
   multiplexed into the RTP payload and is described only in SDP.
   Furthermore, the "clock rate" is set to the audio sampling rate. If =
it is
   set to its default, the audio sampling rate can be obtained by =
parsing
   the "config" parameter.

   The following example shows that the audio configuration data appears =
in
   the RTP payload. The value specified in "config" parameter is used as =
an
   initial value to setup coding parameters.



Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 19]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D


     m=3Daudio 49230 RTP/AVP 96
     a=3Drtpmap:96 MP4A/90000
     a=3Dfmtp:96 cpresent=3D1; config=3D9128B1071070




7. Security Considerations

   RTP packets using the payload format defined in this specification =
are
   subject to the security considerations discussed in the RTP =
specification
   [8]. 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 on the compressed =
data
   so there is no conflict between the two operations.

   This payload type does not exhibit any significant non-uniformity in =
the
   receiver side computational complexity for packet processing  to =
cause a
   potential denial-of-service threat.


8. References


   1  Bradner, S., "The Internet Standards Process -- Revision 3", BCP =
9,
      RFC 2026, October 1996.

   2 ISO/IEC 14496-2:1999, "Information technology - Coding of =
audio-visual
      objects - Part2: Visual", December 1999.

   3 ISO/IEC 14496-3:1999, "Information technology - Coding of =
audio-visual
      objects - Part3: Audio", December 1999.

   4 ISO/IEC 14496-2:1999/FDAM1:2000, December 1999.

   5 ISO/IEC 14496-3:1999/FDAM1:2000, December 1999.

   6 ISO/IEC 14496-1:1999, "Information technology - Coding of =
audio-visual
      objects - Part1: Systems", December 1999.

   7  Bradner, S., "Key words for use in RFCs to Indicate Requirement
      Levels", BCP 14, RFC 2119, March 1997

   8 H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson "RTP: A =
Transport
      Protocol for Real Time Applications",  RFC 1889, Internet =
Engineering
      Task Force, January 1996.

   9  ISO/IEC 14496-2/COR1, "Information technology - Coding of =
audio-visual
      objects - Part2: Visual, Technical corrigendum 1", March 2000.




Kikuchi/Nomura/Fukunaga/Kimata/Matsui                        [Page 20]
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D




9. Author's Addresses


   Yoshihiro Kikuchi
   Toshiba corporation
   1, Komukai Toshiba-cho, Saiwai-ku, Kawasaki, 212-8582, Japan
   Email: yoshihiro.kikuchi@toshiba.co.jp

   Yoshinori Matsui
   Matsushita Electric Industrial Co., LTD.
   1006, Kadoma, Kadoma-shi, Osaka, Japan
   Email: matsui@drl.mei.co.jp

   Toshiyuki Nomura
   NEC Corporation
   4-1-1,Miyazaki,Miyamae-ku,Kawasaki,JAPAN
   Email: t-nomura@ccm.cl.nec.co.jp

   Shigeru Fukunaga
   Oki Electric Industry Co., Ltd.
   1-2-27 Shiromi, Chuo-ku, Osaka 540-6025 Japan.
   Email: fukunaga444@oki.co.jp

   Hideaki Kimata
   Nippon Telegraph and Telephone Corporation
   1-1, Hikari-no-oka, Yokosuka-shi, Kanagawa, Japan
   Email: kimata@nttvdt.hil.ntt.co.jp
=0CRTP payload format for MPEG-4 Audio/Visual streams       February =
2000=0D



Full Copyright Statement

   "Copyright (C) The Internet Society (date). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph
   are included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.
=0C
------=_NextPart_000_01E7_01BFCAF0.97899040--




From rem-conf Tue May 30 23:32:09 2000 
From rem-conf-request@es.net Tue May 30 23:32:09 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12x1y2-0005cT-00; Tue, 30 May 2000 23:27:02 -0700
Received: from talos.forthnet.gr (forthnet.gr) [193.92.150.21] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12x1y0-0005Po-00; Tue, 30 May 2000 23:27:00 -0700
Received: from oemcomputer.unipi.gr (assinik.ath.forthnet.gr [193.92.136.196])
	by forthnet.gr (8.8.8/8.8.5) with ESMTP id IAA31406;
	Wed, 31 May 2000 08:09:16 +0300
Message-Id: <4.3.1.0.20000510233153.00a854a0@assinik.ath.forthnet.gr/popper.forthnet.gr@127.0.0.1>
X-Sender: ASSINIK@assinik.ath.forthnet.gr/popper.forthnet.gr@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 31 May 2000 08:09:32 +0300
To: assinik@unipi.gr
From: Nikitas Assimakopoulos <assinik@unipi.gr>
Subject: Special Issues of  JASS journal
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1188875==_.ALT"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

--=====================_1188875==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed


-------------------------------------------------------------------
   We extend our sincere apologies if this announcement
    would disturb your inbox with multiple copies of it.
-------------------------------------------------------------------

Journal of Applied Systems Studies
       Methodologies and Applications for Systems Approaches
                         ' JASS '

                   http://www.unipi.gr/jass/

JASS announces that the following Special Issues have been scheduled :

         "Challenges Facing General Systems in Practice"
         "Creative Processes in Natural and Human Systems"
         "Distributed Multimedia Systems with Applications"
         "Applications of Electronic Commerce Systems"
         "WEB Information Systems Applications"
         "Industrial Applications of Multi-Agent and Holonic Systems"
         "Anticipating the Effects of the Year 2000 Problem"

If you are interested in the above special issue titles  AND  for the 
current issues, please visit  JASS  web site.
For submission of papers and special issue proposals consult the "Aims & 
Scope" of  JASS.




--=====================_1188875==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<font size=3><br>
-------------------------------------------------------------------<br>
</font><font size=2>&nbsp; We extend our sincere apologies if this
announcement<br>
&nbsp;&nbsp; would disturb your inbox with multiple copies of it.<br>
</font><font size=3>-------------------------------------------------------------------<br>
<br>
</font><font size=6 color="#0000FF"><b>J</font><font size=5 color="#0000FF">ournal
of
</font><font size=6 color="#0000FF">A</font><font size=5 color="#0000FF">pplied
</font><font size=6 color="#0000FF">S</font><font size=5 color="#0000FF">ystems
</font><font size=6 color="#0000FF">S</font><font size=5 color="#0000FF">tudies<br>
</b></font><font size=2 color="#0000FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Methodologies and Applications for Systems Approaches<br>
</font><font size=3 color="#0000FF"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</font><font size=5 color="#0000FF"><b>' JASS '
</font><font size=2 color="#0000FF">&nbsp; <br>
<br>
</b></font><font size=3><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&nbsp;
<a href="http://www.unipi.gr/jass/" eudora="autourl">http://www.unipi.gr/jass/</a><br>
<br>
JASS announces that the following Special Issues have been scheduled
:<br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;Challenges
Facing General Systems in Practice&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;Creative
Processes in Natural and Human Systems&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;Distributed
Multimedia Systems with Applications&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;Applications
of Electronic Commerce Systems&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;WEB
Information Systems Applications&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;Industrial
Applications of Multi-Agent and Holonic Systems&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;Anticipating
the Effects of the Year 2000 Problem&quot;<br>
<br>
If you are interested in the above special issue titles&nbsp;
<b>AND</b>&nbsp; for the current issues, please visit&nbsp; JASS&nbsp;
web site.<br>
For submission of papers and special issue proposals consult the
&quot;Aims &amp; Scope&quot; of&nbsp; JASS.<br>
<br>
<br>
<br>
</font></html>

--=====================_1188875==_.ALT--




From rem-conf Wed May 31 00:16:52 2000 
From rem-conf-request@es.net Wed May 31 00:16:52 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12x2f9-00016Z-00; Wed, 31 May 2000 00:11:35 -0700
Received: from soleil.uvsq.fr [193.51.24.1] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12x2f7-00016P-00; Wed, 31 May 2000 00:11:34 -0700
Received: from atlas.ens.uvsq.fr (root@atlas.ens.uvsq.fr [193.51.26.1])
          by soleil.uvsq.fr (8.9.3/jtpda-5.3.3) with ESMTP id JAA46314
          ; Wed, 31 May 2000 09:11:28 +0200 (CEST)
Received: from ens.uvsq.fr (res.iut-velizy.uvsq.fr [193.51.36.116])
          by atlas.ens.uvsq.fr (8.9.3/jtpda-5.2) with ESMTP id JAA46331
          ; Wed, 31 May 2000 09:11:27 +0200 (CEST)
Sender: ftp@ens.uvsq.fr
Message-ID: <3934BB57.E18FB82@ens.uvsq.fr>
Date: Wed, 31 May 2000 08:12:23 +0100
From: Ftp Anonyme <tahmed@ens.uvsq.fr>
Organization: Iut de =?iso-8859-1?Q?V=E9lizy=20D=E9partement?= SRC
X-Mailer: Mozilla 4.72 [en] (X11; I; SunOS 5.6 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF AVT <rem-conf@es.net>, tahmed@ens.uvsq.fr, tahmed@prism.uvsq.fr
Subject: can someone submit a draft to avt group?
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by soleil.uvsq.fr id JAA46314
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

hello,
Can I (I'm student ) sumbit a draft ?
I'm working for transmission of MPEG-4 over RTP.
what can I do in this case ?
best regards.


AHMED TOUFIK
PRiSM Laboratory - CNRS UMR 86 36
Computer Science Department
Universit=E9 de Versailles-Saint Quentin en Yvelines (UVSQ)
 45, avenue des Etats-Unis, 78035 Versailles Cedex, France
Phone: 33 1 39 25 43 13 from abroad / 01 39 25 43 13  in France
Fax:     33 1 39 25 40 57  from abroad / 01 39 25 40 57  in France
E-mail: tahmed@prism.uvsq.fr, tahmed@ens.uvsq.fr






From rem-conf Wed May 31 00:28:35 2000 
From rem-conf-request@es.net Wed May 31 00:28:35 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12x2qr-00022R-00; Wed, 31 May 2000 00:23:41 -0700
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12x2qp-00020a-00; Wed, 31 May 2000 00:23:40 -0700
Received: from kraftbus.cs.tu-berlin.de (130-149-145-192.dialup.cs.tu-berlin.de [130.149.145.192])
	by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id JAA08070;
	Wed, 31 May 2000 09:19:26 +0200 (MET DST)
Message-Id: <4.3.2.20000531085222.00dd0b60@mail.cs.tu-berlin.de>
X-Sender: stewe@mail.cs.tu-berlin.de
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Wed, 31 May 2000 09:21:04 +0200
To: "Yoshihiro Kikuchi" <kiku@eel.rdc.toshiba.co.jp>,
        "4on2andIP-sys" <4on2andIP-sys@advent.ee.columbia.edu>,
        "IETF AVT" <rem-conf@es.net>
From: Stephan Wenger <stewe@cs.tu-berlin.de>
Subject: Re: Updated I/D for MPEG-4 Audio/Visual RTP payload format
In-Reply-To: <01ec01bfcaa5$28ce8160$19c77885@ave>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Dear all,

I have a some concerns with the current draft.

Number one is the language quality, which really needs
improvement.  An English native speaker should look
through this.  No insult intended :-)

Number two is technical, and much more important.  It
is related to the RTCP-based back channel for NEWPRED in
section 5.

I believe that, when a payload specification defines RTCP-based
feedback, at least the most common mechanisms that could
also use RTCP-based feedback should also be defined.  For
predictive video coding this would be at least a Full Intra Refresh.
Compared to NEWPRED, FIR has obvious disadvantages in
terms of bitrate and delay, but the advantage of being available
in ALL profiles/levels of MPEG-4 visual.  NEWPRED, on the
other hand, is only available when the ARTS profile is implemented,
implying (at least) version 2 of MPEG-4.

I could also think of other back channel messages that report the
loss of single slices, or even macroblocks, and similar.

During a recent ITU-T meeting in Osaka I had the chance to talk
to Mr. Fukunaga regarding this.  There, I promised to come up
with some text to include FIR into the draft.  Unfortunately I was
unable to do this in a as timely fashion as promised, because
a) work overload and b) there is a need for a complete rewriting
of section 5 of the draft.

Why this?  Currently, although the syntax of the RTCP packets
is already general enough to accommodate FIR and other schemes,
the text is only concerned with NEWPRED.  NEWPRED has
certain attributes, which might not be of similar importance to
other schemes.  It is, for example, absolutely necessary to send
NEWPRED NACK messages in a timely fashion in order to make
NEWPRED effective.  Therefore, the draft suggests to send
RTCP packets containing feedback messages without waiting the
random delays suggested for Receiver Reports.  To avoid the
resulting network flooding problems, the draft further limits the
use of RTCP-based feedback to unicast.

While all this makes totally sense for NEWPRED, sending FIR
is not as time critical as NEWPRED, and would thus allow for
using random delays, which in turn would allow to use multicast.

For this reason (and other, similar reasons) it is much more effort to
include FIR into the draft then I originally anticipated.  It is only an
editing job, but a tricky one.

Comments?  Does it make sense to continue this editing job?

Stephan

At 11:08 AM 5/31/00 +0900, Yoshihiro Kikuchi wrote:
>Dear MPEG-4 on IP experts,
>
>I have just submitted the attached text as an updated Internet-Draft for the
>MPEG-4 Audio/Visual RTP payload format.
>
>The following is the list of changes from the previous Internet-Draft.
>
>(1) Revision on the MPEG-4 upstream message RTCP (Section 5)
>The RTCP specification was changed according to the discussion at the
>Adelaide meeting.
>
>(2) MIME type registration (Section 6)
>As announced in Adelaide, a new section was added for the MIME type
>registrations and SDP usages of MPEG-4 Audio/Visual streams.
>
>(3) Some other clarifications and wording changes.
>
>There is no essential change on the RTP part from the previous version,
>which was verified and demonstrated by companies in Noordwijkerhout.
>
>If you have any comments and questions, please let us know. Depend on the
>discussion, we may provide another updated I/D with reflecting all comments
>and suggestions, which should be the very final version of the I/D. We hope
>we can finalize it by the end of the next week. We appreciate if we can have
>all comments, if any, by then.
>
>Best regards,
>Yoshihiro
>
>----
>         Yoshihiro Kikuchi
>
>E-mail: kiku@eel.rdc.toshiba.co.jp
>Corporate Research and Development Center
>TOSHIBA Corporation
>TEL: +81 +44 549 2288    FAX: +81 +44 520 1267
>
>





From rem-conf Wed May 31 00:44:59 2000 
From rem-conf-request@es.net Wed May 31 00:44:59 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12x376-0004IA-00; Wed, 31 May 2000 00:40:28 -0700
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12x374-0004Hy-00; Wed, 31 May 2000 00:40:27 -0700
Received: from kraftbus.cs.tu-berlin.de (130-149-145-202.dialup.cs.tu-berlin.de [130.149.145.202])
	by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id JAA09871
	for <rem-conf@es.net>; Wed, 31 May 2000 09:36:06 +0200 (MET DST)
Message-Id: <4.3.2.20000531092714.00dc2210@mail.cs.tu-berlin.de>
X-Sender: stewe@mail.cs.tu-berlin.de
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Wed, 31 May 2000 09:41:54 +0200
To: rem-conf@es.net
From: Stephan Wenger <stewe@cs.tu-berlin.de>
Subject: Question on RFC2733, packet-based FEC
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Hi all,

I don't understand the reason for an (artificial?) limitation of
RFC2733.  RFC2733 says that, when calculating FEC over
several packets of different sizes, the FEC packet has to
protect all bytes of the biggest packet (and padding is to be
used for the other packets to bring them up to the size of
the biggest packet).  Is there some hidden secret about this
requirement?

The rest of the EMail describes scenarios where this limitation
is counter-productive.

In a recent ITU meeting, Adam Li of UCLA brought to our
attention an idea to implement unequal error protection using
packet based FEC.  What they want to do is to use data
partitioning to put important video data (such as headers and
motion vectors) to the front of a packet, and put the less
important coefficients to the end.  Then apply packet based
FEC only on the first (more important) part of the packets.
Resulting FEC packets are smaller -- lower bandwidth requirements.

Thinking about this idea, several more applications come
readily in mind.  When using FEC on RTP packets using audio
redundancy coding, you can protect only the original audio
but not the redundant copy.  This could, for example, make
sense in a multi-unicast environment with very different QoS
to the various endpoint (telephone conference with wired and
wireless terminals -- the conference bridge applies FEC only
for the wireless links).

So, why MUST a FEC packet protect all bytes of any source packet?

Stephan




From rem-conf Wed May 31 02:31:23 2000 
From rem-conf-request@es.net Wed May 31 02:31:23 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12x4lq-0003Rh-00; Wed, 31 May 2000 02:26:38 -0700
Received: from soleil.uvsq.fr [193.51.24.1] (root)
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12x4lp-0003RX-00; Wed, 31 May 2000 02:26:37 -0700
Received: from atlas.ens.uvsq.fr (root@atlas.ens.uvsq.fr [193.51.26.1])
          by soleil.uvsq.fr (8.9.3/jtpda-5.3.3) with ESMTP id LAA58821
          ; Wed, 31 May 2000 11:26:29 +0200 (CEST)
Received: from ens.uvsq.fr (src-012.iut-velizy.uvsq.fr [193.51.29.97])
          by atlas.ens.uvsq.fr (8.9.3/jtpda-5.2) with ESMTP id LAA63819
          ; Wed, 31 May 2000 11:26:29 +0200 (CEST)
Sender: tahmed@ens.uvsq.fr
Message-ID: <3934DAC4.EEAB95F3@ens.uvsq.fr>
Date: Wed, 31 May 2000 11:26:29 +0200
From: LAHLOU ABDELKRIM <alahlo@ens.uvsq.fr>
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.4-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF AVT <rem-conf@es.net>, tahmed@ens.uvsq.fr, tahmed@prism.uvsq.fr
Subject: can someone submit a draft to avt group?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

hello,
Can I (I'm student ) sumbit a draft ?
I'm working for transmission of MPEG-4 over RTP.
what can I do in this case ?
best regards.


AHMED TOUFIK
PRiSM Laboratory - CNRS UMR 86 36
Computer Science Department
Universit=E9 de Versailles-Saint Quentin en Yvelines (UVSQ)
 45, avenue des Etats-Unis, 78035 Versailles Cedex, France
Phone: 33 1 39 25 43 13 from abroad / 01 39 25 43 13  in France
Fax:     33 1 39 25 40 57  from abroad / 01 39 25 40 57  in France
E-mail: tahmed@prism.uvsq.fr, tahmed@ens.uvsq.fr






From rem-conf Wed May 31 05:34:43 2000 
From rem-conf-request@es.net Wed May 31 05:34:41 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12x7bm-00078g-00; Wed, 31 May 2000 05:28:26 -0700
Received: from bells.cs.ucl.ac.uk [128.16.5.31] 
	by mail1.es.net with smtp (Exim 1.81 #2)
	id 12x7bl-00078B-00; Wed, 31 May 2000 05:28:25 -0700
Received: from csperkins.demon.co.uk by bells.cs.ucl.ac.uk with UK SMTP 
          id <g.23591-0@bells.cs.ucl.ac.uk>; Wed, 31 May 2000 13:27:39 +0100
Received: from csperkins.demon.co.uk (localhost [127.0.0.1]) 
          by csperkins.demon.co.uk (8.9.3/8.8.7) with ESMTP id NAA02102;
          Wed, 31 May 2000 13:26:22 +0100
Message-Id: <200005311226.NAA02102@csperkins.demon.co.uk>
To: LAHLOU ABDELKRIM <alahlo@ens.uvsq.fr>
cc: IETF AVT <rem-conf@es.net>, tahmed@ens.uvsq.fr, tahmed@prism.uvsq.fr
Subject: Re: can someone submit a draft to avt group?
In-Reply-To: Message from LAHLOU ABDELKRIM <alahlo@ens.uvsq.fr> of "Wed, 31 May 2000 11:26:29 +0200." <3934DAC4.EEAB95F3@ens.uvsq.fr>
Date: Wed, 31 May 2000 13:26:22 +0100
From: Colin Perkins <c.perkins@cs.ucl.ac.uk>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

--> LAHLOU ABDELKRIM writes:
>Can I (I'm student ) sumbit a draft ?

The IETF standards process is open to all, and anyone can make an individual 
submission to the AVT working group. Such drafts appear in the archive with 
a filename of the form draft-authorname-avt-...-00.txt. This is the way new
work enters the standards process.

In order for a draft to gain the draft-ietf-avt- prefix, it has to be
accepted as a work item of the group, and be approved for publication 
by the working group chairs. This typically involves presentation of 
the work at an IETF meeting, and rough consensus of the group members
that the work is worthwhile and relevent to the group.

There are guidelines for authors of internet-drafts available from
	http://www.ietf.org/ietf/1id-guidelines.txt
and the working group chairs can also provide advice.

>I'm working for transmission of MPEG-4 over RTP.
>what can I do in this case ?

Before submitting your draft, I would strongly urge you to study the
existing proposals in the area, and to review the mailing list archives and
minutes of past discussions. Identify why we need another standard in this
area, and what problems you solve which can't be solved with the existing
proposals.

Colin



From rem-conf Wed May 31 08:44:06 2000 
From rem-conf-request@es.net Wed May 31 08:44:04 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xAZC-0002ch-00; Wed, 31 May 2000 08:37:58 -0700
Received: from okigate.oki.co.jp (titanic.kansai.oki.co.jp) [202.226.91.194] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xAZA-0002cX-00; Wed, 31 May 2000 08:37:57 -0700
Received: from kangaroo (kansai.kansai.oki.co.jp [10.173.5.1])
	by titanic.kansai.oki.co.jp (8.9.3/3.7W) with SMTP id AAA54289;
	Thu, 1 Jun 2000 00:37:42 +0900 (JST)
Message-ID: <006301bfcb16$81489580$e750fea9@kangaroo>
From: "Shigeru Fukunaga" <fukunaga444@oki.co.jp>
To: "Yoshihiro Kikuchi" <kiku@eel.rdc.toshiba.co.jp>,
        "4on2andIP-sys" <4on2andIP-sys@advent.ee.columbia.edu>,
        "IETF AVT" <rem-conf@es.net>, "Stephan Wenger" <stewe@cs.tu-berlin.de>
References: <4.3.2.20000531085222.00dd0b60@mail.cs.tu-berlin.de>
Subject: Re: Updated I/D for MPEG-4 Audio/Visual RTP payload format
Date: Thu, 1 Jun 2000 00:38:36 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

Dear Stephan and all,

Thank you for your comment to our draft.

> Number two is technical, and much more important.  It
> is related to the RTCP-based back channel for NEWPRED in
> section 5.
> 
> I believe that, when a payload specification defines RTCP-based
> feedback, at least the most common mechanisms that could
> also use RTCP-based feedback should also be defined.  For
> predictive video coding this would be at least a Full Intra Refresh.
> Compared to NEWPRED, FIR has obvious disadvantages in
> terms of bitrate and delay, but the advantage of being available
> in ALL profiles/levels of MPEG-4 visual.  NEWPRED, on the
> other hand, is only available when the ARTS profile is implemented,
> implying (at least) version 2 of MPEG-4.

RTCP for FIR seems good idea, however, there are some problems.

At first, we would like to describe only MPEG-4 specific things in this draft. 
As FIR is a common technique for all video coding, other common document
seems to be appropriate.

Second, new proposal just before the last call is not good. We largely discussed
the issues of RTCP for NEWPRED since Adelade meeting, and revised text.
It also takes much time to discuss FIR, however, we have enough time.

> During a recent ITU-T meeting in Osaka I had the chance to talk
> to Mr. Fukunaga regarding this.  There, I promised to come up
> with some text to include FIR into the draft.  Unfortunately I was
> unable to do this in a as timely fashion as promised, because
> a) work overload and b) there is a need for a complete rewriting
> of section 5 of the draft.

I was looking forward to seeing your revision.

> Why this?  Currently, although the syntax of the RTCP packets
> is already general enough to accommodate FIR and other schemes,
> the text is only concerned with NEWPRED.  NEWPRED has
> certain attributes, which might not be of similar importance to
> other schemes.  It is, for example, absolutely necessary to send
> NEWPRED NACK messages in a timely fashion in order to make
> NEWPRED effective.  Therefore, the draft suggests to send
> RTCP packets containing feedback messages without waiting the
> random delays suggested for Receiver Reports.  To avoid the
> resulting network flooding problems, the draft further limits the
> use of RTCP-based feedback to unicast.

I think you mean the FIR RTCP in H.261 paylord format (FRC2032).
The description of FIR RTCP of the RFC seems to be not good for 
the current networks. Therefore Steve advised us to add many descriptions
of the congestion control for NEWPRED RTCP, and limit to unicast.

> While all this makes totally sense for NEWPRED, sending FIR
> is not as time critical as NEWPRED, and would thus allow for
> using random delays, which in turn would allow to use multicast.
> 
> For this reason (and other, similar reasons) it is much more effort to
> include FIR into the draft then I originally anticipated.  It is only an
> editing job, but a tricky one.

Again it is better that FIR RTCP is defined in the common document.

Best Regards,
Shigeru
--
   Shigeru Fukunaga (fukunaga444@oki.co.jp)
   Oki Electric Industry Co., LTD.
   Tel. +81 6 6949 5101; Fax. +81 6 6949 5108







From rem-conf Wed May 31 09:04:38 2000 
From rem-conf-request@es.net Wed May 31 09:04:37 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12xAvB-0005hO-00; Wed, 31 May 2000 09:00:41 -0700
Received: from igate.nuera.com ([204.216.240.98] helo=sd_exchange.nuera.com)
	by mail2.es.net with esmtp (Exim 1.92 #1)
	for rem-conf@es.net
	id 12xAv9-0005hE-00; Wed, 31 May 2000 09:00:39 -0700
Received: by sd_exchange.nuera.com with Internet Mail Service (5.5.2650.21)
	id <LQR7WZWB>; Wed, 31 May 2000 08:59:05 -0700
Message-ID: <613A6A6A3F09D3118F5C00508B2C24FE67A71A@sd_exchange.nuera.com>
From: "Bratakos, Maroula" <mbratakos@nuera.com>
To: 'Dan Wing' <dwing@cisco.com>
Cc: rem-conf@es.net
Subject: RE: RFC 2833 on Tones
Date: Wed, 31 May 2000 08:59:04 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

I agree that if bandwidth is a problem then you probably only want to send
one representation for the signaling event/dtmf digit.  However, the RFC
2833 says you should (not MUST but SHOULD) send signaling events as both
named signals and tone representation and if you can't send the tone
representation then you should sent regular audio.  My point was that if you
are going to send both then I think it needs to be formated in the redundant
format of 2198.

> I have a question about the last paragraph in section 2 that discusses
> gateways which send signaling events via RTP.  It states: 
> 
> If a gateway cannot present a tone representation, it SHOULD send the
> audio tones as regular RTP audio packets (e.g., as payload format
> PCMU), in addition to the named signals.
>
> If the audio tones are sent along with named signals then shouldn't the
> redundant method of RFC 2198 be used?

That would cause 'issues' (to put it mildly) if you're on any sort of
bandwidth allocation or near the saturation point for the access link,
such as with DSL or cable.

For example, if the admitted calls are currently consuming nearly
all of the upstream bandwidth, then doubling the bandwidth consumed
when someone touches a DTMF keypad will cause problems for the other
calls using that link.

-Dan Wing




From rem-conf Wed May 31 10:48:36 2000 
From rem-conf-request@es.net Wed May 31 10:48:36 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xCXp-0005tx-00; Wed, 31 May 2000 10:44:41 -0700
Received: from canospam.agcs.com [130.131.166.29] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xCXo-0005rw-00; Wed, 31 May 2000 10:44:40 -0700
Received: from frontier. (marshal.agcs.com [130.131.60.2])
	by canospam.agcs.com (8.9.3/8.9.1) with SMTP id KAA21994
	for <rem-conf@es.net>; Wed, 31 May 2000 10:43:38 -0700 (MST)
Posted-Date: Wed, 31 May 2000 10:43:38 -0700 (MST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.168.5])
	by bootstrap.agcs.com (Pro-8.9.3/8.9.3) with ESMTP id KAA03920
	for <rem-conf@es.net>; Wed, 31 May 2000 10:43:21 -0700 (MST)
Received: from agcs.com ([130.131.108.94]) by pxmail1.agcs.com
          (Netscape Messaging Server 3.61)  with ESMTP id AAA4130;
          Wed, 31 May 2000 10:43:25 -0700
Message-ID: <39354F38.1912A938@agcs.com>
Date: Wed, 31 May 2000 10:43:21 -0700
From: "Rex Coldren" <coldrenr@agcs.com>
Reply-To: coldrenr@agcs.com
Organization: AG Communication Systems
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
CC: "Bratakos, Maroula" <mbratakos@nuera.com>, rem-conf@es.net
Subject: Re: RFC 2833 on Tones
References: <0005301808390.5220-100000@omega.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list



Dan Wing wrote:

> On Tue, 30 May 2000 17:05 -0700, Bratakos, Maroula wrote:
>
> > I have a question about the last paragraph in section 2 that discusses
> > gateways which send signaling events via RTP.  It states:
> >
> > If a gateway cannot present a tone representation, it SHOULD send the
> > audio tones as regular RTP audio packets (e.g., as payload format
> > PCMU), in addition to the named signals.
> >
> > If the audio tones are sent along with named signals then shouldn't the
> > redundant method of RFC 2198 be used?
>
> That would cause 'issues' (to put it mildly) if you're on any sort of
> bandwidth allocation or near the saturation point for the access link,
> such as with DSL or cable.
>
> For example, if the admitted calls are currently consuming nearly
> all of the upstream bandwidth, then doubling the bandwidth consumed
> when someone touches a DTMF keypad will cause problems for the other
> calls using that link.
>

Yeah, not to mention the fact that if there's policing/filtering being done on the
upstream link the transmitter is liable to get busted.

In any event, sending the DTMF events in addition to the RTP stream will not
necessarily double the bandwidth used.  And you have more than one option
for sending the DTMF (events and tonal representations).  RFC 2833 is set
up to use less bandwidth than the original encoding, in general.  When used
with RFC 2198, the number of redundant encodings also has an impact on the
total bandwidth used.

>
> -Dan Wing




From rem-conf Wed May 31 11:01:37 2000 
From rem-conf-request@es.net Wed May 31 11:01:37 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xCm5-0006q5-00; Wed, 31 May 2000 10:59:25 -0700
Received: from lint.cisco.com [171.68.224.209] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xCm4-0006oS-00; Wed, 31 May 2000 10:59:24 -0700
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA06951; Wed, 31 May 2000 10:57:49 -0700 (PDT)
Date: Wed, 31 May 2000 10:57:49 -0700 (PDT)
From: Dan Wing <dwing@cisco.com>
To: Rex Coldren <coldrenr@agcs.com>
cc: "Bratakos, Maroula" <mbratakos@nuera.com>, rem-conf@es.net
Subject: Re: RFC 2833 on Tones
In-Reply-To: <39354F38.1912A938@agcs.com>
Message-ID: <0005311046400.19593-100000@omega.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

On Wed, 31 May 2000 10:43 -0700, Rex Coldren wrote:

> Dan Wing wrote:
> 
> > On Tue, 30 May 2000 17:05 -0700, Bratakos, Maroula wrote:
> >
> > > I have a question about the last paragraph in section 2 that discusses
> > > gateways which send signaling events via RTP.  It states:
> > >
> > > If a gateway cannot present a tone representation, it SHOULD send the
> > > audio tones as regular RTP audio packets (e.g., as payload format
> > > PCMU), in addition to the named signals.
> > >
> > > If the audio tones are sent along with named signals then shouldn't the
> > > redundant method of RFC 2198 be used?
> >
> > That would cause 'issues' (to put it mildly) if you're on any sort of
> > bandwidth allocation or near the saturation point for the access link,
> > such as with DSL or cable.
> >
> > For example, if the admitted calls are currently consuming nearly
> > all of the upstream bandwidth, then doubling the bandwidth consumed
> > when someone touches a DTMF keypad will cause problems for the other
> > calls using that link.
> >
> 
> Yeah, not to mention the fact that if there's policing/filtering being
> done on the upstream link the transmitter is liable to get busted.
> 
> In any event, sending the DTMF events in addition to the RTP stream
> will not necessarily double the bandwidth used.

Agreed.

> And you have more than one option for sending the DTMF (events and
> tonal representations). 

Yes.  Actually, there are three mechanisms:

  1. audio tones
  2. events, as per RFC2833
  3. both, which is what is recommended in RFC2833

Maroula Bratakos' message about using RFC2198 to duplicate packets
concerned (3).  I'm sure there was an intent to also cover (1) but that
requires a DTMF detector, in which case you would expect an implementation
to do (3).

> RFC 2833 is set up to use less bandwidth than the original encoding,
> in general. 

Agreed.

> When used with RFC 2198, the number of redundant encodings also has an
> impact on the total bandwidth used.


I think the duplication has merit, but appropriate text is required
explaining when such RFC2198 duplication of DTMF tones isn't appropriate.

Perhaps a simple MAY is good enough, but only if we assume implementors
will understand why it's a MAY instead of SHOULD or MUST.  I haven't read
RFC2198 in awhile, but it may have text which explains some of the
drawbacks of arbitrary duplication of packets in a bandwidth-constrained
or policed network.  My quick skim of RFC2198 didn't turn up such text,
however.

-Dan Wing





From rem-conf Wed May 31 11:58:40 2000 
From rem-conf-request@es.net Wed May 31 11:58:38 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xDdS-0000QL-00; Wed, 31 May 2000 11:54:34 -0700
Received: from canospam.agcs.com [130.131.166.29] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xDdQ-0000Q9-00; Wed, 31 May 2000 11:54:32 -0700
Received: from frontier. (marshal.agcs.com [130.131.60.2])
	by canospam.agcs.com (8.9.3/8.9.1) with SMTP id LAA24871
	for <rem-conf@es.net>; Wed, 31 May 2000 11:53:28 -0700 (MST)
Posted-Date: Wed, 31 May 2000 11:53:28 -0700 (MST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.168.5])
	by bootstrap.agcs.com (Pro-8.9.3/8.9.3) with ESMTP id LAA06950
	for <rem-conf@es.net>; Wed, 31 May 2000 11:53:11 -0700 (MST)
Received: from agcs.com ([130.131.108.94]) by pxmail1.agcs.com
          (Netscape Messaging Server 3.61)  with ESMTP id AAA4967;
          Wed, 31 May 2000 11:14:05 -0700
Message-ID: <39355668.6B6E05F8@agcs.com>
Date: Wed, 31 May 2000 11:14:00 -0700
From: "Rex Coldren" <coldrenr@agcs.com>
Reply-To: coldrenr@agcs.com
Organization: AG Communication Systems
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
CC: "Bratakos, Maroula" <mbratakos@nuera.com>, rem-conf@es.net
Subject: Re: RFC 2833 on Tones
References: <0005311046400.19593-100000@omega.cisco.com>
Content-Type: multipart/alternative;
 boundary="------------4ED5415FF03FADE4790E482C"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


--------------4ED5415FF03FADE4790E482C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dan Wing wrote:

> > When used with RFC 2198, the number of redundant encodings also has an
> > impact on the total bandwidth used.
>
> I think the duplication has merit, but appropriate text is required
> explaining when such RFC2198 duplication of DTMF tones isn't appropriate.
>
> Perhaps a simple MAY is good enough, but only if we assume implementors
> will understand why it's a MAY instead of SHOULD or MUST.  I haven't read
> RFC2198 in awhile, but it may have text which explains some of the
> drawbacks of arbitrary duplication of packets in a bandwidth-constrained
> or policed network.  My quick skim of RFC2198 didn't turn up such text,
> however.

You're right.  I don't think it's there.

Note that the usual situation involving the need to send DTMF tones outside of
the normal RTP payload implies that the tones inside the normal RTP payload
are of no use, or at least should not be trusted.  Indeed, in many/all cases you
would want to strip those tones out of the normal RTP payload when sending
via RFC 2833/2198 methods.  Consequently, the normal RTP payload has an
element of mutual exclusivity with the RTP payload used to carry the RFC
2833/2198 encodings.  Some benefit can be gained from this knowledge when
the access network is bandwidth limited, as in the cable and DSL cases.

RFC 2833 does not address the possibility of replacing normal RTP payloads
with RFC 2833 payloads.  This would be a useful concept in bandwidth limited
networks.  What do you think?

Rex Coldren

>
>
> -Dan Wing

--------------4ED5415FF03FADE4790E482C
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Dan Wing wrote:
<blockquote TYPE=CITE>> When used with RFC 2198, the number of redundant
encodings also has an
<br>> impact on the total bandwidth used.
<p>I think the duplication has merit, but appropriate text is required
<br>explaining when such RFC2198 duplication of DTMF tones isn't appropriate.
<p>Perhaps a simple MAY is good enough, but only if we assume implementors
<br>will understand why it's a MAY instead of SHOULD or MUST.&nbsp; I haven't
read
<br>RFC2198 in awhile, but it may have text which explains some of the
<br>drawbacks of arbitrary duplication of packets in a bandwidth-constrained
<br>or policed network.&nbsp; My quick skim of RFC2198 didn't turn up such
text,
<br>however.</blockquote>
You're right.&nbsp; I don't think it's there.
<p>Note that the usual situation involving the need to send DTMF tones
outside of
<br>the normal RTP payload implies that the tones inside the normal RTP
payload
<br>are of no use, or at least should not be trusted.&nbsp; Indeed, in
many/all cases you
<br>would want to strip those tones out of the normal RTP payload when
sending
<br>via RFC 2833/2198 methods.&nbsp; Consequently, the normal RTP payload
has an
<br>element of mutual exclusivity with the RTP payload used to carry the
RFC
<br>2833/2198 encodings.&nbsp; Some benefit can be gained from this knowledge
when
<br>the access network is bandwidth limited, as in the cable and DSL cases.
<p>RFC 2833 does not address the possibility of <i>replacing</i> normal
RTP payloads
<br>with RFC 2833 payloads.&nbsp; This would be a useful concept in bandwidth
limited
<br>networks.&nbsp; What do you think?
<p>Rex Coldren
<blockquote TYPE=CITE>&nbsp;
<p>-Dan Wing</blockquote>
</html>

--------------4ED5415FF03FADE4790E482C--




From rem-conf Wed May 31 14:29:00 2000 
From rem-conf-request@es.net Wed May 31 14:28:58 2000
Received: from list by mail2.es.net with local (Exim 1.92 #1)
	for rem-conf-dist@es.net
	id 12xFwU-0007cz-00; Wed, 31 May 2000 14:22:22 -0700
Received: from igate.nuera.com ([204.216.240.98] helo=sd_exchange.nuera.com)
	by mail2.es.net with esmtp (Exim 1.92 #1)
	for rem-conf@es.net
	id 12xFwS-0007cm-00; Wed, 31 May 2000 14:22:20 -0700
Received: by sd_exchange.nuera.com with Internet Mail Service (5.5.2650.21)
	id <LQR7WZ7Q>; Wed, 31 May 2000 13:58:49 -0700
Message-ID: <613A6A6A3F09D3118F5C00508B2C24FE67A71F@sd_exchange.nuera.com>
From: "Bratakos, Maroula" <mbratakos@nuera.com>
To: "'coldrenr@agcs.com'" <coldrenr@agcs.com>, Dan Wing <dwing@cisco.com>
Cc: "Bratakos, Maroula" <mbratakos@nuera.com>, rem-conf@es.net
Subject: RE: RFC 2833 on Tones
Date: Wed, 31 May 2000 13:58:48 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFCB43.0451E300"
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFCB43.0451E300
Content-Type: text/plain;
	charset="iso-8859-1"


Dan Wing wrote: 

> When used with RFC 2198, the number of redundant encodings also has an 
> impact on the total bandwidth used. 

I think the duplication has merit, but appropriate text is required 
explaining when such RFC2198 duplication of DTMF tones isn't appropriate. 


Perhaps a simple MAY is good enough, but only if we assume implementors 
will understand why it's a MAY instead of SHOULD or MUST.  I haven't read 
RFC2198 in awhile, but it may have text which explains some of the 
drawbacks of arbitrary duplication of packets in a bandwidth-constrained 
or policed network.  My quick skim of RFC2198 didn't turn up such text, 
however.

You're right.  I don't think it's there. 

Note that the usual situation involving the need to send DTMF tones outside
of 
the normal RTP payload implies that the tones inside the normal RTP payload 
are of no use, or at least should not be trusted.  Indeed, in many/all cases
you 
would want to strip those tones out of the normal RTP payload when sending 
via RFC 2833/2198 methods.  Consequently, the normal RTP payload has an 
element of mutual exclusivity with the RTP payload used to carry the RFC 
2833/2198 encodings.  Some benefit can be gained from this knowledge when 
the access network is bandwidth limited, as in the cable and DSL cases. 


RFC 2833 does not address the possibility of replacing normal RTP payloads 
with RFC 2833 payloads.  This would be a useful concept in bandwidth limited

networks.  What do you think? 


Rex Coldren 


  
 -Dan Wing  

I think RFC 2833 already allows for replacing normal RTP payloads with RFC
2833 payloads because it says you MAY send both.  This implies to me you
don't have to send both and could just send RFC 2833 payloads.  The
advantage of RFC 2833 is that it provides a more reliable transport of tone
information (DTMF or otherwise) that can not be achieved via the audio media
stream due to degredation of the tones in the vocoding process (PCM and G726
excluded).  
 
I'm just trying to point out that people need to be careful how they send
DTMF/tone information.  If only audio is sent there should be no problem
(except that the tone information may be garbled for low bit-rate vocoders).
If only the RFC 2833 events are sent then there should be no problem.  But
if both payload types are sent it should be in a redundant format (2198) to
avoid the receiver from playing out both packets which could result in
double digits, tones out of phase, etc.
 
-Maroula Bratakos
 


------_=_NextPart_001_01BFCB43.0451E300
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.00.2722.2800" name=GENERATOR></HEAD>
<BODY>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2></DIV></FONT>Dan Wing wrote: 
  <BLOCKQUOTE TYPE="CITE">&gt; When used with RFC 2198, the number of 
    redundant encodings also has an <BR>&gt; impact on the total bandwidth used. 

    <P>I think the duplication has merit, but appropriate text is required 
    <BR>explaining when such RFC2198 duplication of DTMF tones isn't 
    appropriate. 
    <P>Perhaps a simple MAY is good enough, but only if we assume implementors 
    <BR>will understand why it's a MAY instead of SHOULD or MUST.&nbsp; I 
    haven't read <BR>RFC2198 in awhile, but it may have text which explains some 
    of the <BR>drawbacks of arbitrary duplication of packets in a 
    bandwidth-constrained <BR>or policed network.&nbsp; My quick skim of RFC2198 
    didn't turn up such text, <BR>however.</P></BLOCKQUOTE>You're right.&nbsp; I 
  don't think it's there. 
  <P>Note that the usual situation involving the need to send DTMF tones outside 
  of <BR>the normal RTP payload implies that the tones inside the normal RTP 
  payload <BR>are of no use, or at least should not be trusted.&nbsp; Indeed, in 
  many/all cases you <BR>would want to strip those tones out of the normal RTP 
  payload when sending <BR>via RFC 2833/2198 methods.&nbsp; Consequently, the 
  normal RTP payload has an <BR>element of mutual exclusivity with the RTP 
  payload used to carry the RFC <BR>2833/2198 encodings.&nbsp; Some benefit can 
  be gained from this knowledge when <BR>the access network is bandwidth 
  limited, as in the cable and DSL cases. 
  <P>RFC 2833 does not address the possibility of <I>replacing</I> normal RTP 
  payloads <BR>with RFC 2833 payloads.&nbsp; This would be a useful concept in 
  bandwidth limited <BR>networks.&nbsp; What do you think? 
  <P>Rex Coldren 
  <BLOCKQUOTE TYPE="CITE">
    <DIV>&nbsp;<SPAN class=930184120-31052000><FONT color=#0000ff face=Arial 
    size=2>&nbsp;</FONT></SPAN></DIV>
    <DIV><SPAN class=930184120-31052000>&nbsp;</SPAN>-Dan Wing<FONT 
    color=#0000ff face=Arial size=2><SPAN 
    class=930184120-31052000>&nbsp;</SPAN></FONT><FONT color=#0000ff face=Arial 
    size=2><SPAN class=930184120-31052000>&nbsp;</SPAN></FONT></DIV></BLOCKQUOTE>
  <DIV><FONT face=Arial size=2><SPAN class=930184120-31052000>I think RFC 2833 
  already allows for replacing normal RTP payloads with RFC 2833 payloads 
  because it says you MAY send both.&nbsp; This implies to me you don't have to 
  send both and could just send RFC 2833 payloads.&nbsp; The advantage of RFC 
  2833 is that it provides a more reliable transport of tone information (DTMF 
  or otherwise) that can not be achieved&nbsp;via the&nbsp;audio media stream 
  due to degredation of the tones in the vocoding process (PCM and G726 
  excluded).&nbsp; </SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=930184120-31052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2><SPAN class=930184120-31052000>I'm just trying to 
  point out that people need to be careful how they send DTMF/tone 
  information.&nbsp; If only audio is sent there should be no problem (except 
  that the tone information may be garbled for low bit-rate vocoders).&nbsp; If 
  only the RFC 2833 events are sent then there should be no problem.&nbsp; But 
  if both payload types are sent it should be in a redundant format (2198) to 
  avoid the receiver from playing out both packets which could result in double 
  digits, tones out of phase, etc.</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=930184120-31052000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2><SPAN class=930184120-31052000>-Maroula 
  Bratakos</SPAN></FONT></DIV>
  <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
  class=930184120-31052000></SPAN></FONT>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BFCB43.0451E300--



From rem-conf Wed May 31 17:09:48 2000 
From rem-conf-request@es.net Wed May 31 17:09:46 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xIQj-0005IK-00; Wed, 31 May 2000 17:01:45 -0700
Received: from lint.cisco.com [171.68.224.209] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xIQi-0005FY-00; Wed, 31 May 2000 17:01:44 -0700
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id RAA21345; Wed, 31 May 2000 17:00:12 -0700 (PDT)
Date: Wed, 31 May 2000 17:00:12 -0700 (PDT)
From: Dan Wing <dwing@cisco.com>
To: "Bratakos, Maroula" <mbratakos@nuera.com>
cc: "'coldrenr@agcs.com'" <coldrenr@agcs.com>, rem-conf@es.net
Subject: RE: RFC 2833 on Tones
In-Reply-To: <613A6A6A3F09D3118F5C00508B2C24FE67A71F@sd_exchange.nuera.com>
Message-ID: <0005311655060.21927-100000@omega.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

On Wed, 31 May 2000 13:58 -0700, Bratakos, Maroula wrote:

> 
> Dan Wing wrote: 
> 
> > When used with RFC 2198, the number of redundant encodings also has an 
> > impact on the total bandwidth used. 
> 
> I think the duplication has merit, but appropriate text is required 
> explaining when such RFC2198 duplication of DTMF tones isn't appropriate. 
> 
> 
> Perhaps a simple MAY is good enough, but only if we assume implementors 
> will understand why it's a MAY instead of SHOULD or MUST.  I haven't read 
> RFC2198 in awhile, but it may have text which explains some of the 
> drawbacks of arbitrary duplication of packets in a bandwidth-constrained 
> or policed network.  My quick skim of RFC2198 didn't turn up such text, 
> however.
> 
> You're right.  I don't think it's there. 
> 
> Note that the usual situation involving the need to send DTMF tones outside
> of 
> the normal RTP payload implies that the tones inside the normal RTP payload 
> are of no use, or at least should not be trusted.  Indeed, in many/all cases
> you 
> would want to strip those tones out of the normal RTP payload when sending 
> via RFC 2833/2198 methods.  Consequently, the normal RTP payload has an 
> element of mutual exclusivity with the RTP payload used to carry the RFC 
> 2833/2198 encodings.  Some benefit can be gained from this knowledge when 
> the access network is bandwidth limited, as in the cable and DSL cases. 
> 
> 
> RFC 2833 does not address the possibility of replacing normal RTP payloads 
> with RFC 2833 payloads.  This would be a useful concept in bandwidth limited
> 
> networks.  What do you think? 
> 
> 
> Rex Coldren 
> 
> 
>   
>  -Dan Wing  
> 
> I think RFC 2833 already allows for replacing normal RTP payloads with RFC
> 2833 payloads because it says you MAY send both.  This implies to me you
> don't have to send both and could just send RFC 2833 payloads.  The
> advantage of RFC 2833 is that it provides a more reliable transport of tone
> information (DTMF or otherwise) that can not be achieved via the audio media
> stream due to degredation of the tones in the vocoding process (PCM and G726
> excluded).  
>  
> I'm just trying to point out that people need to be careful how they send
> DTMF/tone information.  If only audio is sent there should be no problem
> (except that the tone information may be garbled for low bit-rate vocoders).
> If only the RFC 2833 events are sent then there should be no problem.  But
> if both payload types are sent it should be in a redundant format (2198) to
> avoid the receiver from playing out both packets which could result in
> double digits, tones out of phase, etc.

OH!  I had completely misunderstood.  Sorry.  I understand now.

-Dan Wing






From rem-conf Wed May 31 17:37:05 2000 
From rem-conf-request@es.net Wed May 31 17:37:04 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xImj-0006Aw-00; Wed, 31 May 2000 17:24:29 -0700
Received: from tnt.isi.edu [128.9.128.128] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xImi-0006Ab-00; Wed, 31 May 2000 17:24:28 -0700
Received: from rum.isi.edu (rum.isi.edu [128.9.160.237])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id RAA08003
	for <rem-conf@es.net>; Wed, 31 May 2000 17:24:28 -0700 (PDT)
From: Joe Touch <touch@ISI.EDU>
Received: (from touch@localhost)
	by rum.isi.edu (8.9.3/8.8.6) id RAA22782
	for rem-conf@es.net; Wed, 31 May 2000 17:24:27 -0700 (PDT)
Date: Wed, 31 May 2000 17:24:27 -0700 (PDT)
Message-Id: <200006010024.RAA22782@rum.isi.edu>
To: rem-conf@es.net
Subject: SIGCOMM 2000 Call for Participation
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list


			Call for Participation
		     ACM SIGCOMM 2000 Conference

		    August 28 - September 1, 2000
		    Grand Hotel, Stockholm, Sweden
		http://www.acm.org/sigcomm/sigcomm2000
		       sigcomm2000-info@acm.org

Deadlines:

Proposals for student travel grant:	June 22, 2000
Proposals for poster session:		July 12, 2000
Advance registration ends:		July 28, 2000
Outrageous opinions desired:		starting August 25, 2000

SIGCOMM 2000 is the annual conference of the Special Interest Group on
Data Communication (SIGCOMM), a single-track, highly selective
conference with a technical program of 26 papers, tutorials by noted
instructors on the two days prior, and sessions on speculative results.

Early registration for Sigcomm 2000 is now open. Registration details,
as well as information on student travel grants and requests for
proposals for a work-in-progress poster session are available at the
Sigcomm website above.

Registration

Conference and hotel registration is handled by the Stockholm Convention
Bureau (see address below, or website above). Note that the number of
delegates is limited to 500 and that registration requests will be
handled on a "first-come-first-served" basis. Please refer to the web
form or paper form for various rates and options. ACM has selected Delta
Air Lines as the Official airline for its conferences in Europe for
2000. Delta has special fares in place for ACM and your traveling
companions. See the website for further details.

Sigcomm registration is by secure web form, or fax or ordinary mail.
On-line registration is available at the Sigcomm website; fax and
ordinary mail registrations must be completed well in advance of the
deadlines, using this PDF form sent or faxed to the address below:
	   https://www.it.uu.se/conf/sigcomm2000/register.pdf 
	   http://www.acm.org/sigcomm/sigcomm2000/register.pdf

           Stockholm Convention Bureau 
	   ACM SIGCOMM 2000
           P O Box 6911
           SE-102 39 Stockholm, SWEDEN
           Phone: +46 8 546 515 00 / Fax: +46 8 546 515 99

Opening Reception and Dinner events

The reception is generously hosted by Stockholm City, and includes a
sightseeing cruise on the water ways of Stockholm, through the Old Town
to the City Hall, site of the famous for the Nobel Prize festivities.
The banquet dinner is hosted at the Vasa Museum, site of the Sweden's
largest and most prestigious warship; dinner is included in the cost of
registration, and guest tickets are available. Advance reservations
necessary for all events.

Stockholm - the Royal capital of Sweden - is one of the most beautiful
cities in the world. It is built on fourteen islands and surrounded by
waters so clean that you can fish and swim right in the middle of the
city. Stockholm became the capital of Sweden 750 years ago. In the
winding alleyways of the city's medieval Old Town, the air is redolent
with history.  And yet, only a few minutes walking distance away lies
the throbbing pulse of a modern city.

SIGCOMM Award

The SIGCOMM Award is given annually to a person whose career and
technical achievements demonstrate a long-term commitment to the field
of data communications. ACM SIGCOMM is pleased to announce that the 2000
SIGCOMM Award is being given to Prof. André Danthine, University of
Liege, Belgium, who will also provide the keynote address.

Tutorials

SIGCOMM 2000 begins with two days of full-day tutorials covering single
topics in detail at both the introductory and advanced level.  Tutorials
offered this year are:
 - Voice over IP	
	   Prof. Henning Schulzrinne, Columbia Univ.
 - Analysis of Network and Protocol Behavior with Common Tools
	   Prof. Shawn Ostermann, Ohio Univ.
 - Network Security Protocols
	   Dr. Radia Perlman, Sun Microsystems
 - Distributed control and resource pricing
	   Dr. Richard Gibbens, Univ. of Cambridge
	   Dr. Peter Key, Microsoft Research

Outrageous Opinions Session

The Outrageous Opinions Session provides an opportunity for sharing
entertaining, provocative, and otherwise enriching ideas and suggestions
in their early stages. Submissions are actively solicited by the OO
Chair Gary Delp (gdelp@acm.org) beginning August 25, 2000.

Poster Session - Work in Progress

The Poster Session is an opportunity for students (as primary poster
authors) to present work in progress.  Poster proposals should be sent
to the PC chairs by July 12.  Posters will be reviewed by the TPC, and
decisions made by early August; see the website for further details.

Student Travel Awards

The student travel program provides support for SIGCOMM conference
participation to students, primarily not paper authors, who would
otherwise find it difficult to attend. Students at degree granting
institutions throughout the world are eligible.  See the website for
further criteria and application procedures.

General Co-Chairs
	Per Gunningberg, Uppsala U., Sweden (perg@docs.uu.se)
	Steve Pink, Lulea U. Tech., Sweden (steve@cdt.luth.se)
Program Co-Chairs
	Christophe Diot, Sprint ATL, USA (cdiot@sprintlabs.com)
	Jim Kurose, U. Massachusetts, USA (kurose@cs.umass.edu)
Publicity Chair
	Joe Touch, USC/ISI, USA (touch@isi.edu)
Tutorials Chair
	Steve Pink, Lulea U Tech., Sweden (steve@cdt.luth.se)
Local Arrangements Co-Chairs
	Bengt Ahlgren, SICS, Sweden (bengta@sics.se)
	Christian Tschudin, Uppsala U., Sweden (tschudin@docs.uu.se)

Support from Ericsson, Telia, and Sprint is gratefully acknowledged.
The student travel grant program is supported by Nokia and the US
National Science Foundation.



From rem-conf Wed May 31 18:54:43 2000 
From rem-conf-request@es.net Wed May 31 18:54:42 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xK6p-0000Ne-00; Wed, 31 May 2000 18:49:19 -0700
Received: from avocet.prod.itd.earthlink.net [207.217.121.50] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xK6o-0000NU-00; Wed, 31 May 2000 18:49:18 -0700
Received: from mail.earthlink.net (ip240.birmingham5.al.pub-ip.psi.net [38.37.100.240])
	by avocet.prod.itd.earthlink.net (8.9.3/8.9.3) with SMTP id SAA26610
	for <rem-conf@es.net>; Wed, 31 May 2000 18:49:09 -0700 (PDT)
From: aeh123@beer.com
Received: from netbiz12@beer.com by netbiz12@beer.com (8.8.5/8.6.5) with SMTP id GAA05567 for <rem-conf@es.net>; Wed, 31 May 2000 21:42:41 -0600 (EST)
Date: Wed, 31 May 00 21:42:41 EST
To: rem-conf@es.net
Subject: FREE 32 Page Booklet exposes Insider's Web Marketing Secrets!
Message-ID: <>
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list

<HTML><PRE><BODY BGCOLOR="#000000"><FONT COLOR="#00FFFF" SIZE=3>
Dear rem-conf@es.net,

Hello,

I noticed that you have been advertising your business on some of the  free
online advertising sites. If your results have been excellent then read no further. But
if this activity has produced the same poor results for you, that it did for me, then I
think you might be interested in reading a Free publication called "Inside Secrets to
Wealth on the Web".

And don't think you'll have to pay anything for the information. You don't! If
you act today .....it's absolutely FREE!

It normally would cost as much as $99.95, but for now I am just giving it away
to introduce our new Infoshare Web Marketing concept!

Just click the link below and I'll send you all the details on how to download
the FREE 32 page booklet "Inside Secrets to Wealth on the Web" There is nothing
to buy... nothing to do (except learn how to be truly successful in your Web
Business)!

 Mailto:aeh123@beer.com?subject=SendFreeBooklet

After stumbling around for three months and getting absolutely nowhere with my
web business, I have been truly amazed at my success the last 30 days since reading
this remarkable booklet. You will too!

Best of luck in your internet ventures,
John 
Internet Marketing Consultant

PS: Thousands of new entrepreneurs will become wealthy doing business on the
Internet over the next few years. If you apply the techniques you will learn in our FREE
booklet now, you will be one of them this year!


</FONT><FONT  COLOR="#000000" SIZE=3>




From rem-conf Wed May 31 22:57:54 2000 
From rem-conf-request@es.net Wed May 31 22:57:51 2000
Received: from list by mail1.es.net with local (Exim 1.81 #2)
	id 12xNtH-00043G-00; Wed, 31 May 2000 22:51:35 -0700
Received: from (redball.dynamicsoft.com) [216.173.40.51] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12xNtG-000436-00; Wed, 31 May 2000 22:51:34 -0700
Received: from dynamicsoft.com (1Cust28.tnt2.freehold.nj.da.uu.net [63.17.114.28])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id BAA08295;
	Thu, 1 Jun 2000 01:52:42 -0400 (EDT)
Message-ID: <3935F9DB.85DE1FEF@dynamicsoft.com>
Date: Thu, 01 Jun 2000 01:51:23 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephan Wenger <stewe@cs.tu-berlin.de>
CC: rem-conf@es.net
Subject: Re: Question on RFC2733, packet-based FEC
References: <4.3.2.20000531092714.00dc2210@mail.cs.tu-berlin.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailing-List: <rem-conf@es.net> 
X-Loop: rem-conf@es.net
Precedence: list



Stephan Wenger wrote:
> 
> Hi all,
> 
> I don't understand the reason for an (artificial?) limitation of
> RFC2733.  RFC2733 says that, when calculating FEC over
> several packets of different sizes, the FEC packet has to
> protect all bytes of the biggest packet (and padding is to be
> used for the other packets to bring them up to the size of
> the biggest packet).  Is there some hidden secret about this
> requirement?


The aim is to provide complete recovery of a missing packet, which
results in this requirement.

> 
> The rest of the EMail describes scenarios where this limitation
> is counter-productive.
> 
> In a recent ITU meeting, Adam Li of UCLA brought to our
> attention an idea to implement unequal error protection using
> packet based FEC.  What they want to do is to use data
> partitioning to put important video data (such as headers and
> motion vectors) to the front of a packet, and put the less
> important coefficients to the end.  Then apply packet based
> FEC only on the first (more important) part of the packets.
> Resulting FEC packets are smaller -- lower bandwidth requirements.

This has actually been discussed within IETF. In fact, I think one of
the MPEG-4 over RTP drafts may actually be doing this. We rejected this
>from the rfc2733 mechanism, as I recall, because you needed a whole
bunch of additional stuff to indicate what is covered by the FEC, if its
not the whole packet. In the worst case, you'd actually need a bitmap
which is the size of the largest packet, where the bitmap indicates
which bits are protected by FEC. As a result, any general purpose
mechanism for unequal protection would likely require as many bits to
signal as the savings obtained from the unequal protection. Note that
the advantages of this unequal proection is solely reducing packet
sizes.

-Jonathan R.
-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (732) 741-4778
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com



