From daemon@optimus.ietf.org  Thu Jul  4 06:42:01 2002
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 GAA13730
	for <policy-archive@odin.ietf.org>; Thu, 4 Jul 2002 06:42:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA11081
	for policy-archive@odin.ietf.org; Thu, 4 Jul 2002 06:42:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA10772;
	Thu, 4 Jul 2002 06:33:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA10741
	for <policy@optimus.ietf.org>; Thu, 4 Jul 2002 06:33:08 -0400 (EDT)
Received: from wiprom2mx1.wipro.com (wiprom2mx1.wipro.com [203.197.164.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13565
	for <policy@ietf.org>; Thu, 4 Jul 2002 06:32:18 -0400 (EDT)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id g64AWSe15769
	for <policy@ietf.org>; Thu, 4 Jul 2002 16:02:28 +0530 (IST)
Received: from mdppbms31877 ([192.168.34.38]) by
          vindhya.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GYPZY000.AWQ for <policy@ietf.org>; Thu, 4 Jul 2002
          16:02:24 +0530 
Reply-To: <pratap.chilukuri@wipro.com>
From: "Chilukuri Narasimha Pratap" <pratap.chilukuri@wipro.com>
To: <policy@ietf.org>
Date: Thu, 4 Jul 2002 16:14:58 +0530
Message-ID: <NGBBKIGGBDIOKBDOGDLBMEGCCDAA.pratap.chilukuri@wipro.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Policy] QPIM
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

Can you please tell the status of the QPIM draft? Now the current QPIM draft
has expired on May 2002.

Regards
Pratap


_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Thu Jul  4 11:36:11 2002
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 LAA19736
	for <policy-archive@odin.ietf.org>; Thu, 4 Jul 2002 11:36:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA25952
	for policy-archive@odin.ietf.org; Thu, 4 Jul 2002 11:36:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25367;
	Thu, 4 Jul 2002 11:30:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25330
	for <policy@optimus.ietf.org>; Thu, 4 Jul 2002 11:30:06 -0400 (EDT)
Received: from ams-msg-core-1.cisco.com (ams-msg-core-1.cisco.com [144.254.74.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19652
	for <policy@ietf.org>; Thu, 4 Jul 2002 11:29:17 -0400 (EDT)
Received: from kaspit.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g64FSnGn029199;
	Thu, 4 Jul 2002 17:28:50 +0200 (MET DST)
Received: from YSNIRW2K ([10.56.232.8])
	by kaspit.cisco.com (Mirapoint)
	with SMTP id AAO04026;
	Thu, 4 Jul 2002 18:30:12 +0200 (IST)
Reply-To: <ysnir@cisco.com>
From: "Yoram Snir" <ysnir@cisco.com>
To: <pratap.chilukuri@wipro.com>, <policy@ietf.org>
Subject: RE: [Policy] QPIM
Date: Thu, 4 Jul 2002 18:32:30 +0200
Message-ID: <001101c22378$6509bd60$040a0a0a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <NGBBKIGGBDIOKBDOGDLBMEGCCDAA.pratap.chilukuri@wipro.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org
Content-Transfer-Encoding: 7bit

QPIM was submitted to the IESG for approval as a proposed standard a few
months ago.
Yoram


> -----Original Message-----
> From: policy-admin@ietf.org [mailto:policy-admin@ietf.org]On Behalf Of
> Chilukuri Narasimha Pratap
> Sent: Thu, July 04, 2002 12:45 PM
> To: policy@ietf.org
> Subject: [Policy] QPIM
>
>
>
> Hi,
>
> Can you please tell the status of the QPIM draft? Now the
> current QPIM draft
> has expired on May 2002.
>
> Regards
> Pratap
>
>
> _______________________________________________
> Policy mailing list
> Policy@ietf.org
> https://www1.ietf.org/mailman/listinfo/policy


_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Tue Jul  9 17:22:39 2002
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 RAA18012
	for <policy-archive@odin.ietf.org>; Tue, 9 Jul 2002 17:22:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA10227
	for policy-archive@odin.ietf.org; Tue, 9 Jul 2002 17:23:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA09730;
	Tue, 9 Jul 2002 17:15:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA09694
	for <policy@optimus.ietf.org>; Tue, 9 Jul 2002 17:15:45 -0400 (EDT)
Received: from mail.sandvine.com (hidden-user@sandvine.com [199.243.201.138])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17750
	for <policy@ietf.org>; Tue, 9 Jul 2002 17:14:49 -0400 (EDT)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19)
	id <NGG7TC12>; Tue, 9 Jul 2002 17:15:35 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337814EEB@mail.sandvine.com>
From: David McTavish <dmctavish@SANDVINE.com>
To: "'policy@ietf.org'" <policy@ietf.org>
Date: Tue, 9 Jul 2002 17:15:33 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2278D.C2FEDDB0"
Subject: [Policy] Policy LDAP Schema
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C2278D.C2FEDDB0
Content-Type: text/plain;
	charset="iso-8859-1"


I was wondering if there was any progress in obtaining OID's and definitions
for the LDAP implementation of the Policy schema.
(http://www.ietf.org/internet-drafts/draft-ietf-policy-core-schema-14.txt).
My company is basing our schema on the PCIM model and would like to
implement soon.  Any idea on when OID's will be obtained, or what they are
would be greatly appreciated.  In the interim, I have been using my own
company OID to have a usable schema. Please feel free to replace the
Sandvine PCIM OID's (1.3.6.1.4.1.11610.2) with the proper IANA-sponsored
PCIM OID.



Regards,
David McTavish



 <<pcim.schema>> 


------_=_NextPart_000_01C2278D.C2FEDDB0
Content-Type: application/octet-stream;
	name="pcim.schema"
Content-Disposition: attachment;
	filename="pcim.schema"
Content-Transfer-Encoding: quoted-printable

attributeType ( 1.3.6.1.4.1.11610.2.2
    NAME 'pcimKeywords'
    DESC 'A set of keywords to assist directory clients in=20
          locating the policy objects applicable to them.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20
 )

objectClass ( 1.3.6.1.4.1.11610.2.1
    NAME 'pcimPolicy'
    DESC 'An abstract class that is the base class for all classes=20
          that describe policy-related instances.'
    SUP top
    ABSTRACT
    MAY ( cn $ pcimKeywords )
 )

attributeType ( 1.3.6.1.4.1.11610.2.4
    NAME 'pcimGroupName'
    DESC 'The user-friendly name of this policy group.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.3
    NAME 'pcimGroup'
    DESC 'A container for a set of related pcimRules and/or
         a set of related pcimGroups.'
    SUP pcimPolicy
    ABSTRACT
    MAY ( pcimGroupName )
 )

objectClass ( 1.3.6.1.4.1.11610.2.5
    NAME 'pcimGroupAuxClass'
    DESC 'An auxiliary class that collects a set of related=20
         pcimRule and/or pcimGroup entries.'
    SUP pcimGroup
    AUXILIARY
 )

attributeType ( 1.3.6.1.4.1.11610.2.7
    NAME 'pcimRuleName'
    DESC 'The user-friendly name of this policy rule.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.8
    NAME 'pcimRuleEnabled'
    DESC 'An integer indicating whether a policy rule is =
administratively enabled 1 disabled
         2 or enabled for debug 3.'
    EQUALITY integerMatch
    ORDERING caseIgnoreOrderingMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.9
    NAME 'pcimRuleConditionListType'
    DESC 'A value of 1 means that this policy rule is in=20
         disjunctive normal form; a value of 2 means that this
         policy rule is in conjunctive normal form.'
    EQUALITY integerMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.10
    NAME 'pcimRuleConditionList'
    DESC 'Unordered set of DNs of pcimRuleConditionAssociation=20
         entries representing associations between this policy =20
         rule and its conditions.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
 )

attributeType ( 1.3.6.1.4.1.11610.2.11
    NAME 'pcimRuleActionList'
    DESC 'Unordered set of DNs of pcimRuleActionAssociation=20
         entries representing associations between this policy
         rule and its actions.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
 )


attributeType ( 1.3.6.1.4.1.11610.2.12
    NAME 'pcimRuleValidityPeriodList'
    DESC 'Unordered set of DNs of pcimRuleValidityAssociation
         entries that determine when the pcimRule is scheduled
         to be active or inactive.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
 )

attributeType ( 1.3.6.1.4.1.11610.2.13
    NAME 'pcimRuleUsage'
    DESC 'This attribute is a free-form sting providing=20
         guidelines on how this policy should be used.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.14
    NAME 'pcimRulePriority'
    DESC 'A non-negative integer for prioritizing this =20
         pcimRule relative to other pcimRules. A larger=20
         value indicates a higher priority.'
    EQUALITY integerMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.15
    NAME 'pcimRuleMandatory'
    DESC 'If TRUE, indicates that for this policy rule, the =20
         evaluation of its conditions and execution of its=20
         actions (if the condition is satisfied) is required.'
    EQUALITY booleanMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.16
    NAME 'pcimRuleSequencedActions'
    DESC 'An integer enumeration indicating that the ordering of=20
         actions defined by the pcimActionOrder attribute is
         mandatory(1), recommended(2), or dontCare(3).'
    EQUALITY integerMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.17
    NAME 'pcimRoles'
    DESC 'Each value of this attribute represents a role-
         combination.'
    EQUALITY caseIgnoreMatch=09
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
 )

objectClass ( 1.3.6.1.4.1.11610.2.6
    NAME 'pcimRule'
    DESC 'The base class for representing the "If Condition
         then Action" semantics associated with a policy rule.'
    SUP pcimPolicy=09
    ABSTRACT
    MAY ( pcimRuleName $ pcimRuleEnabled $=20
          pcimRuleConditionListType $ pcimRuleConditionList $ =20
          pcimRuleActionList $ pcimRuleValidityPeriodList $ =20
          pcimRuleUsage $ pcimRulePriority $ =20
          pcimRuleMandatory $ pcimRuleSequencedActions $ =20
          pcimRoles )
 )

objectClass ( 1.3.6.1.4.1.11610.2.18
    NAME 'pcimRuleAuxClass'
    DESC 'An auxiliary class for representing the If Condition
         then Action semantics associated with a policy rule.'
    SUP pcimRule
    AUXILIARY
 )

objectClass ( 1.3.6.1.4.1.11610.2.19
    NAME 'pcimRuleInstance'
    DESC 'A structural class for representing the If Condition
         then Action semantics associated with a policy rule.'
    SUP pcimRule
    STRUCTURAL
 )

attributeType ( 1.3.6.1.4.1.11610.2.21
    NAME 'pcimConditionGroupNumber'
    DESC 'The number of the group to which a policy condition
          belongs.  This is used to form the DNF or CNF =20
          expression associated with a policy rule.'
    EQUALITY integerMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.22
    NAME 'pcimConditionNegated'
    DESC 'If TRUE (FALSE), it indicates that a policy condition
          IS (IS NOT) negated in the DNF or CNF expression =20
          associated with a policy rule.'
    EQUALITY booleanMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.23
    NAME 'pcimConditionName'
    DESC 'A user-friendly name for a policy condition.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.24
    NAME 'pcimConditionDN'
    DESC 'A DN that references an instance of a reusable policy=20
          condition.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.20
    NAME 'pcimRuleConditionAssociation'
    DESC 'This class contains attributes characterizing the
          relationship between a policy rule and one of its
          policy conditions.'
    SUP pcimPolicy
    MUST ( pcimConditionGroupNumber $ pcimConditionNegated )
    MAY ( pcimConditionName $ pcimConditionDN )
 )

attributeType ( 1.3.6.1.4.1.11610.2.26
    NAME 'pcimValidityConditionName'
    DESC 'A user-friendly name for identifying an instance of=20
          a pcimRuleValidityAssociation entry.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.27
    NAME 'pcimTimePeriodConditionDN'
    DESC 'A reference to a reusable policy time period
          condition.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.25
    NAME 'pcimRuleValidityAssociation'
    DESC 'This defines the scheduled activation or deactivation =20
          of a policy rule.'
    SUP pcimPolicy
    STRUCTURAL
    MAY ( pcimValidityConditionName $ pcimTimePeriodConditionDN )
 )


attributeType ( 1.3.6.1.4.1.11610.2.29
    NAME 'pcimActionName'
    DESC 'A user-friendly name for a policy action.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.30
    NAME 'pcimActionOrder'
    DESC 'An integer indicating the relative order of an action
          in the context of a policy rule.'
    EQUALITY integerMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.31
    NAME 'pcimActionDN'
    DESC 'A DN that references a reusable policy action.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.28
    NAME 'pcimRuleActionAssociation'
    DESC 'This class contains attributes characterizing the
          relationship between a policy rule and one of its
          policy actions.'
    SUP pcimPolicy
    MUST ( pcimActionOrder )
    MAY ( pcimActionName $ pcimActionDN )
 )

objectClass ( 1.3.6.1.4.1.11610.2.32
    NAME 'pcimConditionAuxClass'
    DESC 'A class representing a condition to be evaluated in
          conjunction with a policy rule.'
    SUP pcimPolicy
    AUXILIARY
    MAY ( cn )
 )

attributeType ( 1.3.6.1.4.1.11610.2.34
    NAME 'pcimTPCTime'
    DESC 'The start and end times on which a policy rule is
          valid. Date formatting is:
          yyyymmddThhmmss/yyyymmddThhmmss
          where THISANDPRIOR and THISANDFUTURE can be substituted
          for start and end times.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.44
    SINGLE-VALUE
 )


attributeType ( 1.3.6.1.4.1.11610.2.35
    NAME 'pcimTPCMonthOfYearMask'
    DESC 'This identifies the valid months of the year for a
          policy rule using a 12-bit octect string that represents=20
          the months of the year from January through December.
          This property is formatted as follows:
               - 4-octect length field always set to 0x00000006
               - 2-octect field consisting of 12 bits identifying=20
                 the 12 months of the year, Jan-Dec, followed by 4=20
                 zero bits.
          A 1 value indicates the policy is valid for that month,=20
          with 0 indicating that it is not valid.'
    EQUALITY bitStringMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.6
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.36
    NAME 'pcimTPCDayOfMonthMask'
    DESC 'This identifies the valid days of the month for a
          policy rule using a 62-bit octect string. The first 31=20
          positions represent the days of the month in ascending=20
          order, and the next 31 positions represent the days of
          the month in descending order.
          This property is formatted as follows:
               - a 4-octect length field always set to 0x0000000C
               - an 8-octect field consisting of 62 day bits and
                 2 bits which are always zero.'
    EQUALITY bitStringMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.6
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.37
    NAME 'pcimTPCDayOfWeekMask'
    DESC 'This identifies the valid days of the week for a
          policy rule using a 7-bit string. This represents=20
          the days of the week from Sunday through Saturday.
          This property is formatted as follows:
               - a 4-octect length field always set to 0x00000005
               - a 1-octect field consisting of 7 bits identifying
                 the days followed by a zero bit.'
    EQUALITY bitStringMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.6
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.38
    NAME 'pcimTPCTimeOfDayMask'
    DESC 'This identifies the valid range of times for a policy =20
          using the format Thhmmss/Thhmmss.'
    EQUALITY caseIgnoreMatch=20
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.44
    SINGLE-VALUE
 )

attributeType ( 1.3.6.1.4.1.11610.2.39
    NAME 'pcimTPCLocalOrUtcTime'
    DESC 'This defines whether the times in this instance=20
          represent local (value=3D1) times or UTC (value=3D2)=20
          times.'
    EQUALITY integerMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.33
    NAME 'pcimTPCAuxClass'
    DESC 'This provides the capability of enabling or disabling=20
          a policy rule according to a predetermined schedule.'
    SUP pcimConditionAuxClass
    AUXILIARY
    MAY ( pcimTPCTime $ pcimTPCMonthOfYearMask $=20
          pcimTPCDayOfMonthMask $ pcimTPCDayOfWeekMask $=20
          pcimTPCTimeOfDayMask $ pcimTPCLocalOrUtcTime )
 )

attributeType ( 1.3.6.1.4.1.11610.2.41
    NAME 'pcimVendorConstraintData'
    DESC 'Mechanism for representing constraints that have not
          been modeled as specific attributes. Their format is=20
          identified by the OID stored in the attribute =20
          pcimVendorConstraintEncoding.'
    EQUALITY octetStringMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
 )

attributeType ( 1.3.6.1.4.1.11610.2.42
    NAME 'pcimVendorConstraintEncoding'
    DESC 'An OID identifying the format and semantics for the
          pcimVendorConstraintData for this instance.'
    EQUALITY objectIdentifierMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.38
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.40
    NAME 'pcimConditionVendorAuxClass'
    DESC 'A class that defines a registered means to describe a
          policy condition.'
    SUP pcimConditionAuxClass
    AUXILIARY
    MAY ( pcimVendorConstraintData $
          pcimVendorConstraintEncoding )
 )

objectClass ( 1.3.6.1.4.1.11610.2.43
    NAME 'pcimActionAuxClass'
    DESC 'A class representing an action to be performed as a
          result of a policy rule.'
    SUP top
    AUXILIARY
    MAY ( cn )
 )

attributeType ( 1.3.6.1.4.1.11610.2.45
    NAME 'pcimVendorActionData'
    DESC ' Mechanism for representing policy actions that have =20
           not been modeled as specific attributes. Their format=20
           is identified by the OID stored in the attribute =20
           pcimVendorActionEncoding.'
    EQUALITY octetStringMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
 )

attributeType ( 1.3.6.1.4.1.11610.2.46
    NAME 'pcimVendorActionEncoding'
    DESC 'An OID identifying the format and semantics for the
          pcimVendorActionData attribute of this instance.'
    EQUALITY objectIdentifierMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.38
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.44
    NAME 'pcimActionVendorAuxClass'
    DESC 'A class that defines a registered means to describe a
          policy action.'
    SUP pcimActionAuxClass
    AUXILIARY
    MAY ( pcimVendorActionData $ pcimVendorActionEncoding )
 )

attributeType ( 1.3.6.1.4.1.11610.2.48
    NAME 'pcimPolicyInstanceName'
    DESC 'The user-friendly name of this policy instance.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.47
    NAME 'pcimPolicyInstance'
    DESC 'A structural class to which aux classes containing
          reusable policy information can be attached.'
    SUP pcimPolicy
    MAY ( pcimPolicyInstanceName )
 )

objectClass ( 1.3.6.1.4.1.11610.2.49
    NAME 'pcimElementAuxClass'
    DESC 'An auxiliary class used to tag instances of classes
          defined outside the realm of policy as relevant to a
          particular policy specification.'
    SUP pcimPolicy
    AUXILIARY
 )


attributeType ( 1.3.6.1.4.1.11610.2.51
    NAME 'pcimRepositoryName'
    DESC 'The user-friendly name of this policy repository.'
    EQUALITY caseIgnoreMatch
    ORDERING caseIgnoreOrderingMatch
    SUBSTR caseIgnoreSubstringsMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
    SINGLE-VALUE
 )

objectClass ( 1.3.6.1.4.1.11610.2.50
    NAME 'pcimRepository'
    DESC 'A container for reusable policy information.'
    SUP top
    ABSTRACT
    MAY ( pcimRepositoryName )
 )


objectClass( 1.3.6.1.4.1.11610.2.52
    NAME 'pcimRepositoryAuxClass'
    DESC 'An auxiliary class that can be used to aggregate=20
          reusable policy information.'
    SUP pcimRepository
    AUXILIARY
 )

objectClass ( 1.3.6.1.4.1.11610.2.53
    NAME 'pcimRepositoryInstance'
    DESC 'A structural class that can be used to aggregate=20
          reusable policy information.'
    SUP pcimRepository
    STRUCTURAL
 )


attributeType ( 1.3.6.1.4.1.11610.2.55
    NAME 'pcimSubtreesAuxContainedSet'
    DESC 'DNs of objects that serve as roots for DIT subtrees=20
          containing policy-related objects.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
 )

objectClass ( 1.3.6.1.4.1.11610.2.54
    NAME 'pcimSubtreesPtrAuxClass'
    DESC 'An auxiliary class providing DN references to roots of
          DIT subtrees containing policy-related objects.'
    SUP top
    AUXILIARY
    MAY ( pcimSubtreesAuxContainedSet )
 )

attributeType ( 1.3.6.1.4.1.11610.2.57
    NAME 'pcimGroupsAuxContainedSet'
    DESC 'DNs of pcimGroups associated in some way with the =20
          instance to which this attribute has been appended.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
 )

objectClass ( 1.3.6.1.4.1.11610.2.56
    NAME 'pcimGroupContainmentAuxClass'
    DESC 'An auxiliary class used to bind pcimGroups to an
          appropriate container object.'
    SUP top
    AUXILIARY
    MAY ( pcimGroupsAuxContainedSet )
 )


attributeType ( 1.3.6.1.4.1.11610.2.59
    NAME 'pcimRulesAuxContainedSet'
    DESC 'DNs of pcimRules associated in some way with the=20
          instance to which this attribute has been appended.'
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
 )

objectClass ( 1.3.6.1.4.1.11610.2.58
    NAME 'pcimRuleContainmentAuxClass'
    DESC 'An auxiliary class used to bind pcimRules to an
          appropriate container object.'
    SUP top
    AUXILIARY
    MAY ( pcimRulesAuxContainedSet )
 )

------_=_NextPart_000_01C2278D.C2FEDDB0--

_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Wed Jul 10 01:33:54 2002
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 BAA28617
	for <policy-archive@odin.ietf.org>; Wed, 10 Jul 2002 01:33:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA14696
	for policy-archive@odin.ietf.org; Wed, 10 Jul 2002 01:34:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA14611;
	Wed, 10 Jul 2002 01:31:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA14581
	for <policy@optimus.ietf.org>; Wed, 10 Jul 2002 01:31:47 -0400 (EDT)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28569
	for <policy@ietf.org>; Wed, 10 Jul 2002 01:30:54 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g6A5VFI19197
	for <policy@ietf.org>; Wed, 10 Jul 2002 01:31:15 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <3GTGZY8K>; Wed, 10 Jul 2002 07:31:14 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E657069@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: David McTavish <dmctavish@sandvine.com>,
        "'policy@ietf.org'"
	 <policy@ietf.org>
Subject: RE: [Policy] Policy LDAP Schema
Date: Wed, 10 Jul 2002 07:31:12 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org

This document is in the IESG queue and being processes.

The IANA normally makes the final assignments just before the
documents get published as RFC. So it may take another couple
of months before that happens.

Bert 

> -----Original Message-----
> From: David McTavish [mailto:dmctavish@sandvine.com]
> Sent: dinsdag 9 juli 2002 23:16
> To: 'policy@ietf.org'
> Subject: [Policy] Policy LDAP Schema
> 
> 
> 
> I was wondering if there was any progress in obtaining OID's 
> and definitions
> for the LDAP implementation of the Policy schema.
> (http://www.ietf.org/internet-drafts/draft-ietf-policy-core-sc
> hema-14.txt).
> My company is basing our schema on the PCIM model and would like to
> implement soon.  Any idea on when OID's will be obtained, or 
> what they are
> would be greatly appreciated.  In the interim, I have been 
> using my own
> company OID to have a usable schema. Please feel free to replace the
> Sandvine PCIM OID's (1.3.6.1.4.1.11610.2) with the proper 
> IANA-sponsored
> PCIM OID.
> 
> 
> 
> Regards,
> David McTavish
> 
> 
> 
>  <<pcim.schema>> 
> 
> 

_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Wed Jul 10 09:37:48 2002
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 JAA02123
	for <policy-archive@odin.ietf.org>; Wed, 10 Jul 2002 09:37:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA24469
	for policy-archive@odin.ietf.org; Wed, 10 Jul 2002 09:38:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23529;
	Wed, 10 Jul 2002 09:28:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23505
	for <policy@optimus.ietf.org>; Wed, 10 Jul 2002 09:28:08 -0400 (EDT)
Received: from mx-relay21.treas.gov (mx-relay21.treas.gov [199.196.132.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01827
	for <policy@ietf.org>; Wed, 10 Jul 2002 09:27:14 -0400 (EDT)
Received: from TIAS24.net.treas.gov (tias24.treas.gov [199.196.132.24])
	by mx-relay21.treas.gov (8.12.3/8.12.3) with SMTP id g6ADIQ8E028490;
	Wed, 10 Jul 2002 09:18:27 -0400 (EDT)
Received: from mailhub-22.net.treas.gov by TIAS24.net.treas.gov
          via smtpd (for [199.196.132.5]) with SMTP; 10 Jul 2002 13:28:05 UT
Received: from irsbd1.net.treas.gov (localhost [127.0.0.1])
	by mailhub-22.net.treas.gov (8.12.3/8.12.3) with SMTP id g6ADS4aA027615;
	Wed, 10 Jul 2002 09:28:04 -0400 (EDT)
Received: from no.name.available by irsbd1.net.treas.gov
          via smtpd (for mailhub.net.treas.gov [10.13.252.12]) with SMTP; 10 Jul 2002 13:28:04 UT
Received: from parnelli.indy.cr.irs.gov (localhost.localdomain [127.0.0.1])
	by mears.indy.cr.irs.gov (8.11.6/8.11.6) with ESMTP id g6ADS4216873;
	Wed, 10 Jul 2002 08:28:04 -0500
Message-ID: <3D2C3663.5090409@parnelli.indy.cr.irs.gov>
Date: Wed, 10 Jul 2002 08:28:03 -0500
From: "Larry S. Bartz" <lbartz@parnelli.indy.cr.irs.gov>
Organization: IRS Directory Services
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF Policy WG LIST <policy@ietf.org>
CC: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: Re: [Policy] Policy LDAP Schema
References: <A451D5E6F15FD211BABC0008C7FAD7BC0E657069@nl0006exch003u.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-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org
Content-Transfer-Encoding: 7bit

Bert and all,

http://www.ops.ietf.org/draft-status.html  indicates Kurt Zeilenga is in
possession of the draft on behalf of the IESG. A month ago, I asked Kurt
about the status of the draft. Here is what he said:

Kurt D. Zeilenga wrote, On 06/07/2002 12:10 PM:
 > As far as I know, the AD is awaiting for submission of a
 > revised I-D to address a number of issues.  These include
 > clarifications associated with the I-D's normative reference
 > to DSP0123, an "external specification" and the addition of
 > an "IANA Considerations" section.

My query http://atm.tut.fi/list-archive/policy/msg00697.html and Kurt's
reply http://atm.tut.fi/list-archive/policy/msg00698.html both posted
to this list.

When Kurt's reply did not elicit a reponse from the draft's authors,
I posted this followup: http://atm.tut.fi/list-archive/policy/msg00701.html
which also failed to elicit a response from the draft's authors.

On Monday of this week, I had a private conversation with one of
the draft's authors. He indicated surprise that the  "external 
specification"
issue was still a hangup. The draft's normative reference to the DMTF's
DSP0123 had been thoroughly discussed in this forum last November.

What is going on here? Is the delay in advancing PCLS due to a
miscommunication, or is there really an unresolved issue?

-- 
--
#::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::|
# Larry Bartz                           |                              |
#  lsbartz@parnelli.indy.cr.irs.gov     | Ooo, ooo,                    |
#                                       | Ooo, ooo, oooooo!            |
#                                       | I've got a gnu attitude!     |
#  voice (317) 226-7060                 |                              |
#  FAX   (317) 226-6378                 |                              |
#::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::|


 

Wijnen, Bert (Bert) wrote, On 07/10/2002 12:31 AM:

>This document is in the IESG queue and being processes.
>
>The IANA normally makes the final assignments just before the
>documents get published as RFC. So it may take another couple
>of months before that happens.
>
>Bert 
>
>  
>
>>-----Original Message-----
>>From: David McTavish [mailto:dmctavish@sandvine.com]
>>Sent: dinsdag 9 juli 2002 23:16
>>To: 'policy@ietf.org'
>>Subject: [Policy] Policy LDAP Schema
>>
>>
>>
>>I was wondering if there was any progress in obtaining OID's 
>>and definitions
>>for the LDAP implementation of the Policy schema.
>>(http://www.ietf.org/internet-drafts/draft-ietf-policy-core-sc
>>hema-14.txt).
>>My company is basing our schema on the PCIM model and would like to
>>implement soon.  Any idea on when OID's will be obtained, or 
>>what they are
>>would be greatly appreciated.  In the interim, I have been 
>>using my own
>>company OID to have a usable schema. Please feel free to replace the
>>Sandvine PCIM OID's (1.3.6.1.4.1.11610.2) with the proper 
>>IANA-sponsored
>>PCIM OID.
>>
>>
>>
>>Regards,
>>David McTavish
>>
>>
>>
>> <<pcim.schema>> 
>>
>>
>>    
>>
>
>_______________________________________________
>Policy mailing list
>Policy@ietf.org
>https://www1.ietf.org/mailman/listinfo/policy
>  
>



_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Tue Jul 16 23:06:38 2002
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 XAA10018
	for <policy-archive@odin.ietf.org>; Tue, 16 Jul 2002 23:06:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA12619
	for policy-archive@odin.ietf.org; Tue, 16 Jul 2002 23:07:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA12045;
	Tue, 16 Jul 2002 23:00:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11976
	for <policy@optimus.ietf.org>; Tue, 16 Jul 2002 23:00:43 -0400 (EDT)
Received: from longmail2.lboard.com ([63.109.116.89])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09814
	for <policy@ietf.org>; Tue, 16 Jul 2002 22:59:45 -0400 (EDT)
Received: by longmail2.lboard.com with Internet Mail Service (5.5.2650.21)
	id <PBPF526X>; Tue, 16 Jul 2002 23:00:41 -0400
Message-ID: <F2F760C942EBD411B98800A0CC733FCF2FCF97@longmail2.lboard.com>
From: Ed Ellesson <eellesson@lboard.com>
To: "'David McTavish'" <dmctavish@SANDVINE.com>,
        "'Larry S. Bartz'"
	 <lbartz@parnelli.indy.cr.irs.gov>
Cc: "'policy@ietf.org'" <policy@ietf.org>
Subject: RE: [Policy] Policy LDAP Schema
Date: Tue, 16 Jul 2002 23:00:41 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org

David and Larry,  

Thank you for your queries about the status of PCLS.  

We have worked out a schedule for updating the PCLS draft based on feedback
we received as a result of the IESG review.  These updates are not expected
to significantly change the technical contents of the document.  We will be
including updated references to the DMTF documentation, and any other
changes/corrections which we have been made aware of since its review by the
IESG.   We expect that these changes will allow the document to proceed to
publication as a proposed standard RFC, including the assignment of OID's.


Our schedule calls for posting a new version of the draft by the end of
July, and then we plan to resubmit that to the IESG for consideration for
advancement to proposed standard.  Bob Moore and I will be doing the
editing.  

Sorry for the delay.  

Thanks, 
Ed Ellesson 



_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Tue Jul 30 09:55:08 2002
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 JAA18349
	for <policy-archive@odin.ietf.org>; Tue, 30 Jul 2002 09:55:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA26758
	for policy-archive@odin.ietf.org; Tue, 30 Jul 2002 09:56:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26559;
	Tue, 30 Jul 2002 09:51:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26526
	for <policy@optimus.ietf.org>; Tue, 30 Jul 2002 09:51:56 -0400 (EDT)
Received: from mail.sandvine.com (hidden-user@sandvine.com [199.243.201.138])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18092
	for <policy@ietf.org>; Tue, 30 Jul 2002 09:50:48 -0400 (EDT)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19)
	id <PH2VZZR1>; Tue, 30 Jul 2002 09:51:56 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337814F70@mail.sandvine.com>
From: David McTavish <dmctavish@SANDVINE.com>
To: "'Larry S. Bartz'" <lbartz@parnelli.indy.cr.irs.gov>,
        IETF Policy WG LIST <policy@ietf.org>
Date: Tue, 30 Jul 2002 09:51:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Policy] PcimRuleList and PcimPolicyList
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org



Just reposting this request/comment seeming as my first attempt was not
acknowledged. Is there any consideration being placed on adding a
PcimRuleList attribute to a PcimPolicy object, and in that same light, is
there any thought on supporting a PcimPolicyList attribute? It seems that
the concept of supporting repository-based policies should be extended to be
fully functional rather than the current implementation.

Any comments would be appreciated.

Regards,
David McTavish

_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Tue Jul 30 10:41:50 2002
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 KAA21469
	for <policy-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:41:50 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA00699
	for policy-archive@odin.ietf.org; Tue, 30 Jul 2002 10:42:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00318;
	Tue, 30 Jul 2002 10:37:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00274
	for <policy@optimus.ietf.org>; Tue, 30 Jul 2002 10:37:55 -0400 (EDT)
Received: from tokyo.ccrle.nec.de (tokyo.ccrle.nec.de [195.37.70.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21050
	for <policy@ietf.org>; Tue, 30 Jul 2002 10:36:47 -0400 (EDT)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace [192.168.102.1])
	by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g6UEb7U60892;
	Tue, 30 Jul 2002 16:37:07 +0200 (CEST)
	(envelope-from brunner@ccrle.nec.de)
Received: from imap.heidelberg.ccrle.nec.de (imap.heidelberg.ccrle.nec.de [192.168.102.11])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA01594;
	Tue, 30 Jul 2002 16:37:06 +0200
Received: from [192.168.102.207] (marcus.heidelberg.ccrle.nec.de [192.168.102.207])
	by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0) with ESMTP
	id B43E52E66A; Tue, 30 Jul 2002 16:37:04 +0200 (CEST)
Date: Tue, 30 Jul 2002 16:37:05 +0200
From: Marcus Brunner <brunner@ccrle.nec.de>
Reply-To: brunner@ccrle.nec.de
To: David McTavish <dmctavish@SANDVINE.com>,
        "'Larry S. Bartz'" <lbartz@parnelli.indy.cr.irs.gov>,
        IETF Policy WG LIST <policy@ietf.org>
Subject: Re: [Policy] PcimRuleList and PcimPolicyList
Message-ID: <24618679.1028047025@[192.168.102.207]>
In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C85337814F70@mail.sandvine.com>
References:  <FE045D4D9F7AED4CBFF1B3B813C85337814F70@mail.sandvine.com>
X-Mailer: Mulberry/2.2.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org
Content-Transfer-Encoding: 7bit

David,

What do you mean by a "RuleList"/"PolicyList" attribute? Are you refering 
to grouping? If yes, we added grouping in in PCIMe.

Or what is the reasoning behind?

Marcus

--On Dienstag, 30. Juli 2002 09:51 -0400 David McTavish 
<dmctavish@SANDVINE.com> wrote:

>
>
> Just reposting this request/comment seeming as my first attempt was not
> acknowledged. Is there any consideration being placed on adding a
> PcimRuleList attribute to a PcimPolicy object, and in that same light, is
> there any thought on supporting a PcimPolicyList attribute? It seems that
> the concept of supporting repository-based policies should be extended to
> be fully functional rather than the current implementation.
>
> Any comments would be appreciated.
>
> Regards,
> David McTavish
>
> _______________________________________________
> Policy mailing list
> Policy@ietf.org
> https://www1.ietf.org/mailman/listinfo/policy



--------------------------------------
Dr. Marcus Brunner
Network Laboratories
NEC Europe Ltd.

E-Mail: brunner@ccrle.nec.de
WWW:    http://www.ccrle.nec.de/
personal home page: http://www.brubers.org/marcus



_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



From daemon@optimus.ietf.org  Tue Jul 30 11:12:40 2002
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 LAA22902
	for <policy-archive@odin.ietf.org>; Tue, 30 Jul 2002 11:12:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA02525
	for policy-archive@odin.ietf.org; Tue, 30 Jul 2002 11:13:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA01998;
	Tue, 30 Jul 2002 11:02:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA01960
	for <policy@optimus.ietf.org>; Tue, 30 Jul 2002 11:02:28 -0400 (EDT)
Received: from mail.sandvine.com (hidden-user@sandvine.com [199.243.201.138])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22471
	for <policy@ietf.org>; Tue, 30 Jul 2002 11:01:19 -0400 (EDT)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19)
	id <PH2VZZVY>; Tue, 30 Jul 2002 11:02:27 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337814F73@mail.sandvine.com>
From: David McTavish <dmctavish@SANDVINE.com>
To: "'brunner@ccrle.nec.de'" <brunner@ccrle.nec.de>,
        David McTavish
	 <dmctavish@SANDVINE.com>,
        "'Larry S. Bartz'"
	 <lbartz@parnelli.indy.cr.irs.gov>,
        IETF Policy WG LIST <policy@ietf.org>
Subject: RE: [Policy] PcimRuleList and PcimPolicyList
Date: Tue, 30 Jul 2002 11:02:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Policy Framework <policy.ietf.org>
X-BeenThere: policy@ietf.org

Basically, what we would like to implement is a referrer-style repository of
rules and policies such that a policy may contain a rule or group, but could
also contain a referrer to a re-usable rule or group.

for example, the PcimRule object encapsulates the concept with the
pcimConditionList attribute. The values specified in this attribute "point"
to a condition that is stored in a repository container. These conditions
can be re-used as often as desired, and have a centrally located
pcimCondition-based object that makes management of conditions/actions much
easier.



           +------------+
           | PcimPolicy |
           +------------+
                 |
            +----------+               +-------------------+
            | PcimRule |o--------------| PcimConditionList |
            +----------+               +-------------------+
                 |                               =
        +--------+---------+                     |
        |                  |                     |
 +---------------+  +------------+               |
 | PcimCondition |  | PcimAction |               |
 +---------------+  +------------+               |
                                                 |
                                                 |
           +----------------+                    |
           | PcimRepository |                    |
           +----------------+                    |
                   |                             |
        +----------+---------+                   |
        |                    |                   |
 +------------+     +---------------+            |
 | PcimAction |     | PcimCondition |<-----------+
 +------------+     +---------------+


What I'm asking is, is it possible to extend this functionality to the
Policy-level for supporting re-use of pcimRule objects.

           +------------+               +--------------+
           | PcimPolicy |o--------------| PcimRuleList |
           +------------+               +--------------+
                 |                               =
            +----------+                         |
            | PcimRule |                         |
            +----------+                         |
                 |                               |
        +--------+---------+                     |
        |                  |                     |
 +---------------+  +------------+               |
 | PcimCondition |  | PcimAction |               |
 +---------------+  +------------+               |
                                                 |
                                                 |
           +----------------+                    |
           | PcimRepository |                    |
           +----------------+                    |
                   |                             |
        +----------+---+---------------+         |
        |              |               |         |
 +------------+ +---------------+ +----------+   |
 | PcimAction | | PcimCondition | | pcimRule |<--+
 +------------+ +---------------+ +----------+



dave.




-----Original Message-----
From: Marcus Brunner [mailto:brunner@ccrle.nec.de]
Sent: Tuesday, July 30, 2002 10:37 AM
To: David McTavish; 'Larry S. Bartz'; IETF Policy WG LIST
Subject: Re: [Policy] PcimRuleList and PcimPolicyList


David,

What do you mean by a "RuleList"/"PolicyList" attribute? Are you refering 
to grouping? If yes, we added grouping in in PCIMe.

Or what is the reasoning behind?

Marcus

--On Dienstag, 30. Juli 2002 09:51 -0400 David McTavish 
<dmctavish@SANDVINE.com> wrote:

>
>
> Just reposting this request/comment seeming as my first attempt was not
> acknowledged. Is there any consideration being placed on adding a
> PcimRuleList attribute to a PcimPolicy object, and in that same light, is
> there any thought on supporting a PcimPolicyList attribute? It seems that
> the concept of supporting repository-based policies should be extended to
> be fully functional rather than the current implementation.
>
> Any comments would be appreciated.
>
> Regards,
> David McTavish
>
> _______________________________________________
> Policy mailing list
> Policy@ietf.org
> https://www1.ietf.org/mailman/listinfo/policy



--------------------------------------
Dr. Marcus Brunner
Network Laboratories
NEC Europe Ltd.

E-Mail: brunner@ccrle.nec.de
WWW:    http://www.ccrle.nec.de/
personal home page: http://www.brubers.org/marcus


_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy



