From owner-rmt@listserv.lbl.gov Mon Jan 3 11:29:25 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03734 for ; Mon, 3 Jan 2000 11:29:22 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id HAA11398; Mon, 3 Jan 2000 07:30:44 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id HAA11394 for ; Mon, 3 Jan 2000 07:30:42 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id HAA20534 for ; Mon, 3 Jan 2000 07:30:42 -0800 (PST) Received: from smtp2.cluster.oleane.net (smtp2.cluster.oleane.net [195.25.12.17]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id HAA20523 for ; Mon, 3 Jan 2000 07:30:36 -0800 (PST) Received: from oleane (dyn-1-1-234.Vin.dialup.oleane.fr [195.25.4.234]) by smtp2.cluster.oleane.net with SMTP id QAA75711; Mon, 3 Jan 2000 16:29:34 +0100 (CET) Message-ID: <005601bf55ff$04f74a80$0401a8c0@oleane.com> From: "Peter Lewis" To: Subject: VoDSL 2000 Conference Date: Mon, 3 Jan 2000 16:27:10 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0053_01BF5607.6292A240" 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 Sender: owner-rmt@lbl.gov Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0053_01BF5607.6292A240 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 Hello, =20 The VoDSL 2000 Conference will stand in Paris next 28-31 March. Key = speakers, case studies: take a look at: = http://www.upperside.fr/bavodsl.htm =20 Regards ------=_NextPart_000_0053_01BF5607.6292A240 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 =20
Hello,
 
The VoDSL 2000 Conference will stand = in Paris=20 next 28-31 March. Key speakers, case studies: take a look at:  http://www.upperside.fr/bavo= dsl.htm
 
Regards
 
------=_NextPart_000_0053_01BF5607.6292A240-- From owner-rmt@listserv.lbl.gov Tue Jan 11 06:35:04 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03545 for ; Tue, 11 Jan 2000 06:35:03 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id CAA03600; Tue, 11 Jan 2000 02:46:28 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id CAA03596 for ; Tue, 11 Jan 2000 02:46:26 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id CAA03060 for ; Tue, 11 Jan 2000 02:46:25 -0800 (PST) Received: from smtp1.cluster.oleane.net (smtp1.cluster.oleane.net [195.25.12.16]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id CAA03028 for ; Tue, 11 Jan 2000 02:45:51 -0800 (PST) Received: from oleane (dyn-1-1-186.Vin.dialup.oleane.fr [195.25.4.186]) by smtp1.cluster.oleane.net with SMTP id LAA20336; Tue, 11 Jan 2000 11:43:57 +0100 (CET) Message-ID: <008501bf5c20$6b51e020$0401a8c0@oleane.com> From: "Peter Lewis" To: Subject: SIP 2000 Call for Paper Date: Tue, 11 Jan 2000 11:41:20 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0082_01BF5C28.C79F0D00" 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 Sender: owner-rmt@lbl.gov Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0082_01BF5C28.C79F0D00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SIP 2000: beyond H.323?=20 Discussing and debating in Paris May 10-12. A CFP is online at: http://www.upperside.fr/basip.htm =20 ------=_NextPart_000_0082_01BF5C28.C79F0D00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
SIP 2000: beyond H.323? =
Discussing and debating in Paris May = 10-12.
A CFP is online at:
http://www.upperside.fr/basip.= htm
 
 
------=_NextPart_000_0082_01BF5C28.C79F0D00-- From owner-rmt@listserv.lbl.gov Wed Jan 12 13:38:35 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21536 for ; Wed, 12 Jan 2000 13:38:28 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id JAA10716; Wed, 12 Jan 2000 09:32:10 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA10712 for ; Wed, 12 Jan 2000 09:32:07 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA00494 for ; Wed, 12 Jan 2000 09:32:05 -0800 (PST) Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA00485 for ; Wed, 12 Jan 2000 09:32:04 -0800 (PST) Received: from sbult1e.Cadence.COM (sbult1e.Cadence.COM [139.99.82.8]) by mailgate.Cadence.COM (8.9.3/8.9.3) with ESMTP id JAA26641; Wed, 12 Jan 2000 09:30:49 -0800 (PST) Received: (from brucelu@localhost) by sbult1e.Cadence.COM (8.8.5/8.8.5) id JAA21661; Wed, 12 Jan 2000 09:30:43 -0800 (PST) From: Bruce Lueckenhoff Message-Id: <200001121730.JAA21661@sbult1e.Cadence.COM> Subject: Re: RMT Team Formation To: rmt@lbl.gov Date: Wed, 12 Jan 100 09:30:43 -0800 (PST) Cc: J.Crowcroft@cs.ucl.ac.uk, jgemmel@microsoft.com, luby@dfountain.com, luigi@info.iet.unipi.it, lorenzo@cisco.com, vincent.roca@lip6.fr In-Reply-To: from "Vincent Roca" at Dec 23, 99 04:19:49 pm Organization: Cadence Design Systems, Inc. X-Mailer: ELM [version 2.4 PL25] Content-Type: text X-Received: By mailgate.Cadence.COM as JAA26641 at Wed Jan 12 09:30:49 2000 Sender: owner-rmt@lbl.gov Precedence: bulk Greetings, Mr. Roca raises a valid point. Layering should be considered separately, at least from the building block point of view. Certainly layering could be part of an ALC protocol instantiation, though. Am I missing any compelling reasons why layering ought to be bundled into the ALC building block? on December 23, 1999, Vincent Roca wrote: > ... > I see that he inserted me in the ALC list... I read the meeting > minutes and saw that it is more dedicated to FEC/CC than on > layered packet organization schemes > ... Bruce -- Bruce Lueckenhoff mailto:brucelu@cadence.com Cadence Design Systems 805-571-1246 FAX:805-571-1300 From owner-rmt@listserv.lbl.gov Wed Jan 12 17:13:39 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25740 for ; Wed, 12 Jan 2000 17:13:38 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id MAA11329; Wed, 12 Jan 2000 12:51:09 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id MAA11325 for ; Wed, 12 Jan 2000 12:51:02 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id MAA07058 for ; Wed, 12 Jan 2000 12:51:02 -0800 (PST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id MAA06846 for ; Wed, 12 Jan 2000 12:50:11 -0800 (PST) Received: from eastmail2.East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA17523 for ; Wed, 12 Jan 2000 12:50:00 -0800 (PST) Received: from bcn.East.Sun.COM (bcn.East.Sun.COM [129.148.75.4]) by eastmail2.East.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id PAA22102 for ; Wed, 12 Jan 2000 15:49:58 -0500 (EST) Received: from bridge (bridge [129.148.75.125]) by bcn.East.Sun.COM (8.9.1b+Sun/8.9.1) with SMTP id PAA25668 for ; Wed, 12 Jan 2000 15:49:58 -0500 (EST) Message-Id: <200001122049.PAA25668@bcn.East.Sun.COM> Date: Wed, 12 Jan 2000 15:49:57 -0500 (EST) From: Dah Ming Chiu - Sun Microsystems Reply-To: Dah Ming Chiu - Sun Microsystems Subject: ACK Building Block To: rmt@lbl.gov MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY=Ambush_of_Tigers_512_000 X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc Sender: owner-rmt@lbl.gov Precedence: bulk --Ambush_of_Tigers_512_000 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: YoliUetor4PDRyrANjucVA== Over a month ago, I wrote a short proposal to develop an ACK building block, and circulated it to a small set of people in RMT for comment. So far, only Brian Whetten and I have been discussing it; and we have some different opinions. Since there may be others on the RMT list who are interested in the (Tree-based) ACK approach, I would like to move the discussion here. Attached is a sketch of an ACK BB (Building Block). I have not updated it since I wrote it a month ago. It describes the relationship between a receiver and its repair head (repair node), and some basic session management functions of the sender, all in terms of an abstract API. I have also sketched out some algorithms that need to be specified (such as deciding when to ack and request ack), and some hooks to other BB's (e.g. congestion control, tree-building). Most importantly, this is all quite simple. I hope this is useful for helping us build the TRACK protocol standards as we move ahead. Comments are welcome. Dah Ming Chiu --Ambush_of_Tigers_512_000 Content-Type: TEXT/plain; name="ACKBB.txt"; charset=us-ascii; x-unix-mode=0600 Content-Description: ACKBB.txt Content-MD5: hZzSk05DmgQ2NOxJNZXvPA== ACK-based reliable multicast service building block (ACK BB) ------------------------------------------------------------ The ACK-based reliable multicast building block abstracts out the basic interface and algorithms used by an ACK-based reliable multicast transport, and described how it interacts with other building blocks such as the use (and building) of a repair tree, congestion/flow control, security and group management. The following is a rough sketch of the ACK BB, including definitions of an abstract API, a number of algorithms, and descriptions of "hooks" used for integrating with other building blocks. 1) Abstract API 1.1) Definition of some primitive datatypes used to describe the abstract API. session: This is possibly identified by the following - session id multicast address [sender address] member: This identifies a receiver using its address and port head: This identifies a repair head using its address and port 1.2) APIs for member to repair head interaction: BindToRepairHead(session, head, scope, [role], [subtree]) This function is used by a member to request repair service from a repair head. The parameter scope includes ttl and/or administrative scoping information, used by a repair head to perform localized repair. The optional parameters [role] and [subtree] provide other information about the receiver. Role says if the receiver can or cannot become head; subtree indicates if the receiver is itself a repair head, and information about its dependents. Ack(session, head, ack_info) This function is used to send an acknowledgement to a repair head. The parameter ack_info is a suitable data structure - for example can contain an ascending list of sequence numbers; the first element of the list signifying the highest sequence number of consecutively received packets, etc. Unbind(session, head, reason) This function is used to tell the current repair head that its services are no longer needed. 1.3) APIs for repair head to member interaction: AcceptMember(session, member, available_packets, [repair_addr], [level]) This function is used to respond to a BindToRepairHead request. The parameter available_packets a suitable data structure for example containing a descending list of sequence numbers; the first element of the list signifying the beginning of a consecutive packet stream this repair head is prepared to repair. Optionally, a separate multicast address can be suggested for members to listen for (multicast) repairs. The optional parameter [level] is used (when there is a repair tree) to indicate the number of other repair heads this repair head depends on. RejectMember(session, member, reason) This function is used to reject a membership request via BindToRepairHead. RequestAck(session, memberlist, seqno) This function is used to request the members in memberlist to ack. The parameter seqno contains the newest sequence number the repair head has seen. RequestFinalAck(session, memberlist, seqno) This function is used to request the members in memberlist to ack the receipt of all packets up to seqno (inclusive), which is the last packet of the session. The repair head cannot exit until it has fulfilled it obligation to see all members have received the last packet of the session. SendRepair(session, [member], seqno) This function is used to send a repair message. If a member parameter is included, then the repair head sends a unicast repair message (seqno) to this member; else the repair message (seqno) is sent to all members served by this repair head. Terminate(session, member, reason) This function is used by the head to terminate a member. Reasons for termination could be the member is not able to following the minimum data rate configured for the session, and/or causing the repair head to fill up its cache. Resign(session, reason) This function is used by the head to resign. It provides a way for its members to gracefully find other repair heads more quickly (than if the repair head crashed). 1.4) APIs for sender to group interaction: SessionStart(session) This function is used by the sender to send a multicast message to the whole group to indicate a multicast session is about to begin. SenderStatus(session, status) This function is used by the sender to tell the whole multicast group that it is still alive and optionally the sequence number of messages it has sent thus far. This is typically done when there is a (time) gap in the data packet stream. SessionEnd(session, seqno) This function is used by the sender to tell the whole multicast group that it has sent out the last packet (seqno). This is an optimization to help the whole group to recognize the end of the session. 2) Algorithms The following algorithms describe when the above functions are used (only the cases where it is s not obvious). In the process, we discuss a number of (configurable) parameters and some internal states of the receiver and repair heads. 2.1) When to ack Three events may trigger a receiver to send an ack: ack window ack timer probe The normal event is the ack window. Ack window is a configured parameter. (Note, in some implementations, this may be a dynamic parameter tied to the congestion window). For example, a receiver may be configured to send an ack once every 32 packets. If the packet stream is continuous and under normal operation conditions, this may be the only mechanism used to schedule sending of acks. The ack timer is also a configured parameter. (Note again, in some implementations this may be a dynamically adjusted parameter based on prediction of expected inter-packet arrival times). This mechanism is typically triggered when losses occur, or when application data has a (time) gap in it. The receiver also sends an ack in response to various probes from the repair head or the sender. For example, the RequestAck, RequestFinalAck, SessionEnd and RTT computation functions may all trigger a receiver to send an ack. 2.2) When to request ack When a repair head detects that a member has not sent an ack for some interval of time, it requests those members to respond with an ack. This time is similar to the ack timer discussed above. Request for ack can be a unicast message (when only one member is being polled) or a multicast message when multiple members are being polled. The addresses of the multiple members can be listed in the request message. This enables the repair heads to disown unresponsive members and reclaim buffers. Request for ack can also be used to compute RTT between a repair head and its member. 2.3) Cache management Depends on the type of late join support and the type of reliability being supported. 2.4) Repair algorithm When some member indicates missing packets, the repair head calls the SendRepair function to queue repairs to the retransmission queue. It is often the case that multiple members request the same repair. The implementation of SendRepair must carefully avoid queueing a repair packet that is already in the queue, or sending a repair that has very recently been sent. The repair head also decides when to send an ack via unicast and when to use multicast to minimize bandwidth usage. 2.5) Session close The algorithm to close the session is for the sender to call sessionEnd(). This results in a multicast message being transmitted to the whole group indicating end of session. Each repair head, separately requests all members in its repair group to send an ack of the final packet. In case the session end message from the sender is not received by a repair head, it may be sent multiple times. Failing that, the session end signal still would propagate down the tree via each repair head requesting the final ack. 3) Other Hooks The hooks describe additional ways (other than the abstract API) this building block interacts with other building blocks and a protocol instantiation. 3.1) Hooks exported 3.1.1) Missing packet info Other BB's may need to query this BB for the total number of lost packet seen and repaired up to now. This information may prove useful for congestion control, for example in calculating the suitable rate for transmission; or in determining which member is keeping the group transmission rate below the minimum data rate. Similarly, there should be a hook for zeroing the above states to accommodate the need to restart certain calculations (for example - when the sender resumes data transmission after a pause). 3.1.2) Cache info Other BB may be interested in the cache occupancy, or available packets in the cache. 3.1.3) ackWindow 3.2) Hooks expected from other BB's 3.2.1) Current Data rate This information probably comes from the congestion control BB. It may be useful for dynamically setting some timers used to send (or request) acks. 3.2.2) Keep alive function The repair head and its member need a keep-alive function which runs in the absence of repairs. If this is covered in the tree-building BB, then the hooks are needed by this BB to access it. 3.2.3) Repair scope The TREE BB may provide a repair scope for controlling the locality of repairs. The repair scope infomation is needed by this BB too. 3.2.4) Security hook Security hooks are needed to perform signature/authentication operations on all BB(protocol) control messages. 4) Issues Some functions in this BB overlap with functions in the tree configuration BB. For example, the Bind/Unbind, Accept/Reject would be used during tree building as well. On the other hand, a receiver and head need some keep-alive function that we did not specify here now (perhaps we should have), and expected it be part of the tree maintenance function in the tree BB. --Ambush_of_Tigers_512_000-- From owner-rmt@listserv.lbl.gov Mon Jan 17 16:42:29 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09333 for ; Mon, 17 Jan 2000 16:42:27 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id MAA28297; Mon, 17 Jan 2000 12:36:17 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id MAA28293 for ; Mon, 17 Jan 2000 12:36:15 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id MAA16294 for ; Mon, 17 Jan 2000 12:36:14 -0800 (PST) Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id MAA16291 for ; Mon, 17 Jan 2000 12:36:13 -0800 (PST) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (VWALL-IN-motgate2 2.0) with ESMTP id NAA12832 for ; Mon, 17 Jan 2000 13:36:12 -0700 (MST)] Received: [from homer.arc.corp.mot.com ([217.1.10.38]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id NAA07552 for ; Mon, 17 Jan 2000 13:36:11 -0700 (MST)] Received: from arc.corp.mot.com ([144.187.5.100]) by homer.arc.corp.mot.com (8.9.3/8.9.3) with ESMTP id HAA03586 for ; Tue, 18 Jan 2000 07:31:43 +1100 (EST) Message-ID: <38837C33.D4D0D71D@arc.corp.mot.com> Date: Tue, 18 Jan 2000 07:31:47 +1100 From: Roger Kermode Reply-To: Roger.Kermode@motorola.com Organization: Motorola X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: rmt-list Subject: RMT: Call For Feb 10 Agenda Items Content-Type: multipart/mixed; boundary="------------CA450681D05075CD7872F10A" Sender: owner-rmt@lbl.gov Precedence: bulk This is a multi-part message in MIME format. --------------CA450681D05075CD7872F10A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Februrary 10th is rapidly approaching and the next meeting is looming up quickly. If everyone could please coordinate with the other people working on your respecitve building block drafts, and send potential agenda items to me as you can I would be most grateful. Thanks! Roger --------------CA450681D05075CD7872F10A Content-Type: text/x-vcard; charset=us-ascii; name="rkermode.vcf" Content-Description: Card for Roger Kermode Content-Disposition: attachment; filename="rkermode.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Kermode;Roger tel;fax:+61-2-9666-0501 tel;home:+61-2-9664-8335 tel;work:+61-2-9666-0558 x-mozilla-html:FALSE url:www.mot.com.au org:Motorola Australian Research Centre;Scalable Commodity Internet Lab version:2.1 email;internet:Roger.Kermode@motorola.com title:Principal Research Engineer SNAIL MAIL: Locked Bag 5028, Botany NSW, 1455=0D=0A;Botany;NSW;2019;Australia adr;quoted-printable:;;PHYSICAL: Level 3, 12 Lord St., Botany, NSW=0D=0A= x-mozilla-cpt:;-1 fn:Roger Kermode end:vcard --------------CA450681D05075CD7872F10A-- From owner-rmt@listserv.lbl.gov Tue Jan 18 08:03:57 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28778 for ; Tue, 18 Jan 2000 08:03:56 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id EAA29267; Tue, 18 Jan 2000 04:22:47 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id EAA29263 for ; Tue, 18 Jan 2000 04:22:45 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id EAA28101 for ; Tue, 18 Jan 2000 04:22:44 -0800 (PST) Received: from bettina.informatik.uni-bremen.de (root@bettina.informatik.uni-bremen.de [134.102.224.3]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id EAA28097 for ; Tue, 18 Jan 2000 04:22:43 -0800 (PST) Received: from cabo2 (dienstmann.informatik.uni-bremen.de [134.102.224.51]) by bettina.informatik.uni-bremen.de (8.8.7/8.8.7) with SMTP id NAA04911; Tue, 18 Jan 2000 13:22:15 +0100 (MET) From: "Dr. Carsten Bormann" To: , "rmt-list" Subject: RE: Call For Feb 10 Agenda Items Date: Tue, 18 Jan 2000 13:22:12 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: <38837C33.D4D0D71D@arc.corp.mot.com> Sender: owner-rmt@lbl.gov Precedence: bulk Content-Transfer-Encoding: 7bit Are we going to run the meeting as an RMT "plenary" or are we going to split up into BB/PI subgroups? I sure have ideas for agenda items for the latter case (which should spawn some plenary items, too). Gruesse, Carsten From owner-rmt@listserv.lbl.gov Thu Jan 20 19:54:38 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17587 for ; Thu, 20 Jan 2000 19:54:37 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id PAA16362; Thu, 20 Jan 2000 15:54:25 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA16358 for ; Thu, 20 Jan 2000 15:54:23 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA14005 for ; Thu, 20 Jan 2000 15:54:22 -0800 (PST) Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA13994 for ; Thu, 20 Jan 2000 15:54:21 -0800 (PST) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (VWALL-IN-ftpbox 2.0) with ESMTP id QAA06504 for ; Thu, 20 Jan 2000 16:54:20 -0700 (MST)] Received: [from homer.arc.corp.mot.com ([217.1.10.38]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id QAA24652 for ; Thu, 20 Jan 2000 16:54:17 -0700 (MST)] Received: from arc.corp.mot.com (everest.arc.corp.mot.com [217.1.10.204]) by homer.arc.corp.mot.com (8.9.3/8.9.3) with ESMTP id KAA08206 for ; Fri, 21 Jan 2000 10:49:34 +1100 (EST) Message-ID: <38879F10.81A21BA3@arc.corp.mot.com> Date: Fri, 21 Jan 2000 10:49:36 +1100 From: Roger Kermode Reply-To: Roger.Kermode@motorola.com Organization: Motorola X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: rmt-list Subject: RMT meeting Feb 10 at Aciri Content-Type: multipart/mixed; boundary="------------EF676A36CF60A9D1D1456D53" Sender: owner-rmt@lbl.gov Precedence: bulk This is a multi-part message in MIME format. --------------EF676A36CF60A9D1D1456D53 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Just a reminder. The next RMT meeting is as follows: Date: Thursday, Feb 10, 2000 Venue: ACIRI, Berkeley, CA Address: 947 Center st., Berkeley, CA Time: 9:00am - 5:00pm Hotels: try Shattuck Hotel (510-845-7300) 5 min from ACIRI So far I have not had an overwhelming response from potential participants. If we want to keep moving people will need to step up an work together on defining the various building blocks and protocol instantiations. Please try to contact the other people in the various sub-groups and make some progress. Please contact me ASAP if you wish to present and discuss a draft Roger --------------EF676A36CF60A9D1D1456D53 Content-Type: text/x-vcard; charset=us-ascii; name="rkermode.vcf" Content-Description: Card for Roger Kermode Content-Disposition: attachment; filename="rkermode.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Kermode;Roger tel;fax:+61-2-9666-0501 tel;home:+61-2-9664-8335 tel;work:+61-2-9666-0558 x-mozilla-html:FALSE url:www.mot.com.au org:Motorola Australian Research Centre;Scalable Commodity Internet Lab version:2.1 email;internet:Roger.Kermode@motorola.com title:Principal Research Engineer SNAIL MAIL: Locked Bag 5028, Botany NSW, 1455=0D=0A;Botany;NSW;2019;Australia adr;quoted-printable:;;PHYSICAL: Level 3, 12 Lord St., Botany, NSW=0D=0A= x-mozilla-cpt:;-1 fn:Roger Kermode end:vcard --------------EF676A36CF60A9D1D1456D53-- From owner-rmt@listserv.lbl.gov Thu Jan 20 19:54:38 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17592 for ; Thu, 20 Jan 2000 19:54:38 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id PAA16368; Thu, 20 Jan 2000 15:55:40 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA16364 for ; Thu, 20 Jan 2000 15:55:37 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA14413 for ; Thu, 20 Jan 2000 15:55:37 -0800 (PST) Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id PAA14402 for ; Thu, 20 Jan 2000 15:55:36 -0800 (PST) Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by ftpbox.mot.com (VWALL-IN-ftpbox 2.0) with ESMTP id QAA07328 for ; Thu, 20 Jan 2000 16:55:35 -0700 (MST)] Received: [from homer.arc.corp.mot.com ([217.1.10.38]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id QAA13142 for ; Thu, 20 Jan 2000 16:55:32 -0700 (MST)] Received: from arc.corp.mot.com (everest.arc.corp.mot.com [217.1.10.204]) by homer.arc.corp.mot.com (8.9.3/8.9.3) with ESMTP id KAA08242 for ; Fri, 21 Jan 2000 10:50:52 +1100 (EST) Message-ID: <38879F5D.C578D26D@arc.corp.mot.com> Date: Fri, 21 Jan 2000 10:50:53 +1100 From: Roger Kermode Reply-To: Roger.Kermode@motorola.com Organization: Motorola X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: rmt-list Subject: [Fwd: RMT meeting Feb 10 at Aciri] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-rmt@lbl.gov Precedence: bulk Content-Transfer-Encoding: 7bit Ahhh the hazards of copying email... ACIRI's address is 1947 Center St. cheers, Roger -------- Original Message -------- Subject: RMT meeting Feb 10 at Aciri Date: Fri, 21 Jan 2000 10:49:36 +1100 From: Roger Kermode Reply-To: Roger.Kermode@motorola.com Organization: Motorola To: rmt-list Just a reminder. The next RMT meeting is as follows: Date: Thursday, Feb 10, 2000 Venue: ACIRI, Berkeley, CA Address: 947 Center st., Berkeley, CA Time: 9:00am - 5:00pm Hotels: try Shattuck Hotel (510-845-7300) 5 min from ACIRI So far I have not had an overwhelming response from potential participants. If we want to keep moving people will need to step up an work together on defining the various building blocks and protocol instantiations. Please try to contact the other people in the various sub-groups and make some progress. Please contact me ASAP if you wish to present and discuss a draft Roger From owner-rmt@listserv.lbl.gov Fri Jan 21 06:15:35 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06622 for ; Fri, 21 Jan 2000 06:15:34 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id BAA17369; Fri, 21 Jan 2000 01:38:14 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id BAA17365 for ; Fri, 21 Jan 2000 01:38:12 -0800 (PST) From: myzhai@990.net Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id BAA21761 for ; Fri, 21 Jan 2000 01:38:11 -0800 (PST) Received: from 990.net ([202.102.13.155]) by SpamWall.lbl.gov (8.9.3/8.9.3) with SMTP id BAA21758 for ; Fri, 21 Jan 2000 01:38:08 -0800 (PST) Received: (fmail 29235 invoked by uid 1300); 21 Jan 2000 09:31:11 -0000 Date: 21 Jan 2000 09:31:11 -0000 Message-ID: <20000121093111.29234.fmail@990.net> Reply-To: myzhai@990.net To: rmt@lbl.gov Cc: luby@dfountain.com Subject: about "ALC" Content-Transfer-Encoding: 8bit Sender: owner-rmt@lbl.gov Precedence: bulk Content-Transfer-Encoding: 8bit Hello,everyone, I am interested in topics about "ALC(Asynchronous Layered Coding)", where can I find more infomation about it? Thx Zjai __________________________________________________ 欢迎使用金陵热线免费电子邮件系统http://www.990.net From owner-rmt@listserv.lbl.gov Wed Jan 26 08:00:09 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02972 for ; Wed, 26 Jan 2000 08:00:08 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id EAA12463; Wed, 26 Jan 2000 04:13:52 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id EAA12459 for ; Wed, 26 Jan 2000 04:13:50 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id EAA22993 for ; Wed, 26 Jan 2000 04:13:49 -0800 (PST) Received: from smtp1.cluster.oleane.net (smtp1.cluster.oleane.net [195.25.12.16]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id EAA22988 for ; Wed, 26 Jan 2000 04:13:48 -0800 (PST) Received: from oleane (dyn-1-1-009.Vin.dialup.oleane.fr [195.25.4.9]) by smtp1.cluster.oleane.net with SMTP id NAA52637; Wed, 26 Jan 2000 13:12:44 +0100 (CET) Message-ID: <008c01bf67f6$3f458680$0401a8c0@oleane.com> From: "Peter Lewis" To: Subject: SIP 2000 Call for Papaer Date: Wed, 26 Jan 2000 13:09:46 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0089_01BF67FE.9E62EA60" 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 Sender: owner-rmt@lbl.gov Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0089_01BF67FE.9E62EA60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SIP 2000: Beyond H.323? A scientific committe composed of the most = eminent experts in this technology will review the abstracts submitted = from the Call For Papers: http://www.upperside.fr/basip.htm Take a look at the exhibition list. ------=_NextPart_000_0089_01BF67FE.9E62EA60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
SIP 2000: Beyond H.323? A scientific = committe=20 composed of the most eminent experts in this technology will review the=20 abstracts submitted from the Call For Papers:
http://www.upperside.fr/basip.= htm
Take a look at the exhibition=20 list.
 
------=_NextPart_000_0089_01BF67FE.9E62EA60-- From owner-rmt@listserv.lbl.gov Thu Jan 27 14:02:47 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12102 for ; Thu, 27 Jan 2000 14:02:44 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id JAA23890; Thu, 27 Jan 2000 09:55:01 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA23886 for ; Thu, 27 Jan 2000 09:54:59 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA22036 for ; Thu, 27 Jan 2000 09:54:58 -0800 (PST) Received: from hercules.cs.ucsb.edu (hercules.cs.ucsb.edu [128.111.41.30]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA22033 for ; Thu, 27 Jan 2000 09:54:57 -0800 (PST) Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10]) by hercules.cs.ucsb.edu (8.8.6/8.8.6) with ESMTP id JAA22607; Thu, 27 Jan 2000 09:54:40 -0800 (PST) Received: by jackson.cs.ucsb.edu (8.9.3+Sun/SMI-SVR4) id JAA25324 for ; Thu, 27 Jan 2000 09:54:36 -0800 (PST) Date: Thu, 27 Jan 2000 09:54:36 -0800 (PST) From: almeroth@cs.ucsb.edu (Kevin C. Almeroth) Message-Id: <200001271754.JAA25324@jackson.cs.ucsb.edu> To: almeroth@cs.ucsb.edu Cc: nonnen@eurecom.fr Subject: Reminder, CFP: Integrating Multicast into the Internet Sender: owner-rmt@lbl.gov Precedence: bulk Reminder, DEADLINE February 1, 2000 CALL FOR PAPERS: Special Issue of Computer Communications on Integrating Multicast into the Internet CFP URL: http://www.cs.ucsb.edu/~almeroth/COMCOM:cfp.html Journal URL: http://www.elsevier.com/inca/publications/store/5/2/5/4/4/0/ TOPICS: The amount of bandwidth available in the Internet is increasing dramatically, both in the backbone networks, as well as in the last mile (broadband access). One consequence is that the delivery of high-quality multimedia data will become feasible, and multimedia data, including audio and video, will become the dominant traffic. As more users gain access to broadband services, new applications and services will become possible. The result will be a growing demand for large-scale multimedia applications and services. Multicasting as a pure networking solution to the transport of media is recognized as offering economies-of-scale for large-scale applications. Multicast is also believed to enable applications which provide service to thousands, even millions of customers. While there has been significant research work on multicast, efforts to successfully deploy a production service have lagged. Reasons range from frequently changing protocols, management and engineering problems, legacy hardware limitations, traffic conflicts with unicast, etc.. This special issue focuses on research issues dealing with the challenges of deploying multicast in the network. Specific topics include, but are not limited to: * Multicast Congestion Control * Multicast Overlay Networks * Next-Generation Multicast Routing Algorithms * Multicast Media Transport * Security for Multicast-Based Services * Multicast Traffic Engineering and Management * Multicast Pricing and Quality of Service GUEST EDITORS: Kevin Almeroth Jorg Nonnenmacher Department of Computer Science Network Research Dept, Lucent Technologies University of California 600-700 Mountain Avenue Santa Barbara, CA 93106-5110 Murray Hill, NJ 07974-0636 Phone: +1(805) 893-2777 Phone: +1(908) 582-1707 Fax: +1(805) 893-8553 Fax: +1(908) 582-6632 Email: almeroth@cs.ucsb.edu Email: nonnen@eurecom.fr IMPORTANT DATES: Paper Submission Deadline: February 1, 2000 Feedback to Authors: May 1, 2000 Final Manuscripts Due: June 1, 2000 Publication Date: Fall 2000 SUBMISSION INSTRUCTIONS: Papers should be double spaced, 11pt font, and standard margins. Length should be 20 pages maximum not including figures, tables, and references. Maximum total length is 30 pages. Authors are requested to send e-mail to one or both of the Guest Editors (almeroth@cs.ucsb.edu, nonnen@eurecom.fr) giving a URL from where a postscript or PDF file can be downloaded (papers can also be emailed though this is not the preferred format). Successfully received papers will be acknowledged. AUTHOR INFORMATION: Submissions made to the special issue should not have appeared in, or been submitted to other archival publications. All papers will be subjected to the journal's usual refereeing process. From owner-rmt@listserv.lbl.gov Fri Jan 28 04:31:32 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04792 for ; Fri, 28 Jan 2000 04:31:31 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id AAA25740; Fri, 28 Jan 2000 00:49:56 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id AAA25736 for ; Fri, 28 Jan 2000 00:49:54 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id AAA29782 for ; Fri, 28 Jan 2000 00:49:53 -0800 (PST) Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.164.217]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id AAA29779 for ; Fri, 28 Jan 2000 00:49:47 -0800 (PST) Received: from sjkoh (sjkoh.etri.re.kr [129.254.164.46]) by pec.etri.re.kr (8.9.1/8.9.1) with SMTP id RAA27055; Fri, 28 Jan 2000 17:43:55 +0900 (KST) Message-ID: <004c01bf696c$845969e0$2ea4fe81@etri.re.kr> From: "Seok J. Koh" To: "Dah Ming Chiu - Sun Microsystems" , References: <200001122049.PAA25668@bcn.East.Sun.COM> Subject: Re: ACK Building Block Date: Fri, 28 Jan 2000 17:48:57 +0900 Organization: ETRI/PEC MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by SpamWall.lbl.gov id AAA25737 Sender: owner-rmt@lbl.gov Precedence: bulk Content-Transfer-Encoding: 8bit Hi, there, The proposal seems to be one of reasonable inputs for initial draft of ACK building block, even though some addings or modifications are required. For examples, the scope of ACK building block can be explictly described, and some assumptions, including that the tree is given by automatic configurations or can be obtained from external software, may be made. Anyway, I cannot find the item of ACK building block as the drafting work, in the plan of this Mid-Feb RMT meeting. I would like to know why the drafting work of ACK building block has not been inlcuded as a drafting item at the meeting, in spite that NACK and GRA BBs were included. Is that item pre-mature yet ? or overlapped by the other BBs such as tree building or TRACK ? cheers, Seok-Joo, Koh ----- Original Message ----- > Over a month ago, I wrote a short proposal to develop an ACK building > block, and circulated it to a small set of people in RMT for comment. > So far, only Brian Whetten and I have been discussing it; and we have > some different opinions. Since there may be others on the RMT list who > are interested in the (Tree-based) ACK approach, I would like to move > the discussion here. > > Attached is a sketch of an ACK BB (Building Block). I have not updated > it since I wrote it a month ago. It describes the relationship > between a receiver and its repair head (repair node), and some basic > session management functions of the sender, all in terms of an abstract > API. I have also sketched out some algorithms that need to be specified > (such as deciding when to ack and request ack), and some hooks to other > BB's (e.g. congestion control, tree-building). Most importantly, this > is all quite simple. > > I hope this is useful for helping us build the TRACK protocol standards > as we move ahead. Comments are welcome. > > Dah Ming Chiu From owner-rmt@listserv.lbl.gov Mon Jan 31 09:32:36 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04537 for ; Mon, 31 Jan 2000 09:32:35 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id FAA03747; Mon, 31 Jan 2000 05:43:00 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id FAA03743 for ; Mon, 31 Jan 2000 05:42:57 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id FAA28677 for ; Mon, 31 Jan 2000 05:42:56 -0800 (PST) Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id FAA28671 for ; Mon, 31 Jan 2000 05:42:55 -0800 (PST) Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (VWALL-IN-motgate2 2.0) with ESMTP id GAA16741 for ; Mon, 31 Jan 2000 06:42:55 -0700 (MST)] Received: [from homer.arc.corp.mot.com (homer.arc.corp.mot.com [217.1.10.38]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id GAA21000 for ; Mon, 31 Jan 2000 06:42:53 -0700 (MST)] Received: from arc.corp.mot.com ([144.187.5.100]) by homer.arc.corp.mot.com (8.9.3/8.9.3) with ESMTP id AAA20062 for ; Tue, 1 Feb 2000 00:42:48 +1100 (EST) Message-ID: <38959155.B284985C@arc.corp.mot.com> Date: Tue, 01 Feb 2000 00:42:45 +1100 From: Roger Kermode Reply-To: Roger.Kermode@motorola.com Organization: Motorola X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: rmt-list Subject: RMT Agenda Update for Feb 10th Content-Type: multipart/mixed; boundary="------------AA49F7503878746450EC11B0" Sender: owner-rmt@lbl.gov Precedence: bulk This is a multi-part message in MIME format. --------------AA49F7503878746450EC11B0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear RMT'ers, A quick note to let you know that we haven't forgotten about the agenda for Feb 10th. We're currently, trying to piece together an order for the presentation requests we have received (speak up if you haven't already!) We're particularly keen to take advantage of having an entire day to *REAL* work. To that end we're looking at an agenda that will *minimize* presentation time and involve us breaking up into focus groups to work on individual drafts. Please put your thinking caps on be prepared for detailed discussions!!!! An agenda will appear early next week. The details of the meeting one more time.... Date: Thursday, Feb 10, 2000 Host: ACIRI Venue: ICSI Building, 6th Floor Address: 1947 Center st., Berkeley, CA Time: 9:30am - 5:00pm Hotels: try Shattuck Hotel (510-845-7300) 5 min from ACIRI cheers, Roger Allison Lorenzo --------------AA49F7503878746450EC11B0 Content-Type: text/x-vcard; charset=us-ascii; name="rkermode.vcf" Content-Description: Card for Roger Kermode Content-Disposition: attachment; filename="rkermode.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Kermode;Roger tel;cell:+61-408-212-284 tel;fax:+61-2-9666-0501 tel;home:+61-2-9664-8335 tel;work:+61-2-9666-0558 x-mozilla-html:FALSE -mozilla-cpt:;-1;;; url:www.mot.com.au org:Motorola Australian Research Centre;Scalable Commodity Internet Lab version:2.1 email;internet:Roger.Kermode@motorola.com title:Australia adr;quoted-printable:;;PHYSICAL: Level 3, 12 Lord St., Botany, NSW=0D=0A= x-mozilla-cpt:;0 fn:Roger Kermode end:vcard --------------AA49F7503878746450EC11B0-- From owner-rmt@listserv.lbl.gov Mon Jan 31 14:02:15 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12912 for ; Mon, 31 Jan 2000 14:02:09 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id JAA04951; Mon, 31 Jan 2000 09:54:55 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA04947 for ; Mon, 31 Jan 2000 09:54:53 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA24748 for ; Mon, 31 Jan 2000 09:54:53 -0800 (PST) Received: from phobos.talarian.com (mailhost.talarian.com [207.5.32.17]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA24743 for ; Mon, 31 Jan 2000 09:54:51 -0800 (PST) Received: from tahoe (ta036.talarian.com [204.147.187.36] (may be forged)) by phobos.talarian.com (8.9.0/8.9.0) with SMTP id JAA02374; Mon, 31 Jan 2000 09:54:31 -0800 (PST) Message-Id: <4.1.20000131092342.0223a6b0@mailhost.talarian.com> X-Sender: bwhetten@mailhost.talarian.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 31 Jan 2000 09:35:19 -0800 To: Roger.Kermode@motorola.com, rmt-list From: Brian Whetten Subject: Re: RMT Agenda Update for Feb 10th In-Reply-To: <38959155.B284985C@arc.corp.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-rmt@lbl.gov Precedence: bulk Hi all, I'm looking at the amount of work to do, and am beginning to feel that one day won't be nearly enough. Is there any way that we can extend this to Friday as well? It seems like we really need to lock everyone in a room for about a week...but that is obviously not going to happen given all our frightening schedules. As a second possibility, which I'll just throw out as an open invitation, I have access to a couple free condos in South Lake Tahoe, 5 minutes from Heavenly (some of the best terrain in the country, although our snow isn't quite as good as Utah or Colorado). Would people be tempted (especially the non-west coasters?) in to a combined work/play weekend? I can't think of a better place I'd rather work on writing billions of pages of documents. ;) Brian At 12:42 AM 2/1/2000 +1100, Roger Kermode wrote: >Dear RMT'ers, > >A quick note to let you know that we haven't forgotten about the >agenda for Feb 10th. We're currently, trying to piece together >an order for the presentation requests we have received (speak >up if you haven't already!) We're particularly keen to take >advantage of having an entire day to *REAL* work. To that end >we're looking at an agenda that will *minimize* presentation time >and involve us breaking up into focus groups to work on individual >drafts. Please put your thinking caps on be prepared for detailed >discussions!!!! > >An agenda will appear early next week. > > >The details of the meeting one more time.... > > Date: Thursday, Feb 10, 2000 > Host: ACIRI > Venue: ICSI Building, 6th Floor > Address: 1947 Center st., Berkeley, CA > Time: 9:30am - 5:00pm > Hotels: try Shattuck Hotel (510-845-7300) 5 min from ACIRI > >cheers, > >Roger >Allison >Lorenzo From owner-rmt@listserv.lbl.gov Mon Jan 31 14:21:43 2000 Received: from listserv.lbl.gov (listserv.lbl.gov [128.3.7.140]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13561 for ; Mon, 31 Jan 2000 14:21:42 -0500 (EST) Received: (from majordom@localhost) by listserv.lbl.gov (8.9.3/8.9.3) id KAA05223; Mon, 31 Jan 2000 10:20:34 -0800 (PST) X-Authentication-Warning: listserv.lbl.gov: majordom set sender to owner-rmt@listserv.lbl.gov using -f Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id KAA05209 for ; Mon, 31 Jan 2000 10:20:29 -0800 (PST) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id KAA04400 for ; Mon, 31 Jan 2000 10:20:28 -0800 (PST) Received: from aardvark.aciri.org (aardvark.aciri.org [192.150.187.20]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id KAA04395 for ; Mon, 31 Jan 2000 10:20:28 -0800 (PST) Received: from aardvark.aciri.org (localhost [127.0.0.1]) by aardvark.aciri.org (8.9.3/8.9.2) with ESMTP id KAA50247; Mon, 31 Jan 2000 10:17:43 -0800 (PST) (envelope-from mjh@aardvark.aciri.org) From: Mark Handley X-Organisation: ACIRI To: Brian Whetten cc: Roger.Kermode@motorola.com, rmt-list Subject: Re: RMT Agenda Update for Feb 10th In-reply-to: Your message of "Mon, 31 Jan 2000 09:35:19 PST." <4.1.20000131092342.0223a6b0@mailhost.talarian.com> Date: Mon, 31 Jan 2000 10:17:43 -0800 Message-ID: <50245.949342663@aardvark.aciri.org> Sender: owner-rmt@lbl.gov Precedence: bulk >I'm looking at the amount of work to do, and am beginning to feel that one >day won't be nearly enough. Is there any way that we can extend this to >Friday as well? It seems like we really need to lock everyone in a room >for about a week...but that is obviously not going to happen given all our >frightening schedules. We're hosting the SMuG RG meeting on Friday 11th, so the lecture room here won't be available, which is the only room that can host 40+ people. We also have a few smaller conference rooms and a number of offices people can use, so it would be possible to continue into Friday. However, I suspect that this is best done only by individual sub-groups that wish to continue working on a specific topic. So, sub-groups: let me know if you want to continue on the Friday (preferably in advance, but we can usually be fairly flexible even without notice) and let me know how many people you expect to be. I'll then try and sort out appropriate rooms. Cheers, Mark BTW, some SMuG people had trouble booking the suggested hotel. There's also a list of hotels at http://www.lbl.gov/Workplace/near-our-shuttle.html All the starred ones are reasonably close to ICSI.