From mailnull@www1.ietf.org Fri May 2 12:33:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19887 for ; Fri, 2 May 2003 12:33:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h42GdeZ04845 for ieprep-archive@odin.ietf.org; Fri, 2 May 2003 12:39:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42Gdd804842 for ; Fri, 2 May 2003 12:39:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19869 for ; Fri, 2 May 2003 12:32:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BdUc-0005TR-00 for ieprep-web-archive@ietf.org; Fri, 02 May 2003 12:34:38 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BdUH-0005TB-00 for ieprep-web-archive@ietf.org; Fri, 02 May 2003 12:34:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42GbA804029; Fri, 2 May 2003 12:37:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42GaE803818 for ; Fri, 2 May 2003 12:36:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19708 for ; Fri, 2 May 2003 12:28:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BdR9-0005RW-00 for ieprep@ietf.org; Fri, 02 May 2003 12:31:03 -0400 Received: from mtahqs3.ncr.disa.mil ([164.117.144.157] helo=pfwhqs1.ncr.disa.mil) by ietf-mx with smtp (Exim 4.12) id 19BdR3-0005RD-00 for ieprep@ietf.org; Fri, 02 May 2003 12:30:57 -0400 Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 2 May 2003 16:22:38 UT Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19) id ; Fri, 2 May 2003 12:35:12 -0400 Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D02EF4E37@emshqs1.ncr.disa.mil> From: "Nguyen, An" To: "'ieprep@ietf.org'" Date: Fri, 2 May 2003 12:28:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Ieprep] FW: How does automated QoS work? Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , It looks like hardware vendors pay more attention to QoS. An -----Original Message----- From: NW on Wide Area Networking [mailto:WAN@bdcimail.com] Sent: Thursday, May 01, 2003 9:00 PM Today's focus: How does automated QoS work? By Steve Taylor and Joanie Wexler We mentioned last time that, as more and more application traffic (including voice) joins IP networks, the ability of enterprises to get their arms around quality-of-service provisioning and management is growing more important. Some of the router vendors, including Alcatel and Cisco, have begun automating this process for their switches and routers. Their early systems focus on voice over IP, for the obvious reason that VoIP is the most persnickety of applications in terms of latency and jitter. Alcatel announced automated QoS in the form of a network management feature called OneTouch last summer. OneTouch is a capability of the PolicyView module in Alcatel's OmniVista 2000 Version 2.0 network management software. It uses preconfigured QoS templates to enable network managers to configure QoS settings once, then distribute them across multiple, distributed switches, says John Reidy, a senior product manager at Alcatel Similarly, Cisco's AutoQoS feature, released earlier this year for Cisco switches - and last month, for use on most Cisco WAN edge routers - also uses templates to automate policy and QoS provisioning networkwide. Cisco routers support perhaps the industry's most exhaustive list of QoS features. But the company finally realized that the richer its portfolio of QoS features became, the more overwhelmed enterprises grew at the prospect of tackling QoS. According to Cisco, AutoQoS reduces the network manager's QoS provisioning tasks down to just three steps: configuring an IP address, specifying the amount of bandwidth on a link, and enabling the Cisco AutoQoS feature. The router maker says it has calculated that AutoQoS reduces the complexity, cost and time of QoS provisioning by two-thirds. The Alcatel and Cisco template-based automated QoS systems work in similar ways. Cisco AutoQoS, for example, detects the underlying network protocols and connection types. It identifies the application traffic on the network using the crown jewel in Cisco's QoS arsenal, a capability called Network Based Application Recognition, or NBAR. AutoQoS matches the autodiscovered network variables to a template that has the proper configuration settings to automatically invoke all the appropriate marking, classifying, queuing, and fragmenting parameters. In theory, this means you should no longer have to worry about how to group application traffic into service classes, figure out which link-layer protocols are running, and determine which specific QoS features to turn on and how to configure them for each service class. _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From mailnull@www1.ietf.org Fri May 2 13:01:53 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21065 for ; Fri, 2 May 2003 13:01:53 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h42H8TF07768 for ieprep-archive@odin.ietf.org; Fri, 2 May 2003 13:08:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42H8T807765 for ; Fri, 2 May 2003 13:08:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21056 for ; Fri, 2 May 2003 13:01:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Bdwa-0005nh-00 for ieprep-web-archive@ietf.org; Fri, 02 May 2003 13:03:32 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BdwZ-0005ne-00 for ieprep-web-archive@ietf.org; Fri, 02 May 2003 13:03:31 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42H6O806746; Fri, 2 May 2003 13:06:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42H5E806687 for ; Fri, 2 May 2003 13:05:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20959 for ; Fri, 2 May 2003 12:57:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BdtC-0005lc-00 for ieprep@ietf.org; Fri, 02 May 2003 13:00:02 -0400 Received: from gnat.inet.org ([63.108.254.91]) by ietf-mx with esmtp (Exim 4.12) id 19Bdt6-0005lW-00 for ieprep@ietf.org; Fri, 02 May 2003 12:59:56 -0400 Received: from extremenetworks.com (unknown [10.0.8.158]) by gnat.inet.org (Postfix) with ESMTP id F3B0867131; Fri, 2 May 2003 13:25:22 -0400 (EDT) Date: Fri, 2 May 2003 12:59:53 -0400 Subject: Re: [Ieprep] FW: How does automated QoS work? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: "'ieprep@ietf.org'" To: "Nguyen, An" From: RJ Atkinson In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D02EF4E37@emshqs1.ncr.disa.mil> Message-Id: <7EA34A7E-7CBF-11D7-BE3D-00039357A82A@extremenetworks.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Friday, May 2, 2003, at 12:28 America/Montreal, Nguyen, An wrote: > It looks like hardware vendors pay more attention to QoS. > > An Probably not. The products described are mostly application software "element manager" enhancements to make it easier for users to configure sets of switches, combined with some analysis of existing network traffic (in some cases). Many other vendors (e.g. Extreme, others) have had similar capabilities available commercially in products for years. Such tools can be useful if one has a single administrative domain and wants to deploy a domain-wide QoS policy to all the affected devices. However, they aren't a panacea -- and there is still no substitute for the operator of an administrative domain actually thinking about what QoS policies (if any) the operator wants to deploy. Example: An operator might have over-provisioned their entire enterprise, so doesn't want any QoS mechanisms enabled. This is pretty common with the advent of Gig Ethernet a few years back and now with 10 Gig E being widely available. Vendor-neutral surveys of enterprise/ISP operators indicate that only a very small percentage of networks have QoS enabled in any way. Example: One's network might have multimedia MBONE traffic, but that might not be the priority of the business that owns and operates the enterprise's network. In such a case, one might actually want to make such traffic lower priority, while application software might (quite reasonably) guess the opposite and configure higher priority for that traffic -- unless the operator intervenes. Note also that there is no new QoS mechanism mentioned. A likely scenario is that these are tools for configuring existing, standard, and widely implemented mechanisms -- for example 802.1p Ethernet precedence, IETF IP ToS, or IETF DiffServ, with industry-standard queuing/shaping disciplines such as WFQ, RED, or WRED. Regards, Ran rja@extremenetworks.com _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From mailnull@www1.ietf.org Fri May 2 19:17:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06922 for ; Fri, 2 May 2003 19:17:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h42NOT505856 for ieprep-archive@odin.ietf.org; Fri, 2 May 2003 19:24:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42NOT805853 for ; Fri, 2 May 2003 19:24:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06918 for ; Fri, 2 May 2003 19:17:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BjoK-0000w4-00 for ieprep-web-archive@ietf.org; Fri, 02 May 2003 19:19:24 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BjoJ-0000vz-00 for ieprep-web-archive@ietf.org; Fri, 02 May 2003 19:19:23 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42NLA805647; Fri, 2 May 2003 19:21:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42NIY805512 for ; Fri, 2 May 2003 19:18:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06725 for ; Fri, 2 May 2003 19:11:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BjiM-0000sZ-00 for ieprep@ietf.org; Fri, 02 May 2003 19:13:14 -0400 Received: from kc-msxproto2.kc.umkc.edu ([134.193.143.159]) by ietf-mx with esmtp (Exim 4.12) id 19BjiG-0000s1-00 for ieprep@ietf.org; Fri, 02 May 2003 19:13:08 -0400 Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329); Fri, 2 May 2003 18:12:38 -0500 x-mimeole: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Ieprep] FW: How does automated QoS work? Date: Fri, 2 May 2003 18:12:38 -0500 Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B02D0E7@KC-MAIL4.kc.umkc.edu> Thread-Topic: [Ieprep] FW: How does automated QoS work? Thread-Index: AcMQzJYAiIqwwrM/Rf+pSKrhL3mxBwAKkUaw From: "Ayyasamy, Senthilkumar (UMKC-Student)" To: "RJ Atkinson" , "Nguyen, An" Cc: X-OriginalArrivalTime: 02 May 2003 23:12:38.0738 (UTC) FILETIME=[530A9320:01C31100] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h42NK9805596 Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit >> It looks like hardware vendors pay more attention to QoS. >> >> An > >Probably not. The products described are mostly application >software "element manager" enhancements to make it easier >for users to configure sets of switches, combined with some >analysis of existing network traffic (in some cases). > >Many other vendors (e.g. Extreme, others) have had similar >capabilities available commercially in products for years. > >Such tools can be useful if one has a single administrative >domain and wants to deploy a domain-wide QoS policy to all >the affected devices. Lets not go into one more over-provisioning discussion. I am very much in agreement with you, seeing the good traffic stats from (i) sprintlabs - recently, they were concerned with the excess network BW which go waste. So, they simulated a scavenger traffic and proved that the legacy traffic is not affected even after adding the degraded service. (ii) AT&T labs - over-provisioning + TE at IP level by tweaking weights. If you notice the above two results, they dimension the network -using historic data and forecasting methods - such that their provisioning is sufficient. But, their are situation where the provisioning turn out to be counter-productive in an not-so-well-planned network[1]. Also, the availability (i.e. always above 80%) is an averaged out figure. Do providers maintain such availability all the time (even milli-second level)? I remember a heated discussion in nanog about selfish routing[2]. The bottom line is that their are few smart router vendors (like route science, sockye etc) which help us to find alternate best paths to the current SPF. +++ C&W do transport level traffic engineering in their backbone. My point is that: 1. Their are some alternatives to over-provisioning at the core (other than QoS): - Smart Routing techniques (like reactive routing) - Transport level TE by some providers like C&W So, we should still focus on core (not just access.) 2. Their is also interest in QoS products for enterprise and access networks (like std configuration methods auto-QoS etc.) So, we can standardize use of QoS techniques for ieprep in access/ enterprise networks. [1] Braess Paradox -- well known in transport networks. [2] but, the whole nanog discussion was based on a theoretical game theory paper on selfish Routing, which has no practical applicability. _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From mailnull@www1.ietf.org Sat May 3 16:52:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08719 for ; Sat, 3 May 2003 16:52:36 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h43Kxm007191 for ieprep-archive@odin.ietf.org; Sat, 3 May 2003 16:59:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h43Kxl807188 for ; Sat, 3 May 2003 16:59:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08679 for ; Sat, 3 May 2003 16:51:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19C415-00068E-00 for ieprep-web-archive@ietf.org; Sat, 03 May 2003 16:53:55 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19C40k-00067w-00 for ieprep-web-archive@ietf.org; Sat, 03 May 2003 16:53:34 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h43Kv1807071; Sat, 3 May 2003 16:57:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h43KrS806755 for ; Sat, 3 May 2003 16:53:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08623 for ; Sat, 3 May 2003 16:45:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19C3ux-000671-00 for ieprep@ietf.org; Sat, 03 May 2003 16:47:35 -0400 Received: from gnat.inet.org ([63.108.254.91]) by ietf-mx with esmtp (Exim 4.12) id 19C3uc-00066o-00 for ieprep@ietf.org; Sat, 03 May 2003 16:47:15 -0400 Received: from extremenetworks.com (unknown [10.0.8.87]) by gnat.inet.org (Postfix) with ESMTP id DC4AF67103; Sat, 3 May 2003 17:12:56 -0400 (EDT) Date: Sat, 3 May 2003 16:47:16 -0400 Subject: Re: [Ieprep] FW: How does automated QoS work? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: To: "Ayyasamy, Senthilkumar (UMKC-Student)" From: RJ Atkinson In-Reply-To: <5EF7D95E17BDAD4A968C812E5ABC390B02D0E7@KC-MAIL4.kc.umkc.edu> Message-Id: <6CF65580-7DA8-11D7-882D-00039357A82A@extremenetworks.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Friday, May 2, 2003, at 19:12 America/Montreal, Ayyasamy, Senthilkumar (UMKC-Student) wrote: > 2. Their is also interest in QoS products for enterprise > and access networks (like std configuration methods > auto-QoS etc.) Interest from NCS seems evident. I haven't seen any operators here express interest in the above. In any event, numerous commercial products are available today to any operator that chooses to use them. Standardised configuration mechanisms are being addressed in the (proposed) IETF NetConf WG and on the related xmlconf mailing list. > So, we can standardize use of QoS techniques for ieprep > in access/ enterprise networks. The standardisation of mechanisms has already been done for single administrative domain networks. IETF does not usually tell operators how to design their networks. Examples of existing mechanisms include (at least): - IETF DiffServ - IEEE 802.1p (later incorporated into 802.1d) Ethernet precedence - Classical IP Tos Given that, I'm not at all sure what you are proposing be undertaken here. Ran _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From mailnull@www1.ietf.org Mon May 5 12:51:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07639 for ; Mon, 5 May 2003 12:51:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45GxWn16621 for ieprep-archive@odin.ietf.org; Mon, 5 May 2003 12:59:32 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45GxW816618 for ; Mon, 5 May 2003 12:59:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07631 for ; Mon, 5 May 2003 12:50:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CjD6-0006zB-00 for ieprep-web-archive@ietf.org; Mon, 05 May 2003 12:53:04 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CjD5-0006z6-00 for ieprep-web-archive@ietf.org; Mon, 05 May 2003 12:53:03 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45GvO816533; Mon, 5 May 2003 12:57:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45GtL816458 for ; Mon, 5 May 2003 12:55:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07455 for ; Mon, 5 May 2003 12:46:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cj93-0006xi-00 for ieprep@ietf.org; Mon, 05 May 2003 12:48:53 -0400 Received: from web41803.mail.yahoo.com ([66.218.93.137]) by ietf-mx with smtp (Exim 4.12) id 19Cj8x-0006xC-00 for ieprep@ietf.org; Mon, 05 May 2003 12:48:47 -0400 Message-ID: <20030505164759.22085.qmail@web41803.mail.yahoo.com> Received: from [65.213.193.49] by web41803.mail.yahoo.com via HTTP; Mon, 05 May 2003 09:47:59 PDT Date: Mon, 5 May 2003 09:47:59 -0700 (PDT) From: CAITR Reply-To: info@caitr.org To: ieprep@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-584815438-1052153279=:21885" Subject: [Ieprep] Internetworking 2003: Call for Participation Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , --0-584815438-1052153279=:21885 Content-Type: text/plain; charset=us-ascii Internetworking 2003 International Conference Hilton San Jose & Towers Hotel, California June 22-June 24, 2003 http://www.caitr.org/internetworking03/index.htm You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials.Registration for the conference is underway. Please visit http://www.caitr.org/internetworking03/registration.htm and follow instructions for registration. The early registration discounts are extremely attractive and are valid till June 1, 2003.Important Dates: --------------------- - Early Registration Rates Cut-Off Date: Sept 30 - Tutorials: Oct 27, 1:00-6:00 pm - Conference sessions: October 28-29 8:30am-6:00pmProgram: ------------- (visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details)Sunday June 22 Tutorial-1: MPLS VPNs Tutorial-2: IPv6 Tutorial-3: Mobile Wireless Internet Architecture and Protocols Tutorial-4: Voice over Packet Monday June 23 Welcome and Keynote Session: Network Technology Trends - Forwarding Element and Control Separation - Evolution of Inter-Domain Routing - Network Processing Building Blocks: Enabling the Routers of the Future Session: Network Architecture - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6 - A new routing architecture: Atomised Routing - Internetworking MPLS Layer 2 Transport with an IP Services Network Session: Storage Area Networks - Storage as a Network Node - Object-Based Storage - Design, Implementation, and Performance Analysis of the iSCSI Protocol for SCSI over TCP/IP - SANs Considerations Session: Mobile & Wireless Networks - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6 - Challenges and Roadmap of UMTS Network Deployment - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS - Mobile Authentication and QoS - Mobile Handoff Technologies Tuesday June 24 Session: Inter-Domain Routing - Optimizing Route Convergence - Traceroute and BGP AS Path Incongruities - Domain Constrained Multicast: A New Approach for IP Multicast Routing Session: Applications & Services - Securing the Web with Next Generation Encryption Technologies - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21 - A novel EAC semantic for the RTSP protocol - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet Session: Network Management & Planning - Pseudowire OAM: A Mandatory Yet Often Overlooked Feature - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems - Design Of Fast Fault Restoration System For WDM Networks - Cross-domain multimedia service provisioning, the EVOLUTE solution Session: QoS Based Routing - QoS Routing in Networks with Non-Deterministic Information - Active Dynamic Routing - QoS routing for Differentiated Services: simulations and prototype experiments - Probabilistic routing for QoS improvement in GPS networks - Fluid flow network modeling for hop-by-hop feedback control design and analysis We look forward to seeing you at the Conference. Regards, Conference Technical Co-chairs: - Dr. Maurice Gagnaire, ENST, France - Daniel Awduche Technical Program Committee of the Internetworking 2003 Conference: - Roberto Sabella, Erisson - Dr. Moshe Zukerman, Univ. of Melbourne - Nada Golmie, NIST - Dr. Guy Pujolle, LIP6, France - Dr. Samir Tohme, ENST, France - Stefano Trumpy, Italian National Research Council - Dr. Ibrahim Habib, City Univ. of NY - Dr. Marc Lobelle, UCL University, Belgium - Dr. Parviz Yegani, Cisco Systems - Dr. G.S. Kuo - Dr. Abbas Jamalipour, Univ. of Sydney - Dr. Hussein Mouftah, Univ. of Ottawa - James Kempf - Elizabeth Rodriguez - Dr. Ferit Yegenoglu, Isocore - Dr. Ali Zadeh, George Mason University - Dr. Tony Przygienda, Xebeo - Ran Canetti, IBM --0-584815438-1052153279=:21885 Content-Type: text/html; charset=us-ascii
     Internetworking 2003 International Conference
     Hilton San Jose & Towers Hotel, California
              June 22-June 24, 2003
    http://www.caitr.org/internetworking03/index.htm
  
You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials.
Registration for the conference is underway. Please visit http://www.caitr.org/internetworking03/registration.htm and follow instructions for registration. The early registration discounts are extremely attractive and are valid till June 1, 2003.
Important Dates:
---------------------
- Early Registration Rates Cut-Off Date: Sept 30
- Tutorials: Oct 27, 1:00-6:00 pm
- Conference sessions: October 28-29 8:30am-6:00pm
Program:
-------------
(visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details)
Sunday June 22
    Tutorial-1: MPLS VPNs 
    Tutorial-2: IPv6 
    Tutorial-3: Mobile Wireless Internet Architecture and Protocols
    Tutorial-4: Voice over Packet 
Monday June 23
    Welcome and Keynote 
    Session: Network Technology Trends
      - Forwarding Element and Control Separation
      - Evolution of Inter-Domain Routing
      - Network Processing Building Blocks: Enabling the Routers of the Future
    Session: Network Architecture
      - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6
      - A new routing architecture: Atomised Routing
      - Internetworking MPLS Layer 2 Transport with an IP Services Network
    Session: Storage Area Networks
      - Storage as a Network Node
      - Object-Based Storage
      - Design, Implementation, and ! Performance Analysis of the iSCSI Protocol for SCSI over TCP/IP
      - SANs Considerations
 
    Session: Mobile & Wireless Networks
      - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6
      - Challenges and Roadmap of UMTS Network Deployment
      - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS 
      - Mobile Authentication and QoS 
      - Mobile Handoff Technologies 
Tuesday June 24
    Session: Inter-Domain Routing
      - Optimizing Route Convergence
      - Traceroute and BGP AS Path Incongruities 
      - Domain Constrained Multicast: A New Approach for IP Multicast Routing
 
    Session: Applications & Services
     -  Securing the Web with Next Generation Encryption Technologies
     - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21
     - A novel EAC semantic for the RTSP protocol
     - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet
 
    Session: Network Management & Planning
     -  Pseudowire OAM: A Mandatory Ye! t Often Overlooked Feature 
     - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems
     - Design Of Fast Fault Restoration System For WDM Networks
     - Cross-domain multimedia service provisioning, the EVOLUTE solution
 
    Session: QoS Based Routing
     - QoS Routing in Networks with Non-Deterministic Information
     - Active Dynamic Routing
     - QoS routing for Differentiated Services: simulations and prototype experiments
     - Probabilistic routing for QoS improvement in GPS networks
     - Fluid flow network modeling for hop-by-hop feedback control design and analysis
 
We look forward to seeing you at the Conference.
Regards,
 Conference Technical Co-chai! rs:
 - Dr. Maurice Gagnaire, ENST, France
 - Daniel Awduche
 Technical Program Committee of the Internetworking 2003 Conference:
 - Roberto Sabella, Erisson
 - Dr. Moshe Zukerman, Univ. of Melbourne
 - Nada Golmie, NIST
 - Dr. Guy Pujolle, LIP6, France
 - Dr. Samir Tohme, ENST, France
 - Stefano Trumpy, Italian National Research Council
 - Dr. Ibrahim Habib, City Univ. of NY
 - Dr. Marc Lobelle, UCL University, Belgium
 - Dr. Parviz Yegani, Cisco Systems
 - Dr. G.S. Kuo
 - Dr. Abbas Jamalipour, Univ. of Sydney
 - Dr. Hussein Mouftah, Univ. of Ottawa
 - James Kempf
 - Elizabeth Rodriguez
 - Dr. Ferit Yegenoglu, Isocore
 - Dr. Ali Zadeh, George Mason University
 - Dr. Tony Przygienda, Xebeo
 - Ran Canetti, IBM

 
--0-584815438-1052153279=:21885-- _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From mailnull@www1.ietf.org Mon May 12 07:04:16 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07969 for ; Mon, 12 May 2003 07:04:16 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CATki15647 for ieprep-archive@odin.ietf.org; Mon, 12 May 2003 06:29:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CATkB15644 for ; Mon, 12 May 2003 06:29:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07966 for ; Mon, 12 May 2003 07:03:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FB7o-0006q4-00 for ieprep-web-archive@ietf.org; Mon, 12 May 2003 07:05:45 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FB7o-0006q0-00 for ieprep-web-archive@ietf.org; Mon, 12 May 2003 07:05:44 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CASDB15553; Mon, 12 May 2003 06:28:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CARtB15536 for ; Mon, 12 May 2003 06:27:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07929 for ; Mon, 12 May 2003 07:01:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FB61-0006p8-00 for ieprep@ietf.org; Mon, 12 May 2003 07:03:53 -0400 Received: from mclmx.mail.saic.com ([149.8.64.10]) by ietf-mx with esmtp (Exim 4.12) id 19FB61-0006p5-00 for ieprep@ietf.org; Mon, 12 May 2003 07:03:53 -0400 Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Mon, 12 May 2003 07:03:22 -0400 Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12]) by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.21) with SMTP id M2003051207045523632 for ; Mon, 12 May 2003 07:04:55 -0400 Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 May 2003 07:04:25 -0400 Message-Id: From: "King, Kimberly S." To: "Ieprep (E-mail)" Date: Mon, 12 May 2003 07:04:52 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Ieprep] converse of "money talks"? Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , "Wireless priority access phones being returned due to budget woes May 07, 2003 1:21 PM EST ARLINGTON, Va.-Since the National Communications System no longer pays for wireless priority access service, some phones are being returned because agencies can no longer afford them, said the NCS's Kathy Blasco on Wednesday at a meeting of the Telecommunications Service Priority System Oversight Committee. States and localities are saying, "It's this (wireless priority access) or we put gas in the police cars," said Blasco. " more at http://www.rcrnews.com/cgi-bin/news.pl?newsId=8479 _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From mailnull@www1.ietf.org Mon May 19 06:15:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14017 for ; Mon, 19 May 2003 06:15:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4J9hDG02243 for ieprep-archive@odin.ietf.org; Mon, 19 May 2003 05:43:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9hDB02240 for ; Mon, 19 May 2003 05:43:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13963 for ; Mon, 19 May 2003 06:13:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19HhgA-0001XT-00 for ieprep-web-archive@ietf.org; Mon, 19 May 2003 06:15:38 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Hhg9-0001XP-00 for ieprep-web-archive@ietf.org; Mon, 19 May 2003 06:15:37 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9fJB02105; Mon, 19 May 2003 05:41:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9eeB02055 for ; Mon, 19 May 2003 05:40:40 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13669; Mon, 19 May 2003 06:11:16 -0400 (EDT) Message-Id: <200305191011.GAA13669@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ieprep@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 19 May 2003 06:11:16 -0400 Subject: [Ieprep] I-D ACTION:draft-polk-ieprep-flow-model-considerations-01.txt Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Considerations for IEPREP Related Protocol Packet Flow Models Author(s) : J. Polk Filename : draft-polk-ieprep-flow-model-considerations-01.txt Pages : 11 Date : 2003-5-16 This document diagrams the packet flows - both signaling and data - of Internet Emergency Preparedness (IEPREP) related protocols. This document serves as a point of reference for the WG when discussing which QoS mechanisms can be employed for each individual (application) protocol packet flow to function properly during congestion events from IP source to IP destination, as well as a potentially different QOS mechanism for a related but separate data flow (if present). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-polk-ieprep-flow-model-considerations-01.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-polk-ieprep-flow-model-considerations-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-polk-ieprep-flow-model-considerations-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-5-16151507.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-polk-ieprep-flow-model-considerations-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-polk-ieprep-flow-model-considerations-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-16151507.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep From mailnull@www1.ietf.org Tue May 20 10:33:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15768 for ; Tue, 20 May 2003 10:33:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KE3Bb03958 for ieprep-archive@odin.ietf.org; Tue, 20 May 2003 10:03:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KE3BB03954 for ; Tue, 20 May 2003 10:03:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15758 for ; Tue, 20 May 2003 10:33:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I8Ci-0005hJ-00 for ieprep-web-archive@ietf.org; Tue, 20 May 2003 10:35:00 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19I8Ch-0005hD-00 for ieprep-web-archive@ietf.org; Tue, 20 May 2003 10:34:59 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KE1RB03857; Tue, 20 May 2003 10:01:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KE03B03708 for ; Tue, 20 May 2003 10:00:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15575 for ; Tue, 20 May 2003 10:30:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I89g-0005fd-00 for ieprep@ietf.org; Tue, 20 May 2003 10:31:52 -0400 Received: from mclmx.mail.saic.com ([149.8.64.10]) by ietf-mx with esmtp (Exim 4.12) id 19I89f-0005fZ-00 for ieprep@ietf.org; Tue, 20 May 2003 10:31:51 -0400 Received: from mcl-its-ieg02.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Tue, 20 May 2003 10:31:30 -0400 Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12]) by mcl-its-ieg02.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003052010345410927 ; Tue, 20 May 2003 10:34:54 -0400 Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19) id ; Tue, 20 May 2003 10:32:35 -0400 Message-Id: From: "King, Kimberly S." To: "Ieprep (E-mail)" Cc: "'Scott Bradner ' (E-mail)" Date: Tue, 20 May 2003 10:33:04 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Ieprep] IEPREP Related Protocol Packet Flow -- WGLC Sender: ieprep-admin@ietf.org Errors-To: ieprep-admin@ietf.org X-BeenThere: ieprep@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet Emergency Preparedness Working Group List-Post: List-Help: List-Subscribe: , This message announces WG last call for "Considerations for IEPREP Related Protocol Packet Flow Models" draft-polk-ieprep-flow-model-considerations-01.txt The intent is for this draft to have informational RFC status. The cut-off date for WG last call is June 3, 2003. _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep m: ieprep-admin@ietf.org [mailto:ieprep-admin@ietf.org] On Behalf Of King, Kimberly S. Sent: Tuesday, May 20, 2003 10:33 AM To: Ieprep (E-mail) Cc: 'Scott Bradner ' (E-mail) Subject: [Ieprep] IEPREP Related Protocol Packet Flow -- WGLC This message announces WG last call for "Considerations for IEPREP Related Protocol Packet Flow Models" draft-polk-ieprep-flow-model-considerations-01.txt The intent is for this draft to have informational RFC status. The cut-off date for WG last call is June 3, 2003. _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep