From owner-forces@PEACH.EASE.LSOFT.COM Wed Sep 11 08:11:33 2002 Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05554 for ; Wed, 11 Sep 2002 08:11:33 -0400 (EDT) Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <13.00714F9B@cherry.ease.lsoft.com>; Wed, 11 Sep 2002 8:13:13 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 27210840 for FORCES@PEACH.EASE.LSOFT.COM; Wed, 11 Sep 2002 08:13:12 -0400 Received: from 132.151.1.176 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 11 Sep 2002 08:03:12 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05145; Wed, 11 Sep 2002 08:01:31 -0400 (EDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Approved-By: nsyracus@CNRI.RESTON.VA.US Message-ID: <200209111201.IAA05145@ietf.org> Date: Wed, 11 Sep 2002 08:01:31 -0400 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-forces-framework-01.txt To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF. Title : ForCES Architectural Framework Author(s) : L. Yang et al. Filename : draft-ietf-forces-framework-01.txt Pages : 23 Date : 2002-9-10 This document defines the architectural framework for ForCES network elements (NE), and identifies the associated entities and the interaction among them. This framework is intended to satisfy the requirements specified in the ForCES requirements draft [FORCES- REQ]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-forces-framework-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-ietf-forces-framework-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-ietf-forces-framework-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: <2002-9-10153710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-forces-framework-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-forces-framework-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-9-10153710.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-forces@PEACH.EASE.LSOFT.COM Wed Sep 11 13:21:40 2002 Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17545 for ; Wed, 11 Sep 2002 13:21:40 -0400 (EDT) Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <13.00715B68@cherry.ease.lsoft.com>; Wed, 11 Sep 2002 13:23:17 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 27230050 for FORCES@PEACH.EASE.LSOFT.COM; Wed, 11 Sep 2002 13:23:16 -0400 Received: from 143.182.124.5 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 11 Sep 2002 13:23:15 -0400 Received: from fmsmsxvs043.fm.intel.com (fmsmsxvs043.fm.intel.com [132.233.42.129]) by petasus.ch.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.43 2002/08/30 20:06:11 dmccart Exp $) with SMTP id g8BHP6k16599 for ; Wed, 11 Sep 2002 17:25:06 GMT Received: from fmsmsx29.FM.INTEL.COM ([132.233.42.29]) by fmsmsxvs043.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091110214112991 for ; Wed, 11 Sep 2002 10:21:41 -0700 Received: by fmsmsx29.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 11 Sep 2002 10:23:12 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C259B7.E31BC390" Approved-By: "Yang, Lily L" Message-ID: Date: Wed, 11 Sep 2002 10:23:04 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "Yang, Lily L" Subject: FW: I-D ACTION:draft-ietf-forces-framework-01.txt To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C259B7.E31BC390 Content-Type: text/plain; charset="iso-8859-1" The changes occured in this revision of the ForCES framework document are mostly minor except in Section 6 (Applicability to RFC1812). There are some editorial revision throughout the document, and important correction to a few cross reference errors. The technical comments we got since last revision are mostly concerning Section 6. There are questions like where ARP should be done (CE or FE), where ICMP error messages are generated etc. To calrify on this, a general guideline is added in this section (more specifically, in 6.2): "...ARP support may be implemented in either CEs or FEs. As we will see later, a number of behaviors that RFC1812 mandates fall into this category -- they may be performed by the FE and may be performed by the CE. A general guideline is needed to ensure interoperability between separated control and forwarding planes. The guideline we offer here is that CEs are required to be capable of these operations while FEs may or may not choose to implement them. FE model should indicate its capabilities in this regard. " Some clarification along this line is also made in section 6.3 regarding IP options like source route, record route, time stamp, etc. There was also a error in previous revision regarding forwarding tables in multiple FEs. That was also corrected in this revision. Once again, we would like to thank all the people that have provided comments to us. We would like to ask you to take one more look at the document, esp. Section 6 and provide feedback. Thanks, Lily -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, September 11, 2002 5:02 AM To: FORCES@PEACH.EASE.LSOFT.COM Subject: I-D ACTION:draft-ietf-forces-framework-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF. Title : ForCES Architectural Framework Author(s) : L. Yang et al. Filename : draft-ietf-forces-framework-01.txt Pages : 23 Date : 2002-9-10 This document defines the architectural framework for ForCES network elements (NE), and identifies the associated entities and the interaction among them. This framework is intended to satisfy the requirements specified in the ForCES requirements draft [FORCES- REQ]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-forces-framework-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-ietf-forces-framework-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-ietf-forces-framework-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_000_01C259B7.E31BC390 Content-Type: message/rfc822 To: Subject: Date: Wed, 11 Sep 2002 10:23:12 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C259B7.E31BC390" ------_=_NextPart_002_01C259B7.E31BC390 Content-Type: text/plain ------_=_NextPart_002_01C259B7.E31BC390 Content-Type: application/octet-stream; name="ATT43074.txt" Content-Disposition: attachment; filename="ATT43074.txt" Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-9-10153710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-forces-framework-01.txt ------_=_NextPart_002_01C259B7.E31BC390 Content-Type: message/external-body; site="internet-drafts"; dir="draft-ietf-forces-framework-01.txt"; mode="ftp.ietf.org"; access-type="anon-ftp" ------_=_NextPart_002_01C259B7.E31BC390-- ------_=_NextPart_000_01C259B7.E31BC390-- From owner-forces@PEACH.EASE.LSOFT.COM Thu Sep 12 20:44:25 2002 Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11959 for ; Thu, 12 Sep 2002 20:44:25 -0400 (EDT) Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <5.00719895@cherry.ease.lsoft.com>; Thu, 12 Sep 2002 20:46:05 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 27359735 for FORCES@PEACH.EASE.LSOFT.COM; Thu, 12 Sep 2002 20:46:05 -0400 Received: from 66.122.42.228 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 12 Sep 2002 20:46:04 -0400 Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com (Content Technologies SMTPRS 2.0.15) with SMTP id for ; Thu, 12 Sep 2002 17:45:27 -0700 Received: from TSRIDHAR (adsl-66-122-42-230.futsoft.com [66.122.42.230]) by sanjose.futsoft.com (8.9.3/8.8.7) with SMTP id QAA10554 for ; Thu, 12 Sep 2002 16:22:46 -0700 MIME-Version: 1.0 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 V6.00.2600.0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Approved-By: "T. Sridhar" Message-ID: Date: Thu, 12 Sep 2002 17:46:07 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "T. Sridhar" Subject: Re: I-D ACTION:draft-ietf-forces-framework-01.txt To: FORCES@PEACH.EASE.LSOFT.COM In-Reply-To: Precedence: list Content-Transfer-Encoding: 7bit Lily, I have some minor comments/suggestions on the document - can I call you up to discuss them? Regards, Sridhar -----Original Message----- From: Forwarding and Control Element Separation [mailto:FORCES@peach.ease.lsoft.com]On Behalf Of Yang, Lily L Sent: Wednesday, September 11, 2002 10:23 AM To: FORCES@peach.ease.lsoft.com Subject: FW: I-D ACTION:draft-ietf-forces-framework-01.txt The changes occured in this revision of the ForCES framework document are mostly minor except in Section 6 (Applicability to RFC1812). There are some editorial revision throughout the document, and important correction to a few cross reference errors. The technical comments we got since last revision are mostly concerning Section 6. There are questions like where ARP should be done (CE or FE), where ICMP error messages are generated etc. To calrify on this, a general guideline is added in this section (more specifically, in 6.2): "...ARP support may be implemented in either CEs or FEs. As we will see later, a number of behaviors that RFC1812 mandates fall into this category -- they may be performed by the FE and may be performed by the CE. A general guideline is needed to ensure interoperability between separated control and forwarding planes. The guideline we offer here is that CEs are required to be capable of these operations while FEs may or may not choose to implement them. FE model should indicate its capabilities in this regard. " Some clarification along this line is also made in section 6.3 regarding IP options like source route, record route, time stamp, etc. There was also a error in previous revision regarding forwarding tables in multiple FEs. That was also corrected in this revision. Once again, we would like to thank all the people that have provided comments to us. We would like to ask you to take one more look at the document, esp. Section 6 and provide feedback. Thanks, Lily -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, September 11, 2002 5:02 AM To: FORCES@PEACH.EASE.LSOFT.COM Subject: I-D ACTION:draft-ietf-forces-framework-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF. Title : ForCES Architectural Framework Author(s) : L. Yang et al. Filename : draft-ietf-forces-framework-01.txt Pages : 23 Date : 2002-9-10 This document defines the architectural framework for ForCES network elements (NE), and identifies the associated entities and the interaction among them. This framework is intended to satisfy the requirements specified in the ForCES requirements draft [FORCES- REQ]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-forces-framework-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-ietf-forces-framework-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-ietf-forces-framework-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. From owner-forces@PEACH.EASE.LSOFT.COM Fri Sep 13 12:51:55 2002 Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12048 for ; Fri, 13 Sep 2002 12:51:55 -0400 (EDT) Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <2.0071B8CA@cherry.ease.lsoft.com>; Fri, 13 Sep 2002 12:53:37 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 27401997 for FORCES@PEACH.EASE.LSOFT.COM; Fri, 13 Sep 2002 12:53:29 -0400 Received: from 143.183.121.6 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Fri, 13 Sep 2002 12:53:29 -0400 Received: from petasus.sc.intel.com (petasus.sc.intel.com [10.3.253.4]) by caduceus.sc.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.50 2002/08/30 20:04:57 dmccart Exp $) with ESMTP id g8DGqhK11552 for ; Fri, 13 Sep 2002 16:52:43 GMT Received: from fmsmsxvs042.fm.intel.com (fmsmsxvs042.fm.intel.com [132.233.42.128]) by petasus.sc.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.24 2002/08/30 20:04:21 dmccart Exp $) with SMTP id g8DGqwN10931 for ; Fri, 13 Sep 2002 16:52:58 GMT Received: from fmsmsx26.fm.intel.com ([132.233.42.26]) by fmsmsxvs042.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091309551117246 for ; Fri, 13 Sep 2002 09:55:11 -0700 Received: by fmsmsx26.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 13 Sep 2002 09:53:28 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Approved-By: "Yang, Lily L" Message-ID: Date: Fri, 13 Sep 2002 09:53:18 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "Yang, Lily L" Subject: Re: I-D ACTION:draft-ietf-forces-framework-01.txt To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list Sridhar -- Sure. Here is my number at my office (503)264-8813. I have meetings this morning. I should be around after 1:30 this afternoon. Thanks, Lily -----Original Message----- From: T. Sridhar [mailto:sridhar@futsoft.com] Sent: Thursday, September 12, 2002 5:46 PM To: FORCES@PEACH.EASE.LSOFT.COM Subject: Re: I-D ACTION:draft-ietf-forces-framework-01.txt Lily, I have some minor comments/suggestions on the document - can I call you up to discuss them? Regards, Sridhar -----Original Message----- From: Forwarding and Control Element Separation [mailto:FORCES@peach.ease.lsoft.com]On Behalf Of Yang, Lily L Sent: Wednesday, September 11, 2002 10:23 AM To: FORCES@peach.ease.lsoft.com Subject: FW: I-D ACTION:draft-ietf-forces-framework-01.txt The changes occured in this revision of the ForCES framework document are mostly minor except in Section 6 (Applicability to RFC1812). There are some editorial revision throughout the document, and important correction to a few cross reference errors. The technical comments we got since last revision are mostly concerning Section 6. There are questions like where ARP should be done (CE or FE), where ICMP error messages are generated etc. To calrify on this, a general guideline is added in this section (more specifically, in 6.2): "...ARP support may be implemented in either CEs or FEs. As we will see later, a number of behaviors that RFC1812 mandates fall into this category -- they may be performed by the FE and may be performed by the CE. A general guideline is needed to ensure interoperability between separated control and forwarding planes. The guideline we offer here is that CEs are required to be capable of these operations while FEs may or may not choose to implement them. FE model should indicate its capabilities in this regard. " Some clarification along this line is also made in section 6.3 regarding IP options like source route, record route, time stamp, etc. There was also a error in previous revision regarding forwarding tables in multiple FEs. That was also corrected in this revision. Once again, we would like to thank all the people that have provided comments to us. We would like to ask you to take one more look at the document, esp. Section 6 and provide feedback. Thanks, Lily -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, September 11, 2002 5:02 AM To: FORCES@PEACH.EASE.LSOFT.COM Subject: I-D ACTION:draft-ietf-forces-framework-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF. Title : ForCES Architectural Framework Author(s) : L. Yang et al. Filename : draft-ietf-forces-framework-01.txt Pages : 23 Date : 2002-9-10 This document defines the architectural framework for ForCES network elements (NE), and identifies the associated entities and the interaction among them. This framework is intended to satisfy the requirements specified in the ForCES requirements draft [FORCES- REQ]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-forces-framework-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-ietf-forces-framework-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-ietf-forces-framework-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. From owner-forces@PEACH.EASE.LSOFT.COM Wed Sep 18 08:22:12 2002 Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09980 for ; Wed, 18 Sep 2002 08:22:11 -0400 (EDT) Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <21.00725ED8@cherry.ease.lsoft.com>; Wed, 18 Sep 2002 8:23:56 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 27712717 for FORCES@PEACH.EASE.LSOFT.COM; Wed, 18 Sep 2002 08:23:56 -0400 Received: from 134.134.136.7 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 18 Sep 2002 08:23:55 -0400 Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6]) by caduceus.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.50 2002/08/30 20:04:57 dmccart Exp $) with ESMTP id g8ICLiA27008 for ; Wed, 18 Sep 2002 12:21:44 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by petasus.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.24 2002/08/30 20:04:21 dmccart Exp $) with SMTP id g8ICLIc21678 for ; Wed, 18 Sep 2002 12:21:18 GMT Received: from orsmsx26.jf.intel.com ([192.168.65.26]) by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091805262131462 for ; Wed, 18 Sep 2002 05:26:21 -0700 Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 18 Sep 2002 05:23:54 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Approved-By: "Putzolu, David" Message-ID: Date: Wed, 18 Sep 2002 05:23:51 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "Putzolu, David" Subject: Fwd: CFP for IEEE Network Magazine -- Special Issues on Network P rocessors: Architectures, Tools and Applications To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list Forwarded as relevant to list content. -----Original Message----- Our apologies if you receive multiple copies of this CFP. CALL FOR PAPERS IEEE Network Magazine Special Issue on Network Processors: Architectures, Tools, and Applications Guest Editors: Raj Yavatkar Prof. Harrick Vin Intel Corporation Department of Computer Sciences 2111 NE 25th Avenue, JF3-462 University of Texas at Austin Hillsboro, OR, 97124 Austin, TX 78712-1188 raj.yavatkar@intel.com vin@cs.utexas.edu Tel: (503) 264 9077 Tel: (512) 471-9732 Scope: The rapid and pervasive evolution of the Internet has created an insatiable need for supporting sophisticated services and high bandwidth at both edges of the network and within the network infrastructure. Traditionally, telecom and datacom equipment vendors have used fixed-function ASICs to implement packet-processing functions in hardware. However, such ASICs provide little flexibility when the type or nature of the media interfaces change or new protocol standards require changes to lookup operations or header processing. To meet the demand for higher performance, flexibility, and economy, an alternative to ASICs, called network processors (NPs), has emerged. These processors are programmable and their designs are optimized for processing packets; they can be used to implement efficiently a wide range of network services such as IP datagram forwarding, label switching, content-based routing, voice-over-packet, VPNs, and Quality of Service (QoS). We use the term network processor here in a generic sense to represent devices ranging from task-specific processors, such as classification and encryption engines, to more general-purpose, programmable packet or communications processors. Because many of these NPs are programmable, they offer a significant advantage over ASICs as new features or functions can be introduced or modified easily without having to re-design a network component. Design and development of networking systems using network processors is an emerging field that offers numerous challenges and opportunities. The goal of this special issue is to publish contributions from both industry and academia that describe the state-of-the-art in the architecture, design, programming, software tools, and use of network processors. Papers with tutorial/survey content are also welcome. Topics of particular interest include (but are not limited to): Architectures for network processors Novel product designs based on NPs Co-processors for search/lookup, packet classification, compression, encryption and security, etc. Design and implementation of new techniques/algorithms for QoS, voice-over-packet, wireless communication, etc Programming languages, tools, and development environments for software development on NPs Benchmarking and performance analysis Interfaces to high-speed packet buses and switch fabrics Techniques for accelerating network services Performance measurement and analysis Novel applications made possible by NPs Submission Guidelines: Interested authors should submit an electronic version of the manuscript either in Postscript or PDF format as an email attachment to one of the guest editors. Additional information including "Guidelines for authors" is available at the IEEE Network Website: http://www.comsoc.org/pubs/net/ntwrk/authors.html Important Dates: Paper Submission Deadline: October 30, 2002 Feedback to Authors: February 1, 2003 Final Manuscripts to Publisher: April 1, 2003 Publication of Special Issue: July 2003