RE: PCELS position

David McTavish <[email protected]> Fri, 19 Sep 2003 22:46:46 -0400
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_01C37F21.6ECFDB30
Content-Type: text/plain;
	charset="iso-8859-1"

Opening the box a little further, is it still possible to provide feedback
to PCIMe so that its original intent can be maintained, while preserving
option #1? It seems that the work so far in PCELS is correct in relation to
the PCIMe proposal, and perhaps the schema changes that we are debating
should in fact be taken to a higher level.
Is PCIMe considered so complete, that it is beyond modification, if such
modification could preserve its intent while also adhering to the desires of
maintaining consistency with PCIM and PCLS?
 
d.
 

-----Original Message-----
From: Pana, Mircea [mailto:[email protected]]
Sent: Friday, September 19, 2003 5:34 PM
To: '[email protected]'
Cc: 'John Strassner'; 'David McTavish'; 'Joel M. Halpern'
Subject: PCELS position



After having read so many arguments on the position of PCELS relative to
PCLS I've come to the conclusion that people wish PCELS to be either a fully
interoperable extension of PCLS or a stand-alone policy schema. At the same
time the main goal of PCELS was to implement PCIMe (as an increment of
PCIM).

Based on these facts, I can see three major options (and perhaps a lot of
variations): 
1. If PCELS ignores or alters some of the PCIMe recommendations, then it can
be fully interoperable with PCLS. 
2. For PCELS to be fully compliant with PCIMe it must at the minimum define
replacement for a couple of the schema items defined by PCLS.

3. For PCELS to be fully compliant with PCIMe and stand-alone (i.e. no
dependency on PCLS), it would need to redefine many (otherwise re-usable)
PCLS schema items.

So, my question to the group is: of the three options above, which one do
you like the most (or find the easiest to live with)?

Joel, is #1 a viable option? 

Thank you, 
Mircea. 


------_=_NextPart_001_01C37F21.6ECFDB30
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>PCELS position</TITLE>

<META content="MSHTML 6.00.2800.1226" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=814564302-20092003><FONT face="Courier New" size=2>Opening the 
box a little further, is it still possible to provide feedback to PCIMe so that 
its original intent can be maintained, while preserving option #1? It seems that 
the work so far in PCELS is correct in relation to the PCIMe proposal, and 
perhaps the schema changes that we are debating should in fact be taken to a 
higher level.</FONT></SPAN></DIV>
<DIV><SPAN class=814564302-20092003><FONT face="Courier New" size=2>Is PCIMe 
considered so complete, that it is beyond modification, if such modification 
could preserve its intent while also adhering to the desires of maintaining 
consistency with PCIM and PCLS?</FONT></SPAN></DIV>
<DIV><SPAN class=814564302-20092003><FONT face="Courier New" 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=814564302-20092003><FONT face="Courier New" 
size=2>d.</FONT></SPAN></DIV>
<DIV><SPAN class=814564302-20092003><FONT face="Courier New" 
size=2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Pana, Mircea 
  [mailto:[email protected]]<BR><B>Sent:</B> Friday, September 19, 2003 5:34 
  PM<BR><B>To:</B> '[email protected]'<BR><B>Cc:</B> 'John Strassner'; 'David 
  McTavish'; 'Joel M. Halpern'<BR><B>Subject:</B> PCELS 
  position<BR><BR></FONT></DIV>
  <P><FONT size=2>After having read so many arguments on the position of PCELS 
  relative to PCLS I've come to the conclusion that people wish PCELS to be 
  either a fully interoperable extension of PCLS or a stand-alone policy schema. 
  At the same time the main goal of PCELS was to implement PCIMe (as an 
  increment of PCIM).</FONT></P>
  <P><FONT size=2>Based on these facts, I can see three major options (and 
  perhaps a lot of variations):</FONT> <BR><FONT size=2>1. If PCELS ignores or 
  alters some of the PCIMe recommendations, then it can be fully interoperable 
  with PCLS.</FONT> <BR><FONT size=2>2. For PCELS to be fully compliant with 
  PCIMe it must at the minimum define replacement for a couple of the schema 
  items defined by PCLS.</FONT></P>
  <P><FONT size=2>3. For PCELS to be fully compliant with PCIMe and stand-alone 
  (i.e. no dependency on PCLS), it would need to redefine many (otherwise 
  re-usable) PCLS schema items.</FONT></P>
  <P><FONT size=2>So, my question to the group is: of the three options above, 
  which one do you like the most (or find the easiest to live with)?</FONT></P>
  <P><FONT size=2>Joel, is #1 a viable option?</FONT> </P>
  <P><FONT size=2>Thank you,</FONT> <BR><FONT size=2>Mircea.</FONT> 
</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C37F21.6ECFDB30--