From owner-diffserv@optimus.ietf.org Wed Sep 22 13:01:33 1999 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09713 for ; Wed, 22 Sep 1999 13:01:33 -0400 (EDT) From: sweilnau@optimus.ietf.org Received: (from root@localhost) by optimus.ietf.org (8.9.1a/8.8.8) id NAA27427 for diffserv@ietf.org; Wed, 22 Sep 1999 13:01:27 -0400 (EDT) Date: Wed, 22 Sep 1999 13:01:27 -0400 (EDT) Message-Id: <199909221701.NAA27427@optimus.ietf.org> To: diffserv@ietf.org Subject: Test1 test1 From owner-diffserv@optimus.ietf.org Wed Sep 22 13:02:45 1999 Received: (from root@localhost) by ietf.org (8.9.1a/8.9.1a) id NAA09735 for diffserv; Wed, 22 Sep 1999 13:02:45 -0400 (EDT) Date: Wed, 22 Sep 1999 13:02:45 -0400 (EDT) From: Stanley Weilnau Message-Id: <199909221702.NAA09735@ietf.org> To: diffserv Subject: test from odin hello from odin. From owner-diffserv@optimus.ietf.org Wed Sep 29 08:12:25 1999 Received: from cnri.reston.va.us (cnri.reston.va.us [132.151.1.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24158 for ; Wed, 29 Sep 1999 08:12:25 -0400 (EDT) Received: from action-nt.cnri.reston.va.us (action-nt [132.151.1.91]) by cnri.reston.va.us (8.9.1a/8.9.1) with ESMTP id IAA00490 for ; Wed, 29 Sep 1999 08:12:12 -0400 (EDT) Date: Wed, 29 Sep 1999 08:14:08 -0400 (Eastern Daylight Time) From: Stanley Weilnau To: diffserv@ietf.org Subject: test message Message-ID: X-X-Sender: sweilnau@kaluha.cnri.reston.va.us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Lets make sure this gets in the archive also. From diffserv-admin@ietf.org Wed Sep 29 15:23:56 1999 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11973 for ; Wed, 29 Sep 1999 15:23:56 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id PAA18563 for ; Wed, 29 Sep 1999 15:23:44 -0400 (EDT) Date: Wed, 29 Sep 1999 15:23:44 -0400 (EDT) From: diffserv-admin@ietf.org Message-Id: <199909291923.PAA18563@optimus.ietf.org> Subject: Welcome To "Diffserv"! To: diffserv-archive@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Welcome to the Diffserv@ietf.org mailing list! To post to this list, send your email to: diffserv@ietf.org General information about the mailing list is at: http://www.ietf.org/mailman/listinfo/diffserv If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://www.ietf.org/mailman/options/diffserv/diffserv-archive@lists.ietf.org You can also make such adjustments via email by sending a message to: Diffserv-request@ietf.org with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: EhyO If you forget your password, don't worry, you will receive a monthly reminder telling you what all your ietf.org mailing list passwords are, and how to unsubscribe or change your options. There is also a button on your options page that will email your current password to you. You may also have your password mailed to you automatically off of the Web page noted above. From owner-diffserv@optimus.ietf.org Thu Sep 30 01:12:24 1999 Received: from etri.re.kr ([129.254.113.113]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22857 for ; Thu, 30 Sep 1999 01:12:23 -0400 (EDT) Received: from jsjang (jsjang.etri.re.kr [129.254.191.104]) by etri.re.kr (8.9.3/8.9.3) with SMTP id OAA26093 for ; Thu, 30 Sep 1999 14:10:05 +0900 (KST) Message-ID: <005f01bf0b02$9dd3b240$68bffe81@etri.re.kr> From: "jsjang" To: Subject: subscribe Date: Thu, 30 Sep 1999 14:14:01 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_005C_01BF0B4E.0B5F1AC0" 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 This is a multi-part message in MIME format. ------=_NextPart_000_005C_01BF0B4E.0B5F1AC0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 c3Vic2NyaWJlIA0K ------=_NextPart_000_005C_01BF0B4E.0B5F1AC0 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWtz X2NfNTYwMS0xOTg3IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1T SFRNTCA1LjAwLjI2MTQuMzQwMSIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+c3Vic2NyaWJlIDwvRElWPjwvQk9E WT48L0hUTUw+DQo= ------=_NextPart_000_005C_01BF0B4E.0B5F1AC0-- From owner-diffserv@optimus.ietf.org Thu Sep 30 01:13:08 1999 Received: from etri.re.kr ([129.254.113.113]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22960 for ; Thu, 30 Sep 1999 01:13:06 -0400 (EDT) Received: from jsjang (jsjang.etri.re.kr [129.254.191.104]) by etri.re.kr (8.9.3/8.9.3) with SMTP id OAA26181 for ; Thu, 30 Sep 1999 14:10:51 +0900 (KST) Message-ID: <007001bf0b02$b8f705e0$68bffe81@etri.re.kr> From: "jsjang" To: Subject: Subscribe Date: Thu, 30 Sep 1999 14:14:50 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006D_01BF0B4E.28AC5340" 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 This is a multi-part message in MIME format. ------=_NextPart_000_006D_01BF0B4E.28AC5340 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 U3Vic2NyaWJlIGRpZmZzZXJ2OiAgIGpzamFuZ0BldHJpLnJlLmtyDQo= ------=_NextPart_000_006D_01BF0B4E.28AC5340 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWtz X2NfNTYwMS0xOTg3IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1T SFRNTCA1LjAwLjI2MTQuMzQwMSIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPlN1YnNjcmli ZSBkaWZmc2VydjombmJzcDsmbmJzcDsgDQpqc2phbmdAZXRyaS5yZS5rcjwvRk9OVD48L0RJVj48 L0JPRFk+PC9IVE1MPg0K ------=_NextPart_000_006D_01BF0B4E.28AC5340-- From owner-diffserv@optimus.ietf.org Thu Sep 30 10:12:38 1999 Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10033 for ; Thu, 30 Sep 1999 10:12:36 -0400 (EDT) Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA92284; Thu, 30 Sep 1999 15:11:28 +0100 Received: from hursley.ibm.com (lig32-226-176-90.us.lig-dial.ibm.com [32.226.176.90]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA24450; Thu, 30 Sep 1999 15:11:23 +0100 (BST) Message-ID: <37F362B8.8C3EBD43@hursley.ibm.com> Date: Thu, 30 Sep 1999 08:16:40 -0500 From: Brian E Carpenter Organization: IBM Internet Division X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Diff Serv CC: Vern Paxson , Scott Bradner Subject: RFC 793 issue Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Diffservers, It has recently been observed that the diffserv model has potential impact on TCP implementations that strictly implement the provisions of RFC 793 regarding the old IP precedence bits (bits 0, 1 and 2 of the type-of-service byte in IPv4, renamed the Differentiated Services field for the purposes of the diffserv model). There is an explanation, and a proposed change to the TCP specification, in draft-xiao-tcp-prec-00.txt. In particular, the diffserv architecture allows intermediate routers to rewrite the bits in the DS field according to locally installed traffic conditioning specifications. Concern has been expressed that such rewriting may trigger TCP resets in strict implementations of RFC 793. Regardless of whether the TCP specification is updated, this concern must be addressed for existing implementations. RFC 793 assumes that the old IP Precedence bits are transmitted unchanged and symmetrically across the network. In practice, TOS bytes are commonly rewritten (zeroed) today, to prevent abusive use of high precedence, except in networks specifically configured to allow the use of precedence for user traffic. Diffserv does not change this situation, except that ad hoc router configuration is replaced by diffserv traffic conditioning specifications. If a network requires certain precedence values to be transmitted unchanged, these can be configured as DCSPs mapped to a PHB that never re-marks traffic. In practical terms, this changes nothing compared to today (and meets the Diffserv goal of backwards compatibility with IP Precedence). A secondary point is that even when the DSCP is rewritten by intermediate routers, in most cases all packets of the same flow will have their DSCP rewritten in the same way. To date, only one per-hop behavior (PHB) has been standardized that allows different packets from the same flow to receive different code points. This is the Assured Forwarding PHB defined in RFC 2597. However, even when different AF packets from the same flow carry different DS code points, they all have (by design) the same value in bits 0-2, i.e. in the old precedence bits. A TCP implementation strictly conforming to RFC 793 will not see any change in the precedence level, even if some packets of the AF flow are marked differently from others. Therefore it seems that the diffserv architecture, and all the PHBs standardized so far, do not break even strictly conforming RFC 793 implementations, as long as appropriate traffic conditioning specifications are configured. Clearly, some text to document this issue and constrain future diffserv design work should be included in the next version of the basic diffserv documents. Brian + Kathie From owner-diffserv@optimus.ietf.org Thu Sep 30 10:21:19 1999 Received: from adn.alcatel.com (postman.adn.alcatel.com [198.205.32.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10175 for ; Thu, 30 Sep 1999 10:21:18 -0400 (EDT) Received: from postal.adn.alcatel.com (postal [198.205.32.56]) by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id KAA23003 for ; Thu, 30 Sep 1999 10:14:58 -0400 (EDT) Received: from adn.alcatel.com ([198.205.33.227]) by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with ESMTP id AAA1278 for ; Thu, 30 Sep 1999 10:24:19 -0400 Message-ID: <37F3737A.148762A3@adn.alcatel.com> Date: Thu, 30 Sep 1999 10:28:10 -0400 From: Alex Mondrus X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: diffserv@ietf.org Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit From owner-diffserv@optimus.ietf.org Thu Sep 30 12:02:08 1999 Received: from slb-smtpout-01.boeing.com ([12.13.237.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12648 for ; Thu, 30 Sep 1999 12:02:07 -0400 (EDT) Received: from slb-hub-01.boeing.com ([129.172.13.51]) by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id JAA28300 for ; Thu, 30 Sep 1999 09:02:01 -0700 (PDT) Received: from [199.191.48.146] by slb-hub-01.boeing.com for diffserv@ietf.org; Thu, 30 Sep 1999 09:02:01 -0700 Received: by engr03.arl.bna.boeing.com (UCX V4.1-12A, OpenVMS V7.1 Alpha); Thu, 30 Sep 1999 12:01:19 -0400 Message-Id: <003901bf0b5d$20e1db80$c330bfc7@arl.bna.boeing.com> From: "Albert Manfredi" To: "Brian E Carpenter" , "Diff Serv" References: <37F362B8.8C3EBD43@hursley.ibm.com> Subject: Re: [Diffserv] RFC 793 issue Date: Thu, 30 Sep 1999 12:01:58 -0400 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 7bit Brian, I agree with everything you say below, but I think the possible problem scenario that was raised was when the diffserv environment _re-marks_ packets. If the DSCP is changed somewhere between ingress and egress, then how would the egress know to what original TOS value to set the outgoing packet? In a steady stream, where packets are potentially being re-marked, _in general_ this could be a problem. I agree that the problem might not be realistic today, and that just setting the TOS byte at the egress to 0 fixes everything, and that so far the DSCP top three bits aren't changed by AF now anyway, but these are not the final word. Are they? (Or maybe they are the final word. The world is full of this sort of pragmatic solution, after all. It still rotates around the sun.) Bert manfredi@arl.bna.boeing.com ----- Original Message ----- From: Brian E Carpenter > Diffservers, > > It has recently been observed that the diffserv model has > potential impact on TCP implementations that strictly implement > the provisions of RFC 793 regarding the old IP precedence > bits (bits 0, 1 and 2 of the type-of-service byte in IPv4, > renamed the Differentiated Services field for the purposes > of the diffserv model). There is an explanation, and a > proposed change to the TCP specification, in > draft-xiao-tcp-prec-00.txt. > > In particular, the diffserv architecture allows intermediate > routers to rewrite the bits in the DS field according to > locally installed traffic conditioning specifications. Concern > has been expressed that such rewriting may trigger TCP resets > in strict implementations of RFC 793. Regardless of whether > the TCP specification is updated, this concern must be addressed > for existing implementations. > > RFC 793 assumes that the old IP Precedence bits are transmitted > unchanged and symmetrically across the network. In practice, > TOS bytes are commonly rewritten (zeroed) today, to > prevent abusive use of high precedence, except in networks > specifically configured to allow the use of precedence for user > traffic. Diffserv does not change this situation, except that > ad hoc router configuration is replaced by diffserv traffic > conditioning specifications. If a network requires certain > precedence values to be transmitted unchanged, these can be > configured as DCSPs mapped to a PHB that never re-marks traffic. > In practical terms, this changes nothing compared to today > (and meets the Diffserv goal of backwards compatibility > with IP Precedence). > > A secondary point is that even when the DSCP is rewritten by > intermediate routers, in most cases all packets of the same flow will > have their DSCP rewritten in the same way. To date, only one per-hop > behavior (PHB) has been standardized that allows different packets > from the same flow to receive different code points. This is the > Assured Forwarding PHB defined in RFC 2597. However, even when > different AF packets from the same flow carry different DS code > points, they all have (by design) the same value in bits 0-2, i.e. > in the old precedence bits. A TCP implementation strictly > conforming to RFC 793 will not see any change in the precedence > level, even if some packets of the AF flow are marked differently > from others. > > Therefore it seems that the diffserv architecture, and all the > PHBs standardized so far, do not break even strictly conforming > RFC 793 implementations, as long as appropriate traffic conditioning > specifications are configured. Clearly, > some text to document this issue and constrain future diffserv > design work should be included in the next version of the basic > diffserv documents. > > Brian + Kathie > > > > _______________________________________________ > Diffserv mailing list > Diffserv@ietf.org > http://www.ietf.org/mailman/listinfo/diffserv > From owner-diffserv@optimus.ietf.org Thu Sep 30 12:23:22 1999 Received: from cs.bu.edu (root@CS.BU.EDU [128.197.10.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13060 for ; Thu, 30 Sep 1999 12:23:22 -0400 (EDT) Received: from cs.bu.edu (matta@memphis [128.197.10.43]) by cs.bu.edu ((8.8.8.buoit.v1.0)/8.8.8/(BU-S-10/16/98-v1.0a)) with ESMTP id MAA27622; Thu, 30 Sep 1999 12:23:19 -0400 (EDT) Sender: matta@cs.bu.edu Message-ID: <37F38E76.C7778983@cs.bu.edu> Date: Thu, 30 Sep 1999 12:23:18 -0400 From: Ibrahim Matta Organization: Boston University, Computer Science Department X-Mailer: Mozilla 4.61 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: diffserv@ietf.org, qosr@newbridge.com, int-serv@isi.edu, te-wg@UU.NET Subject: [Fwd: ICNP'99 program] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit My apologies if you receive multiple copies. Regards, ibrahim > > ------------------------------------------------------------------------ > > CALL FOR REGISTRATION > > 7th International Conference on Network Protocols > > October 31 - November 3, 1999 > > The Royal York Hotel, Toronto, Canada > > www.computer.org/conferen/home/icnp/ > > ICNP is one of the premier conferences in the computer networking > field. This year ICNP'99 will be held in Toronto, whose name is a > Huron Indian word meaning "place of meeting". Toronto is Canada's > largest city, the capital of the province of Ontario, and one of the > most exciting and progressive cities in the world. Its attractions are > far too numerous to list. > > The conference will be held at the famous Royal York Hotel. The Royal > York has been in operation since 1929 and is one of the grand hotels > of Canada. It is located in the centre of downtown Toronto, a focal > point for shopping, culture and nightlife. > > -------------------- > ICNP'99 REGISTRATION > -------------------- > > Conference and hotel registration information is available at the > ICNP'99 web site: www.computer.org/conferen/home/icnp/ > > * The hotel room cutoff date is OCTOBER 8, 1999. > > * The conference advance registration deadline is OCTOBER 11, 1999. > > To avoid disappointment, please register as soon as possible. > > --------------- > ICNP'99 PROGRAM > --------------- > > Sunday, 31 October 1999 > ----------------------- > > Full-Day Tutorials > > 9:00am - 5:00pm Lunch provided > > * Internet Telephony > Henning Schulzrinne, Columbia University > > * Mobile Networking with Mobile IP > Charles E. Perkins, Sun Microsystems > > (Further details of the tutorials are given at the end of this > program.) > > Monday, 1 November 1999 > ----------------------- > > 9:00am - 9:30am Welcome Session > > 9:30am - 10:30am Keynote Address: > > * Dr. Jon Turner, Washington University > > "Technology Changes and Networking Research -- Speculations on > the Future" > > 10:30am - 11:00am Break > > 11:00am - 12:30am Paper Session 1: Protocols and Routing > > Automated Protocol Implementations based on Activity Threads > P. Langendoerfer, H. Koenig (Brandenburg University of Cottbus) > > Dynamic Memory Model-based Optimization and Code Synthesis for IP > Address Lookup > G. Cheung, S. McCanne (U.C. Berkeley) > > Policy Disputes in Path-Vector Protocols > T. Griffin, F. Shepherd, G. Wilfong (Bell Laboratories) > > Fault Detection in Routing Protocols > D. Massey (UCLA), B. Fenner (AT&T Research) > > 12:30am - 2:00pm Lunch Break > > 2:00pm - 3:30pm Paper Session 2: Multicast I > > Receiver-Cooperative Bandwidth Management for Layered Multicast > H. Yamaguchi, T. Higashino, K. Taniguchi (Osaka University), K. > Yasumoto (Shiga University) > > Receiver-initiated Group Membership Protocol (RGMP): A New Group > Management Protocol for IP Multicasting > W. Liao, D. Yang (National Taiwan university) > > Centralized Multicast > S. Keshav (Cornell University), S. Paul (Bell Laboratories) > > Optimal Allocation of Clients to Replicated Multicast Servers > Z. Fei, M. Ammar, E. Zegura (Georgia Institute of Technology) > > 3:30pm - 4:00pm Break > > 4:00pm - 5:30pm Paper Session 3: Multicast II > > Scaling End-to-end Multicast Transports with a Topologically-sensitive > Group Formation Protocol > S. Ratnasamy, S. McCanne (U.C. Berkeley) > > WDM Multicasting in IP over WDM Networks > C. Qiao, M. Jeong, (SUNY at Buffalo), A. Guha (AT&T Labs), X. Zhang > (Lucent Technologies), J. Wei (Telcordia Technologies, Inc) > > Evaluating the Utility of FEC with Reliable Multicast > D. Li, D. Cheriton (Stanford University) > > A Logical Ring Reliable Multicast Protocol for Mobile Nodes > I. Nikolaidis, J. Harms (University of Alberta) > > 5:30pm - 7:30pm Reception > > Tuesday, 2 November 1999 > ------------------------ > > 9:00am - 10:30am Paper Session 4: Quality of Service I > > ERUF: Early Regulation of Unresponsive Best-Effort Traffic > A. Rangarajan, A. Acharya (U.C. Santa Barbara) > > An In-Depth Look at Flow Aggregation for Quality of Service > Jorge Cobb (University of Texas at Dallas) > > NBQ: Neighbor-state Based Queuing for Adaptive Bandwidth Sharing > Y. Tamura, Y. Tobe, H. Tokuda (Keio University) > > Evaluation of Bandwidth Broker Signaling > M. Gunter, T. Braun (University of Berne) > > 10:30am - 11:00am Break > > 11:00am - 12:30am Paper Session 5: Quality of Service II > > Minimum Rate Guarantee without Per-Flow Information > Y. Kim, W. Tsai, M. Iyer, J. Ros (U.C. Irvine) > > A New Proposal of RSVP Refreshes > L. Wang, A. Terzis, L. Zhang (UCLA) > > Effect of Unreliable Nodes on QoS Routing > S. Gokhale, S. Tripathi (U.C. Riverside) > > How to make assured services more assured > W. Lin, R. Zheng, J. Hou (Ohio State University) > > 12:30am - 2:00pm Lunch Break > > 2:00pm - 3:30pm Panel 1: Embedded Wireless Networks > > 3:30pm - 4:00pm Break > > 4:00pm - 5:30pm Paper Session 6: Transport Protocols > > Empirical TCP Profiles and Application > C. Popescu, A.U. Shankar (University of Maryland) > > On Individual and Aggregate TCP Performance > L. Qiu, Y. Zhang, S. Keshav (Cornell University) > > Improving TCP Congestion Control Over Internets with Heterogenous > Transmission Media > C. Parsa, J. Garcia-Luna-Aceves (U.C. Santa Cruz) > > TCP Trunking: Design, Implementation and Performance > H.T. Kung, S.Y. Wang (Harvard University) > > Wednesday, 3 November 1999 > -------------------------- > > 9:00am - 10:30am Paper Session 7: Wireless Networks I > > The Havana Framework for Supporting Application and Channel > Dependent QOS in Wireless Networks > J. Gomez, A. Campbell (Columbia University), H. Morikawa (University > of Toyko) > > A Distributed Scheduling Algorithm for Quality of Service Support in > Multiaccess Networks > C. Barrack, K. Siu (MIT) > > Fluid Analysis of Delay Performance for QoS Support in Wireless Networks > J. Kim, M. Krunz (University of Arizona) > > Scheduling in Wireless Networks with Multiple Transmission Channels > S. Damodaran, K. Sivalingam (Washington State University) > > 10:30am - 11:00am Break > > 11:00am - 12:30am Panel 2: Active Networks: Where Do We Stand Today? > > 12:30am - 2:00pm Lunch Break > > 2:00pm - 3:30pm Paper Session 8: Wireless Networks II > > Source-Tree Routing in Wireless Networks > J. Garcia-Luna-Aceves (U.C. Santa Cruz), M. Spohn (Nokia Wireless Routers) > > HAWAII: A Domain-based Approach for Supporting Mobility in Wide-area > Wireless Networks > R. Ramjee, T. La Porta, S. Thuel, K. Varadhan (Bell Labs, Lucent > Technologies) and S. Wang (Harvard University) > > Analysis of Caching-based Location Management in Personal Communication > Networks > K. Ratnam (Northeastern University), I. Matta (Boston University), > S. Rangarajan (Bell Laboratories) > > Wave and Wait Protocol (WWP): An Energy Saving Protocol for Mobile > IP-Devices > V. Tsaoussidis, H. Badr, R. Verma (SUNY at Stony Brook) > > 3:30pm - 4:00pm Break > > 4:00pm - 5:30pm Paper Session 9: Internet Services > > Smoothing and Prefetching Video from Distributed Servers > S. Bakiras, V. Li (University of Hong Kong) > > Analysis of Receiver Adaptation for Layered Video Transmission over > Heterogeneous Networks: A Microscopic Perspective > P. Hu, Z. Zhang, M. Kaveh (University of Minnesota) > > A Behavioral Model of Web Traffic > H. Choi, J. Limb (Georgia Institute of Technology) > > Concast: Design and Implementation of a New Network Service > K. Calvert, J. Griffioen, A. Sehgal, S. Wen (University of Kentucky) > > ---------------- > TUTORIAL PROGRAM > ---------------- > > Internet Telephony > > Henning Schulzrinne, Columbia University > > Internet telephony or voice-over-IP (VoIP), the use of the Internet to > replace parts of the existing circuit-switched telephone network, holds > the promise of fundamentally changing how telephone calls are made. > Beyond replacing the circuit-switched network, VoIP has the potential of > making phone service as flexible and programmable as email and web > service, speed the availability of multimedia communications, as well as > integrating phone service with existing common Internet services. > > This tutorial introduces the major components needed to support > telephony in the Internet: signaling, quality-of-service support and > media transport. It covers the basic signaling protocols, such as > H.323, MGCP/Megaco and SIP, as well as how to use them to provide common > and advanced services. VoIP will likely be a major user of resource > reservation and differentiated services, possibly with charging and > policy extensions. Finally, voice and video data has to be carried > efficiently across the network. > > For the foreseeable future, Internet telephony has to interwork with the > existing phone system. We discuss how this can be done, either by > viewing the Internet telephone as a switch or as an end system. A basic > introduction to the existing telephone architecture will be provided. > > Internet Telephony > > motivation for Internet telephony > transmission efficiency > OAM integration > services > > short summary of the existing PSTN (SS7) > digital transmission and switching > SS7 architecture: SSP, SCP, ... > SS7 protocol stack: MTP, ISUP, TCAP > > signaling: H.323, SIP > role of signaling > SIP architecture: user agents, proxies and redirect servers > SIP forking > SIP security > H.323 architecture > interaction of signaling and resource reservation > > Internet telephony services > SIP services > cgi-bin > Call Processing Language > > Internet telephony device control > motivation and architecture > MGCP > > Interoperation with the PSTN > architectures: bridging or tunneling > SIP-to-ISUP translation > E.164 address mapping > > Gateway location > motivation and architecture > BGP and synchronization approaches > > Billing and operational issues > Billing for what and where? > Emergency services > Operator services > Intercepts > > audio/video codings > audio coding techniques: sample vs. frame > impairments for packet audio > uncompress digital video formats: YUV, CIF, ... > JPEG > MPEG > > quality of service constraints and impairments > packet loss > packet delay: causes and requirements > delay jitter > QOS compensation mechanisms > > packet scheduling and resource reservation > traffic policing: GCRA and token buckets > packet scheduling: priority and WFQ > receiver-oriented resource reservation: RSVP > sender-oriented resource reservation: YESSIR > Diff-Serv > > RTP > motivation > packet formats for data > RTCP for QOS feedback and audience size estimation > media synchronization > > BIOGRAPHY > --------- > > Henning Schulzrinne received his undergraduate degree in economics and > electrical engineering from the Technische Hochschule in Darmstadt, > Germany, in 1984, his MSEE degree as a Fulbright scholar from the > University of Cincinnati, Ohio and his Ph.D. degree from the > University of Massachusetts in Amherst, Massachusetts in 1987 and > 1992, respectively. From 1992 to 1994, he was a member of technical > staff at AT&T Bell Laboratories, Murray Hill. From 1994-1996, he was > associate department head at GMD-Fokus (Berlin), before joining the > Computer Science and Electrical Engineering departments at Columbia > University, New York. His research interests encompass real-time, > multimedia network services in the Internet and modeling and performance > evaluation. > > He is an editor of the Journal of Communications and Networks and IEEE > Communications Society editor of the IEEE Internet Computing Magazine. > He co-chairs the IEEE Communications Society Internet Technical > Committee and is vice chair of the IEEE Communications Society Technical > Committee on Computer Communications. He has been vice general chair of > IEEE Infocom and will be co-technical chair of that conference in 2000. > > Protocols co-developed by him are now Internet standards, used by almost > all Internet telephony and multimedia applications. > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Mobile Networking with Mobile IP > > Charles E. Perkins, Sun Microsystems > > When mobile computers move, and attach themselves to new networks > within the Internet, they can use mobile-IP as a means to achieve > seamless roaming transparently to application software. In this > situation, transparent means that the applications work just as > before, and don't need to be recompiled or reconfigured. Seamless > means that roaming from one place to another occurs without > inconvenience to the user. As long as a physical path exists for > communication, the user might not even be aware when a cell boundary > has been crossed. The objective of the seminar is to lay out the > necessary protocol technology to allow mobile computers to use > mobile-IP, and to describe the relevant operation of other protocols > which can be used to aid mobility. > > In this tutorial, I will explore in detail all aspects of > mobile-IP and other standard protocols that further simplify > the operation of mobile computers in the Internet, including: > - Mobile Agent advertisements > - Registration procedures > - Tunneling mechanisms > - The role of Security > - Home Agents > - Foreign Agents > - How to set up a home network > - Getting Care-of Addresses via DHCP > - Route Optimization > - Smooth handoffs > - Reverse tunnels and filtering by border routers > - IPv6 mobility support > - AAA (Authentication, Authorization, and Accounting) > > The seminar is intended for anyone who is interested in learning > about how to use mobile-IP, create a home network for mobile > users within their organization, or explore new Internet protocols > and mobile computing. This includes programmers, administrators, > network managers, and mobile computer users who are already familiar > with using the Internet. > > The following is a rough outline of the tutorial, which will be adapted > to fit the interests of the audience and the time available. > > Introduction - Why Mobile Networking? > o Wireless Technologies > o Laptop Computing > o Information Superhighway > o Mobility vs. Portability > o The Need for two-level addressing > > Mobile IP > o What is Mobile IP? > o Terminology > o Protocol Oveview > o Mobile Agent Discovery > o Solicitation Packet Format > o Advertisement Packet Format > o Registration > o Registration Packet Format > o Registration Reply and Status Codes > o Tunneling > o IP-Within-IP > o Minimal Encapsulation Format > o Generic Record Encapsulation (GRE) > o Security > o Home Networks > o Virtual Home Networks > o Discovering Home Agent Addresses > o Gratuitous ARP > o ARP handling by the mobile node > o TCP Congestion control vs Error-prone Media > o Private Addresses > o Route Optimization > o Role of the Internet Engineering Task Force > > Mobility Considerations in IP version 6 > o An Overview of IPv6 > o IPv6 Options > o IP version 4 vs IP version 6 > o Mobility Considerations in IPv6 > o Binding Update Option > o Binding Acknowledgment ICMP Message > o Binding Request option > o Home Address option > o Home Agent Discovery > o Node and Router requirements for Mobility Support > > Mobile IP and AAA > o AAA functionality > o Simple Mobile IP protocol extensions > o Local Handoff > o Dynamic home-address allocation > o Surrogate Registration > o Localized Registration/multi-level foreign agents > > BIOGRAPHY > --------- > > Charles E. Perkins is a Senior Staff Engineer at Sun Laboratories, > investigating mobile wireless networking and dynamic configuration > protocols. He is the editor for several ACM and IEEE journals > for areas related to wireless networking. He is serving as document > editor for the mobile-IP working group of the Internet Engineering Task > Force (IETF), and is author or co-author of standards-track documents > in the mobileip, svrloc, dhc (Dynamic Host Configuration) and IPng working > groups. Charles is also associate editor for Mobile Communications and > Computing Review, the official publication of ACM SIGMOBILE, and is > on the editorial staff for IEEE Internet Computing magazine. He has > served on the Internet Architecture Board (IAB) of the IETF. Charles > has authored a book on Mobile IP, and has published a number of papers > and award winning articles in the areas of mobile networking, ad-hoc > networking, route optimization for mobile networking, resource discovery, > and automatic configuration for mobile computers. Charles has served > on various committees for the National Research Council, and is currently > the chairperson of the Nomadicity Working Team of the Cross-Industry > Working Team (XIWT). > > Charles holds a B.A. in mathematics and a M.E.E. degree from Rice > University, and a M.A. in mathematics from Columbia University. > He is a member of ISOC, ACM, IEEE, and the IETF. -- Ibrahim Matta Dept of Comp Sci, 111 Cummington St, MCS-271 Assistant Professor Boston University, Boston, MA 02215 matta@cs.bu.edu http://www.cs.bu.edu/faculty/matta/ From owner-diffserv@optimus.ietf.org Thu Sep 30 13:41:57 1999 Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14731 for ; Thu, 30 Sep 1999 13:41:57 -0400 (EDT) Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182]) by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id TAA06872; Thu, 30 Sep 1999 19:32:01 +0200 (MET DST) Received: from alcatel.be ([138.203.66.143]) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id TAA22667; Thu, 30 Sep 1999 19:31:49 +0200 (MET DST) Message-ID: <37F39E3E.BF83E244@alcatel.be> Date: Thu, 30 Sep 1999 19:30:38 +0200 From: Omar Elloumi Organization: Alcatel Corporate Research Center X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: diffserv@ietf.org, qosr@newbridge.com, int-serv@isi.edu, te-wg@UU.NET, xtp-relay@cs.concordia.ca, sigmedia@bellcore.com, tccc@ieee.org, Conferencesa@comsoc.org, "Undisclosed-Recipient:@s2.smtp.oleane.net" , "end2end-interest@ISI.EDU" , "fokus-user@fokus.gmd.de" , "hipparch@sophia.inria.fr" , "giga@tele.pitt.edu" , "WG-ALL@TERENA.NL" , rap@iphighway.com, ippm@advanced.org, iptel@lists.research.bell-labs.com, nat@livingston.com, pilc@grc.nasa.gov, tcpsat@grc.nasa.gov, ipsec@lists.tislabs.com, www-security@ns2.Rutgers.EDU, mpls@UU.NET, lsma@gmu.edu Subject: CFP ISCC'2000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Please accept my apologies if you receive multiple copies of this CFP. CALL FOR PAPERS ISCC'2000 IEEE Symposium on Computers and Communications Antibes- France, July 4-6 2000 http://www.rennes.enst-bretagne.fr/~afifi/iscc/2000.html Please note that the deadline for paper submission is October 5 1999. For the publicity committee Omar Elloumi. From owner-diffserv@optimus.ietf.org Thu Sep 30 16:46:37 1999 Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18550 for ; Thu, 30 Sep 1999 16:46:36 -0400 (EDT) Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182]) by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id WAA23630; Thu, 30 Sep 1999 22:34:49 +0200 (MET DST) Received: from alcatel.be ([138.203.66.143]) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) with ESMTP id WAA02752; Thu, 30 Sep 1999 22:35:21 +0200 (MET DST) Message-ID: <37F3C943.D1E28B42@alcatel.be> Date: Thu, 30 Sep 1999 22:34:11 +0200 From: Omar Elloumi Organization: Alcatel Corporate Research Center X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: diffserv@ietf.org, qosr@newbridge.com, int-serv@isi.edu, te-wg@UU.NET, xtp-relay@cs.concordia.ca, sigmedia@bellcore.com, tccc@ieee.org, Conferencesa@comsoc.org, "Undisclosed-Recipient:@s2.smtp.oleane.net" , "end2end-interest@ISI.EDU" , "fokus-user@fokus.gmd.de" , "hipparch@sophia.inria.fr" , "giga@tele.pitt.edu" , "WG-ALL@TERENA.NL" , rap@iphighway.com, ippm@advanced.org, iptel@lists.research.bell-labs.com, nat@livingston.com, pilc@grc.nasa.gov, tcpsat@grc.nasa.gov, ipsec@lists.tislabs.com, www-security@ns2.Rutgers.EDU, mpls@UU.NET, lsma@gmu.edu, Tarek Saadawi Subject: CFP ISCC'2000 References: <37F39E3E.BF83E244@alcatel.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sorry for the typo, the deadline for ISCC paper submission is November 5 1999 instead of October 5 as indicated in my last mail Omar Elloumi > Please accept my apologies if you receive multiple copies of this CFP. > > CALL FOR PAPERS ISCC'2000 > > IEEE Symposium on Computers and Communications > Antibes- France, July 4-6 2000 > http://www.rennes.enst-bretagne.fr/~afifi/iscc/2000.html > > Please note that the deadline for paper submission is October 5 1999. > > For the publicity committee > Omar Elloumi. -- ____________________________________________________________ Omar Elloumi Alcatel Research - Network Architecture - Traffic Technology Francis Wellesplein 1, 2018 Antwerp, Belgium Phone: + 32 3 240 78 33 Fax: + 32 3 240 99 32 http://www.alcatel.com/crc/ ____________________________________________________________ Opinions expressed are those of the sender and do not reflect Alcatel policy or agreement From owner-diffserv@optimus.ietf.org Thu Sep 30 21:08:01 1999 Received: from procyon.pmc-sierra.bc.ca ([134.87.115.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24136 for ; Thu, 30 Sep 1999 21:08:00 -0400 (EDT) Received: from nt-exchange1.pmc-sierra.bc.ca (nt-exchange1.pmc-sierra.bc.ca [134.87.116.183]) by procyon.pmc-sierra.bc.ca (6.6.6/6.6.6) with ESMTP id SAA04322 for ; Thu, 30 Sep 1999 18:07:30 -0700 (PDT) Received: by nt-exchange1.pmc-sierra.bc.ca with Internet Mail Service (5.5.2448.0) id ; Thu, 30 Sep 1999 18:07:32 -0700 Message-ID: From: Shahram Davari To: Diff Serv Subject: EF shaping Date: Thu, 30 Sep 1999 18:07:24 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Hi All, A stupid question. Do we need to shape EF traffic in the "interior" nodes? Regards Shahram From owner-diffserv@optimus.ietf.org Thu Sep 30 23:10:56 1999 Received: from nsa-mail.us.newbridge.com ([209.58.11.226]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27152 for ; Thu, 30 Sep 1999 23:10:55 -0400 (EDT) Received: from nsa-gw1.us.newbridge.com (nsa-gw1 [209.58.11.225]) by nsa-mail.us.newbridge.com (8.9.3/8.9.3) with SMTP id XAA03067 for ; Thu, 30 Sep 1999 23:06:33 -0400 (EDT) Received: from herndon-mh1.us.newbridge.com by nsa-gw1.us.newbridge.com via smtpd (for nsa-mail.us.newbridge.com [209.58.11.226]) with SMTP; 1 Oct 1999 03:10:27 UT Received: from nsamail01.us.newbridge.com by herndon-mh1.us.newbridge.com with ESMTP for diffserv@ietf.org; Thu, 30 Sep 1999 23:10:26 -0400 Received: from newbridge.com ([138.120.232.243]) by nsamail01.us.newbridge.com (Netscape Messaging Server 3.6) with ESMTP id AAA5360 for ; Thu, 30 Sep 1999 23:12:54 -0400 Message-Id: <37F426ED.D00D4835@newbridge.com> Date: Thu, 30 Sep 1999 23:13:49 -0400 From: "Victor F Perez" Organization: Newbridge Networks -Ineternetworking Products Group X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: "diffserv@ietf.org" Subject: subscribe Content-Type: multipart/mixed; boundary="------------D7076F96C77FF8C84E5C8708" This is a multi-part message in MIME format. --------------D7076F96C77FF8C84E5C8708 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit subscribe --------------D7076F96C77FF8C84E5C8708 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Description: Card for Vic Perez Content-Disposition: attachment; filename="vcard.vcf" Content-Transfer-Encoding: 7bit begin: vcard fn: Vic Perez n: Perez;Vic org: Internetworking Products Group email;internet: vperez@newbridge.com title: Consulting Engineer tel;work: 703-736-5762 PSTN,740-5762 INT x-mozilla-cpt: ;0 x-mozilla-html: TRUE version: 2.1 end: vcard --------------D7076F96C77FF8C84E5C8708--