[Policy] RE: PCELS position
David McTavish <dmctavish@sandvine.com> Tue, 30 March 2004 23:59 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08734 for <policy-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:59:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8Ris-0006YH-Nr for policy-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:43 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8KFdA7Q002609 for policy-archive@odin.ietf.org; Sat, 20 Sep 2003 11:39:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A0jpF-0000fq-Mo; Sat, 20 Sep 2003 11:39:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A0ibl-0006f7-1Q for policy@optimus.ietf.org; Sat, 20 Sep 2003 10:21:09 -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 WAA05270 for <policy@ietf.org>; Fri, 19 Sep 2003 22:47:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A0XmN-0005wT-00 for policy@ietf.org; Fri, 19 Sep 2003 22:47:23 -0400
Received: from sandvine.com ([199.243.201.138] helo=mail.sandvine.com ident=hidden-user) by ietf-mx with esmtp (Exim 4.12) id 1A0XmD-0005vm-00 for policy@ietf.org; Fri, 19 Sep 2003 22:47:13 -0400
Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id <SZM8GBP6>; Fri, 19 Sep 2003 22:46:53 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337022B159B@mail.sandvine.com>
From: David McTavish <dmctavish@sandvine.com>
To: "'Pana, Mircea'" <mpana@metasolv.com>, "'policy@ietf.org'" <policy@ietf.org>
Cc: 'John Strassner' <John.Strassner@intelliden.com>, David McTavish <dmctavish@sandvine.com>, "'Joel M. Halpern'" <joel@stevecrocker.com>
Date: Fri, 19 Sep 2003 22:46:46 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C37F21.6ECFDB30"
Subject: [Policy] RE: PCELS position
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: <https://www1.ietf.org/mailman/listinfo/policy>, <mailto:policy-request@ietf.org?subject=unsubscribe>
List-Id: Policy Framework <policy.ietf.org>
List-Post: <mailto:policy@ietf.org>
List-Help: <mailto:policy-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/policy>, <mailto:policy-request@ietf.org?subject=subscribe>
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:mpana@metasolv.com] Sent: Friday, September 19, 2003 5:34 PM To: 'policy@ietf.org' 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.
- [Policy] PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position Wijnen, Bert (Bert)
- RE: [Policy] RE: PCELS position David McTavish
- RE: [Policy] RE: PCELS position Wijnen, Bert (Bert)
- RE: [Policy] RE: PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position Joel M. Halpern
- RE: [Policy] RE: PCELS position David McTavish
- RE: [Policy] RE: PCELS position John Strassner
- RE: [Policy] RE: PCELS position John Strassner
- RE: [Policy] RE: PCELS position Robert Moore
- RE: [Policy] RE: PCELS position Robert Moore
- RE: [Policy] RE: PCELS position David McTavish
- RE: [Policy] RE: PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position John Strassner
- RE: [Policy] RE: PCELS position John Strassner
- RE: [Policy] RE: PCELS position John Schnizlein
- RE: [Policy] RE: PCELS position John Strassner
- RE: [Policy] RE: PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position Pana, Mircea
- RE: [Policy] RE: PCELS position David McTavish
- RE: [Policy] RE: PCELS position John Strassner
- RE: [Policy] RE: PCELS position David McTavish
- RE: [Policy] RE: PCELS position David McTavish
- [Policy] RE: PCELS position David McTavish