RE: RE: PCELS position
John Strassner <[email protected]> Tue, 23 Sep 2003 10:43:19 -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_01C381F1.CB654920 Content-Type: text/plain 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: [email protected] -----Original Message----- From: Wijnen, Bert (Bert) [mailto:[email protected]] Sent: Sunday, September 21, 2003 4:14 AM To: 'David McTavish'; 'Pana, Mircea'; '[email protected]' 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 ------_=_NextPart_001_01C381F1.CB654920 Content-Type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 10 (filtered)"> <title>PCELS position</title> <style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;} p {margin-right:0in; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman";} p.Numbered, li.Numbered, div.Numbered {margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.8in; margin-bottom:.0001pt; text-indent:-.25in; line-height:200%; font-size:10.0pt; font-family:"Times New Roman";} p.Bulletted, li.Bulletted, div.Bulletted {margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:1.5in; margin-bottom:.0001pt; text-indent:-.25in; line-height:200%; font-size:10.0pt; font-family:"Times New Roman";} span.EmailStyle19 {font-family:Arial; color:navy;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {page:Section1;} /* List Definitions */ ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>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.</span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p> <div> <p><font size=3 color=navy face="Times New Roman"><span style='font-size:12.0pt; color:navy'>regards,<br> John </span></font></p> <p><font size=3 color=navy face="Times New Roman"><span style='font-size:12.0pt; color:navy'>John C. Strassner <br> Chief Strategy Officer <br> Intelliden Inc. <br> 90 South Cascade Avenue <br> Colorado Springs, CO 80906 USA <br> phone: +1.719.785.0648 <br> fax: +1.719.785.0644 <br> email: [email protected] </span></font></p> </div> <div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'> <p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt; font-family:Tahoma'>-----Original Message-----<br> <b><span style='font-weight:bold'>From:</span></b> Wijnen, Bert (Bert) [mailto:[email protected]] <br> <b><span style='font-weight:bold'>Sent:</span></b> Sunday, September 21, 2003 4:14 AM<br> <b><span style='font-weight:bold'>To:</span></b> </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>'David McTavish'</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>; </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>'Pana, Mircea'</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt; font-family:Tahoma'>; </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>'[email protected]'</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'><br> <b><span style='font-weight:bold'>Cc:</span></b> </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>'</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>John Strassner</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt; font-family:Tahoma'>'</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>; </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>'Joel M. Halpern'</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt; font-family:Tahoma'><br> <b><span style='font-weight:bold'>Subject:</span></b> RE: [Policy] RE: PCELS position</span></font></p> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'> </span></font></p> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>W.r.t.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>> </span></font><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>Is PCIMe considered so complete, that it is beyond modification, if such</span></font><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial; color:blue'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>> </span></font><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>modification could preserve its intent while also adhering to the desires</span></font><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial; color:blue'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>></span></font><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> of maintaining consistency with PCIM and PCLS?</span></font><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial; color:blue'> </span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>PCIMe is at Proposed Standard. If, for example because of this effort to try and MAP it onto LDAP, we</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>find that we did some things in PCIMe that we should not have done, then, with WG consensus,</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>we can make incompatible changes to PCIMe and then recycle at Proposed Standard.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>That is part of the normal standars track process. That is, we get something to PS, then we start</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>using/implementing (the "using" part is reusing PCIMe definitions in otehr CIM docs (like the</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>other docs we did in Policy, and like the IPsec work, the "implementing" is sort of mapping onto for </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>example LDAP I think)... and if we find major issues, then we fix and recycle at PS. If we do not</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>find major issues, we may advance to DS.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt; font-family:"Courier New"'> </span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>Hope this helps.</span></font></p> </div> <div> <p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:blue'>Bert</span></font></p> </div> </div> </div> </body> </html> ------_=_NextPart_001_01C381F1.CB654920--