From owner-rap@ops.ietf.org Sun Dec 2 01:45:00 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02669 for ; Sun, 2 Dec 2001 01:45:00 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16AQIr-00014L-00 for rap-data@psg.com; Sat, 01 Dec 2001 22:40:41 -0800 Received: from fmfdns02.fm.intel.com ([132.233.247.11] helo=thalia.fm.intel.com) by psg.com with esmtp (Exim 3.33 #1) id 16AQIq-00014F-00 for rap@ops.ietf.org; Sat, 01 Dec 2001 22:40:41 -0800 Received: from fmsmsxvs042.fm.intel.com (fmsmsxv042-1.fm.intel.com [132.233.48.110]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.46 2001/10/25 21:02:55 root Exp $) with SMTP id GAA09337 for ; Sun, 2 Dec 2001 06:40:39 GMT Received: from orsmsx26.jf.intel.com ([192.168.65.26]) by fmsmsxvs042.fm.intel.com (NAVGW 2.5.1.6) with SMTP id M2001120122414327361 ; Sat, 01 Dec 2001 22:41:43 -0800 Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19) id ; Sat, 1 Dec 2001 22:40:39 -0800 Message-ID: <59885C5E3098D511AD690002A5072D3C0157CD76@orsmsx111.jf.intel.com> From: "Hahn, Scott" To: rap@ops.ietf.org Cc: bwijnen@lucent.com, "Mark L. Stevens" Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Date: Sat, 1 Dec 2001 22:40:38 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-rap@ops.ietf.org Precedence: bulk This WG last call for the Framework PIB document http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt has completed. We have had no dissenting comments on the mailing list and we intend to advance this document to the AD for review by the IESG. Scott Hahn Mark Stevens WG co-chairs From owner-rap@ops.ietf.org Mon Dec 3 08:38:21 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29155 for ; Mon, 3 Dec 2001 08:38:20 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16AtGu-0001nE-00 for rap-data@psg.com; Mon, 03 Dec 2001 05:36:36 -0800 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by psg.com with esmtp (Exim 3.33 #1) id 16AtGt-0001n7-00 for rap@ops.ietf.org; Mon, 03 Dec 2001 05:36:35 -0800 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28827; Mon, 3 Dec 2001 08:36:31 -0500 (EST) Message-Id: <200112031336.IAA28827@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rap@ops.ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-rap-feedback-frwk-01.txt Date: Mon, 03 Dec 2001 08:36:31 -0500 Sender: owner-rap@ops.ietf.org Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Resource Allocation Protocol Working Group of the IETF. Title : Framework of COPS-PR Policy Usage Feedback Author(s) : D. Rawlins, A. Kulkarni Filename : draft-ietf-rap-feedback-frwk-01.txt Pages : 7 Date : 30-Nov-01 Common Open Policy Services Protocol [COPS], RFC 2748, defined the capability of reporting information to the PDP. The types of report information are success, failure and accounting of an installed state. This document focuses on the accounting report type and the necessary framework for the monitoring and reporting of usage feedback for an installed state. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rap-feedback-frwk-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-rap-feedback-frwk-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-rap-feedback-frwk-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: <20011130133547.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rap-feedback-frwk-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rap-feedback-frwk-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20011130133547.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-rap@ops.ietf.org Mon Dec 3 08:38:24 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29170 for ; Mon, 3 Dec 2001 08:38:22 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16AtGo-0001n4-00 for rap-data@psg.com; Mon, 03 Dec 2001 05:36:30 -0800 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by psg.com with esmtp (Exim 3.33 #1) id 16AtGo-0001mx-00 for rap@ops.ietf.org; Mon, 03 Dec 2001 05:36:30 -0800 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28815; Mon, 3 Dec 2001 08:36:26 -0500 (EST) Message-Id: <200112031336.IAA28815@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rap@ops.ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-rap-feedback-fr-pib-01.txt Date: Mon, 03 Dec 2001 08:36:26 -0500 Sender: owner-rap@ops.ietf.org Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Resource Allocation Protocol Working Group of the IETF. Title : Framework of COPS-PR Policy Information Base for Policy Usage Feedback Author(s) : D. Rawlins et al. Filename : draft-ietf-rap-feedback-fr-pib-01.txt Pages : 27 Date : 30-Nov-01 Currently there are no policy classes defined for the PEP to convey provisioned policy usage feedback to the PDP. The purpose of this document is to define the policy usage feedback framework PIB that specifies the policy classes common for COPS feedback reports. The basic operation and objects for reporting usage information are defined in [COPS]. A specific clientSI feedback object named REPORT is defined in [COPS-PR]. A framework for approaching solicited and periodic usage feedback is described in [COPS-FEED-FRWK]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rap-feedback-fr-pib-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-rap-feedback-fr-pib-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-rap-feedback-fr-pib-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: <20011130133535.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rap-feedback-fr-pib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rap-feedback-fr-pib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20011130133535.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-rap@ops.ietf.org Mon Dec 3 10:11:00 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03620 for ; Mon, 3 Dec 2001 10:10:59 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16Aujh-00046L-00 for rap-data@psg.com; Mon, 03 Dec 2001 07:10:25 -0800 Received: from mail2.orchestream.com ([195.153.64.126]) by psg.com with esmtp (Exim 3.33 #1) id 16Aujg-00046F-00 for rap@ops.ietf.org; Mon, 03 Dec 2001 07:10:24 -0800 Received: from rimmer.orchestream.com (rimmer.orchestream.com) by mail2.orchestream.com (Content Technologies SMTPRS 4.1.5) with ESMTP id for ; Mon, 3 Dec 2001 15:12:42 +0000 Received: from s1000.orchestream.com (s1000.orchestream.com [192.168.0.16]) by rimmer.orchestream.com (8.9.3/8.9.3) with ESMTP id LAA03363 for ; Mon, 3 Dec 2001 11:11:38 GMT Received: by s1000.orchestream.com with Internet Mail Service (5.5.2653.19) id ; Mon, 3 Dec 2001 15:04:37 -0000 Message-ID: From: "Da Silva, Pedro" To: rap@ops.ietf.org Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Date: Mon, 3 Dec 2001 15:04:36 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-rap@ops.ietf.org Precedence: bulk Given that last call period is over I presume there was consensus on a few issues raised recently concerning the frwkIfRoleCombo table. Could you please provide the resolutions? The two messages where these issues were raised were: Sent: Friday, November 16, 2001 2:43 PM Subject: RE: frameworkpib-06 comments and Sent: Friday, November 23, 2001 11:23 AM Subject: frwkIfRoleComboTable cheers, Pedro -----Original Message----- From: Hahn, Scott [mailto:scott.hahn@intel.com] Sent: Sunday, December 02, 2001 6:41 AM To: rap@ops.ietf.org Cc: bwijnen@lucent.com; Mark L. Stevens Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes This WG last call for the Framework PIB document http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt has completed. We have had no dissenting comments on the mailing list and we intend to advance this document to the AD for review by the IESG. Scott Hahn Mark Stevens WG co-chairs -----Original Message----- From: Hahn, Scott [mailto:scott.hahn@intel.com] Sent: Sunday, December 02, 2001 6:41 AM To: rap@ops.ietf.org Cc: bwijnen@lucent.com; Mark L. Stevens Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes This WG last call for the Framework PIB document http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt has completed. We have had no dissenting comments on the mailing list and we intend to advance this document to the AD for review by the IESG. Scott Hahn Mark Stevens WG co-chairs From owner-rap@ops.ietf.org Tue Dec 4 14:23:37 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07906 for ; Tue, 4 Dec 2001 14:23:36 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16BL93-000KXB-00 for rap-data@psg.com; Tue, 04 Dec 2001 11:22:21 -0800 Received: from fmfdns02.fm.intel.com ([132.233.247.11] helo=thalia.fm.intel.com) by psg.com with esmtp (Exim 3.33 #1) id 16BL92-000KWo-00 for rap@ops.ietf.org; Tue, 04 Dec 2001 11:22:20 -0800 Received: from fmsmsxvs041.fm.intel.com (fmsmsxv041-1.fm.intel.com [132.233.48.109]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.46 2001/10/25 21:02:55 root Exp $) with SMTP id TAA03381 for ; Tue, 4 Dec 2001 19:22:19 GMT Received: from FMSMSX018.fm.intel.com ([132.233.42.197]) by fmsmsxvs041.fm.intel.com (NAVGW 2.5.1.6) with SMTP id M2001120411232722076 ; Tue, 04 Dec 2001 11:23:27 -0800 Received: by fmsmsx018.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 4 Dec 2001 11:22:16 -0800 Message-ID: <65D5A07B5098D511BDDA0002A508E64F01D02577@orsmsx110.jf.intel.com> From: "Sahita, Ravi" To: "'Da Silva, Pedro'" , rap@ops.ietf.org Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Date: Tue, 4 Dec 2001 11:22:10 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-rap@ops.ietf.org Precedence: bulk Pedro, Regarding the issues, like you proposed, we can define a base frwkRoleCombo table containing the basic RoleCombination and IfCapSetName attributes; and an extension (the frwkIfRoleCombo table) which contains the IfIndex, IfDirection attributes. This addresses both issues of having a base rolecombo table to form other extensions of and having the IfDirection in its extension the frwkIfRoleCombo table which allows different capability sets in different directions to be defined. Does that sound satisfactory? Ravi -----Original Message----- From: Da Silva, Pedro [mailto:pdasilva@orchestream.com] Sent: Monday, December 03, 2001 7:05 AM To: rap@ops.ietf.org Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Given that last call period is over I presume there was consensus on a few issues raised recently concerning the frwkIfRoleCombo table. Could you please provide the resolutions? The two messages where these issues were raised were: Sent: Friday, November 16, 2001 2:43 PM Subject: RE: frameworkpib-06 comments and Sent: Friday, November 23, 2001 11:23 AM Subject: frwkIfRoleComboTable cheers, Pedro -----Original Message----- From: Hahn, Scott [mailto:scott.hahn@intel.com] Sent: Sunday, December 02, 2001 6:41 AM To: rap@ops.ietf.org Cc: bwijnen@lucent.com; Mark L. Stevens Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes This WG last call for the Framework PIB document http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt has completed. We have had no dissenting comments on the mailing list and we intend to advance this document to the AD for review by the IESG. Scott Hahn Mark Stevens WG co-chairs -----Original Message----- From: Hahn, Scott [mailto:scott.hahn@intel.com] Sent: Sunday, December 02, 2001 6:41 AM To: rap@ops.ietf.org Cc: bwijnen@lucent.com; Mark L. Stevens Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes This WG last call for the Framework PIB document http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt has completed. We have had no dissenting comments on the mailing list and we intend to advance this document to the AD for review by the IESG. Scott Hahn Mark Stevens WG co-chairs From owner-rap@ops.ietf.org Wed Dec 5 06:54:19 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18691 for ; Wed, 5 Dec 2001 06:54:19 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16BaXk-000A3d-00 for rap-data@psg.com; Wed, 05 Dec 2001 03:48:52 -0800 Received: from mail2.orchestream.com ([195.153.64.126]) by psg.com with esmtp (Exim 3.33 #1) id 16BaXk-000A3M-00 for rap@ops.ietf.org; Wed, 05 Dec 2001 03:48:52 -0800 Received: from rimmer.orchestream.com (rimmer.orchestream.com) by mail2.orchestream.com (Content Technologies SMTPRS 4.1.5) with ESMTP id for ; Wed, 5 Dec 2001 11:51:07 +0000 Received: from s1000.orchestream.com (s1000.orchestream.com [192.168.0.16]) by rimmer.orchestream.com (8.9.3/8.9.3) with ESMTP id HAA18264 for ; Wed, 5 Dec 2001 07:49:58 GMT Received: by s1000.orchestream.com with Internet Mail Service (5.5.2653.19) id ; Wed, 5 Dec 2001 11:43:03 -0000 Message-ID: From: "Da Silva, Pedro" To: rap@ops.ietf.org Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Date: Wed, 5 Dec 2001 11:43:03 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-rap@ops.ietf.org Precedence: bulk Ravi, Yes that sounds great, it goes towards the generic nature of the frwk PIB. Although I would expect to see the extended tables in the client type PIB and not in the frwk PIB. Unless, of course, there are different PIBs defs that need that construct (e.g. Feedback PIB) and so one could make a case for placing the table in the frwk PIB. And the frwkIfRoleCombo table certainly falls in that lot...so no worries. cheers, Pedro -----Original Message----- From: Sahita, Ravi [mailto:ravi.sahita@intel.com] Sent: Tuesday, December 04, 2001 7:22 PM To: 'Da Silva, Pedro'; rap@ops.ietf.org Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Pedro, Regarding the issues, like you proposed, we can define a base frwkRoleCombo table containing the basic RoleCombination and IfCapSetName attributes; and an extension (the frwkIfRoleCombo table) which contains the IfIndex, IfDirection attributes. This addresses both issues of having a base rolecombo table to form other extensions of and having the IfDirection in its extension the frwkIfRoleCombo table which allows different capability sets in different directions to be defined. Does that sound satisfactory? Ravi -----Original Message----- From: Da Silva, Pedro [mailto:pdasilva@orchestream.com] Sent: Monday, December 03, 2001 7:05 AM To: rap@ops.ietf.org Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Given that last call period is over I presume there was consensus on a few issues raised recently concerning the frwkIfRoleCombo table. Could you please provide the resolutions? The two messages where these issues were raised were: Sent: Friday, November 16, 2001 2:43 PM Subject: RE: frameworkpib-06 comments and Sent: Friday, November 23, 2001 11:23 AM Subject: frwkIfRoleComboTable cheers, Pedro -----Original Message----- From: Hahn, Scott [mailto:scott.hahn@intel.com] Sent: Sunday, December 02, 2001 6:41 AM To: rap@ops.ietf.org Cc: bwijnen@lucent.com; Mark L. Stevens Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes This WG last call for the Framework PIB document http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt has completed. We have had no dissenting comments on the mailing list and we intend to advance this document to the AD for review by the IESG. Scott Hahn Mark Stevens WG co-chairs -----Original Message----- From: Hahn, Scott [mailto:scott.hahn@intel.com] Sent: Sunday, December 02, 2001 6:41 AM To: rap@ops.ietf.org Cc: bwijnen@lucent.com; Mark L. Stevens Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes This WG last call for the Framework PIB document http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt has completed. We have had no dissenting comments on the mailing list and we intend to advance this document to the AD for review by the IESG. Scott Hahn Mark Stevens WG co-chairs From owner-rap@ops.ietf.org Wed Dec 5 07:24:12 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19050 for ; Wed, 5 Dec 2001 07:24:11 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16Bb5N-000BjT-00 for rap-data@psg.com; Wed, 05 Dec 2001 04:23:37 -0800 Received: from infres-192.enst.fr ([137.194.192.1] helo=infres.enst.fr) by psg.com with esmtp (Exim 3.33 #1) id 16Bb5M-000Bj7-00 for rap@ops.ietf.org; Wed, 05 Dec 2001 04:23:36 -0800 Received: from yahoo.com (dragon.enst.fr [137.194.192.44]) by infres.enst.fr (Postfix) with ESMTP id C2CE518C5 for ; Wed, 5 Dec 2001 13:23:32 +0100 (MET) Message-ID: <3C0E134F.3984C955@yahoo.com> Date: Wed, 05 Dec 2001 13:30:08 +0100 From: Nguyen Thi Mai Trang Organization: ENST - INFRES X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: rap@ops.ietf.org Subject: questions on framworkpib-06.txt (1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-rap@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: 7bit Hello all, After reading the draft-ietf-rap-frameworkpib-06.txt, I have some questions necessary to clarify my comprehension. Thank you very much if someone can answer to my question, even some brief sentences: 1) Section 2.2 : I understand that the Role Combination assignment is the responsibility of the PDP. First of all, the PEP sends to the PDP information about all its physical interfaces and their capabilities with the Role Combination "null". After that, the PDP sends a dicision to assign Role Combination to each physical interface of the device. These Role Combinations will be used later for device configuration. So far, I have thought that Role Combination is assigned with each interface by hand at the device, it is not the responsibility of the PDP. Then, the PEP will send to the PDP all Role Combinations it has, not send information about all physical interfaces it has. Is it a new point in version 06? Anyway, I found that logical to let the PDP make this binding. I agree with Pedro that the class RoleComboEntry should be generic. Thank you. MT From owner-rap@ops.ietf.org Wed Dec 5 13:03:20 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29731 for ; Wed, 5 Dec 2001 13:03:19 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16BgNT-00013i-00 for rap-data@psg.com; Wed, 05 Dec 2001 10:02:39 -0800 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by psg.com with esmtp (Exim 3.33 #1) id 16BgNS-00013I-00 for rap@ops.ietf.org; Wed, 05 Dec 2001 10:02:38 -0800 Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57]) by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB5I1ud02736 for ; Wed, 5 Dec 2001 13:01:56 -0500 (EST) Received: from zbl6c012.corpeast.baynetworks.com by zcars04f.ca.nortel.com; Wed, 5 Dec 2001 13:02:10 -0500 Received: from zbl6c002.corpeast.baynetworks.com ([132.245.205.52]) by zbl6c012.corpeast.baynetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XXVB4QP6; Wed, 5 Dec 2001 13:00:55 -0500 Received: from tweedy.NortelNetworks.com (dhcp229-110.engeast.baynetworks.com [192.32.229.110]) by zbl6c002.corpeast.baynetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XRGWZX8C; Wed, 5 Dec 2001 13:00:57 -0500 Message-Id: <5.0.0.25.0.20011205124537.03339e40@zbl6c002.corpeast.baynetworks.com> X-Sender: khchan@zbl6c002.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 05 Dec 2001 12:59:49 -0500 To: rap@ops.ietf.org From: "Kwok-Ho Chan" Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes Cc: ravi.sahita@intel.com, pdasilva@orchestream.com, "Kwok-Ho Chan" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Orig: Sender: owner-rap@ops.ietf.org Precedence: bulk To All: Here is our (Ravi, Pedro and My) thinkings: We would change the Framework PIB to: frwkRoleComboEntry PIB-INDEX { frwkRoleComboPrid } UNIQUENESS {} ::= { frwkRoleComboTable 1 } FrwkRoleComboEntry ::= SEQUENCE { frwkRoleComboPrid InstanceId, frwkRoleComboRoles RoleCombination, frwkRoleComboCapSetName SnmpAdminString } frwkIfRoleComboEntry EXTENDS { frwkRoleComboEntry } UNIQUENESS { frwkIfRoleComboIfIndex, frwkRoleComboCapSetName } ::= { frwkIfRoleComboTable 1 } FrwkIfRoleComboEntry ::= SEQUENCE { frwkIfRoleComboIfIndex InterfaceIndex } And, in the future, someone can define a new PRC, like: frwkSlotRoleComboEntry EXTENDS { frwkRoleComboEntry } UNIQUENESS { frwkSlotRoleComboSlotNumber, frwkRoleComboCapSetName } ::= { frwkSlotRoleComboTable 1 } FrwkSlotRoleComboEntry ::= SEQUENCE { frwkSlotRoleComboSlotNumber Unsigned32 } We think this will solve the issues Pedro raised and will also allow the DiffServ PIB to work correctly without any modification. Please let us know if you have any comments, as the next version of the draft will be going into IESG. Thank you very much! -- Ravi, Pedro, and Kwok -- At 11:43 AM 12/5/01 +0000, Da Silva, Pedro wrote: >Ravi, > >Yes that sounds great, it goes towards the generic nature of the frwk PIB. > >Although I would expect to see the extended tables in the client type PIB >and not in the frwk PIB. >Unless, of course, there are different PIBs defs that need that construct >(e.g. Feedback PIB) and so one could make a case for placing the table in >the frwk PIB. And the frwkIfRoleCombo table certainly falls in that lot...so >no worries. > >cheers, >Pedro > >-----Original Message----- >From: Sahita, Ravi [mailto:ravi.sahita@intel.com] >Sent: Tuesday, December 04, 2001 7:22 PM >To: 'Da Silva, Pedro'; rap@ops.ietf.org >Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt >concludes > > >Pedro, > >Regarding the issues, like you proposed, we can >define a base frwkRoleCombo table containing the >basic RoleCombination and IfCapSetName attributes; >and an extension (the frwkIfRoleCombo table) which >contains the IfIndex, IfDirection attributes. > >This addresses both issues of having a base rolecombo >table to form other extensions of and having the >IfDirection in its extension the frwkIfRoleCombo table >which allows different capability sets in different >directions to be defined. Does that sound satisfactory? > >Ravi > >-----Original Message----- >From: Da Silva, Pedro [mailto:pdasilva@orchestream.com] >Sent: Monday, December 03, 2001 7:05 AM >To: rap@ops.ietf.org >Subject: RE: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes > > >Given that last call period is over I presume there was consensus on a few >issues raised recently concerning the frwkIfRoleCombo table. Could you >please provide the resolutions? > >The two messages where these issues were raised were: >Sent: Friday, November 16, 2001 2:43 PM >Subject: RE: frameworkpib-06 comments > >and >Sent: Friday, November 23, 2001 11:23 AM >Subject: frwkIfRoleComboTable > >cheers, >Pedro > >-----Original Message----- >From: Hahn, Scott [mailto:scott.hahn@intel.com] >Sent: Sunday, December 02, 2001 6:41 AM >To: rap@ops.ietf.org >Cc: bwijnen@lucent.com; Mark L. Stevens >Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes > > >This WG last call for the Framework PIB document >http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt >has completed. We have had no dissenting comments on the mailing list and we >intend to advance this document to the AD for review by the IESG. > > Scott Hahn > Mark Stevens > WG co-chairs > > >-----Original Message----- >From: Hahn, Scott [mailto:scott.hahn@intel.com] >Sent: Sunday, December 02, 2001 6:41 AM >To: rap@ops.ietf.org >Cc: bwijnen@lucent.com; Mark L. Stevens >Subject: WG Last Call for draft-ietf-rap-frameworkpib-06.txt concludes > > >This WG last call for the Framework PIB document >http://www.ietf.org/internet-drafts/draft-ietf-rap-frameworkpib-06.txt >has completed. We have had no dissenting comments on the mailing list and we >intend to advance this document to the AD for review by the IESG. > > Scott Hahn > Mark Stevens > WG co-chairs From owner-rap@ops.ietf.org Thu Dec 27 00:36:37 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25972 for ; Thu, 27 Dec 2001 00:36:36 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16JTAw-0001ox-00 for rap-data@psg.com; Wed, 26 Dec 2001 21:33:54 -0800 Received: from mail01g.rapidsite.net ([207.158.192.232]) by psg.com with smtp (Exim 3.33 #1) id 16JTAv-0001or-00 for rap@ops.ietf.org; Wed, 26 Dec 2001 21:33:53 -0800 Received: from www.wsspl.com (209.238.114.7) by mail01g.rapidsite.net (RS ver 1.0.62s) with SMTP id 022318 for ; Thu, 27 Dec 2001 00:33:32 -0500 (EST) Received: from 134.15.15.26 [134.15.15.26] by paroksha.wsspl.com (1.61/SMTPD) at Thu, 27 Dec 01 10:54:44 India Received: by MEDHA with Internet Mail Service (5.5.2653.19) id ; Thu, 27 Dec 2001 10:57:01 +0530 Message-ID: <30BFDEA66FF4D41191EB00D0B765BC6F046794@MEDHA> X-Envelope-From: mdhara@WSSPL.com From: Muralidhar S To: "'rap@ops.ietf.org'" Subject: COPS Request State Date: Thu, 27 Dec 2001 10:57:00 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Gateway: --->> pop@GIFT - POP3/SMTP Gateway 5.5 for Exchange <<--- X-Loop-Detect: 1 Sender: owner-rap@ops.ietf.org Precedence: bulk All, We are working on a SDK for PDP and PEP development. As part of this, we have some questions on the cops request state. As part of the SSQ message from PDP, PEP sends "all the Request State" for that particular client handle. Can someone let me know what does it means when we say "all the Request State"? Does PEP needs to send all the Policy Decisions ( PRID, EPD ) that PDP has installed? Thanks murali ______________________ WebSpectrum Software Pvt. Ltd, Jayanagar, Bangalore - 560082 www.wsspl.com ______________________ From owner-rap@ops.ietf.org Thu Dec 27 20:54:42 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23185 for ; Thu, 27 Dec 2001 20:54:41 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16JmAl-000IHr-00 for rap-data@psg.com; Thu, 27 Dec 2001 17:50:59 -0800 Received: from fmfdns01.fm.intel.com ([132.233.247.10] helo=calliope1.fm.intel.com) by psg.com with esmtp (Exim 3.33 #1) id 16JmAk-000IHl-00 for rap@ops.ietf.org; Thu, 27 Dec 2001 17:50:58 -0800 Received: from fmsmsxvs043.fm.intel.com (fmsmsxv043-1.fm.intel.com [132.233.48.128]) by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.48 2001/12/13 16:27:50 root Exp $) with SMTP id BAA29176 for ; Fri, 28 Dec 2001 01:50:54 GMT Received: from orsmsx26.jf.intel.com ([192.168.65.26]) by fmsmsxvs043.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2001122717500520168 ; Thu, 27 Dec 2001 17:50:05 -0800 Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 27 Dec 2001 17:50:54 -0800 Message-ID: From: "Kulkarni, Amol" To: "'Muralidhar S'" , "'rap@ops.ietf.org'" Subject: RE: COPS Request State Date: Thu, 27 Dec 2001 17:50:53 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-rap@ops.ietf.org Precedence: bulk Hi Murali, The PEP only needs to send requests to the PDP. It shouldn't send the decisions it received. When the PDP gets the requests, it should send the appropriate decisions to the PEP. Amol -----Original Message----- From: Muralidhar S [mailto:mdhara@WSSPL.com] Sent: Wednesday, December 26, 2001 9:27 PM To: 'rap@ops.ietf.org' Subject: COPS Request State All, We are working on a SDK for PDP and PEP development. As part of this, we have some questions on the cops request state. As part of the SSQ message from PDP, PEP sends "all the Request State" for that particular client handle. Can someone let me know what does it means when we say "all the Request State"? Does PEP needs to send all the Policy Decisions ( PRID, EPD ) that PDP has installed? Thanks murali ______________________ WebSpectrum Software Pvt. Ltd, Jayanagar, Bangalore - 560082 www.wsspl.com ______________________ From owner-rap@ops.ietf.org Thu Dec 27 23:29:03 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25917 for ; Thu, 27 Dec 2001 23:29:02 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16Job8-000KJc-00 for rap-data@psg.com; Thu, 27 Dec 2001 20:26:22 -0800 Received: from mail01g.rapidsite.net ([207.158.192.232]) by psg.com with smtp (Exim 3.33 #1) id 16Job7-000KJW-00 for rap@ops.ietf.org; Thu, 27 Dec 2001 20:26:21 -0800 Received: from www.wsspl.com (209.238.114.7) by mail01g.rapidsite.net (RS ver 1.0.62s) with SMTP id 029884 for ; Thu, 27 Dec 2001 23:25:49 -0500 (EST) Received: from 134.15.15.26 [134.15.15.26] by paroksha.wsspl.com (1.61/SMTPD) at Fri, 28 Dec 01 09:56:04 India Received: by MEDHA with Internet Mail Service (5.5.2653.19) id ; Fri, 28 Dec 2001 09:58:23 +0530 Message-ID: <30BFDEA66FF4D41191EB00D0B765BC6F046797@MEDHA> X-Envelope-From: mdhara@WSSPL.com From: Muralidhar S To: "'rap@ops.ietf.org'" Subject: RE: COPS Request State Date: Fri, 28 Dec 2001 09:58:12 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Gateway: --->> pop@GIFT - POP3/SMTP Gateway 5.5 for Exchange <<--- X-Loop-Detect: 1 Sender: owner-rap@ops.ietf.org Precedence: bulk Hi, Client Handle anyway will be part of the COPS-PR REQ message. I think as part of the Request State, PEP needs to send some more details. Section 2.3.1 from "draft-ietf-rap-frameworkpib-06.txt" is mentioned below. "2.3.1 Full Request State When the PEP wants to send the entire request state to the PDP (for example, in response to a Synchronize State Request from the PDP), the PEP MUST send the incarnation instance with the frwkPibIncarnationFullState attribute set to TRUE. " But we are not clear as what "the entire request state" is made of? Will it contain updated Role-Combination/Capabilities/Limitations etc? Regards murali > -----Original Message----- > From: ??? [mailto:bjlee@etri.re.kr] > Sent: 2001. December 28. 5:47 > To: Muralidhar S > Subject: Re: COPS Request State > > > I Think that all the request state means the set of > all the client-handle that PEP has. > > regards, > > ----- Original Message ----- > From: "Muralidhar S" > To: > Sent: Thursday, December 27, 2001 2:27 PM > Subject: COPS Request State > > > > All, > > > > We are working on a SDK for PDP and PEP development. As > part of this, we > > have > > some questions on the cops request state. As part of the > SSQ message from > > PDP, PEP > > sends "all the Request State" for that particular client > handle. Can someone > > let me know > > what does it means when we say "all the Request State"? > Does PEP needs to > > send > > all the Policy Decisions ( PRID, EPD ) that PDP has installed? > > > > Thanks > > murali > > ______________________ > > WebSpectrum Software Pvt. Ltd, > > Jayanagar, Bangalore - 560082 > > www.wsspl.com > > ______________________ > > > > > From owner-rap@ops.ietf.org Mon Dec 31 16:05:20 2001 Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06895 for ; Mon, 31 Dec 2001 16:05:19 -0500 (EST) Received: from lserv by psg.com with local (Exim 3.33 #1) id 16L9aU-0008os-00 for rap-data@psg.com; Mon, 31 Dec 2001 13:03:14 -0800 Received: from [65.194.140.130] (helo=uniwest1.it.west.unispherenetworks.com) by psg.com with esmtp (Exim 3.33 #1) id 16L9aT-0008om-00 for rap@ops.ietf.org; Mon, 31 Dec 2001 13:03:13 -0800 Received: by UNIWEST1 with Internet Mail Service (5.5.2653.19) id ; Mon, 31 Dec 2001 16:03:13 -0500 Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C031F44CB@UNIWEST1> From: "Chapman, Ken" To: "'rap@ops.ietf.org'" Subject: draft-ietf-rap-frameworkpib-06 Date: Mon, 31 Dec 2001 16:03:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-rap@ops.ietf.org Precedence: bulk Hi, I am new to this list, so I apologize if this has already been reported. In the FRAMEWORK-TC-PIB (section 3), the Role and RoleCombination TEXTUAL-CONVENTIONs are defined using SnmpAdminString, which is also a TEXTUAL-CONVENTION (imported from SNMP-FRAMEWORK-MIB. This is not allowed in SPPI (RFC3159): "11.1.2. Mapping of the SYNTAX clause The SYNTAX clause, which must be present, defines abstract data structure corresponding to the textual convention. The data structure must be one of the following: a base type (see the SYNTAX clause of an OBJECT-TYPE macro), or the BITS construct. Note that this means that the SYNTAX clause of a Textual Convention can not refer to a previously defined Textual Convention." Happy New Year, Ken ++++++++++++++++++++++++++++++++++++++++++++++ Ken Chapman Unisphere Networks, Inc. M/S 2380 Tel: +1 978 589 0288 10 Technology Park Drive Fax: +1 978 589 0800 Westford, MA 01886 Email: KChapman@UnisphereNetworks.com ++++++++++++++++++++++++++++++++++++++++++++++