RE: [Policy] RE: PCELS position

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Sun, 21 September 2003 10:17 UTC

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 GAA21919 for <policy-archive@odin.ietf.org>; Sun, 21 Sep 2003 06:17:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A11H7-00061M-GB for policy-archive@odin.ietf.org; Sun, 21 Sep 2003 06:17:07 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8LAH5oS023145 for policy-archive@odin.ietf.org; Sun, 21 Sep 2003 06:17:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A11H2-00060z-K7; Sun, 21 Sep 2003 06:17:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A11Fq-00060C-I9 for policy@optimus.ietf.org; Sun, 21 Sep 2003 06:16:21 -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 GAA21876 for <policy@ietf.org>; Sun, 21 Sep 2003 06:15:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A11Fh-0000te-00 for policy@ietf.org; Sun, 21 Sep 2003 06:15:37 -0400
Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1A11FX-0000tF-00 for policy@ietf.org; Sun, 21 Sep 2003 06:15:27 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id h8LAEQu04334 for <policy@ietf.org>; Sun, 21 Sep 2003 05:14:26 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id <TFQWL2RY>; Sun, 21 Sep 2003 12:14:25 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155023315EE@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: 'David McTavish' <dmctavish@sandvine.com>, "'Pana, Mircea'" <mpana@metasolv.com>, "'policy@ietf.org'" <policy@ietf.org>
Cc: 'John Strassner' <John.Strassner@intelliden.com>, "'Joel M. Halpern'" <joel@stevecrocker.com>
Subject: RE: [Policy] RE: PCELS position
Date: Sun, 21 Sep 2003 12:14:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C38028.84FC8B3A"
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>

W.r.t.
>  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? 
 
PCIMe is at Proposed Standard. If, for example because of this effort to try and MAP it onto LDAP, we
find that we did some things in PCIMe that we should not have done, then, with WG consensus,
we can make incompatible changes to PCIMe and then recycle at Proposed Standard.
That is part of the normal standars track process. That is, we get something to PS, then we start
using/implementing (the "using" part is reusing PCIMe definitions in otehr CIM docs (like the
other docs we did in Policy, and like the IPsec work, the "implementing" is sort of mapping onto for 
example LDAP I think)... and if we find major issues, then we fix and recycle at PS. If we do not
find major issues, we may advance to DS.
 
Hope this helps.
Bert