From owner-forces@PEACH.EASE.LSOFT.COM Tue Jul 2 06:40:30 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 GAA02217 for ; Tue, 2 Jul 2002 06:40:30 -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 <17.00679CEB@cherry.ease.lsoft.com>; Tue, 2 Jul 2002 6:41:17 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 21916162 for FORCES@PEACH.EASE.LSOFT.COM; Tue, 2 Jul 2002 06:41:16 -0400 Received: from 132.151.1.176 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Tue, 2 Jul 2002 06:31:16 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00919; Tue, 2 Jul 2002 06:30:27 -0400 (EDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Approved-By: nsyracus@CNRI.RESTON.VA.US Message-ID: <200207021030.GAA00919@ietf.org> Date: Tue, 2 Jul 2002 06:30:27 -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-requirements-04.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 : Requirements for Separation of IP Control and Forwarding Author(s) : T. Anderson et al. Filename : draft-ietf-forces-requirements-04.txt Pages : 15 Date : 01-Jul-02 This document introduces the ForCES architecture and defines a set of associated terminology. This document also defines a set of architectural, modeling, and protocol requirements to logically separate the control and data forwarding planes of an IP (IPv4, IPv6, etc.) networking device. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-forces-requirements-04.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-requirements-04.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-requirements-04.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: <20020701151843.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-forces-requirements-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-forces-requirements-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020701151843.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-forces@PEACH.EASE.LSOFT.COM Wed Jul 3 16:03:36 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 QAA03784 for ; Wed, 3 Jul 2002 16:03:32 -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 <0.0067D625@cherry.ease.lsoft.com>; Wed, 3 Jul 2002 16:04:19 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 22060103 for FORCES@PEACH.EASE.LSOFT.COM; Wed, 3 Jul 2002 16:04:17 -0400 Received: from 134.134.214.21 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 3 Jul 2002 16:04:17 -0400 Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by pallas.or.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.42 2002/05/23 22:21:11 root Exp $) with SMTP id g63K4Gj05579 for ; Wed, 3 Jul 2002 20:04:16 GMT Received: from orsmsx26.jf.intel.com ([192.168.65.26]) by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2002070313042331195 for ; Wed, 03 Jul 2002 13:04:23 -0700 Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 3 Jul 2002 13:04:16 -0700 Importance: high X-Priority: 1 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, 3 Jul 2002 13:04:15 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "Putzolu, David" Subject: ForCES Requirements Last Call - ends 07/15/2002 To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list All, The ForCES requirements design team has just uploaded a new version that incorporates the feedback received during the previous last call. This email begins a second last call for the ForCES requirements document, which will end on July 15. Please send to the list any suggested changes and/or recommendations as to whether this document is ready to progress. Thanks, David & Patrick > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Tuesday, July 02, 2002 3:30 AM > Cc: forces@peach.ease.lsoft.com > Subject: I-D ACTION:draft-ietf-forces-requirements-04.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 : Requirements for Separation of IP Control and > Forwarding > Author(s) : T. Anderson et al. > Filename : draft-ietf-forces-requirements-04.txt > Pages : 15 > Date : 01-Jul-02 > > This document introduces the ForCES architecture and defines a set > of associated terminology. This document also defines a set of > architectural, modeling, and protocol requirements to logically > separate the control and data forwarding planes of an IP (IPv4, > IPv6, etc.) networking device. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-forces-requirem ents-04.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-requirements-04.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-requirements-04.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 Jul 3 16:25:02 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 QAA04967 for ; Wed, 3 Jul 2002 16:25:01 -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 <23.0067D5D5@cherry.ease.lsoft.com>; Wed, 3 Jul 2002 16:25:41 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 22060794 for FORCES@PEACH.EASE.LSOFT.COM; Wed, 3 Jul 2002 16:25:38 -0400 Received: from 143.182.246.25 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 3 Jul 2002 16:25:37 -0400 Received: from fmsmsxvs042.fm.intel.com (fmsmsxvs042.fm.intel.com [132.233.42.128]) by melete.ch.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.42 2002/05/23 22:21:11 root Exp $) with SMTP id g63KPaZ01995 for ; Wed, 3 Jul 2002 20:25:36 GMT Received: from fmsmsx29.FM.INTEL.COM ([132.233.42.29]) by fmsmsxvs042.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002070313261000081 for ; Wed, 03 Jul 2002 13:26:10 -0700 Received: by fmsmsx29.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 3 Jul 2002 13:25:36 -0700 Importance: high X-Priority: 1 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, 3 Jul 2002 13:25:35 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "Putzolu, David" Subject: ForCES Netlink Information Draft Last Call - ends 07/15/2002 To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list All, The ForCES Netlink Informational Draft has just had a new version uploaded and the authors have requested working group last call. This email begins a last call for the ForCES Netlink Informational Draft document, which will end on July 15. Please send to the list any suggested changes and/or recommendations as to whether this document is ready to progress. Thanks, David & Patrick > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Monday, June 10, 2002 4:16 AM > To: FORCES@PEACH.EASE.LSOFT.COM > Subject: [FORCES] I-D ACTION:draft-ietf-forces-netlink-03.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 : Netlink as an IP Services Protocol > Author(s) : J. Salim et al. > Filename : draft-ietf-forces-netlink-03.txt > Pages : 34 > Date : 07-Jun-02 > > This document describes Linux Netlink, which is used in Linux > both as an intra-kernel messaging system as well as between > kernel and user space. This document is intended as > informational in the con- text of prior art for the ForCES > IETF working group. The focus of this document is to > describe Netlink from a perspective of a protocol between a > Forwarding Engine Component (FEC) and a Control Plane > Component (CPC), the two components that define an IP > service. The document ignores the ability of Netlink as a > intra-kernel mes- saging system, as an inter-process > communication scheme (IPC), or as a configuration tool for > other non-networking or non-IP network services (such as > decnet, etc.). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-forces-netlink-03.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-netlink-03.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-netlink-03.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 Tue Jul 9 07:11:38 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 HAA19384 for ; Tue, 9 Jul 2002 07:11:38 -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 <8.00686E25@cherry.ease.lsoft.com>; Tue, 9 Jul 2002 7:12:29 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 22385992 for FORCES@PEACH.EASE.LSOFT.COM; Tue, 9 Jul 2002 07:12:28 -0400 Received: from 195.212.91.199 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Tue, 9 Jul 2002 07:12:28 -0400 Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23]) by d12lmsgate.de.ibm.com (8.12.3/8.12.3) with ESMTP id g69BCPIB050722 for ; Tue, 9 Jul 2002 13:12:26 +0200 Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140]) by d12relay02.de.ibm.com (8.11.1m3/NCO/VER6.2) with SMTP id g69BCPC130276 for ; Tue, 9 Jul 2002 13:12:25 +0200 Received: from dhcp70-7.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA67016 from ; Tue, 9 Jul 2002 13:12:24 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Approved-By: Patrick Droz Message-ID: <3D2AC50D.5030300@zurich.ibm.com> Date: Tue, 9 Jul 2002 13:12:13 +0200 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: Patrick Droz Organization: IBM Research Division Subject: e-mail address Joel Halpern To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list Content-Transfer-Encoding: 7bit Joel, sorry for this unpopular message on the list but your old e-mail address does not work anymore. Could you please contact me. Thanks, Patrick From owner-forces@PEACH.EASE.LSOFT.COM Thu Jul 11 08:03:48 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 IAA16343 for ; Thu, 11 Jul 2002 08:03:47 -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 <17.0068BCA8@cherry.ease.lsoft.com>; Thu, 11 Jul 2002 8:04:40 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 22628049 for FORCES@PEACH.EASE.LSOFT.COM; Thu, 11 Jul 2002 08:04:39 -0400 Received: from 195.212.91.200 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 11 Jul 2002 08:04:38 -0400 Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23]) by d12lmsgate-2.de.ibm.com (8.12.3/8.12.3) with ESMTP id g6BC4Z2Q028870 for ; Thu, 11 Jul 2002 14:04:36 +0200 Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140]) by d12relay02.de.ibm.com (8.11.1m3/NCO/VER6.2) with SMTP id g6BC4Wj50238 for ; Thu, 11 Jul 2002 14:04:32 +0200 Received: from dhcp70-7.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA71742 from ; Thu, 11 Jul 2002 14:04:30 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------070003000001060305000500" Approved-By: Patrick Droz Message-ID: <3D2D7442.7080408@zurich.ibm.com> Date: Thu, 11 Jul 2002 14:04:18 +0200 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: Patrick Droz Organization: IBM Research Division Subject: Tentative Meeting Agenda To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list This is a multi-part message in MIME format. --------------070003000001060305000500 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Attached is a tentative meeting agenda for our WG in Yokohama. The last presentation from Joel is not confirmed yet. Regards, Patrick --------------070003000001060305000500 Content-Type: text/plain; name="agenda_54.txt" Content-Disposition: inline; filename="agenda_54.txt" Content-Transfer-Encoding: 7bit IETF Yokohama, ForCES WG ------------------------ MONDAY, July 15, 2002 0900-1130 Morning Sessions Room 303 RTG forces Forwarding and Control Element Separation WG ForCES I-Ds ----------- Agenda bashing WG Drafts --------- Netlink as an IP Services Protocol draft-ietf-forces-netlink-03.txt no presentation, in last-call Requirements for Separation of IP Control and Forwarding draft-ietf-forces-requirements-04.txt Margaret 15 min in last-call ForCES Applicability Statement draft-ietf-forces-applicability-00.txt David 10 min ForCES Architectural Framework draft-ietf-forces-framework-00.txt Lily 20 min Individual Drafts ----------------- ForCES Forwarding Element Functional Model draft-yang-forces-model-00.txt Joel 40 min ForwArding and Control ElemenT protocol (FACT) draft-gopal-forces-fact-01.txt no presentation --------------070003000001060305000500-- From owner-forces@PEACH.EASE.LSOFT.COM Wed Jul 17 00:30:59 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 AAA11480 for ; Wed, 17 Jul 2002 00:30:59 -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 <8.006960A0@cherry.ease.lsoft.com>; Wed, 17 Jul 2002 0:31:50 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 23071877 for FORCES@PEACH.EASE.LSOFT.COM; Wed, 17 Jul 2002 00:31:49 -0400 Received: from 192.52.58.11 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 17 Jul 2002 00:31:49 -0400 Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126]) by mail2.hd.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.42 2002/05/23 22:21:11 root Exp $) with SMTP id g6H4Vma19215 for ; Wed, 17 Jul 2002 04:31:49 GMT Received: from FMSMSX017.fm.intel.com ([132.233.42.196]) by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002071621313426881 for ; Tue, 16 Jul 2002 21:31:34 -0700 Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19) id <3DWBS855>; Tue, 16 Jul 2002 21:31:48 -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: Tue, 16 Jul 2002 21:31:47 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "Putzolu, David" Subject: ForCES Requirements & Netlink Informational Draft WG Last calls c omplete To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list All, The WG last calls announced on July 03, 2002 for the following two drafts have successfully completed. These drafts incorporate changes addressing all previously raised issues. http://www.ietf.org/internet-drafts/draft-ietf-forces-requirements-04.txt http://www.ietf.org/internet-drafts/draft-ietf-forces-netlink-03.txt The Netlink draft has been forwarded to the ADs for review. The requirements draft was found to have some small editorial issues (references to expired drafts, long author list) that are being corrected before forwarding to the ADs. I'd like to thank the Netlink and requirements draft authors for all their hard work, and the list participants for their help in getting these drafts properly reviewed. Cheers, David From owner-forces@PEACH.EASE.LSOFT.COM Tue Jul 23 17:25:45 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 RAA04677 for ; Tue, 23 Jul 2002 17:25:45 -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.006A3924@cherry.ease.lsoft.com>; Tue, 23 Jul 2002 17:26:45 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 23624725 for FORCES@PEACH.EASE.LSOFT.COM; Tue, 23 Jul 2002 17:26:45 -0400 Received: from 134.134.248.4 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Tue, 23 Jul 2002 17:26:44 -0400 Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by hebe.or.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.42 2002/05/23 22:21:11 root Exp $) with SMTP id g6NLQhO14267 for ; Tue, 23 Jul 2002 21:26:43 GMT Received: from orsmsx26.jf.intel.com ([192.168.65.26]) by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2002072314272624575 ; Tue, 23 Jul 2002 14:27:26 -0700 Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 23 Jul 2002 14:26:42 -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: Tue, 23 Jul 2002 14:26:39 -0700 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: "Putzolu, David" Subject: Summary of ForCES Meeting at IETF 54 Comments: To: Bill Fenner , "Alex Zinin (zinin@psg.com)" To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list The ForCES meeting at IETF 54 marked the successful completion of the last call period for the Netlink Informational draft and the ForCES Requirements draft. The Netlink draft was forwarded to the IESG and the Requirements draft will proceed to the IESG after an editorial revision is posted. Changes to the ForCES framework where discussed and the chairs noted that this document is maturing and may last call soon. An early draft individual contribution of a model document was presented and will be further refined by the authors before being submitted for consideration as a working group document. From owner-forces@PEACH.EASE.LSOFT.COM Wed Jul 24 08:18:13 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 IAA05446 for ; Wed, 24 Jul 2002 08:18:13 -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 <3.006A4C81@cherry.ease.lsoft.com>; Wed, 24 Jul 2002 8:19:15 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 23676982 for FORCES@PEACH.EASE.LSOFT.COM; Wed, 24 Jul 2002 08:19:14 -0400 Received: from 132.151.1.176 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 24 Jul 2002 08:09:14 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02147; Wed, 24 Jul 2002 08:08:10 -0400 (EDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Approved-By: nsyracus@CNRI.RESTON.VA.US Message-ID: <200207241208.IAA02147@ietf.org> Date: Wed, 24 Jul 2002 08:08:10 -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-requirements-05.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 : Requirements for Separation of IP Control and Forwarding Author(s) : H. Khosravi Filename : draft-ietf-forces-requirements-05.txt Pages : 15 Date : 23-Jul-02 This document introduces the ForCES architecture and defines a set of associated terminology. This document also defines a set of architectural, modeling, and protocol requirements to logically separate the control and data forwarding planes of an IP (IPv4, IPv6, etc.) networking device. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-forces-requirements-05.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-requirements-05.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-requirements-05.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: <20020723145515.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-forces-requirements-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-forces-requirements-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020723145515.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-forces@PEACH.EASE.LSOFT.COM Thu Jul 25 08:20:45 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 IAA00582 for ; Thu, 25 Jul 2002 08:20:45 -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 <19.006A76BB@cherry.ease.lsoft.com>; Thu, 25 Jul 2002 8:21:50 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 23792740 for FORCES@PEACH.EASE.LSOFT.COM; Thu, 25 Jul 2002 08:21:49 -0400 Received: from 195.212.91.201 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 25 Jul 2002 08:21:48 -0400 Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23]) by d12lmsgate-3.de.ibm.com (8.12.3/8.12.3) with ESMTP id g6PCLkhF033668 for ; Thu, 25 Jul 2002 14:21:47 +0200 Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140]) by d12relay02.de.ibm.com (8.11.1m3/NCO/VER6.2) with SMTP id g6PCLhe25814 for ; Thu, 25 Jul 2002 14:21:46 +0200 Received: from dhcp70-7.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA60944 from ; Thu, 25 Jul 2002 14:21:42 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------030309070308030200000008" Approved-By: Patrick Droz Message-ID: <3D3FED51.6020204@zurich.ibm.com> Date: Thu, 25 Jul 2002 14:21:37 +0200 Reply-To: Forwarding and Control Element Separation Sender: Forwarding and Control Element Separation From: Patrick Droz Organization: IBM Research Division Subject: ForCES minutes To: FORCES@PEACH.EASE.LSOFT.COM Precedence: list This is a multi-part message in MIME format. --------------030309070308030200000008 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Attached are the minutes from the ForCES meeting in Yokohama. Please comment before I will forward them to the official minutes list. Regards, Patrick PS. Thanks Christian for taking minutes --------------030309070308030200000008 Content-Type: text/plain; name="minutes_54.txt" Content-Disposition: inline; filename="minutes_54.txt" Content-Transfer-Encoding: 7bit IETF 54, Yokohama, ForCES Minutes --------------------------------- About 80 people attending the meeting. Agenda bashing & list of draft to be reviewed. WG status: 2 drafts on last call ForCES Model - Draft 0 (Joel presenting) ------------ Individual contribution: ForCES Functional Model Draft about ForCES models: - How to represent models (on the wire and in the doc)? - How complex a capabilities model? - What Elements for the State Model? Capabilites & State models should share representation & element identification. Should we use a combined document / on the wire representation (XML based?) Should we use an existing one (SMI, SPPI) We should not build our own Q? No opinion on which aspect is used. Instead up level the problem that we're trying to solve by picking one of these solutions? What are the requirements e.g. do things going on the wire must be small, easy to troubleshoot, Q: (Margaret) Want a language that is easy to use to pass the information around. A: (Joel): Important for the model draft to at least have the human readable aspect. Important to also consider it from the protocol angle. Q: Some people want an open model where capabilities and state info might be exchanged over existing protocol. A: (Joel) Don't want to mix multiple protocols here. Hope for a consistent framework for the control protocol. Q: (Margaret): Don't think we're at the point to define the protocols in the WG. CAPABILITIES MODEL: Current doc calls for a simple model, however there is now existing work on which to base a more complex capabilities model. Framework PIB Diff. Serv. QoS PIB. Joel: Should we go for the simple case called for in the document or should we make use of the capabilities information of the Framework PIB & DiffServ. PIB on our framework? How complex the capability model should we include? What is the language to define the capabilities? Q: What do we need to define the capabilities and not the language only? A: (Joel): Need to define the capabilities where we want interoperability. STATE MODEL Need to build a good but not excessive set, DiffServ set would seem a good starting point for QoS Also need a forwarding set (and forwarding capabilities) Q: (Sue)? How do you match the capabilities and the blocks? You have a n x n matrix. A: (Joel) No. Capabilities about a number of state elements. Q: Doesn't work for the forwarding blocks, this FE link to this FE. A: (Joel) Capabilities deal with Forwarding blocks. State model deals with the blocks. Q: Do we want an FE be controlled by two CE? If yes the model becomes more complex. How does topology info between the interconnection of FE interact with the protocol? Q: FE wants to do mcast. FE from one block to n-blocks. CE setup the FE, mcast forwarding table. A: (Joel) Disagreement on whether it works or not. Take if off line. NetLink - Draft 03 (no presentation) ------- Will declare last call completed if no comment Requirement document - Draft 04 (Margaret presenting) -------------------- Last call period ended on the meeting date Changes: High availability -> CE redundancy Include possibility for multiple protocols Added requirements to query statistics. Last call comments: Support both Capability & State model Support for failure notifications from FE Added text for off-loaded functions Is last call complete? Design team thinks so. Doc will be forwarded Applicability Statement (David presenting) ----------------------- 3 main changes to align Applicability stmt with Req. draft Added Purpose section Changed CE Redundancy/Failover to align with Requirements Draft Changed Sections on Locality, per rough consensus on list Q: (Russ) - Draft don't say locality are that close (e.g. the room). A: (David) Current language is that the Locality is very close (fate sharing) David will comment on the lest after checking the exact text. Q: (Russ) Will propose some text to clarify. Architectural framework (Lily presenting) ----------------------- What's new? CE Redundancy support FE Topology examples Message exchange examples Q: (Alex): Routing/Forwarding table needs to be clarified. Who does ARP need to be specified. Q? (Chin Choi): What kinds of messages are exchanged between FE? A: Mostly data packets that will be routed. Fwd & Control Element Protocol (FACT) No slides --------------030309070308030200000008-- From owner-forces@PEACH.EASE.LSOFT.COM Tue Jul 30 08:04:28 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 IAA13872 for ; Tue, 30 Jul 2002 08:04:27 -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 <11.006B2B3E@cherry.ease.lsoft.com>; Tue, 30 Jul 2002 8:05:34 -0400 Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 24148679 for FORCES@PEACH.EASE.LSOFT.COM; Tue, 30 Jul 2002 08:05:33 -0400 Received: from 132.151.1.176 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Tue, 30 Jul 2002 07:55:32 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13289; Tue, 30 Jul 2002 07:54:24 -0400 (EDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Approved-By: nsyracus@CNRI.RESTON.VA.US Message-ID: <200207301154.HAA13289@ietf.org> Date: Tue, 30 Jul 2002 07:54:24 -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-requirements-06.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 : Requirements for Separation of IP Control and Forwarding Author(s) : H. Khosravi, T. Anderson Filename : draft-ietf-forces-requirements-06.txt Pages : 15 Date : 29-Jul-02 This document introduces the ForCES architecture and defines a set of associated terminology. This document also defines a set of architectural, modeling, and protocol requirements to logically separate the control and data forwarding planes of an IP (IPv4, IPv6, etc.) networking device. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-forces-requirements-06.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-requirements-06.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-requirements-06.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: <20020729151155.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-forces-requirements-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-forces-requirements-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020729151155.I-D@ietf.org> --OtherAccess-- --NextPart--