pcimRepository and pcelsReusableContainer
[email protected] Sun, 15 Feb 2004 20:04:43 -0600
| Newsgroups | gmane.ietf.policy |
|---|---|
| Message-ID | <[email protected]> |
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_01C3F431.3E973E60
Content-Type: text/plain;
charset="ISO-8859-1"
The open issue #4 listed in Appendix B) in PCELS-04 refers to the proposed
implementation for the ReusablePolicyContainer class. The authors have
reached an impasse and would appreciate input from the WG wrt. the options
presented below.
Option 1 (current proposal):
...+---dlm1AdminDomain (abstract)
|
+---pcimRepository (abstract)
|
+---pcelsReusableContainer (abstract new)
|
+---pcelsReusableContainerAuxClass
| (auxiliary new)
|
+---pcelsReusableContainerInstance
(structural new)
(pcimRepositoryInstance and pcimRepositoryAuxClass classes omitted here as
irrelevant)
Pro: Virtually seamless compatibility with PCLS.
Con: Through class inheritance a pcelsReusableContainer instance is also a
pcimRepository (PCLS) but the class pcimRepository implements
PolicyRepository (PCIM) which has been deprecated (PCIM_EXT).
Option 2:
+---dlm1AdminDomain (abstract)
|
+---pcelsReusableContainer (abstract new)
|
+---pcelsReusableContainerAuxClass
| (auxiliary new)
|
+---pcelsReusableContainerInstance
(structural new)
(pcimRepository classes omitted here as irrelevant)
Pro: PCELS implementations/deployments may be free of references to
pcimRepository (strict compatibility with PCIM_EXT).
Con: Compatibility with PCLS requires PCELS implementations to perform
additional and explicit actions.
Thank You,
Mircea.
------_=_NextPart_001_01C3F431.3E973E60
Content-Type: text/html;
charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>pcimRepository and pcelsReusableContainer </TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>The open issue #4 listed in Appendix B) in PCELS-04 =
refers to the proposed implementation for the ReusablePolicyContainer =
class. The authors have reached an impasse and would appreciate input =
from the WG wrt. the options presented below.</FONT></P>
<P><FONT SIZE=3D2>Option 1 (current proposal):</FONT>
</P>
<P><FONT SIZE=3D2> ...+---dlm1AdminDomain =
(abstract)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; |</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; +---pcimRepository (abstract)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; |</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; +---pcelsReusableContainer (abstract =
new)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; |</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; =
+---pcelsReusableContainerAuxClass</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; | =
(auxiliary new)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; |</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; =
+---pcelsReusableContainerInstance</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; &nb=
sp; (structural new)</FONT>
</P>
<P><FONT SIZE=3D2>(pcimRepositoryInstance and pcimRepositoryAuxClass =
classes omitted here as irrelevant)</FONT>
</P>
<P><FONT SIZE=3D2>Pro: Virtually seamless compatibility with =
PCLS.</FONT>
<BR><FONT SIZE=3D2>Con: Through class inheritance a =
pcelsReusableContainer instance is also a pcimRepository (PCLS) but the =
class pcimRepository implements PolicyRepository (PCIM) which has been =
deprecated (PCIM_EXT).</FONT></P>
<P><FONT SIZE=3D2>Option 2:</FONT>
</P>
<P><FONT =
SIZE=3D2> =
+---dlm1AdminDomain (abstract)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; |</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; +---pcelsReusableContainer (abstract new)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; |</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; =
+---pcelsReusableContainerAuxClass</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; | (auxiliary =
new)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; |</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; =
+---pcelsReusableContainerInstance</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; =
(structural new)</FONT>
</P>
<P><FONT SIZE=3D2>(pcimRepository classes omitted here as =
irrelevant)</FONT>
</P>
<P><FONT SIZE=3D2>Pro: PCELS implementations/deployments may be free of =
references to pcimRepository (strict compatibility with =
PCIM_EXT).</FONT></P>
<P><FONT SIZE=3D2>Con: Compatibility with PCLS requires PCELS =
implementations to perform additional and explicit actions.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Thank You,</FONT>
<BR><FONT SIZE=3D2>Mircea.</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C3F431.3E973E60--