Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09573; 2 May 96 14:27 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09569; 2 May 96 14:27 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa26783; 2 May 96 14:27 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA101360978; Thu, 2 May 1996 11:16:19 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA256350975; Thu, 2 May 1996 12:16:15 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA12148; Thu, 2 May 96 12:05:53 -0600 Received: from interlock.lexmark.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA157050959; Thu, 2 May 1996 11:16:00 -0700 Received: by interlock.lexmark.com id AA18535 (InterLock SMTP Gateway 3.0 for pmi@hpbs987.boi.hp.com); Thu, 2 May 1996 14:06:23 -0400 Message-Id: <199605021806.AA18535@interlock.lexmark.com> Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-2); Thu, 2 May 1996 14:06:23 -0400 Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-1); Thu, 2 May 1996 14:06:23 -0400 To: "pmi%hpbs987.boi.hp.com" Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Don Wright Date: 2 May 96 14:11:56 EDT Subject: Action Items and May Meeting Notice (sort of) Mime-Version: 1.0 Content-Type: Text/Plain Here's the first pass of a meeting notice for May. Looks like the hotel arrangement are still TBD. I'll let everyone know as soon as it finalizes. Don To: p1284_3 @ pad.prtdev.lexmark.com (Multiple recipients of list) @ SMTP cc: (bcc: Don Wright) From: lstein @ fapo.com (Larry Stein) @ interlock.lexmark.com @ SMTP Date: 05-02-96 11:28:45 AM Subject: Action Items and May Meeting Notice (sort of) The May meetings of the P1284.3, .4 and PWG will be held in Chicago area. The meeting dates are: P1284.4 Monday, May 20 !!!Note the change in order!!!! P1284.3/4 Tuesday, May21 PWG Wed/Thur, May 22-23 Due to a major convention in Chicago that week, I am having some difficulty in finalizing the hotel arraignments. I will send out the hotel information by Monday, May 6. Sorry, but everyone will have to be very quick to make their reservations. The P1284.3 committee is in the process of finalizing the software services section of the standard. This work will be coordinated with the P1284.4 standard Datalink services. For the next couple of months we will combine the .3 and .4 meetings (loosly). The Datalink portion of the .4 will be done on Tuesday during the .3 meeting. We will be able to use Tuesday for any overflow from the Monday meeting. The following list outlines the various action items that are outstanding. Some of you are key contributors to some of the items. If you do not believe that you will have your material ready by the proposed meeting date then please let me know ahead of time. Otherwise, the meeting agendas will consist of these action items. Action Items for IEEE P1284.3 and P1284.4 Updated- 2 May 1996 1. Address Service May draft, June final Brian, Randy, Steve (Bob S.?) Propose a method for the discovery of services. 2. Datalink Functionality May/June draft, July final Brian, Randy, Larry, Rick, Bill, Bob Mc., Grant, Walt, Balaji, Mark Develop the requirements for the Datalink layer. This will be a coordination between the .3 and the .4 committees. 3. Peer to Peer May strategy, June draft, July final Randy, Brian How can either side start a conversation without waiting for permission? 4. Status Byte May proposal, June final Committee How will the Status byte be used? Bit or Byte enumeration? 4A. Registration May Larry Check with IEEE to see how a Registry of Status values or Services can be handled. 5. Naming Conventions May Joe, Larry, Committee What naming conventions will be used in the .4 standard? In particular, what is meant by EOF, EOJ and EOS? Suggest using the conventions used in the IEEE P1284.1 draft. Review sections 2.0 and 5.4 of the draft. 6. P1284.3 Contention and Data Services May draft, June/July final Randy, Grant, Larry, Bill, Committee Finalize proposal on software services for the multiport architecture. Coordinate with the .4 Datalink requirements. 7. P1284.4 Draft May Brian Initial draft and outline of the standard. 8. P1284.3 and P1284.4 Test Requirements July/August strategy, Sep/Oct draft, Nov final(?) Mike M., Committee(s) How do we define compliance to these standards? Do we want to develop a test standard similar to P1284.2? Thanks, Larry -- ******************************************************************* Larry A. Stein FarPoint Communications, Lancaster, CA http://www.fapo.com Ph. 805/726-4420 Fax 805/726-4438 *******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17304; 3 May 96 10:22 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17300; 3 May 96 10:22 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa10506; 3 May 96 10:22 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA167953081; Fri, 3 May 1996 07:18:02 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA199603077; Fri, 3 May 1996 08:17:57 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21026; Fri, 3 May 96 08:07:20 -0600 Received: from interlock.lexmark.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA246182924; Fri, 3 May 1996 07:15:33 -0700 Received: by interlock.lexmark.com id AA24087 (InterLock SMTP Gateway 3.0 for pmi@hpbs987.boi.hp.com); Fri, 3 May 1996 10:03:59 -0400 Message-Id: <199605031403.AA24087@interlock.lexmark.com> Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-2); Fri, 3 May 1996 10:03:59 -0400 Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-1); Fri, 3 May 1996 10:03:59 -0400 To: "pmi%hpbs987.boi.hp.com" Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Don Wright Date: 3 May 96 10:09:11 EDT Subject: Minutes Mime-Version: 1.0 Content-Type: Text/Plain I have posted the April meeting minutes on the ftp server as follows: minutes/dmtfkmin.doc WORD 2.0 format minutes/dmtfkmin.ps PostScript minutes/dmtfkmin.pdf Acrobat Reader format minutes/dmtfkmin.txt Plain, old, boring flat ASCII text Binnur: can you fix up the permissions?? Don ************************************************************* * Don Wright Lexmark International * * Manager Strategic Alliances * * 740 New Circle Rd Phone: 606-232-4808 * * Lexington, KY 40511 Fax: 606-232-6740 * *************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18630; 3 May 96 11:06 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18626; 3 May 96 11:06 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa13290; 3 May 96 11:06 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA013795522; Fri, 3 May 1996 07:58:42 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA027755510; Fri, 3 May 1996 08:58:30 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21079; Fri, 3 May 96 08:48:02 -0600 Received: from uscore.underscore.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA104345491; Fri, 3 May 1996 07:58:11 -0700 Received: by uscore.underscore.com (Smail3.1.28.1 #5) id m0uFMD6-000US3C; Fri, 3 May 96 10:51 EDT Message-Id: Date: Fri, 3 May 96 10:51 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: JK Martin To: pmi@hpbs987.boi.hp.com Subject: Comments on the April Meeting Minutes In reviewing the just-posted meeting minutes from last month, the text describing the "requirements" for submitting a new Type 2 Enum appears a bit confusing. First, this summary paragraph presented: > The registration requirements for an enum: > - descriptive name > - description > - published spec > - contact > - submitter > will be added to the front section of the MIB. This sounds pretty "final" to me; however, the minutes continue with: > The group discussed the need for available documentation for an > enumeration. Some thought that documentation must eventually > be made available while others believe that is not a > requirement. Tom Hastings proposed that an enum request should > indicate whether documentation is or soon will be publicly > available or if that enum represents a private value that will > not be documented publicly. Another concern expressed is the > lifetime of this group. How will the enum type 2 process > continue after this group no longer meets? One of the values > of the type 2 enum is to prevent duplication of enums. So, what exactly was the PWG's final consensus on the issue of mandating that a "published spec" be required as part of submitting/acquiring a registered Type 2 Enum? To my recollection, no such publication was required, and that it is perfectly acceptable to register a non-public (ie, proprietary or otherwise) enum for Type 2 class enums in the Printer MIB. Precedent has shown this to be the case; moreover, at that very same meeting the group approved at least one Type 2 enum for a channel type that has no public, published spec. Furthermore, in raising this discussion to a bit of a higher level, the group discussed the philosophical notion of exactly who may "participate" in the Printer MIB with respect to the integration of proprietary mechanisms. Some in the group believed that only open, standard mechanisms be allowed for Type 2 Enums, stating that the MIB was only supposed to address open mechanisms. After some discussion, the group realized that this simply was NOT true, and that proprietary mechanisms should coexist with open mechanisms. The bottom line in this discussion is that the Printer MIB is supposed to be part of a mechanism to acquire (and possibly control) the data domain of a printer. Period. If some of that data is proprietary in form/nature, well that's just fine. These are my recollections. Do others' recollections differ? I raise this issue so as to ensure the world has a complete understanding of the PWG's decision in this matter. ...jay   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20515; 3 May 96 12:25 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20509; 3 May 96 12:25 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa16917; 3 May 96 12:24 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA031100278; Fri, 3 May 1996 09:17:59 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA225050273; Fri, 3 May 1996 10:17:53 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21194; Fri, 3 May 96 10:07:36 -0600 Received: from uscore.underscore.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA255564410; Fri, 3 May 1996 07:40:29 -0700 Received: by uscore.underscore.com (Smail3.1.28.1 #5) id m0uFLuC-000US3C; Fri, 3 May 96 10:32 EDT Message-Id: Date: Fri, 3 May 96 10:32 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: JK Martin To: pmi@hpbs987.boi.hp.com Subject: Re: Minutes Cc: binnur@hpb15650.boi.hp.com, don@lexmark.com I have changed the protections of the files listed below so that anonymous logins have read access. ...jay > From lexmark.com!don Fri May 3 10:20:47 1996 > To: "pmi%hpbs987.boi.hp.com" > From: Don Wright > Date: 3 May 96 10:09:11 EDT > Subject: Minutes > Mime-Version: 1.0 > > I have posted the April meeting minutes on the ftp server as > follows: > > minutes/dmtfkmin.doc WORD 2.0 format > minutes/dmtfkmin.ps PostScript > minutes/dmtfkmin.pdf Acrobat Reader format > minutes/dmtfkmin.txt Plain, old, boring flat ASCII text > > Binnur: can you fix up the permissions?? > > Don   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16407; 4 May 96 13:45 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16403; 4 May 96 13:45 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa09415; 4 May 96 13:45 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA079041666; Sat, 4 May 1996 10:41:06 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA249601662; Sat, 4 May 1996 11:41:03 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA22782; Sat, 4 May 96 11:30:42 -0600 Received: from interlock.lexmark.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA093901652; Sat, 4 May 1996 10:40:52 -0700 Received: by interlock.lexmark.com id AA06801 (InterLock SMTP Gateway 3.0 for pmi@hpbs987.boi.hp.com); Sat, 4 May 1996 13:32:15 -0400 Message-Id: <199605041732.AA06801@interlock.lexmark.com> Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-2); Sat, 4 May 1996 13:32:15 -0400 Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-1); Sat, 4 May 1996 13:32:15 -0400 To: "pmi%hpbs987.boi.hp.com" Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Don Wright Date: 4 May 96 12:30:01 EDT Subject: May Meeting Notice (finally) Mime-Version: 1.0 Content-Type: Text/Plain Here's the details on the May meeting... Don To: p1284_3 @ pad.prtdev.lexmark.com (Multiple recipients of list) @ SMTP cc: (bcc: Don Wright) From: lstein @ fapo.com (Larry Stein) @ interlock.lexmark.com @ SMTP Date: 05/03/96 12:39:36 PM Subject: May Meeting Notice (finally) Meeting Notice IEEE P1284.3 IEEE P1284.4 PWG The May meetings will be held as follows: IEEE P1284.3 Tuesday, May 21 IEEE P1284.4 Monday, May 20 to Tuesday, May 21 Printer Working Group Wednesday - Thursday, May 22-23 All meeting will start at 8:30AM, breakfast will be available starting at 8:00AM. Sheraton North Shore Hotel Northbrook (Chicago), Illinois 933 Skokie Blvd. Ph. (708) 498-6500 Fax (708) 498-9558 The room rate is $99.00 single, $109.00 double. The meeting charge is $(still TBD) per person, per meeting day. The charge includes all meeting room expenses, breakfast, AV charges and break charges. Sorry for the short notice. You MUST make your reservations by Friday, May 10, and be sure to tell them you are with the FarPoint group. Thank you, Larry Stein -- ******************************************************************* Larry A. Stein FarPoint Communications, Lancaster, CA http://www.fapo.com Ph. 805/726-4420 Fax 805/726-4438 *******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26993; 6 May 96 16:20 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa26989; 6 May 96 16:20 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa17174; 6 May 96 16:19 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA121902564; Mon, 6 May 1996 12:56:04 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA244852555; Mon, 6 May 1996 13:55:55 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA02943; Mon, 6 May 96 13:45:32 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <318E594D@hpb15650.boi.hp.com>; Mon, 06 May 96 13:55:57 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: Draft Printer MIB review reminder Date: Mon, 06 May 96 14:57:00 M Message-Id: <318E594D@hpb15650.boi.hp.com> Encoding: 19 TEXT X-Mailer: Microsoft Mail V3.0 The draft Printer MIB is available on the ftp server: ftp://ftp-out.external.hp.com/snmpmib/prtspec/printer-mib.{doc,ps} Please take your time, and review the document since it will replace RFC 1759 (Printer MIB) eventually. Also, pass the document around for others in your company to review.. It is also important for you to report back your comments not only on the document, but also on your overall impression on Printer MIB, any possible concerns, etc. If you have some operational experience with Printer MIB, we definitely would like to hear about it.. I would like to receive the results of your review by June 3rd. This will give enough time for discussions to take place on the mailing list before the June PWG meeting (June 27 & 28). --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27336; 6 May 96 16:30 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27332; 6 May 96 16:30 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa17345; 6 May 96 16:30 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA261764278; Mon, 6 May 1996 13:24:39 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA019184275; Mon, 6 May 1996 14:24:35 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA02999; Mon, 6 May 96 14:14:16 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <318E6009@hpb15650.boi.hp.com>; Mon, 06 May 96 14:24:41 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: May agenda items (PMP) & Printer MIB document time line Date: Mon, 06 May 96 15:27:00 M Message-Id: <318E6009@hpb15650.boi.hp.com> Encoding: 41 TEXT X-Mailer: Microsoft Mail V3.0 May meeting is around the corner, and here are my thoughts on the Printer MIB/MIF project. Let me know what you think.. 1. We are doing a Printer MIB review here @ HP with 20+ individuals.. If you are doing a similar operation in your company, let me know.. 2. Completion of the document review & results by June 3rd. 3. Discussions on the mailing list during the month of June. 4. At the June (27/28) PWG meeting: * finalize the document by ironing out any issues that may not have been resolved over the mailing list. * finalize a recommendation for doing the interoperability testing * outline the next step & schedules for the Printer MIB (i.e. recommendation to move it to the draft standard) Items of discussion from April meeting - Printer MIB/MIF project 1. Channels - At the last meeting we concluded that the use of NSM (Network Services Monitoring MIB) might solve our needs. I haven't seen any comments on this (unless I lost it..) 2. The question on changing the references to the Interfaces Group of MIB-II to require compliance with Evolution of the Interfaces Group of MIB-II. 3. Reviewing the Printer MIB document. 4. If a peripheral (HP, Lexmark, Xerox, IBM, others?) has implemented Printer MIB, then provide information on: * Which groups has been implemented by the printer * Any implementation experience 5. Others that I am missing?? Items of discussions for May meeting's Printer MIB project: 1. any comments on the Printer MIB document; make sure you also send those comments out to the mailing list 2. finalizing channel discussion (unless we finalize it over the mailing list) 3. others?? --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27726; 6 May 96 16:43 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27722; 6 May 96 16:43 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa17570; 6 May 96 16:43 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA022375059; Mon, 6 May 1996 13:37:40 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA073685057; Mon, 6 May 1996 14:37:37 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA03017; Mon, 6 May 96 14:27:19 -0600 Received: from novell.com (prv-ums.Provo.Novell.COM) by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA215035051; Mon, 6 May 1996 13:37:31 -0700 Received: from INET-PRV-Message_Server by fromGW with Novell_GroupWise; Mon, 06 May 1996 14:35:14 -0600 Content-Length: 652 Content-Type: text/plain Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Mon, 06 May 1996 14:34:03 -0600 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jay Cummings To: pmi@hpbs987.boi.hp.com Subject: Appendix E-Participants list needs to be updated For this future document, we need to update the participants list. I know that Craig Whittle's company has changed from Compaq to Novell for this new document, and my name should be added. I'm sure there are several other changes that should be made to this section. /* - - -S-I-G-N-A-T-U-R-E- -B-L-O-C-K- - - Jay R. Cummings Services Manageability Development Team Development Manager Novell, Inc. -- where #Everything#s Connected# Prv-D-12-1 122 East 1700 South Provo, Utah 84606 Phone: 1-800-453-1267 x.3895 (801) 861-3895 Fax: (801) 861-7520 INTERNET: jay_cummings@novell.com - - -S-I-G-N-A-T-U-R-E- -B-L-O-C-K- - - */   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24691; 7 May 96 15:24 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa24687; 7 May 96 15:24 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa14131; 7 May 96 15:24 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA028036567; Tue, 7 May 1996 12:16:08 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA140406563; Tue, 7 May 1996 13:16:03 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA10349; Tue, 7 May 96 13:05:44 -0600 Received: from avalon.dpc.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA229376555; Tue, 7 May 1996 12:15:55 -0700 Received: (from smap@localhost) by avalon.dpc.com (8.6.11/8.6.9) id LAA20521 for ; Tue, 7 May 1996 11:49:33 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: rbergma%miami.dnet.dpc.com@gate.dpc.com Received: from gate(10.30.0.166) by avalon via smap (V1.3) id sma020518; Tue May 7 11:49:22 1996 Received: by gate.dpc.com (5.65/DEC-Ultrix/4.3) id AA12017; Tue, 7 May 1996 11:49:36 -0700 Date: Tue, 7 May 1996 11:49:36 -0700 Message-Id: <9605071849.AA12017@gate.dpc.com> To: "GATE pmi@hpbs987.boi.hp.com"@avalon.dpc.com Subject: Jobs MIB Charter and revised Goals The following Statement of Charter should agree with the results of the meeting in Alexandria. (This is the version published in the meeting minutes.) I have also modified the Goals section from the document "Proposed Specification of Information Objects/Attributes for the Printer Job Monitoring MIB/MIF", revision 0.9 dated 1/16/96, by Tom Hastings. I know some of these goals will require refinement, so send comments by email or be prepared to discuss in Chicago. (I will bring "clean" copies of the document to the meeting.) I will prepare an agenda for the Job Monitoring Project and post it to the reflector early next week (at the latest). Ron Bergman Dataproducts Corp rbergma@dpc.com -------------------------------------------------------------- The Printer Job Monitoring and Resource Accounting MIB Project -------------------------------------------------------------- Statement of Charter: This project shall develop a set of objects for monitoring of the status and progress of print jobs and to obtain resource accounting data at the completion of a job. The object set will initially be developed independent from the management system format. The object set development shall not preclude use of the set with either an SNMP MIB, a DMI MIF, or the SENSE protocol. Use of the object set shall not be limited to printers. To obtain complete information regarding a print job in many printing systems will require the object set to be implemented into a file server, spooler, and/or a printer management system software. When the object set is finalized, an SNMP MIB will be developed. The object set may also be ported to other formats, such as SENSE and a DMI MIF, as an extension to this project. Goals: 1. The job MIB is intended to provide the following information for the indicated Role Models (see Appendix D - Roles of Users in the Printer MIB draft update to RFC 1759). A limited set of mandatory job and document attributes for a printer, plus a set of optional attributes, will be developed to provide this information. User: (U1) - A timely notification that his job has completed and where. (U2) - The current status of the user's job (user queries). (U3) - Error and diagnostic information for jobs that did not successfully complete. (U4) - Ability to identify the least busy printer. Operator: (OP1) - A presentation of the state of all the jobs in the print system. (OP2) - Which users submitted each job. (OP3) - What resources does each job need. (OP4) For which physical printers are the jobs candidates. (OP5) Some idea of how long each job will take. Capacity Planner: (C1) - How busy are printers. (C2) - What time of day are they used. (C3) - How long do users' jobs wait before starting to print. Accountant: (A1) - A record of resources used and printer usage data for charging users or groups for resources used. 2. The MIB will provide for printers that can contain more than one job at a time, but still be usable for low end printers that only contain a single job at a time. In particular, the MIB shall meet the needs of Windows and other PC environments for managing low-end networked devices without unnecessary overhead or complexity, while also providing for higher end systems and devices. Since the job MIB may also be transformed into a companion DMTF MIF, the job MIB/MIF should meet the needs for managing devices using the DMTF DMI when the devices are directly connected to PCs. 3. The MIB will provide job resource accounting information after the printer has finished printing the job. This resource accounting information is intended to be used by: - A management station that is co-located with the printer to provide an enhanced console capability. - End user job monitoring programs that provide status on progress and completion of jobs during the complete life cycle of the job, including a defined period after the job completes. - System accounting programs that copy the completed job statistics to an accounting system. It is recognized that depending on accounting programs to copy MIB data during the job-retention period is somewhat unreliable, since the accounting program may not be running (or may have crashed). - System usage statistics gathering programs that copy the completed job statistics to system usage logs. 4. The MIB will provide a compatible subset of job and document attributes of the ISO DPA standard, so that coherence is maintained between the two protocols and information presented to end users and system operators. However, the printer job monitoring MIB is intended to be used with printers that implement other job submitting and management protocols, such as IEEE 1284.1 (NPAP), as well as with ones that do implement ISO DPA. So nothing in the printer job monitoring MIB shall require implementation of the ISO DPA protocol. 5. The MIB will be designed so that an additional MIB(s) can be specified in the future for monitoring multifunction (scan, FAX, copy) jobs. The job MIB will be designed such that a future multifunction job monitoring MIB will be able to use entire groups from this MIB. 6. The MIB will provide a limited degree of security such that unauthorized users cannot access job information for jobs that are not theirs. 7. The MIB will provide for the monitoring of jobs that clients submit directly to printers, to printer supervisor control programs, or to spooling print systems. 8. The MIB will provide SNMP MIB access to jobs submitted to the printer by any protocol, including printers that accept jobs using multiple protocols. 9. Schedule: Submit a request for an IETF charter for this project at the December IETF meeting. The request will not be submitted until a final draft of the Job Monitoring object set has been completed.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23646; 8 May 96 15:48 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23637; 8 May 96 15:48 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa13570; 8 May 96 15:48 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA102814214; Wed, 8 May 1996 12:36:54 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA014944207; Wed, 8 May 1996 13:36:47 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA09642; Wed, 8 May 96 13:26:23 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <3190F7D2@hpb15650.boi.hp.com>; Wed, 08 May 96 13:36:50 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: complete list of prtChannelType enums Date: Wed, 08 May 96 14:36:00 M Message-Id: <3190F7D2@hpb15650.boi.hp.com> Encoding: 83 TEXT X-Mailer: Microsoft Mail V3.0 The following list should be the COMPLETE list of prtChannelType enums, with their descriptions.. (Although, I don't know what this really means, since we deprecated the prtChannelType at the last meeting, and replaced it with assocApplicationProtocol.) PrtChannelType == "This enumeration indicates the type of channel that is receiving jobs. This is a type 2 enum." SYNTAX INTEGER { other(1), chSerialPort(3), chParallelPort(4), chIEEE1284Port(5), chSCSIPort(6), chAppleTalkPAP(7), -- AppleTalk Printer Access Protocol chLPDServer(8), -- RFC 1179 chNetwareRPrinter(9), -- Netware Remote Printer Protocol chNetwarePServer(10), -- Netware Print Server Protocol chPort9100(11), -- Network printer data stream chAppSocket(12), -- a bi-directional, LPD-like protocol -- using TCP Port 9100 for control and -- using TCP Port 9101 for control and -- TCP Port 9100 for data. -- Adobe Systems, Inc. chFTP(13), -- FTP "PUT" to printer - RFC 959 chTFTP(14), -- RFC 1350 chDLCLLCPort(15), chIBM3270(16), -- IBM Coax Data Stream chIBM5250(17), -- IBM Twinax Data Stream chFax(18), chIEEE1394(19), chTransport1(20), -- TCP Port 35 chCPAP(21), -- Common Printer Access Protocol -- using port 170; -- Digital Equipment Corp. chDCERemoteProcCall(22), -- OSF chONCRemoteProcCall(23), -- Sun Microsystems chOLE(24), -- Microsoft chNamedPipe(25), chPCPrint(26), -- Banyan chServerMessageBlock(27), -- File/Print sharing protocol used by -- various network operating systems -- from IBM 3Com, Microsoft and others chPSM(28), -- Printing Systems Manager, IBM chDLLAPI(29), -- Microsoft chVxDAPI(30), -- Microsoft chSystemObjectManager(31), -- IBM chDECLAT(32), -- Local Area Transport Protocol -- Digital Equipment Corp. chNPAP(33), -- Network Printer Alliance Protocol -- (NPAP) -- predecessor to IEEE Std. 1284.1 -- (TIPSI) chUSB(34) -- Universal Serial Bus chIrDA(35) -- Infrared Data Association -- IrDA Serial Infrared (SIR) Physical -- Layer Link Specification (IrPHY) -- IrDA Serial Infrared Link Access -- Protocol (IrLAP) http://irda.org/ chPrintxchange(36) -- Printxchange print job delivery channel -- ISO/IEC 10175 (DPA) level 2m conforming -- Printxchange Coalition. -- Current members: -- Digital Equipment Corp. -- Sun Microsystems, Inc. -- Xerox Corporation chPortTCP(37) -- a unidirectional "raw" TCP channel -- that uses an administratively assigned -- port address. chBidirPortTCP(38) -- A bidirectional "raw" TCP channel that -- an administratively assigned port -- address. chUNPP(39) -- Universal Network Printing Protocol(UNPP) -- A bi-directional, multiple port, network -- printing application protocol available -- on a wide variety of standard transport -- protocols. Underscore, Inc. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28037; 8 May 96 19:09 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa28033; 8 May 96 19:09 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa20138; 8 May 96 19:09 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA024555738; Wed, 8 May 1996 15:49:03 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA092925734; Wed, 8 May 1996 16:48:55 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA19234; Wed, 8 May 96 16:38:36 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <319124DF@hpb15650.boi.hp.com>; Wed, 08 May 96 16:49:03 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: Ping Request Date: Wed, 08 May 96 17:48:00 M Message-Id: <319124DF@hpb15650.boi.hp.com> Encoding: 57 TEXT X-Mailer: Microsoft Mail V3.0 Please send your responses to IEEE (p1284_3@lexmark.com) mailing list, as well as the PMI (pmi@hpbs987.boi.hp.com) mailing list.. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Wednesday, May 08, 1996 5:17 PM To: Multiple recipients of list Subject: Ping Request Please ping me if you are attending the May meetings in Chicago. Which meetings: Check in and out dates: Thanks Larry Meeting Notice IEEE P1284.3 IEEE P1284.4 PWG The May meetings will be held as follows: IEEE P1284.3 Tuesday, May 21 IEEE P1284.4 Monday, May 20 to Tuesday, May 21 Printer Working Group Wednesday - Thursday, May 22-23 All meeting will start at 8:30AM, breakfast will be available starting at 8:00AM. Sheraton North Shore Hotel Northbrook (Chicago), Illinois 933 Skokie Blvd. Ph. (708) 498-6500 Fax (708) 498-9558 The room rate is $99.00 single, $109.00 double. The meeting charge is $(still TBD) per person, per meeting day. The charge includes all meeting room expenses, breakfast, AV charges and break charges. Sorry for the short notice. You MUST make your reservations by Friday, May 10, and be sure to tell them you are with the FarPoint group. -- ******************************************************************* Larry A. Stein FarPoint Communications, Lancaster, CA http://www.fapo.com Ph. 805/726-4420 Fax 805/726-4438 *******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28300; 8 May 96 19:34 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa28296; 8 May 96 19:34 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa20424; 8 May 96 19:34 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA116957231; Wed, 8 May 1996 16:13:52 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA158947229; Wed, 8 May 1996 17:13:49 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA20662; Wed, 8 May 96 17:03:30 -0600 Received: from uscore.underscore.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA281677212; Wed, 8 May 1996 16:13:32 -0700 Received: by uscore.underscore.com (Smail3.1.28.1 #5) id m0uHILd-000US3C; Wed, 8 May 96 19:08 EDT Message-Id: Date: Wed, 8 May 96 19:08 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: JK Martin To: pmi@hpbs987.boi.hp.com, p1284_3@lexmark.com Subject: RSVP for May Meetings in Chicago I shall be attending the PWG meetings only, and I'll be staying the hotel. ...jay   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28737; 8 May 96 20:15 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa28733; 8 May 96 20:15 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa20876; 8 May 96 20:15 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA290830226; Wed, 8 May 1996 17:03:47 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA264990224; Wed, 8 May 1996 18:03:44 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA22819; Wed, 8 May 96 17:53:24 -0600 Received: from VNET.IBM.COM by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA260280215; Wed, 8 May 1996 17:03:35 -0700 Message-Id: <199605090003.AA260280215@relay.hp.com> Received: from BLDVMB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 8764; Wed, 08 May 96 19:59:27 EDT Date: Wed, 8 May 96 17:59:51 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Harry Lewis " To: p1284_3@lexmark.com, pmi@hpbs987.boi.hp.com, kishor@mirage.nsc.com Subject: Attendance "Replys" Response to the reflector allows regularly attending members to know who they can expect to be present at the meeting. >From: Kishor Padmanabhan >To: Multiple recipients of list >Subject: Re: RSVP for May Meetings in Chicago > >Doesn't People know how to reply to the originator instead > of replying to the reflector. > >JK Martin wrote: >> >> I shall be attending the PWG meetings only, and I'll be staying the hotel. >> >> ...jay   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29278; 8 May 96 21:09 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa29274; 8 May 96 21:09 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa21401; 8 May 96 21:09 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA139483499; Wed, 8 May 1996 17:58:20 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA095673496; Wed, 8 May 1996 18:58:16 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA22882; Wed, 8 May 96 18:47:58 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA059613490; Wed, 8 May 1996 17:58:10 -0700 Received: from cobra.cp10.es.xerox.com ([13.240.120.35]) by alpha.xerox.com with SMTP id <14456(4)>; Wed, 8 May 1996 17:55:37 PDT Received: from fredferd.cp10.es.xerox.com by cobra.cp10.es.xerox.com (4.1/SMI-4.1) id AA07640; Wed, 8 May 96 17:55:33 PDT Message-Id: <9605090055.AA07640@cobra.cp10.es.xerox.com> X-Sender: stanmcc@cobra X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 May 1996 09:53:08 PDT To: pmi@hpbs987.boi.hp.com, dpa@woden.eng.sun.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Stan McConnell Subject: DPA (ISO/IEC 10175) Final Text sent to ISO Cc: stanmcc@cp10.es.xerox.com A revised version of the Final Text of ISO/IEC 10175 Document Printing Application (DPA), parts 1 and 2, is available in the anonymous ftp server used by the IETF Printer MIB committee: ftp-out.external.hp.com in subdirectory: /snmpmib/dpa/mar96 As indicated below, this is primarily an editorial upgrade to the proposed Final Text version of May '95, and is now in the hands of the ISO Central Secretariat, being prepared for publication. Experience tells me that the Secretariat may request additional editorial revisions, but I do not expect any substantive changes before the Standard is published. Meanwhile, I will be working on proposed addenda and corrigenda to contribute to the ISO working group (SC18/WG4); Annex H indicates some of the things under consideration. Suggested additions/corrections to DPA-1/2 will be gratefully accepted. In addition, ballot comments on the DPA part 3 Committee Draft (CD) will be considered at the next SC18/WG4 meeting, and revision to DPA-3 will begin at that time. The DPA-3 CD can be found in subdirectory: /snmpmib/dpa/dpa-part3 The readme for the new /mar96 version follows: --------------------------------------------- READ-ZIP.TXT -- ISO/IEC 10175 (DPA) 2 APRIL 1996 The files in this directory represent the final state of ISO/IEC 10175 (DPA) parts 1 and 2, as delivered to the ISO Central Secretariat for publication as an International Standard. This version of the Standard differs from the May 1995 version primarily in editorial details. A few substantive changes are noted in the change histories at the beginning of Annexes A and C; also, Figure 9-1 has been revised slightly. The documents are available in four zip files that contain various representations of the Final Text. The four zip files are: dpa-doc.zip - the MS-WORD sources for this version of the Final Text dpa-docr.zip - the MS-WORD sources with revision marks showing the changes made to the proposed Final Text version of May '95 to make this (really, truly, hopefully) Final Text version dpa-ps.zip - the PostScript(tm) (with revision marks removed) in two long files for Part 1 and a second file for Part 2 dpa-asn.zip - the ASN.1 sources for the DPA protocol Each zip file contains a more detailed readme file: read-doc.txt, read-docr.txt, read-ps.txt, and read-asn.txt, respectively; these explain the contents of the zip files in more detail. Any questions or comments should be forwarded to the mail distribution list: dpa@woden.eng.sun.com and members of the committee will respond. Stan McConnell ISO/IEC 10175 Project Editor stanmcc@cp10.es.xerox.com ----------------------------------- PS: If anyone still needs the older version, I have moved those files into a subdirectory named /snmpmib/dpa/may95, where they will remain for a while.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29556; 8 May 96 21:39 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa29552; 8 May 96 21:39 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa21699; 8 May 96 21:39 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA218795652; Wed, 8 May 1996 18:34:13 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA181945648; Wed, 8 May 1996 19:34:08 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA22909; Wed, 8 May 96 19:23:49 -0600 Received: from avalon.dpc.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA084185641; Wed, 8 May 1996 18:34:01 -0700 Received: (from smap@localhost) by avalon.dpc.com (8.6.11/8.6.9) id SAA12380 for ; Wed, 8 May 1996 18:07:39 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: rbergma%miami.dnet.dpc.com@gate.dpc.com Received: from gate(10.30.0.166) by avalon via smap (V1.3) id sma012378; Wed May 8 18:07:17 1996 Received: by gate.dpc.com (5.65/DEC-Ultrix/4.3) id AA15855; Wed, 8 May 1996 18:07:08 -0700 Date: Wed, 8 May 1996 18:07:07 -0700 Message-Id: <9605090107.AA15855@gate.dpc.com> To: "GATE pmi@hpbs987.boi.hp.com"@avalon.dpc.com Subject: RE: Ping Request I will be attending the PWG meetings on May 22 and 23. I will arrive at the hotel on May 21 and will leave May 23. Ron Bergman   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06021; 9 May 96 0:18 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06017; 9 May 96 0:18 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa01082; 9 May 96 0:18 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA164735320; Wed, 8 May 1996 21:15:20 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA195535317; Wed, 8 May 1996 22:15:17 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA23109; Wed, 8 May 96 22:04:58 -0600 Received: from VNET.IBM.COM by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA138175310; Wed, 8 May 1996 21:15:10 -0700 Message-Id: <199605090415.AA138175310@relay.hp.com> Received: from BLDVMB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 1245; Thu, 09 May 96 00:11:02 EDT Date: Wed, 8 May 96 22:11:26 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Harry Lewis " To: p1284_3@lexmark.com, pmi@hpbs987.boi.hp.com Subject: Chicago I'll be at the PWG meetings (Wednesday and Thursday).   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13872; 9 May 96 9:33 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13868; 9 May 96 9:33 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa07387; 9 May 96 9:33 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA214828597; Thu, 9 May 1996 06:29:57 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA092198594; Thu, 9 May 1996 07:29:54 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA23409; Thu, 9 May 96 07:19:35 -0600 Received: from novell.com (prv-ums.Provo.Novell.COM) by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA138888476; Thu, 9 May 1996 06:27:56 -0700 Received: from INET-PRV-Message_Server by fromGW with Novell_GroupWise; Thu, 09 May 1996 07:24:23 -0600 Content-Length: 2211 Content-Type: text/plain Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Thu, 09 May 1996 07:23:03 -0600 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jay Cummings To: pmi@hpbs987.boi.hp.com Cc: p1284_3@lexmark.com Subject: FW: Ping Request -Reply I will be attending the PWG meetings on May 22 and 23. I will arrive at the hotel on May 21 and will leave May 23. /* - - -S-I-G-N-A-T-U-R-E- -B-L-O-C-K- - - Jay R. Cummings Services Manageability Development Team Development Manager Novell, Inc. -- where #Everything#s Connected# Prv-D-12-1 122 East 1700 South Provo, Utah 84606 Phone: 1-800-453-1267 x.3895 (801) 861-3895 Fax: (801) 861-7520 INTERNET: jay_cummings@novell.com - - -S-I-G-N-A-T-U-R-E- -B-L-O-C-K- - - */ >>> Binnur Al-Kazily 05/07/96 11:48pm >>> Please send your responses to IEEE (p1284_3@lexmark.com) mailing list, as well as the PMI (pmi@hpbs987.boi.hp.com) mailing list.. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Wednesday, May 08, 1996 5:17 PM To: Multiple recipients of list Subject: Ping Request Please ping me if you are attending the May meetings in Chicago. Which meetings: Check in and out dates: Thanks Larry Meeting Notice IEEE P1284.3 IEEE P1284.4 PWG The May meetings will be held as follows: IEEE P1284.3 Tuesday, May 21 IEEE P1284.4 Monday, May 20 to Tuesday, May 21 Printer Working Group Wednesday - Thursday, May 22-23 All meeting will start at 8:30AM, breakfast will be available starting at 8:00AM. Sheraton North Shore Hotel Northbrook (Chicago), Illinois 933 Skokie Blvd. Ph. (708) 498-6500 Fax (708) 498-9558 The room rate is $99.00 single, $109.00 double. The meeting charge is $(still TBD) per person, per meeting day. The charge includes all meeting room expenses, breakfast, AV charges and break charges. Sorry for the short notice. You MUST make your reservations by Friday, May 10, and be sure to tell them you are with the FarPoint group. -- ******************************************************************* Larry A. Stein FarPoint Communications, Lancaster, CA http://www.fapo.com Ph. 805/726-4420 Fax 805/726-4438 *******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16191; 9 May 96 11:05 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16186; 9 May 96 11:05 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa08990; 9 May 96 11:05 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA198303662; Thu, 9 May 1996 07:54:23 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA283283660; Thu, 9 May 1996 08:54:20 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA25631; Thu, 9 May 96 08:44:01 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31920724@hpb15650.boi.hp.com>; Thu, 09 May 96 08:54:28 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Cc: 'Don Wright' , 'Larry Stein' Subject: not able to attend Date: Thu, 09 May 96 09:48:00 M Message-Id: <31920724@hpb15650.boi.hp.com> Encoding: 15 TEXT X-Mailer: Microsoft Mail V3.0 I am not able to attend the May PWG meeting due to personal obligations.. However, as I have indicated before, I expect the draft Printer MIB review to be done by 1st week of June. I would to finalize the Printer MIB document, as well as the interoperability testing strategy in June meeting. If there are any items that needs to be added to the agenda for the May PWG PMP meeting, let me know.. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18404; 9 May 96 12:23 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18400; 9 May 96 12:23 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa10600; 9 May 96 12:23 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA241988387; Thu, 9 May 1996 09:13:08 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA196678384; Thu, 9 May 1996 10:13:04 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA00013; Thu, 9 May 96 10:02:40 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA281718358; Thu, 9 May 1996 09:12:38 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <14882(3)>; Thu, 9 May 1996 09:09:51 PDT Received: from cmqlite-6.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA05295; Thu, 9 May 96 09:09:47 PDT Message-Id: <9605091609.AA05295@diana.cp10.es.xerox.com> X-Sender: hastings@diana X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 9 May 1996 09:07:33 PDT To: pmi@hpbs987.boi.hp.com, p1284_3@lexmark.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: May Meeting - I'll be there for PWG May 22-23 I'll be arriving May 21 evening, checking out May 23. Thanks, Tom Hastings   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24769; 9 May 96 17:30 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa24765; 9 May 96 17:30 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa15834; 9 May 96 17:30 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA129446665; Thu, 9 May 1996 14:17:46 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA255916661; Thu, 9 May 1996 15:17:41 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA15543; Thu, 9 May 96 15:07:08 -0600 Received: from mail13.digital.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA257546639; Thu, 9 May 1996 14:17:19 -0700 Received: from us2rmc.zko.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id RAA29369; Thu, 9 May 1996 17:07:46 -0400 (EDT) Received: from hannah.enet by us2rmc.zko.dec.com (5.65/rmc-22feb94) id AA04859; Thu, 9 May 96 17:03:07 -0400 Message-Id: <9605092103.AA04859@us2rmc.zko.dec.com> Received: from hannah.enet; by us2rmc.enet; Thu, 9 May 96 17:03:41 EDT Date: Thu, 9 May 96 17:03:41 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Rick, DECprint engineer without portfolio, DTN 297-8350 (1-508-467-) MRO1-2/K20 09-May-1996 1708 -0400" To: mail11: ;, "@dis$:pmi" MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US Cc: landau@hannah.enet.dec.com Apparently-To: pmi@hpbs987.boi.hp.com Subject: RE: Ping request Yes, I expect to attend the PWG meetings in Chicago, arriving Tuesday, leaving Thurs PM or Friday, not sure yet. rick -------------- Richard Landau landau@hannah.enet.dec.com --- --- --- --- --- --- --- Hardcopy Engrg (Not to worry: | | | | | | | | Digital Equipment Corp. rarely pays much | d | i | g | i | t | a | l | Marlboro, MA attention to my opinions. | | | | | | | | Why should you?) --- --- --- --- --- --- ---   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27112; 9 May 96 19:54 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27108; 9 May 96 19:54 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa17631; 9 May 96 19:54 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA105065420; Thu, 9 May 1996 16:43:41 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA132905418; Thu, 9 May 1996 17:43:38 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA23176; Thu, 9 May 96 17:33:19 -0600 Received: from mailhub.cts.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA100895412; Thu, 9 May 1996 16:43:32 -0700 Received: from raylutz.cts.com(really [198.68.170.124]) by mailhub.cts.com via smail with smtp id for ; Thu, 9 May 96 16:40:04 -0700 (PDT) (Smail-3.1.92 1996-Mar-19 #3 built 1996-Apr-21) Message-Id: Date: Thu, 9 May 96 16:40:04 -0700 (PDT) X-Sender: raylutz@crash.cts.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: pmi Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Raymond Lutz Subject: Cannot attend but have paper. Dear PWG: I cannot attend your meeting since I will be in Tokyo that week. However, I have a proposal for RFC-1759 to align it with the MIME registration process and I would appreciate your discussion of this item. This is a continuation of the prtInterpreterLangFamily/Version issue. I will post this item by tommorrow. -Raymond /*********************************************************************** ** Raymond Lutz Voice: 619-447-3246 ** Director R & D, Cognisys, Inc. Fax: 619-447-6872 ** MFPA EC Chair BBS: 619-447-2223 ** 1010 Old Chase Ave., Suite B EMail: raylutz@cognisys.com ** El Cajon (San Diego Co.), CA 92020 USA MFPA: 1-800-603-MFPA ** WWW: http://www.cognisys.com http://www.mfpa.org ***********************************************************************/   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07040; 10 May 96 1:41 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07036; 10 May 96 1:41 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa02428; 10 May 96 1:41 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA169496703; Thu, 9 May 1996 22:38:24 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA124876701; Thu, 9 May 1996 23:38:21 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA24293; Thu, 9 May 96 23:28:02 -0600 Received: from mailhub.cts.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA042666695; Thu, 9 May 1996 22:38:15 -0700 Received: from raylutz.cts.com(really [198.68.170.124]) by mailhub.cts.com via smail with smtp id for ; Thu, 9 May 96 22:35:20 -0700 (PDT) (Smail-3.1.92 1996-Mar-19 #3 built 1996-Apr-21) Message-Id: Date: Thu, 9 May 96 22:35:20 -0700 (PDT) X-Sender: raylutz@crash.cts.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: pmi Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Raymond Lutz Subject: Technical Contribution: ...LangFamily/Version clarification Cc: MFPA@mfpa.org Dear PWG: I have completed a contribution outlining the changes to RFC-1759 and the IANA registry procedures to accommodate the requirements of MFPA. This proposal does not really change the MIB structure at all, but does clarify the formats accepted by given interpreters. I went out on a limb to define a bunch of MIME types that don't exist yet, but I think the means to define these is at hand and simple. I tried to upload these to the HP ftp server, but I couldn't remember the special tricks involved. So, instead, I loaded them to the MFPA ftp server. If you can tell me how to do it, I can load them, or you are welcome to make copies on the PWG server. MFPA wants to keep copies of these anyway. This submission to your group will be reviewed also by the TR29 committee next week. Sorry, I can't be at your meeting as I am scheduled to be in Tokyo. You can access these as: ftp://ftp.cts.com/pub/MFPA/pwglang.doc (winword 6.0) ftp://ftp.cts.com/pub/MFPA/pwglang.eps (Postscript) You should review this with revisions marking displayed and/or printed for best results. The PS version has revision marks printed. I haven't done it yet, but I was thinking of submitting this directly to the MIME list. Maybe after it is approved (yes!) then it would be the right time. I'm sure that the MIME enhancements authors may have some comment as well, and some of the types that I pulled from the MIME registry may in fact not match those in the MIB. Respectfully submitted, -Raymond Lutz /*********************************************************************** ** Raymond Lutz Voice: 619-447-3246 ** Director R & D, Cognisys, Inc. Fax: 619-447-6872 ** MFPA EC Chair BBS: 619-447-2223 ** 1010 Old Chase Ave., Suite B EMail: raylutz@cognisys.com ** El Cajon (San Diego Co.), CA 92020 USA MFPA: 1-800-603-MFPA ** WWW: http://www.cognisys.com http://www.mfpa.org ***********************************************************************/   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17155; 11 May 96 11:56 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17151; 11 May 96 11:56 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa07820; 11 May 96 11:56 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA137259703; Sat, 11 May 1996 08:48:23 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA040359698; Sat, 11 May 1996 09:48:19 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA14514; Sat, 11 May 96 09:37:55 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <3194B6C9@hpb15650.boi.hp.com>; Sat, 11 May 96 09:48:25 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: Important Notice about Meeting Charge, Ping and Stuff Date: Sat, 11 May 96 10:51:00 M Message-Id: <3194B6C9@hpb15650.boi.hp.com> Encoding: 37 TEXT X-Mailer: Microsoft Mail V3.0 FYI --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Friday, May 10, 1996 7:04 PM To: Multiple recipients of list Subject: Important Notice about Meeting Charge, Ping and Stuff The May meeting will be at the Sheraton. They cannot do the meeting charge as a room charge. I will have to pay for the charges. Please bring a check (personal or company) payable to FarPoint Communications. I will let you know next week how much the charge per day is. Regarding the charges: We pay a sliding rate based upon the sleeping room pickup. The fewer the number of people staying at the hotel, the more we pay for the room. This can vary from no charge to $800 per day. If you have not made you reservations please do so immediately. Also if you have not RSVPed to me you must do so that I can setup the catering (if any this time). Thanks, Larry -- ******************************************************************* Larry A. Stein FarPoint Communications, Lancaster, CA http://www.fapo.com Ph. 805/726-4420 Fax 805/726-4438 *******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08660; 13 May 96 7:03 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08656; 13 May 96 7:03 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa05049; 13 May 96 7:03 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA028835188; Mon, 13 May 1996 03:59:49 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA146415184; Mon, 13 May 1996 04:59:44 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA15650; Mon, 13 May 96 04:49:17 -0600 Received: from dub-img-7.compuserve.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA144695126; Mon, 13 May 1996 03:58:47 -0700 Received: by dub-img-7.compuserve.com (8.6.10/5.950515) id GAA13907; Mon, 13 May 1996 06:55:23 -0400 Date: 13 May 96 06:52:35 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Atsushi Yuki <76247.31@compuserve.com> To: IEEE1284 , PWG Subject: PWG/IEEE meeting Message-Id: <960513105234_76247.31_FHU32-8@CompuServe.COM> I'll be attending both meeting (4 days) Atsushi Yuki Kyocera Corp. Shige Kanemitsu Kyocera Corp. may be attending the meeting also.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20039; 13 May 96 15:47 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20034; 13 May 96 15:47 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa12679; 13 May 96 15:47 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA143976377; Mon, 13 May 1996 12:39:37 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA225826374; Mon, 13 May 1996 13:39:34 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA24352; Mon, 13 May 96 13:29:09 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31978FFD@hpb15650.boi.hp.com>; Mon, 13 May 96 13:39:41 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: May Meeting Charges Date: Mon, 13 May 96 14:40:00 M Message-Id: <31978FFD@hpb15650.boi.hp.com> Encoding: 39 TEXT X-Mailer: Microsoft Mail V3.0 FYI. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Monday, May 13, 1996 12:34 PM To: Multiple recipients of list Subject: May Meeting Charges The meeting charges for the May meeting will be $38.00 per day. This will include: -Meeting room rental -Overhead & Screen Rental -Flipchart -Continential breakfast (varies daily) -Afternoon break Please bring a check(payable to FarPoint) or cash to the meeting. 1 day $38.00 2 days $76.00 3 days $114.00 4 days $152.00 I will bring receipts this time. Thank you, Larry -- ******************************************************************* Larry A. Stein FarPoint Communications, Lancaster, CA http://www.fapo.com Ph. 805/726-4420 Fax 805/726-4438 *******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20754; 13 May 96 16:14 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20750; 13 May 96 16:14 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa13121; 13 May 96 16:14 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA260997841; Mon, 13 May 1996 13:04:01 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA262197833; Mon, 13 May 1996 14:03:53 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA24431; Mon, 13 May 96 13:53:26 -0600 Received: from nls.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA008617819; Mon, 13 May 1996 13:03:39 -0700 Received: by nls.com (MX V4.1 VAX) id 1; Mon, 13 May 1996 12:29:08 PST Date: Mon, 13 May 1996 12:29:06 PST Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: David Kellerman To: p1284_3@lexmark.com, pmi@hpbs987.boi.hp.com Cc: davek@nls.com Message-Id: <009A2450.3DD7BC79.1@nls.com> Subject: PWG/IEEE meeting I will be attending the PWG meeting on May 22-23. :: David Kellerman Northlake Software 503-228-3383 :: kellerman@nls.com Portland, Oregon fax 503-228-5662   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27807; 13 May 96 22:17 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27803; 13 May 96 22:17 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa18302; 13 May 96 22:17 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA038039351; Mon, 13 May 1996 19:02:32 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA133979348; Mon, 13 May 1996 20:02:29 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA25177; Mon, 13 May 96 19:52:07 -0600 Received: from avalon.dpc.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA001049341; Mon, 13 May 1996 19:02:21 -0700 Received: (from smap@localhost) by avalon.dpc.com (8.6.11/8.6.9) id SAA19548 for ; Mon, 13 May 1996 18:35:59 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: rbergma%miami.dnet.dpc.com@gate.dpc.com Received: from gate(10.30.0.166) by avalon via smap (V1.3) id sma019517; Mon May 13 18:35:55 1996 Received: by gate.dpc.com (5.65/DEC-Ultrix/4.3) id AA28413; Mon, 13 May 1996 18:36:12 -0700 Date: Mon, 13 May 1996 18:36:12 -0700 Message-Id: <9605140136.AA28413@gate.dpc.com> To: "GATE pmi@hpbs987.boi.hp.com"@avalon.dpc.com Subject: Review of Intrepreter Group After a review of the Interpreter Group, I have the following comments and suggestions: 1. In PrtInterpreterLangFamily, 'langPSPrinter(42)' follows 'langPS(6)'. All other entries appear to be in numeric order. Is there a specific reason for this to be out of order? (page #30) 2. I suggest the following comments be added in PrtInterpreterLangFamily (pages #30 - 32)... langEscapeP(9), --Epson Corp. langInterpress(12), --Xerox Corp. langTEK4014(19), --Tektronix Inc. langIGP(21), --Printronix Inc. 3. The comment for 'langNPAP(31)' currently reads (page #32): --Network Printer Alliance Protocol --IEEE 1284.1. This protocol has been superseded --by the IEEE 1284.1 TIPSI standard. --(ref. LangTIPSI(49)) change to: --Network Printer Alliance Protocol. --This protocol has been superseded --by the IEEE 1284.1 TIPSI standard. --(ref. LangTIPSI(49)) 4. Both prtInterpreterFeedAddressibility (page #93) and prtInterpreterXFeedAddressibility (page #94) reference 'prtMarkerAddressibilityUnit'. The plurality is expressed by 'prtMarkerAddressibilityUnit s'. Inclusion of the 'space' is confusing. 5. The textual convention PrtInterpreterTwoWayTC (page #36) could be more generic. One of the reasons for creating the textual conventions was to allow their use in other MIBs. For this particular TC, the enums listed need not be restricted to the referenced MIB object. By naming this TC something like 'YesNoTC', it would be easier to justify its use with other MIB objects. Also, the description should then be modified or eliminated. 6. The textual convention PrtInterpreterDefaultOrientationTC (page #36) should be renamed PrintOrientationTC to allow it to be used with other MIB objects. The description should also be modified. 7. All the newly created textual conventions need to be reviewed to insure that the name is not overly restrictive. 8. Some of the textual conventions are categorized according to the associated MIB object group. The TCs recently created are included in somewhat of a random order. I suggest that all TCs be presented in categories referencing their associated MIB object group. Ron Bergman Dataproducts Corp rbergma@dpc.com   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18515; 14 May 96 11:20 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18511; 14 May 96 11:20 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa09315; 14 May 96 11:20 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA220836899; Tue, 14 May 1996 08:15:00 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA080676895; Tue, 14 May 1996 09:14:55 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA26242; Tue, 14 May 96 09:04:29 -0600 Received: from VNET.IBM.COM by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA150836872; Tue, 14 May 1996 08:14:32 -0700 Message-Id: <199605141514.AA150836872@relay.hp.com> Received: from BLDVMB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 7988; Tue, 14 May 96 11:09:54 EDT Date: Tue, 14 May 96 09:09:36 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Harry Lewis " To: lstein@fapo.com, pmi@hpbs987.boi.hp.com Subject: Meeting Schedule I 2nd Ron's request to leave the meetings as currently scheduled. >Larry, > >I would like to cast my vote not to change the July meeting from >Seattle to San Diego. > >(Having just changed my vacation tickets to return to LA via Seattle, at >a fee, I will be in Seattle on July 25-26 regardless of the meeting >location.) > >Let's keep the July and August meetings as originally scheduled! > > Ron Bergman > Dataproducts Corp > rbergma@dpc.com   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19318; 14 May 96 11:47 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19314; 14 May 96 11:47 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa09729; 14 May 96 11:47 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA296817882; Tue, 14 May 1996 08:31:22 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA097297878; Tue, 14 May 1996 09:31:18 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA26691; Tue, 14 May 96 09:20:58 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <3198A753@hpb15650.boi.hp.com>; Tue, 14 May 96 09:31:31 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: Meeting dates.... Date: Tue, 14 May 96 10:32:00 M Message-Id: <3198A753@hpb15650.boi.hp.com> Encoding: 65 TEXT X-Mailer: Microsoft Mail V3.0 FYI --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Monday, May 13, 1996 5:57 PM To: Multiple recipients of list Subject: Re: Meeting dates.... Randy Turner wrote: > > Larry, > > Could you reply (possibly to the reflector or me) about the meeting dates > for the next few months that we have agreed upon? (locations and dates) > > Randy Randy, Here are the meeting dates for the remainder of the year. (These are subject to change if necessary) June Meetings- Montreal Hilton June 26 .4 June 27 .3 June 27-28 PWG July Meetings- (I would like to swap the implementors forum to next month and meet in San Diego in July. We'll discuss at the May meeting) Seattle, Washington July 22 Implementors Forum July 23 .3 July 24 .4 July 25-26 PWG August Meetings- San Diego (see above) August 26 .3 August 27 .4 August 28-29 PWG September/October Meetings- New York City September 30 .3 October 1 .4 October 2-3 PWG November Meetings- New Orleans (Don't forget absentee ballots) November 4 .3 November 5 .4 November 6-7 PWG -- ******************************************************************* Larry A. Stein FarPoint Communications, Lancaster, CA http://www.fapo.com Ph. 805/726-4420 Fax 805/726-4438 *******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28928; 15 May 96 16:35 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa28924; 15 May 96 16:35 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa27548; 15 May 96 16:35 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA008061998; Wed, 15 May 1996 13:26:39 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA230021984; Wed, 15 May 1996 14:26:24 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA29636; Wed, 15 May 96 14:15:51 -0600 Received: from interlock.lexmark.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA069721909; Wed, 15 May 1996 13:25:09 -0700 Received: by interlock.lexmark.com id AA28909 (InterLock SMTP Gateway 3.0 for pmi@hpbs987.boi.hp.com); Wed, 15 May 1996 16:13:18 -0400 Message-Id: <199605152013.AA28909@interlock.lexmark.com> Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-2); Wed, 15 May 1996 16:13:18 -0400 Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-1); Wed, 15 May 1996 16:13:18 -0400 To: "pmi%hpbs987.boi.hp.com" Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Don Wright Date: 15 May 96 10:09:06 EDT Subject: langNPAP(31) Mime-Version: 1.0 Content-Type: Text/Plain Ron Bergman said: >3. The comment for 'langNPAP(31)' currently reads (page #32): > > --Network Printer Alliance Protocol > --IEEE 1284.1. This protocol has been superseded > --by the IEEE 1284.1 TIPSI standard. > --(ref. LangTIPSI(49)) > > change to: > > --Network Printer Alliance Protocol. > --This protocol has been superseded > --by the IEEE 1284.1 TIPSI standard. > --(ref. LangTIPSI(49)) Rather, I suggest the following: --Network Printer Alliance Protocol --This is version 1.0 of a protocol --that will become IEEE 1284.1 (TIPSI) standard --denoted as version 2.0 or higher. --(ref. LangTIPSI(49)) Don ************************************************************* * Don Wright Lexmark International * * Manager Strategic Alliances * * 740 New Circle Rd Phone: 606-232-4808 * * Lexington, KY 40511 Fax: 606-232-6740 * *************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00274; 15 May 96 17:09 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00269; 15 May 96 17:09 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa28442; 15 May 96 17:09 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA141533766; Wed, 15 May 1996 13:56:06 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA261573762; Wed, 15 May 1996 14:56:02 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA29723; Wed, 15 May 96 14:45:41 -0600 Received: from mailhub.cts.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA172183718; Wed, 15 May 1996 13:55:18 -0700 Received: from raylutz.cts.com(really [198.68.170.124]) by mailhub.cts.com via smail with smtp id for ; Wed, 15 May 96 13:53:50 -0700 (PDT) (Smail-3.1.92 1996-Mar-19 #3 built 1996-Apr-21) Message-Id: Date: Wed, 15 May 96 13:53:50 -0700 (PDT) X-Sender: raylutz@crash.cts.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: pmi Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Raymond Lutz Subject: Interesting info on PWG and IETF "Sanction" Cc: MFPA@mfpa.org Hi: I just returned from the TR29 meeting near Newark, NJ. I left slightly early so that I can prepare for my trip to Tokyo next week. I presented the MIME media-types as a possible standard way to handle the Contents-Type field of T.434 (BFT). As a result, I had a side conversation with Steven Pershau of National Communication Systems (some sort of government agency that is interesting in insuring that the critical U.S. communications always stays up). He says that ITU-T does not recognize IETF as any more than a "small-m" member, the same status that any company can have, such as HP, AT&T, Rockwell, etc. (Although this was offered to the IETF free of charge, others must pay a large fee). He says that ITU-T sends virtually all of their recommendations to the IETF, but never has the IETF contributed anything to the ITU. The problem he says with IETF getting more stature at least in these circles, is that IETF has no "leader" who is responsible for the results of the IETF. In the ITU, this person is Mr. Ermer. Other organizations always have a contact person who is ultimately responsible for the quality and coordination of organization activities. IETF has no such person. It sounds like IETF does want higher stature with these institutions, but since they are based on international treaties, they must have some strict agreements with "Large-M" members, such as ISO, ECMA, etc. to be in compliance with these treaties. Therefore, the small-m status. I really admire the good work and obvious results of the IETF. Maybe their approach is better for the fluid nature of the Internet and the future of communication standards. However, some serious organizational changes will have to happen in either IETF or ITU before IETF will be seen as a "legitimate" standards body. I just hope this doesn't get in the way of harmonizing ITU and IETF standards (proposals from myself and others have been seen which suggest that a new generation of facsimile should be based on internet standards -- not the other way around!) -Raymond /*********************************************************************** ** Raymond Lutz Voice: 619-447-3246 ** Director R & D, Cognisys, Inc. Fax: 619-447-6872 ** MFPA EC Chair BBS: 619-447-2223 ** 1010 Old Chase Ave., Suite B EMail: raylutz@cognisys.com ** El Cajon (San Diego Co.), CA 92020 USA MFPA: 1-800-603-MFPA ** WWW: http://www.cognisys.com http://www.mfpa.org ***********************************************************************/   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05096; 15 May 96 21:07 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05092; 15 May 96 21:07 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa04360; 15 May 96 21:07 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA131998542; Wed, 15 May 1996 18:02:23 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA246148539; Wed, 15 May 1996 19:02:19 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA00058; Wed, 15 May 96 18:51:58 -0600 Received: from avalon.dpc.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA090448528; Wed, 15 May 1996 18:02:09 -0700 Received: (from smap@localhost) by avalon.dpc.com (8.6.11/8.6.9) id RAA14112 for ; Wed, 15 May 1996 17:35:44 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: rbergma%miami.dnet.dpc.com@gate.dpc.com Received: from gate(10.30.0.166) by avalon via smap (V1.3) id sma014110; Wed May 15 17:35:35 1996 Received: by gate.dpc.com (5.65/DEC-Ultrix/4.3) id AA04590; Wed, 15 May 1996 17:36:09 -0700 Date: Wed, 15 May 1996 17:36:09 -0700 Message-Id: <9605160036.AA04590@gate.dpc.com> To: "GATE pmi@hpbs987.boi.hp.com"@avalon.dpc.com Subject: JMP Agenda for May 23rd Proposed Agenda for the Job Monitor Discussions: 1. Charter An updated Statement of Charter has been published via email per the discussions in Alexandria. This item will be assumed to be closed unless a concern is raised on email or in the meeting. 2. Job Submission Models Tom Hastings presented three scenarios in the last meeting. Does this cover all conditions? Does anyone wish to add or modify? 3. Terminology Tom Hastings is planning to submit an updated list of terms prior to the meeting. 4. Roles and Required Information Tom Hastings will be making an attempt at defining these. If it is available for the meeting ew can discuss. 5. Goals The following issues remain open. a. Should the project include a 'Job Ticket' or 'Job Submission Protocol'? Will the Job MIB be useful if these are not defined? b. What client software will support this MIB and what are the scenarios for use of the MIB by the software? c. Do OS/NOS vendors need to participate? d. Do we need to define platforms and protocols to be supported or are the proposed job submissions models sufficient? 6. Object Categories These categories should provide all the information that is required for the defined role models. A set of objects must be defined for each category. Do these categories cover all requirements? a. Job Identification b. Job Status c. Job Parameters d. Accounting Parameters 7. What objects are required in each category to provide the required information for each role model? Ron Bergman Dataproducts Corp rbergma@dpc.com   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26066; 17 May 96 16:55 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa26062; 17 May 96 16:55 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa16331; 17 May 96 16:55 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA120045787; Fri, 17 May 1996 13:43:08 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA250965781; Fri, 17 May 1996 14:43:01 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA16710; Fri, 17 May 96 14:32:07 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <319CE4C4@hpb15650.boi.hp.com>; Fri, 17 May 96 14:42:44 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Cc: 'Don Wright' , 'Larry Stein' Subject: May PWG meeting agenda Date: Fri, 17 May 96 15:43:00 M Message-Id: <319CE4C4@hpb15650.boi.hp.com> Encoding: 67 TEXT X-Mailer: Microsoft Mail V3.0 If you are planning on attending to the May PWG meeting, and your name is not in the list below, let me know ASAP. 1. Lee Farrell 2. Jay K. Martin 3. Randy Turner 4. Bill Wagner 5. Ron Bergman 6. Luis Cubero 7. Harry Lewis 8. Jay Cummings 9. Tom Hastings 10. Don Wright 11. Rick Landau 12. Atsushi Yuki 13. Shige Kanemitsu (possibly) 14. David Kellerman Don't forget to bring a check payable to FarPoint (or cash) for the meeting room charges: 1 day $38.00 2 days $76.00 3 days $114.00 4 days $152.00 Since I won't be able to attend the upcoming meeting, Don W. will be running the PMP (Thanks Don.) Below is the proposed agenda. Take a look at the contents, etc. The being/end times for each project is provided as a reference, and it follows from the decision that was made at the last meeting (1 day for JMP, 1/2 for SENSE, etc.). Have fun at the meeting, and hopefully the meeting will be more alive than the mailing list has been.. Wednesday 22nd: -------------- * PWG - 8:30 - 10:00am 1. Next meeting 2. Discussions on PWG and whether it needs to be a sanctioned organization, or be under an "umbrella" organization. 3. Possibility on moving the PWG ftp site & mailing list to another site (possibly UnderScore's?) * Printer MIB/MIF Project - 10:30am-12:00pm 1. Raymond Lutz's proposal on using the MIME registration types for prtInterpreterLangFamily. 2. Any issues/concerns with Channel group changes of using NSM (Network Services Monitoring MIB) to extend the functionality of the channel group. 3. Status of the draft Printer MIB document review. Any issues that needs to be addressed at this meeting? 4. Comments on proposed schedule of completing the document review by June 3rd, and finalizing the document by June meeting. Also, outlining the requirements for interoperability testing in June meeting. * SENSE Project - 1:30-5:00pm Thursday 23rd: ------------- * Job Monitoring Project: Thursday 8:30-5:00pm See the JMP Agenda published by Ron B. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26622; 17 May 96 17:08 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa26618; 17 May 96 17:08 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa16569; 17 May 96 17:08 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA219347027; Fri, 17 May 1996 14:03:47 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA274367024; Fri, 17 May 1996 15:03:44 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA16727; Fri, 17 May 96 14:53:19 -0600 Received: from interlock.lexmark.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA212427011; Fri, 17 May 1996 14:03:31 -0700 Received: by interlock.lexmark.com id AA18847 (InterLock SMTP Gateway 3.0 for pmi@hpbs987.boi.hp.com); Fri, 17 May 1996 16:54:42 -0400 Message-Id: <199605172054.AA18847@interlock.lexmark.com> Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-2); Fri, 17 May 1996 16:54:42 -0400 Received: by interlock.lexmark.com (Protected-side Proxy Mail Agent-1); Fri, 17 May 1996 16:54:42 -0400 To: "pmi%hpbs987.boi.hp.com" Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Don Wright Date: 17 May 96 17:04:23 EDT Subject: Marker Section Review Mime-Version: 1.0 Content-Type: Text/Plain Well I made it through the Marker section on the plane back from Paris. Here are all of my comments (including some which are simply typos.) All page numbers are those on the bottom of the page not the old ones from RFC1759. I also reviewed the intoductory material; those comments are included as well. 1) Page 5, Sentence should read "... three basic categories: descriptions, status and alerts." (change comma to colon after categories.) 2) Page 10, section 2.2.6, second paragraph, "xero-graphic" should be "xerographic." 3) Page 11, section 2.2.6, next to last sentence: insert "(e.g. fuser oil)" after "... such as a fuser supply" 4) Page 70, in the description of prtMarkerDefaultIndex: change "markersub-unit" to "marker sub-unit." 5) Page 72, in the description of prtMarkerLifeCount: insert "prtMarker" as a prefix to "CounterUnit" 6) Page 73, in the description of prtMarkerPowerOnCount: insert "prtMarker" as a prefix to "CounterUnit" 7) Page 73, in the description for both prtMarkerProcessColorants and prtMarkerSpotColorants, the end of the text "Must be 0 greater." is not a sentence. Suggestion: "The value of prtMarkerProcessColorants(prtMarkerSpotColorants) must be greater than 0." 8) Page 73, in the description of prtMarkerAddressabilityUnit add "as applied to the marker's resolution." to the end of the existing description. 9) Page 74, for both prtMarkerAddressabilityFeedDir and prtMarkerAddressabilityXFeedDir I think would should include and example of 300 or 600 dpi. 10) Pages 74/75, the description for south, west, and east margins should fully spell out the object prtMarkerNorthMargin where the text now says "(see NorthMargin)" 11) Page 76, in the description of prtMarkerSuppliesIndex, it is stated "...values are expected to remain stable across successive printer power cycles." This means that printer changes do not occur when the printer is turned off. I think this is the exact opposite of what is meant. It should state "...values are expected to remain stable from power-on until power-off." 12) Page 78, in the description of prtMarkerSuppliesSupplyUnit insert "of measure" after the first word of the text "Unit". 13) Page 78, in the description of prtMarkerSuppliesMaxCapacity change "SupplyUnit" to "prtMarkerSuppliesSupplyUnit" 14) In the same object, change "...this value, the value is sensed by the printer..." to "...this value, the value is reported by the printer..." 15) On page 78, in the description of prtMarkerSuppliesLevel, make the same text change as in #14 above. 16) On page 80, in the description of prtMarkerColorantIndex make the same change in the text as in #11 above. 17) On page 80, the size of prtMarkerColorantValue is given as "OCTET STRING (SIZE(0..63)). Is this string really big enough to hold a color using a worst case of the ISO9070 naming convention. I don't think so. What about changing it to 255? What fun, what fun! Don ************************************************************* * Don Wright Lexmark International * * Manager Strategic Alliances * * 740 New Circle Rd Phone: 606-232-4808 * * Lexington, KY 40511 Fax: 606-232-6740 * *************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11462; 19 May 96 13:36 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa11458; 19 May 96 13:36 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa08391; 19 May 96 13:36 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA079167042; Sun, 19 May 1996 10:30:43 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA022697038; Sun, 19 May 1996 11:30:38 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA18287; Sun, 19 May 96 11:20:11 -0600 Received: from VNET.IBM.COM by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA146737025; Sun, 19 May 1996 10:30:25 -0700 Message-Id: <199605191730.AA146737025@relay.hp.com> Received: from BLDVMB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 9081; Sun, 19 May 96 13:25:30 EDT Date: Sun, 19 May 96 11:18:39 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Harry Lewis " To: pmi@hpbs987.boi.hp.com Subject: Alerts review In reviewing the alerts section of the new draft, in the textual convention part (up front pp. 40-1) I have two comments. 1. markerFuserThermistorFailure(1004) I don't recall discussing this one. What happens when the thermistor fails? Does the fuser go in-operable? If so, can we just call this markerFuserFailure? I guess every fuser must have a thermistor, but this sounds a bit too specific. What if a fuser senses temp via some other technology? Am I being too picky? 2. markerTonerCartridgeEmpty(1115) This one should be added to the list. I know we gyrated a lot going from specific to generic, but my notes have this as one we kept. Any objections, disagreements?   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05867; 20 May 96 0:25 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05863; 20 May 96 0:25 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa01091; 20 May 96 0:25 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA282055973; Sun, 19 May 1996 21:19:33 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA044635970; Sun, 19 May 1996 22:19:31 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA18609; Sun, 19 May 96 22:09:08 -0600 Received: from mail13.digital.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA057475964; Sun, 19 May 1996 21:19:24 -0700 Received: from us2rmc.zko.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id AAA08214; Mon, 20 May 1996 00:14:00 -0400 (EDT) Received: from hannah.enet by us2rmc.zko.dec.com (5.65/rmc-22feb94) id AA07213; Mon, 20 May 96 00:09:53 -0400 Message-Id: <9605200409.AA07213@us2rmc.zko.dec.com> Received: from hannah.enet; by us2rmc.enet; Mon, 20 May 96 00:09:53 EDT Date: Mon, 20 May 96 00:09:53 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Rick, DECprint engineer without portfolio, DTN 297-8350 (1-508-467-) MRO1-2/K20 20-May-1996 0014 -0400" To: "pmi@hpbs987.boi.hp.com !sent to"@dis$, pmi@hannah.enet.dec.com MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US Apparently-To: pmi@hpbs987.boi.hp.com Subject: New SENSE docs on PWG ftp server I uploaded the current state of the SENSE Client API docs to the PWG ftp server (at HP). This is an early, partial release of the API spec. Some portions are somewhat fleshed out, some portions sketchy, and some are outline headings only. I apologize that this did not make the usual meeting-minus-five-days deadline. In the .../sense/... directory you will find sns9605.zip containing six HTML files with the current state of the docs. *.htm the six HTML files, unzipped, in vanilla ASCII. The HTML files should be readable, and printable, with any browser (that supports tables), e.g., Netscape > V1.1, MS Internet Explorer V2.0, and lots of others. Remember to use binary mode when ftp-ing the .zip file. Unzip the archive with any moderately recent version of Info-ZIP or PKZIP. Or copy the .htm files directly, in ASCII mode, if you have the bandwidth. Hope to see you in Chicago. rick   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01092; 20 May 96 21:43 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01088; 20 May 96 21:43 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa16372; 20 May 96 21:43 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA254941880; Mon, 20 May 1996 18:24:41 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA203730667; Mon, 20 May 1996 19:04:28 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA28718; Mon, 20 May 96 18:49:26 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA233060382; Mon, 20 May 1996 17:59:42 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <14764(8)>; Mon, 20 May 1996 17:57:02 PDT Received: from cmqlite-6.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA08503; Mon, 20 May 96 17:56:57 PDT Message-Id: <9605210056.AA08503@diana.cp10.es.xerox.com> X-Sender: hastings@diana X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 20 May 1996 17:54:40 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: Questions about the SMIv1 translation of RFC 1759 and read-only vs. not-accessible indices We have the following questions which we'd like to add to the agenda of the PWG this Wednesday: 1. Is the SMIv1 Printer MIB that is available from the PWG ftp site officially condoned by the PWG? ftp://ftp-out.external.hp.com/snmpmib/prtspec/smiv1/rfc1759.mib 2. Was there a conscience decision made to translate the "not-accessible" indices in the SMIv2 MIB to "read-only" indices in the SMIv1 MIB? 3. If the two SMI versions of the Printer MIB stand as they are, that would imply that the index objects are visible in the SMIv1 version and not in the SMIv2 version. This leads to the same object (same OID) having different behavior, depending on the SMI version. This is recommended against by David Reid of SNMP Research, Inc., as well as others. Has the PWG accepted this caveat? Thanks, Tom Hastings   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01439; 20 May 96 22:08 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01435; 20 May 96 22:08 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa16643; 20 May 96 22:08 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA285532984; Mon, 20 May 1996 18:43:05 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA225071766; Mon, 20 May 1996 19:22:46 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA28731; Mon, 20 May 96 19:07:49 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA245001485; Mon, 20 May 1996 18:18:05 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <14430(9)>; Mon, 20 May 1996 18:15:21 PDT Received: from cmqlite-6.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA08517; Mon, 20 May 96 18:15:17 PDT Message-Id: <9605210115.AA08517@diana.cp10.es.xerox.com> X-Sender: hastings@diana X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 20 May 1996 18:13:00 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: Draft Printer MIB prtAlertIndex should be accessible-for-notify The IETF has deprecated the 144x series MIBs, so that the Printer MIB should now be based on the new 190x series. In order to compile the draft Printer MIB, the prtAlertIndex has to be changed from not-accessible to accessible-for-notify in order to compile with RFC 190x. This is the only problem we know of. Shouldn't we change the draft? This is part of my review of the alerts group. Thanks, Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03228; 20 May 96 22:44 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03223; 20 May 96 22:44 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa16996; 20 May 96 22:44 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA040705308; Mon, 20 May 1996 19:22:18 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA014653895; Mon, 20 May 1996 19:58:15 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA28753; Mon, 20 May 96 19:43:12 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA267163608; Mon, 20 May 1996 18:53:28 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <17019(3)>; Mon, 20 May 1996 18:50:48 PDT Received: from cmqlite-6.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA08532; Mon, 20 May 96 18:50:44 PDT Message-Id: <9605210150.AA08532@diana.cp10.es.xerox.com> X-Sender: hastings@diana X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 20 May 1996 18:48:27 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: Question about prtInterpreterDefaultCharSetIn The current DESCRIPTION: The default coded character set for input octets encounrtered outside a context in which the Page Description Language established the interpretation of the octets. This value shall be (2) if there is not default. Question 1: What does this object really control? Does the value control the character set of the PDL data to be printed or the character set of the PDL command sequences? If a management station wrote this object, what would be the effect? Question 2: Should we change "the Page Description Language" to "this intepreter" in the DESCRIPTION? Maybe the PDL doesn't have a default, but the interpreter is configured so that it does. We'd like to discuss this at the PWG meeting. Thanks, Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00809; 20 May 96 23:21 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00805; 20 May 96 23:21 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa00368; 20 May 96 23:21 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA077567443; Mon, 20 May 1996 19:57:54 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA084486017; Mon, 20 May 1996 20:33:37 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA28772; Mon, 20 May 96 20:18:39 -0600 Received: from alpha.xerox.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA072655655; Mon, 20 May 1996 19:27:35 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <17084(8)>; Mon, 20 May 1996 19:24:54 PDT Received: from cmqlite-6.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA08553; Mon, 20 May 96 19:24:50 PDT Message-Id: <9605210224.AA08553@diana.cp10.es.xerox.com> X-Sender: hastings@diana X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 20 May 1996 19:22:33 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: 10 Questions on the Printer MIB from an implementor Here are some questions from one of our implementors who has carefully studied the Printer MIB. I need some help from the PWG in answering them. We probably need to clarify the MIB when we agree on the answers. Thanks, Tom (1) Regarding objects being defined as 'read-write' without MIN-ACCESS clause in any compliance statements, we must not return a Response-PDU whose error-status field is not set to 'noError'. Is this thought correct? According to 5.4.3.3 "Mapping of the MIN-ACCESS clause" of RFC1904 "Conformance Statements for SNMP2": The MIN-ACCESS clause, which need not be present, is used to define the minimal level of access for the object named in the correspondent OBJECT clause. If this clause is absent, the minimal level of access is the same as the maximal level specified in the correspondent invocation of the OBJECT-TYPE macro. ..... An implementation is compliant if the level of access it provides is greater or equal to the minimal level in the MODULE-COMPLIANCE macro and less or equal to the maximal level in the OBJECT-TYPE macro. Simply interpreted, I think it's correct. If so, most or some of our planned printers can not be compliant to RFC1759, because: - some printers can not support 'resetToNVRAM(5)' of 'prtGeneralReset', - most printers can not support 'disabled(4)' of 'prtConsoleDisable', - most printers can not support to write 'prt[Input|Output|MediaPath]DefaultIndex', and, - most printers can not support to write 'prtConsoleDisplayBufferText' Can we request PWG that these objects be defined to be at least read-only or optional? Otherwise, is our interpretation of conformance of MIB wrong? For example, is it compliant for RFC1759 just if the agent doesn't return 'noSuchName' error everytime set requested? (2) There are objects in RFC1759 whose MAX-ACCESS is 'read-write' which are allowed to be changed by management requests to set proper existence or properties of the resources of the printer which does not have sensors. These are: prtInputMediaDim[X|]FeedDirDeclared prt[Input|Output]MaxCapacity prtInputCurrentLevel prtOutputRemainingCapacity prtOutput[Max|Min]Dim[X|]FeedDir prtMarkerSuppliesMaxCapacity prtMarkerSuppliesLevel The DESCRIPTIONs for these objects say that if the value of the resource is sensed it may not be changed by management requests. In this case, what error should the agent return in the Response-PDU? 'generr' in SNMPV1 and 'wrongValue' in SNMPV2? Moreover, in this case, the Set request always result in error, but conformance requirement of RFC1759 defines these objects are of 'read-write'. Does't this situation cause any inconsistency in interpretation of conformance? (3) Regarding 'prtGeneralConfigChanges', what does mean 'config' here? I tried to extract possible config changes related objects in the MIB. I could extract: change of 'prtInputMediaDim[X]FeedDirChosen', change of 'prtInputMedia[Weight|Type|Color|FormParts]', increment and decrement of 'prt[Storage|Device]RefEntry', increment and decrement of 'prtInputEntry', increment and decrement of 'prtOutputEntry', increment and decrement of 'prtChannelEntry', increment and decrement of 'prtInterpreterEntry' and so on (every subunit entry). (Maybe 'prtInputMedia[Weight|Type|Color|FormParts]' is not printer configuration but media configuration.) Is this thought reasonable? Moreover, must the value of this counter keep across power cycle? If so, when some configuration changes occur during power off, must these changes be counted? (e.g. I think many printers can add/remove input trays only during power off time.) (4)We could not catch the clear meaning of 'prtMarkerColorantTonality'. For example in monochrome printer, if it supports one 'toner save mode' not performed by interpreters but marker itself then is its value '3', i.e. depending on capability of how the marker can mark a paticular 'dot' with the colorant? (5)Regarding 'prtMediaPathType'. How we can distinguish 'longEdgeBindingDuplex(3)' from 'shortEdgeBindingDuplex(4)' in a MediaPath? Doesn't a MediaPath know only either simplex or duplex? Isn't edge bindings a changable property depending on interpreter settings? Shouldn't a MediaPath independent on any interpreters? Or, is this an object representing capability of which the Media Path can turn over a medium along a long edge or a short edge of the medium? (6)Regarding 'prtChannelProtocolVersion', we can not specify such version information for Parallel and Serial interfaces. In this case, is an empty character string appropriate? (7)Regarding 'prtChannelCurrentJobCntlLangIndex', it is defined as holding value of 1 or more. In some of our office printers, we can no control language specified. For example, if page description language is set to 'langEscapeP(9)' by default and no control language is set, the channel does only accept print data described by langEscapeP. In this case, must we use 'other(1)' for 'prtChannelCurrentJobCntlLangIndex'? I prefer 0 or some minus value. (8)Another regarding 'prtChannelCurrentJobCntlLangIndex'. Our office printers have PJL-like control language, called 'JCL' which can switch PDLs. In such a case, may we use 'langPJL(5)' for it? Otherwise, must we register a type 2 enumeration, or must we use 'other(1)'? (In item #7 if we must use 'other(1)' we can not distinguish the case.) (9)I understand a Channel supports a print data stream from interface to interpreter, and does not from interpreter to interface. Is it correct? Should we include a channel from interpreter to marker in prtChannelTable? (10)We could not understand the clear meaning of 'prtInterpreterDefaultCharSetOut'. What direction is this output, from the interpreter to an channel or from the interpreter to a marker? And what is the output, print data or some notification? -----------------   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10404; 21 May 96 4:24 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10400; 21 May 96 4:24 EDT Received: from [15.254.56.2] by CNRI.Reston.VA.US id aa03525; 21 May 96 4:24 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA203595670; Tue, 21 May 1996 01:01:40 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA147484217; Tue, 21 May 1996 01:36:57 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA28964; Tue, 21 May 96 01:22:00 -0600 Received: from alpha.xerox.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA235223934; Tue, 21 May 1996 00:32:14 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <17306(6)>; Tue, 21 May 1996 00:29:24 PDT Received: from ppphastings.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA08626; Tue, 21 May 96 00:29:18 PDT Message-Id: <9605210729.AA08626@diana.cp10.es.xerox.com> X-Sender: hastings@diana (Unverified) X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 21 May 1996 00:26:59 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: Alerts review I have the following comments on the Alerts as per my action item. Comparing with file alrtspec.doc, version 0.3, dated 3/23/96: 1. Much of the object DESCRIPTION seems to have been copied into the new textual-convention as well. Shouldn't the DESCRIPTION for the object be talking about the object and the DESCRIPTION for the enum be talking about the enum, as if the enum could be used by several different objects. Some of the new additions were added to the text copied to the TC but not copied into the object DESCRIPTION which contains duplicted text. I haven't checked to see if this was done for other objects not in the Alerts group. 2. I suggest that each PrtXxxEntry that contains objects from other groups, have a comment showing where the objects for the other groups start, as has been done for the Alerts table which also has an object from the Alert Time Group. 3. prtAlertIndex: add the word "change" after "binary" in the third to last line. 4. See separate mail message about prtAlertSeverityLevel and forward compatibility of warning(4) code with unary and binary warnings. 5. The two sentences: "A warning is defined to be a non-critical alert. The value also indicates whether the event is a binary change event or a unary change event." were copied to the enum TC, but not to the object description. 6. prtAlertTrainingLevel: all of the DESCRIPTION has been copied into the enum. I think some should be in the object and some in the enum. 7. PrtAlertCodeTC: some of the enum symbols didn't have "ed" added: coverOpened(3) interlockOpened(4) configurationChanged(7) subunitOpened(18) interpreterMemoryIncreased(1501) interpreterMemoryDecreased(1502) 8. I believe that we agreed to delete the DEPRECATED interpreterContextSavingOn(1512) and interpreterContextSavingOff(1513) Thanks, Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10431; 21 May 96 4:26 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10427; 21 May 96 4:26 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa03550; 21 May 96 4:26 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA207085816; Tue, 21 May 1996 01:04:07 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA150394369; Tue, 21 May 1996 01:39:29 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA28968; Tue, 21 May 96 01:24:34 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA137034091; Tue, 21 May 1996 00:34:51 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <17310(7)>; Tue, 21 May 1996 00:30:22 PDT Received: from ppphastings.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA08629; Tue, 21 May 96 00:30:16 PDT Message-Id: <9605210730.AA08629@diana.cp10.es.xerox.com> X-Sender: hastings@diana (Unverified) X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 21 May 1996 00:27:57 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: How to make prtAlertSeverityLevel enum addition compatible The PWG agreed to clarify the prtAlertSeverityLevel enums to indicate binary versus unary change event as well as follows: old new --- --- other(1) other(1) critical(3) criticalBinaryChangeEvent(3) warning(4) warningUnaryChangeEvent(4) warningBinaryChangeEvent(5) Presumably we picked the clarification for enum value 4 to be for a unary change event, because the current implementations had implemented warnings that were unary change events (such as configuration change), rather than binary change events (such as toner low). However, this puts an implementor that wants to implement a warning binary change event, such as toner low, in a quandry. If they are implementing a conforming implementation of RFC 1759, they have to use warning(4). If they implement the new draft Printer MIB (when it becomes an RFC), they have to implement wanringBinaryChangeEvent(5). We have such an implementation. An alternative would be to deprecate (the ambiguous) warning(4) in the draft Printer MIB and add two new codes: warning(4) -- DEPRECATED warningBinaryChangeEvent(5) warningUnaryChangeEvent(6) Then a management application that gets a 4 knows that the warning may be either a unary or a binary change event. However, if a management app gets a 5 or a 6, the management application knows which type of warning. I'd like to discuss this issue as part of the review of the alerts. Thanks, Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10442; 21 May 96 4:26 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10438; 21 May 96 4:26 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa03555; 21 May 96 4:26 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA207075816; Tue, 21 May 1996 01:04:06 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA150364369; Tue, 21 May 1996 01:39:29 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA28966; Tue, 21 May 96 01:24:33 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA137014090; Tue, 21 May 1996 00:34:50 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <17312(1)>; Tue, 21 May 1996 00:30:25 PDT Received: from by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AB08629; Tue, 21 May 96 00:30:19 PDT Message-Id: <9605210730.AB08629@diana.cp10.es.xerox.com> X-Sender: hastings@diana (Unverified) X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 21 May 1996 00:28:00 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: Is Manual Feed and Auto Switch one per printer or one per input sub-unit? In reviewing the Input Switching Group, the suggest was made that two of the objects need not be in the Input table, but could be in the General table instead. The objects are: prtInputManualFeedTimeout prtInputAutoSwitch A printer only has one manual input sub-unit and its is desirable to switch the auto switching on and off with a single write. These object would still remain in the optional Input Switching Group, but just be allocated in the General table, as are other objects from other groups that have only one object per printer. However, if anyone sees a need for prtInputManualFeedTimeout to be per input sub-unit or for prtInputAutoSwitch to be per input sub-unit, then I'd withdraw the suggested change. Only the OIDs and SEQUENCE would need be changed as follows: 1. Add prtInputManualFeedTimeout and prtInputAutoSwitch to the end of the PrtGeneralEntry SEQUENCE 2. Remove prtInputManualFeedTimeout and prtInputAutoSwitch from the PrtInputEntry (leaving prtInputNextIndex). 3. Change the OID assigned to prtInputManualFeedTimeout from prtInputEntry 24 to prtGeneralEntry 18. 4. Change the OID assigned to prtInputAutoSwitch from prtInputEntry 25 to prtGeneralEntry 19. 5. Change the OID assigned to prtInputNextIndex from prtInputEntry 26 to prtInputEntry 24. I'd like to discuss at the PWG meeting this Wednesday. Thanks, Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20409; 21 May 96 11:36 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20405; 21 May 96 11:36 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa08428; 21 May 96 11:36 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA014471941; Tue, 21 May 1996 08:19:01 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA012211937; Tue, 21 May 1996 09:18:57 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA29401; Tue, 21 May 96 09:08:29 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31A1DEED@hpb15650.boi.hp.com>; Tue, 21 May 96 09:19:09 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: hastings , pmi Subject: RE: Questions about the SMIv1 translation of RFC 1759 and read -only vs.not-accessible indices Date: Tue, 21 May 96 10:19:00 M Message-Id: <31A1DEED@hpb15650.boi.hp.com> Encoding: 62 TEXT X-Mailer: Microsoft Mail V3.0 Tom & all, 1. The SMIv1 Printer MIB that is available on the HP PWG ftp site is nothing more than a translation that was done from v2 to v1. It was provided by me as a tool for others that needed a v1 version of the MIB, and if you look at the file, you will find a lot of problems with it.. It seems to work with OpenView (somewhat), but it doesn't even compile with ManageWise. So, the answer is: "No, it is not condoned by PWG." 2. As far as the index objects visibility, that was done during the conversion from v2 to v1 by the tool that was used. There was a discussion of this on the mailing list earlier. I guess the bottom line, someone needs to do a better job of writing v2 to v1 converters. 3. One way to solve this problem would be to do an official Printer MIB v1 translation, and make it available to the NMS vendors to ship with their products. As it stands right now, having visible indexes in v1 seems to be a convenience factor (check out the earlier mailings on the subject). As far as the two objects having different behaviors, I believe this is totally depend on how you are planning on using the MIB. Since Printer MIB has not been integrated into any NMS products (correct me if I am wrong, here..), the usage of Printer MIB v1 mostly adds up to using it as a MIB browser (which is exactly how I use it..) From that perspective, I don't see a problem regarding to two objects having different behaviors.. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: hastings[SMTP:hastings@cp10.es.xerox.com] Sent: Monday, May 20, 1996 5:55 PM To: pmi Subject: Questions about the SMIv1 translation of RFC 1759 and read-only vs.not-accessible indices We have the following questions which we'd like to add to the agenda of the PWG this Wednesday: 1. Is the SMIv1 Printer MIB that is available from the PWG ftp site officially condoned by the PWG? ftp://ftp-out.external.hp.com/snmpmib/prtspec/smiv1/rfc1759.mib 2. Was there a conscience decision made to translate the "not-accessible" indices in the SMIv2 MIB to "read-only" indices in the SMIv1 MIB? 3. If the two SMI versions of the Printer MIB stand as they are, that would imply that the index objects are visible in the SMIv1 version and not in the SMIv2 version. This leads to the same object (same OID) having different behavior, depending on the SMI version. This is recommended against by David Reid of SNMP Research, Inc., as well as others. Has the PWG accepted this caveat? Thanks, Tom Hastings   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20880; 21 May 96 11:48 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20875; 21 May 96 11:48 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa08720; 21 May 96 11:48 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA082342765; Tue, 21 May 1996 08:32:46 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA051522761; Tue, 21 May 1996 09:32:41 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA29464; Tue, 21 May 96 09:22:18 -0600 Received: from VNET.IBM.COM by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA209302753; Tue, 21 May 1996 08:32:33 -0700 Message-Id: <199605211532.AA209302753@relay.hp.com> Received: from BLDVMB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 8145; Tue, 21 May 96 11:28:22 EDT Date: Tue, 21 May 96 09:28:08 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Harry Lewis " To: pmi@hpbs987.boi.hp.com Subject: Indexes Tom Hastings wrote - >We have the following questions which we'd like to add to the agenda >of the PWG this Wednesday: > >1. Is the SMIv1 Printer MIB that is available from the PWG ftp site > officially condoned by the PWG? > > ftp://ftp-out.external.hp.com/snmpmib/prtspec/smiv1/rfc1759.mib > >2. Was there a conscience decision > made to translate the "not-accessible" indices in the SMIv2 MIB to > "read-only" indices in the SMIv1 MIB? > >3. If the two SMI versions of the Printer MIB stand as they are, > that would imply that the index objects are visible in the SMIv1 > version and not in the SMIv2 version. This leads to the same > object (same OID) having different behavior, depending on the > SMI version. This is recommended against by David Reid of SNMP > Research, Inc., as well as others. Has the PWG accepted this > caveat? > >Thanks, >Tom Hastings I would like to know when, where and how the SMIv1 MIB was developed. We have been working strictly from RFC1759 which only addresses differences in SMI as it pertains to alerts. I agree that dual behavior of the agent should not be required. While I like the idea of r/o indexes, I believe conformance to RFC1759 requires they be not-accessible. I agree we should discuss this in Chicago.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21434; 21 May 96 12:09 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21429; 21 May 96 12:09 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa09094; 21 May 96 12:09 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA195224219; Tue, 21 May 1996 08:57:00 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA126204217; Tue, 21 May 1996 09:56:57 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA29547; Tue, 21 May 96 09:46:34 -0600 Received: from VNET.IBM.COM by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA235514208; Tue, 21 May 1996 08:56:48 -0700 Message-Id: <199605211556.AA235514208@relay.hp.com> Received: from BLDVMB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 8970; Tue, 21 May 96 11:52:35 EDT Date: Tue, 21 May 96 09:51:41 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Harry Lewis " To: pmi@hpbs987.boi.hp.com, lmorgan@vnet.ibm.com Subject: Question about prtInterpreterDefaultCharSetIn Tom Hastings wrote - >The current DESCRIPTION: > > The default coded character set for input octets > encounrtered outside a context in which the Page > Description Language established the interpretation > of the octets. > > This value shall be (2) if there is not default. > > >Question 1: > >What does this object really control? >Does the value control the character set of the PDL data >to be printed or the character set of the PDL command sequences? >If a management station wrote this object, what would be the >effect? Tom, this object is intended to establish the *default* Character Set for the specified Interpreter. The language about "context" is an attempt to acknowledge that the print datastream itself may well alter the active Character Set. No distinction is made between data and commands in this definition. >Question 2: > >Should we change "the Page Description Language" to "this intepreter" >in the DESCRIPTION? Maybe the PDL doesn't have a default, but the >interpreter is configured so that it does. No. This would be incorrect in my estimation. What we're really trying to say here is more like ... "the print job datastream changes the active character set...". It seems we were straining here to avoid the use of "print job". >We'd like to discuss this at the PWG meeting. Might be a good idea > >Thanks, >Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01732; 21 May 96 17:31 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01728; 21 May 96 17:31 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa19465; 21 May 96 17:31 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA139373072; Tue, 21 May 1996 14:11:13 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA077433069; Tue, 21 May 1996 15:11:09 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA00174; Tue, 21 May 96 15:00:46 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA101503063; Tue, 21 May 1996 14:11:03 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <15394(1)>; Tue, 21 May 1996 14:08:19 PDT Received: from cmqlite-6.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA08917; Tue, 21 May 96 14:08:14 PDT Message-Id: <9605212108.AA08917@diana.cp10.es.xerox.com> X-Sender: hastings@diana X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 21 May 1996 14:05:58 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: The OMG has a CORBA Event Service To SENSE people, I was just told about the OMG Event Service which has the concept of publishers and subscribers, producers, consumers, channels, and factories. Have the SENSE project people seen it? I tried to find it on their home page: http://www.omg.org but was unsuccessful. The OMG has a huge number of documents. Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18737; 23 May 96 10:13 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18731; 23 May 96 10:13 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa08280; 23 May 96 10:13 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA119734271; Wed, 22 May 1996 15:31:11 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA282984267; Wed, 22 May 1996 16:31:07 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA02264; Wed, 22 May 96 16:20:36 -0600 Received: from alpha.xerox.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA161464127; Wed, 22 May 1996 15:29:02 -0700 Received: from zombi.eso.mc.xerox.com ([13.1.189.45]) by alpha.xerox.com with SMTP id <15516(7)>; Wed, 22 May 1996 15:24:20 PDT Received: from truckstop ([13.231.196.89]) by zombi.eso.mc.xerox.com (4.1/SMI-4.1) id AA19130; Wed, 22 May 96 18:23:41 EDT Received: by truckstop (4.1/XeroxClient-1.1) id AA07186; Wed, 22 May 96 18:23:46 EDT Date: Wed, 22 May 1996 15:23:46 PDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Ira Mcdonald x10962 Message-Id: <9605222223.AA07186@truckstop> To: pmi@hpbs987.boi.hp.com Subject: Re: Index Access Levels in Printer MIB Hi Harry and PWG folks, The reason that RFC 1759 (in SMIv2 from March 1993 - RFC 1442 style) has the indices 'not-accessible' is because it's explicitly called for by RFC 1442 for 'auxiliary' objects. The additional wrinkle is that the NEW version of SMIv2 (RFC 1902, 1996) has a NEW access level for indices ('accessible-for-notify') when and only when they must be reported in an SNMPv2 style NOTIFICATION-TYPE (ie, trap) - otherwise they are still supposed to be 'not-accessible'. Now the PWG will inevitably be forced into some judgment call for the update to RFC 1759, but this is pretty generally broken in SNMP standards - SMIv1 permitted the 'not-accessible' usage (although without any prescriptive text - it was simply done - most notably in the Ethernet MIB - RFC 1643/1650 in SMIv1/v2 style) - early SMIv2 called for 'not-accessible' at all times (prescriptively) and new SMIv2 has a fresh wrinkle (which causes RFC 1759 to fail compilation in the Epilogue Emissary V6.0 ASN.1 compiler). I'd appeal to IETF SNMP experts (like the folks who changed the SMIv2 spec) for 'ruling' and not bother with the PWG debate, I guess. Cheers, - Ira McDonald (outside consultant at Xerox) High North Inc PO Box 221 Grand Marais, MI 49839 906-494-2434 PS - Hi Jay - we got home on 6 May - six feet of snow on the north side of the barn - crocuses and snowdrops opened that day - we are now flying into mid-Spring, with warm weather.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17470; 28 May 96 11:49 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17466; 28 May 96 11:49 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa09645; 28 May 96 11:49 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA223627321; Tue, 28 May 1996 08:28:42 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA173377318; Tue, 28 May 1996 09:28:38 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA26802; Tue, 28 May 96 09:18:11 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31AB1BBB@hpb15650.boi.hp.com>; Tue, 28 May 96 09:28:59 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: Draft Printer MIB review Date: Tue, 28 May 96 10:29:00 M Message-Id: <31AB1BBB@hpb15650.boi.hp.com> Encoding: 133 TEXT X-Mailer: Microsoft Mail V3.0 1. Update the header & footer section of the document. 2. Textual conventions should follow the standard naming convention of PrtxxxTC: MediaUnit, CapacityUnit, SubUnitStatus, PresentOnOff, CodedCharSet, PrtInterpreterLangFamily. 3. Problems with smart quotes on pg. 44 prtGeneralReset description, pg. 45 prtCoverEntry description, pg. 47 prtLocalizationEntry description, pg. 52 prtInputEntry description, pg. 62 prtOutputEntry description, pg. 68 prtOutputStackingOrder description, pg. 68 prtOutputPageDeliveryOrientation description, pg. 70 prtMarkerEntry description, pg. 76 prtMarkerSuppliesEntry description, pg. 79 prtMarkerColorantEntry description, pg. 82 prtMediaPathEntry description, pg. 87 prtChannelEntry description, pg. 91 prtInterpreterEntry description, pg. 99 prtConsoleDisplayBufferEntry description, pg. 100 prtConsoleLightEntry description, pg. 103 prtAlertEntry description, pg. 108 prtAlertDescription description, 4. Pg. 1 - Update the author information for Randy Turner & Joel Gyllenskog. 5. Pg. 1 - Update the Request for comments section on the front page. 6. Pg. 1 - Update the table of contents. 7. Pg. 12 - Section 2.2.10: References to Channels & Channel Group should be changed to: Print Job Delivery Channel. 8. Pg. 13 - Section 2.2.13: The sentences 'if and only if the event is a critical event, initiating a trap' and 'Each reportable event causes an entry to be made in the Alert Table' should be rephrased to reflect the optional alert alert implementation. 9. Pg. 19 - 1st paragraph: This section should be rephrased to indicate the optional alert alert implementation. 10. Pg. 19 - Section 2.2.13.4 3rd paragraph: This sentence should be rephrased to indicate the optional alert alert implementation. 11. Pg. 20 - Section 2.2.13.5: This section is missing. It should include information from prtAlertGroupIndex description, i.e. the MIB is indexed with hrDeviceIndex & another index optionally which could be the value -1 if not present. 12. Pg. 21 - Item #2: The sentence 'The printer will behave differently if the installation of the resource is reported than the printer would if the installation were not reported; that is, the object is not to be used as a place to put information not used by the printer, i.e., not a "PostIt"' should be reworded. 13. Pg. 22 - Section 2.4.1 enumeration(3): "controls; An" should be "controls; an". 14. Pg. 29 - PrtChannelTypeTC: This section should be replaced with the updated version. 15. Pg. 33 - PrtInterpreterLangFamily: langPrescribe(50) is missing. 16. Pg. 34 - photographicImagesetter(23): Extra space at the beginning of the word. 17. Pg. 39 - Example alert table entry section: prtAlertGroup alert(18) should be indented to match others. 18. Pg. 40 - subunitPowerSaver(23): This might need rewording, since the word does not indicate a state or action. 19. Pg. 44 - prtGeneralReset description: Missing ' before resetToNVRAM. 20. Pg. 46 - Localization table section: extra line in the group description. 21. Pg. 50 - prtGeneralCurrentOperator & prtGeneralServicePerson descriptions should be identical regarding to the phone number specification. 22. Pg. 53 - prtInputType description: What does the "other choice" specifies?? 23. Pg. 55 - The 1st paragraph: Return should be deleted after the "Feed dimension measurements". 24. Pg. 55 - prtInputMediaDimFeedDirChoosen & prtInputMediaDimXFeedDirChosen description: DimUnit should be MediaUnit (prtOutputDimUnit). 25. Pg. 67 - prtOutputMaxDimFeedDir & prtOutputMaxDimXFeedDir & prtOutputMinDimFeedDir & prtOutputMinDimXFeedDir description: DimUnit should be MediaUnit (prtInputDimUnit). 26. Pg. 68 - prtOutputStackingOrder description: 'FirstToLast' should be 'firstToLast'; 'LasttoFirst' should be 'lastToFirst'. 27. Pg. 68 - prtOutputPageDeliveryOrientation: Face-Up should be faceUp; Face-Down should be faceDown. 28. Pg. 70 - prtMarkerDefaultIndex description: There should be a space between marker and sub-unit. 29. Pg. 73 - prtMarkerProcessColorants description: SpotColorants should be prtMarkerSpotColorants. 30. Pg. 73 - prtMarkerSpotColorants description: ProcessColorants should be prtMarkerProcessColorants. 31. Pg. 74 - prtMarkerAddressabilityFeedDir & prtMarkerAddressabilityXFeedDir & prtMarkerNorthMargin & prtMarkerSouthMargin description: AddressabilityUnit should be prtMarkerAddressabilityUnit. 32. Pg. 74 - prtMarkerSouthMargin description: NorthMargin should be prtMarkerNorthMargin. 33. Pg. 75 - prtMarkerWestMargin & prtMarkerEastMargin description: AddressabilityUnit should be prtMarkerAddressabilityUnit. 34. Pg. 75 - prtMarkerWestMargin & prtMarkerEastMargin description: NorthMargin should be prtMarkerNorthMargin. 35. Pg. 78 - prtMarkerSuppliesMaxCapacity description: SupplyUnit should be prtMarkerSuppliesSupplyUnit. 36. Pg. 83 - prtMediaPathMaxMediaFeedDir & prtMediaPathMaxMediaXFeedDir descriptions: MediaSizeUnit should be prtMediaPathMediaSizeUnit. 37. Pg. 84 - prtMediaPathMinMediaXFeedDir & prtMediaPathMinMediaFeedDir descriptions: MediaSizeUnit should be prtMediaPathMediaSizeUnit. 38. Pg. 85 - The Channel Group is now called Print Job Delivery Channel Group. References to the Channel Group through out the document should be corrected. 39. Pg. 86 - ChannelType (2 occurrances) should be prtChannelType which is now assocApplicationProtocol. 40. Pg. 86 - The definition of Channel Table should be extended to include the use of the NSM MIB. 41. Pg. 90 - The Interpreter Group object definitions should be changed to reflect the support for MFPA device communications and discovery functions. 42. Pg. 96 - prtInterpreterFeedAddressability description: Remove the 's' after the '... direction in 10000 prtMarkerAddressabilityUnit'. 43. Pg. 97 - prtInterpreterXFeedAddressability description: Remove the 's' after the '... direction in 10000 prtMarkerAddressabilityUnit'. 44. Pg. 100 - prtConsoleDisplayBufferText description: ConsoleLocalization should be prtConsoleLocalization. 45. Pg. 103 - prtAlertIndex description: Should the optional alert alert code implementation be included here? See the end of the description on pg. 104 relating to discovering binary alerts that are deleted. 46. Pg. 106 - prtAlertGroupIndex description: Group should be prtAlertGroup; GroupIndex should be prtAlertGroupIndex. 47. Pg. 113 - Where does the conformance of printerV1Alert & printerV2Alert fit? There is nothing that indicates that these objects are mandatory or not in the MIB. 48. Pg. 116 - Appendix A: The description of impressions should be added to the appendix. 49. Pg. 116 - Appendix A: The '.' should be added to the end of descriptions where ever appropriate. 50. Pg. 118 - Object definition: Remove the ')' at the end of the line. 51. Pg. 119 - Appendix B description: Remove the '-' in prtInputChosen-MediaDimXFeedDir. 52. Pg. 132 - Appendix E: Participant list needs to be updated. 53. Pg. 134 - Authors' Addresses: This section needs to be updated. 54. New Appendix section: Need to add an appendix to reflect all the different enums that are used through out the document as an easy to use reference. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19778; 28 May 96 13:33 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19774; 28 May 96 13:33 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa11417; 28 May 96 13:33 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA216363813; Tue, 28 May 1996 10:16:54 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA258823809; Tue, 28 May 1996 11:16:49 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA02873; Tue, 28 May 96 11:06:24 -0600 Received: from uscore.underscore.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA131623797; Tue, 28 May 1996 10:16:38 -0700 Received: by uscore.underscore.com (Smail3.1.28.1 #5) id m0uOSIw-000US2C; Tue, 28 May 96 13:11 EDT Message-Id: Date: Tue, 28 May 96 13:11 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: JK Martin To: pmi@hpbs987.boi.hp.com Subject: Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting There was some discussion on the 2nd day of the last PWG meeting (Chicago) in which some folks expressed an interest in having a sort of "dress rehearsal" for the Printer MIB bake-off at the Networld-Interop show this September. The discussion talked about having such a dress rehearsal at the July PWG meeting in Portland, Oregon. Unfortunately, I was not present at that part of the meeting, so I'm not sure if I have the "facts" straight...please correct me on any of the above points. Anyway, Underscore was expecting to publically unveil the first implementation of the new SENSE project at the next PWG meeting (June, Montreal), in which we would bring a horde of equipment and personnel to effect a real, live hands-on demo of the entire system, including Windows, NT and Unix systems, and several different types of printers. However, if the PWG desires to have a dress rehearsal bake-off at the July meeting--and if several participants expect to bring their pet printers to that meeting--then this would be a big help for Underscore, since we would not have to bring as much equipment, etc. So, is this pre-bake-off for real? If so, can we start making public plans? Who is interested? Underscore would be bringing a full complement of SENSE components; included in that collection *might* be the first generic Publisher component based on the Printer MIB, so we might be able to kill two birds with one stone in this effort. Please post your interest/comments/etc as soon as you can...even if you're against the idea (but please state why you think we should not have one!). ...jay PS: By the way, if any vendor is interested in having their printer(s) become part of the SENSE demo, please contact me privately and we'll see what we can do with what time we have before the bake-off.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23859; 28 May 96 16:33 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23855; 28 May 96 16:33 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa14597; 28 May 96 16:33 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA167834307; Tue, 28 May 1996 13:11:52 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA080804297; Tue, 28 May 1996 14:11:37 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA06487; Tue, 28 May 96 14:00:54 -0600 Received: from mail.sharplabs.com ([204.75.175.200]) by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA273314268; Tue, 28 May 1996 13:11:08 -0700 Received: from sla5c by mail.sharplabs.com (SMI-8.6/SMI-SVR4) id MAA17918; Tue, 28 May 1996 12:59:52 -0700 Received: by sla5c (SMI-8.6) id MAA10586; Tue, 28 May 1996 12:59:42 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Randy Turner Message-Id: <9605281259.ZM10584@sla5c.sharplabs.com> Date: Tue, 28 May 1996 12:59:42 -0700 In-Reply-To: jkm@underscore.com (JK Martin) "Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting" (May 28, 1:11pm) References: X-Mailer: Z-Mail (3.2.1 10apr95) To: JK Martin , pmi@hpbs987.boi.hp.com Subject: Re: Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi Jay, The portland meeting is going to be a dress rehearsal for Fall Interop in Atlanta in September. I think Lexmark,Xerox,HP and Sharp will have peripherals there, and I will have a small LAN setup in the meeting room for testing. 10-Base-t connections only unless I hear different from anyone. I will also have an SNMP NMS running with the Printer MIB compiled in for Printer and/or other MIB testing. This will be a SunNet Mgr NMS running on a SparcStation. Let me know if you can think of that we might need. This applies to anyone on the list that will be attending as well. I would like to have a list of final equipment sometime before the end of June if possible so I can make sure everything is available. Thanks! R. On May 28, 1:11pm, JK Martin wrote: > Subject: Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting > There was some discussion on the 2nd day of the last PWG meeting > (Chicago) in which some folks expressed an interest in having a sort of > "dress rehearsal" for the Printer MIB bake-off at the Networld-Interop > show this September. The discussion talked about having such a dress > rehearsal at the July PWG meeting in Portland, Oregon. > > Unfortunately, I was not present at that part of the meeting, so I'm > not sure if I have the "facts" straight...please correct me on any of > the above points. > > Anyway, Underscore was expecting to publically unveil the first > implementation of the new SENSE project at the next PWG meeting (June, > Montreal), in which we would bring a horde of equipment and personnel > to effect a real, live hands-on demo of the entire system, including > Windows, NT and Unix systems, and several different types of printers. > > However, if the PWG desires to have a dress rehearsal bake-off at the > July meeting--and if several participants expect to bring their pet > printers to that meeting--then this would be a big help for Underscore, > since we would not have to bring as much equipment, etc. > > So, is this pre-bake-off for real? If so, can we start making public > plans? > > Who is interested? > > Underscore would be bringing a full complement of SENSE components; > included in that collection *might* be the first generic Publisher > component based on the Printer MIB, so we might be able to kill two > birds with one stone in this effort. > > Please post your interest/comments/etc as soon as you can...even if > you're against the idea (but please state why you think we should not > have one!). > > ...jay > > PS: By the way, if any vendor is interested in having their printer(s) > become part of the SENSE demo, please contact me privately and we'll > see what we can do with what time we have before the bake-off. >-- End of excerpt from JK Martin   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24706; 28 May 96 17:02 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa24701; 28 May 96 17:02 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa15110; 28 May 96 17:02 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA003556101; Tue, 28 May 1996 13:41:41 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA158596099; Tue, 28 May 1996 14:41:39 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA06525; Tue, 28 May 96 14:31:14 -0600 Received: from uscore.underscore.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA297066088; Tue, 28 May 1996 13:41:28 -0700 Received: by uscore.underscore.com (Smail3.1.28.1 #5) id m0uOVG1-000US2C; Tue, 28 May 96 16:20 EDT Message-Id: Date: Tue, 28 May 96 16:20 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: JK Martin To: pmi@hpbs987.boi.hp.com Subject: Re: Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting Jay Cummings has allowed me to post his informative (yet personal) reply to the PWG list at large. Jay believes Randy Turner and David Kellerman signed up to coordinate this "event". Is this true? If this is true, then can Randy and/or David say a few words about this event? ...jay ----- Begin Included Message ----- From novell.com!Jay_Cummings Tue May 28 15:33:43 1996 Date: Tue, 28 May 1996 13:35:10 -0600 From: Jay_Cummings@novell.com (Jay Cummings) To: jkm@underscore.com Subject: Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting -Reply Jay, I think you have the bake-off facts straight. It will be the day before the normal PWG, PMP, JMP, Sense meetings. The pre-bake-off was planned for 6/22/96. Novell is planning on bringing our implementation of RFC1759 for NDPS. (I hope it works by then. :-) I think Randy & David were going to coordinate the equipment, setup, room, etc. /* - - -S-I-G-N-A-T-U-R-E- -B-L-O-C-K- - - Jay R. Cummings Services Manageability Development Team Development Manager Novell, Inc. -- where #Everything#s Connected# Prv-D-12-1 122 East 1700 South Provo, Utah 84606 Phone: 1-800-453-1267 x.3895 (801) 861-3895 Fax: (801) 861-7520 INTERNET: jay_cummings@novell.com - - -S-I-G-N-A-T-U-R-E- -B-L-O-C-K- - - */ ----- End Included Message -----   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27258; 28 May 96 19:13 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27254; 28 May 96 19:13 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa17366; 28 May 96 19:13 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA277584757; Tue, 28 May 1996 16:05:58 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA233974754; Tue, 28 May 1996 17:05:54 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA06789; Tue, 28 May 96 16:54:52 -0600 Received: from nls.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA154764658; Tue, 28 May 1996 16:04:19 -0700 Received: by nls.com (MX V4.1 VAX) id 1; Tue, 28 May 1996 14:53:01 PST Date: Tue, 28 May 1996 14:52:59 PST Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: David Kellerman To: pmi@hpbs987.boi.hp.com Message-Id: <009A302D.D3AADB5D.1@nls.com> Subject: Re: Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting > Jay Cummings has allowed me to post his informative (yet personal) reply > to the PWG list at large. > > Jay believes Randy Turner and David Kellerman signed up to coordinate > this "event". Is this true? If this is true, then can Randy and/or > David say a few words about this event? > > ...jay It's Randy's show. Northlake, however, is located in downtown Portland, about ten blocks from the Marriott where the meeting and the pre-bakeoff are planned. So I told Randy in the meeting to call if there was anything I could help with. (Someone did ask whether we could hold the pre-bakeoff at Northlake, but we really don't have the space.) Northlake does have an internet connection, which we're glad to make available if anyone needs it. (Ten blocks is just far enough to be inconvenient, though, I'm afraid.) Also discussed at about this time was the fact that the Portland Microbrew Festival happens the weekend following the meeting (and somehow the PWG meetings got swapped to the first half of the week, furthest from the festival weekend). It turns out the microbrew selection in Portland is pretty good, festival or not, and I did promise to assemble a list of pubs for those interested. :: David Kellerman Northlake Software 503-228-3383 :: kellerman@nls.com Portland, Oregon fax 503-228-5662   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27755; 28 May 96 19:47 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27751; 28 May 96 19:47 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa17770; 28 May 96 19:47 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA105426891; Tue, 28 May 1996 16:41:31 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA021766888; Tue, 28 May 1996 17:41:28 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA06874; Tue, 28 May 96 17:31:03 -0600 Received: from dub-img-1.compuserve.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA187436879; Tue, 28 May 1996 16:41:19 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: YUKI@kei-ca.ccmail.compuserve.com Received: by dub-img-1.compuserve.com (8.6.10/5.950515) id TAA05226; Tue, 28 May 1996 19:38:41 -0400 Date: 28 May 96 19:37:29 EDT To: PMI@hpbs987.boi.hp.com, jkm@underscore.com MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US Subject: Re: Call for Interest for a "Pre-BakeOff BakeOff" at the Jul Message-Id: <960528233729_702420.204300_BHD30-9@CompuServe.COM> Jay Kyocera is planing to bring a printer that support Printer MIB and a utility that can access minimum items of Printer MIB for any printer at July meeting. A. Yuki Kyocera ___________________________________ o?EM _______________________________________ iAu?: Call for Interest for a "Pre-BakeOff BakeOff" at the Jul... ?uEMA?: INTERNET:jkm@underscore.com at CSERVE o.ot: 5/28/96 12:41 PM Sender: jkm@underscore.com Received: from paloalto.access.hp.com (paloalto.access.hp.com [15.254.56.2]) by dub-img-3.compuserve.com (8.6.10/5.950515) id NAA09518; Tue, 28 May 1996 13:29:50 -0400 Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA254364215; Tue, 28 May 1996 10:23:35 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA266564203; Tue, 28 May 1996 11:23: 24 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA02873; Tue, 28 May 96 11:06:24 -0600 Received: from uscore.underscore.com by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA131623797; Tue, 28 May 1996 10:16:38 -0700 Received: by uscore.underscore.com (Smail3.1.28.1 #5) id m0uOSIw-000US2C; Tue, 28 May 96 13:11 EDT Message-Id: Date: Tue, 28 May 96 13:11 EDT From: jkm@underscore.com (JK Martin) To: pmi@hpbs987.boi.hp.com Subject: Call for Interest for a "Pre-BakeOff BakeOff" at the July Meeting There was some discussion on the 2nd day of the last PWG meeting (Chicago) in which some folks expressed an interest in having a sort of "dress rehearsal" for the Printer MIB bake-off at the Networld-Interop show this September. The discussion talked about having such a dress rehearsal at the July PWG meeting in Portland, Oregon. Unfortunately, I was not present at that part of the meeting, so I'm not sure if I have the "facts" straight...please correct me on any of the above points. Anyway, Underscore was expecting to publically unveil the first implementation of the new SENSE project at the next PWG meeting (June, Montreal), in which we would bring a horde of equipment and personnel to effect a real, live hands-on demo of the entire system, including Windows, NT and Unix systems, and several different types of printers. However, if the PWG desires to have a dress rehearsal bake-off at the July meeting--and if several participants expect to bring their pet printers to that meeting--then this would be a big help for Underscore, since we would not have to bring as much equipment, etc. So, is this pre-bake-off for real? If so, can we start making public plans? Who is interested? Underscore would be bringing a full complement of SENSE components; included in that collection *might* be the first generic Publisher component based on the Printer MIB, so we might be able to kill two birds with one stone in this effort. Please post your interest/comments/etc as soon as you can...even if you 're against the idea (but please state why you think we should not have one!). ...jay PS: By the way, if any vendor is interested in having their printer(s) become part of the SENSE demo, please contact me privately and we'll see what we can do with what time we have before the bake-off.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29493; 28 May 96 21:40 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa29489; 28 May 96 21:39 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa19122; 28 May 96 21:40 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA094763508; Tue, 28 May 1996 18:31:49 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA279353497; Tue, 28 May 1996 19:31:38 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA06969; Tue, 28 May 96 19:21:00 -0600 Received: from alpha.xerox.com by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA010253480; Tue, 28 May 1996 18:31:20 -0700 Received: from diana.cp10.es.xerox.com ([13.240.120.44]) by alpha.xerox.com with SMTP id <14852(5)>; Tue, 28 May 1996 18:27:27 PDT Received: from cmqlite-6.cp10.es.xerox.com by diana.cp10.es.xerox.com (4.1/SMI-4.1) id AA10649; Tue, 28 May 96 18:27:20 PDT Message-Id: <9605290127.AA10649@diana.cp10.es.xerox.com> X-Sender: hastings@diana X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 28 May 1996 18:25:05 PDT To: pmi@hpbs987.boi.hp.com Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Hastings Subject: OMG Event Notification Service specification Cc: sun@wrc.xerox.com We ran AltaVista at the PWG meeting and found: CORBA Object Specification Volume 1 http://www.omg.org/docs/1994/94-01-01.ps Contains the events services somewhere inside. Its a 4.5 Mega byte PostScript file. Tom   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02606; 30 May 96 18:44 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa02602; 30 May 96 18:44 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa17762; 30 May 96 18:44 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA279095814; Thu, 30 May 1996 15:36:55 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA132025807; Thu, 30 May 1996 16:36:47 -0600 Received: from relay.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA10672; Thu, 30 May 96 16:26:18 -0600 Received: from VNET.IBM.COM by relay.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA148625796; Thu, 30 May 1996 15:36:36 -0700 Message-Id: <199605302236.AA148625796@relay.hp.com> Received: from BLDVMB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 3446; Thu, 30 May 96 18:32:23 EDT Date: Thu, 30 May 96 16:22:53 MDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "Harry Lewis " To: pmi@hpbs987.boi.hp.com Subject: v2 MIB - Alerts RFC 1759 has the following structre in the Alert Table: printerV1Alert OBJECT-IDENTITY STATUS current DESCRIPTION "The value of the enterprise-specific oid in a SNMPv1 trap sent signalling a critical event in the prtAlertTable." ::= { prtAlert 2 } printerV2AlertPrefix OBJECT IDENTIFIER ::= { printerV1Alert 0 } printerV2Alert NOTIFICATION-TYPE OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, prtAlertGroupIndex, prtAlertLocation, prtAlertCode } STATUS current DESCRIPTION "This trap is sent whenever a critical event is added to the prtAlertTable." ::= { printerV2AlertPrefix 1 } -- Note that the SNMPv2 to SNMPv1 translation rules dictate that the -- preceding structure will result in SNMPv1 traps of the following -- form: -- -- printerAlert TRAP-TYPE -- ENTERPRISE printerV1Alert -- VARIABLES { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, -- prtAlertGroupIndex, prtAlertLocation, prtAlertCode } -- DESCRIPTION -- "This trap is sent whenever a critical event is added to the -- prtAlertTable." -- ::= 1 The SMIv1 version which we have posted resolves this to: printerV1Alert OBJECT IDENTIFIER ::= { prtAlert 2 } printerV2AlertPrefix OBJECT IDENTIFIER ::= { printerV1Alert 0 } printerV2Alert TRAP-TYPE ENTERPRISE { printerV2AlertPrefix } VARIABLES { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, prtAlertGroupIndex, prtAlertLocation, prtAlertCode } DESCRIPTION "This trap is sent whenever a critical event is added to the prtAlertTable." ::= 1 My question is, what should the actual SMIv2 version of the Printer MIB look like? I'm having trouble compiling the MIB with a v2 compiler. Has anyone else run into this. It seems like v2 does not like the printerV1Alert OID.   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22420; 31 May 96 14:47 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa22416; 31 May 96 14:47 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa12564; 31 May 96 14:47 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA035417822; Fri, 31 May 1996 11:37:02 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA233577818; Fri, 31 May 1996 12:36:59 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21073; Fri, 31 May 96 12:26:32 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31AF3C63@hpb15650.boi.hp.com>; Fri, 31 May 96 12:37:23 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: June Meeting Notice -- Urgent!! Date: Fri, 31 May 96 13:39:00 M Message-Id: <31AF3C63@hpb15650.boi.hp.com> Encoding: 58 TEXT X-Mailer: Microsoft Mail V3.0 Unfortunately, the cut-off date for the reservation is May 31st.. I have contacted Larry S. to see if we can extend it at least till the end of next week.. Let me know if you have questions.. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Friday, May 31, 1996 1:16 PM To: Multiple recipients of list Subject: June Meeting Notice Meeting Notice IEEE P1284.3 IEEE P1284.4 PWG The June meetings are being held in Montreal in order to match up with the IETF quarterly meetings. The meeting schedule is modified as follows: IEEE P1284.4 Wednesday, June 26 IEEE P1284.3 Thursday, June 27 Printer Working Group Thursday-Friday, June27-28 All meeting will start at 8:30AM. Montreal Bonaventure Hilton 1 Place Bonaventure Montreal, Quebec, Canada Reservations: (514) 878-2332 Rooms: $199.00 (CAN, approx $149 US) Cutoff Date: Friday, May 31 The room rate is $199.00 (Canadian, about $149 US) single. The meeting charge is $(still TBD) per person, per meeting day. The charge includes all meeting room expenses, AV charges and break charges. Sorry for the short notice. You MUST make your reservations by Friday, May 31, and be sure to tell them you are with the FarPoint group. Thank you, Larry Stein ****************************************************************** Larry A. Stein Phone: (805)726-4420 President Fax: (805)726-4438 FarPoint Communications Web: http://www.fapo.com ******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23229; 31 May 96 15:17 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23225; 31 May 96 15:17 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa13043; 31 May 96 15:17 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA108998797; Fri, 31 May 1996 11:53:17 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA254978794; Fri, 31 May 1996 12:53:14 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21104; Fri, 31 May 96 12:42:48 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31AF4033@hpb15650.boi.hp.com>; Fri, 31 May 96 12:53:39 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: 1996 Meeting Calander Date: Fri, 31 May 96 13:52:00 M Message-Id: <31AF4033@hpb15650.boi.hp.com> Encoding: 80 TEXT X-Mailer: Microsoft Mail V3.0 Take a look at the calendar, and send in your comments.. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Friday, May 31, 1996 1:17 PM To: Multiple recipients of list Subject: 1996 Meeting Calander Well, I broke down and spent a couple of days setting up all of the meetings for the remainder of the year. The July meeting had to be changed, but everything else was the same. At the May meeting we developed a schedule to send both the .3 and .4 specs to ballot by the end of the year. Your cooperation and participation will be key to meeting this objective. Please review the list and send me your comments. I have about 3 days until I have to finalize the contracts. Also, don't forget to review the Implementers Forum outline (http://www.fapo.com/1284if.htm) -Larry (lstein@fapo.com) June: you should have made your reservations already. Montreal Bonaventure Hilton Montreal, Canada June 26 IEEE P1284.4 June 27 IEEE P1284.3 (Note overlap and change in days) June 27-28 PWG July Meetings (This was changed do to room availablity) Red Lion- Downtown Portland, OR $109/night July 29 1284.3 July 30 1284.4 July 31 - Aug 1 PWG August Meeting This will be the Implementers Forum plus the regular meetings Marriott Suites Downtown at Symphony Towers San Diego, CA $89/night Aug 26 1284 Implementers Forum Aug 27 1284.3 Aug 28 1284.4 Aug 29-30 PWG September/October Meeting New York Marriott Marquis New York City $209/night Sep 30 1284.3 Oct 1 1284.4 Oct 2-3 PWG November Meeting Bourbon Orleans Hotel New Orleans, LA Nov 4 1284.3 Nov 5 1284.4 (Don't forget your absentee ballots) Nov 6-7 PWG ****************************************************************** Larry A. Stein Phone: (805)726-4420 President Fax: (805)726-4438 FarPoint Communications Web: http://www.fapo.com ******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23438; 31 May 96 15:32 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23434; 31 May 96 15:32 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa13271; 31 May 96 15:32 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA218240210; Fri, 31 May 1996 12:16:50 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA028430207; Fri, 31 May 1996 13:16:47 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21146; Fri, 31 May 96 13:06:22 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31AF45B8@hpb15650.boi.hp.com>; Fri, 31 May 96 13:17:12 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: Change in Ultimate Meeting Schedule Date: Fri, 31 May 96 14:16:00 M Message-Id: <31AF45B8@hpb15650.boi.hp.com> Encoding: 83 TEXT X-Mailer: Microsoft Mail V3.0 FYI --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Friday, May 31, 1996 1:17 PM To: Multiple recipients of list Subject: Change in Ultimate Meeting Schedule Sorry, I screwed up the schedule for the PWG for the July meeting. I've changed it back to the original changed week of July 22 to 26. They will have one additional meeting on Monday, July 22 for the Printer MIB MibOFF. At the May meeting we developed a schedule to send both the .3 and .4 specs to ballot by the end of the year. Your cooperation and participation will be key to meeting this objective. Please review the list and send me your comments. I have about 3 days until I have to finalize the contracts. Also, don't forget to review the Implementers Forum outline (http://www.fapo.com/1284if.htm) -Larry (lstein@fapo.com) June: you should have made your reservations already. Montreal Bonaventure Hilton Montreal, Canada June 26 IEEE P1284.4 June 27 IEEE P1284.3 (Note overlap and change in days) June 27-28 PWG July Meetings (This was changed do to room availablity, and then changed again...) Red Lion- Downtown Portland, OR $109/night July 22 PWG Printer MIB MibOFF July 23 PWG July 24 PWG July 25 1284.4 July 26 1284.3 July 27-28 Portland MicroBear Brewfest August Meeting This will be the Implementers Forum plus the regular meetings Marriott Suites Downtown at Symphony Towers San Diego, CA $89/night Aug 26 1284 Implementers Forum Aug 27 1284.3 Aug 28 1284.4 Aug 29-30 PWG September/October Meeting New York Marriott Marquis New York City $209/night Sep 30 1284.3 Oct 1 1284.4 Oct 2-3 PWG November Meeting Bourbon Orleans Hotel New Orleans, LA Nov 4 1284.3 Nov 5 1284.4 (Don't forget your absentee ballots) Nov 6-7 PWG ****************************************************************** Larry A. Stein Phone: (805)726-4420 President Fax: (805)726-4438 FarPoint Communications Web: http://www.fapo.com ******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23459; 31 May 96 15:33 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23455; 31 May 96 15:33 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa13283; 31 May 96 15:33 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA218740219; Fri, 31 May 1996 12:16:59 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA028480216; Fri, 31 May 1996 13:16:56 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21149; Fri, 31 May 96 13:06:27 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <31AF45BE@hpb15650.boi.hp.com>; Fri, 31 May 96 13:17:18 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: "'pmi@hpbs987.boi.hp.com'" Subject: FW: June Meeting Rate Change Date: Fri, 31 May 96 14:16:00 M Message-Id: <31AF45BE@hpb15650.boi.hp.com> Encoding: 30 TEXT X-Mailer: Microsoft Mail V3.0 FYI --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010 ---------- From: p1284_3[SMTP:p1284_3@lexmark.com] Sent: Friday, May 31, 1996 1:16 PM To: Multiple recipients of list Subject: June Meeting Rate Change Sorry, when I put out the meeting notice I listed the room rate at $199 (Can). This is for the executive floor. The lower rate is $159 (Can). Be sure to mention the FarPoint group name and to make your reservations by Friday, May 31. Thanks, Larry ****************************************************************** Larry A. Stein Phone: (805)726-4420 President Fax: (805)726-4438 FarPoint Communications Web: http://www.fapo.com ******************************************************************   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29330; 6 May 96 17:28 EDT Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa29325; 6 May 96 17:28 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa18357; 6 May 96 17:28 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA180987241; Mon, 6 May 1996 14:14:01 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA161887237; Mon, 6 May 1996 15:13:57 -0600 Received: from hpb15650.boi.hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA03070; Mon, 6 May 96 15:03:39 -0600 Received: by hpb15650.boi.hp.com with NT SMTP Gateway ver 31 id <318E6B9C@hpb15650.boi.hp.com>; Mon, 06 May 96 15:14:04 M Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Binnur Al-Kazily To: 'Steve Waldbusser' Cc: "'pmi@hpbs987.boi.hp.com'" Subject: Printer MIB & references to Intefaces group Date: Mon, 06 May 96 16:13:00 M Message-Id: <318E6B9C@hpb15650.boi.hp.com> Encoding: 12 TEXT X-Mailer: Microsoft Mail V3.0 Steve, At the last PWG meeting, we had discussions on whether to have the Interfaces Group of MIB-II (RFC 1213) to require compliance with the Evolution of the Interfaces Group of MIB-II (RFC 1573). We are leaning towards keeping the references as is, but we are also wondering what would be your recommendation. --- Binnur Al-Kazily Hewlett-Packard Company Integrated Network Solutions binnur@boi.hp.com (208)396-6372 KB7WYD DoD #2010   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28749; 8 May 96 20:15 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa28745; 8 May 96 20:15 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa20885; 8 May 96 20:15 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA294260287; Wed, 8 May 1996 17:04:48 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA284630284; Wed, 8 May 1996 18:04:44 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA22822; Wed, 8 May 96 17:54:25 -0600 Received: from mail.sharplabs.com ([204.75.175.200]) by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA020140275; Wed, 8 May 1996 17:04:35 -0700 Received: from sla5c by mail.sharplabs.com (SMI-8.6/SMI-SVR4) id QAA14622; Wed, 8 May 1996 16:54:45 -0700 Received: by sla5c (SMI-8.6) id QAA07745; Wed, 8 May 1996 16:54:35 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Randy Turner Message-Id: <9605081654.ZM7743@sla5c.sharplabs.com> Date: Wed, 8 May 1996 16:54:35 -0700 In-Reply-To: Larry Stein "Ping Request" (May 8, 5:17pm) References: <199605082120.AA23457@interlock.lexmark.com> X-Mailer: Z-Mail (3.2.1 10apr95) To: p1284_3@lexmark.com Subject: Re: Ping Request Cc: pmi@hpbs987.boi.hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii I am planning on attending 1284.3,1284.4 and PWG meetings. (Ping!) Rt   Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23326; 31 May 96 15:23 EDT Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23322; 31 May 96 15:23 EDT Received: from paloalto.access.hp.com by CNRI.Reston.VA.US id aa13164; 31 May 96 15:23 EDT Received: from hpdmd48.boi.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA156219409; Fri, 31 May 1996 12:03:30 -0700 Received: from hpbs987.boi.hp.com by hpdmd48.boi.hp.com with SMTP (1.37.109.16/15.5+ECS 3.4 Openmail) id AA288309406; Fri, 31 May 1996 13:03:27 -0600 Received: from hp.com by hpbs987.boi.hp.com with SMTP (1.37.109.4/15.5+IOS 3.12) id AA21128; Fri, 31 May 96 12:53:00 -0600 Received: from uscore.underscore.com ([199.125.69.1]) by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA088189393; Fri, 31 May 1996 12:03:13 -0700 Received: by uscore.underscore.com (Smail3.1.28.1 #5) id m0uPZNn-000US2C; Fri, 31 May 96 14:57 EDT Message-Id: Date: Fri, 31 May 96 14:57 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: JK Martin To: lstein@fapo.com Subject: Re: Change in Ultimate Meeting Schedule Cc: pmi@hpbs987.boi.hp.com Hi, Larry. I have a real schedule conflict with having the October meetings the first week in October. Can we move the meetings to the following (or any other) week in October? ...jay