From exim@www1.ietf.org Wed Aug 6 08:48:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14385 for ; Wed, 6 Aug 2003 08:48:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kNi3-0003Pv-4n for policy-archive@odin.ietf.org; Wed, 06 Aug 2003 08:48:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h76Cm7Gf013135 for policy-archive@odin.ietf.org; Wed, 6 Aug 2003 08:48:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kNhw-0003PY-Iz; Wed, 06 Aug 2003 08:48:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kNht-0003PN-Ob for policy@optimus.ietf.org; Wed, 06 Aug 2003 08:47:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14366 for ; Wed, 6 Aug 2003 08:47:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19kNhs-0002Uq-00 for policy@ietf.org; Wed, 06 Aug 2003 08:47:56 -0400 Received: from mail.metasolv.com ([12.105.131.5] helo=srvmaddog.metasolv.com) by ietf-mx with esmtp (Exim 4.12) id 19kNhr-0002Ug-00 for policy@ietf.org; Wed, 06 Aug 2003 08:47:55 -0400 Received: by mail.metasolv.com with Internet Mail Service (5.5.2655.55) id ; Wed, 6 Aug 2003 07:50:26 -0500 Message-ID: From: "Pana, Mircea" To: "IETF Policy (E-mail)" Date: Wed, 6 Aug 2003 07:46:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C35C18.CD1287A0" Subject: [Policy] draft-reyes-policy-core-ext-schema-03.txt Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , 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_001_01C35C18.CD1287A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Policy WG, We have submitted a new revision of PCELS that includes the following changes: 1. Request for an IANA assigned OID as recommended by RFC 3383 2. Clarifications for potentially ambiguous situations where both = references and attachments can be used to realize associations (e.g. PolicySetAssociation) 3. Introduction of an extension mechanism for vendor variables and = vendor=20 values 4. References separated into normative and informative 5. Intellectual Property and other formal aspects added for conformance = with http://www.ietf.org/ID-nits.html Joel, with these changes the document should be ready for a WG Last = Call. Thank you, Mircea. > -----Original Message----- > From: Pana, Mircea=20 > Sent: Tuesday, August 05, 2003 7:58 PM > To: 'internet-drafts@ietf.org' > Cc: 'brunner@ccrle.nec.de'; 'telabm@mat.upc.es';=20 > 'angelica@mat.upc.es'; > 'David Mor=F3n' > Subject: draft-reyes-policy-core-ext-schema-03.txt >=20 >=20 > RFC-Editor, >=20 > Please publish the attached draft-reyes-policy-core-ext-schema-03.txt >=20 > Abstract >=20 > This document defines a number of changes and extensions to the > Policy Core LDAP Schema [PCLS] based on the specifications of the > Policy Core Information Model Extensions [PCIM_EXT]. The changes > include additional object classes previously not covered,=20 > deprecation > of some object classes and changes to the object class hierarchy > defined in [PCLS]. > ------_=_NextPart_001_01C35C18.CD1287A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable draft-reyes-policy-core-ext-schema-03.txt

Policy WG, We have submitted a new revision of PCELS = that includes the following changes:

1. Request for an IANA assigned OID as recommended by = RFC 3383
2. Clarifications for potentially ambiguous = situations where both references
and attachments can be used to realize associations = (e.g. PolicySetAssociation)
3. Introduction of an extension mechanism for vendor = variables and vendor
values
4. References separated into normative and = informative
5. Intellectual Property and other formal aspects = added for conformance with
 http://www.ietf.org/ID-nits.html

Joel, with these changes the document should be ready = for a WG Last Call.

Thank you,
Mircea.

> -----Original Message-----
> From: Pana, Mircea
> Sent: Tuesday, August 05, 2003 7:58 PM
> To: 'internet-drafts@ietf.org'
> Cc: 'brunner@ccrle.nec.de'; = 'telabm@mat.upc.es';
> 'angelica@mat.upc.es';
> 'David Mor=F3n'
> Subject: = draft-reyes-policy-core-ext-schema-03.txt
>
>
> RFC-Editor,
>
> Please publish the attached = draft-reyes-policy-core-ext-schema-03.txt
>
> Abstract
>
>    This document defines a = number of changes and extensions to the
>    Policy Core LDAP Schema = [PCLS] based on the specifications of the
>    Policy Core Information Model = Extensions [PCIM_EXT]. The changes
>    include additional object = classes previously not covered,
> deprecation
>    of some object classes and = changes to the object class hierarchy
>    defined in [PCLS].
>

------_=_NextPart_001_01C35C18.CD1287A0-- _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Wed Aug 6 11:34:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21475 for ; Wed, 6 Aug 2003 11:34:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kQIg-00027w-Hq for policy-archive@odin.ietf.org; Wed, 06 Aug 2003 11:34:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h76FY60D008162 for policy-archive@odin.ietf.org; Wed, 6 Aug 2003 11:34:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kQIb-00027F-Cq; Wed, 06 Aug 2003 11:34:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19kQIS-00026v-2R for policy@optimus.ietf.org; Wed, 06 Aug 2003 11:33:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21453 for ; Wed, 6 Aug 2003 11:33:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19kQIR-0003uo-00 for policy@ietf.org; Wed, 06 Aug 2003 11:33:51 -0400 Received: from ns.execdsl.net ([208.184.15.238] helo=EXECDSL.COM) by ietf-mx with esmtp (Exim 4.12) id 19kQIQ-0003ug-00 for policy@ietf.org; Wed, 06 Aug 2003 11:33:50 -0400 Received: from [64.254.114.114] (HELO JLaptop.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 5163730 for policy@ietf.org; Wed, 06 Aug 2003 11:33:49 -0400 Message-Id: <5.1.0.14.0.20030806113124.02ed2dc0@mail.stevecrocker.com> X-Sender: joel@stevecrocker.com@mail.stevecrocker.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 06 Aug 2003 11:32:39 -0400 To: policy@ietf.org From: "Joel M. Halpern" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Policy] Re: draft-reyes-policy-core-ext-schema-03.txt Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , The revised Internet draft is now available in the I-D repository: http://www.ietf.org/internet-drafts/draft-reyes-policy-core-ext-schema-03.txt I believe it is appropriate for this document to go forward as an individual contribution that has been reviewed by a (our) working group. As such, I will give folks one more chance to comment before indicating that the author's can (and should) contact the AD for this. Please respond by August 20 (preferably sooner) with any comments, concerns, issues, etc. It would even be helpful if folks would merely indicate that they had read and liked the document. Thank you, Joel M. Halpern At 07:21 PM 8/5/2003 -0500, Pana, Mircea wrote: >Policy WG, We have submitted a new revision of PCELS (also attached below) >that includes the following changes: > >1. Request for an IANA assigned OID as recommended by RFC 3383 >2. Clarifications for potentially ambiguous situations where both references >and attachments can be used to realize associations (e.g. >PolicySetAssociation) >3. Introduction of an extension mechanism for vendor variables and vendor >values >4. References separated into normative and informative >5. Intellectual Property and other formal aspects added for conformance with > http://www.ietf.org/ID-nits.html > >Joel, with these changes the document should be ready for a WG Last Call. > >Thank you, >Mircea. _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Thu Aug 14 12:58:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18041 for ; Thu, 14 Aug 2003 12:58:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nLQQ-0004wf-55 for policy-archive@odin.ietf.org; Thu, 14 Aug 2003 12:58:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7EGwAL7018984 for policy-archive@odin.ietf.org; Thu, 14 Aug 2003 12:58:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nLQH-0004u1-DL; Thu, 14 Aug 2003 12:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nLPx-0004re-Us for policy@optimus.ietf.org; Thu, 14 Aug 2003 12:57:41 -0400 Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18026 for ; Thu, 14 Aug 2003 12:57:36 -0400 (EDT) Received: from apache by asgard.ietf.org with local (Exim 4.14) id 19nLPo-0007JX-8U; Thu, 14 Aug 2003 12:57:32 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce:; Cc: Internet Architecture Board , RFC Editor , Message-Id: Date: Thu, 14 Aug 2003 12:57:32 -0400 Subject: [Policy] Protocol Action: 'Information Model for Describing Network Device QoS Datapath Mechanisms' to Proposed Standard Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , The IESG has approved the Internet-Draft 'Information Model for Describing Network Device QoS Datapath Mechanisms' as a Proposed Standard. This document is the product of the Policy Framework Working Group. The IESG contact persons are Bert Wijnen and Randy Bush. Technical Summary The purpose of this document is to define an information model to describe the quality of service (QoS) mechanisms inherent in different network devices, including hosts. Broadly speaking, these mechanisms describe the properties common to selecting and conditioning traffic through the forwarding path (datapath) of a network device. This selection and conditioning of traffic in the datapath spans both major QoS architectures: Differentiated Services and Integrated Services. This documen should be used with the QoS Policy Information Model (QPIM) to model how policies can be defined to manage and configure the QoS mechanisms (i.e., the classification, marking, metering, dropping, queuing, and scheduling functionality) of devices. Together, these two drafts describe how to write QoS policy rules to configure and manage the QoS mechanisms present in the datapaths of devices. This document, as well as QPIM, are information models. That is, they represent information independent of a binding to a specific type of repository. Working Group Summary The Working Group has consensus on this document to be published as Proposed Standard. Protocol Quality This document has been reviewed for the IESG by Bert Wijnen RFC-Editor notes: - 2nd para of abstract OLD: This documenthis document NEW: This document - Page 2, 7th sentence OLD: Together, these two drafts NEW: Together, these two documents - Page 5, 1st para OLD: Together, these two drafts NEW: Together, these two documents - Page 5, 2nd para OLD: A separate draft could be written NEW: A separate document could be written - The word "draft occurs at several more places. It is best to change those all to "document". - Section 7 OLD: Like [PCIM} and {PCiME}, NEW: Like [PCIM] and [PCiME], - Co-Author Walter Weiss is now at: walterweiss@attbi.com _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Fri Aug 15 05:47:52 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22770 for ; Fri, 15 Aug 2003 05:47:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nbB9-0002bN-K9 for policy-archive@odin.ietf.org; Fri, 15 Aug 2003 05:47:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7F9lRa4009978 for policy-archive@odin.ietf.org; Fri, 15 Aug 2003 05:47:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nb9m-0002QB-95; Fri, 15 Aug 2003 05:46:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nb9b-0002Lw-9y for policy@optimus.ietf.org; Fri, 15 Aug 2003 05:45:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22758 for ; Fri, 15 Aug 2003 05:45:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nb9X-0001T5-00 for policy@ietf.org; Fri, 15 Aug 2003 05:45:47 -0400 Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19nb9X-0001T2-00 for policy@ietf.org; Fri, 15 Aug 2003 05:45:47 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7F9jaI28253 for ; Fri, 15 Aug 2003 04:45:37 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Aug 2003 11:45:14 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502361847@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: policy@ietf.org Subject: RE: [Policy] Re: draft-reyes-policy-core-ext-schema-03.txt Date: Fri, 15 Aug 2003 11:45:13 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , Joel asked from the WG: > -----Original Message----- > From: Joel M. Halpern [mailto:joel@stevecrocker.com] > Sent: woensdag 6 augustus 2003 17:33 > To: policy@ietf.org > Subject: [Policy] Re: draft-reyes-policy-core-ext-schema-03.txt > > > The revised Internet draft is now available in the I-D repository: > http://www.ietf.org/internet-drafts/draft-reyes-policy-core-ex > t-schema-03.txt > > I believe it is appropriate for this document to go forward as an > individual contribution that has been reviewed by a (our) working group. > As such, I will give folks one more chance to comment before indicating > that the author's can (and should) contact the AD for this. > Please respond by August 20 (preferably sooner) with any comments, > concerns, issues, etc. It would even be helpful if folks would merely > indicate that they had read and liked the document. > So did anyone actually READ (or even BROWSE) the document??? PLEASE be active and participate! Bert > Thank you, > Joel M. Halpern _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Wed Aug 27 00:44:09 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19926 for ; Wed, 27 Aug 2003 00:44:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rntU-0000R5-8m for policy-archive@odin.ietf.org; Tue, 26 Aug 2003 20:10:36 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7R0AaoN001650 for policy-archive@odin.ietf.org; Tue, 26 Aug 2003 20:10:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rmP4-0003ZG-Ub; Tue, 26 Aug 2003 18:35:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rljI-0001kn-V6 for policy@optimus.ietf.org; Tue, 26 Aug 2003 17:51:56 -0400 Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13161 for ; Tue, 26 Aug 2003 17:51:46 -0400 (EDT) Received: from apache by asgard.ietf.org with local (Exim 4.14) id 19rlgu-000202-JV; Tue, 26 Aug 2003 17:49:28 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce:; Cc: Internet Architecture Board , RFC Editor , Message-Id: Date: Tue, 26 Aug 2003 17:49:28 -0400 Subject: [Policy] Protocol Action: 'Policy QoS Information Model' to Proposed Standard Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , The IESG has approved the Internet-Draft 'Policy QoS Information Model' as a Proposed Standard. This document is the product of the Policy Framework Working Group. The IESG contact persons are Bert Wijnen and Randy Bush. Technical Summary This document presents an object-oriented information model for representing QoS network management policies. This document is based on the IETF Policy Core Information Model and its extensions. It defines an information model for QoS enforcement for differentiated and integrated services using policy. It is important to note that this document defines an information model, which by definition is independent of any particular data storage mechanism and access protocol. Working Group Summary The Working Group has consensus to publish this document as Proposed Standard. Protocol Quality This document has been reviewed for the IESG by Bert Wijnen RFC-Editor Note: Please replace the abstract with this new text: Abstract This document presents an object-oriented information model for representing QoS network management policies. This document is based on the IETF Policy Core Information Model and its extensions. It defines an information model for QoS enforcement for differentiated and integrated services using policy. It is important to note that this document defines an information model, which by definition is independent of any particular data storage mechanism and access protocol. _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Sat Aug 30 02:42:40 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25924 for ; Sat, 30 Aug 2003 02:42:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19swkD-0005H8-94 for policy-archive@odin.ietf.org; Fri, 29 Aug 2003 23:49:47 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7U3njL5020277 for policy-archive@odin.ietf.org; Fri, 29 Aug 2003 23:49:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19svBt-0000hg-S9; Fri, 29 Aug 2003 22:10:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sqCG-0003Vh-Gb for policy@optimus.ietf.org; Fri, 29 Aug 2003 16:50:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03768 for ; Fri, 29 Aug 2003 16:50:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sqCE-0006r6-00 for policy@ietf.org; Fri, 29 Aug 2003 16:50:14 -0400 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19sqCD-0006qC-00 for policy@ietf.org; Fri, 29 Aug 2003 16:50:13 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7TKneZ09906 for ; Fri, 29 Aug 2003 15:49:40 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id ; Fri, 29 Aug 2003 22:49:39 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502331450@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'Pana, Mircea'" , "'Marcus Brunner'" , "'telabm@mat.upc.es'" , "'angelica@mat.upc.es'" , "'David Moron'" Cc: "Policy (E-mail)" Date: Fri, 29 Aug 2003 22:49:38 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [Policy] AD review: draft-reyes-policy-core-ext-schema-03.txt (targeted fo r PS) Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , Here are my comments. Would be good to not only hear authors/editors responses, but also input from the WG. - RFC3460 Updates RFC3060. So would it not be logical to say/claim that this PCELS Updates PCLS ?? If so, we need to say so in the abstract with a simple, but explicit sentence: This document updates RFC zzzz -- RFC-Editor replaces zzzz with RFC number assigned to [PCLS] - Maybe I just do not understand... But is it valid to just move a class, like you moved the pcimGroup (and all that was under it) underneath a new pcimPolicySet. Would it not be more cuatious to deprecate the pcimGroup and define s pcimeGroup or such under pcimPolicySet and do something similar for the other moved groups classes? I understand that PCIM-EXT did this moving too, but that is an information model (so abstract) while this is a mapping onto a repository, so here things may get incompatible if we already have implementation of PCLS, no? - Is it wise to have (as part of this document) two Vendor specific classes that are not part of or based on PCIM-EXT ?? This doc is supposed to do the LDAP Schema defintiions for PCIM-EXT, right? So why these additions? - Is it wise to just rename classes (sect 4.2, bullet 1). Would it not be wiser to deprecate the old ones and add new ones? - There seems to be more of these things that I wonder if deprecation and adding new ones would be better. I guess I do not very well understand the impact (or non-impact) on existing implementations of the PCLS by the changes being made. Can someone explain to me. Or possibly add text to the document that describes such (non-)impact. - In section 5, I think you need to explain/define which matching rules are used and make citations to where they are defined. PCLS does that too (zeilenga-user_schema), but you probably better use: draft-zeilenga-ldap-user-schema-mr-00.txt Pls make sure that that indeed covers all matching rules. - Security Considerations Would it not be better to change the first 3 paragraphs: This topic is based on requirements from previous [PCLS] documents and also takes into account other RFCs about the same security aspects entitled as following: RFC 2829 (Authentication Methods for LDAP) RFC 2830 (Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security) These RFC documents provide a general framework for security architecture of the system. However some comments have to be provided as a consequence of the inclusion of extensions in this own document and its relation with PCLS doc. Into something like: Since this PCELS document is an update to the [PCLS] it has the same basic security considerations as the [PCLS] document. So see the Security considerations in [PCLS] first. - You may want to check the English on Page 55 (up to IANA considerations) For example: what is "obtention" ?? what is "p.e." ? I guess par example or per exemple? in English text we tend to use e.g. And for me (but I am not a security expert), I do not understand what that text on page 55 is trying to tell me. You may want to check with one of the security ADs, Russ Housley is probably the most appropriate, if this is clear and acceptable for them. - IANA Considerations. Isn't the IANA-ASSIGNED-OID the same as the one in PCLS ?? If so, we should make that clear in the document, so it is easy for IANA to see and understand. NITS: - in abstract, do not use citations as per RFC-Editor policy. It is OK to use RFC numbers. - RFC2119 (your [KEYWORDS] citation) must be a normative reference Your text on keywors on page 1 does not make a citation to this by the way. I want to get this doc reviewed by an LDAP expert (from the LDAP directorate) as well, but maybe you can try to address and/or answer the above first. Thanks, Bert _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Sat Aug 30 02:44:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26009 for ; Sat, 30 Aug 2003 02:44:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19swm9-0005Nf-87 for policy-archive@odin.ietf.org; Fri, 29 Aug 2003 23:51:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7U3pj3t020672 for policy-archive@odin.ietf.org; Fri, 29 Aug 2003 23:51:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19svBP-0000de-BU; Fri, 29 Aug 2003 22:09:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sqiu-00055a-QL for policy@optimus.ietf.org; Fri, 29 Aug 2003 17:24:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06553 for ; Fri, 29 Aug 2003 17:23:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sqis-00001y-00 for policy@ietf.org; Fri, 29 Aug 2003 17:23:58 -0400 Received: from mx-relay1.treas.gov ([199.196.144.5] helo=mx-relay1.net.treas.gov) by ietf-mx with esmtp (Exim 4.12) id 19sqir-00001u-00 for policy@ietf.org; Fri, 29 Aug 2003 17:23:57 -0400 Received: from tias5.treas.gov (tias-gw5.treas.gov [199.196.144.15]) by mx-relay1.net.treas.gov (8.12.9/8.12.9) with SMTP id h7TLNvLi003605; Fri, 29 Aug 2003 17:23:57 -0400 (EDT) Received: from mailhub.net.treas.gov by tias5.treas.gov via smtpd (for mx-relay1.treas.gov [199.196.144.5]) with SMTP; 29 Aug 2003 21:23:57 UT Received: from irsbd2.net.treas.gov (localhost [127.0.0.1]) by mailhub-4.net.treas.gov (8.12.9/8.12.9) with ESMTP id h7TLNmiJ003296; Fri, 29 Aug 2003 17:23:48 -0400 (EDT) Received: from no.name.available by irsbd2.net.treas.gov via smtpd (for mailhub.net.treas.gov [10.7.14.14]) with ESMTP; Fri, 29 Aug 2003 21:23:48 +0000 Received: from parnelli.indy.cr.irs.gov (IDENT:lsbart35@localhost [127.0.0.1]) by big-al.indy.cr.irs.gov (8.11.2/8.9.3) with ESMTP id h7TLNpf00791; Fri, 29 Aug 2003 16:23:51 -0500 Message-ID: <3F4FC466.8020902@parnelli.indy.cr.irs.gov> Date: Fri, 29 Aug 2003 16:23:50 -0500 From: "Larry S. Bartz" Organization: Internal Revenue Service User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wijnen, Bert (Bert)" CC: policy@ietf.org Subject: Re: [Policy] Re: draft-reyes-policy-core-ext-schema-03.txt References: <7D5D48D2CAA3D84C813F5B154F43B1550233144C@nl0006exch001u.nl.lucent.com> In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B1550233144C@nl0006exch001u.nl.lucent.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Wijnen, Bert (Bert) wrote, On 08/29/03 10:14: > What an underwhelming interest in this document. > > When I start reading it, I see in the abstract: > This document defines a number of changes and extensions to the > Policy Core LDAP Schema [PCLS] based on the specifications of the > Policy Core Information Model Extensions [PCIM_EXT]. The changes > include additional object classes previously not covered, deprecation > of some object classes and changes to the object class hierarchy > defined in [PCLS]. > > And so I immediately wonder... is it really OK that this document > deprecates some object classes ?? > > Possibly so... but I'd like to hear some of the PCIM, PCIM-EXT and > PCLS authors/ediotrs to explicitly say so. PLEASE! > > Thanks, > Bert I argued several months ago that it is actually unnecessary to deprecate any of PCLS's information components. There are no naming clashes with PCLS components. The proposed deprecation only insures that PCLS and this schema will not be able to co-exist in the same Directory implementations. This is counter to the spirit of "extension". It casts a negative light on an elegant and highly serviceable information model and schema definition. Further, another commenter (I believe it was Kurt Zielenga) asserted that the specification of deprecation is inappropriate in a schema standards document. Rather, deprecation is to be asserted by Directory service implementers in the course of managing instances of the Directory service. -- -- #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::| # Larry Bartz # # voice (317) 226-7060 # FAX (317) 226-6378 #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::| _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Sat Aug 30 19:00:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07496 for ; Sat, 30 Aug 2003 19:00:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19tEJP-0001Nz-Oz for policy-archive@odin.ietf.org; Sat, 30 Aug 2003 18:35:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7UMZFV5005307 for policy-archive@odin.ietf.org; Sat, 30 Aug 2003 18:35:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19tDe7-0000MJ-HO; Sat, 30 Aug 2003 17:52:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19tDB9-0007hz-Oc for policy@optimus.ietf.org; Sat, 30 Aug 2003 17:22:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02702 for ; Sat, 30 Aug 2003 17:22:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19tDB7-0000xb-00 for policy@ietf.org; Sat, 30 Aug 2003 17:22:37 -0400 Received: from tconl91223.tconl.com ([204.26.91.223]) by ietf-mx with esmtp (Exim 4.12) id 19tDB6-0000xH-00 for policy@ietf.org; Sat, 30 Aug 2003 17:22:36 -0400 Received: (from jayhawk@localhost) by tconl91223.tconl.com (8.11.6/8.11.0) id h7ULLqL01558; Sat, 30 Aug 2003 16:21:52 -0500 Date: Sat, 30 Aug 2003 16:21:52 -0500 From: Ryan Moats To: "Larry S. Bartz" Cc: "Wijnen, Bert (Bert)" , policy@ietf.org Subject: Re: [Policy] Re: draft-reyes-policy-core-ext-schema-03.txt Message-ID: <20030830162152.A1473@privateer.local.windrose.omaha.ne.us> Reply-To: rmoats@lemurnetworks.net References: <7D5D48D2CAA3D84C813F5B154F43B1550233144C@nl0006exch001u.nl.lucent.com> <3F4FC466.8020902@parnelli.indy.cr.irs.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3F4FC466.8020902@parnelli.indy.cr.irs.gov>; from lbartz@parnelli.indy.cr.irs.gov on Fri, Aug 29, 2003 at 04:23:50PM -0500 Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , On Fri, Aug 29, 2003 at 04:23:50PM -0500, Larry S. Bartz wrote: | Wijnen, Bert (Bert) wrote, On 08/29/03 10:14: | > What an underwhelming interest in this document. | > | > When I start reading it, I see in the abstract: | > This document defines a number of changes and extensions to the | > Policy Core LDAP Schema [PCLS] based on the specifications of the | > Policy Core Information Model Extensions [PCIM_EXT]. The changes | > include additional object classes previously not covered, deprecation | > of some object classes and changes to the object class hierarchy | > defined in [PCLS]. | > | > And so I immediately wonder... is it really OK that this document | > deprecates some object classes ?? | > | > Possibly so... but I'd like to hear some of the PCIM, PCIM-EXT and | > PCLS authors/ediotrs to explicitly say so. PLEASE! | > | > Thanks, | > Bert I have to admit that I'm not sold on the idea of deprecating classes for the following reasons: 1. I see no justification for why it's being proposed. 2. Most of the deprecations I see could be handled via inheritance and semantics changes. This would allow the items wanted without changing the parent objects. Ryan Moats _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Sun Aug 31 14:02:13 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10278 for ; Sun, 31 Aug 2003 14:02:13 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19tWMU-0005zb-FV for policy-archive@odin.ietf.org; Sun, 31 Aug 2003 13:51:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7VHpc23023032 for policy-archive@odin.ietf.org; Sun, 31 Aug 2003 13:51:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19tWI1-0005vr-Md; Sun, 31 Aug 2003 13:47:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s8Hz-0002xO-4C for policy@optimus.ietf.org; Wed, 27 Aug 2003 17:57:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11678; Wed, 27 Aug 2003 17:57:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19s8Hw-0001Nv-00; Wed, 27 Aug 2003 17:57:12 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 19s8Hv-0001Nr-00; Wed, 27 Aug 2003 17:57:11 -0400 Received: from jet.isi.edu (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.6p2/8.11.2) with ESMTP id h7RLv6n04632; Wed, 27 Aug 2003 14:57:06 -0700 (PDT) Received: (from rfc-ed@localhost) by jet.isi.edu (8.9.3/8.8.6) id OAA17448; Wed, 27 Aug 2003 14:57:06 -0700 (PDT) Date: Wed, 27 Aug 2003 14:57:06 -0700 From: RFC Editor To: The IESG Cc: IETF-Announce: ;, Internet Architecture Board , policy@ietf.org, RFC Editor Message-ID: <20030827215706.GD17271@isi.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Subject: [Policy] Re: Protocol Action: 'Policy QoS Information Model' to Proposed Standard Sender: policy-admin@ietf.org Errors-To: policy-admin@ietf.org X-BeenThere: policy@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Aug 26, 2003 at 05:49:28PM -0400, The IESG wrote: > The IESG has approved the Internet-Draft 'Policy QoS Information Model' > as a Proposed Standard. This > document is the product of the Policy Framework Working Group. > > The IESG contact persons are Bert Wijnen and Randy Bush. > > Technical Summary > > This document presents an object-oriented information model for > representing QoS network management policies. This document is > based on the IETF Policy Core Information Model and its > extensions. It defines an information model for QoS enforcement > for differentiated and integrated services using policy. > It is important to note that this document defines an information > model, which by definition is independent of any particular data > storage mechanism and access protocol. > > Working Group Summary > > The Working Group has consensus to publish this document as Proposed > Standard. > > Protocol Quality > > This document has been reviewed for the IESG by Bert Wijnen > > RFC-Editor Note: > > Please replace the abstract with this new text: > > Abstract > > This document presents an object-oriented information model for > representing QoS network management policies. This document is > based on the IETF Policy Core Information Model and its > extensions. It defines an information model for QoS enforcement > for differentiated and integrated services using policy. > It is important to note that this document defines an information > model, which by definition is independent of any particular data > storage mechanism and access protocol. _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy