attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>CIM> Brief notes from conccall with CIM Core this morning</TITLE> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD> <BODY> <DIV dir=ltr align=left>Hi Rick,</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>To answer you questions about IPP:</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>(Printer MIB has a good intro.  Where is the  similar overview for IPP?)</DIV> <DIV dir=ltr align=left>TH> The first two sections of RFC 2911 are a good intro to IPP.</DIV> <DIV dir=ltr align=left>Google of RFC 2911 gets: <A href="http://www.faqs.org/rfcs/rfc2911.html">http://www.faqs.org/rfcs/rfc2911.html</A></DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>Also the PWG Semantic Model (IEEE-ISTO 5105.1-2004) gives a good summary of all of IPP semantics, including the many additional IETF and IEEE-ISTO extensions standards to the base IPP RFC 2911.</DIV> <DIV dir=ltr align=left>Google of "PWG Semantic Model" gets: <A href="http://www.pwg.org/sm/">http://www.pwg.org/sm/</A></DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>Tom</DIV> <DIV dir=ltr align=left>P.S. I never leave home without Google.</DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: owner-wims@pwg.org [mailto:owner-wims@pwg.org] On Behalf Of Richard_Landau@Dell.com Sent: Monday, January 23, 2006 09:41 To: wims@pwg.org Cc: Winston_Bumpus@Dell.com Subject: WIMS> CIM> Brief notes from conccall with CIM Core this morning </DIV> <DIV></DIV> Short notes on a few things I heard in the CIM Core concall today.  (I didn't have much opportunity to take notes for the first half hour, but here are some things I remember.) Easy changes first: good idea.  One, maybe two, CRs; maybe enums are separate, since they're sizable and substantive.  Don't bother with white papers.  Draft directly into CR format, then edit as needed.  Don't bother with PWG private extensions.  Propose phase 3 changes as experimental.  Then the implementation experience of two companies will be needed to promote the changes to full status.  Do UML diagrams first for the new class structure, and get agreement on the structure before writing a lot of text.  Core needs some overview of the printing model.  (Printer MIB has a good intro.  Where is the  similar overview for IPP?) Use Capabilities and Settings classes (CIM_xxxx) to express such for printers.  The usual division is - What is the device capable of? (r/o in Capabilities) - What has the manager requested of the device? (r/w in Settings) - What is the device actually doing? (properties in the device class itself) (These classes are not completely straightforward, as I recall.  I will look for some examples.) Think about doing a profile in the long term.  (A really good idea.  I will explain this and get an example for PWG to look at.  I think we should draft the profile along with the UML.) For the major changes, be sure to include some consideration of - related element causing error - health and status - messages - indications (event notifications in CIM, related to traps, alerts, alarms, etc.) Send draft things, if we wish, to John Crandall and Jon_Hass@dell.com, or to wg_cimcore@dmtf.org Gotta go.  rick ------------------------- Richard_Landau(at)dell(dot)com, System Mgt Arch & Stds +1-512-728-9023, One Dell Way, RR5-3 Box 8509, Round Rock, TX 78682 </BODY></HTML>