RE: [Policy] RE: PCELS position

[David McTavish <dmctavish@sandvine.com>]

Title: RE: [Policy] RE: PCELS position

One example of attribute re-use is the x500UniqueIdentifier attribute, which is defined in RFC 2256, and again used in inetOrgPerson RFC 2798.

 

d.

 

-----Original Message-----
From: Pana, Mircea [mailto:mpana@metasolv.com]
Sent: Tuesday, September 23, 2003 9:47 PM
To: 'John Strassner '; ''Robert Moore' '
Cc: ''Wijnen, Bert (Bert)' '; ''David McTavish' '; ''Joel M. Halpern' '; Pana, Mircea; ''policy@ietf.org' '
Subject: RE: [Policy] RE: PCELS position

 John,

>  2) I do not believe that the word "reuse" applies when an
>     attribute is defined in one class, with one set of
>     semantics, and then is blopped into a new class with
>     completely different semantics. That is what I meant
>     by stealing an OID.

I do not understand the difference in semantics that you are referring to.

Let's take pcimRuleEnables one more time as example. PCLS defines it as:
"An integer indicating whether a policy rule is administratively enabled (value=1), disabled (value=2), or enabled for debug (value=3)". In PCLS this attribute indicates the state of pcimRule, class mapped from PCIM's PolicyRule. In PCELS we use (but not redefine) this attribute preserving its its syntax and semantics to indicate the state of a pcimPolicyRule, class mapped from PCIMe's PolicyRule. Doesn't the attribute (I stress: the attribute not the class that uses it) have the same semantics in these two cases?

Regards,
Mircea.