RE: [Policy] RE: PCELS position

"Pana, Mircea" <mpana@metasolv.com> Tue, 23 September 2003 22:18 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 SAA10906 for <policy-archive@odin.ietf.org>; Tue, 23 Sep 2003 18:18:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1vTu-0001Yb-Ab for policy-archive@odin.ietf.org; Tue, 23 Sep 2003 18:18:02 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8NMI2V8005968 for policy-archive@odin.ietf.org; Tue, 23 Sep 2003 18:18:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1vTt-0001Xu-6b; Tue, 23 Sep 2003 18:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1vTf-0001Xb-KV for policy@optimus.ietf.org; Tue, 23 Sep 2003 18:17:47 -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 SAA10892 for <policy@ietf.org>; Tue, 23 Sep 2003 18:17:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A1vTc-00001g-00 for policy@ietf.org; Tue, 23 Sep 2003 18:17:44 -0400
Received: from mail.metasolv.com ([12.105.131.5] helo=srvmaddog.metasolv.com) by ietf-mx with esmtp (Exim 4.12) id 1A1vTc-00001J-00 for policy@ietf.org; Tue, 23 Sep 2003 18:17:44 -0400
Received: by SRVMADDOG with Internet Mail Service (5.5.2655.55) id <S0L043TG>; Tue, 23 Sep 2003 17:21:54 -0500
Message-ID: <A33EE5A81E634B488B099FD31F65196153CDF0@srvotemail.metasolv.com>
From: "Pana, Mircea" <mpana@metasolv.com>
To: 'John Strassner' <John.Strassner@intelliden.com>, "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>, 'David McTavish' <dmctavish@sandvine.com>, "'policy@ietf.org'" <policy@ietf.org>
Cc: "'Joel M. Halpern'" <joel@stevecrocker.com>
Subject: RE: [Policy] RE: PCELS position
Date: Tue, 23 Sep 2003 17:12:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3821F.C98CC9B0"
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>

I agree with John. The mapping of an information model to a data model has
its own chalenges and the chalenges will be different from one technology to
an other. That does not mean that we have to revisit the model each time.
 
I am not trying to say that PCIMe is perfect and that it should never be
revisited, but I do not see (so far) enough reasons for re-opening such
discussions. 
 
Regards,
Mircea.
 

-----Original Message-----
From: John Strassner [mailto:John.Strassner@intelliden.com]
Sent: Tuesday, September 23, 2003 12:43 PM
To: 'Wijnen, Bert (Bert)'; 'David McTavish'; 'Pana, Mircea';
'policy@ietf.org'
Cc: John Strassner; 'Joel M. Halpern'
Subject: RE: [Policy] RE: PCELS position
Importance: High



I fundamentally disagree with rebuilding RFC 3460, which is an INFORMATION
MODEL, because of DATA MODEL concerns. That is exactly backwards, because it
ensures that the information model cannot be mapped to other types of data
models.

 

regards,
John 

John C. Strassner 
Chief Strategy Officer 
Intelliden Inc. 
90 South Cascade Avenue 
Colorado Springs, CO  80906  USA 
phone:  +1.719.785.0648 
  fax:     +1.719.785.0644 
email:    john.strassner@intelliden.com 

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Sunday, September 21, 2003 4:14 AM
To: 'David McTavish'; 'Pana, Mircea'; 'policy@ietf.org'
Cc: 'John Strassner'; 'Joel M. Halpern'
Subject: RE: [Policy] RE: PCELS position

 

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