From james_odonnell at firstclassemails.org Wed May 6 14:01:09 2009 From: james_odonnell at firstclassemails.org (james o'donnell) Date: Wed May 6 14:01:16 2009 Subject: Fwd:people you trust (2600) Message-ID: <45c568f5$520b$9ce@dns.network888.com> An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/pmp/attachments/20030423/15a72fbc/attachment.html From james_odonnell at firstclassemails.org Wed May 6 14:01:09 2009 From: james_odonnell at firstclassemails.org (james o'donnell) Date: Wed May 6 14:01:16 2009 Subject: Fwd:people you trust (2600) Message-ID: <45c568f5$520b$9ce@dns.network888.com> An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/pmp/attachments/20030424/15a72fbc/attachment.html From TSF6GG1yt at stak1ed.net Wed May 6 14:01:09 2009 From: TSF6GG1yt at stak1ed.net (TSF6GG1yt@stak1ed.net) Date: Wed May 6 14:01:53 2009 Subject: PMP> Lasers/Optics/Optical Tables - Save! Message-ID: <3.0.1.32.19971120124733.00f25690@garfield> MWK INDUSTRIES SALE! JUST A QUICK LETTER TO SHOW YOU SOME LASERS- OPTICS AND OPTICAL TABLES SURPLUS THAT WE JUST RECEIVED. ITEM TRIMMU12 14 WATT ARGON LASER MADE FOR HEART SURGERY, TRIMEDYNE MODEL 900 TEMOO, POLORIZED,220VAC INPUT , WATER COOLED , FIBER LAUNCH, ALL ON ROLLAROUND CART EXCELENT FOR LAB USE, THE POWER WAS MEASURED AT 13 TO 14 WATTS. PRICE $9500 12 MONTH WARRANTEE. ITEM: COHERENT ARTICULATING ARM FROM A MODEL 451 CO2 MEDICAL LASER. ECCELLENT COND. $200 ITEM CO220A: CO2 LASER MADE BY PFIZER ,1990, FOR SURGERY, TATTOO REMOVAL ECT. 20 WATT OUTPUT , TESTED AND IN EXC. COND. 110 VAC INPUT, COST $40,000 NEW OUR PRICE 4,900. MODEL 20-C ITEM:PDA-1U1 SPECTRA PHYSICS QUANTRA RAY PULSED DYE LASER , GOOD FOR SPARE PARTS MODEL PDA-1 $500 ITEM NEWU1 NEWPORT OPTICAL TABLE 16" BY 36" 4" THICK, 1 " HOLE SPACING, COMES WITH A RUBBER ISOLATED TABLE STAND, NOT AIR SUPPORTED, $750 ITEM: HEPSN1 HELIUM NEON POWER SUPPLY KIT OPERATES UP TO A 15 mW LASER, INCLUDES ALL COMPONENTS AND PRINTED CIRCUIT BOARD, ALL YOU HAVE TO DO IS STUFF AND SOLDER THE CIRCUIT BOARD . 4" BY 3" BY 3", PRICE $75 ITEM HENEU12 1 TO 1.5 MW HE-NE LASER 632.8 nM INCLUDES 12VDC INPUT POWER SUPPLY ALL IN A PLASTIC HOUSING 6.25 IN. BY 1.375IN BY 2.25 IN. TEMOO,RANDOM POL. ,1.7 MR DIVERGENCE. 12 MONTH WARRANTEE , PRICE $45 ITEM MELU12 1 TO 2 mW HE-NE LASER 632.8 NM , PULLS FROM MEDICAL EQUIPMENT .EACH UNIT INCLUDES HE-NE HEAD AND POWER SUPPLY[110VAC INPUT]. ALL YOU NEED TO PROVIDE IS A POWER CORD AND A FUSE TO MAKE THE UNIT OPERATIONAL. THE BEAM IS TEM00, POLORIZED WE WILL COVER EACH UNIT WITH A 12 MONTH UNLIMITED HOUR WARRANTEE, EXCELLENT FOR FOR LAB OR HOME USE. NEW THESE COST APPROX. $350 OUR PRICE $85. DIMENSIONS 9.75 BY 1.25 INCHES, P.S. 4.25 BY 3.25BY 1.25 INCHES. ITEM RAMCNS1: RAMAN CELL OPTICS 308 nm AR/AR 4600 A 0=0 DEGREES 1000 MM FL. 2" DIA. NEW. ORIGINAL PRICE $520 OUR PRICE $175 ITEM TFPOLNS1: POLARIZERS , THIN FILM FOR 532 nm , NEW, ORIGINAL COST $590 EACH OUR PRICE $200 EACH 10 MM DIA. ITEM CO2OCNS1: CO2 HIGH REFECTOR AND OUTPUT COUPLER 10.5 MM DIA, OC =79%R NEW. $200 A SET. ITEM 25MNS1: DIELECTRIC BROADBAND MIRRORS 450 TO 700NM , NEW WITH PLASTIC PROTECTIVE COATINGS , 2 SIZES 25 MM SQ. AND 50 MM SQ. RECOMENDED FOR HIGHER POWER LASERS. 25MM SIZE ITEM 25MNS1 $20 50MM SIZE ITEM 50MNS1 $25 ITEM # BSDNS1: 50/50 DIELECTRIC COATED PLATE BEAM SPLITTER 630 TO 660 NM COMES IN A TRIANGLE SHAPE EACH SIDE APPROX. 1" PRICE $20 ITEM # 45NS1 45 DEGREE RED REFLECTOR , PASSES 488 TO 532NM , CAN BE USED TO COMBINE RED AND GREEN/BLUE LASERS TO CREATE A WHITE LIGHT LASER. 1" SQ. PRICE $15 ITEM# PCINS1 PLANO/CONVEX LENS COATED FOR YAG 1064NM , AR COATED, 10MM DIA. NEW, ORIG. COST $250 OUR PRICE $100 ITEM# INFILTER : INTERFERENCE FILTERS USED FOR PASSING A PARTICULAR SPECTRAL LINE , 11.8 MM DIA. CAREFULLY REMOVED FROM MEDICAL EQUIPMENT AND WRAPPED IN LENSE PAPER. THE FOLLOWING WAVE LENGTHS ARE AVAILABLE. 523.5, 547.4 , 572.1, 512.9, 550.6, 488, 505.7 nm price $20 each. FOR A COMPLETE LINE OF NEW AND USED LASERS - OPTICS -ELECTRO OPTICS- LASER SHOWS ORDER A COMPLETE CATALOG AT MWKINDUSTRIES.COM TO: ORDER GO TO OUR WEB SITE MWKINDUSTRIES.COM {SECURE ORDERING SITE} QUESTIONS OR REMOVAL FROM MAILING LIST EMAIL: MWK@WORLDNET.ATT.NET MWK INDUSTRIES 1269 POMONA RD CORONA CA 91720 PHONE 909-278-0563 FAX 909-278-4887 From DC1vrIcKe at upnor1th.com Wed May 6 14:01:09 2009 From: DC1vrIcKe at upnor1th.com (DC1vrIcKe@upnor1th.com) Date: Wed May 6 14:01:53 2009 Subject: PMP> We bulk Email for You Message-ID: <3.0.1.32.19971120124733.00f25690@garfield> LET US DO YOUR BULK MAILINGS!!! ...$350 PER MILLION ADDRESSES SENT ...$250 PER 1/2 MILLION ADDRESSES SENT THE WAY OF THE FUTURE FOR SUCCESS IN YOUR BUSINESS! Our company will do bulk emailing for your product/service. DON'T BE LEFT IN THE DUST OF YOUR COMPETORS, ADVERTISE TODAY!!! Addresses are extracted daily by 6 of our computers, which run 24 hours a day 7 days a week, scanning the net for new addresses. Estimated 60-80,000 addresses extracted daily. They are fresh! Over 40 million addresses on file. More computers with cable modems are being added due to increasing responses. All ads can not be more than 2 pages (50 lines) and 68 characters wide. More than 50 lines, there will be an additional charge of $50 per page or 25 lines or less. No porn, no foul language or sex relative material will be sent. ->->->->->->->-> TARGETED MAILINGS <-<-<-<-<-<-<-<- ->-> $150 per 50,000 addresses extracted or less ->-> This price includes mailing of material ->-> Allow 3-7 days for extracting of addresses ->-> Mailings to US only (general addresses) $500 per 500,000 ->-> Many targeted list on file ->-> Purchased target list $150 per 50,000 or less If you have your own list, we will email your list for $200 per 500,000 or less. All list must be in text format and each address must be on individual lines. ***Mailings are done all at once, not broken down into multiple mailings.*** Addrsses are processed against our remove list of those individuals who have asked to be elimated from any of our mailings. All mailings are de-duped for duplicates. No .mil, .gov or .edu included. There are no lower prices on the net. Your mailing can be done in a matter of hours. Turn around time for mailings range from 3 to 5 days. This time varies according to the demand of mailings. For the fastest service, cheapest prices and cleanest mailings call our processing and new accounts office at 904-282-0945, Monday - Friday 9 - 5 EST (English only). If the line is busy or no repsonse, please keep trying, as bulk mailing is growing fast and we are busy responding to those who are interested in advertsing on the internet. We DO want to work with you to advertise your product/service. No collect calls. Our computers are working 24 hours a day to better serve YOU! To have your name removed, call our processing office. Any negative responses will be dealt with accordingly. From piRn5Q78I at 1nashvill.com Wed May 6 14:01:09 2009 From: piRn5Q78I at 1nashvill.com (piRn5Q78I@1nashvill.com) Date: Wed May 6 14:01:53 2009 Subject: PMP> Cheapest Prices! Message-ID: <199801150126.AA09514@interlock2.lexmark.com> LET US DO YOUR BULK MAILINGS!!! ..$350 PER MILLION ADDRESSES SENT ..$250 PER 1/2 MILLION ADDRESSES SENT THE WAY OF THE FUTURE FOR SUCCESS IN YOUR BUSINESS! Our company will do bulk emailing for your product/service. Addresses are extracted daily by six of our computers, which run 24 hours a day 7 days a week, scanning the net for new addresses. Estimated 60-80,000 addresses extracted daily. They are fresh! Over 40 million addresses on file. No more than 2 pages (50 lines), no porn and no foul language. $50 per page/25 lines per page beyond 2 pages. We do not do targeted mailings at this price. Targeted mailings: $150 per 50,000 addresses extracted or less. We can extract by country, occupation, organizations, associations, product, etc. If we can not search and extract what you need, then nobody can. There are no lower prices on the net. Your mailing can be done in a matter of hours. We have 6 computers extracting addresses 24/7. For the fastest service, cheapest prices and cleanest mailings call our processing and new accounts office at 904-282-0945, Monday - Friday 9 - 5 EST. If the line is busy, please keep trying, as bulk mailing is growing fast. We do want to work with you to advertise your product. To have your name removed, call our processing office. Any negative responses will be dealt with accordingly. From 3H1UVSK7M at re-searc1hes.com Wed May 6 14:01:09 2009 From: 3H1UVSK7M at re-searc1hes.com (3H1UVSK7M@re-searc1hes.com) Date: Wed May 6 14:01:53 2009 Subject: PMP> Are You Happy? Message-ID: <199801240110.UAA02960@ns.owlseye.com> There is brilliant information available to you, that will enable you to fully understand yourself and everybody else. This knowledge can benefit you tremendously in many ways. It can help you to get the very best out of your career, or discover your most suitable new career, and of course being happy at work, really improves the finances. It can also really enhance your love life. If you're in a relationship, it works great, because you are able to fully understand your own and your partner's emotions and motivations. If you're not, you will know exactly what you want from your perfect mate and what they will find attractive about you. Another big advantage to becoming balanced and happy is that good health runs hand in hand. Take a closer look two free pages of information at: http://www.po9.com From harry.lewis at infoprint.com Wed Jul 8 14:20:32 2009 From: harry.lewis at infoprint.com (Harry Lewis) Date: Wed Jul 8 14:20:53 2009 Subject: [PMP] Request for new Fin MIB enum Message-ID: An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/pmp/attachments/20090708/c5230d19/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 54058 bytes Desc: not available Url : http://www.pwg.org/archives/pmp/attachments/20090708/c5230d19/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 590 bytes Desc: not available Url : http://www.pwg.org/archives/pmp/attachments/20090708/c5230d19/attachment-0001.gif From Richard_Landau at Dell.com Wed Jul 8 14:27:41 2009 From: Richard_Landau at Dell.com (Richard_Landau@Dell.com) Date: Wed Jul 8 14:27:58 2009 Subject: [PMP] Request for new Fin MIB enum In-Reply-To: References: Message-ID: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 54058 bytes Desc: image001.gif Url : http://www.pwg.org/archives/pmp/attachments/20090708/8539c4ba/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 590 bytes Desc: image002.gif Url : http://www.pwg.org/archives/pmp/attachments/20090708/8539c4ba/attachment-0001.gif From blueroofmusic at gmail.com Wed Jul 8 16:40:24 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Wed Jul 8 16:40:38 2009 Subject: [PMP] Request for new Fin MIB enum In-Reply-To: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> References: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> Message-ID: Hi Harry, I agree with adding this enumerated value. I agree with Rick - keep the 'plastic' prefix. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Jul 8, 2009 at 2:27 PM, wrote: > Keep the extra word.? If there were ever in the future a plastic version and > a metal version, and one wanted to offer the user a choice between them, it > would be necessary to have two separate values.? For the time being, it does > not cost anything to include "plastic" in the name. > > > > rick > > > > > > From: pmp-bounces@pwg.org [mailto:pmp-bounces@pwg.org] On Behalf Of Harry > Lewis > Sent: Wednesday, July 08, 2009 13:21 > To: pmp@pwg.org; fin@pwg.org > Subject: [PMP] Request for new Fin MIB enum > > > > MIB fans - I would like to add a new textual convention to FinBindingTypeTC > as follows. If no objection by July 30 I'd like to proceed with IANA > registration. Also, if anyone needs further information or a diagram I can > provide. This is for a plastic binder that looks like this. My only question > is should we have "plastic" in the enum name or not. My first thought was to > leave it off but then, after looking at JDF and other Fin TC's it seems the > use of "metal" and "plastic" as a prefix is common. > > > > Plastic Multi-Ring Binding: A method of binding in which a series of small > holes is placed along the bind edge of the sheets. The sheets are then held > together by inserting a 'locking' ring through each hole. The set of rings > are all attached to a common spine. > > FinBindingTypeTC ::= TEXTUAL-CONVENTION > ? ? STATUS ? ? ? current > ? ? DESCRIPTION > ? ? ? "The defined binding type enumerations." > ? ? SYNTAX ? ? ? INTEGER { > ? ? ? ? ?other(1), ? ? ? ? ?-- More information in other attributes > ? ? ? ? ?unknown(2), > ? ? ? ? ?tape(4), > ? ? ? ? ?plastic(5), > ? ? ? ? ?velo(6), > ? ? ? ? ?perfect(7), > ? ? ? ? ?spiral(8), > ? ? ? ? ?adhesive(9), > ? ? ? ? ?comb(10), > ? ? ? ? ?padding(11), > ? ? ? ? ?plasticMultiRing(12) > ? ? ? ? } > > Regards, > Harry > > Harry Lewis > Program Manager - Intellectual Property & Open Standards > Phone: 720-663-3456 > e-mail: harry.lewis@infoprint.com > infoprint.com > > > P Think before you print > _____________________________________________________________________________ > "This message and any attachments are solely for the intended recipient and > may contain confidential or privileged information. If you are not the > intended recipient, any disclosure, copying, use, or distribution of the > information included in this message and any attachments is prohibited. If > you have received this communication in error, please notify us by reply > e-mail and immediately and permanently delete this message and any > attachments. Thank you." > _____________________________________________________________________________ > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pmp mailing list > pmp@pwg.org > https://www.pwg.org/mailman/listinfo/pmp > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Tue Jul 28 19:30:34 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Tue Jul 28 19:30:51 2009 Subject: [PMP] Request for new Fin MIB enum In-Reply-To: References: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> Message-ID: Hi Harry, Tickler to remind us all to deal with thiis later this week. Jerry - we could ratify this change at SC call this Thursday and then Harry could proceed with the registration w/ IANA. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Jul 8, 2009 at 4:40 PM, Ira McDonald wrote: > Hi Harry, > > I agree with adding this enumerated value. > > I agree with Rick - keep the 'plastic' prefix. > > Cheers, > - Ira > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Blue Roof Music/High North Inc > email: blueroofmusic@gmail.com > winter: > ?579 Park Place ?Saline, MI ?48176 > ?734-944-0094 > summer: > ?PO Box 221 ?Grand Marais, MI 49839 > ?906-494-2434 > > > > On Wed, Jul 8, 2009 at 2:27 PM, wrote: >> Keep the extra word.? If there were ever in the future a plastic version and >> a metal version, and one wanted to offer the user a choice between them, it >> would be necessary to have two separate values.? For the time being, it does >> not cost anything to include "plastic" in the name. >> >> >> >> rick >> >> >> >> >> >> From: pmp-bounces@pwg.org [mailto:pmp-bounces@pwg.org] On Behalf Of Harry >> Lewis >> Sent: Wednesday, July 08, 2009 13:21 >> To: pmp@pwg.org; fin@pwg.org >> Subject: [PMP] Request for new Fin MIB enum >> >> >> >> MIB fans - I would like to add a new textual convention to FinBindingTypeTC >> as follows. If no objection by July 30 I'd like to proceed with IANA >> registration. Also, if anyone needs further information or a diagram I can >> provide. This is for a plastic binder that looks like this. My only question >> is should we have "plastic" in the enum name or not. My first thought was to >> leave it off but then, after looking at JDF and other Fin TC's it seems the >> use of "metal" and "plastic" as a prefix is common. >> >> >> >> Plastic Multi-Ring Binding: A method of binding in which a series of small >> holes is placed along the bind edge of the sheets. The sheets are then held >> together by inserting a 'locking' ring through each hole. The set of rings >> are all attached to a common spine. >> >> FinBindingTypeTC ::= TEXTUAL-CONVENTION >> ? ? STATUS ? ? ? current >> ? ? DESCRIPTION >> ? ? ? "The defined binding type enumerations." >> ? ? SYNTAX ? ? ? INTEGER { >> ? ? ? ? ?other(1), ? ? ? ? ?-- More information in other attributes >> ? ? ? ? ?unknown(2), >> ? ? ? ? ?tape(4), >> ? ? ? ? ?plastic(5), >> ? ? ? ? ?velo(6), >> ? ? ? ? ?perfect(7), >> ? ? ? ? ?spiral(8), >> ? ? ? ? ?adhesive(9), >> ? ? ? ? ?comb(10), >> ? ? ? ? ?padding(11), >> ? ? ? ? ?plasticMultiRing(12) >> ? ? ? ? } >> >> Regards, >> Harry >> >> Harry Lewis >> Program Manager - Intellectual Property & Open Standards >> Phone: 720-663-3456 >> e-mail: harry.lewis@infoprint.com >> infoprint.com >> >> >> P Think before you print >> _____________________________________________________________________________ >> "This message and any attachments are solely for the intended recipient and >> may contain confidential or privileged information. If you are not the >> intended recipient, any disclosure, copying, use, or distribution of the >> information included in this message and any attachments is prohibited. If >> you have received this communication in error, please notify us by reply >> e-mail and immediately and permanently delete this message and any >> attachments. Thank you." >> _____________________________________________________________________________ >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> _______________________________________________ >> pmp mailing list >> pmp@pwg.org >> https://www.pwg.org/mailman/listinfo/pmp >> >> > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From wamwagner at comcast.net Thu Jul 30 15:37:43 2009 From: wamwagner at comcast.net (William Wagner) Date: Thu Jul 30 15:38:00 2009 Subject: [PMP] new MIB enums Message-ID: <003c01ca114d$35424550$9fc6cff0$@net> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 54058 bytes Desc: not available Url : http://www.pwg.org/archives/pmp/attachments/20090730/808cba33/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 590 bytes Desc: not available Url : http://www.pwg.org/archives/pmp/attachments/20090730/808cba33/attachment-0001.gif From blueroofmusic at gmail.com Mon Aug 3 12:06:56 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Aug 3 12:07:10 2009 Subject: [PMP] Proposal for IEEE 1284 Device ID Command Set (3 August 2009) Message-ID: Hi, Per my moss-covered action item from October 2007 (eek!). I've just posted a proposed new normative appendix for the PWG Printer Port Monitor MIB to standardize the content of the "COMMAND SET" (CMD) capability at: ftp://ftp.pwg.org/pub/pwg/pmp/white/tb-ppm-1284-cmd-20090803.htm For review in WIMS/PMP WG and PWG Steering Committee teleconferences and in the WIMS/PMP session during our upcoming PWG face-to-face on Wednesday 19 August. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Aug 10 12:06:18 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Aug 10 12:07:14 2009 Subject: [PMP] ECMA 388 - OpenXPS Message-ID: Hi, With reference to the topic of potential registration in the IANA Printer MIB of the XPS format, here's a durable link to the ECMA OpenXPS Standard (June 2009): http://www.ecma-international.org/publications/standards/Ecma-388.htm Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From don at lexmark.com Mon Sep 14 11:14:22 2009 From: don at lexmark.com (Don Wright) Date: Mon Sep 14 11:14:37 2009 Subject: [PMP] Fw: [ISEP] Help Message-ID: Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 3457 bytes Desc: not available Url : http://www.pwg.org/archives/pmp/attachments/20090914/3c8c695a/attachment.gif From wamwagner at comcast.net Mon Sep 14 13:14:45 2009 From: wamwagner at comcast.net (William Wagner) Date: Mon Sep 14 13:15:01 2009 Subject: [PMP] Printer MIB question Message-ID: <002e01ca355e$db4c7760$91e56620$@net> With regard to the question that you sent to hastings@cp10.es.xerox.com, szilles@mv.us.adobe.com, don@lexmark.com, jgyllens@hpdmd48.boi.hp.com, it has been forwarded to the Printer Working Group "PMP" mail list, which deals with printer MIB issues. You may well have responses from other members, but if I understand your question, it is how to interpret the response to OID [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The object value is "bit coded" as follows, and your program is interpreting the response in hexadecimal. lowPaper 0 noPaper 1 lowToner 2 noToner 3 doorOpen 4 jammed 5 offline 6 serviceRequested 7 inputTrayMissing 8 outputTrayMissing 9 markerSupplyMissing 10 outputNearFull 11 outputFull 12 inputTrayEmpty 13 overduePreventMaint 14 But remember that, in the MIB, bits are numbered starting with the most significant bit of the first byte being bit 0, To interpret 80 04, it may be easiest conceptually to covert the value to binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 and bit 13, low paper and input tray empty. Hope this helps. Note also that the current Printer MIB is RFC3805, although some printers still support only the earlier verson. Bill Wagner/ Chair, Printer Working Group WIMS/PMP -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/pmp/attachments/20090914/aae8acee/attachment.html From cc at euroform.dk Mon Sep 14 13:55:35 2009 From: cc at euroform.dk (Christian Christiansen) Date: Mon Sep 14 13:55:06 2009 Subject: [PMP] Printer MIB question In-Reply-To: <002e01ca355e$db4c7760$91e56620$@net> References: <002e01ca355e$db4c7760$91e56620$@net> Message-ID: <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> If the endian is correct then, the value 8004 has a binary representation as follows: 1000 0000 0000 0100 That means to me that bit 15 is on and bit 2 is on. However bit 15 is NOT defined in RFC2790 So the interpretation would be "LowToner" If the endian is wrong the the value is 0480 and it has a binary representation as follows: 0000 0100 1000 0000 That means to me that bit 10 is on and bit 7 is on. In this case the interpretation would be "serviceRequested" "markerSupplyMissing" Christian Christiansen ________________________________ From: pmp-bounces@pwg.org [mailto:pmp-bounces@pwg.org] On Behalf Of William Wagner Sent: 14. september 2009 19:15 To: farouk.boujnah@gmail.com Cc: pmp@pwg.org Subject: [PMP] Printer MIB question With regard to the question that you sent to hastings@cp10.es.xerox.com, szilles@mv.us.adobe.com, don@lexmark.com, jgyllens@hpdmd48.boi.hp.com, it has been forwarded to the Printer Working Group "PMP" mail list, which deals with printer MIB issues. You may well have responses from other members, but if I understand your question, it is how to interpret the response to OID [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The object value is "bit coded" as follows, and your program is interpreting the response in hexadecimal. lowPaper 0 noPaper 1 lowToner 2 noToner 3 doorOpen 4 jammed 5 offline 6 serviceRequested 7 inputTrayMissing 8 outputTrayMissing 9 markerSupplyMissing 10 outputNearFull 11 outputFull 12 inputTrayEmpty 13 overduePreventMaint 14 But remember that, in the MIB, bits are numbered starting with the most significant bit of the first byte being bit 0, To interpret 80 04, it may be easiest conceptually to covert the value to binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 and bit 13, low paper and input tray empty. Hope this helps. Note also that the current Printer MIB is RFC3805, although some printers still support only the earlier verson. Bill Wagner/ Chair, Printer Working Group WIMS/PMP -- This message has been scanned for viruses and dangerous content by MailScanner , and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/pmp/attachments/20090914/7f11c868/attachment.html From blueroofmusic at gmail.com Mon Sep 14 15:21:17 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Sep 14 15:21:31 2009 Subject: [PMP] Printer MIB question In-Reply-To: <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> References: <002e01ca355e$db4c7760$91e56620$@net> <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> Message-ID: Hi folks, No - Bill Wagner had it right in his original reply. Right after Bill's previous quotation, RFC2790 says: "Bits are numbered starting with the most significant bit of the first byte being bit 0, the least significant bit of the first byte being bit 7, the most significant bit of the second byte being bit 8..." Read the above carefully! Bit 0 (0x8000) and bit 14 (0x0004) are set. Cheers, - Ira (co-editor of Printer MIB v2, RFC 3805) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Sep 14, 2009 at 1:55 PM, Christian Christiansen wrote: > If the endian is correct then, the value 8004 has a binary representation as > follows: > > 1000 0000 0000 0100 > > That means to me that bit 15 is on and bit 2 is on. However bit 15 is NOT > defined in RFC2790 > > So the interpretation would be > > ?LowToner? > > > > If the endian is wrong the the value is 0480 and it has a binary > representation as follows: > > 0000 0100 1000 0000 > > That means to me that bit 10 is on and bit 7 is on. > > In this case the interpretation would be > > ?serviceRequested? > > ?markerSupplyMissing? > > > > Christian Christiansen > > > > > > ________________________________ > > From: pmp-bounces@pwg.org [mailto:pmp-bounces@pwg.org] On Behalf Of William > Wagner > Sent: 14. september 2009 19:15 > To: farouk.boujnah@gmail.com > Cc: pmp@pwg.org > Subject: [PMP] Printer MIB question > > > > With regard to the question that you sent to hastings@cp10.es.xerox.com, > szilles@mv.us.adobe.com, don@lexmark.com, jgyllens@hpdmd48.boi.hp.com, it > has been forwarded to the Printer Working Group ?PMP? mail list, which deals > with printer MIB issues. You may well have responses from other members, but > if I understand your question, it is how to interpret the response to? OID > [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the > hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The > object value is ?bit coded? as follows, and your program is interpreting the > response in hexadecimal. > > ?? lowPaper????????????? 0 > > ?? noPaper?????????????? 1 > > ??????????????? lowToner????????????? 2 > > ??????????????? noToner?????????????? 3 > > ??????????????? doorOpen????????????? 4 > > ??????????????? jammed??????????????? 5 > > ??????????????? offline?????????????? 6 > > ??????????????? serviceRequested????? 7 > > ??????????????? inputTrayMissing????? 8 > > ??????????????? outputTrayMissing???? 9 > > ??????????????? markerSupplyMissing? 10 > > ??????????????? outputNearFull?????? 11 > > ??????????????? outputFull?????????? 12 > > ??????????????? inputTrayEmpty?????? 13 > > ??????????????? overduePreventMaint? 14 > > > > But remember that, in the MIB, bits are numbered starting with the most > significant bit of the first byte being bit 0, > > > > To interpret 80 04, it may be easiest conceptually to covert the value to > binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 > and bit 13, low paper and input tray empty. > > > > Hope this helps. Note also that the current Printer MIB is RFC3805, although > some printers still support only the earlier verson. > > > > Bill Wagner/ Chair, Printer Working Group WIMS/PMP > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pmp mailing list > pmp@pwg.org > https://www.pwg.org/mailman/listinfo/pmp > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Sep 14 17:33:21 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Sep 14 17:33:36 2009 Subject: [PMP] Printer MIB question In-Reply-To: References: <002e01ca355e$db4c7760$91e56620$@net> <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> Message-ID: Hi, EEK - actually 0x0004 is bit 13 as Bill said originally (not bit 14 as I miscounted), i.e., inputTrayEmpty. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Sep 14, 2009 at 3:21 PM, Ira McDonald wrote: > Hi folks, > > No - Bill Wagner had it right in his original reply. > > Right after Bill's previous quotation, RFC2790 says: > > ?"Bits are numbered starting with the most significant > ?bit of the first byte being bit 0, the least significant bit > ?of the first byte being bit 7, the most significant bit of > ?the second byte being bit 8..." > > Read the above carefully! > > Bit 0 (0x8000) and bit 14 (0x0004) are set. > > Cheers, > - Ira (co-editor of Printer MIB v2, RFC 3805) > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Blue Roof Music/High North Inc > email: blueroofmusic@gmail.com > winter: > ?579 Park Place ?Saline, MI ?48176 > ?734-944-0094 > summer: > ?PO Box 221 ?Grand Marais, MI 49839 > ?906-494-2434 > > > > On Mon, Sep 14, 2009 at 1:55 PM, Christian Christiansen wrote: >> If the endian is correct then, the value 8004 has a binary representation as >> follows: >> >> 1000 0000 0000 0100 >> >> That means to me that bit 15 is on and bit 2 is on. However bit 15 is NOT >> defined in RFC2790 >> >> So the interpretation would be >> >> ?LowToner? >> >> >> >> If the endian is wrong the the value is 0480 and it has a binary >> representation as follows: >> >> 0000 0100 1000 0000 >> >> That means to me that bit 10 is on and bit 7 is on. >> >> In this case the interpretation would be >> >> ?serviceRequested? >> >> ?markerSupplyMissing? >> >> >> >> Christian Christiansen >> >> >> >> >> >> ________________________________ >> >> From: pmp-bounces@pwg.org [mailto:pmp-bounces@pwg.org] On Behalf Of William >> Wagner >> Sent: 14. september 2009 19:15 >> To: farouk.boujnah@gmail.com >> Cc: pmp@pwg.org >> Subject: [PMP] Printer MIB question >> >> >> >> With regard to the question that you sent to hastings@cp10.es.xerox.com, >> szilles@mv.us.adobe.com, don@lexmark.com, jgyllens@hpdmd48.boi.hp.com, it >> has been forwarded to the Printer Working Group ?PMP? mail list, which deals >> with printer MIB issues. You may well have responses from other members, but >> if I understand your question, it is how to interpret the response to? OID >> [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the >> hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The >> object value is ?bit coded? as follows, and your program is interpreting the >> response in hexadecimal. >> >> ?? lowPaper????????????? 0 >> >> ?? noPaper?????????????? 1 >> >> ??????????????? lowToner????????????? 2 >> >> ??????????????? noToner?????????????? 3 >> >> ??????????????? doorOpen????????????? 4 >> >> ??????????????? jammed??????????????? 5 >> >> ??????????????? offline?????????????? 6 >> >> ??????????????? serviceRequested????? 7 >> >> ??????????????? inputTrayMissing????? 8 >> >> ??????????????? outputTrayMissing???? 9 >> >> ??????????????? markerSupplyMissing? 10 >> >> ??????????????? outputNearFull?????? 11 >> >> ??????????????? outputFull?????????? 12 >> >> ??????????????? inputTrayEmpty?????? 13 >> >> ??????????????? overduePreventMaint? 14 >> >> >> >> But remember that, in the MIB, bits are numbered starting with the most >> significant bit of the first byte being bit 0, >> >> >> >> To interpret 80 04, it may be easiest conceptually to covert the value to >> binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 >> and bit 13, low paper and input tray empty. >> >> >> >> Hope this helps. Note also that the current Printer MIB is RFC3805, although >> some printers still support only the earlier verson. >> >> >> >> Bill Wagner/ Chair, Printer Working Group WIMS/PMP >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> _______________________________________________ >> pmp mailing list >> pmp@pwg.org >> https://www.pwg.org/mailman/listinfo/pmp >> >> > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Sep 21 22:17:31 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Sep 21 22:17:46 2009 Subject: [PMP] IANA Printer MIB updates from PWG5100.9 Message-ID: Hi, Today, I sent large IANA Printer MIB updates to IANA - I'll keep folks posted on progress. Taken from IPP Printer State Reasons [PWG5100.9], I sent IANA Printer MIB updates for PrtAlertCodeTC. I also just uploaded them to the PWG FTP server at: ftp://ftp.pwg.org/pub/pwg/pmp/iana/ in the file: iana-prt-20090921.zip Cheers, - Ira (IPP and Printer MIB co-editor) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Thu Oct 1 21:08:23 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Thu Oct 1 21:08:39 2009 Subject: [PMP] Posted Cmd Set Format for 1284 Device ID (1 Oct 2009) Message-ID: Hi, I just posted a first complete draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091001.pdf For review during the WIMS/CIM/PMP WG session at the PWG Meeting at Apple on Tuesday 13 October 2009. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Nov 2 13:49:15 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Nov 2 13:49:39 2009 Subject: [PMP] langXPS and langOpenXPS Message-ID: Hi, For immediate review (today if possible): ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt Mike Fenelon, Michael Sweet, and I have had a productive offline conversation this last week about this. Mike Fenelon proposed two enums and this justification: "The OpenXPS spec is already complete and it does have differences from the MS spec. Since the 2 specifications/types have completely different namespaces I think it is pretty important to have 2 definitions. There are already a number of devices that support the current specification: langXPS. And all Windows 7 clients will generate this format. And MS and others have committed to supporting the new OpenXPS spec also. It is very important to know which." Cheers, - Ira (joint IETF Designated Expert for IANA Printer MIB) ----------------------------------------------------------------------------------- (view in a fixed width font) In PrtInterpreterLangFamilyTC, after 'langC4(65)' add: langXPS(66), -- Not in RFC 3805 -- Microsoft XML Paper Specification -- http://www.microsoft.com/whdc/xps/xpsspec langOpenXPS(67) -- Not in RFC 3805 -- ECMA OpenXPS -- http://www.ecmainternational.org/ -- publications/standards/Ecma-388.htm Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Nov 2 18:29:12 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Nov 2 18:29:32 2009 Subject: [PMP] plasticMultiRing submitted for IANA Finisher MIB Message-ID: Hi, Harry Lewis reminded me last week that we hadn't yet submitted his approved 'plasticMultiRing' for IANA Finisher MIB - oops! Since it was unanimously approved during our August F2F, I submitted it to IANA last Friday. I'll let the PMP/WIMS mailing lists know when it's completed by IANA. Cheers, - Ira (IETF Designated Expert for IANA Finisher MIB) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Nov 2 21:15:53 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Nov 2 21:16:11 2009 Subject: [PMP] Re: langXPS and langOpenXPS In-Reply-To: References: Message-ID: Hi Mike, THANKS! My cut-and-paste error. I have corrected and reposted (to the same dated filename): ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt All - if there are no opposing opinions or clarifications by Thursday (12 November) next week, I will submit these updates to IANA. Cheers, - Ira (IETF Designated Expert for IANA Printer MIB) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Nov 2, 2009 at 7:45 PM, Mike Fenelon wrote: > I discovered a problem in the URL for OpenXPS. > > It is actually: http://www.ecma-international.org/publications/standards/Ecma-388.htm > > Notice the - between ecma & international > > Mike Fenelon > Microsoft > > > -----Original Message----- > From: Ira McDonald [mailto:blueroofmusic@gmail.com] > Sent: Monday, November 02, 2009 10:49 AM > To: pmp@pwg.org; wims@pwg.org; Ira McDonald; Mike Fenelon; Michael R Sweet > Subject: langXPS and langOpenXPS > > Hi, > > For immediate review (today if possible): > > ?ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt > > Mike Fenelon, Michael Sweet, and I have had a productive > offline conversation this last week about this. > > Mike Fenelon proposed two enums and this justification: > > "The OpenXPS spec is already complete and it does have > differences from the MS spec. ?Since the 2 specifications/types > have completely different namespaces I think it is pretty > important to have 2 definitions. > > There are already a number of devices that support the current > specification: langXPS. ?And all Windows 7 clients will generate > this format. And MS and others have committed to supporting > the new OpenXPS spec also. It is very important to know which." > > Cheers, > - Ira (joint IETF Designated Expert for IANA Printer MIB) > > ----------------------------------------------------------------------------------- > (view in a fixed width font) > > In PrtInterpreterLangFamilyTC, after 'langC4(65)' add: > > ? ? ? langXPS(66), ? ? ? ? -- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- Microsoft XML Paper Specification > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- http://www.microsoft.com/whdc/xps/xpsspec > ? ? ? langOpenXPS(67) ? ? ?-- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- ECMA OpenXPS > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- http://www.ecmainternational.org/ > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- ? publications/standards/Ecma-388.htm > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Blue Roof Music/High North Inc > email: blueroofmusic@gmail.com > winter: > ?579 Park Place ?Saline, MI ?48176 > ?734-944-0094 > summer: > ?PO Box 221 ?Grand Marais, MI 49839 > ?906-494-2434 > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Tue Nov 3 13:02:30 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Tue Nov 3 13:02:54 2009 Subject: [PMP] SeaMonkey 2.0 - fine WYSIWIG HTML editor Message-ID: Hi, For anyone who edits web pages or complex HTML forms (like the DMTF CIM Change Request template), a fine tool just got a lot better. SeaMonkey 2.0 now uses common infrastructure with Firefox 3.5: http://www.seamonkey-project.org/releases/ Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Tue Nov 3 22:39:13 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Tue Nov 3 22:39:33 2009 Subject: [PMP] Fwd: [IANA #275889] plasticMultiRing in IANA Finisher MIB - DONE! Message-ID: Hi, Considering that I submitted this update (Harry's new binding type) last Friday to IANA, this is lightspeed turnaround! Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 ---------- Forwarded message ---------- From: Amanda Baber via RT Date: Tue, Nov 3, 2009 at 9:12 PM Subject: [IANA #275889] General Request for Assignments (ianafinisher-mib) To: blueroofmusic@gmail.com Hi Ira, This request is complete: http://www.iana.org/assignments/ianafinisher-mib Let us know if anything needs to be fixed/expanded upon. Thanks, Amanda On Fri Oct 30 16:39:29 2009, blueroofmusic@gmail.com wrote: > Contact Name : > Ira McDonald > > Contact Email : > blueroofmusic@gmail.com > > Type of Assignment : > Permanent enumerated name/value in FinBindingTypeTC > Please add to end after padding(11): > > ? ? ? ? plasticMultiRing(12) > > Registry : > IANA Finisher MIB > http://www.iana.org/assignments/ianafinisher-mib > > Description : > Proposed by Harry Lewis (InfoPrint Solutions Company). > Reviewed by email discussion on Finisher MIB WG mailing list. > Approved by Ira McDonald (IETF Designated Expert for IANA Finisher MIB). > > Additional Info : > IANA Finisher MIB originally published in RFC 3806. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From harry.lewis at infoprint.com Tue Nov 3 23:21:00 2009 From: harry.lewis at infoprint.com (Harry Lewis) Date: Tue Nov 3 23:21:20 2009 Subject: [PMP] Re: Fwd: [IANA #275889] plasticMultiRing in IANA Finisher MIB - DONE! In-Reply-To: Message-ID: An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/pmp/attachments/20091103/f2d3b217/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 590 bytes Desc: not available Url : http://www.pwg.org/archives/pmp/attachments/20091103/f2d3b217/attachment.gif From blueroofmusic at gmail.com Mon Nov 23 18:54:18 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Nov 23 18:54:36 2009 Subject: [PMP] langXPS registered in IANA Printer MIB Message-ID: Hi, Last Friday - I sent the request to IANA. Today (1 business day later), Amanda finished the update - cool. Cheers, - Ira (IETF Designated Expert for IANA Printer MIB) ---------- Forwarded message ---------- From: Amanda Baber via RT Date: Mon, Nov 23, 2009 at 6:08 PM Subject: [IANA #281267] General Request for Assignments (ianaprinter-mib) To: blueroofmusic@gmail.com Hi Ira, This is complete. See http://www.iana.org/assignments/ianaprinter-mib Thanks, Amanda On Fri Nov 20 22:59:36 2009, blueroofmusic@gmail.com wrote: > Contact Name : > Ira McDonald > > Contact Email : > blueroofmusic@gmail.com > > Type of Assignment : > Permanent enumerated name/value in PrtInterpreterLangFamilyTC. > Please add to end after langC4(65): > > ? ? ? ?langXPS(66), ? ? ? ? -- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- Microsoft XML Paper Specification > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- http://www.microsoft.com/whdc/xps/xpsspec > ? ? ? ?langOpenXPS(67) ? ? ?-- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- ECMA OpenXPS > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- http://www.ecma-international.org/ > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- ? publications/standards/Ecma-388.htm > > Exact text for this update is archived at: > ? ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt > > > > Registry : > IANA Printer MIB > http://www.iana.org/assignments/ianaprinter-mib > > Description : > Proposed by Mike Fenelon (Microsoft) and Peter Zehler (Xerox). > Reviewed by email discussion on Printer MIB WG mailing list. > Approved by Ira McDonald (IETF Designated Expert for IANA Printer MIB). > > Additional Info : > IANA Printer MIB originally published in RFC 3805. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Nov 30 17:29:54 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Nov 30 17:30:10 2009 Subject: [PMP] Posted Cmd Set Format for 1284 Device ID (30 Nov 2009) Message-ID: Hi, I just posted a Prototype draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130.pdf / doc - clean copy ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130-rev.pdf / doc - with redlines For review during the WIMS/CIM/PMP WG session during the PWG Face-to-Face at Dell on Tuesday 8 December 2009. Cheers, - Ira ---------------------------------------------------------------- Changes to create the version of 30 November 2009 ? Prototype Draft - Editorial ? changed document status to Prototype Draft, per WIMS WG discussion - Editorial ? revised section 3 Requirements to downcase all imperatives (SHOULD -> should, etc.) - Technical ? revised section 3.2.3 External Network Adapter ? Local Printer, to clarify that local (USB, etc.) Device IDs should not be changed and should be passed through as is, per Jerry Thrasher - Technical ? revised section 5 Definition of Command Set Format in ABNF, to add private types for compatibility with existing practice, per analysis of MIB walks of network printers - Technical ? revised section 5 Definition of Command Set Format in ABNF, to allow 1 or more control characters (CR, LF, or HTAB) *before* each command language keyword (but NOT infixed), per Jerry Thrasher and IEEE 1284 section 7.6 specification - Editorial ? renamed section 6.1 from Conformance for Imaging Systems to Conformance for Network Spoolers and Network Printers, per Jerry Thrasher - Technical ? added new section 6.2 Conformance for External Network Adapters (MUST NOT change IEEE 1284 Device ID values from local printers), per Jerry Thrasher ----------------------------------------------------- Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc email: blueroofmusic@gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Dec 14 12:02:53 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon Dec 14 12:03:13 2009 Subject: [PMP] 1284 Cmd Set w/ IPP "printer-device-id" (14 December 2009) Message-ID: Hi, [To: PMP, WIMS, IPP] I just posted an expanded Prototype draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091214.pdf / doc - clean copy w/ line numbers ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130-rev.pdf / doc - with redlines and line numbers This version defines the new IPP Printer attribute "printer-device-id (text(1023))", per the IPP WG and WIMS WG discussions last week at December PWG F2F. For review at today's WIMS WG teleconference and WIMS WG last call through early January. Cheers, - Ira ---------------------------------------------------------------- Changes to create the version of 14 December 2009 ? Prototype Draft - Editorial ? kept document status at Prototype Draft, per December PWG F2F - Editorial ? revised Abstract and section 1 Introduction to include new IPP ?printer-device-id?, per December PWG F2F - Editorial ? renamed section 3.2.3 to External Network Adapter with locally-attached Printer, for clarity - Technical ? revised all of section 3 Requirements to include new IPP ?printer-device-id?, per December PWG F2F - Editorial ? renamed section 5 to PWG Extensions to IEEE 1284 Device ID, per December PWG F2F - Technical ? added section 5.2 IPP printer-device-id (text(1023)), per December PWG F2F - Technical ? revised section 6 to include REQUIRED implemention of ?printer-device-id? for IPP/2.0 and higher versions (to be added to IPP Version 2.0 Second Edition as well) - Editorial ? revised section 7 IANA and PWG Considerations to include the IANA registration for the new IPP ?printer-device-id? attribute defined in section 5.2 - Editorial ? deleted unused section 13 Appendix A ? Design Alternatives -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From wamwagner at comcast.net Tue Dec 15 13:43:58 2009 From: wamwagner at comcast.net (William Wagner) Date: Tue Dec 15 13:44:21 2009 Subject: [PMP] 1284 Cmd Set w/ IPP "printer-device-id" (14 December 2009) In-Reply-To: References: Message-ID: <000001ca7db6$90a65460$b1f2fd20$@net> At the WIMS/PMP conference call yesterday, it was agreed that this latest draft of the IEEE 1284 Device ID Command Set Format document: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091214.pdf / doc appears to address all issues brought up to date. As agreed at the WIMS face-to-face, this document is now in working group last call. All comments will be considered, but especially from members of PMP, WIMS and IPP WK. Please review the document and post any comments or objections to the combined PMP, WIMS and IPP maillists. These comments will be reviewed at the 11 January WIMS conference call. It is understood that a statement of prototype/product implementation will be provided shortly. This should allow advancing the document to stable status and submitting it to a PWG last call period including the February face-to-face. Thanks, Bill Wagner -----Original Message----- From: pmp-bounces@pwg.org [mailto:pmp-bounces@pwg.org] On Behalf Of Ira McDonald Sent: Monday, December 14, 2009 12:03 PM To: pmp@pwg.org; wims@pwg.org; ipp@pwg.org; Ira McDonald Subject: [PMP] 1284 Cmd Set w/ IPP "printer-device-id" (14 December 2009) Hi, [To: PMP, WIMS, IPP] I just posted an expanded Prototype draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091214.pdf / doc - clean copy w/ line numbers ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130-rev.pdf / doc - with redlines and line numbers This version defines the new IPP Printer attribute "printer-device-id (text(1023))", per the IPP WG and WIMS WG discussions last week at December PWG F2F. For review at today's WIMS WG teleconference and WIMS WG last call through early January. Cheers, - Ira ---------------------------------------------------------------- Changes to create the version of 14 December 2009 - Prototype Draft - Editorial - kept document status at Prototype Draft, per December PWG F2F - Editorial - revised Abstract and section 1 Introduction to include new IPP "printer-device-id", per December PWG F2F - Editorial - renamed section 3.2.3 to External Network Adapter with locally-attached Printer, for clarity - Technical - revised all of section 3 Requirements to include new IPP "printer-device-id", per December PWG F2F - Editorial - renamed section 5 to PWG Extensions to IEEE 1284 Device ID, per December PWG F2F - Technical - added section 5.2 IPP printer-device-id (text(1023)), per December PWG F2F - Technical - revised section 6 to include REQUIRED implemention of "printer-device-id" for IPP/2.0 and higher versions (to be added to IPP Version 2.0 Second Edition as well) - Editorial - revised section 7 IANA and PWG Considerations to include the IANA registration for the new IPP "printer-device-id" attribute defined in section 5.2 - Editorial - deleted unused section 13 Appendix A - Design Alternatives -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pmp mailing list pmp@pwg.org https://www.pwg.org/mailman/listinfo/pmp -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From harry.lewis at infoprint.com Wed Jul 8 18:20:32 2009 From: harry.lewis at infoprint.com (Harry Lewis) Date: Wed, 8 Jul 2009 18:20:32 +0000 Subject: [PMP] Request for new Fin MIB enum Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 54058 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 590 bytes Desc: not available URL: From Richard_Landau at Dell.com Wed Jul 8 18:27:41 2009 From: Richard_Landau at Dell.com (Richard_Landau at Dell.com) Date: Wed, 8 Jul 2009 13:27:41 -0500 Subject: [PMP] Request for new Fin MIB enum In-Reply-To: References: Message-ID: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> Keep the extra word. If there were ever in the future a plastic version and a metal version, and one wanted to offer the user a choice between them, it would be necessary to have two separate values. For the time being, it does not cost anything to include "plastic" in the name. rick From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of Harry Lewis Sent: Wednesday, July 08, 2009 13:21 To: pmp at pwg.org; fin at pwg.org Subject: [PMP] Request for new Fin MIB enum MIB fans - I would like to add a new textual convention to FinBindingTypeTC as follows. If no objection by July 30 I'd like to proceed with IANA registration. Also, if anyone needs further information or a diagram I can provide. This is for a plastic binder that looks like this. My only question is should we have "plastic" in the enum name or not. My first thought was to leave it off but then, after looking at JDF and other Fin TC's it seems the use of "metal" and "plastic" as a prefix is common. Plastic Multi-Ring Binding: A method of binding in which a series of small holes is placed along the bind edge of the sheets. The sheets are then held together by inserting a 'locking' ring through each hole. The set of rings are all attached to a common spine. FinBindingTypeTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The defined binding type enumerations." SYNTAX INTEGER { other(1), -- More information in other attributes unknown(2), tape(4), plastic(5), velo(6), perfect(7), spiral(8), adhesive(9), comb(10), padding(11), plasticMultiRing(12) } Regards, Harry Harry Lewis Program Manager - Intellectual Property & Open Standards Phone: 720-663-3456 e-mail: harry.lewis at infoprint.com infoprint.com P Think before you print ________________________________________________________________________ _____ "This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you." ________________________________________________________________________ _____ -- This message has been scanned for viruses and dangerous content by MailScanner , and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 54058 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 590 bytes Desc: image002.gif URL: From blueroofmusic at gmail.com Wed Jul 8 20:40:24 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Wed, 8 Jul 2009 16:40:24 -0400 Subject: [PMP] Request for new Fin MIB enum In-Reply-To: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> References: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> Message-ID: Hi Harry, I agree with adding this enumerated value. I agree with Rick - keep the 'plastic' prefix. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Jul 8, 2009 at 2:27 PM, wrote: > Keep the extra word.? If there were ever in the future a plastic version and > a metal version, and one wanted to offer the user a choice between them, it > would be necessary to have two separate values.? For the time being, it does > not cost anything to include "plastic" in the name. > > > > rick > > > > > > From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of Harry > Lewis > Sent: Wednesday, July 08, 2009 13:21 > To: pmp at pwg.org; fin at pwg.org > Subject: [PMP] Request for new Fin MIB enum > > > > MIB fans - I would like to add a new textual convention to FinBindingTypeTC > as follows. If no objection by July 30 I'd like to proceed with IANA > registration. Also, if anyone needs further information or a diagram I can > provide. This is for a plastic binder that looks like this. My only question > is should we have "plastic" in the enum name or not. My first thought was to > leave it off but then, after looking at JDF and other Fin TC's it seems the > use of "metal" and "plastic" as a prefix is common. > > > > Plastic Multi-Ring Binding: A method of binding in which a series of small > holes is placed along the bind edge of the sheets. The sheets are then held > together by inserting a 'locking' ring through each hole. The set of rings > are all attached to a common spine. > > FinBindingTypeTC ::= TEXTUAL-CONVENTION > ? ? STATUS ? ? ? current > ? ? DESCRIPTION > ? ? ? "The defined binding type enumerations." > ? ? SYNTAX ? ? ? INTEGER { > ? ? ? ? ?other(1), ? ? ? ? ?-- More information in other attributes > ? ? ? ? ?unknown(2), > ? ? ? ? ?tape(4), > ? ? ? ? ?plastic(5), > ? ? ? ? ?velo(6), > ? ? ? ? ?perfect(7), > ? ? ? ? ?spiral(8), > ? ? ? ? ?adhesive(9), > ? ? ? ? ?comb(10), > ? ? ? ? ?padding(11), > ? ? ? ? ?plasticMultiRing(12) > ? ? ? ? } > > Regards, > Harry > > Harry Lewis > Program Manager - Intellectual Property & Open Standards > Phone: 720-663-3456 > e-mail: harry.lewis at infoprint.com > infoprint.com > > > P Think before you print > _____________________________________________________________________________ > "This message and any attachments are solely for the intended recipient and > may contain confidential or privileged information. If you are not the > intended recipient, any disclosure, copying, use, or distribution of the > information included in this message and any attachments is prohibited. If > you have received this communication in error, please notify us by reply > e-mail and immediately and permanently delete this message and any > attachments. Thank you." > _____________________________________________________________________________ > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pmp mailing list > pmp at pwg.org > https://www.pwg.org/mailman/listinfo/pmp > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Tue Jul 28 23:30:34 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Tue, 28 Jul 2009 19:30:34 -0400 Subject: [PMP] Request for new Fin MIB enum In-Reply-To: References: <8546BF850DA5144EBE4E0486C86E36FC01ADBAFA@ausx3mps304.aus.amer.dell.com> Message-ID: Hi Harry, Tickler to remind us all to deal with thiis later this week. Jerry - we could ratify this change at SC call this Thursday and then Harry could proceed with the registration w/ IANA. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Jul 8, 2009 at 4:40 PM, Ira McDonald wrote: > Hi Harry, > > I agree with adding this enumerated value. > > I agree with Rick - keep the 'plastic' prefix. > > Cheers, > - Ira > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Blue Roof Music/High North Inc > email: blueroofmusic at gmail.com > winter: > ?579 Park Place ?Saline, MI ?48176 > ?734-944-0094 > summer: > ?PO Box 221 ?Grand Marais, MI 49839 > ?906-494-2434 > > > > On Wed, Jul 8, 2009 at 2:27 PM, wrote: >> Keep the extra word.? If there were ever in the future a plastic version and >> a metal version, and one wanted to offer the user a choice between them, it >> would be necessary to have two separate values.? For the time being, it does >> not cost anything to include "plastic" in the name. >> >> >> >> rick >> >> >> >> >> >> From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of Harry >> Lewis >> Sent: Wednesday, July 08, 2009 13:21 >> To: pmp at pwg.org; fin at pwg.org >> Subject: [PMP] Request for new Fin MIB enum >> >> >> >> MIB fans - I would like to add a new textual convention to FinBindingTypeTC >> as follows. If no objection by July 30 I'd like to proceed with IANA >> registration. Also, if anyone needs further information or a diagram I can >> provide. This is for a plastic binder that looks like this. My only question >> is should we have "plastic" in the enum name or not. My first thought was to >> leave it off but then, after looking at JDF and other Fin TC's it seems the >> use of "metal" and "plastic" as a prefix is common. >> >> >> >> Plastic Multi-Ring Binding: A method of binding in which a series of small >> holes is placed along the bind edge of the sheets. The sheets are then held >> together by inserting a 'locking' ring through each hole. The set of rings >> are all attached to a common spine. >> >> FinBindingTypeTC ::= TEXTUAL-CONVENTION >> ? ? STATUS ? ? ? current >> ? ? DESCRIPTION >> ? ? ? "The defined binding type enumerations." >> ? ? SYNTAX ? ? ? INTEGER { >> ? ? ? ? ?other(1), ? ? ? ? ?-- More information in other attributes >> ? ? ? ? ?unknown(2), >> ? ? ? ? ?tape(4), >> ? ? ? ? ?plastic(5), >> ? ? ? ? ?velo(6), >> ? ? ? ? ?perfect(7), >> ? ? ? ? ?spiral(8), >> ? ? ? ? ?adhesive(9), >> ? ? ? ? ?comb(10), >> ? ? ? ? ?padding(11), >> ? ? ? ? ?plasticMultiRing(12) >> ? ? ? ? } >> >> Regards, >> Harry >> >> Harry Lewis >> Program Manager - Intellectual Property & Open Standards >> Phone: 720-663-3456 >> e-mail: harry.lewis at infoprint.com >> infoprint.com >> >> >> P Think before you print >> _____________________________________________________________________________ >> "This message and any attachments are solely for the intended recipient and >> may contain confidential or privileged information. If you are not the >> intended recipient, any disclosure, copying, use, or distribution of the >> information included in this message and any attachments is prohibited. If >> you have received this communication in error, please notify us by reply >> e-mail and immediately and permanently delete this message and any >> attachments. Thank you." >> _____________________________________________________________________________ >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> _______________________________________________ >> pmp mailing list >> pmp at pwg.org >> https://www.pwg.org/mailman/listinfo/pmp >> >> > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From wamwagner at comcast.net Thu Jul 30 19:37:43 2009 From: wamwagner at comcast.net (William Wagner) Date: Thu, 30 Jul 2009 15:37:43 -0400 Subject: [PMP] new MIB enums Message-ID: <003c01ca114d$35424550$9fc6cff0$@net> In addition to the new Finisher MIB FinBindingTypeTC suggested by Harry some time ago, there recently was the observation the XPS might reasonably be included as a entry in PrtInterpreterLangFamilyTC of the Printer MIB. Microsoft has been queried as to whether it is interested in adding this. We should spend a little time on this at the next WIMS call (10 August, 11AM EDT). Thanks, Bill Wagner PS: Harry, I agree with plasticMultiRing From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of Harry Lewis Sent: Wednesday, July 08, 2009 2:21 PM To: pmp at pwg.org; fin at pwg.org Subject: [PMP] Request for new Fin MIB enum MIB fans - I would like to add a new textual convention to FinBindingTypeTC as follows. If no objection by July 30 I'd like to proceed with IANA registration. Also, if anyone needs further information or a diagram I can provide. This is for a plastic binder that looks like this. My only question is should we have "plastic" in the enum name or not. My first thought was to leave it off but then, after looking at JDF and other Fin TC's it seems the use of "metal" and "plastic" as a prefix is common. Plastic Multi-Ring Binding: A method of binding in which a series of small holes is placed along the bind edge of the sheets. The sheets are then held together by inserting a 'locking' ring through each hole. The set of rings are all attached to a common spine. FinBindingTypeTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The defined binding type enumerations." SYNTAX INTEGER { other(1), -- More information in other attributes unknown(2), tape(4), plastic(5), velo(6), perfect(7), spiral(8), adhesive(9), comb(10), padding(11), plasticMultiRing(12) } Regards, Harry Harry Lewis Program Manager - Intellectual Property & Open Standards Phone: 720-663-3456 e-mail: harry.lewis at infoprint.com infoprint.com P Think before you print ____________________________________________________________________________ _ "This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you." ____________________________________________________________________________ _ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00054.gif Type: image/gif Size: 54058 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00057.gif Type: image/gif Size: 590 bytes Desc: not available URL: From blueroofmusic at gmail.com Mon Aug 3 16:06:56 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 3 Aug 2009 12:06:56 -0400 Subject: [PMP] Proposal for IEEE 1284 Device ID Command Set (3 August 2009) Message-ID: Hi, Per my moss-covered action item from October 2007 (eek!). I've just posted a proposed new normative appendix for the PWG Printer Port Monitor MIB to standardize the content of the "COMMAND SET" (CMD) capability at: ftp://ftp.pwg.org/pub/pwg/pmp/white/tb-ppm-1284-cmd-20090803.htm For review in WIMS/PMP WG and PWG Steering Committee teleconferences and in the WIMS/PMP session during our upcoming PWG face-to-face on Wednesday 19 August. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Aug 10 16:06:18 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 10 Aug 2009 12:06:18 -0400 Subject: [PMP] ECMA 388 - OpenXPS Message-ID: Hi, With reference to the topic of potential registration in the IANA Printer MIB of the XPS format, here's a durable link to the ECMA OpenXPS Standard (June 2009): http://www.ecma-international.org/publications/standards/Ecma-388.htm Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From don at lexmark.com Mon Sep 14 15:14:22 2009 From: don at lexmark.com (Don Wright) Date: Mon, 14 Sep 2009 11:14:22 -0400 Subject: [PMP] Fw: [ISEP] Help Message-ID: Perhaps someone would like to help this person. ______________________________________ Don Wright, Director of Standards C14/082-3, 740 New Circle Rd, Lexington Ky 40550 Office: +1 859 825-4808 Fax: +1 859 232-7628 don at lexmark.com | f.wright at ieee.org Director, ANSI & IEEE-ISTO Chair, INCITS Executive Board Member, IEEE SA Board of Governors Treasurer, IEEE Standards Association Member: ANSI IPC, AIC, IPRPC | ECMA General Assembly ----- Forwarded by Don Wright/Lex/Lexmark on 09/14/2009 11:13 AM ----- Farouk BOUJNAH 09/14/2009 10:59 AM To: hastings at cp10.es.xerox.com, szilles at mv.us.adobe.com, don at lexmark.com, jgyllens at hpdmd48.boi.hp.com cc: Subject: [ISEP] Help Hello, I write you to have some help for my training course.Indeed, I must develop a web interface for monitor a printer. My probleme is on the OID. Indeed, after that I have to find the MIB of the printer (rfc1759.mib), I would like create a script (with PHP) which alert me when the printer will have a default.The OID that correspond at this alert is 1.3.6.1.2.1.25.3.5.1.2, but that there is on this OID give me a hexadecimal result (exple: HEX: 8004). The problem it's that I don't know that it correspond this octet.(exple: [.iso.3.6.1.2.1.25.3.5.1.2.1] => Hex: 80 04 ) I would like that you help me. Thank you and sorry for my bad english. -- BOUJNAH Farouk ?l?ve Ing?nieur en 2 i?me ann?e en Informatique fboujnah at isep.fr 06.66.62.51.48 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 3457 bytes Desc: not available URL: From wamwagner at comcast.net Mon Sep 14 17:14:45 2009 From: wamwagner at comcast.net (William Wagner) Date: Mon, 14 Sep 2009 13:14:45 -0400 Subject: [PMP] Printer MIB question Message-ID: <002e01ca355e$db4c7760$91e56620$@net> With regard to the question that you sent to hastings at cp10.es.xerox.com, szilles at mv.us.adobe.com, don at lexmark.com, jgyllens at hpdmd48.boi.hp.com, it has been forwarded to the Printer Working Group "PMP" mail list, which deals with printer MIB issues. You may well have responses from other members, but if I understand your question, it is how to interpret the response to OID [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The object value is "bit coded" as follows, and your program is interpreting the response in hexadecimal. lowPaper 0 noPaper 1 lowToner 2 noToner 3 doorOpen 4 jammed 5 offline 6 serviceRequested 7 inputTrayMissing 8 outputTrayMissing 9 markerSupplyMissing 10 outputNearFull 11 outputFull 12 inputTrayEmpty 13 overduePreventMaint 14 But remember that, in the MIB, bits are numbered starting with the most significant bit of the first byte being bit 0, To interpret 80 04, it may be easiest conceptually to covert the value to binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 and bit 13, low paper and input tray empty. Hope this helps. Note also that the current Printer MIB is RFC3805, although some printers still support only the earlier verson. Bill Wagner/ Chair, Printer Working Group WIMS/PMP -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cc at euroform.dk Mon Sep 14 17:55:35 2009 From: cc at euroform.dk (Christian Christiansen) Date: Mon, 14 Sep 2009 19:55:35 +0200 Subject: [PMP] Printer MIB question In-Reply-To: <002e01ca355e$db4c7760$91e56620$@net> References: <002e01ca355e$db4c7760$91e56620$@net> Message-ID: <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> If the endian is correct then, the value 8004 has a binary representation as follows: 1000 0000 0000 0100 That means to me that bit 15 is on and bit 2 is on. However bit 15 is NOT defined in RFC2790 So the interpretation would be "LowToner" If the endian is wrong the the value is 0480 and it has a binary representation as follows: 0000 0100 1000 0000 That means to me that bit 10 is on and bit 7 is on. In this case the interpretation would be "serviceRequested" "markerSupplyMissing" Christian Christiansen ________________________________ From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of William Wagner Sent: 14. september 2009 19:15 To: farouk.boujnah at gmail.com Cc: pmp at pwg.org Subject: [PMP] Printer MIB question With regard to the question that you sent to hastings at cp10.es.xerox.com, szilles at mv.us.adobe.com, don at lexmark.com, jgyllens at hpdmd48.boi.hp.com, it has been forwarded to the Printer Working Group "PMP" mail list, which deals with printer MIB issues. You may well have responses from other members, but if I understand your question, it is how to interpret the response to OID [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The object value is "bit coded" as follows, and your program is interpreting the response in hexadecimal. lowPaper 0 noPaper 1 lowToner 2 noToner 3 doorOpen 4 jammed 5 offline 6 serviceRequested 7 inputTrayMissing 8 outputTrayMissing 9 markerSupplyMissing 10 outputNearFull 11 outputFull 12 inputTrayEmpty 13 overduePreventMaint 14 But remember that, in the MIB, bits are numbered starting with the most significant bit of the first byte being bit 0, To interpret 80 04, it may be easiest conceptually to covert the value to binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 and bit 13, low paper and input tray empty. Hope this helps. Note also that the current Printer MIB is RFC3805, although some printers still support only the earlier verson. Bill Wagner/ Chair, Printer Working Group WIMS/PMP -- This message has been scanned for viruses and dangerous content by MailScanner , and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: From blueroofmusic at gmail.com Mon Sep 14 19:21:17 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 14 Sep 2009 15:21:17 -0400 Subject: [PMP] Printer MIB question In-Reply-To: <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> References: <002e01ca355e$db4c7760$91e56620$@net> <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> Message-ID: Hi folks, No - Bill Wagner had it right in his original reply. Right after Bill's previous quotation, RFC2790 says: "Bits are numbered starting with the most significant bit of the first byte being bit 0, the least significant bit of the first byte being bit 7, the most significant bit of the second byte being bit 8..." Read the above carefully! Bit 0 (0x8000) and bit 14 (0x0004) are set. Cheers, - Ira (co-editor of Printer MIB v2, RFC 3805) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Sep 14, 2009 at 1:55 PM, Christian Christiansen wrote: > If the endian is correct then, the value 8004 has a binary representation as > follows: > > 1000 0000 0000 0100 > > That means to me that bit 15 is on and bit 2 is on. However bit 15 is NOT > defined in RFC2790 > > So the interpretation would be > > ?LowToner? > > > > If the endian is wrong the the value is 0480 and it has a binary > representation as follows: > > 0000 0100 1000 0000 > > That means to me that bit 10 is on and bit 7 is on. > > In this case the interpretation would be > > ?serviceRequested? > > ?markerSupplyMissing? > > > > Christian Christiansen > > > > > > ________________________________ > > From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of William > Wagner > Sent: 14. september 2009 19:15 > To: farouk.boujnah at gmail.com > Cc: pmp at pwg.org > Subject: [PMP] Printer MIB question > > > > With regard to the question that you sent to hastings at cp10.es.xerox.com, > szilles at mv.us.adobe.com, don at lexmark.com, jgyllens at hpdmd48.boi.hp.com, it > has been forwarded to the Printer Working Group ?PMP? mail list, which deals > with printer MIB issues. You may well have responses from other members, but > if I understand your question, it is how to interpret the response to? OID > [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the > hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The > object value is ?bit coded? as follows, and your program is interpreting the > response in hexadecimal. > > ?? lowPaper????????????? 0 > > ?? noPaper?????????????? 1 > > ??????????????? lowToner????????????? 2 > > ??????????????? noToner?????????????? 3 > > ??????????????? doorOpen????????????? 4 > > ??????????????? jammed??????????????? 5 > > ??????????????? offline?????????????? 6 > > ??????????????? serviceRequested????? 7 > > ??????????????? inputTrayMissing????? 8 > > ??????????????? outputTrayMissing???? 9 > > ??????????????? markerSupplyMissing? 10 > > ??????????????? outputNearFull?????? 11 > > ??????????????? outputFull?????????? 12 > > ??????????????? inputTrayEmpty?????? 13 > > ??????????????? overduePreventMaint? 14 > > > > But remember that, in the MIB, bits are numbered starting with the most > significant bit of the first byte being bit 0, > > > > To interpret 80 04, it may be easiest conceptually to covert the value to > binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 > and bit 13, low paper and input tray empty. > > > > Hope this helps. Note also that the current Printer MIB is RFC3805, although > some printers still support only the earlier verson. > > > > Bill Wagner/ Chair, Printer Working Group WIMS/PMP > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pmp mailing list > pmp at pwg.org > https://www.pwg.org/mailman/listinfo/pmp > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Sep 14 21:33:21 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 14 Sep 2009 17:33:21 -0400 Subject: [PMP] Printer MIB question In-Reply-To: References: <002e01ca355e$db4c7760$91e56620$@net> <89C42F572C9E5341890080C057ED44F1013D1D0A@ef-srv-01.euroform.local> Message-ID: Hi, EEK - actually 0x0004 is bit 13 as Bill said originally (not bit 14 as I miscounted), i.e., inputTrayEmpty. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Sep 14, 2009 at 3:21 PM, Ira McDonald wrote: > Hi folks, > > No - Bill Wagner had it right in his original reply. > > Right after Bill's previous quotation, RFC2790 says: > > ?"Bits are numbered starting with the most significant > ?bit of the first byte being bit 0, the least significant bit > ?of the first byte being bit 7, the most significant bit of > ?the second byte being bit 8..." > > Read the above carefully! > > Bit 0 (0x8000) and bit 14 (0x0004) are set. > > Cheers, > - Ira (co-editor of Printer MIB v2, RFC 3805) > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Blue Roof Music/High North Inc > email: blueroofmusic at gmail.com > winter: > ?579 Park Place ?Saline, MI ?48176 > ?734-944-0094 > summer: > ?PO Box 221 ?Grand Marais, MI 49839 > ?906-494-2434 > > > > On Mon, Sep 14, 2009 at 1:55 PM, Christian Christiansen wrote: >> If the endian is correct then, the value 8004 has a binary representation as >> follows: >> >> 1000 0000 0000 0100 >> >> That means to me that bit 15 is on and bit 2 is on. However bit 15 is NOT >> defined in RFC2790 >> >> So the interpretation would be >> >> ?LowToner? >> >> >> >> If the endian is wrong the the value is 0480 and it has a binary >> representation as follows: >> >> 0000 0100 1000 0000 >> >> That means to me that bit 10 is on and bit 7 is on. >> >> In this case the interpretation would be >> >> ?serviceRequested? >> >> ?markerSupplyMissing? >> >> >> >> Christian Christiansen >> >> >> >> >> >> ________________________________ >> >> From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of William >> Wagner >> Sent: 14. september 2009 19:15 >> To: farouk.boujnah at gmail.com >> Cc: pmp at pwg.org >> Subject: [PMP] Printer MIB question >> >> >> >> With regard to the question that you sent to hastings at cp10.es.xerox.com, >> szilles at mv.us.adobe.com, don at lexmark.com, jgyllens at hpdmd48.boi.hp.com, it >> has been forwarded to the Printer Working Group ?PMP? mail list, which deals >> with printer MIB issues. You may well have responses from other members, but >> if I understand your question, it is how to interpret the response to? OID >> [.iso.3.6.1.2.1.25.3.5.1.2.1]. This appears to be the >> hrPrinterDetectedErrorState object in the host resources MIB (RFC2790.) The >> object value is ?bit coded? as follows, and your program is interpreting the >> response in hexadecimal. >> >> ?? lowPaper????????????? 0 >> >> ?? noPaper?????????????? 1 >> >> ??????????????? lowToner????????????? 2 >> >> ??????????????? noToner?????????????? 3 >> >> ??????????????? doorOpen????????????? 4 >> >> ??????????????? jammed??????????????? 5 >> >> ??????????????? offline?????????????? 6 >> >> ??????????????? serviceRequested????? 7 >> >> ??????????????? inputTrayMissing????? 8 >> >> ??????????????? outputTrayMissing???? 9 >> >> ??????????????? markerSupplyMissing? 10 >> >> ??????????????? outputNearFull?????? 11 >> >> ??????????????? outputFull?????????? 12 >> >> ??????????????? inputTrayEmpty?????? 13 >> >> ??????????????? overduePreventMaint? 14 >> >> >> >> But remember that, in the MIB, bits are numbered starting with the most >> significant bit of the first byte being bit 0, >> >> >> >> To interpret 80 04, it may be easiest conceptually to covert the value to >> binary 1000 0000 0000 0100. The value read therefore corresponds to bits 0 >> and bit 13, low paper and input tray empty. >> >> >> >> Hope this helps. Note also that the current Printer MIB is RFC3805, although >> some printers still support only the earlier verson. >> >> >> >> Bill Wagner/ Chair, Printer Working Group WIMS/PMP >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> _______________________________________________ >> pmp mailing list >> pmp at pwg.org >> https://www.pwg.org/mailman/listinfo/pmp >> >> > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Tue Sep 22 02:17:31 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 21 Sep 2009 22:17:31 -0400 Subject: [PMP] IANA Printer MIB updates from PWG5100.9 Message-ID: Hi, Today, I sent large IANA Printer MIB updates to IANA - I'll keep folks posted on progress. Taken from IPP Printer State Reasons [PWG5100.9], I sent IANA Printer MIB updates for PrtAlertCodeTC. I also just uploaded them to the PWG FTP server at: ftp://ftp.pwg.org/pub/pwg/pmp/iana/ in the file: iana-prt-20090921.zip Cheers, - Ira (IPP and Printer MIB co-editor) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Fri Oct 2 01:08:23 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Thu, 1 Oct 2009 21:08:23 -0400 Subject: [PMP] Posted Cmd Set Format for 1284 Device ID (1 Oct 2009) Message-ID: Hi, I just posted a first complete draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091001.pdf For review during the WIMS/CIM/PMP WG session at the PWG Meeting at Apple on Tuesday 13 October 2009. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Nov 2 18:49:15 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 2 Nov 2009 13:49:15 -0500 Subject: [PMP] langXPS and langOpenXPS Message-ID: Hi, For immediate review (today if possible): ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt Mike Fenelon, Michael Sweet, and I have had a productive offline conversation this last week about this. Mike Fenelon proposed two enums and this justification: "The OpenXPS spec is already complete and it does have differences from the MS spec. Since the 2 specifications/types have completely different namespaces I think it is pretty important to have 2 definitions. There are already a number of devices that support the current specification: langXPS. And all Windows 7 clients will generate this format. And MS and others have committed to supporting the new OpenXPS spec also. It is very important to know which." Cheers, - Ira (joint IETF Designated Expert for IANA Printer MIB) ----------------------------------------------------------------------------------- (view in a fixed width font) In PrtInterpreterLangFamilyTC, after 'langC4(65)' add: langXPS(66), -- Not in RFC 3805 -- Microsoft XML Paper Specification -- http://www.microsoft.com/whdc/xps/xpsspec langOpenXPS(67) -- Not in RFC 3805 -- ECMA OpenXPS -- http://www.ecmainternational.org/ -- publications/standards/Ecma-388.htm Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Nov 2 23:29:12 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 2 Nov 2009 18:29:12 -0500 Subject: [PMP] plasticMultiRing submitted for IANA Finisher MIB Message-ID: Hi, Harry Lewis reminded me last week that we hadn't yet submitted his approved 'plasticMultiRing' for IANA Finisher MIB - oops! Since it was unanimously approved during our August F2F, I submitted it to IANA last Friday. I'll let the PMP/WIMS mailing lists know when it's completed by IANA. Cheers, - Ira (IETF Designated Expert for IANA Finisher MIB) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Tue Nov 3 02:15:53 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 2 Nov 2009 21:15:53 -0500 Subject: [PMP] Re: langXPS and langOpenXPS In-Reply-To: References: Message-ID: Hi Mike, THANKS! My cut-and-paste error. I have corrected and reposted (to the same dated filename): ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt All - if there are no opposing opinions or clarifications by Thursday (12 November) next week, I will submit these updates to IANA. Cheers, - Ira (IETF Designated Expert for IANA Printer MIB) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Nov 2, 2009 at 7:45 PM, Mike Fenelon wrote: > I discovered a problem in the URL for OpenXPS. > > It is actually: http://www.ecma-international.org/publications/standards/Ecma-388.htm > > Notice the - between ecma & international > > Mike Fenelon > Microsoft > > > -----Original Message----- > From: Ira McDonald [mailto:blueroofmusic at gmail.com] > Sent: Monday, November 02, 2009 10:49 AM > To: pmp at pwg.org; wims at pwg.org; Ira McDonald; Mike Fenelon; Michael R Sweet > Subject: langXPS and langOpenXPS > > Hi, > > For immediate review (today if possible): > > ?ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt > > Mike Fenelon, Michael Sweet, and I have had a productive > offline conversation this last week about this. > > Mike Fenelon proposed two enums and this justification: > > "The OpenXPS spec is already complete and it does have > differences from the MS spec. ?Since the 2 specifications/types > have completely different namespaces I think it is pretty > important to have 2 definitions. > > There are already a number of devices that support the current > specification: langXPS. ?And all Windows 7 clients will generate > this format. And MS and others have committed to supporting > the new OpenXPS spec also. It is very important to know which." > > Cheers, > - Ira (joint IETF Designated Expert for IANA Printer MIB) > > ----------------------------------------------------------------------------------- > (view in a fixed width font) > > In PrtInterpreterLangFamilyTC, after 'langC4(65)' add: > > ? ? ? langXPS(66), ? ? ? ? -- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- Microsoft XML Paper Specification > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- http://www.microsoft.com/whdc/xps/xpsspec > ? ? ? langOpenXPS(67) ? ? ?-- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- ECMA OpenXPS > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- http://www.ecmainternational.org/ > ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- ? publications/standards/Ecma-388.htm > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Blue Roof Music/High North Inc > email: blueroofmusic at gmail.com > winter: > ?579 Park Place ?Saline, MI ?48176 > ?734-944-0094 > summer: > ?PO Box 221 ?Grand Marais, MI 49839 > ?906-494-2434 > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Tue Nov 3 18:02:30 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Tue, 3 Nov 2009 13:02:30 -0500 Subject: [PMP] SeaMonkey 2.0 - fine WYSIWIG HTML editor Message-ID: Hi, For anyone who edits web pages or complex HTML forms (like the DMTF CIM Change Request template), a fine tool just got a lot better. SeaMonkey 2.0 now uses common infrastructure with Firefox 3.5: http://www.seamonkey-project.org/releases/ Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Wed Nov 4 03:39:13 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Tue, 3 Nov 2009 22:39:13 -0500 Subject: [PMP] Fwd: [IANA #275889] plasticMultiRing in IANA Finisher MIB - DONE! Message-ID: Hi, Considering that I submitted this update (Harry's new binding type) last Friday to IANA, this is lightspeed turnaround! Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 ---------- Forwarded message ---------- From: Amanda Baber via RT Date: Tue, Nov 3, 2009 at 9:12 PM Subject: [IANA #275889] General Request for Assignments (ianafinisher-mib) To: blueroofmusic at gmail.com Hi Ira, This request is complete: http://www.iana.org/assignments/ianafinisher-mib Let us know if anything needs to be fixed/expanded upon. Thanks, Amanda On Fri Oct 30 16:39:29 2009, blueroofmusic at gmail.com wrote: > Contact Name : > Ira McDonald > > Contact Email : > blueroofmusic at gmail.com > > Type of Assignment : > Permanent enumerated name/value in FinBindingTypeTC > Please add to end after padding(11): > > ? ? ? ? plasticMultiRing(12) > > Registry : > IANA Finisher MIB > http://www.iana.org/assignments/ianafinisher-mib > > Description : > Proposed by Harry Lewis (InfoPrint Solutions Company). > Reviewed by email discussion on Finisher MIB WG mailing list. > Approved by Ira McDonald (IETF Designated Expert for IANA Finisher MIB). > > Additional Info : > IANA Finisher MIB originally published in RFC 3806. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From harry.lewis at infoprint.com Wed Nov 4 04:21:00 2009 From: harry.lewis at infoprint.com (Harry Lewis) Date: Tue, 3 Nov 2009 21:21:00 -0700 Subject: [PMP] Re: Fwd: [IANA #275889] plasticMultiRing in IANA Finisher MIB - DONE! In-Reply-To: Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 590 bytes Desc: not available URL: From blueroofmusic at gmail.com Mon Nov 23 23:54:18 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 23 Nov 2009 18:54:18 -0500 Subject: [PMP] langXPS registered in IANA Printer MIB Message-ID: Hi, Last Friday - I sent the request to IANA. Today (1 business day later), Amanda finished the update - cool. Cheers, - Ira (IETF Designated Expert for IANA Printer MIB) ---------- Forwarded message ---------- From: Amanda Baber via RT Date: Mon, Nov 23, 2009 at 6:08 PM Subject: [IANA #281267] General Request for Assignments (ianaprinter-mib) To: blueroofmusic at gmail.com Hi Ira, This is complete. See http://www.iana.org/assignments/ianaprinter-mib Thanks, Amanda On Fri Nov 20 22:59:36 2009, blueroofmusic at gmail.com wrote: > Contact Name : > Ira McDonald > > Contact Email : > blueroofmusic at gmail.com > > Type of Assignment : > Permanent enumerated name/value in PrtInterpreterLangFamilyTC. > Please add to end after langC4(65): > > ? ? ? ?langXPS(66), ? ? ? ? -- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- Microsoft XML Paper Specification > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- http://www.microsoft.com/whdc/xps/xpsspec > ? ? ? ?langOpenXPS(67) ? ? ?-- Not in RFC 3805 > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- ECMA OpenXPS > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- http://www.ecma-international.org/ > ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- ? publications/standards/Ecma-388.htm > > Exact text for this update is archived at: > ? ftp://ftp.pwg.org/pub/pwg/pmp/iana/langxps-20091102.txt > > > > Registry : > IANA Printer MIB > http://www.iana.org/assignments/ianaprinter-mib > > Description : > Proposed by Mike Fenelon (Microsoft) and Peter Zehler (Xerox). > Reviewed by email discussion on Printer MIB WG mailing list. > Approved by Ira McDonald (IETF Designated Expert for IANA Printer MIB). > > Additional Info : > IANA Printer MIB originally published in RFC 3805. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Nov 30 22:29:54 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 30 Nov 2009 17:29:54 -0500 Subject: [PMP] Posted Cmd Set Format for 1284 Device ID (30 Nov 2009) Message-ID: Hi, I just posted a Prototype draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130.pdf / doc - clean copy ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130-rev.pdf / doc - with redlines For review during the WIMS/CIM/PMP WG session during the PWG Face-to-Face at Dell on Tuesday 8 December 2009. Cheers, - Ira ---------------------------------------------------------------- Changes to create the version of 30 November 2009 ? Prototype Draft - Editorial ? changed document status to Prototype Draft, per WIMS WG discussion - Editorial ? revised section 3 Requirements to downcase all imperatives (SHOULD -> should, etc.) - Technical ? revised section 3.2.3 External Network Adapter ? Local Printer, to clarify that local (USB, etc.) Device IDs should not be changed and should be passed through as is, per Jerry Thrasher - Technical ? revised section 5 Definition of Command Set Format in ABNF, to add private types for compatibility with existing practice, per analysis of MIB walks of network printers - Technical ? revised section 5 Definition of Command Set Format in ABNF, to allow 1 or more control characters (CR, LF, or HTAB) *before* each command language keyword (but NOT infixed), per Jerry Thrasher and IEEE 1284 section 7.6 specification - Editorial ? renamed section 6.1 from Conformance for Imaging Systems to Conformance for Network Spoolers and Network Printers, per Jerry Thrasher - Technical ? added new section 6.2 Conformance for External Network Adapters (MUST NOT change IEEE 1284 Device ID values from local printers), per Jerry Thrasher ----------------------------------------------------- Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc email: blueroofmusic at gmail.com winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From blueroofmusic at gmail.com Mon Dec 14 17:02:53 2009 From: blueroofmusic at gmail.com (Ira McDonald) Date: Mon, 14 Dec 2009 12:02:53 -0500 Subject: [PMP] 1284 Cmd Set w/ IPP "printer-device-id" (14 December 2009) Message-ID: Hi, [To: PMP, WIMS, IPP] I just posted an expanded Prototype draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091214.pdf / doc - clean copy w/ line numbers ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130-rev.pdf / doc - with redlines and line numbers This version defines the new IPP Printer attribute "printer-device-id (text(1023))", per the IPP WG and WIMS WG discussions last week at December PWG F2F. For review at today's WIMS WG teleconference and WIMS WG last call through early January. Cheers, - Ira ---------------------------------------------------------------- Changes to create the version of 14 December 2009 ? Prototype Draft - Editorial ? kept document status at Prototype Draft, per December PWG F2F - Editorial ? revised Abstract and section 1 Introduction to include new IPP ?printer-device-id?, per December PWG F2F - Editorial ? renamed section 3.2.3 to External Network Adapter with locally-attached Printer, for clarity - Technical ? revised all of section 3 Requirements to include new IPP ?printer-device-id?, per December PWG F2F - Editorial ? renamed section 5 to PWG Extensions to IEEE 1284 Device ID, per December PWG F2F - Technical ? added section 5.2 IPP printer-device-id (text(1023)), per December PWG F2F - Technical ? revised section 6 to include REQUIRED implemention of ?printer-device-id? for IPP/2.0 and higher versions (to be added to IPP Version 2.0 Second Edition as well) - Editorial ? revised section 7 IANA and PWG Considerations to include the IANA registration for the new IPP ?printer-device-id? attribute defined in section 5.2 - Editorial ? deleted unused section 13 Appendix A ? Design Alternatives -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From wamwagner at comcast.net Tue Dec 15 18:43:58 2009 From: wamwagner at comcast.net (William Wagner) Date: Tue, 15 Dec 2009 13:43:58 -0500 Subject: [PMP] 1284 Cmd Set w/ IPP "printer-device-id" (14 December 2009) In-Reply-To: References: Message-ID: <000001ca7db6$90a65460$b1f2fd20$@net> At the WIMS/PMP conference call yesterday, it was agreed that this latest draft of the IEEE 1284 Device ID Command Set Format document: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091214.pdf / doc appears to address all issues brought up to date. As agreed at the WIMS face-to-face, this document is now in working group last call. All comments will be considered, but especially from members of PMP, WIMS and IPP WK. Please review the document and post any comments or objections to the combined PMP, WIMS and IPP maillists. These comments will be reviewed at the 11 January WIMS conference call. It is understood that a statement of prototype/product implementation will be provided shortly. This should allow advancing the document to stable status and submitting it to a PWG last call period including the February face-to-face. Thanks, Bill Wagner -----Original Message----- From: pmp-bounces at pwg.org [mailto:pmp-bounces at pwg.org] On Behalf Of Ira McDonald Sent: Monday, December 14, 2009 12:03 PM To: pmp at pwg.org; wims at pwg.org; ipp at pwg.org; Ira McDonald Subject: [PMP] 1284 Cmd Set w/ IPP "printer-device-id" (14 December 2009) Hi, [To: PMP, WIMS, IPP] I just posted an expanded Prototype draft of the PWG Command Set Format for IEEE 1284 Device ID at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091214.pdf / doc - clean copy w/ line numbers ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmp1284cmdset10-20091130-rev.pdf / doc - with redlines and line numbers This version defines the new IPP Printer attribute "printer-device-id (text(1023))", per the IPP WG and WIMS WG discussions last week at December PWG F2F. For review at today's WIMS WG teleconference and WIMS WG last call through early January. Cheers, - Ira ---------------------------------------------------------------- Changes to create the version of 14 December 2009 - Prototype Draft - Editorial - kept document status at Prototype Draft, per December PWG F2F - Editorial - revised Abstract and section 1 Introduction to include new IPP "printer-device-id", per December PWG F2F - Editorial - renamed section 3.2.3 to External Network Adapter with locally-attached Printer, for clarity - Technical - revised all of section 3 Requirements to include new IPP "printer-device-id", per December PWG F2F - Editorial - renamed section 5 to PWG Extensions to IEEE 1284 Device ID, per December PWG F2F - Technical - added section 5.2 IPP printer-device-id (text(1023)), per December PWG F2F - Technical - revised section 6 to include REQUIRED implemention of "printer-device-id" for IPP/2.0 and higher versions (to be added to IPP Version 2.0 Second Edition as well) - Editorial - revised section 7 IANA and PWG Considerations to include the IANA registration for the new IPP "printer-device-id" attribute defined in section 5.2 - Editorial - deleted unused section 13 Appendix A - Design Alternatives -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pmp mailing list pmp at pwg.org https://www.pwg.org/mailman/listinfo/pmp -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.